A noindex tag tells Google not to include a page in search results. Bryan Collins explains when to use noindex, how it works, and common mistakes to avoid.
A noindex tag is an instruction you give Google that says: “Don’t show this page in search results.” It’s a critical technical SEO tool — when used correctly, it improves your site’s overall quality. When used incorrectly, it silently removes important pages from Google.
After 30 years in SEO, noindex mistakes are among the most damaging I find during site audits. Here’s everything you need to know.
What the Noindex Tag Looks Like
The noindex directive is a meta robots tag placed in the <head> section of an HTML page:
<meta name="robots" content="noindex">
Or with additional directives combined:
<meta name="robots" content="noindex, nofollow">
<meta name="robots" content="noindex, follow">
noindex = Don’t show in search results
nofollow = Don’t follow any links on this page
follow (default) = Do follow links on this page
Most of the time, you want noindex, follow — you don’t want the page indexed, but you want Google to still follow links from it. Only use noindex, nofollow if you also don’t want link equity to pass through the page.
What Noindex Actually Does
What noindex does:
- Prevents the page from appearing in Google search results
- Removes the page from Google’s search index (if already indexed)
- Is a directive Google respects (not a “hint” — unlike nofollow links)
What noindex does NOT do:
- Stop Google from crawling the page (Google can still visit it to find the noindex tag)
- Prevent the page from being accessed by users with the direct URL
- Prevent the page from passing link equity (unless you also add nofollow)
When to Use Noindex
Pages That Should Be Noindexed
Thank-you / confirmation pages: The page someone lands on after submitting a form or completing a checkout. These have no organic search value and shouldn’t appear in results.
Login and account pages: User-specific pages with no public search value.
Admin and backend URLs: Any /wp-admin, /dashboard, or internal management URLs.
Internal search result pages: If your site has a search function generating URLs like /search?q=keyword, these thin results pages should be noindexed.
Tag and category archive pages (often): On blogs, tag pages like /tag/seo/ often contain thin, low-value content. Noindexing these keeps your index focused on substantive pages.
Paginated archive pages (sometimes): /page/2, /page/3 of blog listings often have thin content. Consider noindexing beyond page 1.
Staging/development sites: Your staging environment should always have noindex on every page to prevent development URLs from appearing in search results.
Duplicate location pages with thin content: Service pages that are identical except for a city name with no genuine unique content. Better to write unique content — but if you can’t, noindex is better than indexing thin duplicates.
PPC landing pages: Paid traffic landing pages optimized for conversion often aren’t optimized for organic search. Noindexing them keeps them out of results while preserving their conversion focus.
Pages That Should NOT Be Noindexed
- Your homepage
- Service and product pages you want to rank
- Blog articles and content pages
- Your about page
- Location/city pages with genuine unique content
- Any page you want to appear in Google
Noindex vs. Robots.txt: A Critical Distinction
This is one of the most commonly confused technical SEO concepts.
| Noindex | Robots.txt | |
|---|---|---|
| What it does | Removes page from search results | Prevents crawling |
| Google reads the tag | Yes (by crawling) | Checked before crawling |
| Page still crawlable | Yes | No (blocked) |
| Prevents indexing | Yes (if Google can read it) | Unreliable |
The critical mistake: Blocking a URL in robots.txt AND trying to noindex it. If robots.txt blocks a URL, Google can’t crawl the page — so it can’t read the noindex tag. The page may still get indexed from external links even though you think you’ve prevented it.
Correct approach:
- To delist from search results: Use noindex (don’t block in robots.txt)
- To stop crawling (conserve crawl budget): Use robots.txt (but accept the page may still be indexed from external links)
How to Verify Noindex Implementation
Google Search Console URL Inspection
- Open GSC → URL Inspection
- Enter the URL you added noindex to
- Under “Coverage” → “Crawled” data, look for “Indexing allowed? No – ‘noindex’ detected in ‘robots’ meta tag”
This confirms Google has read and registered your noindex directive.
Search Console Coverage Report
GSC → Index → Pages → “Not Indexed” tab shows all noindexed pages, including:
- “Excluded by ‘noindex’ tag” — pages you deliberately noindexed
- Check this list periodically to ensure no important pages appear here accidentally
Screaming Frog Crawl
Screaming Frog’s Directives tab shows the meta robots content for every page it crawls. Filter by “noindex” to see all noindexed pages in bulk.
Common Noindex Mistakes
Accidental sitewide noindex: The most catastrophic mistake — a developer adds noindex to the site template during staging and forgets to remove it before launch. The entire site disappears from Google within weeks. Check this immediately after any redesign or development work.
Noindexing important pages: Check the list of noindexed pages in GSC monthly and verify nothing important is included.
Blocking noindexed pages in robots.txt: If you block a URL in robots.txt, Google can’t crawl the page to read your noindex tag. The page may still be indexed.
Expecting immediate results: Removing a noindex tag doesn’t instantly re-index the page. Google must crawl the page again — which can take days to weeks. Use GSC’s “Request Indexing” to speed this up.
Frequently Asked Questions
What is a noindex tag?
A noindex tag is an HTML meta tag that instructs search engines not to include a page in their search results. It appears in the section as <meta name='robots' content='noindex'>. Pages with noindex can still be crawled but won’t appear in Google search results.
When should I use noindex? Use noindex on: thank-you pages, login and account pages, admin areas, internal search result pages, tag and archive pages with thin content, staging environments, duplicate content pages you don’t want indexed, and landing pages used only for paid ads that shouldn’t rank organically.
What is the difference between noindex and robots.txt? Noindex tells Google not to show a page in search results (but Google can still crawl it). Robots.txt tells Google not to crawl specific URLs at all. If you block a page in robots.txt, Google can’t read the noindex tag on that page — so it may still index it based on external links.
How do I add a noindex tag to a page?
Add <meta name='robots' content='noindex'> in the <head> section of the page HTML. In WordPress with Yoast SEO, toggle ‘Allow search engines to show this Post in search results’ to off. In Rank Math, go to the Advanced tab and set Robots Meta to ‘noindex’.
Does noindex hurt SEO? Noindex on the right pages improves SEO by preventing thin, duplicate, or irrelevant pages from diluting your site’s overall quality signals. Noindex on the wrong pages removes them from Google entirely — which obviously hurts their ability to rank.
How do I check which pages on my site are noindexed? In Google Search Console, Coverage report → Excluded → ‘Excluded by noindex tag’ shows all pages Google has seen the noindex directive on. Screaming Frog crawl will also identify pages with noindex in their meta robots tags under the Directives tab.
What happens when you remove a noindex tag? Removing noindex allows Google to index the page on its next crawl. Submit the URL to Google Search Console’s URL Inspection tool and click ‘Request Indexing’ to accelerate the crawl. Pages may take days to weeks to appear in search results after noindex removal, depending on your crawl frequency.
Bryan Collins is an SEO consultant based in Piscataway, NJ, with 30+ years of experience helping small businesses grow through content and search. He is a U.S. Marine Corps veteran and the author of Why Your Website Isn’t Ringing.