Google Indexation API

TL;DR — The Google Indexation API is a façon pour site owners to tell Google “this page changed, please re-crawl it” via code au lieu de clicking buttons. But here’s the catch la plupart guides skip: Google seulement officially supports it pour job-posting pages and livestream pages. It is pas a shortcut to obtenir votre blog posts or product pages indexé faster — Google has said so over and over.

Ce que the Indexation API is

Quand vous publish or modifier une page, vous normally wait pour Google to come back and re-crawl it on its propre schedule. The Indexation API is a façon to push a notification to Google à la place — “hey, this URL is new/updated” or “ce URL is gone, drop it.” Vous do it with code (a petit program appel Google’s servers), pas by clicking autour in a dashboard.

Que sounds powerful, and it is — pour the exact choses it’s construit pour.

The un chose to comprendre

Google seulement officially supports the Indexation API pour two kinds of pages:

1. Job postings — pages with JobPosting données structurées (job listings, qui expire and besoin to come bas quickly).
2. Livestreams — pages with BroadcastEvent données structurées (live video events, qui seulement matter during the broadcast).

That’s it. Les deux are time-sensitive content que goes stale fast, qui is pourquoi Google construit a fast lane pour les.

Si vous don’t have job listings or livestreams, the Indexation API n’est pas votre outil — aucun matter ce que a “get indexed in hours” plugin or SaaS indique vous.

The myth to ignore

The unique biggest myth online is: “Utiliser the Indexation API to obtenir quelconque page indexé fast.” It doesn’t fonctionner que façon, and Google has repeatedly appelé en utilisant it pour normal pages misuse. Personnes do it anyway parce que outils sell it as a growth hack — but Google peut (and dit it va) revoke votre accès pour abusing it.

There’s a second trap, aussi: quand vous submit une URL and obtenir a “success” réponse, que seulement signifie Google reçu votre requête. It fait pas mean lune page got indexé. Plenty of outils blur que line; Google’s propre docs are clair à propos de it.

Que faire à la place pour faster indexation

Pour regular pages (blogs, products, articles), the choses que en réalité aider are boring but réel:

• Submit an XML sitemap dans la recherche Google Console.
• Lien to votre nouveau pages from autre pages on votre site.
• Faire lune page genuinely worth indexation (quality, pas thin filler).
• Pour a one-off, utiliser “Request indexing” in Search Console’s Inspection d’URL outil — sparingly.

Vouloir the technical version — setup, the réel API méthodes, quotas, and the exact Google quotes? Switch to the Avancé tab.

TL;DR — The Indexation API is a Google Cloud–authenticated REST API (v3) que accepts URL_UPDATED and URL_DELETED notifications. Google officially supports it seulement pour JobPosting and BroadcastEvent-in-VideoObject (livestream) pages — pas general content. A 200 from the status endpoint confirms receipt, pas indexation. Google’s stance has hardened over années: 2022 (“doesn’t faire sense”) → Sept 2024 (a spam warning ajouté to the docs) → May 2025 (Mueller: “spammers misuse the Indexing API… use it properly, or not use it”). Misuse, notamment multiple accounts to inflate quota, peut obtenir accès revoked. Pour general pages, votre levers are sitemaps, lien internes, quality, and occasional GSC “Request indexing” — and remember Google fait pas prise en charge IndexNow.

Ce que the Indexation API en réalité is

The Indexation API is a programmatic push channel: a REST API (v3), authenticated via a Google Cloud service account, que vous appel to tell Google une URL was ajouté/mis à jour (URL_UPDATED) or devrait be supprimé (URL_DELETED). It sits alongside sitemaps and Search Console as a façon pour Google to découvrir and refresh URLs — but it’s the narrowest of the bunch by content type.

In my How Search Fonctionne deck, I liste the Indexation API as une URL-discovery source with the tag “limited use cases” — qui is the whole story in two words. It’s réel, it fonctionne, and it’s seulement sanctioned pour a sliver of the web.

Ce que Google officially supports it pour

Ce is the load-bearing fact, so I’ll state it the façon Google fait. The Indexation API “peut seulement be utilisé to explorer pages with soit JobPosting or BroadcastEvent embedded in a VideoObject.” That’s it — two structured-data types:

• JobPosting — job-listing pages. Ils expire, and stale jobs are a bad utilisateur experience, so timely ajouter/supprimer matters.
• BroadcastEvent in a VideoObject — livestream event pages. They’re seulement relevant during (and simplement autour) the broadcast.

