404 GUARD GUIDE
Make a legitimate address safe without opening up every missing address on the website.
If a real page, form or shop action stops working after protection is enabled, switch 404 Guard to Monitor mode. Try the same action again. This helps you establish whether 404 Guard is involved before changing several other settings.
Record what you were doing, the exact web address and what you expected to happen. A form may send its request to a different address from the page you can see in the browser.
Review the recent requests in Health Check and look for an entry at the time of the failed action. Compare it with the page or request you were testing. Don’t mark an address safe simply because a bot requested it many times.
If you’re a developer, the browser’s Network panel can help identify the request made by a form, booking widget or cart action. Check the path and any relevant query details. If you’re unsure which one matters, send support the information you have.
Use Safe URLs to add the confirmed legitimate address. Keep the entry as specific as the feature allows. A broad entry can let unwanted requests reach WordPress again and reduce the benefit of protection.
If that entry must stay on the safe list, use its lock option where appropriate. Locking should be a deliberate choice for a known working address, rather than a way to keep every old or unknown path.
Turn protection back on and repeat the same action. Then check related actions, such as the form’s confirmation, a booking step or adding an item to the cart.
If the action still fails, return to Monitor mode and check for another request. Don’t keep adding wider exceptions without finding the cause.
Email [email protected] with the exact address, your protection mode, the plugin version and the steps that reproduce the problem. Include a screenshot of the relevant Health Check entry if you have one.
Please leave passwords, licence keys and customer details out of screenshots and messages. Support can ask for a suitable access method if the issue needs a closer look.
Send the exact address, your protection mode and what happened when you tested it.
