# Find out why WordPress pages are not cached with Grok Bot

> Finding out why pages are not cached with Grok Bot means attaching xSpeed Hub to a Bot, letting it read the cache status and a benchmark, and having it confirm the result from the terminal on its own cloud computer.

Page: https://xspeedcache.com/agent/grok-bot/troubleshoot-cache/
Last updated: October 2026

You checked shop from your laptop with curl -I, saw BYPASS on every request, and assumed the cache was dead. Before you touch a setting, you hand the question to a Bot. Type @ in the chat to attach the xspeedhub plugin, then ask it to use xSpeed Hub to find out why shop says BYPASS. A plugin you added from your own chat is personal and account-wide, so any Bot on your account can take the question.

The Bot reads get_cache_status and runs run_benchmark. Caching is on, the hit ratio is healthy and the cached request was a hit. That contradicts what you saw, and the explanation is the command. curl -I sends a HEAD request, xSpeed serves only GET requests from cache, and so a HEAD request reports BYPASS even on a healthy site. Grok Bot's cloud computer has a terminal, so the Bot can show the difference instead of asserting it: two plain GET requests to the same page return MISS and then HIT in the X-XSpeed-Cache header. Nothing was wrong, and nothing needed changing.

If the benchmark had failed, the next read would be get_health, one site per call, and the Bot would quote the failing check. The same pattern works as a routine. A Bot can run a report-only cache check on a schedule on its cloud computer while your laptop is closed, and post the result in the chat. Ask it to list the checks it ran in each report, so a quiet morning reads as a pass and not as a run that never happened.

## Set up Grok Bot once

### 1. Put your sites in xSpeed Hub

Sign in at app.xspeedcache.com with Google or email; the Hub is free and has no site cap. Then connect each WordPress site from its own dashboard: click Connect Hub in the xSpeed Cache top bar, then Connect via xSpeed Hub. Each site needs the free xSpeed Cache plugin.

### 2. Ask your Bot to add xSpeed Hub

In a chat with your Bot, ask it to add a custom remote HTTPS MCP server with this URL. xAI says a plugin you add from your own chat is personal and account-wide, so every Bot on your account can use it. When the browser opens, approve access on the xSpeed Hub page.

```
Add a custom remote HTTPS MCP server called xspeedhub with the URL https://app.xspeedcache.com/xspeed/mcp and sign me in.
```

### 3. Attach it and ask a first question

Type @ in a chat to attach the xspeedhub plugin to the task, then ask something that names xSpeed Hub. A list of your sites means the connection works.

```
Use @xspeedhub (xSpeed Hub) to list my sites and tell me which ones have page caching turned off.
```

Full setup: https://xspeedcache.com/agent/grok-bot/

### Before you send a prompt that changes something

Reads change nothing on your sites, though contact_support emails xSpeed support. Writes run once your connection allows them, so your client's approval prompt and a read-only connection (the token's Read-only everywhere switch, or a Viewer sign-in) are the gates that matter. When an action needs approval, Grok Bot offers Allow once, Always allow or Deny. Always allow saves a rule, so the same kind of call no longer stops for you. Auto-review rules under Settings, General, Auto-review can force Ask first or allow matching actions automatically, and Ask first wins when both match. xSpeed Hub has no confirmation step of its own, so a Hub write tool you always allow runs as soon as your connection allows writes. Add Ask first rules for purge_cache, update_settings, toggle_cache, optimize_site and the other write tools. For read-only access, sign in as a Viewer member of the workspace.

## Prompts

- Use @xspeedhub (xSpeed Hub) to check whether shop is really cached, then confirm it with two plain GET requests from your terminal.
- With xSpeed Hub, run the benchmark on every site and list any where the cached request was not a hit.
- Every weekday at 8:00 AM, use xSpeed Hub to read the cache status of each site and report any with caching off. Report only.

## Example session

```
You: Use @xspeedhub (xSpeed Hub) to find out why shop says BYPASS on every request I make with curl -I.
  → get_cache_status(site: shop) [read-only]: page cache on, 233 cached pages, hit ratio 72% in the last 24h
  → run_benchmark(site: shop) [read-only]: home page: 518 ms uncached, 57 ms cached, cached request was a hit
Agent: Caching works. curl -I sends a HEAD request, and xSpeed only serves GET requests from cache, so HEAD always reports BYPASS. I requested the home page twice from my terminal with a plain GET: the X-XSpeed-Cache header said MISS, then HIT.
You: So nothing to fix?
Agent: Nothing to fix. Check with a plain GET next time, or ask me and I will.
```

## How it works

