seo/get-post-type-seo returns every Yoast setting that applies to one post type: its title and meta description templates, whether it is indexed, whether the metabox and schema controls show, and its default schema page and article types.
Gathered into one view, which is how the admin presents them and not how they are stored.
At a glance
| Ability | seo/get-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 | Read-only — changes nothing |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Abilities Manager 0.0.34 and later |
How it works
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.
So answering “how is the product post type configured” from raw settings means knowing seven key patterns and which area each lives in. This does that and returns the result as one object.
The schema defaults are the settings most often left at their generic values, and the ones with the clearest upside. A post type that is genuinely a news article, a recipe or an FAQ and is declared as a plain web page is eligible for nothing in particular.
The metabox visibility setting decides whether editors see Yoast’s controls on that type at all. Turning it off for an internal post type removes noise; turning it off for a public one removes the ability to set per-post SEO.
Read this before writing, since the write ability needs the exact key names.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
post_type | string | Yes | The post type. |
What comes back
| Name | Type | What it is |
|---|---|---|
settings | object | Every Yoast setting applying to that post type. |
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:
How is the product post type configured in Yoast?
It resolves to one call:
{
"ability": "seo/get-post-type-seo",
"parameters": {
"post_type": "product"
}
}Worth knowing
- Gathers settings stored by suffix across several areas.
- Schema defaults are the most often left generic and the easiest win.
- Hiding the metabox removes per-post SEO control for that type.
- Read this before writing — the writer needs exact key names.
Related abilities
- Update Post Type SEO Settings — change them
- List Content Type SEO Settings — all types at once
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category