Google Search Console API

Name: Google Search Console API
Brand: Google Search Console API
Availability: InStock

✓ Official Vendor SpecMarketingSeo Semoauth211 EndpointsREST

Install Jentic One Beta

Connect the Google Search Console API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Google Search Console API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Google Search Console API.

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

GET STARTED

Start building with Google Search Console API

Explore with Jentic

View OpenAPI Document

For Agents

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

Use for: Get the top 100 search queries driving clicks to my site last month, Check whether a specific URL is indexed by Google, List all sitemaps submitted for example.com, Submit a new sitemap.xml to Search Console

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

Use Cases

Patterns agents use Google Search Console API for, with concrete tasks.

★ 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.

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.

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.

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.

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

11 endpoints — the google search console api gives programmatic access to search console data for verified site owners and to public url inspection tools.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

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.

Intent-based discovery

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.

Time to first call

FAQs

Specific to using Google Search Console API through Jentic.

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.

Google Search Console API

Connect the Google Search Console API to your agent

Capabilities

Start building with Google Search Console API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs