⚑
LiteSpeed

Setting LiteSpeed Cache Rules for WordPress

πŸ“… 10 October 2026 ✏️ 10 October 2026 ⏱ 5 min leestijd

Learn how to properly configure LiteSpeed Cache for WordPress: cache rules, exclusions, and settings for a faster site.

LiteSpeed Cache is one of the fastest ways to speed up WordPress, but only if the rules are set up correctly. Incorrect settings lead to outdated content or broken forms. In this article, you’ll learn how to properly configure cache rules, exclusions, and TTL values so your site loads faster without losing functionality.

What LiteSpeed Cache exactly does

LiteSpeed Cache is a free plugin that works together with the LiteSpeed web server to store full pages as static HTML. When a visitor opens your site, WordPress doesn’t need to rebuild the page from the database; instead, the server directly delivers the stored version. This significantly reduces server load and results in faster loading times, especially for content-rich sites with many plugins.

The difference with regular cache plugins is that LiteSpeed Cache operates at the server level. This means the cache is faster than a plugin that only operates at the PHP level. This combination of server and plugin is exactly why hosting providers with LiteSpeed servers, such as those used within /nl/webhosting/, often offer a noticeably faster WordPress experience.

VisitorLiteSpeed CacheWordPress

Installing the plugin and basic settings

Install LiteSpeed Cache via the WordPress dashboard under Plugins > Add New Plugin. Search for “LiteSpeed Cache” and activate the plugin. Then go to the Cache tab and turn on the main switch. By default, this caches pages, images, and CSS/JS files.

Next, check under Cache > TTL how long pages are retained before they automatically refresh. A public page can easily be cached for 24 hours, while dynamic content such as a shopping cart should not be cached at all. Under Cache > Purge, set the cache to automatically clear when publishing or editing a post, so visitors never see outdated content.

πŸ’‘ Tip: After each change, test the site in an incognito window to make sure you’re viewing the cached version and not a browser cache.

Setting up cache rules and exclusions

Not every page should be cached. Think of the shopping cart, checkout page, account section, and pages with forms displaying personal data. You configure this via Cache > Exclude. Here you can specify URLs, cookies, or user agents that are always excluded from caching.

For WooCommerce sites, the plugin already automatically recognizes many of these pages by default, but it’s wise to check this manually. For example, add /my-account/ and /cart/ to the exclusion list if you notice users seeing incorrect information. Also pay attention to plugins that display dynamic content, such as stock notifications or personalized recommendations; this content should be excluded from object cache or use ESI (Edge Side Includes).

1

Determine which pages are dynamic

Make a list of pages with forms, shopping carts, or account details.

2

Add exclusions

Add these URLs to Cache > Exclude so they are never cached.

3

Set TTL per content type

Give static pages a longer cache time than news posts or promotions.

4

Thoroughly test the live site

Check forms, shopping cart, and login functionality in an incognito window.

Solving common problems

The most common problem is that changes aren’t immediately visible. You can solve this by manually clearing the cache via the “Purge All” button at the top of the WordPress dashboard, or by correctly setting up automatic purge rules when publishing content.

Another problem occurs when logged-in users see the same cache as visitors. Make sure the option for logged-in users under Cache > ESI is set correctly, so personal content is handled separately from the public cache. If you’re using a CDN or Cloudflare, check that the LiteSpeed Cache settings and the CDN don’t conflict; double caching can actually cause outdated content.

For persistent issues, it’s often faster to check via Plesk whether the server settings are correct, something you can quickly verify in the Plesk panel of your hosting environment. If you’re unsure about the correct configuration, consult /nl/support/ for more explanation or contact your hosting provider.

Frequently Asked Questions

Does LiteSpeed Cache also work without a LiteSpeed server?

The plugin will still work as a regular cache plugin, but you’ll miss the server-level benefits. For the best results, you need a hosting environment with LiteSpeed servers.

Can I combine LiteSpeed Cache with WooCommerce?

Yes, the plugin automatically recognizes WooCommerce and excludes cart and checkout pages from caching by default.

How often should I clear the cache?

Set up automatic purging when publishing or editing content, so you don’t have to do it manually.

Does caching affect my email functionality?

No, caching works independently of email. For a reliable business email environment, check out /nl/email-hosting/.

What if I switch to a new hosting provider?

When switching, you can usually simply export and re-import the LiteSpeed Cache settings; see /nl/overstappen/ for the steps.

Conclusion

With the right cache rules and exclusions, you get the most out of LiteSpeed Cache without losing site functionality. Start with the basic settings, exclude dynamic pages, and test thoroughly after each change.

View web hosting β†’

Was dit artikel nuttig?