rank-math/clear-indexing-log permanently deletes the entire IndexNow submission history. It refuses without confirm: true.
There is no partial clear and no undo.
Before you run it
The log is the only record of what was submitted and when. Nothing else on the site keeps it, and it cannot be recovered. If submissions are currently failing, the pattern of response codes in the log is the evidence for why — clearing it discards the diagnosis along with the history. Read it first with rank-math/get-indexing-log.
At a glance
| Ability | rank-math/clear-indexing-log |
| Toolset | Rank Math — toolset/rank-math |
| Group | Rank Math › Instant Indexing |
| Requires | Rank Math SEO, active on the site |
| Capability | manage_options |
| Safety | Destructive — deletes stored values, and refuses to run without confirm: true |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Abilities Manager 0.0.34 and later |
How it works
The legitimate reason to clear is size. On a busy site with auto-submission enabled the log grows continuously, and a log with tens of thousands of entries is both slow to read and useless to look at.
The illegitimate reason is to make a problem go away. A log full of 403s is a key file that cannot be fetched, and clearing it produces an empty log and the same broken submissions.
So read it first, and specifically read the response codes. If they are all 200, clearing loses nothing you need. If they are not, the log is the diagnosis.
Idempotent: clearing an empty log is a no-op.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
confirm | boolean | Yes — must be true | The irreversibility gate. Without it the call is refused before anything is touched. |
What comes back
| Name | Type | What it is |
|---|---|---|
deleted | integer | How many entries were removed. |
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:
Clear the IndexNow log — it has got huge.
It resolves to one call:
{
"ability": "rank-math/clear-indexing-log",
"parameters": {
"confirm": true
}
}Worth knowing
- Read the response codes before clearing. They are the diagnosis.
- No partial clear and no undo.
- Size is the legitimate reason; hiding a failure is not.
- Idempotent.
Related abilities
- Get IndexNow Submission Log — read it first
- Reset IndexNow API Key — if the codes say 403
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category