SEO Migration Playbook: Redirects, QA, and Post-Launch Monitoring

A redesign can improve clarity, usability, and brand presentation, but changes to URLs, templates, navigation, and crawl signals can also disrupt organic visibility. A disciplined SEO migration playbook makes a website redesign safer by treating migration risk as part of the build, not as a marketing afterthought.

This guide is written for teams making real decisions: founders approving budgets, marketing leaders protecting demand, and product and web teams executing the build. If your redesign includes URL changes, CMS changes, navigation changes, or template changes, you need a plan that reduces avoidable SEO risk while UX improves. Brand Vision brings branding, web, UX, and search considerations together so the redesign and migration are planned as connected workstreams.

What Actually Goes Wrong in a Website Redesign

Rankings Drop for Predictable Reasons

Ranking and indexing problems during a redesign often trace back to changes in URLs, internal links, crawl controls, canonicals, or content that were not carried into the new build cleanly. Google recommends careful planning for site moves with URL changes, including URL mapping, permanent redirects, updated internal links, and monitoring during the transition (Google Search Central guidance on site moves).

SEO migration problems can affect more than ranking reports when high-intent organic landing pages lose visibility or stop converting as expected. The safer approach is to scope migration work alongside the redesign so redirects, content, UX, analytics, and technical QA are ready before launch.

Redesign Risks That Look “Design Only” but Are SEO Critical

Some redesign decisions seem purely visual, but they are also tied to SEO services, crawlability, and index signals.

• Navigation changes that orphan pages, even when the pages still exist
• Template rebuilds that change headings, internal links, or canonical logic
• New filters and parameters that create duplicate versions of the same content
• Performance regressions that make the site slower on mobile, especially on key templates

A clean redesign is not only aesthetic. It is measurable. It keeps the same core value pages accessible, fast, and correctly mapped.

At a Glance: The SEO Migration Checklist for Decision Makers

If you only read one section, read this. This is the SEO migration playbook in its shortest form, designed to reduce avoidable search risk during a website redesign.

1. Lock a baseline: top landing pages, top queries, conversions, backlinks, crawl stats
2. Inventory every indexable URL and choose what stays, moves, merges, or retires
3. Build a URL mapping sheet and implement relevant server-side permanent redirects, such as 301 or 308, where URLs change
4. Recreate internal linking and navigation pathways for high-value pages
5. Validate technical SEO on staging: robots, noindex, canonicals, sitemaps, status codes
6. Launch with monitoring: Search Console, analytics, logs, and crawl tests
7. Fix issues fast: redirect gaps, 404s, soft 404s, canonical errors, performance drops
8. Use the first 30 days as an operating checkpoint for indexing, traffic, content, and internal-link issues

The same sequence can be adapted to a service site, a multi-location business, or a content-heavy publication. The scale changes, but the need for inventory, mapping, QA, and monitoring remains.

Phase 1: Baseline and Inventory (Before You Touch Design)

Pull the Pages That Pay the Bills

An effective SEO migration starts with business reality. Identify the pages that drive qualified demand, not just traffic. For service businesses, that often includes core service pages, location pages, and high-intent educational pages. A pre-launch SEO audit can help separate pages that should be preserved, improved, consolidated, redirected, or investigated further.

Start with these exports:

• Top organic landing pages and their conversions
• Top queries tied to revenue or leads
• Pages with strong backlink profiles
• Pages ranking in the top 3 to 10 positions

If you have a fragmented analytics setup, fix that before you migrate. A redesign is not the moment to lose your measurement. A marketing consultation and audit can help establish the baseline, ownership, and reporting decisions before the new site changes what you are measuring.

Capture Benchmarks You Can Compare After Launch

Benchmarks reduce guesswork later. Google notes that significant site moves can produce temporary ranking fluctuations while URLs are recrawled and reindexed. The practical question is whether the movement fits the expected transition or points to a specific technical, content, or measurement issue.

Capture these benchmarks before the build:

• A full crawl export of indexable URLs and status codes
• Current XML sitemap URLs and last modified patterns
• Core Web Vitals and page speed on key templates (PageSpeed Insights)
• Search Console coverage and performance reports (Search Console Help)

This is where technical SEO becomes practical. You are creating a before-and-after dataset.

Phase 2: URL Mapping and Permanent Redirects

How to Build a URL Mapping Sheet That Holds Up

