Noindex is a page-level directive that instructs search engines not to include a specific URL in their search index. Delivered via a meta robots tag or X-Robots-Tag HTTP header, it keeps the page reachable by direct URL while hiding it from search results. About 5.3% of web pages use noindex (Ahrefs data).
Not every page on your site should appear in search results. Staging environments, thank-you pages, admin panels, tag archives, and thin content are all legitimate noindex candidates. Getting this right protects the quality signals of pages that do deserve to rank.
What is noindex?
Noindex is a crawl directive — a signal from your site to search engine crawlers about how to handle a specific URL. Unlike robots.txt, which operates at the crawl level, noindex operates at the index level: Googlebot can still visit and crawl the page; it simply will not add it to the index or serve it in search results.
The two standard implementations are:
<meta name="robots" content="noindex">
# Google-specific variant
<meta name="googlebot" content="noindex">
# HTTP header (for non-HTML files like PDFs)
X-Robots-Tag: noindex
Both methods are honored by all major search engines. The X-Robots-Tag method is the only option for PDFs, images, and other non-HTML resources.
Noindex and robots.txt are not interchangeable. If you block a page with robots.txt, Googlebot cannot crawl it — meaning it cannot read the noindex tag. A page blocked by robots.txt can still appear in search results if Google discovers it through backlinks from other sites. For reliable de-indexing, use the noindex tag and allow crawling.
Why noindex matters for SEO quality
Every page that appears in your index contributes to how Google evaluates your site as a whole. Poor quality pages indexed alongside strong pages can dilute your domain's quality signals. Four reasons to use noindex strategically:
- Quality signal protection. Google's Helpful Content system evaluates content quality at the domain level. Thin pages, duplicate pages, and low-value archived content indexed alongside your strong pages can drag down your entire domain's perceived quality.
- Crawl budget management. Sites over 50 pages should monitor how Googlebot allocates crawl budget. Pages repeatedly crawled but never indexed (because they have noindex) eventually get crawled less frequently — freeing budget for valuable content.
- Duplicate content control. Faceted navigation, filter pages, and sort parameters often create hundreds of near-identical URLs. Noindexing the variants prevents duplicate content from fragmenting ranking signals.
- Staging and admin protection. Development environments, preview pages, and internal admin panels should never appear in search. A forgotten staging site with identical content to your live site can trigger duplicate penalties.
How noindex works technically
The noindex directive is processed during Googlebot's crawl of the page. Here is the sequence:
- Googlebot requests and loads the page (it must be crawlable).
- It reads the meta robots tag or HTTP header.
- It removes the page from the index (or prevents it from being added).
- Over subsequent crawls, Googlebot reduces crawl frequency for consistently noindexed URLs.
Combining directives
Noindex can be combined with follow or nofollow to control what happens to links on the page:
| Directive | Indexed? | Link equity flows out? | Use case |
|---|---|---|---|
noindex | No | Yes | Default — blocks indexing, allows link flow |
noindex, follow | No | Yes | Same as above (explicit follow) |
noindex, nofollow | No | No | Full block — no indexing, no link equity out |
none | No | No | Shorthand for noindex, nofollow |
What pages should be noindexed?
Apply noindex to pages that exist for functional reasons but have no value as search results:
| Page type | Why noindex |
|---|---|
| Thank-you / confirmation pages | No search value; only relevant post-action |
| Login, account, cart pages | Personal state; irrelevant to searchers |
| Staging / development URLs | Duplicate of live site; duplicate content risk |
| Tag and author archive pages | Thin, often duplicate of category pages |
| Faceted navigation / filter URLs | Near-duplicate; fragments ranking signals |
| Internal search result pages | User-specific, duplicate-prone |
| PDF versions of indexed content | Duplicate of existing HTML page |
Real noindex examples
1. WordPress tag pages
A WordPress blog with 400 tag pages — each containing a handful of posts — creates 400 near-duplicate thin pages. Nofollowing all tag archives removes the duplicate risk and consolidates ranking signals to the actual posts and category pages.
2. E-commerce filter URLs
/shoes/?color=blue
/shoes/?color=blue&size=10
/shoes/?sort=price-asc
# Only this should be indexed:
/shoes/
3. Staging environment
<meta name="robots" content="noindex, nofollow">
Noindex vs robots.txt — which to use
Use noindex when
- You want to prevent indexing but allow crawling
- Pages have internal links that should pass equity
- You need page-level precision
- The page may be re-indexed in future
- You want Google to discover the directive reliably
Use robots.txt when
- You want to save crawl budget at scale
- Entire directories should be crawl-blocked
- Pages have no link value to preserve
- You are managing a very large site (1M+ URLs)
- Speed of blocking matters more than precision
6 best practices for using noindex correctly
- Never block crawling and noindex simultaneously. If Googlebot can't crawl the page, it can't read the noindex tag. Use robots.txt disallow only for pages you genuinely want to prevent from being crawled and indexed.
- Audit your noindex pages quarterly. Pages you noindexed last year may now have enough content to deserve ranking. Review, improve, and remove noindex to re-enter the index.
- Remove noindex from staging before going live. Forgotten staging directives are one of the most common causes of sudden ranking drops after a site migration.
- Use Search Console to monitor indexation. Google Search Console's Coverage report shows which pages are indexed, noindexed, excluded, and crawled but not indexed. Review this monthly.
- For large-scale de-indexing, use both robots.txt and noindex. Robots.txt stops crawl budget waste immediately; noindex ensures the directive is recorded even if Google crawls through a sitemap or backlink.
- Noindex, don't delete, thin content you plan to improve. A page with potential value is better noindexed and improved than deleted. Deletion permanently destroys any link equity the URL earned.
Every year, sites launch with the staging noindex still active. Google crawls the live site, reads the noindex tag, and removes every page from search results — often within 48-72 hours. Always include "remove noindex" as the final step of any site launch checklist.
Common noindex mistakes to avoid
- Blocking with robots.txt and expecting noindex to work — Googlebot can't read the noindex tag if it can't crawl the page.
- Nofollowing your entire site after a CMS migration — Staging plugins that apply noindex globally are often not removed on launch day.
- Using noindex as a long-term replacement for deleting content — Noindexed pages still consume crawl budget. Eventually delete or redirect genuinely worthless content.
- Noindexing pages you want to rank — Double-check that category pages, pillar posts, and product pages are not accidentally noindexed after theme or plugin updates.
- Not tracking which pages are noindexed — Maintain a documented list of intentionally noindexed pages so accidental removals are caught quickly.
Frequently asked questions
Noindex tells search engines not to include a page in their search index. The page remains accessible to visitors who have the direct URL, but it will not appear in search results and does not pass ranking signals.
Google typically removes a noindexed page from search results within a few days to a few weeks, depending on crawl frequency. For immediate removal, use Google Search Console's URL Removal tool.
Noindex is more precise — it blocks indexing but allows crawling so link equity can flow. Robots.txt blocks crawling but does not prevent indexing. For pages you want out of the index, use noindex. For large-scale crawl-budget management, use robots.txt.
noindex alone tells Google not to index the page but still allows link equity to pass through outbound links on that page. noindex, nofollow prevents indexing and also stops link equity from passing through the page's outbound links.
Noindex pages with potential future value — thin content you plan to improve, seasonal pages, or pages in development. Delete permanently worthless content and return a 404 or 410. Review noindexed pages quarterly to decide if they can be improved and re-indexed.
Related glossary terms
Sources
