seo/get-indexation-counts reports how many indexables exist per object type: posts, terms, users, archives and system pages.
The numbers are only meaningful against the real content counts.
At a glance
| Ability | seo/get-indexation-counts |
| Toolset | Yoast SEO — toolset/yoast-seo |
| Group | Yoast SEO › Indexation |
| 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
Indexation builds incrementally, so a count that is lower than the content count means work outstanding rather than something broken. A site with four thousand posts and twelve hundred post indexables is a third of the way through.
A count of zero for a type that clearly has content is the more interesting case: either indexation has never run, or it is refusing to — which seo/get-indexing-status explains.
Counts higher than the content are possible too, and mean orphaned indexables: rows left behind by posts and terms that were deleted. seo/cleanup-indexables reports those specifically.
The per-type breakdown matters because indexation covers types in passes. A site can have every post indexed and no terms, which produces working post SEO and empty term archives.
Input
This ability takes no input.
What comes back
| Name | Type | What it is |
|---|---|---|
counts | object | How many indexables exist per object 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 much of the site has Yoast indexed?
It resolves to one call:
{
"ability": "seo/get-indexation-counts",
"parameters": {}
}Worth knowing
- Lower than the content count means work outstanding.
- Zero for a populated type means indexation is not running.
- Higher than the content count means orphaned rows.
- Indexation covers types in passes — partial coverage is normal mid-run.
Related abilities
- Get Indexation Status — why it is where it is
- Report Orphaned Indexables — the excess
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category