X-Robots-Tag noindex Fix Guide

Problem

Pages that should be indexable are blocked by X-Robots-Tag: noindex.

Symptoms

• HTTP Check shows X-Robots-Tag with noindex.
• Pages render normally but do not appear in search results.
• Only some routes or response types are affected.

Top 3 Causes

1. Header injection at the web server or CDN layer - Edge or server rules add noindex.
2. Application logic leaks from preview/staging - A non-production indexing rule remains active in production.
3. Route-specific policy - Certain paths, file types, or status code responses get a different indexing policy.

Diagnose with DechoNet

• HTTP Check to inspect the real response headers and final request path.

Resolution Checklist

• Identify whether the header is injected by the web server, CDN, or application.
• Review whether preview or staging noindex logic leaked into production.
• Check route-level rewrites and header policies for selective noindex behavior.
• Re-run HTTP Check and confirm X-Robots-Tag no longer contains noindex.
• Allow time for search engines to recrawl the page after the fix.

When to Escalate

• Escalate across teams if multiple layers can inject response headers.
• Coordinate with SEO or content owners before changing indexing policy on production pages.