Languages

Google Index Checker

Free, no signup. Diagnose one public URL, or reconcile a sitemap and GSC export. For Google’s actual index decision, use URL Inspection.

Built by Patrick Stox

Checks run from our server; we fetch the URL you enter and don't keep the results. Anonymous run-level outcome counters may be used for aggregate research; URLs, domains, IPs, and identifiers are never included, and no statistic is released below 100 runs.

Feedback
Report a bug

Found something broken in Google Index Checker? Let us know what happened — this goes straight to a private triage queue, not a public list.

What will be sent 
 No tool inputs, uploads, pasted source, complete results, query parameters, or URL fragments are attached automatically. You can edit or remove the selected passage above. Browser and anti-abuse metadata is processed for spam prevention. 
  
 
  
 
 
  
 
 
  
 
Sample report
Illustrative example — fixed observable response
No public indexing blocker observed
  • Final response: HTTP 200.
  • Robots directives: no noindex observed.
  • Canonical: self-referencing https://example.com/guide.
  • Google index status: not evaluated — verify in URL Inspection.
 
 
How to use it
  1. Enter the exact public URL and choose Check signals.
  2. Review status, redirects, robots directives, and canonical hints observed in the response.
  3. Treat a clean amber result as “no public blocker observed,” not “indexed.”
  4. Open URL Inspection in the verified Search Console property for Google’s actual state.
 
 
       
     
   
What the results mean
Red blockers are directly observed technical barriers such as noindex or a failed final response. Redirect and canonical evidence describes the current URL path and declared preference. Amber means the public response does not answer Google-only questions about discovery, crawl scheduling, duplicate selection, quality, or index state.
How it works
A bounded server request follows the URL, returns response headers and HTML, and deterministic checks extract the final status, redirect path, meta and HTTP robots directives, and canonical hints. The Search Console link is a handoff; the tool has no property access and fabricates no index verdict.
Features
  • Live status and redirect evidence.
  • HTML and HTTP noindex checks.
  • Declared canonical hints and conflict context.
  • Direct URL Inspection handoff for the verified answer.
Limitations
It cannot see Google's index, last crawl, selected canonical, coverage reason, rendered JavaScript, or property data. Public fetches may also differ from Googlebot. It never labels a page indexed, discovered-not-crawled, crawled-not-indexed, or a quality issue.
 
Frequently asked questions
Can this tell me whether Google indexed a page?
No. Only Search Console URL Inspection for a verified property can report Google’s actual index stateStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed., crawl statusCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor., and selected canonicalHow search engines pick one canonical URL among duplicates and consolidate signals onto it..
Why is a clean result amber?
A clean HTTP response and noindexNoindex is a directive that tells search engines to keep a page out of their index, so it won't appear in search results. It works only on pages a crawler can actually fetch — a page blocked in robots.txt can never be noindexed./canonical signals only show that no blocker was observed. They do not reveal crawl scheduling, duplicate clustering, quality, or discovered-not-crawled states.
Does a noindex tag remove a page immediately?
No. A crawler must revisit the page and process the directive. This tool can observe the current directive but cannot see when Google last crawled it or when the index will update.
Can robots.txt prove that a page is not indexed?
No. Blocking crawling does not guarantee that a URL is absent from the index, and this page-level check focuses on the fetched response. Use Search Console and a robots tester for those separate questions.
What does a canonical hint mean for indexing?
A canonical names a preferred duplicate URL, but search engines can choose another version. This tool reports the declared signal and conflicts; Search Console is needed for Google’s selected canonical.
 
Reconcile sitemap, crawl, and GSC evidence
 
Free, no signup. Put sitemap membership, current fetch/status/canonical evidence, and a Google Search Console Page Indexing export in one transparent URL table. This reconciles supplied evidence; it does not call URL Inspection or claim Google’s live index state.
 
 
Local limits: 5 MB per sitemap or GSC input, 50,000 sitemap URLs, 50,000 GSC data rows, and 50,000 unique URLs in the combined reconciliation.
 
  Checks run from our server; we fetch the URL you enter and don't keep the results. Sitemap and GSC files are parsed locally. If crawl is enabled, at most 100 public URLs are fetched through the protected page-fetch endpoint; results remain in this tab. Anonymous run-level outcome counters may be used for aggregate research; URLs, domains, IPs, and identifiers are never included, and no statistic is released below 100 runs. 
 
 
