Inspection d’URL Outil

TL;DR — The Inspection d’URL outil dans la recherche Google Console indique vous si un of votre pages is in Google, and pourquoi or pourquoi pas. Simplement know ce: by par défaut it montre vous the dernier temps Google indexé lune page, pas how lune page semble correct now. Si vous simplement modifié something, click Tester Live URL to vérifier the current version.

Ce que c’est

The Inspection d’URL outil lives dans la recherche Google Console. Vous paste in un URL from a site vous propre, and Google indique vous how it sees que page — la plupart importantly, si it’s in Google’s index and able to montrer up in search.

Vous pouvez seulement inspect URLs on a property you’ve verified in Search Console. Vous can’t vérifier a competitor’s page.

The un chose beginners obtenir incorrect

Quand vous inspect une URL, the report vous voir premier is a snapshot from the dernier temps Google indexé it — pas the live page. Google dit it directement: ce is pas a live tester, le résultats are from the la plupart recently indexé version, pas the live version on the web. Evidence for this claim The default URL Inspection result describes Google's indexed version, not a live fetch of the current page. Scope: Google Search Console URL Inspection; Test Live URL is the separate current-page test. Confidence: high · Verified: 2026-07-14 Google Search Console Help: URL Inspection tool

So si vous simplement fixed something and vouloir to know si the fix worked, don’t trust que premier screen. Click Tester Live URL and Google va récupérer lune page correct now.

Ce que it indique vous

• Is lune page on Google? “URL is on Google” signifie it’s eligible to apparaître in search — pas que it’s ranking, simplement que it peut montrer up. “URL is not on Google” signifie it can’t apparaître.
• Was Google allowed to explorer and index it? Si vous accidentally blocked the page, ce is où you’ll voir it.
• Qui version did Google pick? Si vous have duplicate or similaire pages, Google chooses un “canonical” version to montrer. The outil indique vous qui un.
• View crawled page montre vous the réel HTML Google got, a screenshot of how lune page rendered, and quelconque errors.

Requête Indexation

There’s a button que dit Requête Indexation. It indique Google “please come regarder at ce page.” That’s tout it fait. It fait pas force Google to index lune page, it fait pas aider vous rank, and clicking it over and over doesn’t speed anything up — there’s a daily limite, and you’ll simplement utiliser it up. Evidence for this claim Request Indexing does not guarantee that a page will appear in Google's index. Scope: Google Search Console's Request Indexing feature; requests are subject to a daily limit. Confidence: high · Verified: 2026-07-14 Google Search Console Help: URL Inspection tool Utiliser it une fois pour a nouveau or freshly mis à jour page, alors déplacer on. You’ll besoin to be an owner or complet utilisateur on the property to utiliser it — and si you’ve got a batch of nouveau or modifié URLs plutôt que simplement un, Google’s advice is to submit a sitemap au lieu de clicking the button repeatedly.

Vouloir the field-by-field reading guide, the canonical-mismatch diagnostic, the JavaScript debugging workflow, and the API? Switch to the Avancé tab.

TL;DR — Inspection d’URL reports how Google sees un URL on a verified property. The par défaut report is the last-indexed snapshot, pas the live page — run Tester Live URL pour the current state. Lire the coverage panel pour explorer/index permissions, discovery (sitemap + referring page), and the user-declared vs Google-selected canonical (a mismatch is votre la plupart actionable diagnostic). View crawled page donne vous rendered HTML, a screenshot, the HTTP réponse, page resources, and JS console messages — the JavaScript-SEO debugging surface. Requête Indexation is a queue hint with a daily quota: aucun guarantee, aucun ranking effect. The Inspection d’URL API renvoie the indexé state (aucun live tester) at 2 000 QPD / 600 QPM per property.

Ce que the outil en réalité fait

Google’s propre framing: the Inspection d’URL outil “provides information à propos de Google’s indexé version of a spécifique page, and aussi permet vous to tester si a URL pourrait be indexable.” Ceux are two distinct modes, and conflating les is the unique la plupart courant mistake I voir.