URL mapping is a core migration control. A useful mapping sheet goes beyond “old URL to new URL” by documenting intent, content decisions, and what should happen to each page when the structure changes.

A mapping sheet should include:

• Old URL
• New URL (or retirement destination)
• Page type and intent (service, category, guide, location)
• Primary keyword target and supporting topics
• Notes on content changes and what must be preserved
• Redirect rule and implementation owner

For complex migrations, map the indexable URLs that need an explicit decision and use patterns only where the relationship is genuinely one-to-one. Do not redirect unrelated pages to the homepage. Google warns that irrelevant mass redirects can confuse users and may be treated as soft 404s. For important service pages, a website copywriting framework can also record the promise, proof, and CTA that should survive the template change.

If the information architecture is changing, the mapping sheet should become a shared reference across design, development, content, analytics, and SEO so page decisions do not diverge between teams.

Permanent Redirect Rules for URL Changes

When URLs change permanently, Google recommends server-side permanent redirects from the old URLs to their relevant new destinations, using HTTP permanent redirects such as 301 or 308 when possible (Google Search Central guidance on site moves).

Use these rules:

• Prefer one to one redirects, old page to the closest new equivalent
• Use server-side permanent redirects for permanent moves, such as 301 or 308, when technically possible
• Avoid redirect chains and loops
• Keep the destination relevant to the original search intent
• Update internal links to point directly to the new URL, not the redirect

If your redesign includes a domain change, plan Search Console updates. Google provides a Change of Address tool for domain moves, and it has specific limitations, including when not to use it (Change of Address tool documentation).

Redirect Testing Before Launch

Redirects should be tested as a system, not spot checked. If you miss even a small set of high value URLs, rankings can drop in exactly the areas that matter most.

Pre launch redirect tests should include:

• Automated checks for 200, 301, 404, 500 across mapped URLs
• Identification of redirect chains and non-canonical destinations
• Verification that old URLs resolve in a single hop
• Manual tests of the highest-value URLs from your baseline list

This is one of the most repeatable parts of an SEO migration playbook. It is also where disciplined teams separate themselves from rushed launches.

Phase 3: Information Architecture, Internal Links, and On-Page Signals

Keep Intent Stable While You Improve UX

A redesign often changes navigation and page layout. That is fine, as long as the intent remains stable. A high-performing service page should still clearly communicate the service, who it is for, what the user should do next, and how the business is credible.

UI/UX design and information architecture should be reviewed alongside migration requirements. The same structure that helps people scan and decide can also make page relationships easier for crawlers to interpret. A focused UX audit can identify post-click friction before the new templates are locked. When you rebuild templates, keep the core elements consistent:

• One clear H1 that matches the page topic
• Supporting sections that maintain topical depth
• Internal links that reflect the user journey, not just the menu

Internal links help users navigate and help search engines understand relationships between pages. During an SEO migration, update them to point directly to the new URLs and rebuild important contextual paths deliberately. Web design services should account for structure, content, performance, and conversion paths together.

Canonicals, Titles, H1s, and Structured Data

On-page signals often break quietly. A redesign can introduce template logic that changes titles, duplicates H1s, misconfigures canonicals, or strips structured data.

During technical SEO QA, confirm:

• Page titles remain unique and aligned to intent
• H1s are singular and descriptive
• Canonicals point to the correct indexable version
• Structured data is retained where relevant, especially for breadcrumbs and organization markup

Retain and validate structured data that is relevant to the page and current Google Search features. Breadcrumb and Organization markup can still help Google understand page hierarchy and organization details when implemented according to current guidelines.

Phase 4: Technical SEO QA on Staging

Crawl and Index Controls

Staging environments should be testable by the project team while remaining out of public search indexes. The launch risk is carrying development-only blocks or canonical settings into production, or exposing staging URLs unintentionally.

Before launch, validate:

• robots.txt is correct for production
• Noindex tags are not present on templates that should rank
• Canonical tags do not point to staging
• sitemap references are accurate

A sitewide noindex or production robots block can remove important templates from search visibility. This is why an SEO migration needs a launch checklist and a final technical gate rather than a casual “looks good.”

Performance and Core Web Vitals Checks

Redesigns can slow sites down. New fonts, heavy scripts, and large images can degrade performance, which can affect usability and conversion paths as well as page experience. Performance belongs in the launch decision, not only the post-launch backlog.

Run performance checks on:

