You know the feeling. You click a link on your own site, expecting a service page, a product, a booking form, and instead you get that flat, unhelpful message. Web page not found.
For a small business owner, that moment isn't just annoying. It's expensive in all the ways that are hard to see. A customer was ready to learn more, buy, book, or call. Instead, they hit a dead end. Some will try again. Plenty won't.
I've seen this happen after website redesigns, menu updates, old blog clean-ups, product removals, and those innocent little slug changes someone makes in WordPress because the new URL “looks cleaner”. Then a week later, enquiries feel patchy, a campaign link is off, or a popular page disappears from the path people normally take.
That's why this guide isn't going to talk to you like a server manual. If you searched for HTTP 404 web page not found, what you probably want is simple. What does it mean, why does it matter, and what should you do today so customers stop falling through the cracks?
That's the core issue. Not the code itself. The interrupted journey.
That 'Web Page Not Found' Feeling
A 404 often shows up at the worst possible moment.
Someone clicks from Google. Or from Instagram. Or from an email you sent last month that's still doing the rounds. They're interested enough to take action, and then your website says, in effect, “Sorry, no idea.”
That little moment chips away at trust.
Your customer doesn't see a status code
They see a business that feels disorganised.
If they were trying to book a service, they wonder if the business is still active. If they were trying to buy a product, they wonder whether checkout will be just as messy. If they were looking for pricing or contact details, they may not bother digging around to find another way in.
A missing page lands differently depending on context, but the emotional reaction is usually the same. Friction. Doubt. Exit.
A 404 is a business problem first. The technical fix matters, but the customer's experience is what hurts you.
I've seen sites where the homepage looks polished, the branding is sharp, the ads are running, and then one old navigation link or deleted page sends people into a blank cul-de-sac. It's like having a lovely shopfront with one door that opens into a broom cupboard.
The damage isn't always obvious
This is what makes 404s so frustrating. They don't always trigger a dramatic failure.
You can still have a working website and still be losing people every day from broken product links, renamed service pages, old campaign URLs, and blog posts that got moved without a redirect. No sirens. No big alert. Just small leaks in the bucket.
A few common ways it happens:
- After a redesign your old URLs vanish and nobody maps them properly.
- After deleting old content links from search results or bookmarks still point to the removed page.
- Inside your own menus a typo or outdated path sends visitors nowhere.
- On eCommerce stores discontinued products get removed without a sensible next step.
That last one is especially common. A product goes out of stock or is retired, and the page gets deleted. But customers, search engines, and external links don't know that. They keep arriving at the old address.
Why small businesses feel this more
Larger teams usually have someone watching technical reports. Small businesses often don't. The website gets updated between everything else. Fair enough.
But that means a 404 can sit there for ages, especially if the owner only checks the pages they use most often. Meanwhile, someone trying to reach an older service page from Google has a completely different experience.
And that's the point. Your website isn't judged by the pages you know are working. It's judged by the page the visitor lands on.
So What Is a 404 Error Really
At the plain-English level, a 404 Not Found means your website is up, but the specific page someone asked for isn't there.
Imagine a postie delivering a letter. The postie gets to the right suburb and the right street. No problem there. But the house number on the envelope doesn't exist, or it used to exist and now it doesn't. So the delivery fails.
That's basically what happens with a 404.
What the browser and server are actually doing
Here's the simple version:
- Your visitor's browser asks for a page.
- Your server checks whether that page exists at that exact address.
- It can't find a match.
- It sends back a 404 Not Found response.
According to Wikipedia's explanation of HTTP 404, that response means the client successfully reached the origin server, but the server cannot locate the requested resource. That matters because it's different from a DNS failure, where the website name itself can't be resolved at all.
So if you're dealing with a 404 spike, don't start by assuming the whole site is down. In many cases, the fastest checks are much simpler.
Check the exact URL before anything else
A lot of 404 trouble comes from small details people miss in a hurry:
- Casing issues where one version uses capitals and another doesn't
- Trailing slash differences where one path ends with a slash and another doesn't
- Changed permalinks after a CMS update or content tidy-up
- Routing or deployment quirks after a launch
- Content migration leftovers when old paths weren't carried across
Practical rule: If the website loads but a page doesn't, inspect the exact URL path first. Don't jump straight to hosting panic.
What a 404 is not
This helps clear the fog.
| Situation | What it usually means |
|---|---|
| 404 Not Found | The site is reachable, but that page is missing |
| DNS failure | The website name itself can't be found |
| 500-style server issue | The server hit an internal problem while trying to respond |
That distinction matters because the fix changes completely. If the site can't be found at all, you're in one bucket. If the site is there and only one page is missing, you're in another.
For most business owners, that's good news. A 404 usually points to a content, permalink, redirect, or linking issue. Annoying, yes. But often much easier to fix than a full infrastructure problem.
Why a 404 Is More Than Just a Broken Link
A lot of guides treat 404s like housekeeping. Bit of tidying up. Nice to have.
That undersells it.
A 404 can interrupt a sale, waste paid traffic, undermine trust, and make your site feel neglected. Customers don't separate “technical issue” from “brand experience”. They just remember that your website sent them nowhere.
The customer impact is immediate
If someone clicks a service page from your nav and lands on a 404, they don't think, “Ah, this is an HTTP status code issue.” They think, “This site's a bit broken.”
That matters more when the visitor is close to a decision.
A person browsing a blog post might forgive it. A person trying to get a quote at 4:45 on a Thursday probably won't. Same with someone tapping through from a product ad. You paid to bring them in, then dropped them at a dead end.
A rough pattern I've seen is this:
| Visitor intent | What a 404 feels like to them |
|---|---|
| Researching casually | Mild frustration |
| Comparing suppliers | Doubt about professionalism |
| Ready to buy or enquire | A reason to leave immediately |
Search engines notice different kinds of missing pages
Many business owners get tripped up. They only think about the ugly page the user sees.
But 404s also show up in search and crawl reporting. As MDN's 404 reference explains, a 404 occurs when a server cannot find the requested resource, and the practical significance for Australian websites is that they need to monitor both user-facing 404 pages and search-engine crawl errors. It also notes that a 404 does not tell users whether the missing resource is temporary or permanent, which can affect user experience and discoverability across sites.
That's the important bit. The human problem and the crawl problem are related, but they aren't identical.
You might have:
- Users landing on a missing page from an old ad, bookmark, or external link
- Search engines crawling dead URLs that still exist in old references
- Soft 404 issues where a page looks broken or irrelevant even if it doesn't behave like a clean missing-page response
Not every 404 deserves the same fix
Practical judgement matters here.
If a page moved to a clear replacement, redirect it. If there's a typo in your nav, correct the link. If content is gone for good and there's no sensible equivalent, a true 404 may be fine. If something was permanently removed, there are cases where a different status is more appropriate, but the bigger business question is simpler. Are you helping people continue, or just abandoning them?
A bad 404 isn't just a missing page. It's a missing next step.
That's why “just add redirects everywhere” can also go wrong. Redirecting every dead URL to the homepage often feels lazy and confusing. Visitors click for one thing and land somewhere generic. Better than a wall, perhaps, but still not great.
The best fix is usually the most relevant one. Closest match. Clearest path forward. Least confusion.
How to Find and Fix Your Pesky 404 Errors
Most site owners don't struggle with the idea of a 404. They struggle with finding the ones that matter.
That's the essential job. Not random cleanup. Prioritised cleanup.
A useful starting point is this short walkthrough:
Start with reports, not guesswork
One of the best practical points on this topic comes from Plausible's guide to tracking 404 errors. It notes that many explainers obsess over basic fixes but miss the operational question SMEs face, which is how to discover which 404s are hurting traffic. It also points out that Google Search Console's Index report includes both Not found (404) and Soft 404 exclusions, while analytics tools can isolate 404 page views and server logs can show repeated broken requests.
That gives you a sensible workflow.
In Google Search Console
Look for pages flagged under indexing exclusions, especially:
- Not found (404) for URLs Google tried to access
- Soft 404 for pages that aren't serving useful content in a way Google expects
This is often where you spot old URLs from migrations, deleted pages, and broken internal references.
In GA4
GA4 helps you isolate the pages people hit when they see a not-found experience.
Use it to answer practical questions like:
- Which missing pages are landing pages?
- Which traffic sources are sending people there?
- Are these visitors coming from search, ads, email, or internal links?
That tells you what's costing you attention right now, not just what exists in theory.
Match the fix to the cause
This is the part people overcomplicate. Most 404s fall into familiar buckets.
| Cause | Best response |
|---|---|
| Internal link typo | Edit the link at the source |
| Page moved to a new URL | Add a 301 redirect to the new page |
| Page deleted with a close replacement | Redirect to the most relevant alternative |
| Page removed with no useful equivalent | Keep the 404, but make the experience helpful |
| Old sitemap entry | Remove outdated URLs from the sitemap and resubmit it |
If your sitemap is out of date, it's worth understanding what a sitemap is and how it helps search engines so you're not inviting crawlers into pages you no longer want indexed.
Fix the source when you can. Redirect when it helps. Leave a genuine 404 when the content is truly gone and there's no honest substitute.
A few platform-specific realities
For WordPress, permalink changes and deleted pages are common culprits. Redirect plugins can help, but they don't replace a proper audit. Also, industry diagnostics around GA4 tracking note that a small percentage of 404 traffic is normal, but a high share of bad clicks often points to broken internal links, especially in menus or navigation, and can be traced by filtering landing pages and traffic sources in analytics. That same guidance also warns that a page can appear to exist in WordPress or through caching while search systems still see a 404, which is why custom 404 pages, broken-link checks, and audit workflows matter so much for SMEs, as discussed in this GA4 and 404 troubleshooting video.
For Shopify, old product and collection URLs are frequent offenders after catalogue changes. Don't just delete and move on. Check whether the old product should redirect to a successor product, a relevant collection, or stay gone.
For Squarespace and Framer, the issue is often simpler but easier to overlook. A page gets renamed, navigation updates lag behind, and external links keep pointing at the old path.
A quick action list for today
- Open Search Console and review indexing exclusions
- Check GA4 for not-found page titles or paths
- Sort by importance by looking at key landing pages, money pages, and high-intent content
- Repair internal links first because they're fully under your control
- Add 301 redirects for moved pages with a clear replacement
- Update your sitemap and navigation so you stop creating fresh 404s
That's usually enough to stop the bleeding fast.
Turning Your 404 Page Into a Helpful Guide
Even on a tidy website, some 404s will always happen. People mistype URLs. Old bookmarks stick around. Other sites link to the wrong page. You can't eliminate every dead end.
You can make the dead end useful, though.
What a good 404 page should do
The default server message is rarely enough. It's blunt, cold, and gives the visitor no clear next move.
A good custom 404 page should do three jobs:
- Acknowledge the problem clearly
- Offer a fast path forward
- Keep the tone consistent with your brand
That doesn't mean you need to be quirky for the sake of it. A bit of personality is fine. Clarity matters more.
A simple version of good 404 microcopy might look like this:
We can't find that page. It may have moved, the link may be outdated, or the address may be incorrect. Try searching below, head back to the homepage, or contact us if you need a hand.
That's calm, useful, and human.
The elements worth including
If you only add one thing, add navigation. If you add a few more, make them these.
- A clear message so people know what happened
- A search bar so they can look for the page or product themselves
- Links to important pages like services, shop categories, contact, and homepage
- Brand consistency so the page still feels like part of your site
- A contact option for people who were trying to do something important
If you run an online store, links to top categories and current promotions often work better than a generic apology. If you're a service business, links to your core services, booking page, and contact page usually do the heavy lifting.
For businesses with support content or product setup information, I also like how this merchant's guide to support docs frames documentation as part of the customer journey. The same thinking applies to a 404 page. Don't treat it as a failure screen. Treat it as a recovery screen.
Platform-by-platform fixes
Here's the practical version for common platforms.
WordPress and WooCommerce
Most modern themes let you customise the 404 template. If you're using the Site Editor, check your templates and look for the 404 layout there.
Useful additions:
- search
- product categories or service links
- latest blog posts only if they're helpful
- a visible contact button
If your site handles bookings, keep that booking button on the 404 page. Don't make people start from scratch.
Shopify
Shopify themes usually include a 404 template you can edit in the theme customiser or code editor.
For stores, I'd prioritise:
- featured collections
- site search
- best sellers
- a button back to the shop homepage
If a lot of 404s come from retired products, don't rely only on the custom 404 page. Add redirects where the intent is obvious.
Squarespace
Squarespace makes it fairly straightforward to set up a branded 404 page. Keep it simple. Add a search block, a few key navigation links, and one strong call to action.
Framer
Framer gives you design freedom, which is lovely until someone forgets the basics. Make sure the 404 page still feels structured, accessible, and useful. Pretty is not enough.
That accessibility bit matters across every platform. If your custom error page is hard to read, keyboard-unfriendly, or confusing for assistive technology, it's doing half the job at best. This broader guide to website accessibility standards is worth a look if you want your fallback pages to be effectively usable, not just branded.
What doesn't work well
Some 404 pages try too hard.
A joke with no navigation isn't helpful. A dramatic illustration with no search bar isn't helpful either. And redirecting every missing URL to the homepage can leave users feeling lost rather than helped.
The best 404 pages are plainspoken and useful. They respect the visitor's time.
Keeping Your Website Healthy and 404-Free
The easiest 404 to fix is the one you never create.
That doesn't mean running your site like a full-time systems team. It means building a few habits into the way you already update content.
A maintenance rhythm that works
For most small businesses, a simple monthly check is enough to catch the obvious issues before they pile up.
That routine can be very light:
- Review Search Console for new missing URLs and soft 404s
- Check GA4 landing pages tied to your not-found page experience
- Test key menu links on desktop and mobile
- Look at recently changed pages especially renamed services, products, and blog URLs
- Update redirects after content removals or restructures
If you delete a page, decide straight away whether it should redirect, be replaced, or remain a true missing page. Don't leave that decision for later. Later is where broken journeys go to hide.
Be careful with page renames and clean-ups
Here, many fresh 404s begin.
You rename a page because the new URL reads better. Fair enough. But if the old one had traffic, backlinks, bookmarks, or campaign history, changing the address without a redirect is like moving shops and forgetting to tell anyone where you went.
A little discipline helps:
| Change you make | What to do with it |
|---|---|
| Rename a page URL | Add a 301 redirect from old to new |
| Delete a page | Send users to the closest relevant page, if one exists |
| Remove a product | Redirect thoughtfully or keep a helpful custom 404 path |
| Change navigation | Click every updated link yourself |
If you want that process handled consistently, a proper website maintenance plan makes life much easier than reacting to issues one by one.
A healthy website doesn't need perfection. It needs attention. Check the paths people use, keep your redirects organised, and treat every 404 as a sign to improve the journey rather than just patch the symptom.
If your site has broken links, missing pages, or a 404 experience that's silently costing you leads, Wise Web can help you sort it out properly. They build and maintain websites for Brisbane businesses across WordPress, WooCommerce, Shopify, Squarespace, and Framer, with a practical focus on usability, SEO, and the bits that directly affect enquiries and sales.