Indexability checker
Read the final response the way a crawler receives it: status, redirects, HTML directives, response headers, and canonical in one check.
Public check, no account needed. Reads meta robots, the X-Robots-Tag header, canonical and the redirect chain. Rate limited to 60 an hour per IP.
Illustrative result for a reserved example URL. Your check replaces it.
Blocked from indexing
meta robots noindex
- HTTP status
- 200
- Canonical
- https://example.com/pricing
- Meta robots
- noindex, nofollow
- Googlebot meta
- not found
- X-Robots-Tag header
- not found
- Title
- Pricing plans | Example
What this check means
- Indexability
- Indexability is whether a search engine is allowed and able to include a URL in its index.
- Meta robots
- A meta robots tag is an HTML instruction that tells crawlers whether they may index a page or follow its links.
- X-Robots-Tag
- An X-Robots-Tag is an HTTP response header that applies crawler directives before the HTML is parsed.
How to read the result
- Verdict
- Blocked means the response failed or at least one returned directive contains noindex or none.
- HTTP status
- A final 4xx or 5xx response means the requested page did not return usable content, even if its directives look clean.
- Final URL and chain
- These show where the request ended and every redirect response used to get there. An unexpected destination can expose a routing or deployment mistake.
- Meta robots and Googlebot meta
- Any noindex value blocks the page for the matching crawler. A Googlebot-specific value can override the general robots value for Google.
- X-Robots-Tag header
- This lists directives by user agent. A noindex here can block the page while view-source still looks clean.
- Canonical
- A canonical pointing away from the final URL asks search engines to consolidate signals onto another URL and deserves an intent check.
- Title
- The title provides page context beside the indexability signals. A missing title does not create noindex, but it is still a page-quality problem.
Common causes
- A staging noindex setting reached production with a template or environment variable.
- A CMS visibility switch added noindex to a page or an entire content type.
- A proxy, CDN rule, or application middleware added an X-Robots-Tag header.
- A route now redirects to a login page, error page, or unexpected hostname.
- A shared canonical template still points at an older URL pattern.
Can a page be crawlable but not indexable?
Yes. A crawler can fetch a page and still find a noindex directive that prevents the page from appearing in search results. Crawl access and index permission are separate checks.
Which wins, meta robots or X-Robots-Tag?
A restrictive directive in either place can block indexing. A clean meta robots tag does not cancel an X-Robots-Tag noindex header, and the reverse is also true.
Does HTTP 200 mean a page is indexable?
No. HTTP 200 only means the server returned a successful response. The page can still carry noindex, point its canonical elsewhere, or contain other signals that need review.
Will removing noindex make the page appear immediately?
No. Removing noindex makes indexing possible again, but a search engine must recrawl and process the page before its result can change.