Pourquoi seulement ces two? Les deux are inherently time-sensitive and short-lived. The rationale Google donne is que fast notification of changements matters far plus pour ces que pour evergreen pages, qui the normal explorer handles fine.

Comment cela fonctionne

Prerequisites

Setup is non-trivial — ce isn’t a one-click fonctionnalité:

• A Google Cloud project with the Indexation API enabled. As Google puts it, vous “need to tell Google about your client and activate access to the API.”
• A service account with a JSON clé fichier, stored securely.
• Search Console verification of le site, alors ajouter votre service account as a delegated site owner.
• OAuth: “Every appel to the Indexation API doit be authenticated with an OAuth token que vous obtenir in exchange pour votre private clé,” en utilisant the scope https://www.googleapis.com/auth/indexing.

The two méthodes (plus a status vérifier)

• URL_UPDATED — “To notify Google of a nouveau URL to explorer or que content at a previously-submitted URL has been mis à jour.” POST l’URL with "type": "URL_UPDATED". A successful appel obtient an HTTP 200 — Google’s propre wording is que ce “means that Google may try to recrawl this URL soon,” pas que it va, or que the explorer va result in indexation.
• URL_DELETED — avant vous requête removal, Google exige que “l’URL doit retourner a 404 or 410 code d’état or lune page doit contain” a noindex meta tag — it’s an soit/or, pas “delete the page and also add noindex.” Une fois that’s vrai, POST l’URL with "type": "URL_DELETED" so Google drops it.
• Status (GET) — renvoie metadata (latest_update, latest_remove, notify_time). The critical caveat, verbatim: the GET requête “seulement renvoie si vous successfully submitted une requête.” It fait pas tell vous si Google en réalité indexé or supprimé anything.
• Batching — to cut bas on HTTP connections, vous pouvez “combine up to 100 calls to the Indexation API into a unique HTTP requête.” Quota is encore counted per URL: 10 requêtes in un batch encore uses 10 requêtes of quota.

Quotas

Google’s par défaut quota has three separate dimensions, pas simplement un number:

• 200 publish requêtes/day per project — covers les deux URL_UPDATED and URL_DELETED calls combined. Ce is the number la plupart guides cite.
• 180 getMetadata (status) requêtes/minute per project.
• 380 requêtes/minute per project à travers tout endpoints combined.

Tout three are décrit as “initial default quota for testing” — going au-delà les “requires additional approval for usage and resource provisioning,” via a requête formulaire, and Google notes “the quota may augmenter or decrease fondé on the document quality.” The common “hack” of spinning up multiple service accounts or projects to inflate the daily quota is exactly ce que Google forbids (voir ci-dessous).

Peut vous utiliser it pour normal pages? Ce que Google en réalité dit

Short réponse: aucun, pas in a pris en charge façon — and Google has been remarkably consistent and increasingly blunt à propos de it.

The docs carry a spam warning. Autour September 2024, Google ajouté language to the quickstart making the stance explicit: “Tout submissions via the Indexation API undergo rigorous spam detection,” and “quelconque attempts to abuse the Indexation API, notamment the utiliser of multiple accounts or autre signifie to exceed usage quotas, may result in accès being revoked.”

The reps have said it pour années. Back in May 2022, John Mueller framed it with his construction-vehicles analogy: the API “is meant pour very spécifique kinds of content,” and using it elsewhere “doesn’t really faire sense.” By May 2025 the tone was sharper — Mueller: “We voir a lot of spammers misuse the Indexation API comme ce, so I’d recommend simplement sticking to the documented & pris en charge use-cases,” and “I’d simplement utiliser it correctement, or pas utiliser it. Si we wanted to suggest que personnes pourrait utiliser it regardless, we’d document it as tel.”

Que arc — 2022 “doesn’t make sense” → 2024 spam warning in the docs → 2025 “spammers misuse… use it properly or not use it” — is a multi-year pattern, pas a one-off. Coverage has aussi noted the API obtient effectively inundated by bloggers and SEOs treating normal sites as si ils qualified.

The réel risk, stated precisely. Mueller arrête short of promising an algorithmic penalty. The honest framing is: it’s unsupported and contre the guidelines, content pushed in improperly may pas stay indexé, and votre accès peut be revoked. Don’t overstate it as a guaranteed manual action — but don’t pretend it’s free, soit.

The status-endpoint myth

