Wordpress LScache Plugin: Always Fresh Crawl on Quic.Cloud
Last Updated on: Wed, 15 Apr 2026 00:00:02 Hi there, could you please clarify in which cases could be useful the new Always Fresh Crawl feature on Quic.Cloud, please? It is set OFF as default, but for Google crawler uses is better set it ON? Please help me to understand. The description didnt help me: Always send the full page to crawlers even if it has not updated since the last crawl. In effect, this means crawlers will never receive a 304. This also means that crawlers will use more bandwidth. Does it means that if there are not updates the crawler will receive not a full page? Thanks a lot. Hi, what do you mean by always fresh crawl ? where did you see that description ? best regards, Hi @CacheCrawler, here it is. Hi, that is option is specific to LScache build in crawler , doesnt affect any other crawlers from search engine. Our web site is on a LS server, so we could use it. But we didnt understand the utility. Could you explain us better? when crawler hit your page , webserver will return the whole page response body , which is bit of waste of bandwidth so for LSWS , when it is hit by a specific user agent from our crawler , the webserver will generate the response , but it will only send the response header but not response body to save bandwidth and load. HI, my previous reply was incorrect , please ignore it this is the correct version: in some cases the server may return 304 status to crawler bot , some user wants it to be 200 status code all the time , that was this option about Thanks a lot for clarified this!
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference