Performance Glossary
404 error — 404s: Separating Real Losses From Scanner Noise
Search Console lists hundreds of 404s and you need to know which handful are losing sessions rather than being a bot walking your directory tree.
The short answer
A 404 is the server confirming it understood the request and has nothing to serve at that path — a clean, correct answer, and cheap only if the application does not rebuild a page to say it.
The number of 404s is meaningless on its own. What matters is which of them arrive with a referrer or a search-engine user agent, because those are the ones a visitor or a crawler actually walked into.
By the HostingFast team · Reviewed 24 August 2026
0
Terms, measured not asserted
100+
Entries wired together
Real
Log lines, not opinions
Free
Free to read, always
The causes are dull: content moved without a rule, a mistyped href, a page deleted while other sites still point at it. Isolated ones are normal and every crawler budgets for them. A pattern of them on URLs that still receive links is money left on the pavement.
The expensive variant is the soft 404 — an error page returned under a 200 status. It teaches search engines that dead addresses are alive, fills the index with pages nobody can reach, and on WordPress it usually costs a full template render to produce.
Find them in the log, not the dashboard
Your raw access log is the primary source. Grep the last week for a 404 status, cut out the request path, then pipe it through sort, uniq -c and sort -rn: you now have every missing path ranked by how often it was asked for. Search Console shows a sample, weeks late; the log shows everything, this morning.
Then split the list in two. Requests carrying a referrer, or a search-engine user agent, are real losses worth a rule. Requests for /wp-login.php variants, /.env and /phpmyadmin are a scanner enumerating you, and redirecting those simply hands the scanner a faster answer.
What a missing page costs to produce
On a static file the 404 is nearly free. On WordPress it is not: the request misses the page cache by definition, boots PHP, loads the plugin stack and renders 404.php before returning the status. A burst of scanner traffic can therefore occupy your PHP workers with pages nobody will read.
That is why a heavy 404 template is a genuine liability. Keep it light — a search box, a short list of popular links, one line of human writing — and let the cache hold the rendered result where the platform allows it.
410 when you mean it, 301 when you can
410 Gone says the removal is deliberate and permanent, and crawlers drop the URL faster than they do a 404. Use it for content you have retired on purpose, such as expired offers, and keep the 404 for the ordinary case of something that was never there.
Where a replacement exists, the 301 is nearly always the better answer, because the inbound link keeps working. Redirect to the closest genuine equivalent, though — a blanket redirect to the homepage is read as a soft 404 and helps nobody who clicked.
Confirming the report went quiet
Re-run the same log query a week after your rules ship. The referred 404s should have gone; the scanner noise will not have moved, and it should not. If both counts are unchanged, the rules are matching a different path than you think — curl the exact URL from the log and read the status you get back.
Watch the PHP worker graph over the same period too. On sites hit hard by enumeration, cutting rendered 404s down is visible as headroom rather than as a page-speed score.
A glossary that expects you to check the log
Every entry here assumes you have terminal access and a question rather than a beginner's fear. The definition is the short part; where to look and what the reading means is the rest.
Every plan runs on NVMe with LiteSpeed in front of it, so a cached page is served before PHP is even consulted, and free SSL is reissued long before anyone has to think about it.
- The log query, written out
- Status codes used precisely
- Worker cost accounted for
- Cross-linked to the next reading
Why HostingFast
Standard on every plan
Log-first, dashboard second
Where a raw log answers faster than a console, the entry shows you the query rather than the screenshot.
404 traffic, triaged
How to tell a lost visitor from a scanner in the same list of missing paths, using the referrer column.
The cost of an error page
What a rendered 404 does to PHP workers, and why a light template is a capacity decision.
Correct codes, not habitual ones
When 410 beats 404, when 301 beats both, and the case where a homepage redirect makes things worse.
Written by people on shift
These are the answers our engineers give in tickets, published where a search engine can deliver them first.
Linked to the neighbouring fix
Each entry points at the term that explains the reading you are about to take next.
Quick Start
From order to online
- 1
Rank missing paths by request count
Filter the access log to status 404 for the past seven days, count by path, and sort. The top of that list is your entire working set.
- 2
Keep only the ones with a referrer
Discard requests with no referrer and an obvious scanner signature. What survives is traffic a person or a crawler genuinely tried to reach.
- 3
Write rules, then curl each one
Add a 301 or a 410 per surviving path, then curl -I the original URL and confirm the status you get is the status you intended.
Built In
Loaded onto every plan
- LiteSpeed compiled into the server, not a caching plugin bolted on afterwards
- Daily backups with a self-service restore you run yourself from the panel
- In-place upgrades between plans — no migration when you outgrow one
- WordPress Toolkit handling core and plugin updates for you
- NVMe on every tier — the entry plan runs the same drives as the top one
- Year one of your domain included when you order annually
- cPanel, so every script and tutorial you already have still applies
- Money-back cover: 30 days on hosting plans, 7 on reseller
- Renewal billed at your signup rate — no year-two step change
- Mailboxes on your own domain, with IMAP, POP, SMTP and webmail
Frequently Asked
What people ask us most often
Do 404s in Search Console hurt rankings on their own?
No. A URL that never existed returning 404 is correct behaviour and crawlers expect it. What costs you is a 404 on an address that still carries inbound links, and a soft 404 quietly polluting what gets indexed. The report is a work queue, not a penalty notice.
How do I spot a soft 404 without checking every page?
Curl the URL of a deliberately broken path and read the first line: if the body says 'not found' while the status says 200, you have one. Most come from a plugin or a theme catching the miss and rendering a friendly page without setting the header.
What does support actually cover at three in the morning?
A human reply at any hour, with a scope that includes the practical jobs: DNS records, mailbox setup, a restore, a WordPress site that has stopped answering. Send a hard technical question in before you buy — the reply you get is a fair preview of the standard afterwards.
Can I run a restore without opening a ticket?
Yes. Every plan takes a daily backup and the restore runs from your own panel — files, databases or both — at whatever hour you discover the problem. Keeping an additional copy somewhere off our network remains good practice, and nothing in the platform stops you doing it.
Keep reading
Uptime
The share of time the platform answers, and how monitoring proves it.
301 Redirect
The permanent forward, and what each hop in the chain costs in round trips.
How to Fix a WordPress 500 Error
Reading the error log, isolating the cause and getting the site answering again.
Dedicated Servers
Bare metal with a control panel included and the specification stated up front.
Business Hosting
Shared hosting with the developer toolbelt: SSH, Node.js, Python and PostgreSQL.
Changing hosts? Run through our checklist first.
A straightforward sequence for a switch your visitors never feel: which files move first, how to shift email across without losing a single message, the right moment to repoint DNS, and the two mistakes behind almost all the downtime we get asked to rescue.
Stop paying PHP to say nothing is there.
LiteSpeed caching, NVMe storage and daily restores you run yourself, on a plan that renews at the rate you signed up at.
View Dedicated Servers plans