Ce un deserves its propre line parce que so nombreux outils obtenir it incorrect: a successful submission is receipt confirmation, pas an indexation promise. The status GET “only returns whether you successfully submitted a request.” Si a dashboard montre vous a green “indexed” badge off the back of a 200, it’s inferring something the API jamais told it.

Indexation API vs Requête Indexation vs IndexNow

Three choses obtenir conflated constantly. They’re différent mechanisms:

• Indexation API (Google): programmatic, but content-restricted to JobPosting/BroadcastEvent. The narrowest of the three.
• Requête Indexation (GSC Inspection d’URL): fonctionne pour quelconque page vous propre, but it’s manual, un URL at a temps, and meant pour occasional utiliser — and it’s a requête, pas a guarantee.
• IndexNow: the ouvrir, cross-engine push protocol (Bing, Yandex, Yep, Seznam, Naver) — and Google ne fait pas utiliser it. It’s the cross-engine analog to the Indexation API, and the un I en réalité champion: I helped ship the IndexNow integration in Ahrefs Site Audit. But it doesn’t reach Google.

(Complet breakdown in the Frameworks tab.)

Que faire à la place pour general pages

Si you’re pas posting jobs or livestreams, the Indexation API n’est pas votre outil, and Google has said so repeatedly. Votre réel Google levers are the unglamorous ones:

• Sitemaps — pour coverage and discovery.
• Lien internes — orphan pages struggle; lié pages obtenir trouvé.
• Content quality — Google decides what’s worth indexation; thin pages stall at “Discovered – currently not indexed” aucun matter how hard vous push les.
• GSC “Request indexing” — pour genuine one-offs, sparingly.

Pour cross-engine pushing (Bing and friends, pas Google), IndexNow is the correct outil. And si vous care à propos de pourquoi pages aren’t getting indexé in the premier placer, that’s a crawl-frequency and quality question, pas an API question.

AI summary

A condensed prendre on the Avancé version:

• Ce que c’est: a Google Cloud–authenticated REST API (v3) pour pushing URL_UPDATED / URL_DELETED notifications to Google.
• The un fact que matters: officially pris en charge seulement pour JobPosting and BroadcastEvent (livestream) pages — pas general content. Les deux are time-sensitive by design.
• The #1 myth: “it indexes any page fast.” It doesn’t; Google calls broader utiliser misuse. A successful submission seulement confirms Google reçu la requête, pas que anything was indexé.
• Google’s stance hardened over temps: 2022 “doesn’t make sense” → Sept 2024 spam warning ajouté to the docs → May 2025 Mueller “spammers misuse… utiliser it correctement, or pas utiliser it.”
• Risk: unsupported/contre guidelines; multiple accounts to beat the ~200/day quota peut obtenir accès revoked. Pas necessarily a manual penalty — but content may pas stick.
• Pas the même as IndexNow (cross-engine, Bing/Yandex/etc. — Google doesn’t utiliser it) or GSC Requête Indexation (quelconque page, manual, occasional).
• Pour normal pages: sitemaps + lien internes + quality + occasional GSC Requête Indexation.

Documentation officielle

Primary-source documentation from Google.

Google — Indexation API

• Indexation API Quickstart — the overview, the JobPosting/BroadcastEvent restriction, and the spam-detection warning.
• Comment utiliser the Indexation API — the URL_UPDATED / URL_DELETED méthodes and the status-endpoint caveat.
• Prerequisites — Cloud project, service account, OAuth scope, and Search Console delegated ownership.
• Quota and pricing — the par défaut quota (200) and the approval nécessaire pour plus.

Google — context pour general pages

• Demander Google to recrawl votre URLs — sitemaps and the Search Console “Request indexing” chemin pour normal content.
• In-Depth Guide to How Recherche Google Fonctionne — où URL discovery and the explorer → index → serve pipeline fit.

Quotes from the source

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

Google docs — the restriction

• “The Indexing API can only be used to crawl pages with either JobPosting or BroadcastEvent embedded in a VideoObject.” — Recherche Google Central, Indexation API Quickstart. Jump to quote
• “The Indexing API allows site owners to directly notify Google when their job posting or livestreaming video pages are added or removed.” Jump to quote

Google docs — the spam warning (ajouté to the documentation autour September 2024)

• “All submissions through the Indexing API undergo rigorous spam detection.” Jump to quote
• “Any attempts to abuse the Indexing API, including the use of multiple accounts or other means to exceed usage quotas, may result in access being revoked.” Jump to quote

Google docs — the status-endpoint caveat (myth-buster)

