Google Search Console MCP

Calls the Search Console API to list every property your connected Google account can read, preserving exact property identifiers and permission levels. A follow-up lookup returns the details of one property. Most subsequent performance and inspection queries need the exact property identifier returned here.

Runs a performance query filtered to a single page, returning the search queries that drove clicks to it along with impressions, CTR and average position. A matching tool works the other way: given a query, it returns the pages that ranked. A combined tool returns rows grouped by both page and query.

Calls Google's URL Inspection API for one URL and returns the full indexed-version result: crawl date, canonical URL, coverage state and any issues. A batch tool inspects up to 20 URLs in one call, each with its own outcome. This is not a live crawl test and does not request indexing.

Retrieves daily or recent hourly performance: clicks, impressions, position and CTR, as Google reports them. An overview tool combines totals with a daily time series in one call. Period comparison tools retrieve the same report for different named date ranges, returning each period's result separately without calculating differences.

Lists the sitemaps submitted to a Search Console property and returns one sitemap's metadata, including Google's reported warnings and errors. The toolkit reads sitemap records; it does not submit, delete or update them.

List Google Search Console properties accessible to the connected Google identity, preserving exact property identifiers and permission levels.

Get one exact Google Search Console property record. Returns the same fields as property discovery, with a direct lookup outcome.

Retrieve Google Search Console performance using supported dimensions, filters and aggregation. Returns one bounded page of source rows; pagination does not guarantee exhaustive data.

Retrieve Google's aggregate performance for a property and filter scope. Totals come from a separate source query, never from summing displayed detail rows.

Retrieve daily or recent hourly Google Search Console performance. Preserve reported timestamps, missing intervals and available incomplete-data metadata.

Retrieve observed search queries for an exact page or explicit page filter. Returns a bounded page; omitted query identities are not reconstructed.

Retrieve observed pages for an exact query or explicit query filter. Returns source performance rows without judging overlap between pages.

Retrieve performance grouped by page and query, with optional country/device detail. Returns source rows for client-side analysis, subject to Google's detail limits.

Retrieve observed search appearance categories and source metrics for a scope. Use returned categories as filters in a subsequent performance query.

Retrieve dates with reported performance in an explicit window and search surface. Missing dates do not establish zero traffic or a universal freshness boundary.

Retrieve separate source totals and daily performance, optionally with one detail dataset. At most three source requests; each dataset retains its own scope and continuation.

Retrieve the same performance report for supplied named periods. At most six independent source requests; returns datasets without matching rows or calculating changes.

Retrieve the same performance report for selected search surfaces. At most six independent source requests; preserve per-surface results and failures without combining metrics.

Retrieve the same performance report for supplied Google Search Console properties. At most six independent source requests; each property retains its own result and continuation.

List submitted sitemap records for a property, optionally within a sitemap index. Returns Google's metadata, not the sitemap XML URL inventory.

Get one submitted sitemap's Google Search Console metadata, warnings and errors. Deprecated indexed counts do not establish indexed coverage.

Retrieve Google's full indexed-version inspection result for one property-member URL. This is not a live test or an indexing request.

Retrieve indexed-version inspection results for up to 20 supplied URLs, with independent outcomes. Each attempted URL consumes one inspection request; this is not a sitewide index census.

Yes, every property your connected Google account has at least restricted access to. Property identifiers are returned exactly as Search Console uses them: URL-prefix (https://example.com/) or Domain (sc-domain:example.com). Properties your account cannot access are not returned.

No. Every tool is read-only. The toolkit connects with the webmasters.readonly OAuth scope, which Google does not permit to submit sitemaps, request indexing or change property settings. Nothing in your Search Console account or website configuration is modified.

Google Search Console web search data has a standard 3-day reporting lag. Hourly performance data is available only for the most recent 48 hours. The toolkit reports exactly what Google's API returns and does not estimate or fill gaps for missing days.

It cannot submit URLs for indexing, request sitemap processing, change property settings, add or remove users, or modify any data in Search Console. It cannot access properties your Google account cannot read, and URL inspection is limited to 20 URLs per call.

Templates are included with Typenode. Each workflow that starts uses one run from your plan, including workflows called through your custom MCP connector. Third-party services may charge separately; see Apps and setup.

You choose which accounts to connect. The template’s workflows and tools use the access you configure. Review the required scopes and setup details before connecting an account.