No page is marked noindex. noindex is usually a leftover: a staging flag that shipped, a plugin setting, an SEO plugin's "discourage search engines" box.
The check reads each priority page's HTML for <meta name="robots" content="noindex"> and the response headers for X-Robots-Tag: noindex. Either one excludes the page from search indexes — and from the material retrieval systems draw on.
noindex is usually a leftover: a staging flag that shipped, a plugin setting, an SEO plugin's "discourage search engines" box. On a priority page it quietly removes the page from Google and from the indexes AI search engines retrieve from.
View the page source and search for "noindex"; check the response headers for X-Robots-Tag. On WordPress, Settings → Reading → "Discourage search engines" sets it for the whole site.
What the agent does: the agent never flips noindex on its own — it names the page and the exact tag or setting, and you decide.
Part of the 23 checks · group: Crawler access — robots.txt, CDN/bot filter, login walls, noindex, HTTP status, sitemap, canonical.
No. robots.txt stops the fetch; noindex lets the fetch happen and asks the engine not to index the result. Both remove the page from what AI retrieves.
Because noindex is sometimes intentional. A switch that could expose a page you meant to hide is not a switch worth having; the agent proposes, you decide.
The page check reads your public pages from outside and runs all 22 — free, no signup, no AI engine involved.