Ask Search Console in plain English

What your assistant can read

Connected, your assistant works in Search Console under your own Google sign-in, on the sites that login can already open in Search Console. AdCopilot's Search Console tools number 7 once Search Console is connected, 5 that read and 2 that write, as of v2.45.2. The reads:

• Search performance. Clicks, impressions, click-through rate and average position for a site, split by query, page, country, device or date, over the dates you name. Search Console's numbers run a few days behind, so the newest days are thin.
• Your sites. The Search Console properties your login can reach, so it asks about the right one.
• Sitemaps. The sitemaps submitted for a site.
• URL inspection. Index status and coverage for one URL: whether Google has it, and the reason when it does not.

That is the half of the picture your ads account cannot show: what you already earn without paying, and which pages Google is not showing at all.

Prompts to try

These only read. Paste them more or less as they are once your assistant is connected.

• “Which queries brought the most clicks to my site in the last 28 days, and what position did each average?”
• “Which pages lost the most clicks this month compared with last month?”
• “Show clicks and impressions by country and by device for my main site.”
• “Is this URL indexed, and if not, what does Google say is the reason?”
• “Which sitemaps has Google read for my site, and when?”
• “Which searches do I already rank for in the top three, so I can stop paying for them?”

These send something to Google, so AdCopilot proposes each one first, and your AI client asks before it runs if it is set to ask before AdCopilot's write tools:

• “Submit my sitemap to Search Console.”
• “Send this job posting's URL to the Indexing API.”

What requesting indexing does and does not do

One of the two writes sends a URL to Google's Indexing API. Google acts on that notification only for pages with job-posting structured data, and for a livestream's broadcast event inside a video. For any other page it accepts the notification and does nothing with it, so an ordinary page is not crawled or indexed because of it. The result your assistant gets says only that a notification was submitted, and it says so.

Beside Google Ads

With Google Ads connected too, one read puts the search terms your account pays for beside the queries a Search Console site already ranks for, over the same dates. It lists the terms you pay for while ranking in the top three, paid terms that rank lower, and queries with real impressions that no paid term was found for. It needs Search Console connected, and says how to connect it when it is not. The Google Ads side of the work is on the audit page.

What a hosted Search Console MCP server cannot do

A hosted Search Console MCP server is a service your assistant calls, so there is nothing to install. Its limits are as plain as its reads:

• Edit a page or a site. Its two writes send a sitemap and a URL to Google. Neither changes what a page says.
• Promise indexing. See above: for an ordinary page the Indexing API does nothing.
• Add or verify a property. Adding and verifying happen in Search Console, and a site your login cannot open there is not reachable here at all.
• Say whether Google penalised a site. Google gives no way to read a site's manual actions or security issues, so it cannot. The Security and Manual Actions report in Search Console shows them.
• Remove anything. There is no tool that removes a sitemap, a property or a URL.
• Reach what your login cannot open. It runs as you.

How approval works

Nothing changes until you allow it in your AI client — approval is your client's own tool-permission prompt. If you tell your client to always allow a tool, it will run that tool without asking again — which is why the limits that hold either way are server-side: it cannot delete, it cannot publish a container, it will not switch on the campaign it built, and it asks for your budget before it builds.

So for a hard stop, set your AI client to ask before AdCopilot's write tools: Needs approval in Claude; in Cursor, set the run mode to Allowlist and keep them off the allowlist (Cursor's cloud agents never ask). Reads, including every performance query and every inspection, run without asking; they change nothing.

Connect it

Add the connector once, in Claude, ChatGPT or any MCP client, and sign in with Google. Search Console is its own consent beside Google Ads, granted in Google products, and connect it with a Google account that can open the property.

The short overview is on the Search Console page, and the tool reference is in the docs.

Google's own documentation

What the reads and writes above are built on, in Google's words:

• About Search Console. What the product is for and who it is for.
• Performance report (Search results). What clicks, impressions, click-through rate and position mean.
• Search Analytics query. The call behind the performance read, with its dimensions and limits.
• URL Inspection API: index.inspect. What an inspection returns about one URL.
• What is a sitemap. What a sitemap tells Google and what it does not promise.
• How to use the Indexing API. The pages the API acts on, in Google's own words.
• Google's guidance on requesting a recrawl. What works for an ordinary page, and how many requests a site owner may make.