canonical: https://jentic.com/apis/googleapis.com/searchconsole

# Google Search Console API

The Google Search Console API gives programmatic access to Search Console data for verified site owners and to public URL inspection tools. Agents can query search analytics dimensions like clicks, impressions, CTR, and average position, manage verified sites, submit and inspect sitemaps, and run live URL and mobile-friendly checks. Results mirror what site owners see in the Search Console UI and cover the rolling 16-month performance window.

## For AI agents

Pull Google Search performance data, inspect URL indexing status, and manage sitemaps for verified websites.

## Scope

Does not handle ad campaigns, on-site analytics, or content publishing - use for Search Console performance reporting, sitemap management, and URL indexing diagnostics only.

## Capabilities

- Query search analytics by query, page, country, device, and date with up to 16 months of history
- Inspect a specific URL's indexing status, canonical, and rich result eligibility through the URL Inspection API
- Run live mobile-friendly tests on any public URL and retrieve resource-level issues
- List, add, and remove verified sites in a Search Console account
- Submit, list, and delete sitemaps for a verified site and read their last-processed status
- Retrieve the list of search appearance types (AMP, rich results, web light) attributed to a site

## Use cases

### SEO Performance Reporting

Pull daily search performance data into a BI tool or agent dashboard to track organic clicks, impressions, CTR, and average position by query, page, country, and device. The Search Console API exposes the same 16-month dataset visible in the UI but in raw, dimension-broken-down form, ready for joins against site analytics. Most reporting jobs run in under a minute per site once OAuth is set up.

Example prompt: Call POST /webmasters/v3/sites/{siteUrl}/searchAnalytics/query with dimensions [query, page] for the last 28 days and return the top 50 queries by clicks.

### Sitemap Management Automation

Automate sitemap submission and monitoring across many properties. The API lets you list submitted sitemaps, add a new sitemap when content ships, remove stale ones, and read the last-processed timestamp plus any errors or warnings. This replaces manual UI work for agencies and platforms managing dozens of sites.

Example prompt: Call PUT /webmasters/v3/sites/{siteUrl}/sitemaps/{feedpath} to submit https://example.com/sitemap.xml, then GET the same path to confirm processing.

### URL Indexing Diagnostics

Diagnose why a specific URL is or is not in Google's index. The URL Inspection endpoint returns the indexing verdict, last crawl time, canonical chosen by Google, mobile usability, and rich result eligibility. Useful for content QA pipelines and editorial agents that flag pages with indexing issues before launch.

Example prompt: Call POST /v1/urlInspection/index:inspect with inspectionUrl=https://example.com/blog/post-123 and return the indexStatusResult.verdict and coverageState.

### AI Agent SEO Audit Workflow

An AI agent runs end-to-end SEO audits across a portfolio of sites, combining search analytics, sitemap status, and per-URL inspection. Through Jentic the agent searches for the right operation, loads its schema, and executes calls without hand-coding OAuth flows. Useful for content teams that want a daily audit summary delivered to Slack.

Example prompt: For each verified site, call searchAnalytics:query plus sitemaps.list, then run urlInspection:index:inspect on the 10 newest URLs and produce a summary report.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /webmasters/v3/sites/{siteUrl}/searchAnalytics/query | Query search performance by dimension |
| GET | /webmasters/v3/sites | List verified sites |
| PUT | /webmasters/v3/sites/{siteUrl} | Add a site to the account |
| GET | /webmasters/v3/sites/{siteUrl}/sitemaps | List submitted sitemaps |
| POST | /v1/urlInspection/index:inspect | Inspect a URL's index status |
| POST | /v1/urlTestingTools/mobileFriendlyTest:run | Run a live mobile-friendly test |

## Key resources

- **searchanalytics** — Query search performance metrics by dimension
- **sites** — List, add, get, and delete verified sites
- **sitemaps** — List, get, submit, and delete sitemaps for a site
- **urlInspection** — Inspect a URL's index, mobile usability, and rich result status
- **urlTestingTools** — Run live mobile-friendly tests on public URLs

## Why Jentic

- **Setup:** Wiring Google Search Console by hand means registering an OAuth client, walking users through the consent screen, and refreshing access tokens against the searchconsole.googleapis.com host yourself. Through Jentic you install once, import the Search Console API from the API Directory, store the OAuth credential once, and your agent calls it.
- **Permission scoping:** Search Console puts the property in the URL path (/webmasters/v3/sites/{siteUrl}/...), so a rule can pin your agent to one verified site: it can pull search analytics and read sitemaps for that property and nothing else. You choose the operations it may call, so write actions like adding or deleting a site are not included unless you add them.
- **Credential handling:** Your Search Console OAuth credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'pull search analytics by query' or 'inspect a URL in the index', and Jentic returns the matching Search Console operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Google Indexing API** — Notify Google about new or updated URLs to crawl, complementing the Search Console reporting view.
- **Google Analytics Data API** — Pulls on-site behaviour data that pairs with Search Console organic search metrics.
- **Bing Webmaster API** — Bing's equivalent for managing sites and pulling search performance from Microsoft Bing.
- **Semrush API** — Third-party SEO data covering competitor keywords and rankings beyond a site's verified Search Console data.

## FAQ

### What authentication does the Google Search Console API use?

The Search Console API uses OAuth 2.0 with the webmasters or webmasters.readonly scope. Through Jentic the OAuth client and refresh tokens are stored encrypted in your Jentic One instance, so the agent receives only a scoped access token at call time.

### Can I pull historical search analytics data with the Google Search Console API?

Yes. POST /webmasters/v3/sites/{siteUrl}/searchAnalytics/query returns up to 16 months of data with dimensions for query, page, country, device, searchAppearance, and date. Anything older than 16 months is not retained by Google.

### What are the rate limits for the Google Search Console API?

Google enforces a default per-project quota of 1,200 queries per minute and 30,000 per day for the Search Console API, with separate limits for the URL Inspection endpoint at 2,000 queries per day and 600 per minute. Quotas can be raised through the Google Cloud console.

### How do I submit a sitemap through Jentic?

Run the Jentic search query 'submit a sitemap to google search console', load the resulting PUT /webmasters/v3/sites/{siteUrl}/sitemaps/{feedpath} operation, and execute it with the encoded site URL and sitemap feed path. Jentic handles the OAuth token injection.

### Is the Google Search Console API free?

Yes. The Search Console API is free to use within the published quotas. You only pay for any Google Cloud services you build alongside it.

### Can the URL Inspection API check URLs on sites I do not own?

No. POST /v1/urlInspection/index:inspect only works for URLs on properties verified to the authenticated user in Search Console. Public URL inspection is not supported.

### Can I limit what my agent is allowed to do with the Google Search Console API?

Yes. Because you run Jentic One yourself, your own rules decide which Search Console operations and credentials the agent may use. Since the property sits in the URL path (/webmasters/v3/sites/{siteUrl}/...), you can pin the agent to one verified site so it only queries search analytics and reads sitemaps for that property. You also choose the operations it may call, so write actions like adding or deleting a site stay out of reach unless you explicitly grant them.