A safe redesign begins with an inventory and measurable goals, not a homepage mockup. Control content, URLs, analytics, integrations and acceptance criteria through discovery, design, build, migration, QA and launch.
Key takeaways
- Capture the baseline before changing anything.
- Approve templates and content responsibilities separately.
- Build the redirect map before launch week.
- Treat launch as a controlled migration with rollback and monitoring.
Who this is for: Marketing and product teams managing a redesign with internal stakeholders, an agency or both.
Phase 1: establish the baseline
Without a baseline, a redesign can launch successfully while business performance quietly declines. Export the evidence before tracking, content or URLs change.
- Analytics and conversion events
- Search Console queries and landing pages
- Crawl and indexable URL inventory
- Top linked and highest-converting pages
- Core Web Vitals and accessibility samples
- Forms, CRM and integration map
- User complaints and support themes
- Content owners and approval responsibilities
Phase 2: define strategy and information architecture
Translate goals into journeys, templates and measurable acceptance criteria. A sitemap is useful only when each page has an audience, job and next step.
- 1Define primary audiences and decisions.
- 2Map current content to keep, improve, consolidate or retire.
- 3Create the target sitemap and template inventory.
- 4Define navigation, search and cross-linking behavior.
- 5Assign one conversion objective and measurement plan to each key template.
Phase 3: design and content
Design with realistic content, edge cases and responsive states. Placeholder copy hides layout risk and delays meaningful feedback.
| Review | Must include | Approval evidence |
|---|---|---|
| UX | Flows, hierarchy, errors and empty states | Clickable prototype |
| UI | Components, responsive states and accessibility | Design-system inventory |
| Content | Headings, proof, actions and metadata | Approved content sheet/CMS entries |
| Analytics | Events and consent behavior | Measurement specification |
Phase 4: build, migrate and test
Test templates with representative real content and devices. Migration must be rehearsed rather than improvised at launch.
- Semantic headings and keyboard behavior
- Responsive images and layout stability
- Forms, validation and notification delivery
- Structured data matching visible content
- Redirects, canonicals and XML sitemap
- Analytics and consent states
- Browser/device matrix
- Backup and rollback procedure
Launch and first 30 days
A redesign is not complete when DNS changes. Monitor crawl errors, redirects, conversions, performance, forms and stakeholder feedback against the baseline.
How to use this guide with your team
A redesign changes a live business asset, so treat it as a controlled improvement program rather than a visual replacement exercise. Preserve the evidence that already works while addressing the problems that can be demonstrated.
Marketing, content, design and engineering should review the same baseline. If each team uses a different definition of success, a visually successful launch can still create commercial or search losses.
After launch, compare results with the original baseline and document what changed. This creates a better foundation for the next iteration instead of beginning another redesign from opinion.
Practical next steps
Use the following actions as a short working session. Record decisions, owners and unresolved questions so the article becomes an implementation aid rather than passive reading.
- 1Capture the current performance and content baseline.
- 2Separate cosmetic, journey and platform problems.
- 3Map every high-value URL and integration.
- 4Define launch and rollback ownership.
- 5Measure the first 30 days against the baseline.
Frequently asked questions
How early should SEO migration planning begin?
During discovery, before the final sitemap and templates are approved. Redirects and content consolidation depend on those decisions.
Should every old page be migrated?
No. Keep, improve, consolidate or retire pages based on value and intent, but map every indexable URL to a deliberate outcome.
Sources and further reading
Last reviewed: September 1, 2026
