Accidental noindex: how to tell if Google is dropping your pages
A single wrong meta tag can knock entire sections of your site out of Google's index. Here's how to check it in 2 minutes.
What noindex actually does
With noindex you explicitly tell Google: "Do not include this page in the index." Exactly right for login pages, shopping carts or duplicates — but catastrophic when it ends up by accident on important content pages or even your homepage.
How it happens by accident
- A relaunch goes live, but the "Discourage search engines" checkbox from the staging phase is still set (WordPress: Settings → Reading).
- An SEO plugin resets its default rules after an update.
- A template/component suddenly renders a
noindexon every page. - The
X-Robots-Tag: noindexheader comes from the server — in which case there's nothing to see in the HTML at all, which makes it especially insidious.
How to check it in 2 minutes
- Open the page in your browser, view the source code, search for
noindex. - Important: also check the HTTP headers (Developer Tools → Network → Response Headers →
X-Robots-Tag). Many people overlook exactly this. - In Google Search Console, use the URL Inspection tool — it shows "Indexing allowed? No".
- Or you simply enter the domain into Canary — we check the meta tag and the headers and let you know right away.
Why it's so dangerous
Unlike a 404, noindex works quietly: the page loads perfectly normally for visitors, looks flawless — and yet silently disappears from Google. Often it isn't noticed until traffic has already dropped by double digits. That's exactly why "noindex on content pages" is one of Canary's critical findings, with an immediate alert.