• Homepage and core service templates
• Top organic landing pages
• Forms and conversion paths

Use tools that provide consistent diagnostics and a shared language across teams (PageSpeed Insights). If performance drops, solve it before launch. Technical SEO and user experience are not separate concerns.

Analytics and Tagging Validation

A redesign is a common moment for analytics loss. Events stop firing, forms lose attribution, and conversions appear to drop when the real issue is tracking.

Validate before launch:

• GA4 is installed and firing on every template
• Key events and conversions are still captured
• Forms are tracked, including thank you states
• Paid landing pages and attribution paths still work

Tracking should be treated as part of migration stability. Without reliable analytics and conversion events, a traffic or lead change can be difficult to separate from a measurement failure.

Launch Day Runbook: The First 72 Hours

Flip the Switch Without Losing Crawlability

Launch day should be boring. That is the goal. A calm launch comes from a controlled runbook.

On launch day:

• Deploy redirects and verify the highest value URL set first
• Remove staging blocks and confirm indexability
• Confirm canonical tags, status codes, and robots settings
• Publish the XML sitemap and submit it in Search Console

If your redesign includes a host or infrastructure move without URL changes, Google has separate guidance that focuses on monitoring and infrastructure readiness (Google guidance on moves without URL changes).

Sitemaps, Monitoring, and Early Fixes

For this playbook, treat the first 72 hours as an intensive detection window, not as a promise that search systems will settle in three days. Google notes that site moves can take weeks or longer depending on site size and crawl conditions.

Monitor:

• Crawl errors and coverage changes in Search Console
• Spike in 404s, soft 404s, and redirect anomalies
• Traffic to top landing pages compared to baseline
• Conversion rates and form submissions

Fixes in this window should be simple and direct:

• Fill redirect gaps
• Correct canonical mistakes
• Restore missing internal links
• Patch performance regressions

The First 30 Days After Launch

What to Watch in Search Console

Search Console is a primary monitoring tool during an SEO migration. Use it alongside analytics, crawl data, and server or platform logs to confirm how Google is discovering and indexing the new structure.

Track:

• Coverage changes and indexing status
• Performance trends for baseline queries and pages
• Sitemap processing and discovered URL counts
• Manual actions and security warnings

If you changed domains, handle the administrative steps carefully. Google’s documentation covers when to use and when not to use the Change of Address tool (Change of Address tool documentation).

When to Expect Volatility and When to Escalate

Google notes that temporary ranking fluctuation can occur during significant site moves. The first 30 days are therefore an operational checkpoint, not a guaranteed stabilization deadline. Escalate when the pattern suggests a systemic issue rather than normal per-URL processing.

Escalate if you see:

• Large ranking losses concentrated on a page type, like services or locations
• Indexing drops across the site, not just a few pages
• Redirect failures on high value URLs
• Canonicalization problems that point many pages to the wrong destination

Post-launch work can include correcting template signals, restoring lost contextual links, and rebuilding topical depth where the redesign changed content materially. A documented SEO content strategy helps separate intentional content improvements from reactive edits made only because rankings moved.

When to Bring in a Migration Team

If your site has many URLs, multiple languages, complex templates, or meaningful organic demand, the migration has more dependencies to coordinate. The business risk comes from mistakes in content, redirects, crawl controls, analytics, or launch sequencing, not from the word “migration” itself.

A migration team is typically warranted when:

• The redesign includes a CMS change or a platform shift
• You are changing URL structure or consolidating sections
• Organic traffic drives a meaningful share of revenue
• You need design, UX, and technical SEO to move in lockstep

Brand Vision’s web, UX, branding, and SEO services can be coordinated around the same redesign plan rather than handed off as isolated tasks, which is why the work ties back to Brand Vision as a full-service team. For a Canadian organization coordinating several markets or locations, Canadian digital marketing support can provide regional continuity. If the redesign supports a complex buying committee, align the migration with the wider B2B marketing journey and a clear brand strategy so search intent, proof, and conversion paths move together.

Protect the Redesign and the Pipeline

A redesign should improve clarity, speed, and conversion without creating avoidable search loss. Reducing migration risk means treating SEO as a first-class workstream with clear ownership, tested URL mapping, permanent redirects, and technical SEO QA before launch.

If you want a second set of eyes on a redesign plan or migration risk, review Brand Vision’s SEO services, request a marketing consultation, or start a conversation about the project scope.