Indexability Checker: Can Google Index This Page?
Check if a page can be indexed: status, robots.txt, noindex, X-Robots-Tag and canonical. Does not show if Google indexed it. One URL, two fetches.
- Paste one page URL
- Run the indexability check
- Read verdict, conflicts, and fixes
- Browser-based — no install
- Instant results
Paste one URL to check if a page can be indexed from server signals: HTTP status, robots.txt, noindex, X-Robots-Tag, and canonical. Two fetches, one origin. Answers can it be indexed — not whether Google already indexed it. Pair with the Google Index Checker or URL Inspection.
By Faisal YUpdated
Search Console says "Excluded by noindex" but the live page looks fine in your browser. Or the URL ranks nowhere and you are not sure whether the problem is crawl, index, or content. Indexability is whether a page can be indexed from technical signals. Indexed is whether Google chose to keep it. Crawlable is whether Googlebot is allowed to fetch it. Three different questions. This guide walks the order a crawler meets signals, the robots.txt versus noindex trap, canonical mistakes, and how to combine URL Inspection with the Indexability Checker . The checker answers can it be indexed from two server fetches. It does not replace the Google Index Checker or the Page indexing report for what Google already did. ! Three steps: fetch page and robots.txt, read indexing signals, output verdict conflicts and fixes Crawlability vs indexability vs indexed Crawlability is governed first by HTTP reachability and robots.txt . If Googlebot is disallowed for the path, it may never download HTML to read meta tags. Indexability adds on-page and header directives: noindex , none , X-Robots-Tag , and status codes like 404/410. A page can be crawlable but carry noindex . Indexed is Google's decision after crawl. Quality, duplication, and manual actions still matter. A clean indexability report is necessary but not sufficient. Signals in crawl order 1. Status and redirects Check the first response and the final URL after redirects. Longer redirect chains can add hops before Google sees the final URL. Final 404/410 tells crawlers the URL is gone. 401/403/429 may be WAF or login walls; automated checks may differ from Googlebot. Illustrative check: 2. robots.txt on the origin Fetch https://your-host/robots.txt and see whether Googlebot (or * if no Googlebot group) allows the path. Google's robots.txt intro explains that disallow blocks crawling, not necessarily every appearance in…
Read the full guideWhat this checker does
The Indexability Checker fetches **two URLs**: the page you paste and **`/robots.txt` on the input origin** (not a third fetch for a cross-origin redirect target). It reports HTTP status and redirects, whether Googlebot and `*` groups in robots.txt allow the path, `meta robots` / `meta googlebot`, the `X-Robots-Tag` response header, `rel=canonical`, and lightweight `hreflang` / alternate hints. Verdicts are **indexable (likely)**, **blocked from indexing**, or **mixed signals** — always worded as likely or appears, never confirmed indexing.
Use it as a **noindex checker** or to **check if a page is indexable** before you waste time on content tweaks. It checks **one page at a time**; a site-wide answer needs a crawl or tools like the [Bulk Meta Robots Checker](/tools/bulk-meta-robots-checker).
How to read each signal
**Status and redirects** — Final 404/410 usually means the URL should drop from results. 401/403/429/5xx may be bot protection or server errors; Google might see something different. Redirect chains longer than one hop are flagged.
**robots.txt** — Crawling blocked here means Googlebot may not fetch the page to read HTML directives. A disallow alone can still leave a URL in results without content if other sites link to it ([Google robots.txt intro](https://developers.google.com/search/docs/crawling-indexing/robots/intro)).
**Meta robots and X-Robots-Tag** — `noindex` or `none` in either place blocks indexing when Googlebot can crawl and see them ([block indexing](https://developers.google.com/search/docs/crawling-indexing/block-indexing)). Headers matter for PDFs and other non-HTML files.
**Canonical** — A hint, not a hard directive. A canonical to another URL suggests consolidation; conflicting canonicals are warnings.
**Hreflang** — Informational only; missing self-reference is noted but does not by itself block indexing.
Verdicts and conflicts
**Blocked** — Effective noindex/none while crawlable, and/or robots.txt blocks with no contradicting on-page signals, and/or final 404/410.
**Mixed** — robots.txt disallows **and** noindex on the page (Google likely cannot see the noindex), canonical elsewhere, uncertain robots.txt, or conflicting meta vs header directives.
**Indexable (likely)** — 2xx HTML, crawl allowed, no effective noindex, canonical self or missing.
What this tool cannot do
- It **cannot** see Google's index or Search Console decisions — use [URL Inspection](https://support.google.com/webmasters/answer/9012289) or the [Google Index Checker](/tools/google-index-checker) for whether a URL appears indexed. - **No JavaScript rendering** — tags injected only client-side are missed. - **Googlebot and `*` only** in robots.txt; not other bots. - **One URL**, not a site audit; WAFs may answer our fetch differently from Googlebot. - **robots.txt of a cross-origin redirect target** is not checked (only the input origin).
How this differs from other Scrawl tools
- **[Google Index Checker](/tools/google-index-checker)** — Focuses on whether a URL appears indexed; this tool reads live server signals for **can it be indexed**. - **[Bulk Meta Robots Checker](/tools/bulk-meta-robots-checker)** — Many URLs, meta/header directives only. - **[Canonical Checker](/tools/canonical-checker)** — Canonical tag focus; here it is one signal among several. - **[HTTP Header Checker](/tools/http-header-checker)** — Raw headers; here `X-Robots-Tag` is interpreted for indexing. - **[Robots.txt Tester](/tools/robots-txt-tester)** / **[Robots.txt Generator](/tools/robots-txt-generator)** — Test arbitrary paths and user-agents; here Googlebot + `*` for this URL only. - **[Soft 404 Checker](/tools/soft-404-checker)** — Missing-URL behaviour; pair when status and content disagree.
Frequently Asked Questions
What does indexable mean?
Indexable means a crawler that can reach the page would not see blocking signals such as noindex, a robots.txt disallow for its path, or a final 404/410. This tool is a noindex checker on one URL: it reports those signals from two fetches. It does not guarantee Google will index the page.
What requests does this tool make?
Exactly two: your page URL and /robots.txt on the same origin as the normalized input URL. Both pass SSRF-safe validation. No sitemaps, no extra paths, no Google APIs.
Does it tell me whether Google indexed my page?
No. It only reports what your server returned. For index status use Search Console URL Inspection or the Google Index Checker on Scrawl.
Why can robots.txt block hide a noindex?
If robots.txt disallows crawling, Googlebot may never fetch the HTML to read a noindex meta tag. Allow crawling and keep noindex, or use another removal route. The tool flags that conflict as mixed signals.
Can it check my whole website?
No. Paste one URL at a time. For many URLs use the Bulk Meta Robots Checker or a crawler. To test robots rules for arbitrary paths use the Robots.txt Tester.
What are the limits?
One URL per run, two HTTP requests, HTML and robots.txt size caps, standard rate limits, no JavaScript execution, and private or localhost URLs blocked.
Related tools
Google Index Checker
Technical SEOCheck if any URL is indexed by Google instantly. Find why pages are not indexed…
Noindex Checker
Technical SEOCheck meta robots and X-Robots-Tag headers across multiple URLs at once. Find no…
Canonical Checker — Find Missing & Wrong Tags
On-Page SEOVerify rel=canonical tags to resolve duplicate content issues and consolidate ra…
HTTP Header Checker
Utility ToolsInspect raw server response headers to verify caching policies, security headers…