Sample report Static evidence example
https://example.com/a
Sitemap: Yes · Current crawl: indexable · GSC: indexed
Action: Evidence aligns; monitor.
https://example.com/b
Sitemap: Yes · Current crawl: noindex · GSC: indexed
Action: Review the new blocking directive and whether the export is stale.
This demonstrates reconciliation logic; it is not a live Google index report.
 
 
 
How to use it
  1. Paste sitemap URLs/XML and upload a GSC Page Indexing CSV; either source can be used alone.
  2. Keep the fallback at Unknown unless the export’s scope justifies another classification.
  3. Leave current fetch enabled for a bounded sample, or disable it for local-only reconciliation.
  4. Filter the resulting evidence by next action and verify high-impact URLs with URL Inspection separately.
 
  
What the results mean
  • Sitemap — membership in the supplied inventory.
  • Current crawl — raw status, redirects, canonical, and blocking directives from the optional fetch.
  • GSC export — the parsed state in the uploaded file or chosen fallback.
  • Evidence / next action — deterministic explanation of agreement, conflict, or missing evidence.
 
How it works
Local parsers normalize one child sitemap and GSC CSV rows into URL evidence. The optional protected queue fetches up to 100 URLs with pacing and bounded retries, extracts final status, canonical, meta robots, and X-Robots-Tag, then the reconciliation engine joins all sources by normalized URL.
 
Features
  • Up to 50,000 local sitemap and GSC rows.
  • Local parsing with explicit fallback semantics.
  • Optional 100-URL current-evidence crawl.
  • One table combining inventory, crawl, and historical GSC evidence.
 
Limitations
GSC exports can be delayed and scoped, while current fetch evidence can change after export. Only raw HTML is fetched, only the first 100 combined URLs are crawled, and only 1,000 rows are rendered. The tool does not call URL Inspection, prove indexing, crawl sitemap indexes, render JavaScript, or diagnose every reason a URL is excluded.
 
Frequently asked questions
Does the reconciler check Google’s live index?
No. It reads the GSC export you upload and does not call URL Inspection. The result is a reconciliation of supplied and current fetch evidence.
What happens when a GSC export has no status column?
You choose a fallback state. Unknown is recommended because a URL’s presence in a CSV does not by itself prove indexed or not indexed.
How many URLs can it fetch?
Local inputs can contain up to 50,000 unique URLs, but the optional current crawl is bounded to the first 100 combined sitemap/GSC URLs.
What does not evaluated mean in the crawl column?
A current fetch could not be completed, including after bounded rate-limit retries. It is not converted into a blocker or a pass.
Can it parse a sitemap index?
No. Paste URLs or one child URL sitemap. Sitemap-index files are deliberately rejected by this interface.
 
Useful handoffs
Inspect one URL’s observable blockers · Run a broader site audit · Reconcile a migration inventory
 
   
Next stepXML Sitemap Generator — publish a sitemap that only lists URLs you want indexed.

People also explore
ToolCanonicalization CheckerToolXML Sitemap ValidatorToolRaw vs. Rendered HTML CheckerArticleSaaS SEO AuditArticleURL Inspection ToolArticleJoomla SEO
 
 
 
Feature requests for Google Index Checker
 

Upvote what you want most. New ideas can be submitted from the floating Feedback menu;
      requests appear here once approved, and the most-wanted rise to the top.

   
Loading…
  
  ➕ Request a feature   
New requests are reviewed before they appear here.
 
     
  
  
 
 
 
 
   
  
 
