Google index checker

Check whether Google can index a page

Enter one public URL. We check the response, redirects, robots rules, noindex directives, canonical, sitemap presence, visible content, JavaScript dependence, and a simple homepage link signal. This does not prove that the page is already in Google's index.

One URL at a time. We never query or scrape Google search results.

What this Google index checker actually tells you

A page can appear in Google only if Googlebot can reach it, the page allows indexing, and Google chooses that URL as useful enough to keep. This checker covers the first two parts and several signals that affect the third. It follows redirects, tests the final HTTP response, applies Googlebot-style robots.txt matching, reads page and header directives, compares the canonical URL, checks common sitemap locations, estimates visible text, and looks for a link from the homepage.

A clean result means we found no obvious technical block. It is not a promise of indexing or ranking. Google can still exclude a page because it is duplicated, unhelpful, low quality, soft 404, or simply not selected yet. The only reliable place to see Google's current decision for a property you own is the URL Inspection report in Google Search Console.

Why a page may not be indexed

Hard blocks come first. A non-200 response, a Googlebot Disallow rule, a noindex directive, or a canonical pointing elsewhere can stop the submitted URL from being indexed as itself. Fix these before rewriting content or requesting indexing. Also shorten long redirect chains. They waste crawl time and make it easier to link to the wrong version.

Discovery comes next. Put the canonical URL in an XML sitemap and link to it from relevant, crawlable pages. This tool checks only whether the homepage links to the target, so treat that result as a simple clue rather than a full internal-link audit. A page can be healthy without a direct homepage link, but it should not be isolated.

Then review the page itself. Very short pages often land in “Crawled — currently not indexed” because they do not add enough original value. There is no universal word-count rule, but a page with fewer than about 200 visible words deserves a closer look. Explain the topic directly, answer the searcher's next questions, and remove near-duplicate pages. If the raw HTML is nearly empty while scripts are large, server-render the main content and links.

Crawled but not indexed vs. discovered but not crawled

Crawled — currently not indexed means Google fetched the page but did not keep it in the index. Check content uniqueness, canonical selection, soft-404 signals, internal links, and whether the page satisfies a distinct search intent. Repeatedly pressing Request indexing without changing the reason rarely helps.

Discovered — currently not indexed means Google knows the URL but has not fetched it yet. Strengthen internal links, keep sitemaps accurate, improve server reliability, and avoid publishing large sets of low-value URLs. On a new or small site, discovery and crawl scheduling can also take time.

How to request indexing correctly

  1. Fix every hard block and make the canonical version return 200.
  2. Add the canonical URL to a valid sitemap and link to it internally.
  3. Open Search Console and inspect the exact final URL.
  4. Run the live test, then choose Request indexing.
  5. Check again later. A request asks Google to recrawl; it does not force inclusion.

For a portfolio of sites, the harder problem is remembering which key pages need another check. AllSites connects read-only Search Console access and reviews key-page status every week, beside traffic, revenue, uptime, and alerts.

Track the real status every week

Monitor this weekly with AllSites

The checker shows technical eligibility. AllSites uses your own read-only Search Console data to track Google's actual status for key pages.

Start trial

Google indexing FAQ

Common questions

Does this tell me whether my page is already indexed?

No. It checks whether Google can index the page and highlights common technical or discovery risks. Use the Google site search button as a quick clue, then use URL Inspection in Search Console for the authoritative status.

Why can a page be crawled but not indexed?

Google may crawl a URL and still decide not to index it. Common reasons include thin or duplicated content, a conflicting canonical, weak internal linking, soft-404 signals, or a page that adds little beyond other pages.

What does discovered, currently not indexed mean?

Google knows the URL exists but has not crawled it yet. Improve internal links, keep the server fast and reliable, include the URL in a sitemap, and avoid generating large numbers of low-value URLs.

How do I request indexing?

Open Google Search Console, inspect the exact canonical URL, review the live test, and choose Request indexing. Fix any blocking issue first. A request is not a guarantee that Google will index the page.

Can JavaScript stop indexing?

Google can render JavaScript, but rendering can be delayed or fail. Put the main answer, canonical, robots directives, and important internal links in the initial HTML whenever possible.

Is a sitemap enough to get indexed?

No. A sitemap helps discovery and gives Google a clean URL list. It does not override noindex, robots blocks, weak content, duplicate selection, or quality decisions.