Why are redirects essential during a website redesign?

What does "maintaining appropriate signals" really mean?

When Google talks about signals, it refers to all the historical data accumulated by a URL: its PageRank, the backlinks pointing to it, its click history, its presumed conversion rate, its freshness, and its update frequency.

Without a redirect, these signals remain orphaned on the old URL, which has become a 404. Google then has to start from scratch to evaluate the new page — as if it just got created. The search engine doesn't spontaneously know it's the same content that has been moved.

Why does Google specifically emphasize redesigns?

Because it's the time when technical teams focus on design, UX, and structure — often overlooking SEO continuity. A redesign frequently involves architectural changes: shortened URLs, restructured categories, and removed parameters.

If every old URL does not explicitly point to its new version, Google sees hundreds or thousands of indexed pages disappearing at once. The crawl budget is wasted re-crawling 404s, and the engine loses time trying to understand the new hierarchy instead of transferring authority immediately.

What redirects does Google specifically expect?

We're talking about permanent 301 redirects — never temporary 302 redirects that would suggest the old URL might return. Each mapping should be 1:1 whenever possible: one old page leads to its new version, not to a generic category page.

Google favors granularity: redirecting /old-product-123 to /new-product-123 retains signals better than redirecting to /products. If a page has no real equivalent, a 410 (Gone) is cleaner than a 404, but it still means a loss of signals.

• Permanent 301 redirects are mandatory for each migrated URL
• 1:1 Mapping URL by URL, no bulk redirects to generic pages
• Setup before the switch, tested in pre-production on a sample of URLs
• Post-redesign monitoring via Search Console to detect unexpected 404s
• Validation crawl with Screaming Frog or Oncrawl to check redirect chains

Is this statement consistent with observed practices in the field?

Yes, and it's even one of the few points where Google's discourse perfectly matches observations. Redesigns without a redirect plan systematically lead to organic traffic drops of 30 to 70% in the 2-4 weeks post-migration. Signals do not transfer magically.

What Allan Scott doesn't mention: the transfer delay for signals varies significantly based on the site's crawl frequency. A site crawled daily recovers in 2-3 weeks. A site crawled weekly can take 2-3 months to stabilize its positions, even with perfect redirects.

What nuances should be applied to this statement?

Google simplifies by talking about "redirects" in the singular. In reality, redirect chains (A → B → C) dilute PageRank transfer and slow down crawling. A direct redirect A → C is always preferable. [To be verified]: Google officially states that PageRank transfers at 100% via a 301, but tests show a slight loss can occur — likely related to re-crawl and reevaluation delays.

Another point: redirects do not compensate for a radical content change. If the old page was about "running shoes" and the new one is about "beach sandals," Google will not maintain the initial rankings — signals are transferred, but topical relevance takes precedence.

In what cases does this rule not fully apply?

When one deliberately removes outdated content with no relevant equivalent, a 404 or 410 is preferable to a forced redirect to a generic page. Redirecting 50 old exhausted product pages to the homepage creates user frustration, and Google may interpret that as manipulation.

Similarly, for sites with millions of pages (classified ads, real estate), mapping each URL individually becomes technically unrealistic. We then favor redirects by smart regex rules, even if it means accepting a marginal loss of signals on less strategic URLs.

What should you do specifically before a redesign?

First, crawl the entire current site to extract all indexed URLs and those receiving organic traffic (Search Console, last 12 months). Then, create a comprehensive mapping file: old URL → new URL, validated column by column.

Test this mapping in a staging environment on a representative sample (important pages, deep pages, URLs with parameters). Ensure that no redirect chain exceeds 2 hops and that each redirect leads to a functional page (status 200), not another 301 or a 404.

What mistakes should be absolutely avoided?

Never redirect en masse to the homepage or to generic category pages. It's the worst strategy: Google detects that the target content does not match the initial intent, users bounce, and the signals still get lost.

Avoid also launching the redesign on a Friday night or just before a period of high seasonality. If something breaks, you won’t have the time or resources to fix it quickly. Schedule an intensive monitoring window of at least 72 hours post-switch.

How can you verify that the migration went smoothly?

Monitor 404 errors in Search Console daily for the first 2-3 weeks. Any sharp increase signals a mapping problem. Compare the volume of indexed pages before/after through a site: query and via the Coverage tab of GSC.

Monitor organic traffic by landing page in Google Analytics or Matomo. Strategic pages should regain their traffic levels in 2-4 weeks. If a key page remains behind, check that its redirect is properly in place and that the content hasn't radically changed.

• Extract all indexed URLs + those with organic traffic (Search Console 12 months)
• Create a comprehensive mapping file old URL → new URL, validated line by line
• Test in staging on a representative sample before the switch
• Implement redirects at the server level (Apache/Nginx/Cloudflare), never in JavaScript
• Check that no chain exceeds 2 hops and that each target returns a status 200
• Monitor 404s in Search Console for 3 weeks post-redesign