The Google Search Console MCP for hands-off SEO monitoring
Sign in with Google once and your search analytics, sitemaps, and URL inspection results become building blocks for visual automations and AI agent workflows. 10 nodes covering the Search Console API.
What the Google Search Console MCP connector does
The Google Search Console connector for Mattering Automations covers the Search Console API: query search analytics by query, page, country, device, and date, list and manage your verified properties, submit and remove sitemaps, and run URL Inspection to check index status, coverage, and rich results for any page you own.
Each capability is a node on the Automations canvas, and every node speaks MCP, the open protocol for connecting AI assistants to tools. Claude, ChatGPT, and any MCP-capable assistant can use them, and they also power Matter, the platform's AI assistant. Ask for a weekly ranking report in plain language and the workflow gets built on the canvas in front of you.
We run this connector on this site: the pipeline that publishes and indexes these very pages resubmits our sitemap through the GSC Submit Sitemap node and checks the results with GSC Inspect URL. The page you are reading went through it.
One connection, three surfaces
- Visual automations. Drag Google Search Console nodes onto the canvas and wire them to triggers, conditions, and other apps.
- AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
- The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.
Every Google Search Console node, ready to drop on the canvas
10 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.
Read and query nodes 6
GSC Connection Health Check
Force an OAuth token refresh and report the outcome, validating the Google Search Console connection.
GSC Get Sitemap
Get status/details for a single submitted sitemap.
GSC Inspect URL
Run URL Inspection for a page (index status, coverage, rich results).
GSC List Sitemaps
List submitted sitemaps for a property.
GSC List Sites
List the verified sites/properties on the connected account.
GSC Search Analytics
Query Search Analytics (clicks, impressions, CTR, position) by dimension.
Action nodes 4
GSC Add Site
Add a site/property to the account (verification still required in GSC).
GSC Delete Site
Remove a site/property from the account.
GSC Delete Sitemap
Remove a submitted sitemap from a property.
GSC Submit Sitemap
Submit (or re-submit) a sitemap for a property.
Connecting Google Search Console takes one credential
No API key to copy. The connector uses Google sign-in: you authenticate with the Google account that has access to your Search Console properties and grant the Search Console permission on Google's consent screen.
In Mattering Automations, open Connectors and choose Google Search Console.
Sign in with the Google account that owns or has access to your Search Console properties and approve the Search Console permission.
The connector stores the token encrypted and refreshes it automatically from then on.
All 10 Search Console nodes appear in the canvas palette, ready to use. You can revoke access at any time from your Google account's security settings.
Common uses for the Google Search Console MCP
Weekly SEO reports on a schedule
Pull clicks, impressions, CTR, and average position by query or page every Monday and post the digest to your team, so nobody logs into Search Console to copy numbers.
Sitemap resubmission on every release
When new pages ship, resubmit the sitemap automatically so Google re-reads it right away instead of waiting for the next crawl.
Index monitoring for new pages
Run URL Inspection on recently published URLs on a schedule and open a task when a page is still not indexed, so indexing problems surface as work items instead of surprises.
Low-CTR query mining
Find queries with high impressions but weak click-through, then feed them to an agent as title and meta description rewrite candidates.
Content opportunities from position data
List queries ranking just off the first page and turn them into a prioritized content upgrade queue in Mattering Productivity.
Portfolio checks across properties
List every verified site on the account and loop the same health checks over each one, useful for agencies watching many domains.
Example: New pages tracked from publish to indexed
Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.
Trigger: a new page goes live on your site.
Google Search Console: Submit Sitemap resubmits your sitemap so Google re-reads it.
Google Search Console: Inspect URL checks the new page's index status on a schedule.
Output: the index verdict is posted to your team, and a task is created in Mattering Productivity if the page is still not indexed. This is the exact flow Mattering runs for its own pages.
Google Search Console MCP questions, answered
Can an AI agent read my search analytics through this MCP?
Yes. Matter and any MCP-connected assistant, including Claude and ChatGPT, can query clicks, impressions, CTR, and average position, broken down by query, page, country, device, search appearance, or date, at up to 25,000 rows per request.
Does this work with Claude, ChatGPT, or other AI assistants?
Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and work with Search Console through them. Matter, the assistant built into the platform, uses the same nodes natively.
How does authentication work?
Through Google OAuth. You sign in with the Google account that has access to your Search Console properties and approve the permission on Google's consent screen. The token is stored encrypted in Google Secret Manager, refreshed automatically, and revocable at any time from your Google account's security settings.
Can it get my pages indexed?
It can submit sitemaps and inspect a URL's index status, which is how you tell Google about new pages and verify the result. Google decides what gets indexed. The manual Request Indexing button is not available through Google's public APIs, and Google restricts its separate Indexing API to job posting and broadcast event pages, so that one click stays in the Search Console UI.
Which properties can the connector see?
Every property the connected Google account can access, both domain properties (the sc-domain form) and URL-prefix properties. The List Sites node returns them so agents can discover properties instead of relying on hardcoded values.
Can it change anything in my Search Console?
The write surface is narrow: submit or remove sitemaps and add or remove properties. Adding a property still requires verification inside Search Console, and nothing in the connector modifies your website itself.
How much history can it query?
Search Console keeps roughly 16 months of performance data, so that is the window a search analytics query can span. For longer trend lines, an automation can snapshot the numbers into a Mattering database on a schedule.
What are the API rate limits?
Google enforces per-day and per-minute quotas on the Search Console API, with a separate daily quota for URL Inspection. Google's developer documentation is the source of truth for current numbers. The connector surfaces quota errors on the node output so workflows can retry later.
Put Google Search Console to work inside your workspace
Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.
All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Google Search Console is a product of its respective owner; Mattering is an independent platform.