Google Search Console API: Complete SEO Automation & Data Guide
The Google Search Console API gives authorised applications programmatic access to selected Search Console data and management functions. Instead of manually opening reports, developers and SEO teams can query Search Analytics, inspect indexed URL information, work with sitemaps and manage accessible properties through automated workflows. For the standard Search Console interface, start with our Google Search Console guide. This API guide forms part of the wider Google playbook.
What Is the Google Search Console API?
The API lets software interact with selected Search Console resources rather than relying entirely on manual browser-based reporting.
Extract Search Data
Retrieve Search Analytics performance information for authorised properties and process it inside custom applications, reporting systems or data warehouses.
Automate Repetitive Work
Schedule recurring extraction, monitoring and reporting tasks instead of manually downloading similar Search Console data every week or month.
Build Custom SEO Systems
Combine Search Console information with internal datasets, Analytics or reporting tools to create workflows suited to a particular SEO operation.
Search Console UI vs Search Console API
The two access methods complement each other. The API is strongest for automation, while the browser interface remains valuable for interactive investigation.
Search Console Interface
Use the standard interface when an SEO specialist wants to inspect reports interactively, investigate a particular URL or review Google's visual diagnostic information.
- Interactive Performance reports
- Page Indexing reports
- URL Inspection interface
- Live URL testing
- Manual troubleshooting
- Visual enhancements and issue reports
Search Console API
Use the API when Search Console information needs to be extracted or checked programmatically at scale.
- Scheduled performance extraction
- Custom databases and warehouses
- Bulk indexed-URL inspection
- Sitemap automation
- Custom dashboards
- Monitoring and alert workflows
Four Core Search Console API Areas
The public Search Console API is organised around Search Analytics, URL Inspection, sitemaps and Search Console properties.
Search Analytics
Query Search performance using date ranges, dimensions, filters, row limits and aggregation settings to retrieve clicks, impressions, CTR and position.
URL Inspection
Retrieve information about the version of an authorised URL known to Google's index, including crawl, canonical and indexing-related information.
Sitemaps
List, inspect, submit and remove sitemap resources associated with Search Console properties.
Sites
List accessible properties, inspect access levels and work with Search Console site resources according to the authorised user's permissions.
OAuth 2.0 Controls Access to Private Search Console Data
Applications should request only the permissions they genuinely need and must still operate within the Search Console access granted to the authorising Google account.
Authorise the Application Before Requesting Data
A typical workflow starts by creating or selecting a Google Cloud project, enabling the relevant API, configuring the OAuth consent process and creating suitable application credentials.
The user then authorises the requested scope. The resulting token allows the application to make authenticated requests on behalf of that authorised user.
The Cloud setup belongs to the broader developer environment covered separately in our planned Google Cloud Console guide.
Read-Only vs Read/Write Access
Use the least privileged scope that can complete the task. Reporting tools usually do not need write access.
Read-Only Scope
Suitable when the application only needs to retrieve Search Console information and does not need to change Search Console resources.
https://www.googleapis.com/auth/webmasters.readonly
Read/Write Scope
Use the broader scope only when the application genuinely needs operations that modify eligible Search Console resources.
https://www.googleapis.com/auth/webmasters
URL-Prefix and Domain Properties Use Different API Values
The exact Search Console property identifier matters. Applications should use the same property form recognised by Search Console.
URL-Prefix Property
A URL-prefix property includes the protocol and usually ends with a trailing slash.
https://www.example.com/
Only URLs within that exact property scope are represented.
Domain Property
Domain properties use Search Console's domain-property syntax rather than a normal website URL.
sc-domain:example.com
Using the wrong property identifier can lead to access or request errors even when the user can access another version of the site.
Query Search Performance Programmatically
Search Analytics is the core SEO reporting endpoint for retrieving Search performance by selected dimensions and filters.
Build a Search Analytics Request
Requests can define a start date, end date, dimensions, filters, row limit and other query settings.
A common SEO workflow is to request query and landing-page combinations, then analyse their clicks, impressions, CTR and average position.
For definitions and interpretation of the underlying performance metrics, see our complete Search Console guide.
{
"startDate": "2026-07-01",
"endDate": "2026-07-31",
"dimensions": [
"query",
"page"
],
"rowLimit": 25000
}
Dimensions, Metrics and Aggregation
Dimensions determine how the performance data is grouped. Metrics describe how those grouped rows performed.
Common Dimensions
Dimensions can break the response into meaningful SEO groupings.
Core Metrics
Search Analytics response rows can include the principal Search Console performance metrics.
Aggregation Matters
Changing dimensions and aggregation settings can change how Google groups the data. Two queries using different dimensions should not automatically be expected to produce identical totals.
Narrow Large Search Datasets to a Specific SEO Question
Filters can reduce broad performance data to the exact country, device, query theme or landing-page group being investigated.
From Millions of Impressions to One Useful Segment
Suppose an SEO team wants to understand mobile UK performance for queries containing “seo” where the ranking page sits within the blog.
Instead of downloading the entire property dataset, the request can include dimension filters that narrow the response before analysis.
country = GBR
device = MOBILE
query contains "seo"
page contains "/blog/"
The Search Console API Is Not a Raw Log of Every Google Search Query
Search Analytics does not guarantee that every possible row in Google's underlying search data will be returned. The API is subject to Search Console's internal data limits and generally returns the most significant rows rather than functioning as a complete server-style log of every individual search.
This means an SEO reporting system should not describe Search Analytics API exports as a complete list of every query that produced an impression. Missing low-volume query rows are not evidence that those searches never occurred.
When date is included as a dimension, days with no available data may also be absent from the returned rows rather than appearing automatically as rows containing zeros.
FAQ Search Appearance Is Being Deprecated
Google stopped showing FAQ rich results in Search in May 2026. As part of the corresponding Search Console cleanup, the FAQ search-appearance value in Search Analytics is being deprecated during August 2026.
Applications that rely on historic search-appearance values should avoid assuming that a previously supported appearance category will remain available permanently. Search features and API reporting dimensions can evolve as Google changes Search presentation.
For the broader structured-data testing context, see our Google Rich Results Test guide.
Inspect Google's Indexed Understanding of Important URLs
The URL Inspection API is useful for programmatic monitoring, but it does not perform the same live URL test available through the Search Console browser interface.
Indexed URL State — Not a Live Crawl
The API can return information about the URL as known to Google's index, including indexing verdicts, crawl information and canonical signals.
This makes it valuable for checking groups of strategically important pages without manually opening the URL Inspection interface for each one.
For live testing and the full interactive inspection workflow, continue to use the standard Search Console interface.
POST https://searchconsole.googleapis.com/v1/urlInspection/index:inspect
Compare User-Declared and Google-Selected Canonicals
A canonical difference is not automatically an error, but it is a useful signal to investigate when Google consistently selects a different URL from the one the site declares.
Canonical Agreement
The site's declared canonical and Google's selected canonical point to the same preferred URL.
Canonical Difference
Google has selected a different canonical from the site's declared preference. Investigate duplication, internal links, redirects, page content and other canonical signals.
List, Inspect, Submit and Delete Sitemap Resources
Sitemap automation is useful for larger environments, but submitting a sitemap through the API still does not guarantee that Google will index every URL it contains.
List Sitemaps
Retrieve sitemap resources associated with the selected Search Console property and inspect their reported state.
Get Sitemap
Retrieve information about a particular sitemap, including available warnings, errors and submission-related metadata.
Submit Sitemap
Programmatically notify Search Console about a sitemap resource for the authorised property.
Delete Sitemap
Remove a sitemap resource from the property's Search Console sitemap list when appropriate.
Do Not Build New Reporting Around the Old Sitemap “Indexed” Count
Some older sitemap API structures include an indexed count inside sitemap contents. Google marks that value as deprecated, so new monitoring systems should not depend on it as a reliable modern sitemap-indexation metric.
Design Automation Around Search Console Rate Limits
A good integration does not repeatedly request unchanged information or attempt to inspect every URL continuously.
Search Analytics Quotas
Search Analytics uses both rate limits and separate load-based quotas. Large date ranges and expensive page/query combinations can consume more load.
URL Inspection Quotas
URL Inspection has much tighter limits, which makes prioritisation essential for larger websites.
Do Not Re-Download Six Months of Data Every Morning
A more efficient system stores previously retrieved historical data and only requests the incremental period required for the next update.
Store Historical Data
Save completed historical reporting periods rather than requesting the same unchanged date range repeatedly.
Fetch Incrementally
Request new or recently processed dates and append them to the existing dataset.
Cache Inspection Results
Do not use limited URL Inspection quota to inspect the same unchanged URLs again and again within a short period.
Prioritise Important URLs
Focus inspection on money pages, newly launched URLs, pages with recent issues and strategically important templates.
Practical Search Console API Workflows
The API becomes most useful when a team turns Search Console data into a repeatable process rather than simply reproducing the interface.
Daily Search Performance Warehouse
Store daily Search Analytics results so long-term reporting does not depend on repeated manual exports.
Landing-Page Opportunity Finder
Create internal analysis rules that highlight pages with high impressions and commercially interesting positions but comparatively weak CTR.
Canonical Monitoring
Regularly inspect selected important URLs and compare Google's canonical choice with the site's declared preference.
Index Status Monitoring
Track material changes to selected strategic pages rather than repeatedly checking every URL on the site.
Sitemap Monitoring
Monitor sitemap resources for new errors, warnings or operational changes without relying solely on manual Search Console checks.
Branded vs Non-Branded Reporting
Use internal query-classification logic to separate brand-related searches from wider discovery terms for more meaningful organic performance analysis.
Your Automation Rules Are Your Own SEO Logic
If your system flags a page because it ranks between positions 4 and 15 with high impressions and low CTR, that does not mean Google has recommended that page for optimisation. It is an internal analytical rule created from Search Console data.
The API supplies the underlying data. Your software, analysts and SEO strategy decide how that information is interpreted and which actions are appropriate.
Search Console API → Database → Data Studio
For simple reporting, a direct Search Console connector may be sufficient. For more advanced workflows, an API pipeline gives the team greater control over storage, processing and historical data.
Authenticate
Authorise the application using the minimum OAuth scope required.
Extract
Request Search Analytics or other permitted Search Console resources.
Store
Save the information in a controlled historical database or warehouse.
Transform
Normalise URLs, classify queries and calculate internal reporting groups.
Visualise
Build reusable reporting through Google Data Studio.
Direct Connector
Best when the goal is straightforward reporting with minimal engineering and the connector already exposes the required fields.
API Pipeline
Better when the business needs persistent historical storage, custom processing, automated checks or integration with other proprietary data.
Hybrid Approach
Many organisations use the direct connector for quick dashboards while maintaining API-based data for specialist analysis and long-term storage.
Using the Search Console API With Python
Python is a common option for scheduled Search Console extraction, but the important part is the workflow rather than a particular programming language.
Keep the Integration Simple
A typical script authenticates, identifies the correct property, constructs the request, retrieves the response and sends the resulting rows into a database, file or analysis process.
For a reporting-only application, use the read-only OAuth scope unless the workflow genuinely needs write operations.
https://www.googleapis.com/auth/webmasters.readonly
Combine Search Console With Google Analytics Carefully
Search Console describes Google Search performance. Analytics describes onsite behaviour. They complement one another but do not measure identical things.
Search Console
Use Search Analytics for queries, pages, impressions, clicks, CTR and average position before or at the search click.
Google Analytics
Use Google Analytics to understand measurable behaviour after users arrive, including sessions, engagement and business events.
Combined Reporting
Join compatible landing-page data carefully and avoid expecting Search Console clicks and Analytics sessions to reconcile perfectly.
What the Search Console API Does Not Give You
The API is powerful, but treating it as a complete export of every Search Console feature leads to incorrect expectations.
No Live URL Test API
URL Inspection API results relate to Google's indexed understanding rather than performing the interactive live test available in Search Console.
Not Every Search Row
Search Analytics does not expose a complete raw query log containing every possible Search impression.
Not Every UI Report
Do not assume every Search Console interface report has an equivalent public API endpoint.
No Automatic SEO Diagnosis
The API supplies data. It does not determine why rankings fell or which SEO change a business should make next.
Common Search Console API Mistakes
Most integration problems come from property access, poor data assumptions, inefficient requests or treating API responses as more complete than they really are.
Requesting Excessive Permissions
A reporting application should not request read/write access when read-only access is sufficient.
Using the Wrong Property String
A URL-prefix property and a Domain property use different identifiers. Incorrect property syntax can break otherwise valid requests.
Calling It Complete Query Data
Search Analytics rows are not a comprehensive raw log of every search impression.
Repeatedly Downloading Old Data
Store historical results and request incremental updates instead of wasting quota on unchanged date ranges.
Inspecting Every URL Constantly
URL Inspection quotas are much tighter than Search Analytics quotas. Prioritise valuable and recently changed pages.
Confusing Indexed With Live State
The URL Inspection API does not perform the same live fetch as the browser interface's live test.
Bad Cross-Platform Joins
Search Console and GA4 data can be combined, but different scopes and measurement systems can create misleading blends if treated carelessly.
Depending on Deprecated Fields
API fields and Search appearance types can be deprecated as Google's Search features evolve.
Automating Without Human Review
An automated alert should surface a potential issue for investigation rather than automatically assuming that every unusual response represents an SEO problem.
Common Questions About the Google Search Console API
Quick answers covering access, Search Analytics, URL Inspection, quotas, sitemaps and automated SEO reporting.
01 What is the Google Search Console API?
The Google Search Console API lets authorised applications access selected Search Console data and resources programmatically, including Search Analytics, URL Inspection, sitemaps and Search Console properties.
02 Does the Search Console API require OAuth?
Yes. Access to private Search Console property data uses OAuth 2.0 authorisation. Applications should request the minimum scope needed for the workflow.
03 What data can Search Analytics API return?
Search Analytics can return performance metrics including clicks, impressions, CTR and position grouped by supported dimensions such as query, page, country, device, date and other available dimensions.
04 Does the API return every Google Search query?
No. Search Analytics is subject to Search Console's internal data limits and does not guarantee every possible search row. It should not be treated as a complete raw query log.
05 Can I filter Search Console API data?
Yes. Search Analytics supports dimension filters that can narrow results by fields such as query, page, country and device using supported filter operators.
06 Can the URL Inspection API perform a live URL test?
No. The API reports information about the indexed URL state known to Google. The live URL testing workflow remains part of the standard Search Console interface.
07 Can the API show Google's canonical URL?
The URL Inspection response can provide Google's selected canonical and the user-declared canonical where that information is available, making programmatic canonical comparison possible.
08 Can I submit a sitemap through the API?
Yes. The Sitemaps service supports submitting sitemap resources as well as listing, retrieving and deleting them. Sitemap submission does not guarantee that the contained URLs will be indexed.
09 Can Search Console API data be used in Data Studio?
Yes. A custom pipeline can extract and store Search Console data and then visualise the processed dataset in Google Data Studio. For simpler reports, the direct Search Console connector may require less engineering.
10 Is the Search Console API useful for SEO automation?
Yes. It is useful for scheduled performance extraction, selected index-status monitoring, canonical comparisons, sitemap monitoring and custom reporting. The automation logic still needs to be designed and interpreted by the SEO team.
Continue Your Search Console Automation Workflow
Connect Search Console's programmatic data layer with reporting, measurement, structured-data testing and Google's wider developer platform.
Turn Search Console Data Into Repeatable SEO Systems
The Search Console API becomes valuable when it removes repetitive work or creates analysis that the standard interface cannot provide efficiently. Use the minimum OAuth permissions required, preserve the exact Search Console property syntax, store historical Search Analytics data rather than requesting it repeatedly, respect the tighter URL Inspection quotas and remember that API rows are not a complete raw search log. Build automation around specific business questions: important landing-page opportunities, canonical changes, strategic index-status monitoring, sitemap problems and reporting pipelines. The API should make SEO analysis more systematic — not replace the judgement needed to understand what the data actually means.
