noindex
The noindex directive tells search engines not to include a page in their search index. Applied via a meta robots tag or HTTP header, it prevents the page from appearing in search results.
Reviewed by Alexander Yarovenko · Updated: 2026-09-18
What is noindex?
The noindex directive is an instruction to search engine crawlers telling them not to include a specific page in their index — meaning it will not appear in search results. Unlike blocking a page in robots.txt (which prevents crawling), noindex allows crawlers to visit the page but instructs them not to show it in search results.
How to Implement noindex
<!-- Meta robots tag in <head> -->
<meta name="robots" content="noindex">
<!-- Also prevent following links on the page -->
<meta name="robots" content="noindex, nofollow">
<!-- HTTP header (for PDFs or non-HTML files) -->
X-Robots-Tag: noindexWhen to Use noindex
- Thank-you pages and order confirmation pages
- Internal search result pages
- Faceted navigation pages (filter combinations)
- Staging and development environments
- Thin or duplicate content pages that can't be merged
- Tag and category archive pages with little unique value
- Login and account pages
- Printer-friendly page versions
noindex vs robots.txt Disallow
| noindex | robots.txt Disallow | |
|---|---|---|
| Prevents crawling | ❌ No | ✅ Yes |
| Prevents indexing | ✅ Yes | ❌ No (can still be indexed from links) |
| PageRank flow | Links on page still pass PageRank (if follow) | Crawl blocked; links may not be followed |
Critical error: Never block a page in robots.txt AND add noindex to it. If crawlers can't access the page, they can't read the noindex tag — meaning it may remain indexed. Remove the robots.txt block to allow crawling if you want noindex to take effect.
How to use this concept in SEO
Use noindex when a public page may be crawled but should not appear in search. Google must be able to crawl the page to see the directive, so blocking the same URL in robots.txt is contradictory.
Audit checklist
- Confirm that the implementation matches the page purpose and the user task.
- Check the HTTP response, rendered HTML, canonical, robots rules, and internal links together.
- Use Search Console and analytics to verify the result instead of relying on one crawler signal.
- Test a representative URL on mobile and desktop after deployment.
- Document the expected outcome so regressions can be detected in the next audit.
Practical example
Account, internal-search, and thin utility-result pages use noindex, follow; valuable landing pages remain indexable and receive self-canonicals.
How to validate the result
Record the current crawl, indexation, performance, and traffic state before changing anything. Recheck the affected template and a representative URL after deployment, then monitor Search Console over the following crawl cycle. A technical change is complete only when the live response and Google’s observed state agree.