seo/run-indexing marks Yoast’s indexation as needing to run, so it rebuilds on its next scheduled pass.
It deliberately does not rebuild synchronously.
At a glance
| Ability | seo/run-indexing |
| Toolset | Yoast SEO — toolset/yoast-seo |
| Group | Yoast SEO › Indexation |
| Requires | Yoast SEO, active on the site |
| Capability | manage_options |
| Safety | Writes data |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Abilities Manager 0.0.34 and later |
Why it will not do it now
A full index on a large site takes far longer than a request is allowed to run. An ability that tried would time out, and the timeout would leave the indexable table half rebuilt — which is worse than not having started, because partially built indexables produce partially correct output with no indication that anything is wrong.
So the request sets a flag and returns. The background process picks it up on its next pass and works through the site incrementally, which is what that process is designed for.
Poll seo/get-indexing-status for progress. On a large site, expect it to take a while — indexation is throttled specifically so that it does not compete with real traffic.
On a non-production environment this does nothing, because Yoast refuses to index there. The request succeeds and no indexation ever happens, which is why the status read is the first place to look when nothing seems to be progressing.
Idempotent: requesting twice does not queue two runs.
Input
This ability takes no input.
What comes back
| Name | Type | What it is |
|---|---|---|
requested | boolean | Whether indexation was marked as needed. |
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:
Rebuild the Yoast index.
It resolves to one call:
{
"ability": "seo/run-indexing",
"parameters": {}
}Worth knowing
- Asynchronous by design. A synchronous attempt would time out and corrupt the table.
- Does nothing on a non-production environment.
- Poll the status ability for progress.
- Idempotent.
Related abilities
- Get Indexation Status — watch it progress
- Reset Indexation — start from the beginning instead
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category