JavaScript injects a noindex directive

What this means

The server's HTML carries no noindex, but after JavaScript executes the page declares one. Google honours the rendered directive, so this page will silently drop out of the index while looking perfectly indexable to any tool that reads only the raw response.

How to fix it

Remove the client-side noindex injection. If a page genuinely must not be indexed, serve the directive in the initial HTML or as an X-Robots-Tag response header so the decision is visible before rendering.

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