| 开发者 | Imedes |
|---|---|
| 更新时间 | 2026年7月11日 16:09 |
| PHP版本: | 6.2 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv3 |
| 版权网址: | 版权信息 |
The less relevant work a warmup performs, the more efficiently it can serve the URLs that matter.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'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:
A normal sitemap is made for search-engine discovery. It shows which URLs exist, not which URLs have real visitor demand. It can contain URLs that are rarely used and omit cacheable visitor paths such as pagination or filtered listings. UMW creates a sitemap for cache warmup based on real usage instead.
No. URLs Most Wanted is made specifically for LiteSpeed Cache and requires LiteSpeed Enterprise or OpenLiteSpeed together with the LiteSpeed Cache for WordPress plugin.
URL recording is asynchronous and is designed not to affect frontend delivery or PageSpeed measurements. UMW uses a LiteSpeed capability that other LiteSpeed-focused solutions do not normally expose, keeping the additional recording effort exceptionally low.
No. UMW does not predict demand. It records proven demand from visitor-requested URLs and uses that information for future cache warmup.
No. Importing arbitrary URLs would distort the purpose of UMW. The sitemap is meant to represent actual usage, not an externally assembled URL list. Manual database changes via phpMyAdmin are possible, but they are outside the normal workflow.
Yes. UMW can generate its sitemap manually or automatically once per day through WP-Cron.
UMW Capture is activated only when its technical requirements are met. It cannot be activated on Quic.cloud or o2switch hosting. Quic.cloud does not provide the POST caching capability required by UMW Capture. On o2switch, LiteSpeed operates only as an upstream proxy while the WordPress origin runs on Apache. These are hard technical exclusions, not configuration issues, and there is no supported workaround.