- A 404 is fine when a page is gone for good and nothing replaces it. Google's help says so directly.
- Add a 301 redirect only when the page moved or another page answers the same need.
- A soft 404 shows a "not found" message but returns a success code. Make sure your 404 page sends a real 404 status.
- Fix links on your own pages and in your sitemap first. Those are the 404s Google says are worth fixing.
- A helpful 404 page has a plain message, your normal menu and links to your main pages.
The short answer
A 404 is not an error you must always fix. If a page is gone for good and nothing replaces it, a 404 is the honest answer. Fix a 404 in three cases: the page moved (add a 301 redirect to the new address), your own site still links to it (change the link), or the URL is listed in your sitemap (remove it). Leave the rest.
Then check two things about the 404 page itself. It must send a real 404 status code, and it must help a lost visitor find the way back.
A real 404 and a soft 404
Every page a server sends comes with a status code. 200 means "here is the page". 404 means "there is no page at this address". Visitors never see the code, but search engines read it first.
A real 404 shows a "not found" message and sends the 404 code. Google's docs on HTTP status codes say URLs that are already indexed and return a 4xx status code are removed from the index. That is what you want for a page that no longer exists.
A soft 404 is the confusing one. Google's Page indexing report help describes it as a page that returns a user-friendly "not found" message but not a 404 response code. The visitor reads "page not found" while the server says 200, all good. Google recommends returning a 404 response code for pages that are truly not found. The same docs say a 200 page whose content looks empty or like an error message can also show up as a soft 404 in Search Console.
To see which one you have, type an address that cannot exist on your site, then look at the status code. Our free redirect checker shows the status of every hop and of the final page. The Network tab in your browser's developer tools shows it too.
When a 404 is fine, and when to 301
Google's help page puts it plainly: 404 responses are not necessarily a problem if the page has been removed without any replacement. If the page has moved, it says to use a 301 redirect to the new location.
| Situation | What to do |
|---|---|
| The page moved to a new URL | 301 to the new URL |
| The page was merged into another page that covers the same thing | 301 to that page |
| The page is gone and nothing replaces it | Leave the 404 |
| The URL never existed (a typo, a bot guessing addresses) | Leave the 404 |
| Your own pages link to the dead URL | Fix the link, whatever else you do |
| The dead URL is in your sitemap | Remove it from the sitemap |
Use a permanent redirect for a permanent move. Google's redirect docs recommend a permanent server-side redirect whenever possible, and its status code docs call a 301 a strong signal that the target should be processed, and a 302 a weak one.
One habit we advise against: sending every dead URL to the home page. Someone who clicked a link about pricing and lands on the home page has not been helped. Redirect only when the new page answers the same need. If nothing does, a clear 404 page is kinder.
What a helpful 404 page has
A visitor who lands here followed a link that broke. The page has one job: get them back on track. A good one has:
- A plain message. Say the page was not found, in words. No jargon, no blame.
- The normal header and footer. The menu is the fastest way back into the site.
- A link to the home page and to two or three of your most used pages, such as services, pricing or contact.
- A search box, if your site has search.
- A light page. It should load fast and not depend on parts of the site that might be down.
- The 404 status code. A lovely page that returns 200 is a soft 404.
A little personality is fine once the basics are there. Ours is a cookie you can take bites out of, with a link back to the site.
How to find broken links
There are two kinds of broken link: ones on your own pages, and ones on other people's sites that point at you. Three places to look:
- Google Search Console. Open the Page indexing report and look under the reasons pages are not indexed. "Not found (404)" lists URLs that returned a 404 when Google asked for them. "Soft 404" lists pages that look like an error but did not return the code. Google's help says it may have found a 404 URL through a link from another page, or because the page existed before and was deleted.
- A crawl of your own site. A link checker follows every link on every page and lists the ones that end in an error. This finds broken internal links before Google does.
- Your analytics. If your 404 page has its own title, you can filter page views by that title and see which addresses people actually hit.
Do not panic at a long 404 list in Search Console. Many of those URLs are old or were never real. Google's own advice in that help page: in general, fix only the 404 errors that you link to yourself or list in a sitemap.
Fix internal links first
Links on your own pages are fully in your control, and they are the ones your visitors click most. Work in this order:
- Menus, footers and buttons. One broken link in a footer is broken on every page.
- Links inside page and blog copy. Change each one to the correct final URL.
- Links that go through a redirect. They still work, but point them at the final URL anyway. It saves a hop, and it stops a redirect chain forming after the next site change.
- The sitemap. It should list only live pages that return 200.
- Links from other sites. You cannot edit those, so add a 301 from the dead URL to the best matching page. Our post on keeping backlinks working covers this step.
If you have a long list of old and new URLs to pair up, our free redirect map generator matches them and exports the redirects.
The 404 page in Webflow
Every Webflow site has a 404 page you can design. Webflow's 404 page help article says it sits under Utility Pages in the Pages panel, and you can customise it like any other page. Two details from that article:
- You cannot add Collection lists to the 404 page. Webflow's reason: the page should be available even if the CMS or other Webflow features are down.
- To test it, open a new tab and enter a URL on your site that does not exist.
Webflow's own tip there matches the list above: point visitors back to the home page or give them a navigation menu.
Redirects live in Site settings, under Publishing, in the 301 redirects section. Per Webflow's redirect help, you enter the old path and the new path, add the redirect and publish the site. The same article says you need a paid Site plan, or a Workspace with a paid Workspace plan, to add them. When you change a page's slug in Page settings, there is a box to permanently redirect the old URL to the new one, and Webflow then creates the 301 for you.
The 404 page in Astro
In Astro, the 404 page is a file. The Astro docs say you can create a 404.astro or 404.md file in src/pages, that it builds to a 404.html page, and that most deploy services will find and use it.
Two checks after you deploy:
- Open an address that does not exist on the live site and confirm you see your page, not the host's default one.
- Check the status code is 404. The host sends the code, so test it on the real host, not only on your computer.
Because it is a normal Astro page, it can use your site layout, so the header and footer come for free.
What to do next
- Type a made-up address on your site and check the status code. It should be 404.
- Open the Page indexing report in Search Console and read the "Not found (404)" and "Soft 404" lists.
- Fix the links on your own pages and clean the sitemap.
- Add 301 redirects only for pages that moved or have a true replacement.
- Give the 404 page a clear message, your menu and a few useful links.
Broken links are one part of a wider health check. Our website audit checklist lists the rest, in order. If you would like us to run the check on your Webflow or Astro site, send us the URL.