It’s aussi owner-only. “The URL must be in the currently opened property” — vous peut seulement inspect URLs on a Search Console property you’ve verified. There’s aucun inspecting competitors.

Indexé snapshot vs Tester Live URL

The par défaut report is a snapshot of the dernier explorer. Google is explicit: “Ce is pas a live tester. Le résultats affiché are from la plupart recently indexé version of a page, pas the live version on the web.” Evidence for this claim The default URL Inspection result describes Google's indexed version, not a live fetch of the current page. Scope: Google Search Console URL Inspection; Test Live URL is the separate current-page test. Confidence: high · Verified: 2026-07-14 Google Search Console Help: URL Inspection tool

Que distinction drives quand vous utiliser chaque mode:

• Diagnosing what’s en réalité dans l’index correct now? Lire the par défaut indexé view. That’s the state Google is currently acting on.
• Simplement shipped a fix and vouloir to know si it worked? Run Tester Live URL. It récupère and renders the current page so vous pouvez confirmer the fix avant vous wait on a recrawl.

A huge amount of needless panic — and needless “nothing changed” confusion — comes from reading the incorrect un. Si vous fixed a noindex an hour ago and the indexé snapshot encore montre it blocked, that’s attendu; the snapshot predates votre fix.

Two scope limites on Tester Live URL worth knowing: it fait follow redirections quand it récupère lune page, but it doesn’t montrer vous the chaîne de redirections the façon a dedicated redirection checker fait, and it can’t predict qui URL Google va select as canonical — the Google-selected canonical field seulement comes from the indexé view, parce que that’s a decision Google rend as partie of indexation, pas something a unique live récupérer peut determine.

Reading the coverage panel, field by field

Index status verdict. “URL is on Google signifie que l’URL is eligible to apparaître in Résultats de recherche, but n’est pas guaranteed to be là.” Eligible n’est pas the même as présent, and it’s certainly pas the même as ranking. “URL n’est pas on Google signifie que l’URL can’t apparaître in Résultats de recherche.”

Explorer allowed? “Indicates si votre site allowed Google to explorer lune page or blocked it with a robots.txt rule.” A No ici points straight at robots.txt.

Indexation allowed? “Whether or not your page explicitly disallowed indexing.” A No ici points at a noindex directive (meta tag or X-Robots-Tag header).

Discovery. The panel aussi montre the sitemap(s) que référence l’URL and the referring page Google followed to découvrir it. Si une URL vous expect to be trouvé montre aucun sitemap and aucun referring page, treat que as a signal to vérifier votre maillage interne and sitemap inclusion — pas a confirmed verdict. The panel isn’t guaranteed to liste every chemin Google utilisé to trouver une URL, so an vide field is a raison to investigate, pas proof there’s aucun discovery chemin at tout.

Canonicals — the la plupart actionable field ici. Two lines:

• “User-declared canonical: Si votre page explicitly declares une URL canonique, it va be affiché ici.”
• “Google-selected canonical: Lune page que Google selected as the canonical (authoritative) URL.”

Quand ceux two disagree, Google has overridden the canonical vous declared — it decided some autre URL is the authoritative un. That’s votre cue to investigate: duplicate or near-contenu dupliqué, inconsistent maillage interne, mixed canonical signals, or a stronger duplicate elsewhere. Ce unique comparison is the la plupart utile diagnostic in the whole panel. (Pour the underlying mechanics, ce ties into the canonicalization material elsewhere in ce cluster.)

Enhancements. The report surfaces eligible rich-result types and structured données it detected (Breadcrumbs, FAQ, Products, and so on). Remarque que the old Ergonomie mobile section is gone — Google retired que report, so it ne … plus apparaît ici.

View crawled page — the JavaScript-SEO debugging surface

Ce is où Inspection d’URL earns its garder pour technical fonctionner. Ouvrir View crawled page (on the indexé result) or View testé page (on a live tester) and vous obtenir the rendered HTML, a screenshot of the rendered page, the HTTP réponse headers, the liste of page resources Google chargé, and the JavaScript console messages.

Pour a JS-heavy page, ce is the whole debugging loop in un screen:

1. Screenshot — fait the rendered page en réalité contain votre content, or is it blank/half-built? Si content vous pouvez voir in votre navigateur is manquant ici, Google isn’t rendering it.
2. Rendered HTML — search it pour le contenu and liens que devrait be là après JavaScript runs. Si they’re absent, votre content dépend on something Google’s renderer didn’t execute.
3. Page resources — quelconque resource que couldn’t be chargé (a blocked JS fichier, a 404’d API, a robots-blocked script) is a prime suspect pour manquant rendered content.
4. JS console messages — errors ici souvent expliquer exactly pourquoi the render came up short.

Ce is the workflow I lean on pour JavaScript SEO problems, and it’s the partie la plupart write-ups gloss over. Un caveat: ce que you’re looking at is Google’s rendering of que unique récupérer — the indexé snapshot’s dernier réussir, or the live test’s réussir correct now — pas a certified guarantee que every system Google uses pour indexation rendered lune page identically.

Requête Indexation — Ce que c’est and isn’t

The Requête Indexation button runs a rapide live tester and alors pushes l’URL into Google’s explorer queue. Two hard limites to internalize:

• “Submitting une requête ne fait pas guarantee que lune page va apparaître in the Google Index.” It’s a discovery hint, pas a command.
• “There is a daily limit to how many index requests you can submit.” Spamming the même URL simplement burns que quota and accomplishes nothing.
• “Vous doit be an owner or complet utilisateur of the Search Console property to be able to requête indexation in the Inspection d’URL outil.” Restricted utilisateurs don’t obtenir a working option ici.

And to be blunt à propos de Ce que c’est pas: it n’est pas a ranking lever. Indexation and ranking are separate stages; nudging une URL into the explorer queue has aucun effect on où it ranks. It aussi doesn’t override canonicalization — Google has said requesting indexation doesn’t modifier qui URL it selects as canonical. Utiliser it une fois pour genuinely nouveau, mis à jour, or just-fixed pages. That’s the entier legitimate utiliser cas.

It’s aussi pas a bulk outil. Google’s propre recommendation: “Si vous have grand numbers of URLs, submit a sitemap.” Working via a spreadsheet of URLs un Requête Indexation click at a temps simplement burns votre daily quota faster que it helps — a sitemap is the mechanism construit pour volume.

The Inspection d’URL API

Pour monitoring at scale there’s a programmatic equivalent, the Inspection d’URL API (urlInspection.index.inspect). The per-property quota is 2 000 requêtes per day and 600 per minute. Evidence for this claim The URL Inspection API quota is 2,000 queries per day and 600 queries per minute per Search Console property. Scope: Current Search Console URL Inspection API per-property usage limits. Confidence: high · Verified: 2026-07-14 Google Search Console API: Usage limits

Two choses to garder straight:

• The API renvoie the indexé state seulement — verdict, coverage state, robots and indexation state, dernier explorer temps, page récupérer state, the Google-selected and user-declared canonicals, how it was crawled, referring URLs, and sitemap. It fait pas run a live tester the façon the UI’s Tester Live URL fait.
• The 2 000/day-per-property cap signifie bulk index monitoring à travers a grand site nécessite batching, or splitting le site à travers multiple verified properties. Several third-party outils wrap the API to faire ce practical.

It pairs naturally with lune page Indexation report pour spotting qui URLs to inspect, and with the broader Search Console API and the Performances report quand you’re building votre propre monitoring.

Courant myths

• “Request Indexing forces Google to index my page.” Aucun — submitting “ne fait pas guarantee que lune page va apparaître in the Google Index.”
• “Request Indexing makes a page rank, or rank faster.” Aucun. It affecte discovery/recrawl, pas ranking.
• “Re-submitting the same URL speeds it up.” Aucun — it simplement spends votre daily quota.
• “On Google means it’s ranking.” Aucun — it signifie eligible to apparaître.
• “The report shows my page as it is right now.” Aucun — the par défaut is the last-indexed snapshot. Tester Live URL is the live mode.
• “I can inspect any URL.” Aucun — owner-only; l’URL doit be in the currently opened property.
• “The API runs a live test like the UI.” Aucun — the API renvoie indexé state seulement.