• “The GET request doesn’t tell you when Google indexes or removes a URL; it only returns whether you successfully submitted a request.” — Recherche Google Central, Comment utiliser the Indexation API. Jump to quote

Google docs — quota

• “The default value is set to 200.” (publish requêtes/day) — Recherche Google Central, quota & pricing. Jump to quote
• “The default value is set to 180.” (getMetadata status requêtes/minute) and “The default value is set to 380.” (tout endpoints/minute) — the two autre quota dimensions la plupart guides skip. Jump to 180 · Jump to 380
• “The quota may increase or decrease based on the document quality.” — Recherche Google Central, quota & pricing. Jump to quote

Google docs — batching and removal

• “…vous pouvez combine up to 100 calls to the Indexation API into a unique HTTP requête.” — Recherche Google Central, Comment utiliser the Indexation API. Jump to quote
• “…l’URL doit retourner a 404 or 410 code d’état or lune page doit contain” a noindex meta tag — avant requesting removal. — Recherche Google Central, Comment utiliser the Indexation API. Jump to quote
• “An HTTP 200 response means that Google may try to recrawl this URL soon.” — Recherche Google Central, Comment utiliser the Indexation API (on URL_UPDATED). Jump to quote

John Mueller, Recherche Google Advocate — Bluesky, ~May 2025

• “We see a lot of spammers misuse the Indexing API like this, so I’d recommend just sticking to the documented & supported use-cases.”
• “I’d just use it properly, or not use it. If we wanted to suggest that people could use it regardless, we’d document it as such.” Lire the coverage

John Mueller, Google — SEO office-hours, May 2022 (the “construction vehicles” framing)

• “The indexing API is meant for very specific kinds of content. And using it for other kinds of content doesn’t really make sense.”
• “It’s not that it’s illegal or that it will cause problems if you put construction vehicles on your medical website. But it doesn’t really make sense.” Lire the coverage

Indexation API — cheat sheet

Pris en charge utiliser cas (ce is the whole liste)

The two méthodes

Batching: combine up to 100 calls into un HTTP requête — quota encore counts per URL, pas per batch.

Fast facts

• Par défaut quota has three parts: 200 publish requêtes/day, 180 status (getMetadata) requêtes/minute, 380 requêtes/minute à travers tout endpoints. Quota au-delà que nécessite Google’s approval and peut shift with document quality.
• 200 ≠ indexé. A success réponse confirms submission reçu, nothing plus.
• Multiple accounts to beat the quota = accès revoked (per the docs).
• Auth: Google Cloud project + service account + OAuth, scope https://www.googleapis.com/auth/indexing, service account ajouté as a GSC delegated owner.
• Pas IndexNow (cross-engine, pas Google). Pas a replacement pour sitemaps or GSC Requête Indexation.

A minimal publish appel (pour pris en charge content seulement)

Ce is the shape of a unique URL_UPDATED notification. Seulement utiliser it pour pages with JobPosting or BroadcastEvent données structurées — that’s ce que the API is sanctioned pour. The auth step (exchanging votre service-account clé pour an OAuth token) is omitted pour brevity; En pratique you’d utiliser a Google API client library to obtenir the token.

La requête

POST https://indexing.googleapis.com/v3/urlNotifications:publish
Authorization: Bearer <OAUTH_TOKEN>
Content-Type: application/json

{
  "url": "https://example.com/jobs/senior-seo-analyst",
  "type": "URL_UPDATED"
}

To signal a removal (après lune page is gone or noindexed):

{
  "url": "https://example.com/jobs/senior-seo-analyst",
  "type": "URL_DELETED"
}

Checking status — remarque la réponse indique vous seulement que la requête was reçu, pas si anything was indexé:

GET https://indexing.googleapis.com/v3/urlNotifications/metadata?url=https%3A%2F%2Fexample.com%2Fjobs%2Fsenior-seo-analyst
Authorization: Bearer <OAUTH_TOKEN>

A 200 ici signifie “we got your submission” — it is pas a confirmation que Google indexé (or supprimé) l’URL.

Batching multiple URLs: vous pouvez combine up to 100 individual calls into a unique multi-part HTTP requête to https://indexing.googleapis.com/batch au lieu de firing 100 separate requêtes — but quota is encore counted per URL, so a 100-appel batch encore uses 100 requêtes of votre daily allowance. Google’s API client libraries (Java, Python, JavaScript, PHP, .NET) handle the batch formatting pour vous; hand-rolling it is rarely worth it.

Indexation API vs Requête Indexation vs IndexNow

