Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting

WP Super Cache Preload Not Working: Causes and How to Fix It

WP Super Cache Preload Not Working: Causes and How to Fix It

Short answer

WP Super Cache preload runs through WordPress cron, so it fails when WP-Cron is disabled or broken, caching is off, the refresh interval is 0, or an earlier preload is stuck. Turn caching on, fix cron, set an interval, enable preload mode, then cancel and restart the preload.

Key takeaways

  • Preload depends on WP-Cron, not visitor traffic.
  • Caching must be on before preload can store anything.
  • A refresh interval of 0 stops automatic preloads.
  • Preload mode stops garbage collection deleting preloaded files.
  • PHP time limits can stop large preloads partway.

Why is WP Super Cache preload not working?

WP Super Cache preload usually stops because WP-Cron is not running, caching itself is off, the refresh interval is set to zero, or a stuck preload from an earlier run is blocking a new one.

Preloading builds cached copies of your posts and pages ahead of time, so even the first visitor gets a fast static page. It runs in the background in small batches through WordPress's scheduled tasks.

Because it depends on background tasks, preload is more fragile than normal caching. Normal caching happens when a visitor arrives. Preload only happens if WordPress's scheduler actually fires.

If caching does not work at all, start with our general guide to WP Super Cache not working. This guide focuses on the preload feature.

What are the common causes at a glance?

Most preload problems trace back to a handful of causes that you can check in a few minutes.

SymptomLikely causeFirst check
Preload button does nothingWP-Cron not runningCheck DISABLE_WP_CRON and cron events
Preload starts then stopsServer timeouts or memory limitsCheck PHP limits and error log
Preload never repeatsRefresh interval set to 0Set a refresh interval
Status says preload is running for hoursStuck preloadCancel and start again
Cache files appear, then vanishGarbage collection deleting themTurn on preload mode
Some pages never cachedExcluded or non-public pagesCheck rejected URLs and post status

Find the row that matches what you see, then go to that section.

Is caching turned on first?

Preload only works when WP Super Cache caching is switched on, so check the Easy tab before troubleshooting the Preload tab.

Go to Settings, then WP Super Cache. On the Easy tab, make sure caching is on and save.

If caching is off, the Preload tab may still show options, but nothing gets stored. Our guide to WP Super Cache settings walks through every tab in order.

Is WP-Cron running?

WP Super Cache runs preload through WordPress cron, so if WP-Cron is disabled without a real server cron job, or loopback requests fail, preload never starts.

Open wp-config.php and look for this line:

define( 'DISABLE_WP_CRON', true );

If it is there, your host must run a real cron job that calls wp-cron.php on a schedule. If no such job exists, no scheduled tasks run at all, including preload.

You can learn how scheduling works in the WordPress cron documentation. Our guide on fixing WP-Cron not running covers each fix in detail.

To see whether WP Super Cache's preload event is waiting, install WP Crontrol and look under Tools, then Cron Events, for preload events. Past-due events that never run point to a cron problem.

Is the refresh interval set correctly?

On the Preload tab, a refresh interval of 0 turns off automatic refreshing, so preload only runs when you click the button and never repeats on its own.

The setting asks how often preloaded files should be refreshed, in minutes. The plugin enforces a minimum value, so very small numbers may be raised automatically.

Choose an interval that matches how often you publish. A site that posts daily can refresh once or twice a day. A rarely updated site can refresh much less often.

Very frequent refreshes on a big site keep the server busy rebuilding pages that have not changed.

Is preload mode turned on?

Turn on preload mode on the Preload tab so garbage collection does not delete preloaded files before visitors can use them.

WP Super Cache normally deletes old cache files on a schedule. This garbage collection keeps the cache folder from growing forever.

When you preload, garbage collection can remove files you just built, especially if the cache timeout is short. Preload mode turns that cleanup off and lets the preload refresh handle freshness instead.

If files appear in the cache folder and then disappear later, this is the setting to check.

Is a stuck preload blocking new runs?

If a preload was interrupted, the plugin may still think it is running, so cancel the preload on the Preload tab and start it again.