Where this tool helps
Common use cases
Diagnose observable blockers on one public URL
Review the fetched status, redirect path, meta or HTTP robots directives, canonical hint, and robots access without claiming Google indexed the page.
Separate public signals from Google-only evidence
Use the amber URL Inspection handoff for crawl status, Google-selected canonical, coverage reason, and actual index state instead of guessing.
Reconcile sitemap and Search Console exports
Join supplied sitemap membership and GSC Page Indexing rows locally, preserving explicit indexed, not-indexed, unknown, and not-present states.
Compare current crawl evidence with historical exports
Fetch a bounded public sample and surface aligned evidence, new blockers, redirects, off-canonical hints, missing sitemap URLs, and unresolved conflicts.
Create a prioritized indexation-review handoff
Export the transparent URL table and verify high-impact rows in URL Inspection, the source sitemap, page templates, and delivery systems.
Watch the full workflow
Google Index Checker walkthrough
Read the transcript

      
      

        
Google Index Checker

        

        
Hi. Google Index Checker helps you investigate why a page may have trouble appearing in Google. I’ll show you the simple one-page check first, then the larger comparison workflow. Along the way, I’ll explain what each result means and which questions only Google Search Console can answer.

      

      

        
Step 1

        

        
A page is indexed when Google has stored it and can show it in search results. This tool cannot see that private Google decision. What it can do is check the public page for common technical problems, or compare a larger list of URLs with files you provide.

      

      

        
Step 2

        

        
The common use cases are shown here. You can investigate one page, separate public clues from Google-only information, compare a sitemap with a Search Console export, spot changes over time, and create a clear list of URLs that need follow-up.

      

      

        
Step 3

        

        
Start by entering the exact public URL you want to diagnose. The checker reads what an ordinary web request can see. It does not sign in to your Search Console account. For this walkthrough, every URL and response is a clearly fictional example.

      

      

        
Step 4

        

        
I’ll enter the fictional old product URL and choose "Check signals." The tool follows the page request and finds three things worth reviewing: a redirect, a noindex instruction, and a canonical pointing somewhere else. Let’s take those one at a time.

      

      

        
Step 5

        

        
First, "URL redirects" means the address sent the checker to a different address. One redirect is not automatically bad, but your internal links and sitemap should normally use the intended final URL. A redirect alone does not tell you whether Google indexed the page.

      

      

        
Step 6

        

        
Next, "Noindex directive observed" is the clearest blocker in this example. Noindex is an instruction asking search engines not to keep the page in their index. Remove it only if this page should appear in search, then wait for Google to crawl the changed page again.

      

      

        
Step 7

        

        
A canonical is the page owner’s preferred URL when several URLs have similar content. Here, the page names a broader shoes URL instead of itself. That may be intentional, so verify the destination and your internal links. This is only the declared preference; Google can select a different canonical.

      

      

        
Step 8

        

        
The amber card marks the boundary. Use "Open URL Inspection" inside your verified Google Search Console property to see Google’s last known crawl information, selected canonical, and index status. The free checker does not guess those private values.

      

      

        
Step 9

        

        
Behind the scenes, the checker reads response status, redirects, page HTML, robots instructions, and canonical links. It does not run the page’s JavaScript, and the public response may differ from what Googlebot receives. Think of this as technical evidence, not a complete indexing verdict.

      

      

        
Step 10

        

        
The second workflow is for a group of pages. Reconcile simply means line up different sources so you can compare them. Here, the tool combines sitemap membership, a Search Console Page Indexing CSV you upload, and an optional fresh public check.

      

      

        
Step 11

        

        
A sitemap is a file listing URLs you want search engines to discover. The other input is a CSV spreadsheet exported from Search Console. Each file can be up to five megabytes and the combined list can contain fifty thousand URLs. The optional live check covers the first one hundred URLs.

      

      

        
Step 12

        

        
I’ll load a fictional sitemap containing three product URLs, then a fictional Search Console export containing four rows. Alpha, beta, and delta are labeled indexed in that uploaded file. Gamma is labeled not indexed. No real account or customer data is involved.

      

      

        
Step 13

        

        
Leave the fallback set to "Unknown." This is important when an uploaded CSV contains URLs but no clear status column. Unknown means the file does not provide enough evidence. It is safer than turning mere presence in a spreadsheet into a made-up indexing answer.

      

      

        
Step 14

        

        
Now I’ll choose "Reconcile evidence." The tool compares three sitemap URLs, four uploaded Search Console rows, and four current fictional page checks. The completion note also says URL Inspection was not run, so there is no hidden claim of fresh Google data.

      

      

        
Step 15

        

        
The summary groups four URLs by current technical condition and uploaded Search Console label. Two appear technically indexable and were supplied as indexed. One has a current blocker despite an indexed label. One looks indexable but was supplied as not indexed. The rows explain what to do next.

      

      

        
Step 16

        

        
Alpha is the simple case. It appears in the sitemap, returns HTTP 200, points its canonical to itself, and has no observed blocker. The uploaded file also labels it indexed. The suggested action is "Signals align; continue monitoring," not a promise that Google’s status can never change.

      

      

        
Step 17

        

        
Beta needs investigation. The uploaded file labels it indexed, but the current fictional page now contains noindex. The page may have changed after the export, or the export may be older or differently scoped. Confirm whether the page should be searchable before removing anything.

      

      

        
Step 18

        

        
Delta looks technically indexable and is labeled indexed in the uploaded file, but it is missing from this sitemap. Decide whether it belongs in the sitemap or should point somewhere else. Missing from one supplied sitemap is a question to review, not automatic proof of an error.

      

      

        
Step 19

        

        
Gamma is in the sitemap and its current public signals look indexable, but the uploaded file labels it not indexed. This tool cannot explain that difference from public data alone. Open the exact URL in Search Console to check discovery, crawl timing, duplicate selection, and coverage details.

      

      

        
Step 20

        

        
Use "Download CSV" to save the combined table. Each row keeps the URL, sitemap membership, current public check, uploaded Search Console label, evidence, and suggested next action together. Record when each source was collected so the next reviewer can understand why values may differ.

      

      

        
Step 21

        

        
The files are parsed in your browser. If you enable the current check, the protected queue fetches up to one hundred pages and compares them by normalized URL. The screen shows up to one thousand rows, while the downloaded CSV can retain the complete processed result.

      

      

        
Step 22

        

        
Keep these limits in mind. Search Console exports can be delayed or incomplete, public page signals change, sitemap index files are not supported here, and JavaScript is not rendered. Fix the specific technical issue you can prove, rerun the check, and use URL Inspection for Google’s current answer.

      

      

        
Check the signal. Fix the cause. Verify with Google.

        

        
That’s the full workflow. Fix only the problem the evidence actually shows, run the check again, and use URL Inspection for Google’s current decision. You can use the tool free at patrickstox.com slash tools slash google-index-checker.

      

    
 
          
 
