Website Redesign Roadmap Template: Phases, Workstreams, Example

6 min read ยท 2026-10-08

A website redesign roadmap template is a phased plan that takes a site from audit to launch and beyond: measure what the current site does, define goals and audiences, rebuild the information architecture and content, design and develop, migrate without losing search traffic, then optimize. The six-month template below fits a marketing site or content-heavy site of moderate size moving to a new CMS or design system.

It is meant for marketing leads, web managers, product designers, and agencies. You get the phases, the workstreams that need their own owners, an example from a professional services firm, and a routine for keeping the roadmap current through launch and the first optimization cycle.

The roadmap at a glance

Goal: Launch a redesigned website within six months that improves conversions and preserves organic search traffic. Duration: 6 months

  1. Audit and Goals (Weeks 1-3)

    Understand how the current site performs and define what success means.

    • Pull baseline analytics for traffic, conversions, and top landing pages from GA4.
    • Export ranking pages and backlinks from Search Console and an SEO crawler.
    • Run a content inventory classifying pages to keep, merge, rewrite, or remove.
    • Interview sales, support, and a few customers about what visitors need.
    • Set measurable redesign goals such as demo requests or lead quality.

    Milestone: A redesign brief with baseline metrics and goals is approved by stakeholders.

  2. Structure and Content (Weeks 4-8)

    Design the information architecture and plan content before visual design.

    • Draft a sitemap and navigation based on audience tasks, not internal org charts.
    • Validate navigation labels with a card sort or tree test.
    • Write a messaging framework covering value proposition, proof, and calls to action.
    • Assign content owners and deadlines for every page in the new sitemap.
    • Build wireframes for key templates such as home, service, and article pages.

    Milestone: Sitemap, wireframes, and a content plan with owners are signed off.

  3. Visual Design (Weeks 9-12)

    Create a design system and high-fidelity layouts for every template.

    • Define a component library in Figma covering typography, color, and UI patterns.
    • Design high-fidelity templates using real draft content, not placeholder text.
    • Check designs against WCAG 2.2 AA for contrast, focus states, and structure.
    • Run usability tests on clickable prototypes with representative visitors.
    • Hand off annotated designs with responsive behavior to developers.

    Milestone: All templates are approved in a design system ready for development.

  4. Build and Migrate (Weeks 13-20)

    Develop the site, load content, and prepare SEO-safe migration.

    • Set up the CMS, environments, and component library in code.
    • Build templates and integrate forms, CRM, analytics, and consent management.
    • Migrate and enter final content, including metadata and image alt text.
    • Create a full 301 redirect map from old URLs to their new equivalents.
    • Test performance with Lighthouse and Core Web Vitals on staging.

    Milestone: Staging site passes QA, accessibility, performance, and redirect checks.

  5. Launch and Optimize (Weeks 21-26)

    Launch safely, monitor impact, and start continuous improvement.

    • Launch during a low-traffic window with a rollback plan ready.
    • Submit the new XML sitemap and monitor crawl errors in Search Console.
    • Compare traffic, rankings, and conversions to baseline weekly.
    • Fix broken links, redirect gaps, and form issues found after launch.
    • Plan A/B tests on key pages based on early behavior data.

    Milestone: Organic traffic is stable versus baseline and the conversion goal is being tracked weekly.

Who This Template Is For

This template fits B2B, nonprofit, and services websites where the site is a key source of leads or credibility, typically from a few dozen to a few thousand pages. It also works when a redesign coincides with a CMS migration, such as moving from an old WordPress theme to a headless CMS or Webflow.

Large ecommerce platforms and web applications need a different roadmap focused on product features and checkout flows. If you only need a visual refresh with no structural or platform change, compress the plan to the design and build phases, but still keep the redirect and analytics steps.

Workstreams and Owners

Redesigns slip most often on content, not code. Developers finish templates and then wait weeks for copy. Put content on its own swimlane with page-level owners and due dates, and start it as soon as the sitemap is approved.

