litespeed/update-crawler-settings changes the crawler configuration: enable it, set the crawl interval and server load limit, choose the sitemap, and set the roles and cookies it simulates.
A load limit set too high will slow the site for real visitors while a crawl runs.
At a glance
| Ability | litespeed/update-crawler-settings |
| Toolset | LiteSpeed Cache — toolset/litespeed |
| Group | LiteSpeed Cache › The Crawler |
| Requires | LiteSpeed Cache, 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 |
The load limit is the setting that matters
A crawl warms the cache by visiting pages, and visiting pages costs exactly what a visitor costs. On a large site a crawl is a sustained load spike that the site’s real visitors share, which is why the load limit exists and why crawls are usually scheduled for quiet hours.
The limit is a server load average above which the crawler pauses. Set it low and the crawl takes longer and nobody notices it; set it high and the crawl finishes quickly at the expense of the people using the site.
On shared hosting the right value is usually lower than it looks, because the load figure includes neighbours you cannot see.
Changing the roles or cookies changes how many variants exist, and therefore how long a full crawl takes. Adding one role can double it. Check litespeed/list-crawlers after any change here.
Changing the sitemap should be followed by litespeed/reset-crawler, since the stored crawl position refers to a position in the old sitemap.
The write is a patch, not a replacement. Send one key and one key changes; everything else in the area is left alone. The response names the keys that actually moved, so a payload that matched the existing values comes back with an empty list rather than a misleading success.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
settings | object | Yes | A map of setting key to new value. Keys outside this area are refused, and the refusal lists what the area accepts. |
What comes back
| Name | Type | What it is |
|---|---|---|
updated | array | The keys that actually changed. An empty array means every value you sent was already set. |
settings | array | Every setting in the area after the write, in the read shape. |
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:
Lower the crawler load limit so it does not slow the site.
It resolves to one call:
{
"ability": "litespeed/update-crawler-settings",
"parameters": {
"settings": { "crawler-load_limit": 1 }
}
}Worth knowing
- On shared hosting, set the load limit lower than seems necessary.
- Adding a role or cookie multiplies the crawl length.
- Reset the crawl position after changing the sitemap.
- A patch — unsent keys are untouched.
Related abilities
- List Crawlers — see how many variants you just created
- Reset The Crawl Position — after changing the sitemap
- Get Crawler Status — watch the effect
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category