Free · Server-side scan
URL Indexability & Canonical Inspector
Paste one URL. We fetch it safely, check robots.txt, meta robots, X-Robots-Tag, rel=canonical, and hreflang for a browser or bot profile, and explain every blocker, conflict, and canonical problem — without ever claiming an engine will index or rank it.
At a glance
- Trace the redirect chain, final status, and the robots.txt rule that matches your path.
- Read meta robots, X-Robots-Tag, canonical, and hreflang for browser, Googlebot, or Bingbot.
- Get a plain-language verdict with the exact observed signal and a practical fix for each finding.
What this means
Signals guide crawlers — they never guarantee indexing
robots.txt, meta robots, X-Robots-Tag, rel=canonical, and hreflang tell crawlers what they may fetch, which URL to treat as canonical, and where the language equivalents live. This inspector reads those signals from the raw response and reports what they say. Only the search engine decides what it actually crawls, indexes, ranks, or selects.
What do the browser, Googlebot, and Bingbot profiles change?
The profile sets the User-Agent and which rules apply. Googlebot matches Googlebot robots.txt groups and its meta name="robots" plus googlebot-scoped X-Robots-Tag directives; Bingbot matches Bingbot/MSNBot rules and directives; a browser only matches wildcard robots groups. All three read the same rel="canonical" and hreflang tags.
What do indexable, blocked, conflicting, and unknown mean?
Indexable means no observed signal stops this URL. Blocked means robots.txt or a noindex directive explicitly prevents it. Conflicting means signals contradict each other — for example robots.txt blocks the page so the crawler can never see its meta name="robots" noindex, or a rel="canonical" points at a URL that is itself noindex. Unknown means a signal could not be confirmed, such as an unreadable robots.txt.
Does this tell me if Google has indexed the page?
No. It only reads signals from the page and robots.txt — what an engine could see if it crawled. For engine-authoritative index status, use Google Search Console and Bing Webmaster Tools URL Inspection, which this report links to.
Does it render JavaScript?
No. It inspects the raw HTML response only. Canonical, robots, or hreflang tags injected by client-side JavaScript are not evaluated, and the report says so.
Are checked URLs stored?
No. The server fetches your URL, its robots.txt, and at most one canonical target in memory because browser CORS rules block direct checks. Requests run through private-network, DNS, timeout, redirect, and response-size protections, and nothing you submit is saved or embedded in share links.