Noindex Gets Traffic

This check fires when a URL carries a noindex directive but Search Console still reports impressions and clicks for it. On the surface that reads like a bug in Google. It usually is not. Noindex is a request that only takes effect once Google recrawls the page and sees the tag, so there is always a window where a page is marked noindex in your code but still sitting in the index from its last successful crawl. The interesting question is whether you are looking at normal lag or a genuine conflict that will keep the page indexed indefinitely.

What "noindex gets traffic" actually means

A noindex directive tells search engines to drop a page from their index. You deliver it one of two ways: a meta robots tag in the HTML head, <meta name="robots" content="noindex">, or an HTTP response header, X-Robots-Tag: noindex. Both are equally valid. The key detail people forget is that the directive is processed at crawl time. Google has to fetch the page, render it, and read the tag before it will act. Until that happens, the old indexed version stays live and can keep ranking.

So a page that gets traffic despite a noindex is Google telling you: "I have this URL in my index from an earlier crawl, and I have not yet processed your removal request." If you added the tag last week, that is expected. If the tag has been there for two months and the page is still ranking, something is stopping Google from seeing or trusting it.

Why it matters

Two reasons, pulling in opposite directions. First, if you genuinely want this page gone, the traffic is a symptom that your removal is not sticking, and you need to fix the underlying block. Second, and this trips people up more often, the traffic is a hint that maybe you noindexed something you should not have. I have seen a category page, a high-converting comparison page, and an entire paginated archive get noindexed by a careless plugin setting or a staging config that shipped to production. The page kept ranking for a while, revenue looked fine, and then the recrawl landed and the traffic fell off a cliff. If a noindexed URL is bringing in real clicks, confirm that killing it is actually what you want before you help Google along.

The recrawl lag versus real conflict decision

How to detect and diagnose it

Start with the one tool that gives you Google's own view: the URL Inspection tool in Search Console. Paste the URL, look at the indexing status, and use "Test live URL" to see what Googlebot fetches right now. This tells you whether Google currently sees the noindex tag and when it last crawled the page. If the live test shows the noindex but the indexed version does not reflect it yet, you are in lag territory.

• Screaming Frog: crawl the URL and check the Directives tab. Confirm the meta robots value and the X-Robots-Tag header. Run "Render" mode if the tag is injected by JavaScript, because a raw fetch will miss it.
• Server logs: confirm Googlebot is actually reaching the URL and getting a 200. If the page returns a 200 but is blocked in robots.txt, Google cannot read the noindex at all.
• curl: curl -sI https://example.com/page shows response headers so you can catch an X-Robots-Tag that contradicts the meta tag, or vice versa.
• Sitebulb: flags indexability conflicts across the whole site so you can see if this is one page or a pattern.

The classic conflicts that keep a noindex from working

How to fix it, step by step

1. Decide if you actually want it gone. If the traffic is valuable, the right fix might be to remove the noindex, not enforce it. Do this first.
2. Confirm the tag is really there. Use URL Inspection "Test live URL" and a raw curl -sI. Check both the meta robots tag and the X-Robots-Tag header.
3. Rule out a robots.txt block. This is the single most common reason a noindex fails. A blocked page cannot be crawled, so the tag is never read. Allow crawling.
4. Kill any conflicting signals. One page, one clear directive. Remove contradictory tags and headers.
5. Purge caches. Make sure Googlebot gets the current version, not a stale CDN copy.
6. Speed it up if urgent. Use the Removals tool in Search Console for a temporary block while the recrawl catches up. It is not permanent, but it hides the page fast.
7. Wait and recheck. After Google recrawls, the impressions should decay to zero. Recheck in URL Inspection after a couple of weeks.

What good looks like

A clean noindexed page returns a 200, is crawlable (not blocked in robots.txt), and serves a single unambiguous noindex directive that Googlebot can read on fetch. Within a few weeks of the last crawl, its impressions in Search Console trend to zero and it drops out of the index. There is no contradicting X-Robots-Tag, no JavaScript-only tag, and no stale cache in the way.

FAQ