A demand-driven sitemap for LiteSpeed Cache warmup. Record the URLs visitors actually use and warm only what people need.

URLs Most Wanted for LiteSpeed LScache

URLs Most Wanted gives the LiteSpeed Cache crawler the information it is missing: which URLs are actually worth warming.
What this means for your cache warmup
<ul>
<li>Warm URLs that real visitors actually request, not every URL that happens to exist.</li>
<li>Reduce unnecessary crawler work and server stress, especially on shared hosting.</li>
<li>Finish useful warmup work faster by avoiding pages with little or no real demand.</li>
<li>Warm cacheable visitor paths that a normal SEO sitemap may not contain, such as pagination and filter URLs.</li>
<li>Use the LiteSpeed cache engine and the built-in LiteSpeed Cache crawler more economically, with demand as the decision basis.</li>
<li>Record demand asynchronously with exceptionally low overhead, without affecting page delivery or PageSpeed measurements.</li>
</ul>
LiteSpeed Cache provides a crawler. The LiteSpeed cache engine provides the technical foundation for fast cached delivery. But the standard setup cannot answer one important question:
Which URLs should the crawler warm first, and which URLs are not worth the effort?
The usual answer is the sitemap.
A sitemap is useful. It tells search engines which URLs exist and which content should be discoverable. But that is an SEO question, not a cache-warmup question.
A URL can exist without being wanted. A URL can be listed in a sitemap without ever being visited. And many URLs that visitors actually use, such as pagination, filtered listings or other cacheable visitor paths, may not belong in a search-engine sitemap at all.
So why should cache warmup treat every sitemap URL as equally important?
It should not.
Every crawl creates work. The crawler has to request URLs, generate cache entries and use server resources while it does so. On a powerful dedicated server this may be tolerable. On shared hosting, unnecessary crawler work can become visible server stress that affects the website while the warmup is running.
LiteSpeed Cache includes a Server Load Limit, but on shared hosting that value may reflect the load of the entire server rather than the load created by one account. Choosing a threshold cannot make irrelevant crawl work useful. The workload you can control directly is the number of URLs the crawler has to process.
The consequence is simple:
<blockquote>
The less relevant work a warmup performs, the more efficiently it can serve the URLs that matter.
</blockquote>
A sitemap may change when content changes, but it cannot adapt to actual demand. It does not know which URLs visitors use today, which pages they ignore, or whether a cacheable URL outside the SEO sitemap has become important.
That is the gap URLs Most Wanted closes.
URLs Most Wanted records visitor-requested URLs and stores them with their hit count, creation date and last modified date. From this real usage data, it creates an alternative sitemap for the built-in LiteSpeed Cache crawler.
Instead of warming a generic list of URLs because they exist, the crawler can warm the URLs that have proven to be useful.
This is not prediction. It is proven demand.
The recorded hit counts also reveal which URLs have no demonstrated warmup value. That does not automatically make their content disposable, but it makes clear where cache-warmup resources are not creating a benefit.
In practice, a large share of a website&#8217;s URLs may receive little or no traffic. Long-term traffic analysis can reveal that up to 70% of URLs are rarely or never requested. Warming those URLs again and again is not cache strategy. It is resource waste.
URLs Most Wanted changes the economics of cache warmup:
<ul>
<li>Less unnecessary crawling.</li>
<li>Less avoidable server load.</li>
<li>More focus on URLs with real visitor value.</li>
<li>Better coverage of cacheable URLs that the normal SEO sitemap does not represent.</li>
<li>A faster path to a warm cache where it creates an actual benefit.</li>
</ul>
The plugin does not replace the LiteSpeed Cache crawler. It gives the crawler a better source of URLs.
<h4>Built for LiteSpeed Cache</h4>
URLs Most Wanted is designed specifically for LiteSpeed Enterprise or OpenLiteSpeed together with the LiteSpeed Cache for WordPress plugin.
The plugin uses a LiteSpeed capability that other LiteSpeed-focused solutions do not normally expose. It keeps the effort required for recording visitor demand exceptionally low. URL recording happens asynchronously and is designed not to affect frontend delivery or PageSpeed measurements.
The result is deliberately simple: UMW collects the demand data, LiteSpeed Cache performs the warmup, and your server spends its resources where they have a reason to be spent.
<h4>Administration</h4>
URLs Most Wanted is intentionally unobtrusive. The administration screen lets you review saved URLs, their hit counts and timestamps. You can:
<ul>
<li>Delete individual URLs or purge all saved URLs.</li>
<li>Blacklist URLs that must not be used for warmup.</li>
<li>Reset hit counts.</li>
<li>Generate the UMW sitemap manually.</li>
<li>Generate the sitemap automatically once per day through WP-Cron.</li>
</ul>
Nothing changes in the way LiteSpeed Cache warms the cache. You simply configure its crawler to use the UMW sitemap instead of a generic SEO sitemap.
<h3>Requirements</h3>
<ul>
<li>LiteSpeed Cache for WordPress must be installed.</li>
<li>PHP version 8.1 or higher.</li>
<li>LiteSpeed Enterprise or OpenLiteSpeed web server.</li>
</ul>
<h3>Compatibility exclusions</h3>
UMW Capture cannot be activated on Quic.cloud or o2switch hosting.
These are hard technical exclusions, not configuration issues:
<ul>
<li>Quic.cloud is not supported because it does not provide the POST caching capability required by UMW Capture.</li>
<li>o2switch (France) is not supported because LiteSpeed operates only as an upstream proxy while the WordPress origin runs on Apache. UMW requires LiteSpeed Enterprise or OpenLiteSpeed at the origin.</li>
</ul>
There is no supported workaround for either environment.
<h3>External services</h3>
This plugin requests the public QUIC.cloud IP range list from https://quic.cloud/ips when it performs its server-side QUIC.cloud IP check. The IP range data is used to identify QUIC.cloud-served responses during LiteSpeed Cache validation.
The request does not send visitor data, page content, credentials, cookies, WordPress options, or database data. As with any HTTPS request, QUIC.cloud receives the server IP address. The default WordPress HTTP user agent may also include the site URL and WordPress version.
QUIC.cloud Terms of Use: 
https://www.quic.cloud/terms-of-use/
QUIC.cloud Privacy Policy: 
https://www.quic.cloud/privacy-policy/

Alternative Plugins for

Discover the Lists with URLs Most Wanted for LiteSpeed LScache