The Preload tab shows a cancel option while a preload is active. Click it, wait a minute, then start the preload again.

If the cancel option does nothing, clear the full cache from the Contents or Easy tab. That also removes leftover preload status files in the cache folder. Our guide on how to clear WP Super Cache shows each method.

Then start a fresh preload and watch whether the number of cached pages grows.

Is the server stopping preload partway through?

Preload works in batches, and each batch can hit PHP time or memory limits on smaller hosting plans, which stops the process without a clear message.

Shared hosting often limits how long a PHP request can run. The max_execution_time setting controls this. If a batch takes too long, the host kills it.

Check the PHP error log in your hosting panel for timeout or memory errors around the time preload ran. If you see them:

  • Ask your host to raise PHP limits.
  • Increase the WordPress memory limit, as covered in our guide to increasing the PHP memory limit.
  • Lower the load by turning off preloading of tags, categories and other taxonomies.

Large sites with thousands of posts take a long time to preload, even when nothing is wrong. Be patient before deciding it has failed.

Why are some pages never preloaded?

Preload only covers published posts and pages that are allowed in the cache, so drafts, private posts, excluded URLs and pages that set cookies are skipped.

Check these places:

  • Rejected URLs. The Advanced tab lets you list URLs that should never be cached.
  • Taxonomy option. Category and tag archives are only preloaded if you tick the taxonomy option on the Preload tab.
  • Plugins that block caching. Some plugins tell WordPress a page should not be cached, for example carts and checkouts.
  • Post status. Private and password-protected posts are never cached.

If a page should be cached but never is, turn on the debug log described below and load the page while logged out.

How do you use the debug log to find the cause?

Turn on debugging on WP Super Cache's Debug tab, start a preload, then read the log to see which URLs were processed and why any were skipped.

The log records what the plugin does for each request, including preload batches. Jetpack's guide to enabling WP Super Cache debugging shows the settings.

Look for repeated errors or the same URL failing again and again. Turn the debug log off once you have what you need, because it can grow large.

The Preload tab can also send status emails as files are refreshed. Those emails are a simple way to confirm preload is running on schedule.

When should you skip preload entirely?

Skip preload if your host cannot run background tasks reliably, your site is very large on cheap hosting, or most of your traffic lands on a small set of pages that cache quickly anyway.

Preload is a nice extra, not a requirement. WP Super Cache still caches each page the first time a visitor loads it.

For small sites, the difference is often a single slower first visit per page. For very large sites, preloading every URL can put more load on the server than it saves.

If you want to compare other approaches, Jetpack's advanced troubleshooting checklist covers further edge cases, and our explainer on what WP Super Cache does explains how its caching modes work.

Frequently asked questions

How do I know if WP Super Cache preload is working?

Watch the Preload tab while a preload runs, or turn on status emails there. You can also check the Contents tab, where the number of cached pages should grow, and view a page source while logged out for the cache comment.

Does WP Super Cache preload need a real cron job?

Not always. Default WP-Cron runs when visitors load pages, which is enough for many sites. If you disabled WP-Cron in wp-config or your site gets very little traffic, set up a real server cron job so preload runs on time.

Why does preload stop after a few pages?

Usually a PHP time or memory limit ends the batch, or WP-Cron stops firing. Check your host's PHP error log, raise limits if possible, and turn off taxonomy preloading to reduce the workload on smaller hosting plans.

Should I preload categories and tags?

Only if those archive pages get real traffic. Preloading every taxonomy archive adds many pages to the job and puts more load on the server. Most small sites are fine preloading posts and pages only.

Is preload worth using on a small site?

It helps a little, because the first visitor to each page gets a cached copy. On a small site, the gain is modest since WP Super Cache caches pages on first visit anyway. Use it if cron works reliably on your host.

Sources

  1. WP Super Cache WordPress.org
  2. Enable WP Super Cache debugging Jetpack
  3. WP Super Cache advanced troubleshooting checklist Jetpack
  4. Cron WordPress Developer Resources
  5. Runtime configuration: max_execution_time PHP Manual

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.