SEO also deserves its own lane rather than a launch-week checklist. The redirect map, metadata, and internal linking decisions run through the whole project, and they are the main protection against losing traffic you spent years earning.

  • Strategy and Analytics: goals, baselines, measurement plan.
  • Content: messaging, copywriting, page owners, approvals.
  • UX and Design: IA, wireframes, design system, testing.
  • Development: CMS, templates, integrations, performance.
  • SEO and Migration: URL mapping, redirects, metadata, monitoring.

Example: A Professional Services Firm

Picture a consulting firm with a site that grew organically for years: hundreds of pages, overlapping service descriptions, and navigation organized by internal departments. The audit shows that a small number of articles drive most organic traffic, while many service pages get almost no visits.

The new sitemap organizes services by client problem, merges overlapping pages, and keeps every high-traffic article at its existing URL. Content owners in each practice rewrite their service pages against a shared messaging framework. During build, the team maps every retired URL to its closest replacement. After launch, weekly checks catch a handful of missed redirects within days, and organic traffic holds steady while consultation requests rise.

Protecting SEO During a Redesign

Search traffic losses after redesigns usually come from changed URLs without redirects, removed content that ranked, or new templates that strip headings and metadata. Start from a crawl of the old site and a list of pages with organic traffic or backlinks. Those pages either keep their URL or get a one-to-one 301 redirect to the most relevant new page.

Before launch, crawl staging to verify titles, meta descriptions, canonical tags, and heading structure. Block staging from indexing, then remember to remove that block at launch, a surprisingly common mistake. Monitor Search Console coverage and performance daily for the first two weeks.

Keeping the Roadmap Up to Date

Hold a weekly project review with leads from each workstream, and update the roadmap with content completion percentages alongside design and development status. Content readiness is the best early warning of a launch delay.

Set a firm content freeze date a few weeks before launch, and record any late changes as post-launch backlog. After launch, turn the roadmap into a rolling optimization plan reviewed monthly, with tests and improvements prioritized by impact on the conversion goals you set in the audit phase.

Common mistakes to avoid

  • Designing visuals before content is planned produces layouts that break with real copy; finalize the sitemap and messaging first.
  • Launching without a redirect map loses rankings and backlinks; map every indexed URL to a relevant new page.
  • Organizing navigation by internal departments confuses visitors; base structure on audience tasks and test it with users.
  • Letting content approvals drift delays launch; assign page owners with deadlines and track completion weekly.
  • Forgetting to remove the staging noindex setting hides the new site from search; include it on the launch checklist.
  • Skipping baseline metrics makes success impossible to prove; capture analytics and rankings before changing anything.

Frequently asked questions

What are the steps of a website redesign?

Audit the current site and set goals, define audiences and information architecture, plan and write content, design templates and a design system, develop and migrate, run QA and SEO checks, launch, then monitor and optimize. This template groups those steps into five phases over six months with a milestone at the end of each.

How long does a website redesign take?

Small sites can be redesigned in a couple of months, while larger content-heavy sites with CMS migrations commonly take four to six months or more. Content creation and stakeholder approvals are usually the longest parts. Starting content work early, right after the sitemap is approved, is the most effective way to shorten the timeline.

How do I redesign a website without losing SEO?

Crawl the old site, identify pages with traffic or backlinks, and keep their URLs or redirect each one with a 301 to the closest new page. Preserve titles, headings, and content depth on ranking pages, verify metadata on staging, submit the new sitemap at launch, and monitor Search Console closely for several weeks.

Who should be involved in a website redesign?

A project owner from marketing, a UX or web designer, developers, a content lead with page owners across the business, an SEO specialist, and analytics support. Sales and customer support should contribute during research since they hear visitor questions daily. Keep the approval group small to avoid design by committee.

Should content or design come first in a redesign?

Content and structure should come first. Knowing what each page must say lets designers create layouts that fit real messages, rather than forcing copy into placeholder boxes. Wireframes can develop alongside content planning, but high-fidelity design works best once draft content exists for the key templates.

Generate this roadmap with AI