Check the barriers in one pass.
HTTP status, redirects, Googlebot's robots.txt rule, page and header noindex directives, canonical and HTML response.
- Matched robots.txt line
- Canonical destination shown
Enter any page URL to check the status, redirects, Googlebot access, noindex directives, canonical and page type that decide whether Google can index it.
Free, no account needed. MrKeyword fetches the page live and shows only what it found.
Built on first-party data from Google and Bing
A page is crawlable when Googlebot can fetch it, and indexable when Google can include it in Search. Crawlability is one requirement: a page that answers successfully can still tell Google not to index it, or point its canonical at a different URL.
Five things commonly block or complicate indexing: an HTTP error, a long or temporary redirect chain, a robots.txt rule that blocks Googlebot, a noindex meta tag or X-Robots-Tag header, and a canonical that names another page. Google also needs an HTML page to read its content and page-level directives.
An “indexable” result means this check found no direct technical block; it does not mean Google has indexed the URL. For that, use Search Console URL Inspection, which reports Google's own last crawl and indexing decision.
HTTP status, redirects, Googlebot's robots.txt rule, page and header noindex directives, canonical and HTML response.
Use MrKeyword's site audit to crawl your site, find indexability problems across pages and see which URLs need attention.
The fictional northwind-plumbing.example serves a normal service page with a self canonical and no indexing blocks. The checker reads the page and its robots.txt:
| Check | Status | Detail |
|---|---|---|
| HTTP status | pass | Final page returned HTTP 200. |
| Redirects | pass | 0 redirect hops; all permanent. |
| robots.txt | pass | Googlebot is allowed (no matching rule). |
| HTML page | pass | The response is HTML. |
| Meta robots | pass | No noindex directive in meta robots or Googlebot tags. |
| X-Robots-Tag | pass | No noindex directive in X-Robots-Tag. |
| Canonical | pass | Canonical points to this page. |
Example result for a fictional website (northwind-plumbing.example). It is produced by the checker's own code from the setup described above; run the checker for your own pages.
The page returns HTTP 200, has no redirect, allows Googlebot in robots.txt, has no noindex directive and points its canonical at itself. This means the page can be indexed; it cannot promise that Google will choose to index it. Use Search Console URL Inspection for Google's own decision. For further reading, see the on-page SEO checklist, test robots.txt, inspect redirects or preview the SERP snippet.
Remove noindex from the meta tag and X-Robots-Tag header, then let Google recrawl.
Allow Googlebot to fetch it so it can read the content and indexing directives.
Keep it only when the other URL is the preferred duplicate; otherwise use a self canonical.
Check a URL when launching a page, after a migration, or when Search Console says Google has not indexed it.
No. A robots.txt Disallow stops Googlebot fetching the page, so it cannot see a noindex tag. Allow crawling and use a meta robots or X-Robots-Tag noindex directive to keep a page out of Search.
Google fetched the page but chose not to add it to its index yet. It is not necessarily an error; review whether the page is useful and distinct, then use URL Inspection to request indexing after improvements.
Google treats that as a signal that the other URL is the preferred version. If the pages are duplicates, that may be intentional; otherwise make the canonical self-referencing and align internal links and sitemap.
There is no fixed time or guarantee. Google may take days or longer to recrawl a URL, and requesting indexing in Search Console does not guarantee inclusion.
This checker tests one URL. MrKeyword's site audit crawls your site and flags indexability issues across its pages.