Google’s 404 Guidance: Redirect Only True Replacements and Build a Better Missing-Page Experience

Google has reiterated that 404 errors should not be treated as an automatic SEO emergency. The more useful question is whether a missing URL has a genuine replacement and, if it does not, whether the site gives visitors a clear path forward.

In an episode of Google’s The Non-Canonical Cabinet, the company framed 404 handling primarily as a user-experience and business decision. The guidance offers a straightforward workflow: redirect a URL only when a closely relevant replacement exists, return a 404 or 410 when it does not, and make the missing-page experience helpful rather than a dead end.

That approach matters for sites with discontinued products, expired campaigns, changed editorial archives, migrations, and old links from other websites. It also pushes back on a common reflex: sending every unavailable URL to the homepage.

The three-step workflow for missing URLs

1. Redirect only to a true replacement

A redirect makes sense when the destination substantially satisfies the intent behind the old URL. Common examples include a product page replaced by a newer version, an article moved permanently to a new URL, or a consolidated service page that now contains the equivalent information.

In these cases, a permanent server-side redirect is generally the appropriate implementation. The key test is relevance, not simply the desire to avoid an error status.

A visitor seeking a specific discontinued product may reasonably be sent to its direct successor. They may not benefit from being sent to a broad category page, and they are unlikely to benefit from being sent to the homepage with no explanation. Google’s discussion cautions against these indiscriminate or “lazy” homepage redirects because they create a poor user journey.

Before adding a redirect, teams should ask:

• Is there a page that closely matches the old page’s purpose?
• Would a visitor reasonably expect this destination after following the old link?
• Is the redirect permanent, rather than a temporary workaround?
• Can the destination stand on its own instead of merely being the least-bad available page?

If the answer is no, preserving a clear missing-page response is usually more honest and more useful.

2. Return 404 or 410 when no replacement exists

A 404 status means the server cannot find the requested resource. A 410 status communicates that the resource is gone. In Google’s public 404 error guidance, the company says that 404 errors generally do not affect a site’s rankings, and that site owners can ignore them when there is no suitable replacement.

This is important because a valid 404 is not the same as a broken SEO implementation. A page that no longer exists, and has no relevant successor, should be allowed to say so through an appropriate HTTP response.

The choice between 404 and 410 should reflect the site’s own circumstances. A 410 can be useful when a business knows content was intentionally and permanently removed. A 404 remains appropriate when a resource cannot be found. In either case, the status code should match what users and crawlers receive.

Do not turn an unavailable page into a “soft 404.” This can occur when a URL appears to return a successful response but the visible page effectively says that the content is missing. Follow-up reporting has noted that soft 404s can create unnecessary crawl-budget concerns, unlike normal 404 responses that accurately communicate a missing resource. The practical objective is clarity: either serve a useful live page or return a genuine missing-page status.

A custom 404 page is for people first

Google’s recommendation to make 404 pages useful does not mean that every error page needs extensive design or promotional content. It means visitors should not be stranded after following an outdated bookmark, search result, campaign link, or external referral.

A practical custom 404 page can include:

• A plain-language explanation that the requested page is unavailable.
• Primary navigation so visitors can return to familiar areas of the site.
• Internal search, where the site has a useful search function.
• Links to key sections, such as products, services, help content, recent articles, or account support.
• A route to report a broken link when that is appropriate for the business.

The page should still return an actual 404 status code. A visually polished error page that returns HTTP 200 can confuse crawlers and may be interpreted as a soft 404. Technical teams should verify both the page template and the server response after deployment.

For ecommerce sites, this can mean directing visitors to a relevant category or search option rather than pretending an obsolete product still exists. For publishers, it may mean offering site search and links to current coverage. For service businesses, a concise route to current service pages or contact information may be more useful than a generic apology.

A practical implementation process

The guidance is especially helpful when applied during routine maintenance rather than only after a migration. Start with URLs reported in server logs, crawl reports, analytics, external-link reviews, or internal site audits. Then classify each URL by what happened to the underlying content.

This review should also identify patterns. A large number of missing URLs caused by internal links may indicate navigation, publishing, or migration issues that should be fixed at the source. External links to genuinely retired pages are different: the site can provide a useful 404 page without manufacturing an irrelevant redirect for each one.

What this means for SEO teams

The main lesson is not to optimize for a lower count of 404 reports at any cost. It is to make URL decisions that reflect content reality and user intent. Redirects are valuable when they preserve a relevant journey. Accurate 404 and 410 responses are valuable when that journey no longer exists.

That distinction can make maintenance work more efficient. Instead of creating broad redirect rules to make reporting tools look cleaner, teams can prioritize high-value URLs, broken internal paths, genuinely relevant replacements, and an error-page experience that helps users recover.

If outdated URLs, redirects, and missing pages are making it hard to understand where your site’s discovery journey breaks down, create a GEO Search Leads account. It can help you assess website GEO readiness and identify optimization opportunities around the pages and content paths that support clearer access to your information.

Frequently Asked Questions

Do 404 errors hurt Google rankings?

Google’s guidance says 404 errors generally do not affect rankings. If a missing URL has no relevant replacement, it can be left as a 404 rather than redirected solely to eliminate the error.

When should a site use a 301 redirect for a missing page?

Use a permanent redirect when there is a genuinely relevant replacement, such as a page that moved or a direct successor to a discontinued product. Do not redirect unrelated missing URLs to the homepage.

Should a custom 404 page return a 200 status code?

No. A custom 404 page should remain useful for visitors while returning an actual 404 status code. A page that looks like an error page but returns 200 may be treated as a soft 404.

What is the difference between a 404 and a 410 response?

A 404 says the requested resource cannot be found. A 410 says the resource is gone. Both can be appropriate when no relevant replacement exists, depending on whether the removal is known to be permanent.

Conclusion

Google’s guidance replaces blanket 404 avoidance with a more practical standard: match the response to the reality of the URL and the visitor’s likely intent. Redirect true replacements, use clear 404 or 410 responses for retired content, and ensure the missing-page experience gives people a useful next step.