Weave
Sign InSign Up
View as .md ↗
Google Search Console

Google Search Console | Batch Url Inspection

MCP server · Marketing · google.com · 4 categories · 10 tools

Powered by Advanced GSC ↗

Google Search Console is Google's free tool for tracking how your sites perform in Google Search. This integration lets your AI workflows read that data — search traffic and rankings, index coverage and URL inspection, and sitemap status — for the properties your connected Google account can access.

gsc_batch-url-inspection

Get Google's index status for up to 10 URLs in one call. SLOW — can take up to about two minutes; prefer gsc_inspect-url for a single URL. If the connected Google account cannot verify siteUrl, the partner returns no data rather than an error. Read-only.

Tool Input

siteUrlstringrequired— The Search Console property, exactly as it appears in Search Console — either an absolute URL-prefix property (e.g. https://www.example.com/, including any trailing slash) or a domain property (sc-domain:example.com). Forwarded verbatim, never normalized; use gsc_list-properties to see the connected account's exact property identifiers. If the connected Google account cannot verify this property, the partner returns no data rather than an error.(min length: 1)
urlsarrayrequired— The page URLs to inspect (1-10). Each URL is inspected individually against the Google index, so this call is slow — it can take up to about two minutes for a full batch of 10 and never retries internally on failure. For a single URL, use gsc_inspect-url instead.(min items: 1, max items: 10)
[]string(uri)— The absolute page URL, exactly as it appears on the site (e.g. https://www.example.com/path).

Tool Output

siteUrlstringrequired— The Search Console property.
resultsarrayrequired— Per-URL inspection results, in request order.
[]object
pageUrlstringrequired— The inspected page URL.
verdictstring— Overall verdict (e.g. PASS, NEUTRAL, FAIL).
coverageStatestring— Human-readable index coverage state (e.g. 'Submitted and indexed').
summarystring— Human-readable summary of the index status.
robotsTxtStatestring— robots.txt state (e.g. ALLOWED).
indexingStatestring— Indexing state (e.g. INDEXING_ALLOWED).
pageFetchStatestring— Page fetch state (e.g. SUCCESSFUL).
lastCrawlTimestringnullrequired— When Google last crawled the page; null when never crawled.
googleCanonicalstringnullrequired— The canonical URL Google selected; null when unknown.
userCanonicalstringnullrequired— The canonical URL declared by the page; null when unknown.
crawledAsstringnullrequired— Crawler user-agent type (e.g. MOBILE); null when n/a.
inspectionLinkstring— Deep link to the URL in Search Console.
richResultsobjectnullrequired— Rich-results detail; null when none detected.
2 fields
verdictstring— Rich-results verdict.
detectedTypesarray— Detected rich-result types.
1 field
[]string
okboolean— Whether this URL was inspected successfully.

We're Adding More Google Search Console Tools Constantly!

Don't see a specific Google Search Console tool you need? Email [email protected] and we can add it.

Google Search Console Frequently Asked Questions

What does the Batch Url Inspection tool do?

This page documents the Batch Url Inspection tool (gsc_batch-url-inspection). Get Google's index status for up to 10 URLs in one call. SLOW, can take up to about two minutes; prefer gsc_inspect-url for a single URL. If the connected Google account cannot verify siteUrl, the partner returns no data rather than an error. Read-only. It is one of the Google Search Console URL Inspection tools, invoked through your firm's Weave MCP connection and available to members whose access level permits it.

Why is this slow, and does it retry on failure?

It inspects each URL individually against the Google index, so a full batch of ten can take up to about two minutes, and it never retries internally on failure. For a single URL, use gsc_inspect-url instead, it's faster.

What is the Google Search Console integration?

The Google Search Console integration connects your firm's Google Search Console account to Weave. Google Search Console is Google's free tool for tracking how your sites perform in Google Search. This integration lets your AI workflows read that data, search traffic and rankings, index coverage and URL inspection, and sitemap status, for the properties your connected Google account can access. It groups 10 tools into 4 categories, exposed through your firm's Weave MCP connection and filtered per member by access level.

How does my firm connect Google Search Console to Weave?

An admin authorizes a Google account with access to your Search Console properties once, via Google's OAuth consent flow in the Weave console. Every firm member then works through that single connection, there is no per-member Google sign-in.

Why did a tool return no data for our site?

Every gsc tool that takes a siteUrl requires the connected Google account to be a verified owner or user of that property in Search Console, if it can't verify the property, the tool returns no data rather than an error. gsc_list-properties is the exception: it takes no input and simply lists every property the connected account can access, so start there to get the right siteUrl.

Why does the data look a couple of days behind our live traffic?

Search Console's performance data typically lags live traffic by about two days; that's a Google-side reporting delay, not a Weave sync issue.

Can these tools change anything in Search Console?

No. Every gsc tool is read-only, none of them can submit URLs, edit sitemaps, or change any Search Console setting.

Related Tools

inspect-urlcheck-indexing-issues