Google Search Console

01

Setup

1. 01Connect Google. In the superagnt app open Integrations, pick Google Search Console and click Connect with Google.
2. 02Approve Search Console access. Google asks only for Search Console access (the https://www.googleapis.com/auth/webmasters scope, which also covers adding properties and submitting sitemaps) plus your Google identity. Approve it in the Google window.

Google Search Console, Google Docs, Google Sheets and Google Calendar share one Google sign-in, but each is its own connection with its own consent: connecting one never grants the others. If the workspace already has a Google account connected for another Google app, the dialog offers Connect Google Search Console instead, which asks that account for Search Console's permissions only. Access tokens are refreshed for you.

02

Things to know

• Search analytics data is typically 2 to 3 days behind. Pass dataState: "all" to include fresh data that is not final yet.
• Rows come sorted by clicks, highest first. Grouping by query leaves out rare and anonymized queries, so per-query rows can add up to far less than the property's totals. For totals, run a second query with no dimensions and read its single row.
• rowLimit is 1 to 25,000 (default 1,000). Page with startRow.
• URL inspection reports what Google knows about a URL; it does not request indexing, and there is no public API for that. The URL must belong to the siteUrl property. Report coverageState to a person rather than verdict, where NEUTRAL usually means excluded, not an error. Inspection is limited to about 600 a minute and 2,000 a day per property.
• A sitemap's errors and warnings are counts sent as strings. The API does not say what each error is: only the Search Console UI does.
• A new property covered by one the account already verified inherits the verification. Otherwise it shows as siteUnverifiedUser, with no data, until it is verified in Search Console.
• Removing a property unlinks it from the account. Search Console keeps its history, but the account loses access until the property is added and verified again.

03

Permissions

These defaults decide whether a superagnt_ agent runs a call or waits for a person (Permissions). Reads run without asking, including search analytics queries and URL inspection, which use POST but change nothing. Adding a property and submitting a sitemap ask by default. Removing a property and deleting a sitemap always ask a person first.

04

Examples

Top queries for the last 28 days

curl -X POST "https://api.superagnt.com/v1/connections/google-search-console/webmasters/v3/sites/sc-domain%3Aexample.com/searchAnalytics/query" \
  -H "Authorization: Bearer $AGNTDATA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "startDate": "2026-09-18",
    "endDate": "2026-10-15",
    "dimensions": ["query"],
    "rowLimit": 25
  }'

Which pages are losing clicks?

curl -X POST "https://api.superagnt.com/v1/connections/google-search-console/webmasters/v3/sites/sc-domain%3Aexample.com/searchAnalytics/query" \
  -H "Authorization: Bearer $AGNTDATA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "startDate": "2026-10-08",
    "endDate": "2026-10-15",
    "dimensions": ["page", "date"],
    "dimensionFilterGroups": [{"filters": [{"dimension": "page", "operator": "contains", "expression": "/blog/"}]}]
  }'

Is this URL indexed?

curl -X POST "https://api.superagnt.com/v1/connections/google-search-console/v1/urlInspection/index:inspect" \
  -H "Authorization: Bearer $AGNTDATA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "inspectionUrl": "https://example.com/blog/launch",
    "siteUrl": "sc-domain:example.com"
  }'

8 tools, one per resource and risk

MCP servers and agents on the grouped surface list Google Search Console as these tools. Each takes an action, and the ones that work across record types an object. Every operation also keeps its own per-operation name, in the next table, which works on every server. How grouping works: Grouped tools.

All 10 operations

Each operation is a REST path under https://api.superagnt.com/v1/connections/google-search-console and an MCP tool. The per-operation tool name is the one permissions, approvals and usage records use.

Related