The noindex Tag: When to Use It and When It's Hurting You
Most indexing problems are ambiguous. A page sits unindexed and you are left guessing among a dozen causes. The noindex tag is the exception. It is one of the few instructions Google treats as a rule rather than a suggestion: if Googlebot can read a noindex on your page, that page will be dropped from the index, however good the content and however many links point at it. That makes noindex the sharpest tool in technical SEO, in both senses. Used deliberately, it keeps clutter out of search results. Left behind by accident, it removes pages you were counting on, and it does so silently.
This guide covers what the tag actually does, where it belongs, and the handful of ways it ends up hurting sites that never meant to use it.
What the noindex tag actually does
A noindex is a one-line instruction that tells search engines not to include a page in their results. It comes in two forms. The common one is a meta tag in the page’s <head>:
<meta name="robots" content="noindex">The other is an HTTP response header, X-Robots-Tag: noindex, set by the server rather than the page. The header form matters for files that have no HTML head, PDFs for instance, and it is worth knowing it exists because it is invisible in the page source. This post concentrates on the meta tag.
Two properties of noindex are worth being precise about. First, it is a rule Google obeys, not a hint it weighs. A canonical tag is a suggestion Google may override. A noindex is not. Second, it acts at indexing time, not crawling time. Googlebot still has to fetch the page to see the tag. Crawling and indexing are separate steps, and noindex only governs the second one. That distinction is the source of the most common noindex mistake, which we will come to.
When the noindex tag is the right call
Some pages should exist for users but not for search. Typical candidates:
- Internal search result pages. They generate endless thin URLs that compete with your real category and content pages.
- Thank-you and confirmation pages. Anyone landing on these from Google skipped the step that gives the page meaning.
- Thin utility pages. Login screens, cart pages, print views, filtered archives that duplicate a main listing.
- Low-value tag and date archives on blogs, where the archive adds navigation for readers but nothing for searchers.
- Paid or gated landing page variants you run for campaigns and do not want competing with the canonical page.
The common thread is honest: these pages serve visitors who are already on your site, and would serve a searcher badly. Marking them noindex is not hiding anything. It is telling Google the same thing you would tell a visitor who arrived there cold: this is not the page you wanted.
What noindex is not for is duplicate content with a clear preferred version. That is a canonical’s job, because a canonical consolidates signals to the preferred URL, while a noindex simply discards the page. The two solve different problems, and swapping one for the other usually loses something.
When it’s hurting you
The damage noindex does is almost never the result of a bad decision. It is the result of an old decision nobody revisited. The recurring cases:
The staging leftover. A site is built behind a sitewide noindex, sensibly, and then launched without removing it. Everything works, traffic from ads and social arrives, and organic search stays at zero. Because nothing errors, this can survive for weeks. A sitewide noindex is the first thing to rule out when a whole site is missing from Google.
The plugin or theme setting. CMS plugins often expose noindex as a checkbox per page, per template, or per content type. A setting toggled during a redesign, or inherited from an imported theme, can mark whole sections noindex without anyone editing a line of code.
The template accident. A noindex placed in a shared template lands on every page using that template. Intending to noindex one archive page and actually noindexing every paginated URL under it is a classic version.
The stale cleanup. A page was noindexed years ago for a reason that no longer applies, the page has since been rewritten into something genuinely useful, and it still cannot appear in search because nobody remembers the tag is there.
A noindex is only one of several reasons a decent page stays out of the index, and it is worth diagnosing alongside the others; we have catalogued the usual suspects in six reasons Google declines to index a page that looks fine.
The noindex Google cannot see
Here is the trap the crawling-versus-indexing distinction sets. For a noindex to work, Google must be able to fetch the page and read the tag. If the page is also blocked in robots.txt, Googlebot never fetches it, never sees the noindex, and the instruction does nothing. Google’s own documentation is explicit on this point: a page blocked from crawling can still be indexed from links elsewhere, appearing in results as a bare URL without content.
So the combination that feels doubly safe, robots.txt block plus noindex tag, is actually self-defeating. If you want a page out of the index, let it be crawled so the noindex can be read. If you want to save crawl capacity, block it in robots.txt and accept that blocking is a crawling control, not an indexing control. Pick the tool that matches the outcome you want, not both.
Finding the noindex you didn’t intend
For a single suspect page, the URL Inspection tool in Search Console will tell you whether Google sees a noindex. For a site’s worth of pages, you need something more systematic: a crawl of your own site that reports the robots meta value per URL, checked against the list of pages you expect to rank.
This is also where a submission tool should be honest with you. When AIndexify runs its preflight check on a submitted URL and detects a noindex, it does not submit and quietly bill you. It reports Couldn’t check and refunds the credit, because asking Google to index a page that instructs Google not to index it wastes the request. That status showing up against a URL you expected to rank is itself the diagnosis: the page is carrying a noindex you probably forgot about. Removing the tag is only the first step, of course; after that the page still has to earn its place through the normal process described in our full guide to Google indexing.
The noindex tag deserves more respect than it gets. It is the rare instruction Google follows without argument, which makes it powerful on the pages you chose and quietly expensive on the pages you forgot. If you are not certain which of yours is which, see where your pages actually stand: submit your URLs and read what comes back, status by status.