seo/update-schema-settings sets the default schema page type and article type per post type: what Yoast declares each kind of content to be in structured data.
A post left as the wrong article type is a common and invisible cause of rich results not appearing.
At a glance
| Ability | seo/update-schema-settings |
| Toolset | Yoast SEO — toolset/yoast-seo |
| Group | Yoast SEO › Settings |
| 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 |
Declaring what something is
Structured data works by claiming a type. A page declared as a WebPage is eligible for nothing in particular; the same page declared as an FAQPage or a NewsArticle is eligible for specific search features.
The defaults Yoast ships are safe and generic, which means a site whose posts are news articles, or whose pages are FAQ pages, is declaring them as something less specific and getting nothing for it.
Nothing reports this. The structured data is valid, it just claims less than it could, and the absence of a rich result is not an error anybody sees.
The reverse mistake is worse and equally silent: declaring a type the content does not match. A product page declared as a recipe validates cleanly and misleads.
These are defaults per post type. Individual posts can override them where Yoast exposes the control in the editor.
Idempotent.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
settings | object | Yes | A map of setting key to new value. Keys outside this area are refused. |
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:
Declare our news post type as news articles.
It resolves to one call:
{
"ability": "seo/update-schema-settings",
"parameters": {
"settings": { "schema-article-type-post": "NewsArticle" }
}
}Worth knowing
- The default types are safe and generic — and safe means eligible for nothing specific.
- Nothing reports a missed rich result. The absence is silent.
- Declaring a type the content does not match validates and misleads.
- Per post type; individual posts can override.
Related abilities
- Update Knowledge Graph Settings — the entity these reference
- Get Post Type SEO Settings — read the current defaults
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category