Use a 301 redirect only when a missing URL has a clear, relevant replacement; otherwise, return a useful 404 page. Redirecting every broken URL to the homepage is not a cleanup plan. It confuses users, wastes crawler time, and can create soft 404 signals.
TLDR: A 301 redirect is best when the old URL has moved to a closely matching new URL, such as /pricing-old moving to /pricing. A 404 page is better when the content is gone and no suitable replacement exists. In one common audit pattern, a site with 1,000 missing URLs might redirect 240 to relevant pages, leave 680 as proper 404s, and fix 80 internal links. That approach is cleaner than sending all 1,000 to the homepage and hoping search engines sort it out.
What a 301 Redirect Actually Tells Search Engines
A 301 redirect says, “This page has permanently moved.” It passes users and search engines from the old URL to the new one. Used well, it protects rankings, backlinks, and user trust.
Used poorly, it creates noise. If a discontinued product URL redirects to an unrelated blog post, the user lands somewhere they did not ask to go. Search engines may treat that as a bad signal. They may also ignore the redirect if the target is not relevant.
Good 301 redirect use cases include:
- Changed URL structure: /services/web-design becomes /web-design-services.
- Merged pages: Three weak articles are combined into one stronger guide.
- Product replacement: An old model redirects to a newer version with similar features.
- Domain migration: A business moves from one domain to another.
The rule is simple: redirect when the intent still matches. If the user wanted waterproof hiking boots, do not send them to a general footwear category unless that is the closest useful page.
When a 404 Page Is the Right Choice
A 404 status code says the requested page was not found. That sounds bad, but it is not always a problem. Websites change. Products sell out. Old campaigns end. Staff profiles disappear. Not every missing URL deserves a redirect.
A proper 404 helps search engines drop dead URLs from the index over time. It also gives users a clear message instead of sending them on a strange detour. Honestly, it feels like some sites are terrified of 404s, so they redirect everything to the homepage. That usually makes the experience worse.
Use a 404 when:
- The page has no relevant replacement.
- The content was thin, outdated, or no longer useful.
- The URL was created by spam, filters, tracking errors, or typos.
- The product or service is gone and nothing similar exists.
A 404 should not be a dead end. A strong error page includes:
- A clear message that the page cannot be found.
- A search box or site search link.
- Links to major categories, support, or popular resources.
- A simple path back to the homepage.
- Clean branding and plain language.
301 Redirect vs 404 Page: The Practical Decision
The best decision starts with user intent. Ask one question: What did the visitor expect to find? If you can answer that with a highly relevant live page, use a 301. If you cannot, return a 404.
| Situation | Best Response | Reason |
|---|---|---|
| Old blog post replaced by a better version | 301 redirect | The topic still exists in a stronger form. |
| Deleted product with a direct successor | 301 redirect | The user can still satisfy the same need. |
| Expired hiring page from three years ago | 404 or 410 | The page no longer serves a current purpose. |
| Random URL generated by a bot | 404 | There is no real user intent to preserve. |
| Old category merged into another category | 301 redirect | The new category is a close match. |
There is also a 410 Gone status. It tells search engines the page was removed on purpose. A 410 can be useful for content that is permanently gone and should be dropped faster. Still, for most websites, a clean 404 is enough.
The Homepage Redirect Trap
Redirecting all missing URLs to the homepage looks tidy in a report. It is not tidy in real use. A person clicks a link to a specific product review and lands on the homepage with no explanation. That adds friction. It also hides the real issue from your team.
Search engines can class these redirects as soft 404s. That means the server returns a success or redirect response, but the content looks like an error or mismatch. It drives me crazy that some audit tools still show this as “fixed” just because the old URL no longer returns 404. Technically, the report is green. Practically, the problem is still sitting there.
How to Audit Missing URLs
Start with reliable data. Use server logs, analytics, crawl tools, and search console reports. Do not treat every missing URL as equal. A broken URL with ten visits in a year does not deserve the same attention as one with 5,000 visits and 120 backlinks.
Group missing URLs into buckets:
- High value: Traffic, backlinks, conversions, or recurring visits.
- Relevant replacement exists: Good candidates for 301 redirects.
- No replacement: Keep as 404 or use 410 if truly gone.
- Internal link errors: Fix the source link instead of relying only on redirects.
- Spam or junk URLs: Leave as 404 and ignore unless they cause crawl issues.
For example, an ecommerce site may find 3,200 missing URLs after a platform migration. After review, 900 may point to retired products, 400 to categories that changed names, 1,600 to junk filter combinations, and 300 to broken internal links. The right plan would not use one rule for all of them. It would redirect the category changes, map valuable retired products to close alternatives, fix internal links, and leave junk URLs as 404s.
SEO Impact: What Matters Most
A 301 can preserve value when there is a strong match. That is the main SEO benefit. It helps search engines connect the old URL’s signals to the new page. But relevance controls how useful that redirect is.
A 404 is not an SEO disaster by itself. Search engines expect websites to have some missing URLs. Problems start when important pages vanish, internal links point to errors, or users hit dead ends on key paths. If a checkout help page returns 404, that is urgent. If a five year old campaign URL returns 404, it may be fine.
Watch these metrics after changes:
- 404 hits per week: Look for spikes after migrations or redesigns.
- Organic landing page drops: Check if former ranking URLs were removed.
- Backlinks to missing pages: Redirect only when there is a close match.
- Soft 404 reports: Review weak redirects and thin target pages.
- User exits from 404 pages: Improve links and search options if exits are high.
Best Practice Checklist
- Do not redirect every 404 to the homepage.
- Use 301 redirects for permanent moves with matching intent.
- Keep true missing content as 404, or use 410 when removal is final.
- Fix internal links that point to missing URLs.
- Monitor server logs after launches, migrations, and bulk content removals.
- Review redirects every few months. Old chains and loops slow users down.
- Make the 404 page useful. It should help people recover fast.
The serious answer is not “301 or 404.” The serious answer is match the technical response to the user’s intent. Redirect when you can send someone to a genuinely useful replacement. Return a clear 404 when the content is gone. That keeps your site honest, easier to maintain, and far less annoying for real users.