litespeed/update-guest-mode turns guest mode on or off.
Guest mode serves a pre-built page to a first-time visitor immediately, then replaces it with their real page once that is ready.
At a glance
| Ability | litespeed/update-guest-mode |
| Toolset | LiteSpeed Cache — toolset/litespeed |
| Group | LiteSpeed Cache › Page Cache |
| 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 trade it makes
A first-time visitor has no cookies, so LiteSpeed cannot know which cached variant they should get and normally has to build the page. Guest mode short-circuits that: everybody new gets the same pre-built page instantly, and the correct page arrives immediately after.
The gain is real and shows up directly in first-visit metrics, which are the ones search engines measure.
The cost is that the first thing a new visitor sees is a generic page. On a site where the variants differ visibly — a currency, a language, a location-based banner — that flash of the wrong thing is noticeable, and on a slow connection it is not brief.
So the right answer depends on how much the variants differ. A site whose pages look the same to everyone loses nothing; a site with visible personalisation may.
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:
Turn on guest mode.
It resolves to one call:
{
"ability": "litespeed/update-guest-mode",
"parameters": {
"settings": { "guest": true }
}
}Worth knowing
- Helps first-visit speed, which is what page-experience metrics measure.
- Shows a generic page briefly. Noticeable when variants differ visibly.
- Test on a slow connection, where the flash lasts longest.
- Purge afterwards.
Related abilities
- Get Cache Settings — the surrounding configuration
- Update Cache Scope — who else gets cached
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category