how a call runs
what it reaches
Search Console API
server to server · straight to the platform’s API
access granted once · OAuth · scoped to this account
no browser session · no password sharing · no scraping
what you get
read-only by default · Every question is answered without touching the property. Submitting a site map is a separate, deliberate step with its own guards and its own record.
scoped on purpose · It reads organic search and nothing else, so it adds to the analytics server instead of overlapping it. One question, one server.
a blank list means nobody · An empty list of permitted properties denies everything rather than allowing everything. A wrong configuration reaches nothing.
| tool | type of access | what it does | why it exists |
|---|---|---|---|
| queries.pull | reads only | pulls clicks and impressions per search term | demand as Google records it |
| pages.pull | reads only | shows which pages earn search traffic | the pages that carry organic demand |
| index.status | reads only | reports pages in the index and pages that fell out | pages that quietly left the index |
| crawl.issues | reads only | lists what Google could not read | what Google could not read, before rankings show it |
| core_web.read | reads only | reads page experience as search measures it | page experience as search scores it |
| sitemap.submit | adds new | hands Google the site map once you approve | tells Google what changed instead of waiting for it to notice |
covers
All 10 active methods of the Search Console API v1: search analytics, sitemaps, sites and URL inspection. The eleventh method in the vendor's list was retired by Google in 2023 and is not covered.
how it operates · alone, or with the rest of the fleet
alone
a weekly organic ledger with zero hand-sampling
01
you ask · “Did organic move last week, or only paid?”
02
it picks · the query read and the page read · reads only
03
comes back · clicks and impressions per search term, and the pages that earn them
04
lands · organic separated from paid, in one plain answer
with Google Ads
Paid and organic clicks are read from their own records and kept apart. When traffic moves, the two are set side by side, so an organic loss is not hidden behind a paid gain, and a paid gain is not credited to organic.
01
you ask · “Traffic fell. Was it organic, paid, or both?”
02
it picks · the query read in Search Console and the campaign-results read in Google Ads, same window · reads only
03
comes back · organic clicks per search term beside paid clicks per campaign, kept apart
04
lands · which side moved, by how much, and whether one is hiding the other · no blending
with GA4
Search Console shows the terms and pages that earned a click. GA4 shows what those visitors did once they arrived. Read together, an organic click is followed through to the behaviour on your site.
01
you ask · “Do organic visitors do anything once they arrive?”
02
it picks · the page read in Search Console and the landing-page behaviour read in GA4 · reads only
03
comes back · the pages earning organic clicks, beside what those sessions did on the site
04
lands · the organic pages that lead somewhere, and the ones that bounce · named