Bahasa

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 state, crawl status, and selected canonical.
Why is a clean result amber?
A clean HTTP response and noindex/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.
 
     
  
  
 
 
 
 
   
  
Tentang alat
Periksa sinyal kemampuan indeks yang dapat diamati dari satu URL, atau cocokkan bukti sitemap, perayapan, dan Google Search Console untuk sekumpulan URL. Alat ini tidak mengklaim mengetahui status pengindeksan yang hanya dapat diketahui Google.
Gratis tanpa pendaftaran. Diagnosis satu URL publik, atau cocokkan sitemap dengan ekspor GSC. Untuk keputusan indeks Google yang sebenarnya, gunakan URL Inspection.
Fitur
  • Status langsung dan bukti pengalihan.
  • Pemeriksaan noindex HTML dan HTTP.
  • Petunjuk canonical yang dinyatakan dan konteks konflik.
  • Handoff langsung ke URL Inspection untuk jawaban terverifikasi.
Cara kerja
Permintaan server terbatas mengikuti URL, mengembalikan header respons dan HTML, lalu pemeriksaan deterministik mengambil status akhir, jalur pengalihan, direktif robots meta dan HTTP, serta petunjuk canonical. Tautan Search Console adalah handoff; alat ini tidak memiliki akses properti dan tidak mengarang putusan indeks.
Batasan
  • Alat ini tidak dapat melihat indeks Google, perayapan terakhir, canonical yang dipilih, alasan cakupan, JavaScript yang dirender, atau data properti. Pengambilan publik juga dapat berbeda dari Googlebot. Alat ini tidak pernah memberi label terindeks, ditemukan-belum-dirayapi, dirayapi-belum-diindeks, atau masalah kualitas.
Pertanyaan umum
Bisakah alat ini memberi tahu apakah Google mengindeks sebuah halaman?
Tidak. Hanya URL Inspection di Search Console untuk properti terverifikasi yang dapat melaporkan keadaan indeks, status perayapan, dan canonical pilihan Google yang sebenarnya.
Mengapa hasil yang bersih berwarna amber?
Respons HTTP yang bersih dan sinyal noindex/canonical hanya menunjukkan bahwa tidak ada penghambat yang teramati. Keduanya tidak mengungkap jadwal perayapan, pengelompokan duplikat, kualitas, atau keadaan ditemukan-belum-dirayapi.
Apakah tag noindex segera menghapus halaman?
Tidak. Perayap harus mengunjungi ulang halaman dan memproses direktif tersebut. Alat ini dapat mengamati direktif saat ini, tetapi tidak dapat melihat kapan Google terakhir merayapinya atau kapan indeks diperbarui.
Bisakah robots.txt membuktikan bahwa halaman tidak diindeks?
Tidak. Memblokir perayapan tidak menjamin URL tidak ada di indeks, dan pemeriksaan tingkat halaman ini berfokus pada respons yang diambil. Gunakan Search Console dan penguji robots untuk pertanyaan terpisah tersebut.
Apa arti petunjuk canonical untuk pengindeksan?
Canonical menyebut URL duplikat yang diutamakan, tetapi mesin pencari dapat memilih versi lain. Alat ini melaporkan sinyal yang dinyatakan dan konfliknya; Search Console diperlukan untuk mengetahui canonical pilihan Google.