seo/get-indexable returns the computed SEO output for any page that is not a single post: the home page, the blog page, a post type archive, an author archive, a term archive or the search results.
These are the pages whose titles come from templates rather than from anything editable per page.
At a glance
| Ability | seo/get-indexable |
| Toolset | Yoast SEO — toolset/yoast-seo |
| Group | Yoast SEO › Archives & System Pages |
| 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 ships abilities of its own for single posts. This suite fills in what those cannot reach rather than duplicating them.
What those cannot reach is everything that is not a post — and on most sites that is a large share of the indexed pages. Every category archive, every author page, the blog index, the search results.
Yoast titles and descriptions are templates — patterns like %%title%% %%sep%% %%sitename%% expanded per page — rather than literal strings.
For a post, the template is a fallback behind a per-post override. For these pages there is no per-post anything: the template is the title, which makes reading the computed output the only way to know what they say.
The computed output is the resolved result — variables expanded, fallbacks applied — rather than the stored template. That distinction is the whole value: a template containing %%term_title%% tells you very little, and the expansion tells you what a search engine reads.
Reading a kind requires that kind to be indexed. 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.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
kind | string | Yes | Which kind of indexable, from seo/list-indexables. |
subject | string | integer | Depends on the kind | What identifies it — a term ID, an author ID, a post type name, and so on. |
What comes back
| Name | Type | What it is |
|---|---|---|
seo | object | The computed title, description, canonical, robots directives and social tags. |
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:
What title does our category archive actually use?
It resolves to one call:
{
"ability": "seo/get-indexable",
"parameters": {
"kind": "term-archive",
"subject": 87
}
}Worth knowing
- These pages have no per-page override. The template is the whole answer.
- The output is resolved, not the stored template.
- Needs the relevant indexables built.
- Read-only.
Related abilities
- List Indexable Kinds — what to pass
- Update Title And Meta Templates — change what they say
- Get Indexation Status — if it returns nothing
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category