Page is noindexed by an X-Robots-Tag header

What this means

The response carries a noindex directive in the X-Robots-Tag HTTP header, so the page will be dropped from the index. Because the directive lives in the response headers and not the HTML, it is invisible when viewing source and is a common accident from a CDN rule, a staging config promoted to production, or a framework default.

How to fix it

Remove the noindex (or none) token from the X-Robots-Tag header for this route at whatever layer sets it — origin app, reverse proxy, or CDN. If the page genuinely should not be indexed, keep the header and remove the page from the sitemap and internal navigation instead.

Fix effort

This check needs a developer fix: it turns on a routing, hosting or infrastructure decision that no automatic edit can make safely.

Authoritative source

https://developers.google.com/search/docs/crawling-indexing/block-indexing