Page Caching and HostingNew
Docs pages look the same for every visitor, so they can be stored by a page cache and served fast: a cache plugin, your host’s server cache or a CDN. WP Super Docs works with them on its own. It clears the cache when your docs change, and keeps the few pages that are made for one visitor out of the cache.
When the cache is cleared#
The page cache is cleared once, at the end of the save, when something changes that shows on more than one page:
- A doc is published, unpublished or trashed, or its title, address, order, parent or excerpt changes.
- A doc moves to another product, category, tag or version.
- A category, product, tag or version is added, edited or deleted.
- A snippet, roadmap item, changelog entry, service or download that’s live changes.
- The sidebar order or a WP Super Docs setting changes.
Editing only the text of a doc leaves clearing that page to your cache plugin or host, which already does that for any post.
Votes, searches and other things visitors do never clear the cache.
Supported caches#
WP Super Docs clears the cache through each one’s own public function or hook. Anything that isn’t installed is skipped.
| Cache plugins | Hosts with their own server cache |
|---|---|
| WP Rocket | RunCloud (RunCloud Hub and RunCache) |
| LiteSpeed Cache | Kinsta |
| W3 Total Cache | WP Engine |
| WP Super Cache | Pantheon |
| WP Fastest Cache | GoDaddy Managed WordPress |
| WP-Optimize | Pressable |
| Hummingbird | Cloudways (Breeze, including Varnish) |
| FlyingPress | SiteGround (SiteGround Optimizer) |
| NitroPack | SpinupWP |
| Cache Enabler | GridPane and other nginx hosts (Nginx Helper) |
| Comet Cache | DreamHost and other Varnish hosts (Proxy Cache Purge) |
| Powered Cache | Pressidium |
| Swift Performance | Savvii |
| Super Page Cache | Hostinger and other LiteSpeed hosts (LiteSpeed Cache) |
| Cloudflare (APO) | xSpeed |
Bluehost and HostGator clear their own cache when posts and settings change, so they need nothing extra.
Pages that are never cached#
A few pages are built for one visitor, and a cached copy would show one visitor’s page to the next:
- The roadmap, with its feature requests and shipped pages, which show each visitor’s own votes.
- Docs pages shown in a version the visitor picked earlier (see The Version Picker & Cookie Persistence).
- Download links, so every download is counted (see Downloads).
These pages tell every kind of cache not to store them: cache plugins, CDNs, Varnish, nginx and LiteSpeed server caches, and WP Engine’s page cache.
On Kinsta, the server cache can only skip a page through a rule Kinsta adds. If the roadmap shows the wrong votes, ask Kinsta support to exclude your roadmap addresses (starting with /docs/roadmap/ on most sites) and addresses with ?wpsd_download= from the cache.
The “Was this helpful?” buttons#
The vote buttons work on cached pages too. If a cached page is old enough that its security token has expired, the vote gets a fresh token and still goes through.
For developers#
Turn off WP Super Docs’ cache clearing, for example to clear the cache your own way:
add_filter( 'wpsd_purge_page_cache', '__return_false' );
Clear another cache whenever WP Super Docs clears the page cache:
add_action( 'wpsd_page_cache_purged', function () {
// Clear your cache here.
} );
If Claude can’t connect#
The Claude connection test names your host and gives the exact fix for it. See Troubleshooting in Connecting Claude to Your Docs (MCP).
Was this helpful?
Thanks for your feedback!
✓ Feedback received. Thank you!