Search ConsolePlatform
What search already knows about you
Read search performance, inspect a URL, request indexing and submit a sitemap.
- Live
- Your own Google sign-in
- Your verified properties
What it can do
What a Search Console MCP server can do here
6 tools, usable once Search Console is connected, as of v2.16.0: 4 read and 2 write. The writes — a request to recrawl a URL and a sitemap submission — run only with your approval in your AI client.
- Search performance
- Clicks, impressions, position and the queries behind them, for any date range the property holds.1 tool, usable once Search Console is connected
- Verified properties
- Which sites your Google account is verified on, so a report cannot silently read the wrong one.1 tool, usable once Search Console is connected
- URL inspection
- Whether a page is indexed and what Google saw when it last looked, and asking for a fresh crawl.2 tools, usable once Search Console is connected
- Sitemaps
- The sitemaps a property already has, and submitting one it does not.2 tools, usable once Search Console is connected
In practice
The first read, across what you connected
A worked example rather than a recording of your account — the shape of it, not your numbers.
An illustrative first turn: the assistant reads four connected products.
Google Ads
campaigns · spend
Google Analytics
key events
Search Console
verified sites
Tag Manager
tags · triggers
first read, before any change
Where you stand
- Account
- live, spending daily
- Tracking
- one tag quiet for 11 days
- Search terms
- 18% of spend unchosen
- Schedule
- always on, results are not
Start with the quiet tag.
Illustrative session
Access
What you actually grant
Stated in the words you would use, because you are being asked to make a decision here.
- What you are granting
- Read and submit access for the Search Console properties your Google account is already verified on. Verification itself happens in Search Console, not here.
- What it can never widen
- It runs as you. If you cannot open an account or a property in Google's own interface, the connector cannot reach it either, and no setting on our side changes that.
- Where the grant lives
- In your own Google account, on its permissions page, where you can withdraw it at any moment without asking us first.
Connect it with the Google account the property is verified under. A property you have not verified in Search Console is not reachable from here.
Google is still reviewing these permissions, so the consent screen may warn you that the app is not verified. You are granting access to your own account either way, and you can withdraw it from your Google account at any time.
Questions
Four short answers
The four things people ask before they connect this one, answered without hedging.
The ones your Google account is already verified on. Verification happens in Search Console itself, not here, and a property you have not verified is not reachable from the connector at all.
No. It reads performance and inspection data, and the two things it can send are a request to recrawl a URL and a sitemap submission. Neither one edits a page.
No. It asks Google to look again; it promises neither a result nor a position. What the connector adds is being able to ask, and to read the answer, in the same conversation as the rest of the work.
No. Google publishes an MCP server for Google Ads and one for Analytics, and neither covers Search Console. AdCopilot's hosted connector does: 6 tools usable once Search Console is connected, 4 read and 2 write, as of v2.16.0. The two writes ask Google to recrawl a URL and submit a sitemap, each only with your approval in your AI client.