AI summary

A condensed prendre on the Avancé version:

• Ce que c’est: Inspection d’URL reports how Google sees un URL on a verified property vous propre (aucun competitor URLs). Google: it “provides information à propos de Google’s indexé version of a spécifique page, and aussi permet vous to tester si une URL pourrait be indexable.”
• Snapshot vs live: the par défaut view is the last-indexed snapshot, “pas the live version on the web.” Run Tester Live URL to vérifier the current state après a fix — it follows redirections but doesn’t montrer the chain, and it can’t predict the Google-selected canonical (that’s an indexed-view-only field).
• Verdict: “URL is on Google” = eligible to apparaître, pas ranking, pas guaranteed.
• Coverage panel: explorer allowed (robots.txt), indexation allowed (noindex), discovery (sitemap + referring page), and user-declared vs Google-selected canonical — a mismatch signifie Google overrode votre canonical and is the la plupart actionable diagnostic.
• View crawled page: rendered HTML + screenshot + HTTP réponse + page resources + JS console messages — the JavaScript-SEO debugging surface.
• Requête Indexation: a queue hint with a daily limite, exige owner or full-user accès to the property; “ne fait pas guarantee que lune page va apparaître in the Google Index,” aucun ranking effect, doesn’t modifier canonicalization. Pour bulk URLs, Google’s advice is to submit a sitemap à la place.
• API: renvoie indexé state seulement (aucun live tester) at 2 000 QPD / 600 QPM per property; batch or split properties pour bulk monitoring.

Documentation officielle

Primary-source documentation from Google.

Recherche Google Console

• Inspection d’URL Outil — the canonical Aider doc: index status verdicts, coverage, canonicals, View crawled page, and Requête Indexation.
• Demander Google to recrawl URLs — la requête Indexation permission requirement, le sitemap-for-bulk-URLs recommendation, and the no-guarantee framing.

Inspection d’URL API

• Welcoming the nouveau Search Console Inspection d’URL API — Search Central blog announcing the API.
• Usage Limites — Search Console API — the 2 000/day and 600/minute per-property quotas.
• urlInspection.index.inspect référence — the méthode and the fields it renvoie.

Quotes from the source

On-the-record statements from Google’s documentation. Chaque lien is a deep lien que jumps to the quoted passage on the source page.

Google — ce que the outil is

• “The URL Inspection tool provides information about Google’s indexed version of a specific page, and also allows you to test whether a URL might be indexable.” — Recherche Google Console Aider. Jump to quote
• “This is not a live test. The results shown are from most recently indexed version of a page, not the live version on the web.” Jump to quote

Google — index status verdicts

• “URL is on Google means that the URL is eligible to appear in Search results, but is not guaranteed to be there.” Jump to quote
• “URL is not on Google means that the URL can’t appear in Search results.” Jump to quote

Google — coverage: explorer, indexation, canonicals

• “Crawl allowed? Indicates whether your site allowed Google to crawl the page or blocked it with a robots.txt rule.” Jump to quote
• “Indexing allowed? Whether or not your page explicitly disallowed indexing.” Jump to quote
• “User-declared canonical: If your page explicitly declares a canonical URL, it will be shown here.” Jump to quote
• “Google-selected canonical: The page that Google selected as the canonical (authoritative) URL.” Jump to quote

Google — Requête Indexation and ownership

• “Submitting a request does not guarantee that the page will appear in the Google Index.” Jump to quote
• “There is a daily limit to how many index requests you can submit.” Jump to quote
• “The URL must be in the currently opened property.” Jump to quote

Google — Requête Indexation permission and scale

• “You must be an owner or full user of the Search Console property to be able to request indexing in the URL Inspection tool.” — Google, “Ask Google to recrawl URLs.” Jump to quote
• “If you have large numbers of URLs, submit a sitemap.” Jump to quote

Reading a Inspection d’URL result — checklist

A rapide réussir to diagnose un URL:

