Use a phased redesign plan that starts with discovery and SEO-preserving audits, then proceeds through design, development, and a staged launch. Every phase needs a measurable goal, a URL and redirect map, and Core Web Vitals targets set before design begins. We build these roadmaps with templates and a kickoff form, so you can start structuring your own project today.
TL;DR:
- Use at least 12 months of analytics to set three to five measurable KPIs tied to business outcomes before design begins.
- Map every old URL to its new destination before development, test all redirects on staging, and set a written rollback trigger before launch.
- Set Core Web Vitals limits at LCP 2.5 seconds, INP 200 milliseconds, and CLS 0.1, measured at the 75th percentile.
- A small or midsize business redesign typically takes 8 to 16 weeks, but content approvals and third party integrations can extend the schedule.
- Track rankings for the top 20 landing pages daily for two weeks, and allow two to four weeks of stable traffic before treating changes as trends.
Table of Contents
- What the Redesign Roadmap Covers
- How to Run Discovery and Set Measurable Goals
- SEO Audit and Migration Checklist
- Content Audit and Information Architecture
- Design, Accessibility, and User Experience Choices
- Development, Staging, and Quality Assurance
- Launch Day and the First 72 Hours
- Measuring Results and Prioritizing What to Fix Next
- Templates and Resources Worth Reusing
- What Actually Slows Down a Redesign
- Get Hands-On Help Planning Your Redesign
- FAQ
- Sources
What the Redesign Roadmap Covers
A redesign that protects traffic and revenue moves through seven phases, each ending with a decision gate rather than a vague handoff. Skipping a gate is usually what turns a 10 week project into a 20 week one.
- Discovery: audits, stakeholder interviews, and a documented list of goals and constraints.
- Planning and strategy: KPIs, site map, content inventory, and a locked scope document.
- Design: wireframes, a component library, and a clickable prototype signed off by stakeholders.
- Development: built pages on staging, content loaded, integrations connected and tested.
- Testing and QA: cross-browser, accessibility, performance, and redirect verification.
- Launch: redirects activated, monitoring in place, support team briefed.
- Optimize: 30, 90, and 365 day reviews tied back to the original KPIs.
The people who need to be in the room from day one include the business owner or marketing lead, whoever owns content production, a developer or technical lead, and anyone who manages paid campaigns or CRM integrations that touch the site. Leaving content owners out of early meetings is one of the most common reasons timelines slip, since written and approved copy is usually the slowest-moving dependency.
Timelines vary by scope, but a typical small to midsize business site runs 8 to 16 weeks from kickoff to launch, assuming content is ready on schedule and approvals happen within agreed windows. Third-party integrations, like a CRM, payment processor, or booking system, tend to add the most unpredictable delay because they depend on another vendor’s documentation and support responsiveness. Our guide to a six-step website design process walks through how we sequence these phases for client projects, which is a useful reference point even if you plan to run the project in-house.
How to Run Discovery and Set Measurable Goals
Discovery is where a redesign either gets grounded in data or drifts into opinion. The work here determines whether your new site actually performs better or just looks different.
- Pull analytics and behavioral baselines. Export at least 12 months of traffic, conversion rate, bounce rate, and top landing pages so you have a before picture to compare against after launch.
- Interview five to eight stakeholders and a handful of real users. Ask what tasks the current site makes hard, which pages they distrust, and what competitors do better.
- Draft 3 to 5 measurable KPIs tied to business outcomes. Examples: raise organic conversion rate from 1.8% to 2.5%, cut mobile bounce rate by 15%, or reduce average page load time to meet the Core Web Vitals “good” thresholds at the 75th percentile.
- Document technical dependencies. List every login system, payment gateway, CRM integration, and marketing pixel the new site must support, since these often dictate which platform or framework is viable.
Our preparatory checklist for redesign readiness covers the assets and decisions worth locking in before you brief a designer or developer.
Pro Tip: Write your KPIs as a single sentence with a number and a deadline, like “increase demo requests by 20% within 90 days of launch,” so nobody can argue later about whether the project succeeded.
SEO Audit and Migration Checklist
A redesign is the single most common cause of a sudden organic traffic drop, and almost always the cause is preventable. Treat the audit and migration plan as a control document that design and development both have to respect, not an afterthought bolted on before launch.
- Build a full content inventory listing every live URL, its traffic, its top keyword, and whether it stays, merges, or gets removed.
- Map every old URL to its new destination before development starts, not after.
- Write 301 redirect rules for every URL that changes, and set canonical tags for any near-duplicate pages.
- Test the full redirect map on staging using a crawler before launch day, not during it.
- Run prelaunch checks: confirm robots.txt isn’t blocking the new site, submit the new XML sitemap, verify structured data with a validator, and check hreflang tags if you serve multiple regions or languages.
- Reconfirm Google Search Console property verification and link the new sitemap the day you launch.
- After launch, monitor for spikes in 404 errors, track how many pages get reindexed, and watch ranking positions for your top 20 landing pages daily for the first two weeks.
- Set a rollback trigger in advance, such as a 20% drop in indexed pages or a ranking collapse on priority terms within 72 hours, so the decision to revert isn’t made in a panic.
Our own six-point prelaunch SEO migration checklist walks through these checks in more detail, and the team at Baby Love Growth publishes a useful breakdown of URL mapping timelines for larger migrations if your site runs into the thousands of pages. Getting this sequence wrong, mapping URLs after design instead of before, is the single most expensive mistake we see in redesign projects.
Content Audit and Information Architecture
Deciding what to keep, cut, or rewrite shapes both your SEO equity and how easily visitors complete the actions you want. Score every existing page against four criteria: traffic over the last year, conversion contribution, relevance to a keyword you still want to rank for, and how current the information is.
- Keep: high-traffic, high-relevance pages that just need a design refresh.
- Merge: several thin pages covering the same topic that split ranking signals and should become one stronger page.
- Rewrite: pages with decent traffic but outdated content, broken calls to action, or weak on-page structure.
- Remove: zero-traffic, zero-relevance pages that add maintenance cost without return, redirected to the closest relevant page.
Once the inventory is scored, build the sitemap around user intent rather than internal org chart logic. Visitors looking to buy should reach a conversion path in two clicks or fewer; visitors researching should have a clear path from a blog post to a relevant service page. Our SEO audit methodology covers how we score pages during a full audit, which is a reasonable template to adapt for an in-house review.
Metadata and template standards need to be locked before development, not left to whoever builds the last page. Set a title tag formula, a meta description length cap, heading hierarchy rules, and an image alt text standard, then enforce it across every template so the build doesn’t drift page by page.
Design, Accessibility, and User Experience Choices
Design deliverables should include wireframes for key templates, a component library (buttons, forms, cards, navigation), and a clickable prototype that stakeholders sign off on before any code gets written. Skipping the prototype stage and jumping straight to a visual comp is how teams end up redesigning a page twice.
- Wireframes for every unique template type, not just the homepage.
- A documented component library so development doesn’t reinvent patterns page by page.
- A clickable prototype tested with 5 to 8 real users before build starts.
- Accessibility notes attached directly to the design file, not handled as a separate pass later.
WCAG 2.2 adds success criteria around navigability, input modalities, and focus appearance that are worth building into your design file from the start rather than retrofitting after launch. Focus states need to be clearly visible for keyboard users, touch targets need enough spacing for input accuracy, and navigation patterns need to stay predictable across pages.
Core Web Vitals thresholds are set at LCP ≤2.5 seconds, INP ≤200 milliseconds, and CLS ≤0.1, measured at the 75th percentile of real visits. Design choices drive two of these directly: oversized hero images without defined dimensions cause layout shift, and web fonts loaded without a fallback strategy delay largest contentful paint. Reserve space for images and ads before they load, and test the prototype with a five-user hallway test focused on task completion rather than aesthetic feedback.
Development, Staging, and Quality Assurance
Developer handoff needs to be complete before a single line of code gets written against it, not negotiated mid-sprint. A clean handoff saves more time than almost any other single habit in this list.
- Confirm assets are final: specs, exported images, copy loaded into a CMS or content file, and accessibility notes attached to each component.
- Stand up a staging environment that mirrors production configuration, including CDN and caching rules, so performance testing on staging actually predicts launch-day behavior.
- Use feature flags for risky changes so a problematic feature can be switched off without a full rollback.
- Run lab performance tests (Lighthouse or PageSpeed Insights) on every key template, then layer in real-user monitoring once the site is live, since Web Vitals guidance recommends combining both rather than relying on lab data alone.
- Check Interaction to Next Paint specifically, since INP became a Core Web Vital and is commonly caused by long main-thread tasks or heavy client-side rendering that lab tests alone can miss.
QA should run a matrix covering cross-browser rendering, mobile and tablet devices, accessibility checks against WCAG 2.2 criteria, redirect verification against your mapping sheet, and a structured-data validator pass on every template type.
Pro Tip: Run your redirect map through a crawler on staging at least a week before launch, since catching a broken redirect chain then costs you an hour; catching it after launch can cost you a week of lost rankings.
Launch Day and the First 72 Hours
Launch day should feel procedural, not improvised. A written checklist, confirmed against each item the morning of launch, is what separates a calm launch from a chaotic one.
- Take a full backup of the current live site and database immediately before cutover.
- Activate the redirect map and spot-check a sample of 20 to 30 URLs across different page types.
- Submit the new sitemap and confirm the correct robots.txt is live, not a staging version that blocks indexing.
- Reverify Google Search Console ownership and watch the coverage report for crawl errors.
- Brief support and sales teams on what changed so they can answer customer questions about navigation or missing pages.
- Set rollback triggers in writing before launch: a spike in 404s, a checkout or form failure, or a major ranking drop within 72 hours.
- Monitor analytics, Search Console, and uptime hourly for the first day, then daily through the first 30 days.
Communication matters as much as the technical steps. Tell stakeholders launch is happening, confirm who owns the rollback decision if something breaks, and schedule a check-in 24 hours after launch rather than assuming silence means success.
Measuring Results and Prioritizing What to Fix Next
The first real test of a redesign comes 30, 90, and 365 days after launch, when you compare results against the baseline KPIs set during discovery. Organic traffic and conversion rate are the two numbers worth watching weekly at first, alongside Core Web Vitals scores pulled from field data rather than a single lab test.
- Compare organic traffic and conversion rate against your pre-redesign baseline at 30, 90, and 365 days.
- Score every proposed fix by impact versus effort, and tackle high-impact, low-effort items first.
- Use feature flags and A/B tests for any change stakeholders disagree on, rather than debating it in a meeting.
- Set a monthly review cadence for the first quarter, then shift to quarterly once metrics stabilize.
A drop in one metric alongside a gain in another is normal immediately after launch and doesn’t necessarily mean something is broken. Give the site at least two to four weeks of stable traffic before treating any single number as a trend.
Templates and Resources Worth Reusing
A redesign goes faster when you’re not building every document from scratch. We maintain a few resources built from running these projects repeatedly that are worth adapting for your own, whether you’re managing it in-house or bringing in outside help.
- Project Kick Off Form: captures goals, stakeholders, technical dependencies, and content ownership in one document before work starts.
- Six-step process guide: our documented design and development sequence that maps to the phases above.
- Prelaunch SEO checklist: the same migration checklist referenced earlier, formatted as a sign-off sheet.
- Design and SEO crossover tips: our practical list of design choices that affect both conversions and rankings.
Adapting these for an in-house project is straightforward: copy the structure, swap in your own stakeholders and KPIs, and keep the sequencing intact even if your timeline compresses or stretches. This article was written by Ruthwik; for direct support applying any of these templates to your own project, our team at Courimo is set up to help.
What Actually Slows Down a Redesign
The biggest bottleneck in almost every redesign we’ve been part of isn’t design or development. It’s how quickly a client reviews a deliverable and gives a clear yes or no. A two-week design phase can stretch to six weeks if feedback takes ten days to arrive each round, and that delay compounds across every remaining phase.
Favor a phased or template-driven rollout over a single big-bang launch wherever the scope allows it. Rolling out section by section, or testing a new template on a handful of pages before applying it site-wide, makes it far easier to isolate a problem to its source instead of debugging a fully replaced site under pressure.
Budget more time for content production and approval cycles than feels comfortable. Content is almost always the real critical path, and padding that estimate by a couple of weeks tends to save far more time than it costs.
— Ruthwik
Get Hands-On Help Planning Your Redesign
Planning a redesign in-house is entirely doable with the checklists above, but a second set of experienced eyes on your scope, timeline, and SEO migration plan tends to catch costly mistakes before they happen. A full redesign project covers everything from the technical audit through launch and ongoing optimization.
- Website development: design, build, hosting, and a maintenance plan for the finished site.
- Search engine optimization: audit, migration support, and post-launch ranking recovery if traffic dips.
- Migration support: URL mapping, redirect strategy, and prelaunch checks handled alongside your development team.
If you want a second opinion on your redesign plan or a full build handled for you, request a website development quote and we’ll walk through your timeline, budget, and SEO migration needs together.
FAQ
How do I plan a website redesign?
Start with discovery: audit your analytics, interview stakeholders, and set 3 to 5 measurable KPIs before any design work begins. From there, move through planning, design, development, testing, and a staged launch, with an SEO migration plan (URL mapping and redirects) locked in before development starts.
How much does it cost to redesign a website?
Cost depends heavily on scope, page count, and whether you need custom integrations like a CRM or payment system, so there’s no single figure that applies across projects. Request a quote based on your specific requirements rather than relying on a generic estimate.
What are the 7 C’s of website design?
Definitions vary across sources, but a common version covers context, content, community, customization, communication, connection, and commerce, as general principles for structuring a site around user needs. Treat it as a planning lens rather than a strict checklist, since the phased roadmap above covers the practical steps more directly.
What is the 3 second rule in website design?
The 3 second rule is a common guideline suggesting visitors form an impression of a site, and decide whether to stay, within the first few seconds of loading. It’s closely tied to performance: meeting Core Web Vitals targets like LCP under 2.5 seconds helps ensure the page is usable within that window rather than still loading.
