To fix 404 errors at scale, collect every broken URL from several sources, rank them by backlinks, past traffic and internal links, then give each valuable URL a 301 redirect to its closest replacement or restore the page. Leave worthless URLs as a 404 or 410. Fix the source of the broken links last, so the errors stop returning.
Do 404 errors need fixing at all?
A 404 means the server could not find the page. Google has said that 404 errors on URLs that do not exist are normal and do not hurt the rest of your site. The harm comes from valuable URLs that now return 404: pages with backlinks, pages that earned traffic, and pages your own site still links to. For the wider question, read our short answer on whether 404 errors hurt SEO.
That is why scale changes the method. You cannot judge ten thousand URLs one at a time. You sort them.
Step 1: Collect every broken URL
Search Console is the start, not the full list. In the Pages report, open the Not found (404) reason and export the examples. Then add these sources:
Collect
Where broken URLs hide
Merge them into one sheet with one URL per row. Remove duplicates and trailing slash variants.
Pull from all of these
- Search Console Pages report, Not found (404) and Soft 404
- Server access logs: every URL Googlebot requested that returned 404
- A full crawl of your own site, to catch internal links to dead pages
- Backlink data: URLs on your domain that other sites still link to
- Analytics landing pages with past traffic that now show errors
- Your old sitemap and the list of URLs from before any migration
Step 2: Sort by value
Give each URL three scores: referring domains linking to it, clicks or sessions it earned before it broke, and the number of internal links pointing at it. A URL with any real score is worth saving. A URL with all zeros usually is not.
| URL type | Best fix |
|---|---|
| Page moved to a new address | 301 redirect to the new address |
| Page removed, close replacement exists | 301 redirect to the closest relevant page |
| Page removed by mistake | Restore the page and return a 200 |
| Removed permanently, nothing relevant to point to | Leave as 404, or return a 410 |
| Junk URLs from parameters or bad links | Fix the source, block crawling if needed, let them drop |
| Soft 404: empty page returning 200 | Return a real 404 or redirect, see the soft 404 guide |
Step 3: Redirect in bulk, not one by one
Group URLs by pattern. If an entire folder moved, one rule covers it. Write rules in your server config, a CDN rule set or your CMS redirect tool, not as a manual list of thousands of single lines where a pattern would do.
Send each URL to the most relevant page, not the homepage. Mass redirects to the homepage tend to be treated as soft 404s, so the old URL still earns nothing. Keep each redirect to one hop: old URL straight to final URL. Our redirect mapping guide walks through building the map for a large move, and our guide to soft 404 errors explains the homepage trap.
A practical test for each redirect: would a visitor who clicked the old link be glad to land on the new page? If the answer is no, the redirect is a poor match. In that case a clean 404 with helpful links on the error page serves people better, and it tells Google the truth about the page.
Step 4: Fix the cause so they stop coming back
Redirects patch the symptom. Find out why the URLs broke. Common sources are a migration without a redirect map, a CMS that changed URL structure, a deleted product category, a plugin that rewrote links, or internal links with typos. Update internal links to point at live URLs directly. Redirecting your own links wastes crawl effort.
Step 5: Verify and monitor
After you deploy, run your crawl again and confirm the redirects return a 301 and land on a 200 page. Use URL Inspection on a sample. Then watch the Pages report over the following weeks. Google recrawls on its own schedule, so the count falls gradually, not overnight. If it does not fall, the redirects are not firing or new broken links are being created.
On very large sites, a flood of dead URLs can also eat into your crawl budget. Our crawl budget guide explains when that becomes a real concern.
When to call for help
Call for help when the error list runs into tens of thousands, when the 404s began right after a migration and traffic fell with them, or when redirects are in place and the numbers are not improving. Those cases need logs, crawl data and backlink data read together. This is core work in our technical SEO fixes service. Send us the details in a free SEO triage and we will tell you which URLs matter and what to do with them.
FAQ
Questions owners ask us
Should I redirect every 404 error?
No. Redirect URLs that have a close replacement, backlinks, or past traffic. Let genuinely dead URLs with no value return a 404 or 410. Redirecting everything to the homepage can be read by Google as a soft 404, which solves nothing.
Is a 410 better than a 404?
Both tell Google the page is gone. A 410 says it was removed on purpose. Google treats them very similarly, so the choice matters less than making sure the right URLs are removed, redirected or restored.
How do I find 404s that Search Console does not list?
Search Console shows only a sample of what Google found. Pull the full picture from your server logs, a crawl of your site, your backlink data and your analytics landing pages. Our free SEO triage can help if the list is too big to handle by hand.
Get started