Guide : Search Console API

TL;DR — The Search Console API lets vous grab votre Recherche Google Console données with code au lieu de clicking via the interface. It’s how vous obtenir plus que the UI hands vous — the export in the interface tops out autour 1 000 rows, pendant que the API donne vous up to 25 000 per requête. Vous log in with Google (OAuth, pas a simple API clé), and vous seulement obtenir données pour sites you’ve verified.

Ce que the Search Console API is

Search Console montre vous how votre site fait in Google — ce que requêtes vous rank pour, how nombreux clicks and impressions vous obtenir, si votre pages are indexé. The API donne vous programmatic accès to beaucoup of que même données and ceux même contrôle, so vous pouvez feed it into a spreadsheet, a dashboard, or a script que runs on a schedule. It’s pas complet UI parity, though — a few choses (comme live-testing une URL) seulement exist in the interface, and having API accès or automation doesn’t by itself guarantee indexation, rankings, trafic diagnosis, or AI-search visibility.

Là are four pieces:

1. Search Analytics API — votre Performances report numbers (clicks, impressions, CTR, average position), broken bas by requête, page, country, device, and date.
2. Inspection d’URL API — the index status of a unique URL. It reports the version currently in Google’s index; the interface’s Inspection d’URL outil peut aussi run a live tester, qui the API can’t do.
3. Sitemaps API — liste, submit, or delete votre sitemaps.
4. Sites API — liste, ajouter, or supprimer the properties on votre account.

Platform-property boundary: Search Console now has separate Instagram, TikTok, X, and YouTube properties, but Google’s current platform documentation describes leur interface reports and report export—pas a siteUrl identifier or prise en charge contract pour ces legacy endpoints. The API workflow in ce article therefore covers website properties seulement. LinkedIn n’est pas a pris en charge platform property.

Pourquoi utiliser it au lieu de the interface

The big un: rows. Si vous export the Performances report from the Search Console interface, vous obtenir roughly 1 000 rows. The API renvoie up to 25 000 rows per requête, and vous pouvez page via pour plus. Si you’ve got a site with thousands of requêtes or pages, the interface simply doesn’t montrer vous la plupart of votre données.

The autre raison is automation. Une fois it’s an API appel, vous pouvez run it every morning, dump it into a dashboard, or alert yourself quand clicks drop.

The catch

Vous pouvez seulement pull données pour properties you’ve verified in Search Console. Point the API at a site vous don’t propre and vous obtenir nothing back — that’s the la plupart courant beginner stumble.

And the API doesn’t give vous everything. It renvoie the top rows, pas the complet liste, and it jamais montre vous the requêtes Google anonymizes pour privacy. Pour a big site que veut the complet picture, the meilleur outil is the bulk données export to BigQuery — more on that in the Advanced version.

TL;DR — The Search Console API is four REST APIs sous webmaster-tools/v1 — Search Analytics, Inspection d’URL, Sitemaps, Sites — tout OAuth 2,0, tout scoped to verified properties seulement. Search Analytics renvoie 1–25 000 rows per requête (par défaut 1 000) but “ne fait pas guarantee to retourner tout données rows but plutôt top ones,” so pour completeness at scale vous graduate to the BigQuery bulk données export. Inspection d’URL is hard-capped at 2 000 QPD / 600 QPM per site — que arithmetic is ce que gates large-scale index monitoring.

Ce API guide is scoped to website properties. Ne faites pas assume le sites, Search Analytics, Inspection d’URL, or Sitemaps endpoints prise en charge Instagram, TikTok, X, or YouTube platform properties jusqu’à Google documents the identifier and endpoint contract.

The four APIs En un coup d’œil

Google’s propre framing of ce que the API fait: it lets vous “view, ajouter, or supprimer properties and sitemaps, run avancé requêtes pour Recherche Google results données pour the properties que vous manage in Search Console, and tester individual pages.” Que maps cleanly onto the four resources, tout sous webmaster-tools/v1:

• Search Analytics API — the Performances report, programmatically: clicks, impressions, CTR, position by dimension (requête, page, country, device, search appearance, date, hour).
• Inspection d’URL API — the index status of a unique URL, the programmatic sibling of the Inspection d’URL outil.
• Sitemaps API — liste, obtenir, submit, and delete sitemaps.
• Sites API — liste, ajouter, and supprimer verified properties.

