How Long Does It Take Google to Notice a Noindex Tag?

From hours to weeks, depending entirely on how often Google recrawls the page — with no fixed number to plan around.

This is one of the most common questions about deindexing, and the honest answer is unsatisfying: it depends, and there's no published number to rely on. But "it depends" isn't the whole story — the factors it depends on are well understood, and they explain why silent deindexing is such a persistent problem.

It's entirely about recrawl frequency

Google doesn't watch pages continuously. It revisits them on a schedule determined by crawl frequency, which itself is driven by a mix of the page's authority, how often it historically changes, how many other pages link to it, and the site's overall crawl budget. A homepage on a high-traffic, frequently-updated site might get recrawled within hours. A low-traffic page deep in a site's structure might go weeks between crawls.

What that means in practice

If a noindex tag (or an X-Robots-Tag, or a canonical mismatch) gets introduced on a high-authority, frequently-crawled page, Google can notice and act on it within the same day in some cases. On a page Google visits rarely, the same change can sit undetected — meaning the page continues appearing in search results for a while, or continues being absent after the noindex is removed — for considerably longer, with no way to force Google to look sooner short of explicitly requesting a recrawl.

You can request a recrawl, but it's not instant either

Search Console's URL Inspection tool has a "Request indexing" option, which nudges a specific URL toward the front of the crawl queue rather than waiting for its normal schedule. It genuinely helps, but it's a request, not a guarantee of immediate action, and it doesn't scale to checking every page on a site regularly — it's meant for one-off nudges, not a monitoring strategy.

Why this makes silent deindexing genuinely dangerous

The unpredictable timeline cuts both ways, and both directions are bad. A change that removes a page from search can take a while to fully manifest, meaning the damage compounds before it's even visible in most metrics. And when someone does notice a traffic drop, there's no way to know from the traffic data alone how long the underlying cause has actually been in place — the noindex tag could have shipped yesterday or a month ago, and traffic-graph analysis alone can't tell you which.

What actually closes the gap

Since there's no fixed timeline to plan around, the only reliable fix is checking the actual indexability signals — noindex tags, X-Robots-Tag headers, canonical tags, robots.txt — directly and on a recurring schedule, independent of when Google happens to recrawl. That doesn't change how fast Google itself acts, but it does mean the underlying cause gets caught and fixed within one check cycle instead of being discovered by accident, days or weeks after the fact, via a traffic graph.