What this tool checks

The Indexability Inspector performs a bounded public fetch and reports the signals a crawler can observe without executing JavaScript or accessing a private Search Console account.

It checks:

The requested URL and final URL
HTTP status
Redirect count
Content type
Whether robots.txt appears to allow the final URL for Googlebot
Robots meta directives
Googlebot-specific meta directives
X-Robots-Tag response headers
HTML and HTTP canonical annotations
Multiple or conflicting canonical declarations
Title and primary heading presence
Approximate visible text availability in the returned HTML
Obvious status, directive, and canonical conflicts

The result is an inspection report, not an indexing guarantee.

Google's minimum technical requirements include crawl access, a working 200 response, and indexable content. Meeting those requirements makes a page eligible for consideration; it does not require Google to index or rank the page.

Report summary labels

Potentially indexable

The inspected response does not show an obvious crawl block, noindex directive, or non-success status. This means the page appears technically eligible under the signals this tool can observe. It does not prove that Google has indexed the URL.

Indexing prohibited

The final response contains a noindex rule in HTML or an X-Robots-Tag header. A crawler that can access the page may use that rule to keep the resource out of search results.

Crawling blocked

The robots.txt evaluation indicates that Googlebot is disallowed from fetching the final URL. Because the crawler cannot reliably read the page, this tool cannot treat page-level noindex or canonical signals as fully observable to Google.

Unavailable or error response

The final URL did not return a normal successful HTML response. Review the status, redirect chain, access controls, and server behavior before evaluating page-level indexing signals.

Redirecting URL

The requested URL redirects. Search systems normally process the destination rather than indexing the redirecting response as a standalone content page. Review the final URL and the full chain.

Indeterminate

The response could not be classified reliably within the tool's bounded fetch and parsing limits. Review the detailed fields and test the URL with an owner-authorized search-engine inspection tool.

Result fields

Field	Help text
Requested URL	The exact URL submitted to the tool.
Final URL	The URL reached after HTTP redirects.
HTTP status	The final response status returned to this inspector.
Redirects	The number of HTTP redirect hops followed.
Content type	The response media type declared by the server.
Robots.txt	The matching allow or disallow result for Googlebot, with the rule shown when available.
Robots meta	Directives found in `<meta name="robots">`.
Googlebot meta	Directives found in `<meta name="googlebot">`.
X-Robots-Tag	Indexing and serving directives found in response headers.
HTML canonical	Canonical URL declarations found in HTML.
HTTP canonical	Canonical URL declarations found in `Link` response headers.
Title	The returned HTML document title.
H1 count	The number of primary headings found in the bounded HTML sample.
Text sample	Whether the returned HTML contains meaningful text after basic markup removal.
Warnings	Conflicts or conditions requiring manual review.

How to interpret the report

Start with the final response

A page cannot be evaluated as an ordinary indexable HTML document when the final response is a redirect, authentication challenge, client error, server error, or empty success response.

Use the final URL rather than assuming the submitted form is canonical.

Separate crawl control from index control

Robots.txt controls crawler access. It is not a dependable way to keep a public web page out of search results.

A noindex rule is different. It can be delivered in HTML or with X-Robots-Tag, but the crawler must be allowed to access the resource to observe it.

The inspector therefore warns when a page is simultaneously blocked by robots.txt and declares noindex. That combination can hide the removal instruction from the crawler expected to obey it.

Read every directive source

A clean HTML template does not prove that the public response is indexable.

A directive can come from robots meta tags, Googlebot-specific meta tags, X-Robots-Tag, application middleware, web server configuration, or a reverse proxy or CDN. When several directive sources exist, restrictive rules can combine.

Treat canonical annotations as preferences

The inspector reports declared canonical signals. It cannot report Google's selected canonical because that decision is made during indexing and requires owner-authorized indexed data.

Warnings appear when more than one HTML canonical is present, HTML and HTTP canonicals disagree, the canonical resolves to the same redirecting URL, the canonical uses a different protocol or hostname, or the canonical is malformed or cannot be resolved.

A declared canonical is a preference, not proof that a search engine selected it.

Remember the JavaScript boundary

This tool does not execute page JavaScript.

It can inspect the returned HTML, but it cannot confirm whether client-rendered content, metadata, links, or error states appear after hydration. Use URL Inspection or another renderer when the main content depends on JavaScript.

What this tool cannot tell you

The Indexability Inspector cannot determine:

Whether Google has indexed the page
Google's selected canonical
Whether the page ranks for a query
Whether a manual action, security issue, or removal request applies
What a fully rendered browser DOM contains
Whether content quality is sufficient for index selection
Whether search engines other than Google interpret every rule identically
Whether a private, cookie-dependent, or logged-in experience works

For a URL in a Search Console property you control, compare this report with the indexed and live information in URL Inspection.

Safe use and privacy

The tool accepts only bounded public HTTP and HTTPS URLs. It rejects credentials, private-network destinations, loopback addresses, link-local addresses, cloud metadata targets, unsupported ports, oversized responses, and excessive redirect chains.

It does not submit forms, send cookies, reuse visitor credentials, or intentionally retain submitted URLs.

DNS prevalidation reduces but cannot eliminate the risk inherent in arbitrary public fetching. Every redirect target is checked again, Cloudflare platform protections remain in force, and strict response, time, and byte limits bound each request.

Indexability Inspector

Inspect one public URL