Support » Plugins » Make WP Super Cache cache the 404 page

  • Resolved walkinman



    I have the Super Cache plugin on my site, and it’s working great. Thanks. However, I need to cache the 404 pages, as some other error elsewhere is causing a massive amount of 404s (thank you bingbot). So I need to cache the 404 pages to lower my server load.

    My webhost told me WP Super Cache doens’t have this option, but it seems when I look at the changelog for 0.9.7 it indicates this is now possible. Also this page suggests it’s possible. I’m just not smart enough to figure out how to do that.

    Do I just go to “Advanced” > “Add here those filenames that can be cached, even if they match one of the rejected substring specified above.” and add in this line


    or do I need to put the whole string like this:


    Sorry to bother you with such lame questions. I just have no idea how to make this stuff work correctly.

    Thanks so much.


Viewing 2 replies - 1 through 2 (of 2 total)
  • Unfortunately it doesn’t cache 404 pages. What I do when something like this happens is add a mod_rewrite rule (or php code) that redirects the offending pattern of requests to the homepage or the post they’re supposed to go to. That avoids a 404.

    Hey Donncha

    Ahhh … bummer … OK .. I’m actually in the process of trying to put a mod_rewrite rule for the urls, as well as block bing from the offending directory (which doesn’t exist), and still the problem continues. Unfortunately I either have to switch to W3 Total Cache, or re-configure wordpress so it doesn’t point to the root directory any more, which would at least allow me to simply configure a static 404 page, and lower the resource usage.

    ‘course, I have no idea how to do all that, but I’ll stab away at it. But I appreciate you taking the time to clear this up for me; thank you. The irish have always been revered for their customer service. 🙂


    Carl (Donohue) 🙂

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Make WP Super Cache cache the 404 page’ is closed to new replies.