seo/list-content-type-settings lists every public post type and taxonomy on the site with a summary of its Yoast SEO configuration: whether it is indexed, whether it shows in the admin, and whether it has a title and description template.
It is the orientation call before tuning any single type.
At a glance
| Ability | seo/list-content-type-settings |
| 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.
Gathering them per type is how the admin presents them and how a caller thinks about them — but it is not how they are stored, which is why a direct settings read does not produce this view.
The orientation value is in the pattern rather than any single row. A site with fifteen public post types, half of them registered by plugins and none of them configured, has a specific and common problem: types that are indexed by default and advertised to search engines without anybody deciding they should be.
The missing-template column is the other pattern worth looking for. A type with no title template falls back to a generic default, which on an important content type is a wasted opportunity repeated across every item.
Input
This ability takes no input.
What comes back
| Name | Type | What it is |
|---|---|---|
content_types | array | Each public post type and taxonomy with its indexing, admin visibility and template state. |
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 each of our content types configured for SEO?
It resolves to one call:
{
"ability": "seo/list-content-type-settings",
"parameters": {}
}Worth knowing
- Per-type settings are stored by key suffix across several areas, not grouped.
- Plugin-registered types indexed by default are the common problem.
- A missing template is a wasted opportunity repeated across every item.
- Read-only.
Related abilities
- Get Post Type SEO Settings — one type in full
- Get Taxonomy SEO Settings — one taxonomy in full
- List Sitemap Coverage — the sitemap consequence
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category