TECHNICAL SEO DIAGNOSTICS
URL Indexability Checker
Review HTTP status, robots.txt, meta robots, X-Robots-Tag and canonical signals together for a technical SEO diagnosis.
Detailed findings
This report evaluates technical signals returned by the URL. It cannot guarantee indexing. If robots.txt blocks crawling, a crawler may be unable to see a page-level noindex directive.
What is URL indexability?
URL indexability describes whether technical signals allow a search engine to crawl a page, understand its indexing directives and consider it for inclusion in search results. No single status code or tag can guarantee indexing, but a combined check helps surface common configuration issues.
Signals checked together
The checker reviews the HTTP response and final URL, robots.txt rules for Bingbot, HTML meta robots directives, the X-Robots-Tag response header, and the canonical URL and target status. It combines these findings into a practical summary and lists the reasons that may need attention.
Crawlability is not the same as indexability
A robots.txt rule controls whether a crawler may fetch a URL; it is not a reliable way to remove a URL from search results. If a page is blocked, the crawler may not be able to read a meta robots or X-Robots-Tag noindex directive on that page. For this reason, a blocked URL is reported as a crawl restriction, and the checker explains this limitation instead of treating robots.txt as equivalent to noindex.
How to read the assessment
No blocking signals found means this check did not identify the main technical blockers in the response. Review recommended means some signals are missing, uncertain or need context. Not indexable signals found means the report detected a likely technical blocker such as a non-success HTTP response or a noindex directive. These are diagnostic labels, not a prediction of a search engine's final decision.
Use the results to investigate
Check that the final URL is the intended destination, that robots.txt allows the selected crawler when crawling is desired, and that no unintended noindex directive is present in HTML or HTTP headers. Review canonical targets for redirects or errors. A page can still remain unindexed for other reasons, including quality, duplication, relevance and search-engine processing.
Privacy and request behavior
The checker requests the public URL you submit and the relevant robots.txt and canonical targets needed for the report. Requests are limited by timeouts, response-size limits and public-address validation. Do not submit URLs that contain credentials or private information.
Read indexability as a set of signals
Indexability is not determined by one status code alone. Search engines may consider whether a page can be crawled, whether indexing is allowed, which canonical URL is declared, and whether the content is useful and eligible for results. Treat this checker as a technical diagnosis: fix clear conflicts, then verify the live page and monitor how search engines process it.