Website Redirects and SEO: Migration and Redesign Guide

Website redirects are one of the highest-risk parts of a migration, redesign, replatforming project, HTTPS move, domain change, or content consolidation. A good redirect plan helps users and search engines reach the right new URLs. A poor redirect plan can break traffic, waste crawl time, create soft 404s, split signals, damage analytics, and make a new site look weaker than the old one.

Redirects are not only a developer task. They are an SEO, content, analytics, user experience, and business continuity task. The team must know which old URLs matter, where each should go, which redirects are permanent or temporary, how to test them, and how to monitor the result after launch.

This guide explains how to plan, implement, test, and monitor website redirects for SEO during migrations and redesigns. It covers redirect types, URL mapping, 301 and 308 redirects, temporary redirects, soft 404s, canonical signals, sitemaps, Search Console, e-commerce URLs, and postlaunch QA.

Use this with the Technical SEO Audit Guide, Canonical Tags Guide, XML Sitemaps Guide, and Indexing Problems Guide. For e-commerce migrations, pair it with the E-Commerce Migration Testing Checklist.

Key Takeaways

• Use permanent redirects for permanent URL moves and temporary redirects for temporary changes.
• Google treats permanent redirects such as 301 and 308 as signals that the redirect target should become canonical.
• Server-side redirects are preferred when technically possible.
• Build a URL mapping before launch; do not improvise redirects after traffic drops.
• Redirect each old URL to the most relevant new URL, not automatically to the homepage.
• Avoid redirect chains and loops; redirect directly to the final destination.
• Keep migration redirects for as long as possible, generally at least one year.
• Update internal links, canonicals, hreflang, structured data, sitemaps, ads, email links, and profile links to the new URLs.
• Test redirects in bulk before launch and monitor old and new URLs after launch.
• Expect temporary search fluctuation during significant site moves while Google recrawls and reprocesses URLs.

Table of Contents

1. What Redirects Do

2. Redirect Types and SEO Meaning

3. When Redirects Are Needed

4. Build a URL Inventory

5. Create the Redirect Map

6. Choose the Redirect Strategy

7. Redirects, Canonicals and Sitemaps

8. Testing Redirects Before Launch

9. Launch-Day Redirect Checklist

10. Postlaunch Monitoring

11. E-Commerce Redirect Rules

12. Common Redirect Mistakes

13. Fixing Redirect Problems

14. Redirect QA Matrix

15. 100-Point Redirect Readiness Score

16. Frequently Asked Questions

What Redirects Do

A redirect sends a request for one URL to another URL. For users, it prevents dead ends. For search engines, it communicates that content moved, changed, merged, disappeared, or should be accessed elsewhere.

Redirects are useful when:

• a page URL changes
• a domain changes
• HTTP moves to HTTPS
• www and non-www are consolidated
• a page is merged into another page
• an old product has a close replacement
• an old campaign has a durable destination
• duplicate URLs should resolve to one preferred URL
• a temporary page needs to send users somewhere else

Redirects should preserve intent. If a user wanted a product, service, article, category, or document, the destination should satisfy that same purpose as closely as possible.

Redirects are part of canonicalization

Google's canonical guidance treats redirects as a strong canonicalization signal. That means a permanent redirect from an old URL to a new URL strongly suggests that the new URL should represent the content in search.

This is why redirect quality matters. If old important URLs redirect to irrelevant destinations, the site sends poor signals and creates poor user experience.

Redirect Types and SEO Meaning

Redirect type should match intent.

Permanent redirects

Use permanent redirects when the old URL should be replaced by the new URL.

Common permanent redirects:

Google's redirect documentation says permanent redirects tell Google Search to show the new redirect target in search results. Google also says 301 and other permanent redirects do not cause PageRank loss.

Temporary redirects

Use temporary redirects when the old URL should remain the canonical search result and the destination is only temporary.

Common temporary redirects:

Google says temporary redirects send users to another page temporarily while the original source page remains the expected search-result URL.

Client-side redirects

JavaScript redirects and meta refresh redirects exist, but server-side redirects are preferred when possible. Use client-side redirects only when server-side options are not available.

When Redirects Are Needed

Redirects are needed when an old URL has a relevant new destination.

Migration and redesign cases

Use redirects for:

• old URLs to new URLs
• HTTP to HTTPS
• old domain to new domain
• old CMS paths to new paths
• changed slugs
• changed category folders
• merged pages
• renamed services
• old file downloads
• important images and videos
• paid campaign landing pages
• backlinks and profile links

Content consolidation

When multiple pages become one stronger page, redirect retired pages to the consolidated URL. This helps users, preserves external links where possible, and sends a strong signal about the preferred destination.

When not to redirect

Do not redirect:

• unrelated deleted pages to the homepage
• every missing product to the main shop page
• old spammy URLs to important pages
• expired internal search pages to a category without relevance
• broken bot-generated URLs to the homepage

If no relevant replacement exists, a real 404 or 410 may be better.

Build a URL Inventory

A redirect map is only as good as the old URL inventory.

Sources for old URLs

Collect:

• current XML sitemaps
• CMS exports
• crawl exports
• server logs
• analytics landing pages
• Search Console pages
• Search Console links report
• paid ads landing pages
• email campaign links
• social profile links
• backlinks from SEO tools where available
• product feed URLs
• PDFs, images, videos, and downloads
• old redirect files
• staging and legacy URL lists

Google's site move guidance recommends starting with important URLs from sitemaps, analytics, server logs, CMS exports, and Search Console link data, and including embedded resources such as images, videos, JavaScript, CSS, and PDFs where they matter.

Prioritize URLs

Mark:

• high organic traffic
• high revenue or lead value
• backlinks
• paid campaign usage
• email/social usage
• internal navigation
• legal/policy importance
• product feed importance
• current indexation

Not every old URL deserves equal attention, but important old URLs must not be guessed.

Create the Redirect Map

A redirect map pairs old URLs with new destinations.

Redirect map fields

Map by intent

Good redirects:

• old product to same product new URL
• discontinued product to close replacement
• old service page to same service page
• old article to updated article
• old category to equivalent category
• merged article to consolidated guide

Weak redirects:

• old product to homepage
• old article to unrelated service page
• old category to all-products page when a closer category exists
• every 404 to homepage

Google warns that redirecting many old URLs to one irrelevant destination, such as the homepage, can confuse users and may be treated as a soft 404.

Choose the Redirect Strategy

Implementation depends on platform and scale.

Common implementation layers

• web server config
• CDN/edge rules
• CMS redirects
• framework routing
• platform redirect manager
• application middleware
• database lookup
• static host config

Use the most reliable layer available. For large sites, centralize redirects so they can be exported, reviewed, and tested.

Pattern rules vs one-to-one rules

Use pattern redirects when structure maps cleanly:

`text

/old-blog/:slug -> /blog/:slug

`

Use one-to-one redirects when URLs change unpredictably:

`text

/blue-running-shoe.html -> /products/blue-trail-runner

`

Pattern rules are efficient but dangerous if they catch URLs that should go elsewhere.

Change one major thing at a time

Google's site move guidance recommends changing major site elements one at a time where possible, such as moving domain first, then changing layout later. Combining domain move, CMS change, redesign, content rewrite, and URL restructure creates more risk and makes diagnosis harder.

Redirects, Canonicals and Sitemaps

Redirects should agree with other SEO signals.

New site checks

After redirects are active:

• new URLs self-canonicalize
• canonicals use new URLs
• hreflang uses new URLs
• internal links use new URLs
• sitemap includes new canonical URLs
• old redirected URLs are removed from the new sitemap
• structured data references new canonical URLs
• noindex used during development is removed where appropriate

Google's migration guidance says to check canonical annotations and robots meta rules after redirects are active and to submit the new sitemap after launch.

Redirect vs canonical

Use redirects when an old URL should not remain accessible.

Use canonical when duplicate URLs must remain accessible, such as user filters or duplicate product paths that cannot be redirected.

See the Canonical Tags Guide for the full decision framework.

Testing Redirects Before Launch

Testing is where migrations are saved.

Bulk redirect tests

Test:

• source URL
• final destination URL
• status code
• number of hops
• final status
• final canonical
• destination indexability
• mobile response
• query-parameter behavior
• HTTPS behavior
• www/non-www behavior
• trailing slash behavior

Acceptance criteria

For important permanent redirects:

• old URL returns 301 or 308
• destination is the most relevant URL
• final destination returns 200
• no loop
• chain kept short
• destination canonical points to itself
• destination is not noindexed
• destination appears in new sitemap where appropriate
• internal links point directly to destination

Google says Googlebot can follow up to 10 redirect hops but recommends redirecting directly to the final destination; if unavoidable, keep chains low, ideally no more than 3 and fewer than 5.

Launch-Day Redirect Checklist

Before launch:

• redirect map approved
• critical URLs tested
• pattern rules tested
• old sitemap exported
• new sitemap ready
• Search Console properties verified
• analytics annotations or launch notes prepared
• paid campaigns checked
• email links checked
• profile links listed
• noindex/robots development blocks reviewed
• rollback plan ready

At launch:

• turn on redirects
• test homepage variants
• test top old URLs
• test top product/category/service URLs
• check old HTTP and HTTPS
• check www and non-www
• check old sitemap URLs
• check final canonical tags
• submit new sitemap
• monitor server errors
• monitor Search Console over time

For full launch QA, use the E-Commerce Migration Testing Checklist.

Postlaunch Monitoring

