How to Catch a Noindex Before It Kills Your Rankings

A stray noindex in production is one of the fastest ways to lose organic traffic, and one of the quietest. The site works, the page loads fine, nothing errors, and Google slowly drops the page from its index. Here's how it happens, how to find it, and how to make sure you're the first to know instead of the last.

Deltio checks your client sites daily and alerts you on Slack the moment a noindex appears where it shouldn't. From £20 a month.

The noindex tag does exactly one thing: it tells search engines not to include a page in their index. That's genuinely useful for thank-you pages, internal search results, staging environments and duplicate content. It becomes a disaster when it lands on a page you very much want ranking, and nobody notices for three weeks.

How a noindex ends up in production

Almost always by accident, and almost always in a way that leaves no trace in your normal workflow:

• Staging leaks to production. Staging sites are usually set to noindex so Google ignores them. When a deploy copies staging config to production, the noindex comes along for the ride.
• A CMS or plugin setting. A checkbox in the CMS, an SEO plugin default, or a theme update flips a page or a whole section to noindex.
• A developer being cautious. Someone adds noindex to a new section while it's being built and forgets to remove it at launch.
• A robots meta or an X-Robots-Tag header. The tag can live in the HTML or in the HTTP header, and the header version is easy to miss because you can't see it in the page source.

In every case the page looks perfectly normal to a human. That's the trap.

How to check for noindex manually

If you want to check a specific page right now, here are the reliable ways:

• View the page source and search for noindex. Look inside a meta robots tag, something like <meta name="robots" content="noindex">.
• Check the HTTP headers for an X-Robots-Tag: noindex. This one isn't in the HTML, so a source view alone will miss it. Browser dev tools, under the Network tab, show response headers.
• Use Google Search Console. The URL Inspection tool tells you whether a page is indexable and flags "Excluded by noindex tag." Search Console is authoritative, but it's reactive and often slow to reflect a fresh change.
• Run a crawler like Screaming Frog across the site and filter for pages returning noindex. Great for a full sweep, but it's a manual job you have to remember to run.

These all work. The problem is they all rely on you deciding to look. A noindex added on a Friday doesn't announce itself, so unless you happen to inspect that page, you won't find it until the traffic report does.

The real fix: get told automatically

Manual checks catch a noindex you go looking for. What actually protects a client site is a system that watches for it and tells you the moment it appears, on every page, without you remembering to check.

That's the difference between checking and monitoring. A checker answers "is this page noindexed right now?" A monitor answers "did any page just become noindexed?" and pushes that answer to you.

How Deltio catches it

Deltio scans the pages in your sitemap on a daily cycle and checks their indexing signals, including noindex in both the meta tag and the HTTP header. When a page that was indexable yesterday carries a noindex today, Deltio sends a plain alert to Slack: this page on this client site is now set to noindex. You see it the same day, before Google has finished recrawling, while it's still a two-minute fix instead of a month of lost traffic.

It does the same for the related indexing signals that fail the same quiet way: robots.txt changes, canonicals pointing somewhere new, and URLs dropping out of the sitemap.

Stop finding out from the traffic graph

Add your first client site, connect Slack, and Deltio starts watching the same day. Start your 14-day trial and make sure the next stray noindex reaches you first.