Google Search Console
Manage Search Console sites and sitemaps, run Search Analytics queries, and inspect a URL's index status.
About
Google Search Console ships in the w6w first-party pack. It declares 10 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.googlesearchconsole- Version
- 0.1.1
- Author
- w6w
- Licence
- MIT
- Categories
- Marketing · Analytics & BI
Overview
Google Search Console is where a site owner sees how Google Search treats their site — what it indexes, what ranks, what breaks. This app runs the same operations the Search Console UI does, so they can be scripted or scheduled instead of clicked through.
Manage the property list itself: list every site the connected account can see, look up one site’s permission level, add a new site (a sc-domain: domain property or a URL-prefix property), or remove one. Inspect and maintain sitemaps: list what has been submitted for a site (or read the entries inside a sitemap index), fetch one sitemap’s processing status and error/warning counts, submit a new sitemap, or delete one. Run a Search Analytics query — clicks, impressions, CTR and position, grouped by date, query, page, country or device, with dimension filters and paging — the same data behind the Performance report. Run a URL Inspection to see whether a specific URL is indexed, which canonical Google chose, whether robots.txt or a noindex rule blocks it, and when it was last crawled.
Good for auditing sitemap health after a migration, watching a URL’s indexing status until it clears, pulling ranking data into a dashboard on a schedule, or provisioning a new property as part of a site-launch workflow — all without opening search.google.com/search-console.
Build with Google Search Console
Three routes to the same 10 actions. The Workflow tab is generated from Google Search Console's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Query Search Analytics
search-analytics-query Run a Search Analytics query — clicks, impressions, CTR and position.
List sitemaps
sitemap-list List the sitemaps submitted for a site, or the entries inside a sitemap index.
Inspect a URL
url-inspection-inspect Check a URL's indexing status: coverage, canonical, robots.txt, last crawl.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Google Search Console's real ids.
{
"manifestVersion": "2",
"name": "googlesearchconsole-example",
"steps": [
{
"id": "search-analytics-query",
"uses": {
"app": "io.w6w.googlesearchconsole",
"action": "search-analytics-query",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"startDate": "<startDate>",
"endDate": "<endDate>"
}
}
]
}Here are some of the things you can do
-
Query Search Analytics
readsearch-analytics-query -
Add a site
performsite-add -
Get a site
readsite-get -
List sites
readsite-list -
Get a sitemap
readsitemap-get
+5 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Google Search Console, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Google Search Console. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "search-analytics-query",
payload: {
// siteUrl: "<value>",
startDate: "<value>",
endDate: "<value>",
// dimensions: "<value>",
// type: "<value>",
// aggregationType: "<value>",
// dataState: "<value>",
// rowLimit: "<value>",
// startRow: "<value>",
// dimensionFilterGroups: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action search-analytics-query --payload '{"startDate":"<value>","endDate":"<value>"}'Give an AI agent Google Search Console — without giving it Google Search Console's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.googlesearchconsole#search-analytics-query",
"input": {
"startDate": "<startDate>",
"endDate": "<endDate>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Google Search Console connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Google Search Console's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Google Search Console itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Google Search Console declares its own checks, so its health is a property of the app rather than something the host guesses at.