1. **Start with the quick summary**: get_cache_status returns whether page caching is on, the stats (cached pages, size, hit ratio, last purge) and the web server xSpeed detected. It is a glance. If caching is off, or the hit ratio is far below what you expect, the agent moves on to the diagnostic.
2. **Run the diagnostic**: get_health is the tool for troubleshooting. It returns the environment checks with pass or warn tones (the advanced-cache.php drop-in, the WP_CACHE constant, rewrite rules, PHP and WordPress versions, caching plugin conflicts), the cache stats, 24 hourly hit and miss buckets and a 30-day hit-ratio series. The Hub tells the agent to use it, not get_cache_status, when you are troubleshooting rather than glancing.
3. **Time cached against uncached**: run_benchmark requests the home page once with the cache bypassed and once normally, after a warm-up request, and returns the timings. If the second request still is not a cache hit, the page cache is not serving the home page, and the result says so. It measures xSpeed's own response time. It does not return a Lighthouse score.
4. **Read what the checks mean**: A warn is a lead, not always a fault. A static-file rewrite warning, for example, can mean the nginx snippet is not in your server config yet, or that xSpeed could not verify it, which is not evidence the config is wrong. The agent reads the detail line and tells you which one it is.
5. **Fix it or hand it over**: If caching is simply off, toggle_cache turns it on. If another caching plugin owns the drop-in, the site refuses to enable xSpeed and says why; removing the other plugin is yours to do. If nothing explains it, contact_support emails xSpeed support with the agent's summary, after the agent has confirmed the message with you.

## Reference

| | |
| --- | --- |
| Quick check | get_cache_status (read): cache on or off, stats, detected web server |
| Diagnostic | get_health (read): environment checks, 24 hourly buckets, 30-day hit-ratio series, recent activity |
| One site per call | get_health does not accept site: "all"; call it for each site you care about |
| Benchmark | run_benchmark (read): home page only, cache bypassed against cache served, timings in milliseconds |
| Benchmark on every site | run_benchmark accepts site: "all" or a list of handles, one result per site |
| Benchmark history | get_benchmark_history reads past runs and the settings changes on the same timeline |
| Pro suggestions | get_pro_audit (read): which Pro features would help this site, from its settings and stats |
| Hit ratio scope | Counts requests that reach your server; pages answered by a CDN or Cloudflare edge are not counted |
| Support | contact_support emails xSpeed support with your account email and site list attached; classed read |
| Turning caching on | toggle_cache (write); refused by the site when another plugin owns the cache drop-in |

## Rules

- Diagnose with the read tools first. get_cache_status, get_health, run_benchmark and get_pro_audit change nothing on the site, so a read-only connection can run all of them. For clients that send the connection token, that means Read-only everywhere on; an OAuth sign-in gets the scopes the client asks for, unless the member is a Viewer.
- Do not answer a PageSpeed question with run_benchmark. It measures cached against uncached response time and returns no Lighthouse score; for a score, use the speed test or scan jobs.
- toggle_cache is a write. It runs as soon as your connection allows writes, and the Hub tells the agent to confirm the target site first. That is guidance to the agent, so your client's approval prompt is the gate that matters.
- contact_support sends a real email. The Hub tells the agent to confirm the message with you before sending, but the tool is classed read, so even a read-only connection can send one.
- The agent cannot edit your server configuration or another plugin's settings. When a check needs an nginx snippet or a conflicting plugin removed, it tells you what to do and you do it.

## Good to know with Grok Bot

Grok Bot offers Allow once, Always allow or Deny when an action needs approval, and Always allow saves a rule for that kind of call. For the reads in this job, saving rules is reasonable. Do not save one for contact_support or toggle_cache. contact_support emails xSpeed support and the Hub classes it as a read, so even a Viewer sign-in does not stop it, and the Hub's request that the agent confirm the message with you first is guidance to the model. Add Ask first rules for both under Settings, General, Auto-review; Ask first wins over an automatic allow. A routine's Test run does real work and can call connected tools, so test with the report-only prompt. If your team's Cursor connector policy blocks the plugin, it shows as Disabled by team admin until an admin allows it.

## More prompts for this job

They work in any client connected to xSpeed Hub.

- Using xSpeed Hub, why is the cache hit ratio so low on shop? Run the full health check and tell me the most likely cause.
- Using xSpeed Hub, is page caching actually working on blog? Benchmark cached against uncached and tell me if the second request was a hit.
- xSpeed Hub's get_health on docs shows a warning about the static-file rewrite. What does it mean and do I need to act?
- Use xSpeed Hub to check whether another caching plugin is conflicting with xSpeed on shop.
- Caching looks off on the staging site. Use xSpeed Hub to turn it on and tell me if the site refuses.
- Using xSpeed Hub, which Pro features would help the shop site, based on how it is set up now?
- With xSpeed Hub, compare the last few benchmark runs on blog and tell me whether my settings changes helped.

## Frequently asked questions

### Can Grok Bot check the X-XSpeed-Cache header itself?

Yes. Its cloud computer has a terminal, so it can request your page with a plain GET and read the header, next to the cache status and benchmark it reads through xSpeed Hub. Avoid HEAD requests such as curl -I, which report BYPASS even on a healthy site.

### Should I choose Always allow for the xSpeed tools in Grok Bot?

For the read tools used in troubleshooting, that is reasonable. For toggle_cache and contact_support, keep an Ask first rule, because xSpeed Hub has no confirmation step of its own and contact_support sends a real email.

### Why are my WordPress pages not being cached?

