Agent PlannersAgent Planners
Platform
Update

Search Console gets its first writes — submit and delete sitemaps

TL;DR

A platform audit found one genuine gap among the read-only integrations. AdSense and AdMob are read-only because their APIs have no write endpoints — that is the shape of the product. Search Console was different: it has sitemap submission and deletion, we had been listing sitemaps since June, and the agent could watch a feed error without being able to do the one thing that fixes it.

What shipped

  • `submit_sitemap` — resubmit a sitemap after a content release, or after seeing one error.
  • `delete_sitemap`, for removing one that should no longer be crawled.
  • The `webmasters` scope is now requested by default on new connections, alongside the read-only one.
  • Sixteen redundant calls removed from the read path, which were asking Google the same question repeatedly within a single run.
Neither write carries a fence, and the reasoning is stated in the module rather than assumed: a submission is a hint Google acts on when it chooses, and a deletion is undone by submitting again. A gate is for changes you cannot walk back.

The scope detail, and what it means for existing connections

Reading Search Console uses `webmasters.readonly`. Submitting or deleting a sitemap needs `webmasters` — a different, broader scope, not a superset the read grant happens to include. A connection authorized before this release therefore carries read access only, and the API's refusal reads like a generic permissions error rather than "the scope you granted months ago does not cover this".

If your Search Console connection predates this release, reconnect it once to pick up the write scope. New connections get both.

An older connection may also carry no record of which scopes were granted at all. Absent is not the same as missing — the only reliable signal is what the API actually answers, so the refusal is translated from Google's own response rather than from a stored field that may never have been written.

Why this was the only real gap

The audit that found it asked a narrow question of every read-only integration: is this read-only because the API has no writes, or because we never built them? AdSense and AdMob came back as the former — they are reporting APIs, and a write tool would be inventing an endpoint. Search Console came back as the latter, which is the kind of gap worth closing rather than explaining.

Frequently asked questions

Can an AI agent submit a sitemap to Search Console?
Yes — submit_sitemap and delete_sitemap both exist now. Neither sits behind a fence, because a submission is a hint Google acts on when it chooses and a deletion is undone by submitting again.
Why can't my existing Search Console connection submit a sitemap?
Reading uses the webmasters.readonly scope and writing needs the broader webmasters scope. Connections made before this release carry read access only — reconnect once and the write scope is included by default.
Why are AdSense and AdMob still read-only?
Because their APIs are reporting APIs with no write endpoints. That is the shape of the product rather than a gap in the integration, which is exactly the distinction the audit was drawing.
Try it on your own account

Start free — 2,500 credits a month, no credit card. Reads are free, and every write waits for your approval.

Related releases

September 16, 2026
Merchant Center can write
The Shopping integration was read-only. It now inserts and removes products, creates and fetches data sources, and pushes a feed — with a safety fence drawn on what a shopper actually sees.
September 16, 2026
Data Manager uploads offline conversions straight from a query
Offline conversion events now upload from a SELECT's own rows, with no file in between. Data Manager also stopped being an 11-pixel link under a disconnect button.
September 11, 2026
DV360 and CM360 get threshold alerts
Alert rules now cover DV360 and Campaign Manager 360. The reason they were excluded was a property of the alert loop, not of those platforms, so the loop was fixed rather than the platforms special-cased.