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

Google Search Console | Check Indexing Issues

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_check-indexing-issues

Check up to 10 URLs for indexing problems (excluded, blocked, or otherwise unindexed) against a Search Console property. 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 check for indexing issues (1-10).(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.
totalCheckednumber— Number of URLs checked.
indexedarrayrequired— URLs that are indexed.
[]string
notIndexedarrayrequired— URLs that are not indexed, with their coverage state.
[]object
urlstringrequired— The not-indexed URL.
coverageStatestring— Why the URL is not indexed.
canonicalIssuesarrayrequired— URLs with canonical issues (partner shape unobserved; keys camelCased).
[]object
[key: string]any
robotsBlockedarrayrequired— URLs blocked by robots.txt (partner shape unobserved; keys camelCased).
[]object
[key: string]any
fetchIssuesarrayrequired— URLs Google could not fetch, with their fetch state.
[]object
urlstringrequired— The URL Google could not fetch.
pageFetchStatestring— The fetch failure state.

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 Check Indexing Issues tool do?

This page documents the Check Indexing Issues tool (gsc_check-indexing-issues). Check up to 10 URLs for indexing problems (excluded, blocked, or otherwise unindexed) against a Search Console property. 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.

How is this different from inspect-url or batch-url-inspection?

check-indexing-issues is purpose-built to triage a list of up to ten URLs into buckets, indexed, not indexed, canonical issues, robots-blocked, fetch issues, rather than returning the full inspection detail inspect-url and batch-url-inspection do.

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

batch-url-inspectioninspect-urllist-sitemaps