After launch, monitor both old and new URLs.

First 24 hours

Check:

• critical old URLs redirect correctly
• no 5xx spike
• no redirect loops
• no mass homepage redirects
• checkout and lead forms work
• analytics still records landing pages and conversions
• old campaign links resolve
• sitemap is accessible
• Search Console can fetch pages

First 7 days

Review:

• 404 logs
• redirect hits
• top old URLs
• top new landing pages
• Search Console indexing
• sitemap processing
• organic clicks and impressions
• paid landing pages
• backlinks worth updating
• internal links still pointing to old URLs

First 30 to 90 days

Monitor:

• search performance trend
• Google-selected canonicals
• old URL impressions
• new URL impressions
• crawl errors
• soft 404s
• redirect chains
• indexed URL count
• conversions by landing page

Google says significant site moves can cause temporary ranking fluctuation while the site is recrawled and reindexed. Use evidence rather than panic, but respond quickly to technical failures.

E-Commerce Redirect Rules

E-commerce migrations have special redirect patterns.

Products

Redirect:

• old product to same product new URL
• discontinued product to close replacement if available
• variant URL to canonical product if variant is not separately indexable

Use 404/410 when:

• product is gone
• no replacement exists
• page has no meaningful demand, backlinks, or support value

Categories

Redirect:

• old category to equivalent new category
• merged category to parent or consolidated category if relevant
• seasonal category to evergreen category only when intent matches

Avoid:

• all deleted categories to shop homepage
• filter URLs to unrelated category

Filters and parameters

Decide whether to:

• redirect to base category
• canonicalize to base category
• allow indexable facet landing page
• noindex
• block crawl traps carefully

The decision depends on user value, search demand, product depth, and technical scale.

Common Redirect Mistakes

Avoid:

• no redirect map
• homepage dumping
• long chains
• loops
• 302 used for permanent moves
• 301 used for temporary tests
• old URLs left in sitemap
• new pages canonicalize to old URLs
• development noindex left live
• redirecting to redirected URLs
• ignoring PDFs and images with backlinks
• failing to update internal links
• forgetting ads, email, and profile links
• launching without bulk tests
• deleting redirects too soon
• combining migration, redesign, content rewrite, and analytics changes without controls

Redirect mistakes often hide until traffic drops.

Fixing Redirect Problems

Common fixes

Retest

After fixing:

• crawl old URL list
• inspect priority URLs
• verify final destinations
• check Search Console
• check analytics landing pages
• monitor logs

Redirect QA Matrix

Use this test matrix.

100-Point Redirect Readiness Score

Use this score before migration launch.

Scoring guidance:

• 90-100: Redirect plan is ready for launch.
• 75-89: Good plan with a few risks to fix before high-traffic launch.
• 60-74: Launch is risky unless gaps are accepted and monitored closely.
• 40-59: Redirect plan is incomplete.
• Below 40: Do not launch the migration until mapping and testing are rebuilt.

Frequently Asked Questions

What redirect is best for SEO?

For permanent URL moves, use a permanent server-side redirect such as 301 or 308 when possible. For temporary changes, use a temporary redirect such as 302 or 307.

Do 301 redirects lose PageRank?

Google says 301 and other permanent redirects do not cause PageRank loss. Redirect quality still matters because the destination should be relevant and technically accessible.

Should old URLs redirect to the homepage?

Only if the homepage is genuinely the most relevant replacement, which is uncommon for product, service, category, or article URLs. Irrelevant mass homepage redirects can confuse users and may be treated like soft 404s.

How long should redirects stay live after migration?

Google recommends keeping redirects for as long as possible, generally at least one year. From a user perspective, keeping important redirects indefinitely is often helpful.

Are 302 redirects bad for SEO?

No, they are useful for temporary moves. The issue is using a temporary redirect when the move is permanent and you want the new URL to replace the old one in search results.

How many redirect hops are okay?

Googlebot can follow multiple hops, but Google recommends redirecting directly to the final destination. If chains cannot be avoided, keep them low, ideally no more than 3 and fewer than 5.

Should redirected URLs remain in the sitemap?

No. The new sitemap should list canonical destination URLs, not old redirected URLs. Redirects handle old URLs; sitemaps support discovery of preferred new URLs.

Do I need the Change of Address tool?

Use the Change of Address tool for domain moves when appropriate and when old/new properties are verified. Do not use it for HTTP to HTTPS moves.

Can redirects fix duplicate content?

Yes, when duplicate URLs do not need to remain accessible. If duplicates need to remain accessible, canonical tags may be better. Use the Canonical Tags Guide for the decision.

What should a redirect project deliver?

It should deliver an old URL inventory, approved redirect map, implementation rules, prelaunch test evidence, launch checklist, postlaunch monitoring plan, and issue log. For support, review the technical SEO audit service.