Wordpress LScache Plugin: Cache posts for a stretch of last xx? days
Last Updated on: Wed, 15 Apr 2026 00:00:02 Hello: Its possible do not cache posts older than specific days? I have a lot of pages from 11 years site, so the crowls slow down the site, I have to limit the cache pages to last 10 days. Thank you. This topic was modified 4 years, 1 month ago by Marlimant. Hi, Marlimant. There is actually a better way to deal with your old content. Do you know what you have set as your Default Public Cache TTL in the Settings > General tab? If you are using the default 604800 seconds, then your sites content expires every week. And so, every week, the crawler has a lot of work to do to recache that content. If you have a shorter TTL, then the crawler is working even harder than that. One option is to increase the TTL to something much longer, say a month (2630000 seconds) or 3 months (7890000 seconds). Then, when the crawler runs, there will be much less uncached content for it to deal with, and it will go much more quickly. You dont need to be worried about caching your content for such a long period. LiteSpeeds smart purge technology ensures that your cache stays current, even when there are updates. When new content is posted, or existing content is edited, any related pages, as defined in Settings > Purge > Auto Purge Rules For Publish/Update, will be purged from the cache. If nothing changes, though, the old content stays cached for the full TTL period. The only complication here is if you have a widget that appears on every page and must be updated when new content is posted (i.e. a New Posts widget). In that case, you can enable ESI, and make the widget an ESI widget with a much shorter TTL. This allows the widget be updated frequently while the rest of the page ramains cached. A long TTL (plus ESI if necessary), should be enough to keep your old content cached for a long time and speed up the crawler runs considerably. If you need me to explain any of these concepts further, let me know! Thanks for the fast reply Lisa. Your solution is a way out ? but I think there is much simple create a function limiting the cach? to some days. With this, there no complications with widgets, or pay a high cost when there is needed renew all the cache. Also, a big cache may increase the data base and hard drive size. I leave you the concern, maybe you can implement this solution later, in future versions. Best regards.
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference