A page that never enters Google's index will not rank. Most "why isn't this ranking" tickets start one layer earlier: the URL is blocked, redirected, canonicalized away, or simply never kept.
This guide is the workflow. How to check if Google indexed a URL, how to read a technical indexability report, what to fix when the page is out, and when to escalate to a readiness pulse or a full technical audit. The matching tool is the Google Index Checker. Run that for the five blocking signals. Use this page for the order of work.
What "indexed" actually means
Crawling is Googlebot fetching the URL. Indexing is Google deciding to keep it and make it eligible for results. Those are different steps. A page can be crawlable and still stay out of the index.
Search Console's Pages report is where Google labels the reasons: excluded by noindex, blocked by robots.txt, alternate page with proper canonical, crawled but not indexed, and the rest. A free browser tool cannot invent those Google-side labels. What it can do is tell you whether your page is sending a signal that blocks indexing before Googlebot even gets a clean look at the page.
That is the job of Scrawl's Google Index Checker. It does not query Google's index. There is no free public API for that. It fetches the URL and reports the technical blockers on the page and in the response.
What the Google Index Checker actually checks
Paste a public URL into the Google Index Checker. No login. Free. No usage limits on the tool page.
The report covers five signals (the same five the live tool documents):
- HTTP status — you want a clean 200 on the URL you care about
- robots.txt — whether a Disallow rule blocks the path for Googlebot
- noindex — meta robots in the HTML and
X-Robots-Tagin the headers (View Source misses the header) - Canonical — whether
rel=canonicalpoints somewhere else - Redirects — whether the URL hops away instead of serving the content
A page that fails any of these is not "ready to be kept." A page that passes all five is indexable. It may still be new, thinly linked, or held out for quality reasons. Indexable is not the same as already indexed.
For the definitive "is this URL in Google right now?" answer, use URL Inspection in Search Console on a property you own. Google's own recrawl documentation is also where you request a crawl of individual URLs after you fix something. The site: operator in Google Search is a quick smell test. It is not reliable for new or recently changed pages, and the live tool page says the same thing.
How to run the check
- Open the Google Index Checker.
- Paste the full production URL — HTTPS, the host you want indexed, not staging.
- Run the check.
- Read each failed signal. Fix those first. Then confirm in Search Console.
Skip basic-auth staging and preview hosts. If the checker cannot fetch what Googlebot sees on production, the report is noise.
How to read the result
Treat the report as a triage board, not a ranking score.
All five pass. The page is technically clear. If Search Console still says it is not indexed, the problem moved into discovery, quality, duplication, or crawl priority. Do not keep hunting for a phantom noindex. Look at internal links, the sitemap, and the Pages report reason.
HTTP status fails. Soft 404s, real 404s, 5xx, or a surprise redirect status. Restore the page, return an honest 404/410 if it should be gone, or put a single permanent redirect to the real destination. Do not dump everything on the homepage.
robots.txt blocks the path. Open https://yourdomain.com/robots.txt and find the Disallow. Confirm with the Robots.txt Tester against the URL you care about. Staging leftovers that ship as Disallow: / are still the classic launch bug.
noindex is present. Google's noindex documentation is blunt: when Googlebot sees the rule, the page is dropped from results. The rule can live in a meta tag:
<meta name="robots" content="noindex">Or in an HTTP header:
X-Robots-Tag: noindexGoogle also notes that robots.txt must not block the URL if you rely on noindex. If Googlebot cannot fetch the page, it never sees the tag, and the URL can still show up from other signals. Remove leftover staging noindex from both the HTML and the CDN headers. Re-check the same URL.
Canonical points elsewhere. Google may keep the other URL instead of yours. Confirm with the Canonical Checker. Self-referencing on unique money pages. Never point at a 404, a redirect, a noindex URL, or a parameter variant you do not want in the index.
Redirects. If you pasted a URL that should be the final page and it hops, fix the chain. Googlebot will follow multiple hops; that is not a reason to ship them. Land on the final URL in one permanent redirect when you can.
When the page is not indexed: fix order
Work the stack top to bottom. Later layers are wasted motion if the earlier ones are broken.
P0 — you are blocking the URL yourself. robots Disallow on a live section. noindex on a money template. Canonical to the wrong host. Non-200 on the live address. Redirect loop. Fix this week. Re-run the checker on the same URL after deploy.
P1 — clear technically, still missing in Search Console. Submit or refresh the XML sitemap with the canonical 200 URLs. Add internal links from pages Google already crawls. In Search Console, open URL Inspection on the money URL and request indexing if you manage the property. Google says crawling after a request can take anywhere from a few days to a few weeks, that inclusion is not guaranteed, and that hammering the same URL with repeat requests does not make it faster. There is a quota.
P2 — "Crawled — currently not indexed" (or similar) with no technical block. That is usually quality, duplication, or asking Google to keep a pile of near-identical filtered URLs. Title rewrites will not save an architecture problem. Escalate to the technical SEO audit checklist.
After any cutover, spot-check the new money URLs the same way. The full sequence lives in the site migration SEO checklist.
Pair the index check with a readiness pulse
The index checker answers: "is something on this URL blocking indexation?"
When the page is clear but still feels weak (missing title, broken schema, soft indexability elsewhere on the template), run the SEO Readiness Score Checker on the same URL. That is a single-URL 0–100 pulse across on-page tags, indexability, structured data, content and links, security headers, and AI signals. It is not a ranking forecast. The companion write-up is the SEO readiness checker guide.
Order that matches how the work depends on itself:
- Google Index Checker for hard blockers
- SEO Readiness Checker for the rest of the URL's pulse
- Technical audit checklist when the whole site is the patient
- Migration checklist when URLs moved
Worked patterns that keep showing up
Staging noindex on a live product. HTTP 200. robots.txt allows the path. Meta robots still says noindex,follow from the theme. That alone explains a drop in Search Console. Remove the tag (and any matching X-Robots-Tag). Re-check. Then request indexing on the money URLs.
Canonical to the category. Product URL returns 200. Canonical points at /category/widgets. Google keeps the category. Fix the template so unique products self-canonicalize. Confirm with the Canonical Checker.
Blocked by robots, "fixed" in the CMS only. Someone toggled "allow search engines" in WordPress while the CDN or root robots.txt still Disallows the path. Test the live file, not the settings screen.
Fixed the noindex, then waited. Google has to recrawl before the change matters. Request indexing for the critical URLs. Monitor URL Inspection and the Pages report. Do not burn the quota refreshing the same URL every hour.
Mistakes that waste the afternoon
Treating a technical pass as "we are indexed." Pass means indexable. Indexed is Search Console's call.
Using `site:` as proof. Useful as a quick look. Unreliable for recent changes. The tool page says so; believe it.
Polishing titles while robots still blocks. A brilliant title on a Disallow or noindex URL is a draft.
Ignoring `X-Robots-Tag`. View Source will not show it. Headers will.
Checking staging. Different host, different robots, different answer.
Skipping the re-check after deploy. Audits that never re-hit production are how the staging rule survives three sprints.
When to stop spot-checking and audit the site
Escalate when:
- Money templates share the same noindex or bad canonical
- The Pages report is a wall of crawled-but-not-indexed on URLs that pass the five checks
- A migration left mixed hosts, leftover Disallows, or a sitemap full of redirects
- You need the full crawl → index → architecture → CWV order
That is the technical SEO audit checklist. For cutover night, use the site migration SEO checklist instead. Different job.
Closing
Run the Google Index Checker on the URLs that pay the bills. Clear every failed signal. Confirm the same URLs in Search Console. Re-check after deploy. That is the whole loop.
If the blockers are gone and the page still will not stick, stop tweaking meta tags. Open the readiness checker, then the audit checklist.
FAQ
What is a Google index checker?
A tool that tests whether a URL is technically free to be indexed. Scrawl's version checks HTTP status, robots.txt, noindex (meta and X-Robots-Tag), canonical mismatches, and redirects. It does not query Google's live index.
How do I check if a page is indexed by Google?
Use URL Inspection in Google Search Console for the definitive answer on a property you own. For a free technical pre-check, paste the URL into the Google Index Checker. The site: operator is a quick signal only.
Why is my page not indexed by Google?
Common technical causes: noindex meta or X-Robots-Tag, a robots.txt Disallow, a canonical pointing elsewhere, redirects, or a non-200 status. Google may also crawl a clear page and still decline to index it for quality or duplication reasons. Read the Pages report reason before rewriting titles.
Does Scrawl's Google Index Checker say "indexed" or "not indexed"?
No. It reports whether blocking signals are present. Search Console answers whether Google has kept the URL.
Is the Google Index Checker free?
Yes. Free, no login, no usage limits on the tool page.
How long does Google take to index a new page?
Google's recrawl docs say crawling after a request can take a few days to a few weeks, and that requesting a crawl does not guarantee inclusion. Strong internal links and a clean sitemap help discovery. There is no published SLA for "indexed by Tuesday."
What is the difference between crawled and indexed?
Crawled means Googlebot fetched the page. Indexed means Google kept it and may show it in results. A page can be crawled and still excluded.
How do I get Google to index a page faster?
Remove blocking signals first. Link the URL from pages Google already crawls. Include it in the XML sitemap. Then use URL Inspection → Request indexing for a small set of money URLs. Do not spam the same request; Google notes a quota and that repeats do not speed the crawl.
When should I use the SEO readiness checker instead?
When the five indexability checks pass but the URL still looks weak on tags, schema, or related hygiene. Start with the SEO Readiness Score Checker. Use the index checker when you suspect a hard block.
Do I need this if I already have Search Console?
Yes, as a pre-check and a post-deploy sanity pass. Search Console tells you what Google decided. The checker tells you what you are still sending that would make that decision easy.