HOW IT WORKS
WordPress can do a surprising amount of work before it says ‘page not found’. 404 Guard helps it give that answer earlier.
A normal 404 request can load plugins, run database queries and start the theme before WordPress decides the page is missing. One request may be harmless. A steady stream can leave less capacity for customers.
01
404 Guard builds an index of known website addresses, including supported content and redirect sources.
02
Test your main pages, forms and shop. Add any legitimate custom addresses to the safe list.
03
Start with checks, then choose repeat-request protection or Strict mode to suit your website.
MONITOR
Use this while checking your setup or investigating a page that doesn’t work. Requests continue through the usual WordPress process.
CONFIRMED 404 CACHE
Useful when the same missing addresses keep coming back. Protection applies to paths already confirmed as missing.
STRICT PROTECTION
Useful for made-up paths that change constantly. Make sure custom pages and important requests are on the safe list first.
Choose a supported response style to suit your website, from a small response to a prepared page. A real person arriving from an old link should still have a clear way to find your services or contact you.
Missing pages keep a proper 404 status. Existing redirects and important shop behaviour need to be checked as part of setup.
Use the Performance screen to compare normal and protected 404 response times. Check real pages as well, because a faster 404 result alone doesn’t tell you how the rest of the site is running.
404 Guard handles missing requests. Keep your security tools, updates, backups and hosting protection in place.
Try it with 500 protected 404 hits, then compare your results.
