Understand a page missing from Google
Check that no noindex is hiding in the template, an SEO plugin or the server header.
Analyze local indexability directives in HTML and an optional X-Robots-Tag without network requests.
This analyser tells you whether a page can be indexed based on its HTML code and, if you provide it, its X-Robots-Tag HTTP header. It combines the directives of the robots and googlebot meta tags, compares the canonical with the page URL and lists the reasons for any block, without contacting the site.
The tool reads the <meta name="robots"> tag, the <meta name="googlebot"> tag and the X-Robots-Tag value you enter, then merges them: the most restrictive directive wins, as it does at Google.
If noindex appears in any of these sources, the page is reported as not indexable and the reason is added to the report. nofollow sets followLinks to false.
The canonical is resolved against the page URL, so a relative canonical such as /shoes/women becomes a full address. If it differs from the URL entered, a warning says so.
The report adds warnings for a missing canonical, title or meta description, and states its limit: neither robots.txt nor the live HTTP status is checked.
At least the page’s <head> section, in the HTML code field.
It is used to resolve and compare the canonical.
Optional: copy its value from the Network tab of the browser developer tools.
Read indexable, followLinks, reasons and warnings in the indexability report.
Check that no noindex is hiding in the template, an SEO plugin or the server header.
Make sure a URL with sorting parameters canonicalises to the main page.
Confirm that a staging site is set to noindex before making it reachable.
The page sorted by price is set to noindex and its canonical points to the version without parameters: it will not be indexed, but its links are still followed. The report gives the reason (noindex) and two warnings: canonical different from the URL entered and missing meta description.
Input
HTML code: <head><title>Chaussures femme</title><meta name="robots" content="noindex, follow"><link rel="canonical" href="/chaussures/femme"></head>
Page URL: https://example.com/chaussures/femme?tri=prixResult
"indexable": false, "followLinks": true, "canonical": "https://example.com/chaussures/femme", "canonicalMatches": false,
"robots": { "meta": "noindex, follow", "googlebot": null, "xRobotsTag": null }The HTML has no directive, but the X-Robots-Tag header alone excludes the page and stops its links from being followed. This is a common method for PDFs and private documents.
Input
HTML code: <head><title>Facture 2026-114</title><meta name="description" content="…"><link rel="canonical" href="https://example.com/factures/2026-114"></head>
Page URL: https://example.com/factures/2026-114
X-Robots-Tag: noindex, nofollowResult
"indexable": false, "followLinks": false, "canonicalMatches": true,
"robots": { "meta": null, "googlebot": null, "xRobotsTag": "noindex, nofollow" }The meta robots tag sits in the HTML; the X-Robots-Tag header is sent by the server with the HTTP response. They accept the same directives, but the header also works for non-HTML files such as PDFs and images.
It downloads nothing: it only analyses the HTML and header you provide. To test a robots.txt rule, use the robots.txt report in Search Console or our robots.txt generator.
No, it is a hint, not a directive. Google often picks the declared canonical but can choose another URL. The tool therefore reports it as a warning, not as a blocking reason.
For Google, the two add up and the most restrictive directive applies. The tool does the same: a noindex in either makes the page non-indexable.
No. The analysis runs in your browser.
Related tools
Tools similar or complementary to this one.
Analyze key SEO signals in HTML locally.
Create a clear robots.txt file to guide web crawlers.
Create an XML sitemap from a list of URLs.
Learn how title, description, canonical and social metadata work together and avoid common technical SEO mistakes.
A practical workflow to review SEO changes before publishing: sitemap, link relationships, redirects, keyword usage and structured data.
Check metadata, canonical, robots, structured data, URL, internal links and images before a page goes live.
Resize a batch of images, convert them to WebP and remove metadata with one reusable Pipeline.