• Confirmer you’re in the correct verified property (owner-only; aucun competitor URLs).
• Vérifier the verdict — “on Google” signifie eligible, pas ranking.
• Si vous simplement modifié lune page, run Tester Live URL — don’t trust the indexé snapshot pour current state.
• Explorer allowed? No → vérifier robots.txt.
• Indexation allowed? No → vérifier pour noindex (meta tag or X-Robots-Tag).
• Comparer user-declared vs Google-selected canonical — a mismatch signifie Google overrode votre canonical; investigate duplicates and linking.
• Vérifier discovery — is a sitemap and/or referring page listed? Si pas, vérifier maillage interne and sitemap inclusion; an vide field is a signal to investigate, pas proof there’s aucun chemin in.
• Ouvrir View crawled page → screenshot, rendered HTML, page resources, JS console messages pour render problèmes.
• Seulement utiliser Requête Indexation pour nouveau/mis à jour/fixed pages — une fois, pas repeatedly.

The mental models

1. Snapshot vs live — pick by votre question. The par défaut report réponses “what is Google acting on right now?” (the last-indexed snapshot). Tester Live URL réponses “would the current page be indexable?” Decide qui question you’re asking avant vous lire a result, and you’ll arrêter misreading stale données as a live échec.

2. Verdict ≠ ranking. “URL is on Google” = eligible to apparaître. Pas présent, pas ranked. Garder indexation and ranking as separate stages in votre head.

3. The canonical comparison. User-declared vs Google-selected canonical is the panel’s la plupart actionable line. Ils match → Google agrees with vous. Ils differ → Google overrode vous; go trouver the duplicate or signal that’s stronger que votre declared canonical.

4. The render-debug loop (View crawled page). Screenshot (is le contenu là?) → rendered HTML (is the markup là?) → page resources (did anything échouer to charger?) → JS console (quelconque errors?). Walk it in que order to localize a JavaScript rendering échec.

5. Requête Indexation is a hint, pas a command. It nudges discovery/recrawl. It doesn’t guarantee indexation, doesn’t rank, doesn’t modifier canonicalization, and has a daily quota. Un nudge per nouveau/modifié page.

Inspection d’URL — cheat sheet

Two modes

Coverage fields → ce que to vérifier

Verdicts

• URL is on Google — eligible to apparaître (pas ranking, pas guaranteed présent).
• URL n’est pas on Google — can’t apparaître in results.

Requête Indexation

• Queue hint, daily quota, aucun guarantee, aucun ranking effect, doesn’t modifier canonicalization. Exige owner/full-user accès. Utiliser une fois per nouveau/mis à jour page; pour bulk URLs, submit a sitemap à la place.

API

• urlInspection.index.inspect — 2 000 QPD / 600 QPM per property.
• Renvoie indexé state seulement (aucun live tester).

Inspect une URL via the API

The Inspection d’URL API renvoie the même indexé state as the UI (aucun live tester), at 2 000 requêtes/day and 600/minute per property. Here’s a minimal curl contre the urlInspection.index.inspect endpoint — swap in an OAuth accès token with the webmasters.readonly scope, l’URL you’re inspecting, and the verified property (siteUrl).

macOS / Linux

ACCESS_TOKEN="ya29...your-oauth-token"

curl -s -X POST \
  "https://searchconsole.googleapis.com/v1/urlInspection/index:inspect" \
  -H "Authorization: Bearer ${ACCESS_TOKEN}" \
  -H "Content-Type: application/json" \
  -d '{
    "inspectionUrl": "https://example.com/some-page/",
    "siteUrl": "sc-domain:example.com"
  }'

La réponse’s inspectionResult.indexStatusResult carries the verdict, coverageState, robotsTxtState, indexingState, lastCrawlTime, pageFetchState, and les deux googleCanonical and userCanonical — the même fields vous lire in the UI’s coverage panel. Comparer the two canonical fields programmatically to flag pages où Google overrode votre declared canonical.

Remarque the per-property cap: monitoring a grand site signifie batching requêtes sous 600/minute and 2 000/day, or splitting le site à travers multiple verified properties.

Outils

