Search Console gets its first writes — submit and delete sitemaps
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
webmastersscope 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.
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.
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.
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.