Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #40947

    Im using the yoast sitemap_index.xml as the URL in the preload setting section.
    Apparently w3 is not preloading my pages, so am I doing something wrong here?

    Marko Vasiljevic

    Hello Sephan,

    Thank you for your inquiry and I am happy to assist you with this.
    When using cache Preload in W3 Total Cache, depending on how big your website is and on the settings it may take some time for the entire website to be preloaded.
    What the Cache preload does is:
    – Check the last offset
    – Check how many URLs are allowed to be processed per run
    – Fetch all URLs from sitemap (even nested sitemaps work)
    – Loop through a set of URLs to visit them
    Your sitemap URL should be added like this: https://yourwebsite.com/sitemap_index.xml
    If the end of the list is reached, it will start from the beginning of the next run. That means that when the last page is reached, it will start from the beginning with the first 10 pages and so on (10 pages if the default values are set).
    If you have your site set to use wp-cron the default way (native wp-cron), it only triggers visits to your site. WP allows you to turn this offdefine('DISABLE_WP_CRON', 'true'); so u can trigger wp-cron.php manually via your system’s cron. When you do it that way the preload will run in batches on each cron job call to wp-cron.
    WP-CLI can also be used for priming and logging. If you don’t want to rely on wp-cron – use the wp-cli command for preloading and Unix cron. You should call it directly in wp-cli wp w3-total-cache pgcache_prime
    and track the output which pages/sitemap positions are primed by script.
    I hope this helps.

Viewing 2 posts - 1 through 2 (of 2 total)
  • The topic ‘Preload not working’ is closed to new replies.