seo/update-post-type-seo changes the Yoast settings for one post type: title and description templates, indexing, metabox visibility, schema defaults.
Each key is routed to the settings area that owns it, so a mixed patch still passes through the right validation.
At a glance
| Ability | seo/update-post-type-seo |
| Toolset | Yoast SEO — toolset/yoast-seo |
| Group | Yoast SEO › Content Types |
| 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 |
Routing a mixed patch
Yoast keys its per-content-type settings by suffix — title-{type}, metadesc-{type}, noindex-{type}, schema-page-type-{type} and so on — spread across several settings areas.
Which means a natural patch — a title template, an indexing flag and a schema type for one post type — spans three different option groups with three different validators.
Writing that through a single-area ability would mean three calls and knowing which key belongs where. This routes each key to its owner and writes each group once.
A key that belongs to no known area is refused rather than written somewhere plausible.
Read seo/get-post-type-seo first for the exact key names. They include the post type as a suffix, so they differ per type and are not guessable from a generic example.
Changing the indexing flag here also changes the type’s sitemap membership, since Yoast derives one from the other.
Idempotent.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
post_type | string | Yes | The post type. |
settings | object | Yes | A map of key to value. Keys are routed to their owning area. |
What comes back
| Name | Type | What it is |
|---|---|---|
updated | array | The keys that changed. |
settings | object | The area after the write. |
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:
Noindex the product post type and give it a title template.
It resolves to one call:
{
"ability": "seo/update-post-type-seo",
"parameters": {
"post_type": "product",
"settings": { "noindex-product": true }
}
}Worth knowing
- Keys include the post type as a suffix. Read them first.
- A mixed patch is routed to the right areas and validated per group.
- Changing indexing changes sitemap membership too.
- Idempotent.
Related abilities
- Get Post Type SEO Settings — get the exact key names
- Update Post Type Archive SEO — the archive, not the items
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category