Cache Preload

Hello @natasha006,
Thank you for your inquiry.
Go to Performance –> General Settings Tab, scroll down to the Miscellaneous section near the bottom. There, you need to uncheck “Use single network configuration file for all sites.”
W3 total cache doesn’t support multiple sitemaps in cache preload so you need to configure subsites individually.
I hope this helps.

Thanks for your reply.

Do you think that it is a logical solution to uncheck it and use of individual sitemap URL for each site?
Is it worth it?

Hello @natasha006,

If you need the warm cache often, you can benefit from cache preload so this could prove to be very useful. It really depends on what you want to achieve.
W3 Total cache is offering you the freedom to set up the plugin the way it best suits your needs.

Hello @vmarko
Thanks for assisting me.

There is an inquiry for me.
We assume that we are on the cold cache (Cache Preload is off)
After the cache is expired (3600 seconds default), W3TC will not create a new one until a user is visiting the site? right?

Hello @natasha006,

The pages need to be visited in order for cache to created. If you are not using Cache Preload, and If The TTL of page cache files is set via the “Expires header lifetime” field in the “HTML”, the cache will expire depending on “Expires header lifetime”.
If the cache is expired and cache data is removed, pages need to be revisited in order to be cached.
I hope this helps.