The decision framework: figure out ce que vous have and qui engine vous care à propos de, alors pick the channel.

How to choisir

1. Got job postings or livestreams, and vouloir to automate? → Indexation API.
2. Vouloir to push general pages to Bing/Yandex/Yep? → IndexNow.
3. Vouloir Google to recrawl un normal page, une fois? → GSC “Request indexing.”
4. Vouloir general pages indexé at scale on Google? → There’s aucun push button. Sitemaps + lien internes + quality. (And patience — voir explorer frequency.)

The mental model: the Indexation API sounds comme the la plupart powerful of the three parce que it’s an API, but by content type it’s the narrowest. Power and scope aren’t the même chose.

Outils

• Google Cloud Console — créer the project, enable the Indexation API, and generate the service-account JSON clé you’ll authenticate with.
• Recherche Google Console — Inspection d’URL — pour normal pages, ce is votre réel outil: vérifier how une URL was crawled/rendered/indexé, and utiliser “Requête indexation” pour occasional one-offs.
• Recherche Google Console — Sitemaps & Coverage — submit sitemaps and voir what’s indexé, “Discovered – currently not indexed,” or excluded.
• Google API client libraries — the cleanest façon to handle the OAuth token-exchange pour Indexation API calls (plutôt que hand-rolling JWT signing).
• IndexNow integration (Ahrefs Site Audit, etc.) — pour the cross-engine push channel (Bing and others, pas Google). The correct outil quand vous vouloir the programmatic-push behavior personnes wish the Indexation API gave les pour general pages.

Ressources utiles

My connexe writing

• Ce que Is Googlebot & How Fait It Fonctionner? — où the Indexation API sits among Google’s URL-discovery sources (liens, sitemaps, RSS, GSC, and the API).
• Comment corriger “Discovered – currently not indexed” — the réel “why won’t my pages index” page; the fix is quality and lien internes, pas a push API.
• The Beginner’s Guide to SEO technique — où exploration and indexation fit in the bigger picture.

My speaking

• How Search Fonctionne (SlideShare) — my walkthrough of discovery, exploration, rendering, indexation, and ranking; l’URL-discovery slide tags the Indexation API “limited use cases.” (My standing disclaimer s’applique: “This is my understanding of systems… not going to be 100% complete or accurate.”)

On IndexNow (the cross-engine sibling — remarque Google fait pas utiliser it)

• IndexNow integration in Ahrefs Site Audit — the push channel I en réalité endorse, pour Bing/Yandex/Yep plutôt que Google.
• How to submit pages to IndexNow dans Site Audit.

From others

• Google Adds Spam Warning To Indexation API Documentation (Moteur de recherche Journal, Sept 2024) — documents quand the spam-detection language went in.
• Google À nouveau Dit Arrêter En utilisant Indexation API Pour Unsupported Content (Moteur de recherche Roundtable, May 2025) — Barry Schwartz covers Mueller’s Bluesky warning to arrêter misusing the API.
• Misuse of Indexation API Pourrait Lead to SEO Problèmes (StanVentures, May 2025) — reproduces Mueller’s May 2025 Bluesky quotes verbatim and explique the access-revocation risk.
• Google Réponses Si En utilisant the Indexation API pour a Normal Website Is Bon or Bad (iLoveSEO, May 2022) — transcript of Mueller’s “construction vehicles” office-hours framing.
• Google Dit Its Indexation API Is Inundated by Bloggers (Optimixed) — covers how off-label utiliser by bloggers and SEOs has overwhelmed the API.
• r/TechSEO — the community pour explorer/index debugging.

Courant problèmes

Problems personnes en réalité run into with the Indexation API, in symptom → causer → fix order.

”I got a 200 response but the page still isn’t indexed”

• Symptom: The URL_UPDATED appel (or the status GET) renvoie success, but lune page jamais montre up in search, or Search Console encore dit “Découvert – currently non indexée.”
• Causer: A 200 seulement confirms Google reçu the notification. Per Google’s propre docs, the status endpoint “seulement renvoie si vous successfully submitted une requête” — it doesn’t tell vous si anything was crawled, indexé, or supprimé.
• Fix: Arrêter treating the API réponse as an indexation confirmation. Vérifier réel indexation status in the Inspection d’URL outil in Search Console, or the Coverage report. Si lune page encore isn’t indexé après a reasonable wait, the problème is discovery/quality (voir “What to do instead” in the Avancé tab), pas the API appel.

”My Indexing API access got revoked”

