Knowing how to fix 404 errors SEO teams actually care about starts with a surprising fact: most 404 errors are harmless. Google says plainly that a 404 on a URL that should not exist does not hurt your site’s search performance. The real risk is narrower. It is the important URL that was deleted by accident, the page with backlinks that now leads nowhere, or the “not found” page that quietly returns a success code. This guide shows you how to tell the difference, find the 404s worth fixing, choose the right fix, and set up a routine so they do not pile up again.

Key takeaways

What a 404 Error Really Is

A 404 means the server could not find anything at the requested address. It happens when a page is deleted, a URL is renamed without a redirect, someone mistypes a link, or a bot probes for pages that never existed. Three related cases matter for SEO:

Single-page apps deserve a mention. If your app shows a “page not found” view but the server still answers with 200, every dead route becomes a soft 404. Make sure unknown routes return a real 404 status.

Do 404 Errors Hurt SEO?

Google’s help documentation says 404 errors generally will not affect your site’s search performance and can be ignored when the URLs should not exist. That does not mean you can stop caring. The damage comes from the cases where a 404 replaces something valuable:

The rule is to separate 404s into two groups: URLs that should return something useful, and URLs that should not exist. Fix the first group. Leave the second as a clean 404.

How to Find 404 Errors

No single source shows everything, so combine a few.

1. Search Console page indexing report

Open the Page indexing report and look at the “Not found (404)” and “Soft 404” reasons. Google notes that the 404 list covers URLs it found through a link or because the page existed before, that it keeps trying these URLs for a while but less often over time, and that the report shows only URLs that returned a 404 in the past month. Its own advice is to generally fix only the 404s for URLs you link to yourself or list in a sitemap.

2. A crawl of your own site

A site crawler lists every internal link that leads to a 4xx response and shows which pages contain those links. This is the fastest way to find fixable errors, because the broken link is on a page you control.

3. Server logs and CDN reports

Logs show which dead URLs real visitors and bots request most. Sort by hits and by referrer to see which ones deserve attention.

4. Analytics

If your 404 template has a distinct page title, you can build a report in Google Analytics 4 that lists the dead URLs visitors reach. Mark an event for 404 views if you want to monitor them over time.

Website audit finding broken links and 404 errors across a sitemap

A 90-Minute Quarterly Audit

A repeatable routine beats a one-off cleanup. Run these steps every quarter and after any redesign, migration, or content purge.

  1. Export (15 minutes). Download the 404 and soft 404 URLs from Search Console and the 4xx list from a fresh crawl. Merge them in one sheet.
  2. Add context (20 minutes). For each URL, add organic clicks, number of referring domains, and number of internal links pointing to it. Your analytics and backlink tool supply these.
  3. Triage (15 minutes). Assign each URL one outcome: restore, redirect, fix the link, or leave alone.
  4. Fix (30 minutes). Apply redirects, edit internal links, and correct any soft 404 templates.
  5. Verify (10 minutes). Re-crawl the fixed URLs. In Search Console, use Validate fix on the relevant issue. Google says validation can take about two weeks and stops if even one instance remains, so fix every instance before you click.

Example scenario: a hypothetical furniture retailer deletes 40 discontinued product pages. The audit shows that 31 have no traffic or links, 6 have backlinks from design blogs, and 3 are still linked from the main navigation. The retailer returns a clean 404 for the 31, redirects the 6 to the closest category pages, and removes the 3 navigation links. The work takes under two hours and touches only what matters.

Choosing the Right Fix

Situation Best response Why
Important page deleted by mistake Restore it Keeps the URL, links, and rankings intact
Page moved or renamed 301 redirect to the new URL Permanent redirects tell Google the target is the canonical page
Several old pages merged into one 301 redirect each to the merged page Consolidating is fine when the content truly matches
Content gone, no replacement Return 404 or 410 The correct signal for removed content
Internal link points to a dead URL Edit the link Removes the dead end at its source
Error page returns 200 Make it return 404 Fixes the soft 404
Spam or junk URLs with no value Leave as 404 or 410 Nothing to preserve

Redirect rules worth following

Server-side redirects are the most reliably interpreted. Google lists JavaScript redirects as a last resort because they may never be seen if rendering fails. On WordPress, a redirect plugin or your SEO plugin’s redirect module handles most cases without code.

Does 404 or 410 Matter?

A common belief is that 410 removes a URL from Google faster. Google’s help page on 404 errors states that it currently treats 410 the same as 404, and its HTTP status documentation lists 410 alongside 404 under the same handling. Use 410 if it fits your workflow, such as when cleaning up pages after a hack, but do not expect faster removal from the index. For urgent removal of sensitive content, use the removal tools in Search Console and also fix the page itself.

Build a 404 Page That Helps

A custom 404 page will not change rankings, but it can save a visit. Keep it simple:

Make sure the page really returns a 404 status. Google lists redirecting missing pages to the homepage and showing filler content under a success code as ways to create soft 404s. To check, load a made-up URL and inspect the response status in your browser’s developer tools or a header checker.

Custom 404 error page design with search bar and helpful navigation links

Handling Migrations and Large Sets of URLs

When a redesign changes hundreds of URLs, individual redirects are impractical. Build a complete old-to-new map before launch, including images, scripts, and stylesheets that have their own URLs. Google’s site move guidance recommends storing the map in a database or as rewrite rules, using server-side permanent redirects, and testing with the URL Inspection tool or scripts. Pattern-based rules help when the new structure follows a predictable change, such as removing a date from a path. Test each rule on a sample first, and expect some ranking movement while Google processes the change. Our website migration SEO checklist covers the full process.

Technical hygiene extends beyond redirects. If you are reviewing how crawlers and AI tools see your site, our article on llms.txt explains what that file does and does not do.

Preventing 404s

Common Mistakes

Frequently Asked Questions

Should I redirect every deleted page?

No. Redirect when there is a close replacement. Otherwise, a clean 404 is the correct response.

How long does Validate fix take?

Google says validation typically takes up to about two weeks, and you will get email updates. Fix every instance first.

What is the quickest check for a soft 404?

Run a live test in the URL Inspection tool and compare what the page shows with the status code it returns. A “not found” message with a 200 code is a soft 404.

Sources

Leave a Reply

Your email address will not be published. Required fields are marked *