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.
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.
Sample report
Illustrative example — fixed observable response
- 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
- Enter the exact public URL and choose Check signals.
- Review status, redirects, robots directives, and canonical hints observed in the response.
- Treat a clean amber result as “no public blocker observed,” not “indexed.”
- Open URL Inspection in the verified Search Console property for Google’s actual state.
+ saves the current site or page. Use ☆ beside any saved site, page, or list to favorite it. Recent check history appears below.
Create a named list
Target filled from your local choices.
Site passport Local context for this saved site
Local data
Saved targets, named lists, and recent check summaries remain only in this browser.
Observable signals
Need Google’s actual answer?
Open URL Inspection in the verified Search Console property for crawl status, Google-selected canonical, and indexing coverage. This tool intentionally does not guess those values.
Open URL Inspection →Rate this tool
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
- Paste sitemap URLs/XML and upload a GSC Page Indexing CSV; either source can be used alone.
- Keep the fallback at Unknown unless the export’s scope justifies another classification.
- Leave current fetch enabled for a bounded sample, or disable it for local-only reconciliation.
- Filter the resulting evidence by next action and verify high-impact URLs with URL Inspection separately.
| URL | Sitemap | Current crawl | GSC export | Evidence / next action |
|---|
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.
Inspect one URL’s observable blockers · Run a broader site audit · Reconcile a migration inventory
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.
You won't be emailed about that request anymore.
Loading…
➕ Request a feature
New requests are reviewed before they appear here.
À propos de l’outil
Vérifiez les signaux d’indexabilité observables d’une URL ou rapprochez les preuves d’un sitemap, d’une exploration et d’un export Google Search Console pour un ensemble d’URL. L’outil ne prétend jamais connaître les statuts d’indexation réservés à Google.
Gratuit, sans inscription. Diagnostiquez une URL publique ou rapprochez un sitemap et un export GSC. Pour la décision réelle de Google, utilisez l’inspection de l’URL.
Fonctionnalités
- Statut en direct et preuves de redirection
- Contrôles noindex HTML et HTTP
- Signaux canonical déclarés et contexte des conflits
- Lien direct vers l’inspection de l’URL pour la réponse vérifiée
Fonctionnement
Une requête serveur limitée suit l’URL, récupère les en-têtes et le HTML, puis des contrôles déterministes extraient le statut final, le chemin de redirection, les directives robots meta et HTTP ainsi que les indices canonical. Le lien Search Console sert de relais ; l’outil n’accède à aucune propriété et n’invente aucun verdict d’indexation.
Limites
- L’outil ne voit pas l’index Google, le dernier passage, la canonical sélectionnée, la raison de couverture, le JavaScript rendu ni les données de propriété. Les récupérations publiques peuvent différer de Googlebot. Il ne classe jamais une page comme indexée, découverte non explorée, explorée non indexée ou problème de qualité.
Questions fréquentes
Cet outil peut-il dire si Google a indexé une page ?
Non. Seule l’inspection de l’URL dans Search Console, pour une propriété vérifiée, peut rapporter l’état réel de l’index Google, le statut d’exploration et la canonical sélectionnée.
Pourquoi un résultat propre est-il ambre ?
Une réponse HTTP propre et l’absence de signaux noindex ou canonical bloquants montrent seulement qu’aucun obstacle public n’a été observé. Ils ne révèlent ni le calendrier d’exploration, ni les doublons, ni la qualité.
Une balise noindex supprime-t-elle immédiatement une page ?
Non. Un robot doit revisiter la page et traiter la directive. L’outil observe la directive actuelle, mais ne connaît ni le dernier passage de Google ni la date de mise à jour de l’index.
robots.txt peut-il prouver qu’une page n’est pas indexée ?
Non. Bloquer l’exploration ne garantit pas qu’une URL est absente de l’index. Utilisez Search Console et un testeur robots pour ces questions distinctes.
Que signifie un indice canonical pour l’indexation ?
La canonical indique une URL préférée pour un doublon, mais un moteur peut choisir une autre version. L’outil signale les signaux observables ; vérifiez la canonical choisie dans Search Console.