Opus Growth

Batch URL Index Inspection

Inspects the Google index status of MANY URLs in one call: a batch wrapper over gsc_url_inspect for site-wide crawl-freshness audits (which URLs Google recrawled since a content change, which are indexed, which were…

Type
Reads only
Credits
1
Platform
Search Console
Approval
Not needed, nothing changes

What it does

Inspects the Google index status of MANY URLs in one call: a batch wrapper over gsc_url_inspect for site-wide crawl-freshness audits (which URLs Google recrawled since a content change, which are indexed, which were never crawled). Returns a compact row per URL — page_url, verdict, coverage (coverageState), last_crawl, indexing, google_canonical — deliberately WITHOUT the rich-results / mobile detail so the whole table stays within the result-size limit. page_urls is a list of full URLs (a comma/newline-separated string is also accepted). `limit` = URLs per call (0 = all given URLs). Google's URL Inspection API is quota-limited (~2000/day and 600/min per property) and answers ~6.6 s per URL; URLs are inspected 5 at a time within a 100-second budget, URLs beyond it come back in `skipped`, and if a quota or rate error is hit mid-batch the tool STOPS and reports how many rows it managed. site_url must be a verified property. To ask Google to crawl the URLs that come back unknown, discovered-not-indexed or stale, pass them to gsc_request_indexing.

MCP: gsc_inspect_urls

How to use it

You don't call tools by name. Write what you want in ChatGPT, Claude or another assistant connected to Opus Growth, in your own words; it picks this tool when it fits.

Parameters

NameTypeRequiredDefault
site_urlstringRequired·Exact URL of the connected WordPress site to target when more than one site is available.
page_urlsarrayOptional·Page urls value for gsc inspect urls. Follow the documented provider format and use values returned by Opus Growth discovery tools where possible.
limitintegerOptional0Maximum number of rows returned in this response. When the result has_more flag is true, continue with next_page_token rather than assuming the list is complete.