seo/update-sitemap-settings turns the XML sitemap on or off.
That is all it does, because that is all there is to configure. Which content appears is derived from indexing rather than set here.
At a glance
| Ability | seo/update-sitemap-settings |
| Toolset | Yoast SEO — toolset/yoast-seo |
| Group | Yoast SEO › XML Sitemaps |
| Requires | Yoast SEO, active on the site |
| Capability | manage_options |
| Safety | Writes data |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Abilities Manager 0.0.34 and later |
How it works
The narrowness is the design. Yoast’s sitemap has exactly one switch, and everything else about it follows from settings that live elsewhere and mean something in their own right.
Turning the sitemap off is rarely correct. The usual reason people do it is a conflict with another plugin generating its own sitemap, and the better fix there is to stop the other plugin — two sitemaps at different URLs is a configuration that confuses search engines and the people maintaining the site equally.
The other reason is a site that should not be crawled at all, which is better expressed through the search-engine visibility setting than by hiding the sitemap.
Turning it on when it has been off for a while is worth following with a fresh submission in Search Console, since the previous fetch will have failed and the schedule backs off after failures.
Idempotent.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
enabled | boolean | Yes | Whether the XML sitemap is served. |
What comes back
| Name | Type | What it is |
|---|---|---|
enabled | boolean | The state afterwards. |
success | boolean | Whether the call completed. |
message | string | A one-line summary of what happened, suitable for showing a human. |
error_code | string | Present only on failure — a stable machine-readable reason, such as a missing field, a wrong field type or an unmet confirmation. |
Example
Ask your assistant:
Turn the XML sitemap back on.
It resolves to one call:
{
"ability": "seo/update-sitemap-settings",
"parameters": {
"enabled": true
}
}Worth knowing
- Inclusion is not configurable here. It follows indexing.
- Two plugins generating sitemaps is the problem; disabling one sitemap is the workaround.
- Resubmit in Search Console after re-enabling.
- Idempotent.
Related abilities
- Update Archive And Indexing Settings — change what is in it
- List Conflicting Plugins — find the other sitemap
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category