01 · Response
Does the URL return a usable response?
Review failures and redirect stops before interpreting the page’s declarations.
Separate the signals
Before you ask why it is missing, check what it allows.
A page can load for you and still declare that it should stay out of search. Check crawl access, indexing directives and canonical signals without reducing them to a misleading SEO score.
Check a page
Indexability Checker
Bring one URL. Get a clearer next step.
The check reviews HTTP responses, robots.txt rules for Googlebot, indexing directives and canonical declarations. It does not look up whether Google has indexed the page.
02 / Understand the result
Your indexability report
Enter a public URL to check its indexing signals.
Plain-text report
Use Search Console separately to check Google’s actual indexing status.
Understand the report
Four checks. Different questions.
These signals answer different questions. Treat them as a diagnostic sequence, not four boxes that guarantee a search listing.
02 · Crawl access
Can Googlebot fetch this path?
robots.txt controls crawling. Blocking a path does not by itself guarantee its removal from search.
03 · Indexing directives
Does the response ask to stay out?
Review applicable robots meta and X-Robots-Tag directives. A nofollow instruction alone is not a noindex instruction.
04 · Canonical
Does it nominate a different version?
A different canonical prompts review; it is not the same thing as a crawl block or a noindex directive.
From finding to action
Match the next action to the finding.
Expand the situation closest to your report. These are examples of how to investigate, not automatic instructions to remove every restriction.
The page declares noindex
Check whether exclusion is intentional.
For a public service page, inspect the SEO setting, template and X-Robots-Tag header. For a private or utility page, keeping it out of search may be correct.
robots.txt blocks crawling
Crawl access and indexing are different.
Google may not be able to see a page-level noindex when crawling is blocked. Decide the intended outcome before changing either rule.
No obvious blocks detected
Move from access checks to search evidence.
Review URL Inspection in Search Console, the selected canonical and how the page is linked internally. A clear report cannot establish that Google has crawled or indexed it.
If a check is incomplete, resolve that uncertainty first. A timeout, access challenge or unreadable response is not a clean result.
Before you move on
Keep the evidence with the decision.
Save the exact URL and report
Include the checked variant, any redirect destination and which checks were incomplete.
Confirm the intended behaviour
Some URLs should stay out of search. Review the page’s purpose before changing a restriction.
Recheck, then use Search Console
Retest the response after a fix. Search Console supplies the separate evidence about Google’s crawling and indexing.
Your questions
Know what the check can tell you.
Does a clear result mean the page is indexed?
No. “No obvious indexing blocks detected” describes the signals checked in this response. It is not confirmation of inclusion, ranking or traffic.
Which crawler is this report about?
The verdict is scoped to Googlebot web search. Other crawler-specific declarations may be shown for context, but do not automatically apply to that verdict.
What can this check miss?
It does not render JavaScript, detect every soft 404 or inspect Google’s cached robots rules. Responses can also differ by user agent, location or authentication. Use it alongside a browser check and Search Console.
Need help getting from a finding to a fix?
Share the page, the report and whether it should appear in search. We can help separate intentional restrictions from technical problems.
Send an enquiry