The common causes are that page caching is switched off, the advanced-cache.php drop-in or the WP_CACHE constant in wp-config.php is missing, another caching plugin owns the drop-in, or the pages set cookies or headers that make them uncacheable. An agent can read all of these from get_health through xSpeed Hub and tell you which one applies to your site.

### What is the difference between get_cache_status and get_health?

get_cache_status is a quick summary: whether caching is on, the stats and the detected web server. get_health is the diagnostic. It adds the environment checks with pass or warn tones, 24 hourly hit and miss buckets and a 30-day hit-ratio series. The Hub tells the agent to use get_health when you are troubleshooting.

### Does run_benchmark give me a PageSpeed score?

No. run_benchmark measures how fast your own cache answers compared with an uncached request for the home page. For a Lighthouse score, ask for a speed test or a speed scan instead.

### Can the agent check every site at once?

Only partly. run_benchmark accepts every site in one call. get_cache_status and get_health take one site per call, and get_health does not accept site: "all", so for a fleet the agent calls them site by site or you use the Hub dashboard for the rollup.

### Will troubleshooting change anything on my site?

Not with the diagnostic tools. They are read tools and change nothing. Changes only happen if the agent calls a write tool such as toggle_cache, which runs once your connection allows writes, so your AI client's approval prompt and a read-only connection (the connection token with Read-only everywhere on, or a Viewer sign-in) are the gates.

## Find out why pages are not cached with other agents

[Claude Code](https://xspeedcache.com/agent/claude-code/troubleshoot-cache/) · [Claude](https://xspeedcache.com/agent/claude/troubleshoot-cache/) · [Claude Cowork](https://xspeedcache.com/agent/claude-cowork/troubleshoot-cache/) · [ChatGPT](https://xspeedcache.com/agent/chatgpt/troubleshoot-cache/) · [Codex](https://xspeedcache.com/agent/codex/troubleshoot-cache/) · [Cursor](https://xspeedcache.com/agent/cursor/troubleshoot-cache/) · [GitHub Copilot in VS Code](https://xspeedcache.com/agent/github-copilot/troubleshoot-cache/) · [Windsurf](https://xspeedcache.com/agent/windsurf/troubleshoot-cache/) · [Gemini CLI](https://xspeedcache.com/agent/gemini-cli/troubleshoot-cache/) · [Antigravity](https://xspeedcache.com/agent/antigravity/troubleshoot-cache/) · [Zed](https://xspeedcache.com/agent/zed/troubleshoot-cache/) · [Kiro](https://xspeedcache.com/agent/kiro/troubleshoot-cache/) · [OpenCode](https://xspeedcache.com/agent/opencode/troubleshoot-cache/) · [OpenClaw](https://xspeedcache.com/agent/openclaw/troubleshoot-cache/) · [Hermes Agent](https://xspeedcache.com/agent/hermes-agent/troubleshoot-cache/) · [Grok Build](https://xspeedcache.com/agent/grok-build/troubleshoot-cache/) · [ChatGPT dots](https://xspeedcache.com/agent/chatgpt-dots/troubleshoot-cache/) · [Grok](https://xspeedcache.com/agent/grok/troubleshoot-cache/) · [Muse](https://xspeedcache.com/agent/muse/troubleshoot-cache/) · [Manus](https://xspeedcache.com/agent/manus/troubleshoot-cache/) · [Kimi Code](https://xspeedcache.com/agent/kimi/troubleshoot-cache/) · [Paperclip](https://xspeedcache.com/agent/paperclip/troubleshoot-cache/) · [NanoClaw](https://xspeedcache.com/agent/nanoclaw/troubleshoot-cache/)

## More with Grok Bot

- [Purge the WordPress cache with Grok Bot](https://xspeedcache.com/agent/grok-bot/purge-cache/)
- [Scan a website for speed problems with Grok Bot](https://xspeedcache.com/agent/grok-bot/speed-scan/)
- [Run and track PageSpeed tests with Grok Bot](https://xspeedcache.com/agent/grok-bot/pagespeed-tests/)
- [Raise a WordPress site's PageSpeed score with Grok Bot](https://xspeedcache.com/agent/grok-bot/optimize-site/)
- [Tune WordPress cache settings with Grok Bot](https://xspeedcache.com/agent/grok-bot/cache-settings/)
- [Warm the WordPress cache with Grok Bot](https://xspeedcache.com/agent/grok-bot/preload-cache/)
- [Set up the Redis object cache with Grok Bot](https://xspeedcache.com/agent/grok-bot/object-cache/)
- [Manage Cloudflare caching with Grok Bot](https://xspeedcache.com/agent/grok-bot/cloudflare/)
- [Manage every WordPress site at once with Grok Bot](https://xspeedcache.com/agent/grok-bot/fleet/)

## Documentation

- How to read your cache diagnostics: https://xspeedcache.com/docs/cache-diagnostics/
- Understanding cache hits and misses: https://xspeedcache.com/docs/hits-and-misses/
- How to check your site health: https://xspeedcache.com/docs/health/
- Common problems and troubleshooting: https://xspeedcache.com/docs/common-problems-and-troubleshooting/
- How to enable Page Cache: https://xspeedcache.com/docs/page-cache/