Check indexability.
Check technical signals that may prevent Google indexing.
What instructions does your page give Google?
A page can be reachable in a browser while sending noindex. This check reads the technical signals in the response and shows what deserves a closer look.
Use for freeCrawling and indexing are different things.
A noindex directive tells search engines not to include a page in the index. A robots.txt rule blocks requests to certain paths. A known address may still appear in the index as a URL; blocking crawling therefore does not replace noindex.
A canonical is a separate signal: the page identifies a preferred address for the same or very similar content. After a relaunch, check whether it still points to an old domain, a test environment or an unsuitable product variant.
The tool examines the public HTTP response without executing JavaScript. Content or metadata added by a script is outside this check. To see the actual Google index status, use URL Inspection in your Search Console.
Keep these signals separate
HTML: <meta name="robots" content="noindex">
Header: X-Robots-Tag: noindex
Diese Angaben können unabhängig voneinander gesetzt sein.| Signal | Was es aussagt | Typische Kontrolle |
|---|---|---|
| noindex | The page should not be indexed. | Is this instruction intentional on a public service page? |
| robots.txt: Disallow | Der angegebene Pfad soll nicht gecrawlt werden. | Was this block carried over from a test environment? |
| Canonical | Eine andere Adresse wird als bevorzugte Fassung benannt. | Does the destination exist and is its content relevant? |
| HTTP-Fehler | The page was not delivered successfully. | Is the error permanent or temporary? |
A technical snapshot, not proof or a promise of Google indexing. A free account is required to request the page.
Open Indexability checker