What is the noindex Directive? Definition & Use Cases
Definition
noindex is a directive that tells search engines not to include a page in their search results. Unlike robots.txt, which blocks crawling, noindex allows the page to be crawled but excludes it from the index. It can be applied via a meta tag (<meta name="robots" content="noindex">) or an X-Robots-Tag HTTP header.
When to use noindex
- Thin or duplicate pages — internal search results, filtered category pages, paginated archives.
- Private content — staging environments, login pages, dashboards, account areas.
- Thank-you and confirmation pages — pages that should only be reached after a user action.
- Outdated content kept online for users but no longer worth ranking.
Common pitfalls
- Blocking with both robots.txt and noindex — if a crawler is blocked by robots.txt, it can never read the noindex directive, so the URL may still appear in results.
- Accidentally noindexing the entire site — a misconfigured CMS template can deindex production overnight. Always check before deploying.
- Forgetting the matching
nofollow— by default noindex still allows link signals to flow; pair withnofollowif you want to fully isolate the page.
noindex is the right tool when you want a page to exist for users but disappear from search. Combined with a clean XML sitemap and consistent internal linking, it keeps your indexable surface focused.
Related terms
robots.txt
The file that tells crawlers which parts of your site they can access.
XML Sitemap
The map you give search engines to discover and prioritize your pages.
nofollow
The link attribute that tells search engines not to pass ranking signals.
Internal Link
Links between pages on the same domain — the backbone of site structure.
Soft 404
A page that returns HTTP 200 but displays error content instead of useful information.
404 Error
What happens when a page can't be found — and how it affects SEO.