seo/get-seo-status reports Yoast’s version and edition, whether sitemaps and the content analyses are on, whether indexables have been built, and the WordPress environment type.
It is the fastest answer to “why is Yoast not doing X” — most of those questions turn out to be the environment or an unbuilt index.
At a glance
| Ability | seo/get-seo-status |
| Toolset | Yoast SEO — toolset/yoast-seo |
| Group | Yoast SEO › Status & Tools |
| 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
The environment type is the field that resolves the largest share of confusing behaviour. Yoast changes what it does on non-production environments, indexation being the most visible — and a developer on a staging site sees features that appear broken and are working as designed.
Yoast keeps a table of indexables — one row per post, term, author, archive and system page — and that table is what archive titles, breadcrumbs and the internal-link reporting are read from. It is built by a background process, and an empty index is the usual reason those features return nothing.
The edition matters because a good deal of what people expect from Yoast is premium-only: redirects, multiple keyphrases, internal linking suggestions, the cannibalisation warning. An ability failing because a feature is not present looks the same as one failing for any other reason until you check.
Sitemaps and the analyses being on are the two master switches whose absence explains a whole category of “nothing is happening”.
One call, cheap, and worth making first.
Input
This ability takes no input.
What comes back
| Name | Type | What it is |
|---|---|---|
version | string | The installed Yoast version. |
edition | string | Free or premium. |
sitemaps_enabled | boolean | Whether XML sitemaps are on. |
analysis_enabled | object | Whether the SEO and readability analyses are on. |
indexables_built | boolean | Whether the indexable table is populated. |
environment_type | string | The WordPress environment 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:
Why is Yoast not doing anything on this site?
It resolves to one call:
{
"ability": "seo/get-seo-status",
"parameters": {}
}Worth knowing
- The environment type explains most staging-site confusion.
- A lot of expected behaviour is premium-only.
- An unbuilt index explains empty archives, breadcrumbs and link reporting.
- Make this the first call.
Related abilities
- Get Indexation Status — the index in detail
- Get Configuration Status — whether setup was finished
- List Conflicting Plugins — what else is emitting tags
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category