Could redirecting to the homepage during a redesign ruin your SEO efforts?

Why does Google insist so much on individual redirects?

The logic is simple: each URL accumulates authority through the backlinks it receives. When you redirect an old page to its direct equivalent, you transfer that authority to the new destination. PageRank is preserved, and the link remains relevant for the user.

Redirecting to the homepage is like throwing that authority into a void. The user clicks on a link meant to take them to a specific article and ends up on your homepage instead. They leave immediately. Google registers this pogo-sticking as a negative signal: the destination doesn't match the initial search intent.

What technically happens with a 301 redirect?

The 301 code signals a permanent move. Google understands that the old URL no longer exists and must transfer all its signals to the new one. The transfer of authority is never perfect—there's always a slight percentage lost—but it's negligible compared to a redirect to the homepage.

A redirect to the homepage is technically a valid 301. However, Google treats it as a soft 404 in many cases: the destination page doesn't meet the intent, so the engine may decide to de-index the old URL without transferring the equity. You lose everything.

Does this rule really apply to all types of content?

Let's be honest: no. If you shut down an entire section of your site without a direct equivalent, you have no choice. But even in this case, redirecting to a close category page is preferable to sending users to the homepage. The idea is to minimize relevance loss.

For outdated content without a logical successor, a 410 Gone is often cleaner than an artificial redirect. Google appreciates clarity: if the resource no longer exists and has no replacement, it's best to say so outright. The 410 quickly frees up crawl budget faster than a redirect to a generic page.

• Individual 301 redirects: maintain authority and thematic relevance between old and new URLs.
• Bulk redirect to the homepage: dilutes PageRank, degrades UX, generates negative behavioral signals.
• Potential soft 404: Google may ignore a 301 redirect to a non-relevant page and treat the old URL as deleted.
• Alternative to 301: the 410 Gone for content that has been permanently removed without a logical equivalent.
• Edge case: entire sections closed without a successor—prefer a redirect to the closest category rather than the homepage.

Is this statement consistent with field observations?

Absolutely. In dozens of monitored migrations, sites that redirect to the homepage lose between 40 and 70% of their organic traffic in the three months following. Those who map out cleanly URL by URL see an initial drop of 10-20% that recovers in a few weeks. The difference is dramatic.

The problem is that many clients or decision-makers don't grasp the stakes. They see a redesign as a reset and think Google will ‘relearn’ their site. No. Google does not forget. It actively seeks to reconcile the old structure with the new. If you provide a shaky mapping, it penalizes the site.

What nuances should be added to this rule?

Not all pages deserve a redirect. An old URL with zero backlinks, zero traffic, and zero indexing can be left returning a 404 without harm. Exhaustive mapping is time-consuming: focus on pages that generate traffic or have incoming links.

Another point: redirect chains are toxic. If A redirects to B which redirects to C, Google seldom follows beyond the second jump. During a redesign, ensure that your new URLs do not themselves point to other redirects. Clean everything up before launch.

In what scenarios doesn't this rule strictly apply?

When you close a line of obsolete products without a direct replacement, redirecting to a relevant parent category remains acceptable. For example, if you stop a line of running shoes—redirect to the general 'Running Shoes' page, not the homepage. Google will accept the thematic logic.

For dated editorial content (news, past events), a 410 Gone is often more honest. Google understands that the information is no longer relevant and frees up crawl budget. [To be confirmed]: some complex cases (multilingual site, domain consolidation) may justify temporary redirects to intermediary pages, but this is rare and risky.

What should you practically do before launching a redesign?

Crawl your existing site with Screaming Frog or Oncrawl to extract the complete list of indexed URLs. Then export Google Analytics (URLs generating traffic over the past 12 months) and Google Search Console (URLs with impressions). Cross-reference these three sources to identify critical pages.

Build a mapping spreadsheet: column A = old URL, column B = corresponding new URL. For each row, manually verify that the theme and intent are aligned. If an old page has no strict equivalent, document the reason and propose an alternative (parent category, 410, 404).

What mistakes should be absolutely avoided during implementation?

Never redirect using JavaScript or via meta refresh. Google may ignore them or process them with a delay. 301 redirects must be server-side (Apache, Nginx, .htaccess, CDN rules). Test each redirect with a tool like Redirect Path or httpstatus.io before the launch.

Avoid temporary 302 redirects ‘while waiting to see’. Google will not transfer authority. If you’re uncertain about a destination, it’s better to leave a temporary 404 and redirect properly later than to create a chain or a poor permanent mapping.

How to check that everything works after migration?

Set up post-migration monitoring: watch server logs for unexpected 404s, track the evolution of organic traffic by segment (brand, generic, long tail), and inspect Google Search Console for crawling errors. A spike in 404s signals incomplete mapping.

Reinject your old XML sitemap into Search Console for a few weeks. Google will recrawl the old URLs, detect the 301s, and update its index. Concurrently, submit the new sitemap. Both must coexist briefly to accelerate the transition.

• Crawl the current site (Screaming Frog, Oncrawl) and extract all indexed URLs
• Cross-reference with Google Analytics and Search Console to identify pages with traffic and backlinks
• Create a 1:1 mapping between old and new URLs, validating relevance manually
• Implement 301 redirects server-side (Apache, Nginx, CDN) — never in JS
• Test each redirect before going live (httpstatus.io, Redirect Path)
• Submit both the old and new XML sitemaps to Google Search Console during the transition
• Monitor 404s, organic traffic, and GSC errors for 3 months post-migration