Common issues & how to fix them
 
     
  •  Error URL is not a live 2xx response Fix: Restore a live 2xx response at the evaluated URL, then rerun the check. 
  •  Error Noindex directive blocks indexing Fix: Remove the noindex directive from pages that should be indexed, then rerun the check. 
  •  Warning Canonical points to another URL Fix: Point the canonical at the intended preferred URL, or confirm that consolidation is deliberate. 
  •  Warning URL redirects before evaluation Fix: Update the source to use the live final URL directly, then rerun the check. 
  •  Error Robots.txt blocks crawling Fix: Allow Googlebot to crawl this path in robots.txt, publish the file, then rerun the check. 
  •  Warning Sitemap URL is missing from the index set Fix: Verify the URL is canonical, indexable, useful, and internally linked, then inspect its exclusion reason in URL Inspection. 
  •  Warning Indexed URL is absent from the sitemap Fix: Add the canonical indexable URL to the sitemap or confirm its deliberate exclusion and remove stale variants. 
  •  Warning Indexed URL conflicts with the canonical set Fix: Choose the preferred URL and align sitemap membership, canonical tags, redirects, and internal links to it. 
  •  Warning Expected indexed URL is blocked by robots Fix: Remove or narrow the robots.txt rule when the expected URL must be crawled and indexed. 
  •  Warning Expected indexed URL has noindex Fix: Remove noindex from the expected URL and confirm both raw and rendered directives permit indexing. 
  •  Warning Multiple URL variants appear in the index set Fix: Redirect and canonicalize duplicate variants to one preferred URL and link internally only to that version. 
    •