TECHNICAL
Noindex Tag: When to Use It and How to Implement It Correctly
The noindex tag tells search engines not to include a page in their index. Here's a complete guide to when noindex is appropriate, how to implement it via meta robots and X-Robots-Tag, and the common mistakes that cause pages to remain indexed despite a noindex directive.
Published July 13, 2026 · 8 min read
The noindex tag is a directive that tells search engines not to include a page in their index. When a search engine crawls a page with a valid noindex directive and honours it, the page won't appear in search results for any query — it's effectively invisible to organic search regardless of how much link equity points to it or how strong the content is.
Noindex is a powerful tool that's frequently misused in both directions: applied too broadly (noindexing pages that should rank) and too narrowly (leaving junk pages indexed that dilute site quality). Understanding when noindex is appropriate — and when it isn't — is one of the most consequential technical SEO decisions on any site.
The two implementation methods
Meta robots tag
The most common noindex implementation is the <meta name="robots" content="noindex"> tag in the <head> of the HTML page:
<head>
<meta name="robots" content="noindex">
</head>
Variants:
content="noindex"— don't index, but follow links (Googlebot still crawls links on the page)content="noindex, nofollow"— don't index, and don't follow any links on the pagecontent="noindex, follow"— explicitly stating the default follow behaviour alongside noindex
For Google specifically, you can target the directive to Googlebot only:
<meta name="googlebot" content="noindex">
This affects only Googlebot while allowing other crawlers to index the page — useful for pages you want in Bing but not Google (rare in practice).
X-Robots-Tag HTTP response header
The X-Robots-Tag is an HTTP response header that provides the same noindex directive without requiring HTML access. It's the only noindex method that works for non-HTML files (PDFs, images, XML files):
X-Robots-Tag: noindex
Implementation in Next.js (via next.config.mjs headers or app/robots.ts), nginx, Apache, or any server/CDN that allows response header customisation. The X-Robots-Tag is also useful when you can't modify the page's HTML directly — for example, applying noindex to an entire subdirectory via server configuration without editing each page template.
What does NOT work for noindex
robots.txt disallow. Blocking a URL in robots.txt prevents Googlebot from crawling it but does not prevent Google from indexing it. A URL blocked in robots.txt can still appear in search results if Google discovers the URL through external links — it will appear as a "URL-only" result with no snippet. If you want a page completely removed from Google's index, you need a noindex directive that Googlebot can actually read — which means Googlebot must be able to crawl the page. Paradox: to successfully noindex a page, you must allow it to be crawled.
Removing the page from the sitemap. Sitemaps declare which pages should be indexed; removing a URL from the sitemap doesn't instruct Google to deindex it. Pages already indexed will remain indexed after sitemap removal — the sitemap omission only prevents the sitemap from being a discovery source for new pages.
When noindex is appropriate
Paginated archive pages (pages 2, 3, 4... of a blog archive or product category). Paginated pages typically have thin content relative to page 1 of the same archive and can dilute crawl budget. Common pattern: noindex paginated pages beyond page 1 while keeping page 1 indexed.
Search results pages (/search?q=...). Site search results are thin, non-canonical, highly variable, and provide no value to Google's users — they're a classic example of low-quality content that benefits from noindex.
Tag and author archive pages (on blogs where these archives exist). Tag pages for rarely-used tags are often near-empty and thin. Author pages for sites with one or two authors produce duplicate content from the author's post listing. Apply noindex selectively to low-value tag/author archives, not universally.
Staging and preview environments. If a staging site is publicly accessible (at staging.example.com or dev.example.com), noindex every page with <meta name="robots" content="noindex"> or a blanket X-Robots-Tag: noindex header at the server level, plus Disallow: / in the staging site's robots.txt.
Internal utility pages. Shopping cart pages (/cart), checkout confirmation pages (/order/thank-you), account dashboard pages (/account), and login pages (/login) should be noindexed — they contain no content for organic search and often have unique URL parameters per session that could create crawl budget problems if indexed.
Thin or duplicate product variants. E-commerce sites with large product variant structures (colour × size × material combinations) sometimes generate hundreds of near-identical URLs. Apply noindex to variant pages that are visually identical to the canonical product page, using the canonical product URL as the indexed version.
When noindex is a mistake
Noindexing pages you want to rank. The most catastrophic noindex error: applying a blanket noindex to a CMS template and accidentally noindexing thousands of content pages, or leaving a staging-mode noindex in place after a production launch. Always verify the production site's robots meta tag in the HTML source after launch.
Noindexing pages with good backlinks. A page that has earned quality backlinks but is thin or low-quality should be improved or consolidated — not noindexed. Noindexing a page with valuable backlinks wastes the link equity those links provide (equity flows into a noindexed page but can't be used for ranking).
Using noindex instead of canonicals for duplicate content. If you have multiple URL versions of the same page (with and without trailing slash, HTTP vs HTTPS, parameter variants), the correct tool is a canonical tag pointing all variants to the preferred URL — not noindex on the non-preferred variants. Canonical lets Googlebot consolidate signals; noindex tells Googlebot to completely ignore the page.
Noindexing pages blocked by robots.txt. If a page is blocked in robots.txt, Googlebot can't read the noindex tag — the page remains indexed from its previous crawl. Fix: allow crawling, let Googlebot read the noindex, then the page will drop from the index. After confirming deindexing, you can re-block in robots.txt if needed.
Verification and monitoring
After applying noindex, Google typically removes the page from its index within days to a few weeks, depending on crawl frequency. Monitor deindexing via:
- Google Search Console → Indexing → Pages — the "Excluded by noindex tag" section shows which pages GSC has confirmed as noindexed
- URL Inspection Tool in GSC — inspect a specific URL to see whether Google has registered the noindex directive and whether the page is still in the index
site:example.com/page-pathoperator in Google Search — if the page still appears after several weeks, the noindex may not be reaching Googlebot correctly
Run a DeepSEOAnalysis audit to surface pages with unexpected noindex directives — particularly pages where the noindex is inconsistent with sitemap inclusion (a page both in the sitemap and noindexed is a configuration conflict that should be resolved).
Frequently asked questions
Does noindex pass link equity?
No. A page with a noindex directive does not contribute to the ranking of other pages via internal or external links in the same way that an indexed page does. Link equity flows into a noindexed page from external links pointing to it, but the noindexed page does not accumulate ranking authority that it can then pass to other pages — it's effectively outside the ranking system. This is why noindexing pages with good backlinks is usually a mistake: those backlinks' equity is lost when the page is noindexed, rather than consolidating onto a canonical or redirecting to a relevant page.
Can I noindex a page and still have it crawled?
Yes. Noindex and crawling are independent. To successfully noindex a page, Googlebot must be able to crawl it to read the noindex directive — which means the page must not be blocked in robots.txt and must return a 200 response. A noindex directive on a page that's also blocked in robots.txt is invisible to Googlebot and ineffective. The correct pattern: allow crawling in robots.txt, implement noindex in the meta robots tag or X-Robots-Tag header, and verify in GSC that Google has registered the noindex status.
How long does noindex take to remove a page from Google's index?
Typically days to weeks, depending on how frequently Googlebot crawls the page. Pages that are crawled daily (high-traffic, frequently updated pages) may be deindexed within a few days. Pages crawled monthly may take 4–6 weeks. You can accelerate deindexing by using Google Search Console's URL Removal Tool for individual URLs — this temporarily removes the URL from search results within hours, while the noindex takes effect in the background. The URL Removal Tool is a temporary 6-month suppression, not a permanent removal — but combined with a persistent noindex directive, it provides immediate removal while the crawler processes the noindex.
Should I noindex or delete pages I don't want in Google's index?
It depends on whether the page has any backlinks or referral traffic. If a page has external backlinks: set up a 301 redirect to the most relevant live page — this preserves the link equity from the backlinks and removes the page from the index. If a page has no external backlinks and no traffic value: delete it and return 404 (or 410 for intentional permanent removal). If a page should exist but shouldn't be indexed (utility pages, thin archives): apply noindex and keep the page live. Noindex is not a substitute for improving or consolidating low-quality content — it only hides the problem from Google rather than resolving it.
MORE FROM THE BLOG
Related articles
11 min read
YouTube SEO: How to Rank Videos on YouTube and Google Search
YouTube SEO covers title optimisation, description keyword placement, chapters, thumbnails, closed captions, and the watch signals that drive YouTube and Google ranking.
Read →7 min read
Voice Search SEO: How to Optimise for Voice Queries and AI Assistants
How voice search queries differ from typed queries, what technical signals (FAQ schema, speakable schema, featured snippet eligibility) matter for voice results, and why optimising for voice search overlaps heavily with AI visibility.
Read →10 min read
TikTok SEO: How to Rank in TikTok Search and Get Discovered in Google
TikTok SEO covers how to optimise videos for TikTok's internal search algorithm, how TikTok content ranks in Google Search, and how TikTok presence feeds into AI answer systems.
Read →Run DeepSEOAnalysis on your own site.
Free, no signup. Technical SEO, Core Web Vitals, structured data, and AI visibility in one report.
Run a free audit →