The pages aren’t there. The work can still be real.
You open the traffic logs and see requests for old backup files, random PHP files and addresses you’ve never used. None of them leads to a real page. It’s tempting to assume a 404 response means the website has done very little work.
On WordPress, that isn’t always the case. A missing-page request may still load plugins, query the database and start the theme before returning ‘page not found’. A few requests may go unnoticed. A steady flood can be a different story.
Why do bots try these addresses?
Some automated scans look for files or software with known weaknesses. Others try common backup names or paths copied from lists. The scanner doesn’t know whether those files exist on your website.
That’s why the addresses can look so unrelated to the business. A florist, an accountant and an online shop may all receive similar probes. The requests can also come from changing IP addresses.
What a business owner might notice
The website may feel slow while visitor numbers or sales haven’t risen. Your host may report higher resource use, and the logs may contain large numbers of missing-page requests.
Those signs are a reason to investigate, not proof of a single cause. Slow database queries, scheduled jobs or other traffic can also put the site under strain. Compare the timing of the 404 requests with the slowdown.
Where 404 Guard fits
404 Guard helps WordPress answer supported missing requests earlier, with less of the usual page-building work. Its check focuses on the requested address, so it can still help when the bot changes IP address.
Confirmed 404 cache can help with repeat requests for addresses already known to be missing. Strict protection can handle unknown addresses on the first hit, but you need to check the Safe URL index and important customer actions before using it.
Check useful pages before stronger protection
Build the safe list and test the pages the business relies on. Include contact forms, booking actions, search and, for a shop, cart and checkout. Custom plugin features can use addresses that need to be added.
If a real request is blocked, switch to Monitor mode while you identify it. Add the precise legitimate address as safe and test it again.
Measure the result without waiting for the bots to leave
Keep a record of normal and protected 404 response times, then check ordinary pages while the site is busy. Traffic Gate graphs can help show whether the unwanted traffic continued during the comparison.
The aim is less work per missing request. Incoming traffic doesn’t have to fall for that to be useful. Keep your security plugin, updates and hosting protection in place, because they handle problems outside 404 Guard’s job.