Google Index Checker

How this checker works

For each URL you submit, this tool runs a site:-restricted public search query through the Google Custom Search API or SerpApi and checks whether that exact URL appears among the top organic results returned. That makes it a public search-visibility proxy: it reflects what a live search query can surface right now, not a direct read of Google's internal index. It does not connect to Google Search Console, does not use any Search Console credentials, and cannot see crawl history, manual actions, or the canonical URL Google actually selected for a page.

Because the result depends on a live third-party search query, treat a Not found result as a prompt to investigate rather than final proof of exclusion, and treat an Appears indexed result as a positive signal rather than a ranking guarantee. If you control the property, Search Console's URL Inspection tool is the only first-party source for Google's actual indexing decision.

What each result status means

Common reasons a URL may not appear in search results

A Not found result can come from several different causes. Some resolve on their own as Google recrawls the site; others need a direct fix before recrawling will help.

• New or recently changed page. The URL has not been crawled or reprocessed since it was published or last edited.
• A noindex directive. A page-level meta robots tag or an X-Robots-Tag HTTP header set to noindex tells Google not to index the page.
• A robots.txt block. Crawling is disallowed for the URL or a parent path, so Googlebot cannot fetch it at all.
• A canonical pointing elsewhere. A rel="canonical" tag naming a different preferred URL tells Google to index that URL instead of this one.
• A redirect or error response. The URL returns a redirect chain, a 4xx or 5xx status, or a soft 404 (a page that returns HTTP 200 but reads as an error, empty, or placeholder page) instead of a clean, substantial 200 response.
• No discoverable path. The page is not linked from any crawlable page and is missing from the submitted XML sitemap, so Google has no reliable way to find it.
• Thin or duplicate content. The page has very little unique text, or its content closely matches another page that is already indexed.
• Content hidden from crawling. The main content only appears after a user interacts with the page, or depends on client-side rendering that does not reliably produce the same result during a crawl.
• A login or access restriction. The page requires authentication or otherwise blocks automated requests, so a crawl sees a restricted or empty state instead of the real content.
• A manual action or quality signal. In some cases, Search Console's Manual Actions or Security Issues reports explain why a property or URL is excluded.

Practical troubleshooting workflow

Start with evidence from the affected URL. A new page may simply be waiting for discovery or recrawling, while an older page may have a technical or quality issue from the list above.

1. Confirm the response. The preferred URL should normally return HTTP 200 rather than redirecting, returning a soft 404, or failing at the server.
2. Review crawl and index controls. Check robots.txt and page-level robots directives for accidental blocks or noindex.
3. Check the canonical. A canonical pointing elsewhere tells Google that another URL is preferred.
4. Confirm discovery paths. Include indexable URLs in a clean XML sitemap and link to important pages from relevant, crawlable pages.
5. Verify what a crawl actually sees. Confirm the page's main content renders without requiring a login, a click, or client-side JavaScript that a crawl cannot execute the same way a browser does.
6. Use URL Inspection. Search Console can show the selected canonical, last crawl, indexing decision, and whether an indexing request is appropriate.

Requesting indexing does not force crawling or inclusion. Google decides whether and when to crawl and index a URL.

Related technical checks

Index checking questions