litespeed/get-crawler-map returns a page of the sitemap the crawler works from, along with the total URL count.
If it is empty, the crawler has nothing to do — which is the usual explanation for a crawl that appears to finish instantly.
At a glance
| Ability | litespeed/get-crawler-map |
| Toolset | LiteSpeed Cache — toolset/litespeed |
| Group | LiteSpeed Cache › The Crawler |
| Requires | LiteSpeed Cache, 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
The crawler does not discover pages. It works from a stored map, generated from the sitemap the configuration points at, and if that generation never ran or produced nothing, the crawler runs correctly over zero URLs and reports success.
That is a confusing state: the crawler is enabled, runs on schedule, completes every time, and warms nothing. The total count here is the one number that makes it obvious.
It is also worth reading for size. A map of a hundred thousand URLs will not be crawled within any useful interval, and the practical answer is a narrower sitemap rather than a more aggressive crawler.
Paging is by limit and offset, because the whole map is rarely what you want.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
limit | integer | No | How many URLs to return. |
offset | integer | No | Where to start. |
What comes back
| Name | Type | What it is |
|---|---|---|
urls | array | A page of the sitemap. |
total | integer | How many URLs the map holds in total. |
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 is the crawler actually going to visit?
It resolves to one call:
{
"ability": "litespeed/get-crawler-map",
"parameters": {
"limit": 20
}
}Worth knowing
- An empty map explains a crawl that finishes instantly.
- A very large map will never be fully crawled on a normal interval.
- The crawler does not discover pages — it reads this map.
Related abilities
- Get Crawler Status — where in this map it has reached
- Reset The Crawl Position — start from the beginning again
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category