Platform
Update

Search Console gets its first writes — submit and delete sitemaps

TL;DR

Search Console can now submit and delete sitemaps — its first write tools, found by a platform audit of the read-only integrations. The API had submission and deletion all along, 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.

How the audit found it

The audit 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? Search Console came back as the latter, which is the kind of gap worth closing rather than explaining.

★ Correction, 18 September 2026: this entry originally said AdSense and AdMob were read-only because their APIs have no write endpoints. That was the audit's conclusion and it was wrong — measured against the AdSense v2 reference, create and patch for ad units and create, patch and delete for custom channels have been there all along. See publisher write tools. The Search Console finding above is unaffected.

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.
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