It exposes beaucoup of ce que vous déjà utiliser in the interface — the Performances report and the Inspection d’URL outil — as endpoints vous pouvez script contre. It isn’t a 1:1 mirror, though: the API doesn’t guarantee complet UI parity (URL Inspection’s live tester, pour instance, is UI-only — voir ci-dessous), and neither API accès nor automation on its propre guarantees indexation, rankings, trafic diagnosis, or AI-search visibility.

Auth: OAuth 2,0, two scopes, verified properties seulement

There’s aucun API clé. Every appel is OAuth 2,0 — Google is explicit que “tout requêtes to the Recherche Google Console API doit be authorized by an authenticated utilisateur.” Vous register an app in Google Cloud, requête a scope, and obtenir a short-lived accès token. Two scopes exist:

• https://www.googleapis.com/auth/webmasters — lire/écrire.
• https://www.googleapis.com/auth/webmasters.readonly — read-only.

Pour server-to-server automation (a nightly reporting job, an index monitor) vous grant a service account accès to the property and skip the interactive consent flow.

Pour website properties, two property-identifier formats matter ici aussi: une URL-prefix property is réussi as a complet property URL (Google’s propre exemple is http://www.example.com/), and a Domain property uses the sc-domain:example.com formulaire — vous have to réussir whichever formulaire matches how the property is verified in Search Console. Soit façon, the service account (or utilisateur) nécessite to be granted accès to que exact property; it’s pas a bypass pour ownership or a blanket grant à travers every property on the account.

And the gate que trips everyone up: “Vous doit have appropriate accès (owner, complet, lire) to quelconque Recherche Google Console account que vous wish to accès en utilisant the API.” Appel the API pour a property you’re pas verified on and it renvoie nothing — pas an error you’ll necessarily notice, simplement vide données.

Search Analytics API — the Performances report, at scale

Commencer with the ceiling, pas the convenience: Google’s propre caveat is que “The API is bounded by internal limitations of Search Console and ne fait pas guarantee to retourner tout données rows but plutôt top ones.” Pagination extends how far vous pouvez page into que top-rows liste — it doesn’t supprimer the ceiling. Quand vous besoin every row, that’s the cue to reach pour BigQuery bulk export (ci-dessous), pas a bigger rowLimit.

Dans que ceiling, ce is encore the un la plupart personnes come pour. The raison it beats the interface is the rowLimit parameter: “[Optional; Valid range is 1–25 000; Par défaut is 1 000].” The interface export caps near 1 000 rows; the API donne vous up to 25 000 per requête, and vous paginate past que with startRow. On a site with a long tail of requêtes, that’s the difference entre seeing the top of votre données and seeing plus of it — encore pas tout of it.

Two plus choses shape ce que comes back. Premier, dataState contrôle freshness: final (the par défaut) renvoie seulement finalized données, all inclut fresh, recently collected données, and hourly_all donne hourly breakdowns que are explicitly partial — la réponse metadata flags a first_incomplete_date or first_incomplete_hour, and Google notes valeurs après que point peut encore modifier. Second, Search Analytics quotas aren’t a unique number: the usage limites page splits les into charger limites (a resource-based allowance mesuré in 10-minute and 1-day chunks — wider date ranges, plus dimensions, and heavier filtering tout draw it bas faster) and the QPS/QPM/QPD request-rate limites covered ci-dessous. Vous pouvez hit the charger ceiling avant vous hit la requête-rate ceiling.

Inspection d’URL API — and the quota que en réalité constrains vous

The Inspection d’URL API “view[s] the indexé, or indexable, status of the provided URL. Presently seulement the status of the version in the Google index is disponible; vous pouveznot tester the indexability of a live URL.” Que dernier clause is a réel scope limite, pas a technicality: the interface’s Inspection d’URL outil peut run a live tester contre lune page as it exists correct now; the API peut seulement report on the version Google déjà has indexé. Utiliser the API to construire index-coverage monitoring à travers nombreux URLs — pas as a substitute pour the UI’s live tester.

Here’s où the math matters. Per site, vous obtenir 2 000 requêtes per day and 600 per minute. (Per project the ceiling is far plus élevé — 10 000 000/day and 15 000/minute — but the per-site cap is ce que bites.) Si vous vouloir to monitor the index status of a 50 000-URL site, vous pouvez’t inspect les tout in a day; vous batch and schedule à travers days, or vous prioritize. Few posts do ce arithmetic, and it’s the unique biggest planning constraint on large-scale index monitoring.

By contrast, Search Analytics is generous — 1 200 QPM per site and per utilisateur — and the autre resources (Sitemaps, Sites) sit at 20 QPS / 200 QPM per utilisateur. URL Inspection is the tight un.

Sitemaps and Sites APIs

The Sitemaps API is the management couche pour votre sitemaps: it “submits a sitemap pour a site,” “deletes a sitemap from ce site,” “retrieves information à propos de a spécifique sitemap,” and “listes le sitemaps-entries submitted pour ce site, or inclus in le sitemap index fichier.” Le sitemap resource it renvoie inclut fields comme path, lastSubmitted, isPending, isSitemapsIndex, lastDownloaded, warnings, errors, and a contents array — handy pour auditing sitemap health at scale.

The Sites API listes, adds, and removes verified properties — utile si vous manage nombreux properties and vouloir to provision or audit les programmatically.

Quand to utiliser BigQuery bulk export à la place

Pour grand sites, the API’s 25 000-rows-per-request, top-rows-only model becomes a ceiling. Google’s réponse isn’t a fifth API resource que renvoie the même shape of données — it’s a separate, scheduled export pipeline: the bulk données export to BigQuery. Think of the choice as pull vs. scheduled push, pas “API A vs. API B.” Google’s own framing: “Schedule a daily export of votre Search Console performances données to BigQuery, où vous pouvez run complex requêtes over votre données or export it to an external storage service. En utilisant the bulk données export fonctionnalité, you’ll voir tout the performances données disponible to Search Console pour votre property, with the exception of anonymized requêtes.”

That’s the decision rule:

• Interface export — ~1 000 rows, rapide one-off regarder.
• Search Analytics API — up to 25 000 rows/requête, paginate, scriptable; great pour moderate on-demand pulls and dashboards.
• BigQuery bulk export — tout disponible performances données, daily, aucun row cap; the correct outil une fois you’ve got tens of thousands of pages or requêtes.

The un chose none of les give vous is anonymized requêtes — the terms Google hides pour privacy. That’s a réel gap, pas a bug vous pouvez fonctionner autour. I know the scale of it firsthand: as Ahrefs’ Brand Ambassador I helped surface a study où we pulled tout the données disponible from the API à travers a very grand sample of sites and trouvé Google hides the keyword term on a grand share of clicks. We plus tard construit que into Ahrefs Rank Tracker — complet history of votre GSC données, the percent of clicks going to anonymized requêtes, and a custom CTR curve construit from votre propre numbers. Quand someone indique vous the API renvoie “all your data,” que anonymized slice is the honest asterisk.

Courant utiliser cas

• Automated reporting — scheduled pulls into Sheets or a warehouse.
• BI dashboards — Looker Studio or BigQuery on top of the Performances données.
• Large-scale index/coverage monitoring — Inspection d’URL, batched dans the 2 000/day quota.
• CTR curve building — model attendu CTR by position from votre propre données.
• Anomaly alerting — flag click/impression drops automatically.

Ce is aussi how third-party outils fonctionner: quand Ahrefs or a Looker Studio connector “integrates Search Console,” they’re appel ces même APIs (and increasingly, the BigQuery export) on votre behalf.

AI summary

A condensed prendre on the Avancé version:

• The Search Console API = four REST APIs sous webmaster-tools/v1: Search Analytics (Performances données), Inspection d’URL (index status), Sitemaps, and Sites. It’s pas complet UI parity — a few choses, comme Inspection d’URL’s live tester, seulement exist in the interface, and API accès alone doesn’t guarantee indexation, rankings, or trafic diagnosis.
• Auth is OAuth 2,0, aucun API clé. Two scopes (webmasters, webmasters.readonly); service accounts pour server-to-server, but ils encore besoin explicit accès to the exact property. siteUrl takes soit a URL-prefix property or a sc-domain:example.com Domain property — match how it’s verified. The API seulement renvoie données pour properties you’ve verified — the #1 beginner gotcha.
• Search Analytics renvoie top rows premier, pas a complet dump — “ne fait pas guarantee to retourner tout données rows but plutôt top ones,” regardless of pagination. Dans que ceiling: 1–25 000 rows per requête (par défaut 1 000), vs ~1 000 in the interface export, and quotas split into charger limites and QPS/QPM/QPD request-rate limites.
• Inspection d’URL: 2 000 requêtes/day, 600/minute per site, and it reports seulement the indexé version — it can’t run a live tester. Que quota is the réel constraint on large-scale index monitoring — batch and schedule autour it.
• Sitemaps API listes/obtient/submits/deletes sitemaps; Sites API listes/adds/removes properties.
• Pour grand sites, utiliser the BigQuery bulk données export — a separate scheduled pipeline (pas a fifth API resource) giving tout disponible performances données daily, aucun row cap, except anonymized requêtes.
• Anonymized requêtes are a genuine gap aucun API or export fills — Patrick’s Ahrefs fonctionner quantified how grand que hidden slice is.

Documentation officielle

Primary-source documentation from Google.

Search Console API référence

• Search Console API — Overview / à propos de — ce que the API fait and the verified-property requirement.
• Search Analytics: requête référence — the rowLimit (1–25 000) and dimension parameters.
• Inspection d’URL API référence — ce que index-status données the inspect méthode renvoie.
• Sitemaps API référence — liste, obtenir, submit, delete.
• Sites API référence — liste, ajouter, supprimer verified properties.
• Usage limites — the complet per-site, per-user, and per-project quota table.
• Authorizing requêtes (OAuth 2,0) — scopes and the auth flow.

Bulk données export

• À propos de bulk données export (Search Console Aider) — schedule a daily BigQuery export of tout performances données except anonymized requêtes.
• Bulk données export announcement (Search Central blog) — the launch post positioning bulk export pour grand sites.

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 API fait and who peut utiliser it

• “view, add, or remove properties and sitemaps, run advanced queries for Google Search results data for the properties that you manage in Search Console, and test individual pages.” — Recherche Google Console API docs (Overview). Jump to quote
• “You must have appropriate access (owner, full, read) to any Google Search Console account that you wish to access using the API.” — Recherche Google Console API docs (Overview). Jump to quote
• “All requests to the Google Search Console API must be authorized by an authenticated user.” — Authorizing requêtes guide. Jump to quote

Google — Search Analytics API

• “[Optional; Valid range is 1–25,000; Default is 1,000]” — the rowLimit parameter. — Search Analytics: requête référence. Jump to quote
• “The URL of the property as defined in Search Console.” — the siteUrl parameter, whose exemples give les deux l’URL-prefix formulaire (http://www.example.com/) and the Domain-property formulaire (sc-domain:example.com). — Search Analytics: requête référence. Jump to quote
• “The API is bounded by internal limitations of Search Console and does not guarantee to return all data rows but rather top ones.” — Search Analytics: requête référence. Jump to quote

Google — Inspection d’URL API

• “View the indexed, or indexable, status of the provided URL. Presently only the status of the version in the Google index is available; you cannot test the indexability of a live URL.” — Inspection d’URL API référence. Jump to quote

Google — Sitemaps API

• “Submits a sitemap for a site.” / “Deletes a sitemap from this site.” / “Lists the sitemaps-entries submitted for this site, or included in the sitemap index file.” — Sitemaps API référence. Jump to quote

Google — bulk données export

• “Schedule a daily export of your Search Console performance data to BigQuery… you’ll see all the performance data available to Search Console for your property, with the exception of anonymized queries.” — Search Console Aider: À propos de bulk données export. Jump to quote

OAuth setup & first-call checklist

Getting from zero to a working Search Console API appel:

• Confirmer vous have verified accès (owner, complet, or lire) to the property in Search Console — the API renvoie nothing pour unverified properties.
• Créer a project in the Google Cloud Console.
• Enable the Search Console API pour que project.
• Créer credentials: an OAuth 2,0 client (pour interactive/utilisateur apps) or a service account (pour server-to-server automation).
• Si en utilisant a service account, grant it accès to the property in Search Console settings.
• Requête the correct scope: webmasters.readonly pour reporting, webmasters si you’ll submit sitemaps or manage properties.
• Obtain an accès token via the OAuth flow (or service-account clé).
• Confirmer the siteUrl format matches how the property is verified: a complet URL pour une URL-prefix property, or sc-domain:example.com pour a Domain property.
• Faire a tester appel to searchAnalytics.query with a petit date range and rowLimit: 10 to confirmer données comes back.
• Plan autour quotas: Search Analytics requête rates are generous but aussi draw bas a separate charger quota; Inspection d’URL is capped at 2 000/day, 600/min per site — batch accordingly. Don’t expect URL Inspection to run a live tester — that’s UI-only.
• Pour tens of thousands of rows, définir up the BigQuery bulk export à la place of paginating.

The mental models

1. Four APIs, un auth. Search Analytics (lire votre Performances données), Inspection d’URL (lire une URL’s index status), Sitemaps (manage sitemaps), Sites (manage properties). Tout four go via the même OAuth 2,0 door and respect the même verified-property rule.

2. The data-scale ladder. Pick the outil by volume:

• Rapide regarder → interface export (~1 000 rows).
• Scriptable, moderate → Search Analytics API (up to 25 000/requête, paginate).
• Grand site, complet → BigQuery bulk export (tout données, daily, aucun row cap). Déplacer up the ladder quand the rung ci-dessous arrête fitting votre données.

3. Top rows, pas tout rows. Internalize que the API renvoie “top ones,” pas everything, and que anonymized requêtes are excluded from les deux the API and the export. Si completeness matters, BigQuery is closer — but the anonymized slice is gone regardless.

4. Quota arithmetic avant vous construire. Avant designing an index monitor, do the math: Inspection d’URL is 2 000/day per site. A 50k-URL site can’t be inspected daily — so batch, prioritize, or schedule à travers days. Design autour the cap, don’t découvrir it in production.

Search Console API — cheat sheet

The four APIs and leur clé limites

Auth

• OAuth 2,0 seulement — aucun API clé.
• Scopes: webmasters (lire/écrire), webmasters.readonly (lire).
• Service accounts pour server-to-server (grant les property accès).
• Seulement verified properties retourner données.

Fast facts

• API renvoie top rows seulement — pas guaranteed complet — regardless of pagination.
• Interface export caps near 1 000 rows; API donne up to 25 000/requête, paginate with startRow.
• Search Analytics quotas split into charger limites (resource-based, 10-min / 1-day chunks) and the QPS/QPM/QPD request-rate limites ci-dessus.
• siteUrl takes une URL-prefix property (http://www.example.com/) or a Domain property (sc-domain:example.com) — match how it’s verified.
• Inspection d’URL reports the indexé version seulement — it can’t run a live tester; that’s UI-only.
• Anonymized requêtes are excluded from the API and the BigQuery export.
• Pour tens of thousands of rows → BigQuery bulk données export — a separate scheduled pipeline, pas a fifth API resource.
• Exposes beaucoup of the Performances report (Search Analytics) and the URL Inspection outil, but isn’t complet UI parity.

A minimal Search Analytics requête

Ce is illustrative, pas copy-paste-ready — you’ll besoin to wire up votre propre OAuth credentials and adjust the dates and property. It montre the shape of a searchAnalytics.query appel: the corps de la requête with a date range, the dimensions vous vouloir, and the rowLimit.

The corps de la requête (the partie que matters)

{
  "startDate": "2026-05-01",
  "endDate": "2026-05-31",
  "dimensions": ["query", "page"],
  "rowLimit": 25000,
  "startRow": 0
}

Sketch in Python (with the google-api-python-client library)

# Illustrative only — assumes you've already built an authorized `service`
# via OAuth 2.0 (scope: webmasters.readonly) or a service account.
from googleapiclient.discovery import build

service = build("searchconsole", "v1", credentials=creds)

request = {
    "startDate": "2026-05-01",
    "endDate": "2026-05-31",
    "dimensions": ["query", "page"],
    "rowLimit": 25000,   # max per request; default is 1000
    "startRow": 0,       # bump by 25000 to paginate
}

response = service.searchanalytics().query(
    siteUrl="https://example.com/",  # URL-prefix property; use "sc-domain:example.com"
                                      # instead for a Domain property — must be verified
    body=request,
).execute()

for row in response.get("rows", []):
    print(row["keys"], row["clicks"], row["impressions"])

To go past 25 000 rows, loop and increment startRow by 25 000 jusqu’à une requête renvoie aucun rows. Remember le résultat is encore “top rows,” pas a complet dump — pour que, utiliser the BigQuery bulk export.

Outils que utiliser (or wrap) the Search Console API

• Google Cloud Console — où vous créer the project, enable the API, and mint OAuth/service-account credentials.
• Official client libraries — Google API client libraries pour Python, Java, JavaScript/Node, PHP, and .NET wrap the REST calls.
• BigQuery — the destination pour the bulk données export; requête tout votre performances données with SQL.
• Looker Studio — connects to Search Console (and BigQuery) pour dashboards construit on the même données.
• Ahrefs — integrates the Search Console API; its Rank Tracker montre complet GSC history, the share of clicks going to anonymized requêtes, and a custom CTR curve from votre propre données.
• Search Console interface — the Performances report and Inspection d’URL outil are the manual counterparts to the Search Analytics and Inspection d’URL APIs, with un gap the API can’t fermer: seulement the interface outil peut run a live tester on une URL.

Prompts pour planning Search Console API fonctionner

Utiliser ces prompts to shape code or an analysis plan. Garder credentials, refresh tokens, and service-account keys out of quelconque chat input.

Design a Search Analytics requête

Paste votre property URL, date range, dimensions, filters, and reporting goal.

Design a Google Search Console Search Analytics API request for the following reporting task.

Property: [sc-domain:example.com or exact URL-prefix property]
Date range: [start and end]
Goal: [the question the report must answer]
Dimensions: [date, query, page, country, device, searchAppearance, or hour]
Filters: [include/exclude rules]

Return:
1. The request body, including a rowLimit no higher than 25,000.
2. Pagination logic using startRow.
3. The aggregation and grouping needed after retrieval.
4. Warnings about top-rows-only data and anonymized queries.
5. A small validation query I can run before scheduling the full pull.

Do not invent credentials or assume the result is a complete census.

Plan a quota-safe Inspection d’URL schedule

Paste a CSV summary or counts by URL priority plutôt que confidential tokens.

Create a quota-safe sampling and scheduling plan for the Search Console URL Inspection API.

Property: [property]
Total URLs: [count]
Priority groups: [critical templates, new URLs, changed URLs, long-tail sample]
Required revisit cadence: [daily, weekly, monthly]

Constraints from this article:
- 2,000 inspection queries per day per site.
- 600 inspection queries per minute per site.
- The API reports the indexed version, not a live test.

Return a daily allocation by priority group, a rotation method, retry/backoff rules,
and alerts for unexpected index or canonical states. Explain what cannot fit inside
the quota instead of silently dropping it.

Choisir API versus BigQuery export

Help me choose between the Search Console interface, Search Analytics API, and BigQuery bulk export.

Reporting need: [one-off analysis, dashboard, warehouse, anomaly alerts]
Expected rows per day: [estimate]
History required: [range]
Refresh cadence: [cadence]
Dimensions needed: [list]
Infrastructure available: [spreadsheet, script runner, BigQuery, BI tool]

Compare setup cost, row/completeness limits, automation, and maintenance. Account for
the API returning top rows and for anonymized queries being absent from every path.
End with one recommendation and the smallest proof-of-concept to validate it.

Ressources utiles

My connexe fonctionner

• Ahrefs blog — my posts — notamment the fonctionner on GSC données at scale and anonymized requêtes.
• Now in Ahrefs Rank Tracker: complet GSC history + anonymized-query share — the CTR-curve and GSC-history fonctionnalité I announced.

Google’s docs

• Search Console API overview and the usage limites page — the two pages to bookmark premier.
• À propos de bulk données export — quand and how to déplacer to BigQuery.

From others

• Hidden keywords in GSC — the Ahrefs study (Moteur de recherche Journal coverage) — third-party write-up of the anonymized-query findings.
• Enhanced Search Console analytics with BigQuery (SEJ) — a practical regarder at the bulk-export chemin.
• Bulk données export: a nouveau and powerful façon to accès votre Search Console données (Recherche Google Central blog) — the Feb 2023 launch post from the Search Console team positioning bulk export pour grand sites.
• google-api-python-client (PyPI) — the official Python client library utilisé to appel the Search Console API; aussi disponible pour Node, Java, PHP, and .NET via the Google APIs client library family.
• r/TechSEO — the community pour API and data-pull troubleshooting.

Stats worth citing

• Search Analytics row limite: 25 000 per requête (par défaut 1 000) — versus the interface export’s ~1 000-row cap. Ce is the core raison to utiliser the API. Source
• Inspection d’URL quota: 2 000 requêtes/day and 600/minute per site — the hard ceiling on large-scale index monitoring (10M/day, 15 000/min per project). Source
• Anonymized requêtes are excluded from même the la plupart complet chemin (BigQuery bulk export) — a réel, unavoidable gap in votre requête données. Source
• Google hides the keyword term on a grand share of clicks — from the Ahrefs study I helped surface, qui pulled tout disponible données from the API à travers a very grand sample of sites. Coverage

Testez vos connaissances: Search Console API

Five rapide questions on the APIs, authentication, données limites, and scale. Pick an réponse pour chaque, alors vérifier votre result.

Journal des modifications