Google 建議採用自訂 404 頁面，並更審慎地設定重新導向

A missing page does not automatically harm a site’s Google rankings. Google’s recent guidance instead places the emphasis on handling dead URLs accurately and helping visitors recover when a page is unavailable.

In a Google-hosted discussion summarized by Search Engine Journal’s report on custom 404 pages, Google’s Gary Illyes and Cherry Prommawin described 404 errors as a normal part of the web. Their practical message is straightforward: redirect a retired URL only when a truly relevant replacement exists, return a 404 or 410 when it does not, and make the error page useful to the person who reached it.

That distinction matters for SEO teams that have historically treated every reported 404 as an urgent defect to eliminate. A cleaner process can protect user experience while keeping status codes meaningful for crawling and indexing.

Google’s three-step approach to dead URLs

The guidance can be reduced to three decisions, each based on what actually happened to the missing content.

1. Redirect when there is a relevant replacement. If an old product, article, location page, or resource has moved to a page that satisfies substantially the same need, a redirect can take users and search engines to the appropriate destination.
2. Return a 404 or 410 when there is no replacement. A 404 means the resource was not found. A 410 signals that it is gone. Both are valid responses when the former URL should no longer exist.
3. Provide a helpful custom 404 page. Navigation, on-site search, and links to relevant sections can help visitors continue their journey instead of abandoning the site.

The key is relevance. Redirecting an unavailable URL to an unrelated homepage, category, or popular article may conceal the missing resource without solving the visitor’s problem. It also makes it harder to understand the site’s real URL history and content lifecycle.

Why 404s are not automatically an SEO problem

Google’s position is that 404 and 410 responses are normal signals. They tell crawlers that a URL does not contain an available resource. A site is not penalized simply because some URLs return not-found responses.

This is different from an accidental server failure. A server error can prevent Google from reliably accessing content and may need technical investigation. A correctly served 404 or 410 communicates an intentional, understandable state: the content is unavailable.

The reporting also notes Google’s view that 404s do not consume crawl budget in the same way as server errors. That does not mean teams should ignore every not-found URL. Large volumes of unexpected 404s can still reveal broken internal links, faulty migrations, expired campaigns, malformed URLs, or missing assets that create a poor experience.

The useful question is not, “How do we make the 404 report disappear?” It is, “Which missing URLs represent an avoidable journey failure, and which correctly represent retired content?”

What a useful custom 404 page should do

A custom error page cannot restore missing content, but it can make the next action clear. Google recommends a user-centric approach, and the reported discussion specifically points to navigation, search, and links to relevant content.

For most sites, a custom page should retain familiar branding and site navigation while clearly stating that the requested page is unavailable. It can then offer a limited number of recovery paths, such as:

• A site-search option for visitors who know what they were seeking.
• Links to primary sections, product categories, documentation, or current resources.
• Contextual suggestions where the site can reliably infer a nearby relevant destination.
• A way to report a broken link, particularly for support-heavy, publisher, or ecommerce sites.

Avoid presenting the page as if the original content still exists. The HTTP response itself should remain a genuine 404 or 410, rather than returning a successful page response with an error message. That latter pattern can create a soft 404, where Google sees a page that appears to be missing despite a different response signal. Soft 404s can affect crawl behavior and deserve investigation.

A practical workflow for redirects and retired content

Redirect decisions work best when they are part of ongoing site maintenance, not a one-time cleanup exercise after a redesign. Start by reviewing sources of missing-URL traffic, including internal links, external referrals, site migrations, discontinued inventory, and old campaign URLs.

Then classify each meaningful URL:

• Moved or replaced: Redirect to the closest page that fulfills the original intent.
• Permanently retired with no equivalent: Serve 404 or 410 and offer recovery options through the custom page.
• Broken internally: Fix or remove the internal link, then decide whether a redirect is warranted.
• Unknown or malformed: Confirm that the server returns the appropriate not-found response rather than generating thin substitute pages.

This approach prevents redirect chains and indiscriminate redirects from accumulating over time. It also preserves a clearer relationship between the URL a visitor requested and the content the site can genuinely provide.

The relevance for AI-assisted discovery and GEO

There is no evidence in this guidance that a polished 404 page directly improves visibility in AI-generated answers. The more defensible GEO implication is indirect: reliable URL management makes a website easier for people and crawlers to navigate, understand, and maintain.

For content that supports search visibility, citations, or brand discovery, stable URLs and accurate status codes reduce ambiguity. A discontinued page should not point broadly to an unrelated destination merely to avoid a 404. Conversely, a current replacement should be clearly reachable when one exists. These practices support a coherent content architecture across conventional search and AI-assisted journeys.

If retired pages once attracted links or referrals, a relevant successor can preserve a useful path for those visitors. If no successor exists, a helpful 404 page gives them an honest route back into the site.

If dead URLs, soft 404s, and unclear replacements are complicating your content architecture, create a GEO Search Leads account to begin assessing your website’s GEO readiness and identify optimization opportunities. A structured review can help teams focus on pages and journeys that deserve attention, rather than treating every valid not-found response as a search problem.

Frequently Asked Questions

Do 404 errors cause a Google ranking penalty?

No. Google treats correctly served 404 and 410 responses as normal indicators that a page is unavailable. Their presence alone does not create a ranking penalty.

When should a website redirect a missing URL?

Redirect a missing URL when there is a genuinely relevant replacement page that meets substantially the same visitor need. Do not use a broad or unrelated redirect simply to eliminate a 404.

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

A 404 indicates that a resource was not found. A 410 indicates that it is gone. Both can be appropriate when no replacement exists.

Can a custom 404 page help users?

Yes. Useful navigation, on-site search, and links to relevant sections can help visitors recover after reaching an unavailable URL. The page should still return a genuine 404 or 410 response.

Conclusion

Google’s guidance favors accuracy over cosmetic cleanup. Use redirects for real replacements, use 404 or 410 responses for genuinely retired URLs, and make not-found pages useful enough to keep visitors moving. That combination supports better site maintenance, clearer crawling signals, and a more reliable path through the content that remains available.