Integration

Google Search Console integration

Google Search Console API for monitoring and optimizing website presence in Google Search results. Query search analytics data, manage sitemaps, inspect URLs, and monitor indexing status for SEO and webmaster operations.

Connect Google Search Console How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Google Search Console.Built from the 16 Google Search Console tools below, on the connection you add once.

Common Google Search Console use cases

finding top performing keywords
removing outdated sitemaps
identifying top performing pages
removing a site from Search Console
monitoring sitemap submission status
tracking daily organic traffic trends
adding a new website to Search Console
analyzing international search traffic
checking if a URL is indexed by Google
analyzing organic search traffic trends

What you can do with Google Search Console

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Searchanalytics, 6 operations

query_search_analyticsQuery search analyticsPOSTQueries search analytics data for a verified site. Returns rows of search performance data including clicks, impressions, CTR, and average position. Use dimensions to group results by query, page, country, device, or date.
query_search_analytics_by_countryQuery search analytics by countryPOSTQueries search analytics grouped by country. Returns per-country metrics showing geographic distribution of search traffic. Preset with country dimension for international SEO analysis.
query_search_analytics_by_dateQuery search analytics by datePOSTQueries search analytics data grouped by date. Returns daily metrics showing search performance trends over time. Preset with date dimension for time-series analysis.
query_search_analytics_by_deviceQuery search analytics by devicePOSTQueries search analytics grouped by device type. Returns per-device metrics (DESKTOP, MOBILE, TABLET) showing how search traffic varies by device. Preset with device dimension.
query_search_analytics_by_pageQuery search analytics by pagePOSTQueries search analytics grouped by page URL. Returns per-page metrics showing which pages receive the most search traffic. Preset with page dimension for content performance analysis.
query_search_analytics_by_queryQuery search analytics by queryPOSTQueries search analytics grouped by search query/keyword. Returns per-keyword metrics showing which search terms drive traffic. Preset with query dimension for keyword analysis.

Site, 4 operations

add_siteAdd sitePUTAdds a new property to the user's Search Console account. The site still requires ownership verification after being added.
delete_siteDelete siteDELETERemoves a site from the user's Search Console account. Only removes the user's association with the property, not the property or its data.
get_siteGet siteGETRetrieves details for a specific Search Console property. Returns the site URL and the user's permission level for that property.
list_sitesList sitesGETLists all Search Console sites/properties accessible by the authenticated user. Returns site URLs and permission levels for each property.

Sitemap, 4 operations

delete_sitemapDelete sitemapDELETERemoves a sitemap from Search Console's submitted sitemaps list. Already-indexed URLs from the sitemap remain in Google's index.
get_sitemapGet sitemapGETRetrieves detailed information about a specific sitemap. Returns status, last processed dates, error/warning counts, and content type breakdowns with submitted vs indexed URL counts.
list_sitemapsList sitemapsGETLists all sitemaps submitted for a site. Returns sitemap paths, last submission/download times, status, warning and error counts, and content type breakdowns.
submit_sitemapSubmit sitemapPUTSubmits a sitemap to Google Search Console for crawling and indexing. The sitemap must be accessible at the specified URL and contain valid XML.

Urlinspection, 2 operations

batch_inspect_urlsBatch inspect urlsPOSTInspects a single URL per call; intended for iterating over a URL list. Returns indexing status, crawl data, and mobile usability for the inspected URL.
inspect_urlInspect urlPOSTInspects a URL's indexing and crawl status in Google Search. Returns coverage state, crawl details, indexing verdict, mobile usability, rich results, and AMP status.

OAuth scopes Google Search Console requires

Each operation declares the scopes Google Search Console requires for it.

https://www.googleapis.com/auth/webmasters.readonlyneeded by batch_inspect_urls, get_site, get_sitemap and 9 more
https://www.googleapis.com/auth/webmastersneeded by add_site, delete_site, delete_sitemap and 1 more

Use Google Search Console from Claude Code, Cursor or Codex

Connect Google Search Console in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Google Search Console operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Google Search Console

Create your workspace
Sign up free. Nothing to install.
Connect Google Search Console once
Add your Google Search Console connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Google Search Console integration FAQ

What can you do with the Google Search Console integration?

LiveContext exposes 16 operations on Google Search Console, covering searchanalytics, site, sitemap and urlinspection. Common uses include finding top performing keywords, removing outdated sitemaps and identifying top performing pages.

Which OAuth scopes does Google Search Console require?

It depends on the operation: each one declares the scopes Google Search Console requires for it. The most common are https://www.googleapis.com/auth/webmasters.readonly (12 operations) and https://www.googleapis.com/auth/webmasters (4 operations).