Fetches a page from our server and tells you whether Google can index it: the status code, the redirect chain, noindex in the page and in the headers, the canonical address, whether robots.txt blocks it, and whether it appears in your sitemap. For founders and marketers whose page does not show up in search.
How to use it
Enter the address of the page that does not appear in search. You can leave out https://.
- Type or paste the address of the page and press Run check.
- Read the signals summary: robots.txt, noindex, canonical and sitemap.
- Start with the critical findings. Each one names the signal that stops the page and how to fix it.
- Change the page or its headers, then run the check again.
How Reavlo tests this
This tool runs on our server, because a browser cannot read another site's page, headers or robots.txt. Nothing about the request is stored or logged: not the address, not the page.
Fetching. One request to the page, with up to 3 redirects, a size cap and a time limit, then one request to /robots.txt on the same host and up to 5 sitemap files. Addresses that point to private or internal networks are refused before any connection is made, and every request follows the same rules. The chain of redirects is shown.
Status and redirects. A status of 400 or higher is critical, because a page that answers with an error is not indexed. A chain of more than 2 redirects is a warning.
Noindex. The robots and googlebot meta tags and the X-Robots-Tag header are read as Google documents them. noindex and none stop indexing. A header value that names another crawler is ignored.
robots.txt. The file is read as RFC 9309 defines it and the page path is matched for Googlebot, with the longest matching rule deciding. A missing file (a 4xx answer) means nothing is blocked. A file that cannot be reached is reported as unreachable and is not treated as a block.
Canonical. The rel=canonical address is resolved against the final address. A canonical that points to a different page tells Google to index that page instead.
Sitemap. The sitemaps named in robots.txt are read, or /sitemap.xml when there are none, following a sitemap index up to 5 files and 50,000 entries. If the caps are reached before the page is found, the answer is reported as unknown, not as "not listed". Compressed (.gz) sitemaps are not read.
Limits. The tool shows signals that block indexing. It does not tell you that a page is indexed, which only Google can say, and it does not run JavaScript: a page that sets noindex or a canonical with JavaScript is read as the server sent it. A page that is allowed can still be left out of the index for quality reasons.
Questions
Is the address I enter stored?
No. The address goes to our server only to fetch the page, and neither it nor the page is stored or written to a log. Analytics records only that the tool ran, never the address.
Why is my page not in Google if the tool finds no problem?
The tool checks the signals that block indexing. A page can pass them all and still be waiting to be crawled, be treated as a duplicate, or be judged not useful enough. Google Search Console's URL Inspection shows what Google itself decided.
What is the difference between robots.txt and noindex?
Robots.txt tells a crawler not to fetch a page; noindex tells it not to keep the page in the index. If robots.txt blocks a page, the crawler never sees a noindex on it, and the address can still appear in results without a description.
Does a canonical to another page remove my page from search?
It asks Google to index the other page instead. Google treats a canonical as a strong hint, not a command, but a page that points elsewhere is usually left out.
Does a missing sitemap stop indexing?
No. A sitemap helps Google find pages but is not required, so a page missing from it is reported as information only.