agentsgyagentsgym
Open dashboard

Integrations/Google Search Console

Google Search Console + agentsgym

A separate, opt-in connection to your Search Console properties: search analytics, URL Inspection and sitemap submission — asked for after sign-up, never during it, and revocable from your Google account in two clicks.

Facts checked 2026-10-22. Prices and limits are the vendor's published numbers on that date.

Search Console is the only source that tells you which queries Google actually showed you for — and which submitted pages it has refused to index. agentsgym connects to it opt-in: the connection is a button in settings, not a step in sign-up.

Connecting

  1. Sign in to agentsgym (sign-in itself never touches Search Console).
  2. Open Settings → Search Console and press Connect. You go to Google’s consent screen for one scope.
  3. Approve https://www.googleapis.com/auth/webmasters. You return to agentsgym with every site matched to its property and its sitemap submitted once.

That is the whole flow. The consent asks for access_type: offline so Google returns a refresh token, which is what lets the daily job read your data without you being logged in.

What we can and cannot do with it

Scope requested https://www.googleapis.com/auth/webmasters (read and write)
We read Your Search Console properties, search analytics, sitemaps, and URL Inspection results
The one write sitemaps.submit — on connect, on a property change, and when you or your agent press Submit sitemap. Every submission is logged on the site
We never Add or remove properties, delete sitemaps, change settings, or Request indexing (no API exists for that button — it stays manual)
Property per site Auto-matched by domain (Domain property first, closest ancestor next, then URL-prefix); a picker on each site page overrides it
Where the token lives Encrypted server-side against your account; never exposed to the browser or to another user
Revoke Settings → Disconnect, or Google Account → Security → Third-party access

Submitting a sitemap

Submit sitemap on a site’s Indexing card, or the submit_sitemap tool over MCP, does this in order:

  1. Submits the sitemap (/sitemap.xml or /sitemap-index.xml, or the URL you give) with sitemaps.submit.
  2. Reads it back: last submitted, last downloaded, warnings and errors.
  3. Runs URL Inspection on up to 10 of the URLs it lists and shows how many are indexed.

Each attempt, including a refusal from Google, is logged against the site.

What the dashboard shows today

Submitted pages Google has not indexed, reconstructed from your sitemaps + the URL Inspection API (the public API has no Pages report). Reasons are grouped the way Search Console groups them; each URL links to Inspect so you can Request indexing yourself (there is no API for that button). Per-query and per-page impressions/clicks are still the next release.

Domain Rating, referring domains, cookieless traffic and AEO scans all work without connecting anything.

Why bother at all

Because the three data sets answer different questions, and only together do they explain a flat month:

  • Authority (Domain Rating, referring domains) — is the domain gaining weight?
  • Search Console — is Google showing the pages, and for what?
  • First-party analytics — did anyone actually arrive and land where you wanted?

Once your agent can read all three, “why did nothing happen this month” becomes an answerable question — see Claude Code + agentsgym.

Questions

What permission does agentsgym ask for?
One scope: https://www.googleapis.com/auth/webmasters (read and write). Google describes it as seeing, editing, creating and deleting your Search Console data. agentsgym uses exactly one write call, submitting a sitemap (sitemaps.submit), and reads everything else: search analytics, sitemaps, URL Inspection.
Why read and write, not read-only?
Submitting your sitemap is the one supported way to tell Google about your pages by API, and it needs the write scope. agentsgym submits it once when you connect, when a property is assigned to a site, and when you or your agent press Submit sitemap. Each submission is logged on the site; nothing else in your Search Console is ever changed.
Can agentsgym click Request indexing for me?
No. Google has no public API for Request indexing; the Indexing API covers only job postings and livestreams. That button stays manual in Search Console. The supported path is the sitemap: agentsgym submits it, reads it back (last submitted, last downloaded, warnings) and runs URL Inspection on the listed URLs, so you see what Google did instead of assuming it.
How is each site matched to a property?
Automatically by domain: the Domain property of the host (sc-domain:example.com), then the closest ancestor Domain property (t.example.com falls under sc-domain:example.com), then an https URL-prefix property. You can pick or change the property per site on the site page.
Why is it a separate step from signing in?
Google requires app verification before more than 100 users may grant that scope. Keeping it off the sign-up path means the review never blocks registration — you can use agentsgym fully without ever connecting Search Console.
How do I disconnect?
Disconnect from the settings page, or revoke agentsgym under your Google Account permissions. Either kills the refresh token for agentsgym.

Try it on your own domain

One project is free: a daily Domain Rating reading, referring domains, cookieless pageviews and AEO scans — all readable by your agent over MCP.

Check a site free