• Symptom: Calls que utilisé to fonctionner commencer failing, or Google Cloud/Search Console montre the service account’s accès has been pulled.
• Causer: Google states plainly que “quelconque attempts to abuse the Indexation API, notamment the utiliser of multiple accounts or autre signifie to exceed usage quotas, may result in accès being revoked.” The la plupart courant trigger is submitting non-JobPosting/non-BroadcastEvent pages, or spinning up supplémentaire service accounts to obtenir autour the ~200/day par défaut quota.
• Fix: Audit ce que you’ve been submitting — si it’s general content (blog posts, product pages, anything sans JobPosting or BroadcastEvent données structurées), arrêter. The API n’est pas documented to prise en charge it, and Mueller has said directement: “I’d just use it properly, or not use it.” There’s aucun documented appeal chemin au-delà staying à l’intérieur the pris en charge utiliser cas going forward.

”Submissions for normal pages don’t seem to do anything”

• Symptom: Vous submit URL_UPDATED pour a regular article or product page and nothing changements — aucun faster explorer, aucun faster indexation.
• Causer: Le contenu type isn’t un of the two Google supports. The Indexation API “peut seulement be utilisé to explorer pages with soit JobPosting or BroadcastEvent embedded in a VideoObject.” Submissions outside que scope aren’t a documented, pris en charge signal.
• Fix: Ce isn’t a bug to fix — it’s the incorrect outil. Pour general pages, utiliser a sitemap, lien internes, and (pour occasional one-offs) “Request indexing” in Search Console’s Inspection d’URL outil à la place.

”I’m hitting the quota limit”

• Symptom: Submissions commencer failing or getting throttled — soit autour 200/day, or En brefer bursts même sous 200/day.
• Causer: Google en réalité enforces three separate par défaut quotas: 200 publish (URL_UPDATED/URL_DELETED) requêtes per day, 180 status (getMetadata) requêtes per minute, and 380 requêtes per minute à travers tout endpoints combined. A burst of status checks peut throttle vous on the per-minute limites bien avant vous hit the daily 200. Going au-delà quelconque of ces “exige additional approval pour usage and resource provisioning,” and Google notes the granted quota “may increase or decrease based on the document quality.”
• Fix: Si you’re legitimately publishing/updating que nombreux JobPosting or BroadcastEvent pages a day, requête a quota augmenter via Google Cloud — don’t créer supplémentaire service accounts or projects to fonctionner autour it, since that’s explicitly named as the kind of abuse que obtient accès revoked.

Checklists

Avant vous touch the Indexation API

• Confirmer lune pages vous vouloir to submit en réalité carry JobPosting données structurées, or BroadcastEvent embedded in a VideoObject — the seulement two content types Google supports.
• Si neither s’applique, arrêter ici. Utiliser sitemaps, lien internes, content quality, and occasional GSC “Request indexing” à la place — pas the API.
• Decide si votre submission volume va realistically fit à l’intérieur the par défaut ~200/day quota, or si you’ll besoin to requête an augmenter.

Setting it up

• Créer (or choisir) a Google Cloud project and enable the Indexation API in it.
• Créer a service account and download its JSON clé fichier; store it securely (jamais commit it to a public repo).
• Vérifier votre site in Search Console si it isn’t déjà.
• Ajouter the service account’s email as a delegated site owner in Search Console.
• Confirmer vous pouvez exchange the service-account clé pour an OAuth token with scope https://www.googleapis.com/auth/indexing (typically via a Google API client library plutôt que hand-rolled JWT signing).

Submitting a notification

• Pick the correct méthode: URL_UPDATED pour a nouveau or modifié pris en charge page, URL_DELETED après lune page is gone or noindexed.
• POST l’URL with the correct type field to https://indexing.googleapis.com/v3/urlNotifications:publish.
• Treat a 200 réponse as receipt confirmation seulement — pas proof the page was indexé or supprimé.
• Follow up in Search Console (Inspection d’URL or Coverage) si vous devez confirmer réel indexation status.

Staying à l’intérieur the guidelines

• Seulement submit JobPosting/BroadcastEvent pages via ce API — nothing sinon.
• Don’t créer multiple service accounts or projects simplement to exceed the quota; requête a legitimate augmenter à la place.
• Si you’re pas certain si une page qualifies, treat que as “it doesn’t” and utiliser sitemaps/lien internes/Requête indexation pour it à la place.

Quiz

Five questions to vérifier ce que en réalité stuck à propos de the Indexation API.

Journal des modifications