• Inspection d’URL (Recherche Google Console) — the outil itself; inspect un URL, run a live tester, view the crawled/testé page, and requête indexation.
• Page Indexation report (GSC) — trouver qui URLs to inspect: it groupes votre pages by index status and the raison they’re non indexée.
• Inspection d’URL API — the programmatic equivalent pour bulk index monitoring (2 000/day, 600/min per property); several third-party SEO outils wrap it.
• Search Console API / Performances report (GSC) — pair with inspection données quand building votre propre monitoring autour impressions, clicks, and indexation.

Inspection d’URL mistakes que lead to bad conclusions

Treating “URL is on Google” as a ranking vérifier

Pourquoi it fails: The verdict signifie l’URL is eligible to apparaître, pas que it is currently visible pour a requête or ranking in a particulier position.

Do à la place: Utiliser the Performances report or a réel search-result vérifier pour search visibility, and garder Inspection d’URL focused on explorer and index state.

Confusing indexé données with a live tester

Pourquoi it fails: The par défaut inspection describes the version Google dernier indexé; it peut lag behind lune page vous simplement modifié.

Do à la place: Run Tester live URL to vérifier the current récupérer, alors comparer it with the indexé view to comprendre ce que modifié and ce que Google has pas reprocessed yet.

Repeatedly clicking Requête indexation

Pourquoi it fails: The button is a crawl-queue hint with a daily limite. It ne fait pas force indexation, améliorer rankings, or faire repeated submissions traiter faster.

Do à la place: Submit une fois après the live page is ready, garder it discoverable via liens and sitemaps, and investigate quality or technical exclusion raisons si Google encore declines to index it.

Ignoring a canonical mismatch

Pourquoi it fails: Quand Google-selected canonical differs from the user-declared canonical, the inspected URL may pas be the version Google treats as authoritative. Reading seulement the headline verdict misses the la plupart actionable partie of the report.

Do à la place: Comparer canonicals, redirections, lien internes, sitemap inclusion, and contenu dupliqué à travers the cluster avant deciding si Google’s selection is incorrect.

En utilisant Inspection d’URL as a site-wide audit

Pourquoi it fails: The interface inspects un URL at a temps, and the API is quota-limited. A few hand-picked URLs ne peut pas prove an entier template or inventory is sain.

Do à la place: Utiliser lune page Indexation report and a robot d’exploration to trouver patterns, alors utiliser Inspection d’URL on representative exemples from chaque affected template and status.

Inspecting the incorrect property or URL variant

Pourquoi it fails: Inspection is limited to the verified property vous opened. Protocol, host, and URL-prefix scope peut put the target outside que property.

Do à la place: Confirmer the exact URL and property scope avant interpreting an vide, unavailable, or unexpected result.

Ressources utiles

My connexe writing

• The Beginner’s Guide to SEO technique — où Inspection d’URL fits into seeing how Google crawled, rendered, and indexé une page.
• JavaScript SEO Problèmes & Meilleur Practices — the live tester / View crawled page workflow pour debugging rendering.
• How to Supprimer URLs From Recherche Google — context pour index status vs removals.

From others

• Moteur de recherche Land — Recherche Google Console Inspection d’URL outil: practical SEO utiliser cas.
• Moteur de recherche Land — SEO outils to obtenir Inspection d’URL API insights.
• Moteur de recherche Journal — Google Announces Search Console Inspection d’URL API.
• Ahrefs — Google’s Nouveau Search Console Inspection d’URL API: Ce que c’est & Comment utiliser It.
• Moteur de recherche Roundtable — Google Dit Requête Indexation Ne fait pas Modifier Canonicalization — Barry Schwartz reporting on Google’s confirmation que Requête Indexation has aucun effect on canonical selection.

Videos

• Recherche Google Central (YouTube) — Search Console and JavaScript-SEO explainers from Martin Splitt que cover inspecting URLs and reading rendered output. Channel

Testez vos connaissances: The Inspection d’URL Outil

Five rapide questions on the Inspection d’URL outil. Pick an réponse pour chaque, alors vérifier.

Journal des modifications