# Find out why WordPress pages are not cached with Grok

> Finding out why pages are not cached with Grok means asking xAI's chat assistant on grok.com, which reads xSpeed cache status and health checks through the xSpeed Hub connector and explains what it finds, including a refusal from the site.

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

You added xSpeed Hub on grok.com as a custom connector, signed in once, and moved on. Weeks later a new landing page goes live and feels slow, so you open a chat and ask about it. xAI says Grok uses a connector's tools whenever a question relates to that service, so you do not pick the connector from a menu first. Naming xSpeed Hub in the message is still worth the extra words, because it tells Grok which tools to reach for when more than one connector could answer.

Grok reads get_cache_status for landing and finds page caching off, with nothing cached. get_health adds the reason the switch alone will not fix: the advanced-cache.php drop-in belongs to another caching plugin. Grok offers to turn page caching on anyway, you agree, and the site refuses. That refusal comes from the xSpeed plugin, which will not take over a drop-in another plugin owns when the request arrives through the Hub, and its message says so. It is a useful result, not an error to retry. The fix is yours: deactivate the other caching plugin in wp-admin, then ask Grok to try again and run the benchmark.

This is a chat, so Grok works from what the Hub returns. That is enough for most causes, because get_health covers the drop-in, the WP_CACHE constant, permalinks, conflicting plugins, the cache directory and cookies on anonymous pages. For a single URL that bypasses the cache, Grok can tell you what to look for, and you request the page yourself in a private window with a plain GET.

## Set up Grok 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. Add xSpeed Hub as a custom connector

Go to grok.com/connectors, click New Connector and select Custom. Enter this as the MCP server URL and complete the authentication: approve access on the xSpeed Hub page that opens. Grok then reads the Hub's tools and makes them available in your conversations.

```
https://app.xspeedcache.com/xspeed/mcp
```

### 3. Ask a first question

Start a chat and ask something that names xSpeed Hub, so Grok reaches for the connector. A list of your sites with their cache status means the connection works.

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

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

### 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. xAI's connector documentation describes no per-tool approval setting. It says Grok can use a connector's tools whenever your questions relate to that service. xSpeed Hub has no confirmation step of its own, so a purge or a settings change runs as soon as Grok calls it and your connection allows writes. The Hub tells the agent to confirm the target site and to ask once before a write that touches every site, but that is an instruction, not a lock. If you want Grok to read and never change anything, sign in as a Viewer member of the workspace, which only ever gets read access. Otherwise read what Grok says it is about to do before you answer yes.

## Prompts

- Use xSpeed Hub to tell me why landing is not serving cached pages, and quote the failing health check.
- With xSpeed Hub, turn page caching on for landing and tell me exactly what the site says if it refuses.
- Using xSpeed Hub, which of my sites has the lowest hit ratio today, and does its health report explain why?

## Example session

```
You: Use xSpeed Hub to tell me why the new landing site feels uncached.
  → get_cache_status(site: landing) [read-only]: page caching is off, 0 cached pages
  → get_health(site: landing) [read-only]: 1 warning: advanced-cache.php belongs to another caching plugin
Agent: Page caching is off on landing, and the cache drop-in belongs to another caching plugin. I can try to turn xSpeed's page caching on, but the site may refuse while the other plugin owns that file. Try it?
You: Yes, try.
  → toggle_cache(site: landing, enabled: true) [changes site]: refused: another plugin owns advanced-cache.php; deactivate it first
Agent: The site refused, as expected. Deactivate the other caching plugin in wp-admin on landing, tell me when it is done, and I will turn caching on and run the benchmark.
```

## 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

xAI's connector documentation describes no per-tool approval setting, so the question Grok asked before the toggle came from the model following the Hub's instruction to confirm the target site, not from a lock. On a connection that allows writes, toggle_cache runs as soon as Grok sends it, and contact_support sends an email whenever Grok decides to call it, because the Hub classes it as a read. If you want Grok to diagnose and never change anything, sign in as a Viewer member of the workspace, which only ever gets read access. That stops the toggle but not contact_support, so ask Grok to show you any support message before it sends one. On Grok Business and Enterprise, a team admin provisions the connector in the cloud console first.

## 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

### Why did Grok say the site refused to turn caching on?

The xSpeed plugin will not take over the cache drop-in through the Hub while another caching plugin owns it, and it says so when asked to enable caching. Deactivate the other plugin in wp-admin, then ask Grok to try again.

### Can Grok troubleshoot my cache without being able to change it?

Yes. Sign in to the connector as a Viewer member of the workspace, which only ever gets read access. Grok can still read cache status, health checks and the benchmark, which is all a diagnosis needs. contact_support still works on that sign-in, because the Hub classes it as a read.

### 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 Bot](https://xspeedcache.com/agent/grok-bot/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

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