Three different things can keep a page out of search, and two of them are invisible in a browser: a robots meta tag, an X-Robots-Tag response header, and a robots.txt rule. This reads all three.
We read the page, its response headers and your robots.txt, and evaluate the rules the way engines do: most specific group, longest matching path, Allow wins a tie.
Reading the page, its headers and your robots.txt…
Nothing to fix here — this part of the page is in order.
A single line in the head: <meta name="robots" content="noindex">. It is the usual culprit, it survives redesigns, and it is often left over from a staging site that went live.
The same instruction sent as a response header instead of a tag. Nothing on the page shows it, so you can read the HTML all day and never find it — it is set by the host, a CDN rule or the server configuration.
A disallowed path is not a noindex: the page can still appear in search, with no content behind it, because the crawler was never allowed to read it. We evaluate your robots.txt with the same precedence engines use and name the rule that matched.
A checkout, an account page or a thank-you page should be out of the index. What this tool is for is the page you expected to find and cannot.
This is check 0.5 — No page is marked noindex and check 0.1 — robots.txt allows AI crawlers, run on one page instead of all of them. All 35+ checks are what the agent reads on a site it is installed on, and most of them it can also fix.
On your site, by the agent: what Reflexa Agent does · pricing · install the agent
All of them on one page: free tools.
If this tool says nothing blocks it, the page is indexable and the reason is elsewhere: it is too new, nothing links to it, it is not in the sitemap, or it is a duplicate whose canonical names another URL. If it does find a block, that is the whole answer.
Noindex says "read this but keep it out of the index". A robots.txt disallow says "do not read it at all" — and a page nobody may read can still be listed from its links alone, which is why the two are not interchangeable.
From the server, not the page: a host rule, a CDN configuration, a framework setting, a .htaccess line. It is the hardest of the three to find by hand and the reason this tool reads headers.
Yes — lifting a noindex is one of the fields the agent writes. It shows you the page and the change, and applies it on your click; an X-Robots-Tag set by the host is named with the exact place to change it.
The free page check reads your public pages from outside and reports what is keeping each one out — and the agent lifts what it can on your click.