Say an old menu links to /images/summer-menu.jpg after the image has been removed. Each visit can trigger another WordPress error page. Check the link first, then use 404 Guard for requests that keep coming back.
1
Find a repeating URL
In the access log, look for repeated 404 responses such as /images/summer-menu.jpg. Compare the count with requests to a working page over the same period.
2
Decide whether the URL should exist
If the image belongs on the site, restore it or fix the link at its source. For a moved page, redirect to its genuine replacement.
3
Observe with 404 Guard
Start in Monitor only. Review the recorded paths and identify confirmed misses. For repeated requests to a genuinely missing resource, use Confirmed 404 cache to serve a lightweight response.
4
Check the result
Request the missing address again and confirm it still returns HTTP 404. Compare protected hits and response times, then open a valid page. If the flood uses a different URL every time, send a sample to support for review.
Still seeing the same 404?
Check the path in 404 Guard’s log against the address in your access log, including the file extension.