Noindex

Why it matters

The noindex directive tells Google not to include a page in its index. When correctly set, that is intentional. When a page that should be indexed carries a noindex tag, it disappears from search results without raising an error anywhere.

The directive is binary. A page with <meta name="robots" content="noindex"> or an X-Robots-Tag: noindex HTTP header will be dropped from the index entirely, typically within days of the next crawl.

The mistake is common during development. Staging environments are routinely blocked to prevent them appearing in search results. A production deployment that carries over the staging noindex tag is a quiet catastrophe. The page ranks, then it does not, and the change can take weeks to surface in analytics.

CMS theme updates, plugin changes, and robots configuration in page-builder tools are frequent culprits.

How we check it

We read the <meta name="robots"> tag from the rendered page and check for noindex in its content value. We also check the HTTP X-Robots-Tag response header.

If noindex status changes — from absent to present, or vice versa — we flag it. Because this is a binary field, a single change warrants investigation.

What to watch for

If noindex appears on a page that should be indexed, check your CMS settings, any SEO plugins, and whether a recent deployment brought in environment-specific configuration.

A noindex change that corresponds with a theme update or CMS migration is a known risk pattern. Check Canonical URL and HTTP Status Code at the same time — they are often affected by the same deployment.