Your site looks dated, the sales team complains about lead quality, and someone on the board just asked why the homepage feels slower than the competition. So you start pricing out a rebuild. Then a quieter fear shows up: what if the new site looks great and converts worse than the old one?
That fear is well founded. Plenty of redesigns ship beautiful pages and flat revenue. Knowing how to redesign a website is less about picking a visual direction and more about protecting the paths that already produce leads and sales.
The teams that get this right treat a redesign like a product decision with measurable stakes. They audit before they design. They set conversion targets before they open Figma, and they test critical journeys before launch instead of after.
Keep reading to learn how to scope the work, run discovery, plan architecture and content, design and build around real user tasks, and validate the release with data. Follow this sequence, and you will be able to defend the redesign with numbers, not opinions.
Decide Whether the Problem Calls for a Refresh or a Rebuild
Not every underperforming site needs a rebuild. A refresh updates the visual design, typography, and messaging on the existing platform. A rebuild changes the foundation: content management system, code, structure, or all three.
The deciding factor is the source of the pain. If the layout converts but looks tired, that is design debt, and a revamp usually solves it. If your forms break on mobile, your CMS blocks publishing, or page templates cannot support new products, you are dealing with structural failure.
How to Redesign a Website Around Measurable Business Risk
Start by naming the business risk in numbers. A weak value proposition costs you qualified demos. Poor mobile responsiveness costs you the paid traffic you already bought through Google Ads.
Write the risk as a sentence with a metric attached. “Mobile visitors convert at half the desktop rate” is a scope decision. “The site feels old” is not.
Recognize the Signals That a Revamp Cannot Ignore
Some signals point clearly to structural work. Smashing Magazine notes that the most important indication that it is time to redesign is metrics that start to tank.
Watch for these:
- Conversion rates falling while traffic holds steady
- Editors blocked by the current content management system
- Templates that cannot support new services or pricing models
- Responsive design failures on the pages that drive revenue
- Brand identity and brand voice that no longer match how you sell
Set the Right Scope for Rebranding, Migration, or New Functionality
Rebranding, platform migration, and new functionality are three separate projects. Bundling all three into one release multiplies risk and makes failure hard to diagnose. Sequence them instead. If branding is unsettled, lock the identity first.
Then migrate. Then add features. Once the scope is honest, discovery tells you where the money is actually leaking.
Run Discovery Before Making Design Decisions
Discovery exists to find out where visitors drop off and why. Skip it, and the design team ends up guessing at problems you could have measured in a week.
CMOs who lack defined core KPIs struggle to advise on the changes their websites require. The same gap sinks redesigns at product companies.
Audit Traffic, Conversion Paths, and High-Value Pages
Start with a website audit and a content audit in Google Analytics. Rank pages by revenue and lead generation contribution, not by pageviews.
Then map the user journey for each conversion goal. Look at bounce rate on entry pages, drop-off in multi-step forms, and cart abandonment at checkout. Those numbers tell you which pages are untouchable and which deserve a rethink.
Combine Quantitative Data With Direct User Evidence
Quantitative data shows where users leave. Qualitative data explains why. Pair heatmaps and session recordings with user interviews, surveys, and usability testing on the flows that matter most.
Five moderated sessions will surface more friction than a month of dashboard staring. Use that user research to build user personas grounded in your real target audience.
Benchmark the Market Without Copying Competitors
Competitive analysis is for spotting expectations, not for borrowing layouts. Note how competitors handle pricing clarity, demo requests, and product proof. Then decide where you differentiate.
Turn Findings Into SMART Goals and Accountable KPIs
Convert findings into SMART goals with an owner attached. “Raise demo form completion from 12% to 18% within two quarters” is accountable. “Improve UX” is not.
Pick three to five key performance indicators and agree on them before wireframes exist. Those goals now shape the structure and content of the new site.
Plan the Experience, Content, and Search Foundation
Structure and content decide most of your conversion outcome before a single pixel is designed. Plan them together. Treat search equity as a first-class requirement.
Build Information Architecture That Matches User Intent
Good information architecture reflects how buyers think, not how your org chart is drawn. Build a content inventory.
Then test a proposed sitemap with tree testing or card sorting. Practitioners recommend mapping the existing experience before proposing a new site structure. That map prevents you from deleting pages that quietly earn pipeline.
Prioritize Content Strategy Before Page Layouts
Write the message before you design the container. Real headlines, proof points, and CTAs reveal whether a page layout works. Placeholder text hides every weakness.
Draft content for your top landing pages first, including forms and the offer attached to each one. Strong UI and UX design services always start from the message and the task, not the grid.
Protect Search Equity During Structural Changes
SEO performance is where redesigns quietly bleed revenue. Every URL change needs a 301 redirect. Every high-ranking page needs its page title, meta description, and internal links preserved or improved.
Before launch, confirm:
- Redirect map complete for all changed URLs
- No broken links in navigation, footer, or body content
- Titles and meta descriptions carried over for ranking pages
- XML sitemap updated and submitted
- Organic traffic baseline recorded page by page
Create a Redesign Roadmap With Clear Ownership and Dependencies
Run the build in Scrum sprints with a named owner for content, design, engineering, and SEO. List dependencies openly. Content approval is the most common cause of slipped launches.
With the plan set, design work can focus on the tasks users actually came to complete.
Design and Build the New Experience Around Real Tasks
Design decisions should trace back to a task and a metric. Anything that cannot be tied to either is decoration.
Translate Requirements Into Wireframes and Testable User Flows
Move from sketch to wireframes to prototyping quickly. Build clickable prototypes in Figma and run usability testing on the top three user flows before visual design starts. Watch where users hesitate. Hesitation predicts abandonment better than any opinion in a stakeholder review.
Use Visual Design to Reinforce Clarity and Trust
Visual design earns trust through readability and consistency. Typography, color palette, and imagery should push attention toward the next step, not compete with it. A documented design system that scales keeps buttons, forms, and states consistent as the site grows.
Engineer for Accessibility, Mobile Use, and Site Speed
Accessibility standards are conversion work. Sufficient color contrast, alt text, keyboard navigation, and clear focus states help every user, including those on a phone in bad light.
Test page load time in PageSpeed Insights and set a tight budget for the templates that carry traffic. A responsive mobile website that loads in under two seconds outperforms a prettier one that stalls.
Treat E-commerce and Lead Capture as High-Risk Conversion Journeys
Checkout and lead forms deserve their own scrutiny. On an e-commerce website, guest checkout, visible shipping costs, and inline validation reduce cart abandonment more than a new hero image. Now the release needs proof that it performs better than what it replaced.
Validate the Release and Measure What Changed
Launch is a test, not a finish line. Validate before go-live. Release in stages. Compare against the baseline you recorded during discovery.
Test Critical Journeys Before Launch
Run usability testing on the final build, not just the prototype. Then check every conversion path in staging: forms submit, confirmation pages fire, and tracking records events correctly.
Use a Phased Rollout to Reduce SEO and Revenue Risk
A phased rollout limits damage. Release a section or template group. Confirm the sitemap and redirects behave, then continue.
Compare the two approaches:
- Big-bang launch: faster to announce. Harder to diagnose. All traffic exposed at once
- Phased rollout: slower, but isolates broken links, SEO drops, and conversion dips to one area
Monitor Conversion, Search, and Experience Signals After Go-Live
Watch conversion rate, organic traffic, bounce rate, and user engagement daily for the first two weeks. Layer in heatmaps and session recordings to see how real behavior differs from the prototype. Use A/B testing in a platform like VWO on the highest-traffic pages. Test one variable at a time so results stay readable.
Create a Continuous Improvement Backlog From Evidence
Log every observed problem with its evidence and estimated revenue impact. That backlog turns continuous improvement into a funded habit instead of a wish list. The last decision is who owns this work with you.
Make the Redesign a Measurable Growth Decision
A redesign is a growth investment, so judge it the way you judge any other one: by conversions, lead generation, and revenue against a known baseline.
Choose a Partner That Connects UX, Technology, and Commercial Outcomes
The website redesign process breaks when UX, engineering, and marketing sit in separate contracts. Look for a partner who owns research, build, and performance together, and who will commit to your KPIs in writing.
Ask how they handle redirects, how they test, and what they measure in week one. Vague answers are a warning. If you are still shortlisting, review practical criteria for choosing a website redesign agency.
Start With a Focused Discovery Conversation
You do not need a full brief to start. Bring your analytics, your top three conversion problems, and your timeline.
A UX audit will tell you fast whether you need a refresh or a rebuild, and where the friction actually sits. M7 connects human-centered UX, clean engineering, and digital strategy and marketing services into one accountable team.
The riskiest part of any redesign is the set of pages that already produce the pipeline. Book a discovery call, and we will pinpoint them before anything gets rebuilt.
Frequently Asked Questions
What Are the First Steps to Take When Planning a Website Redesign?
Start with a website audit in Google Analytics to rank pages by revenue and lead contribution. Then record a conversion baseline for every key page. Those two steps protect you from replacing something that was quietly working.
How Do I Decide Whether My Website Needs a Refresh or a Full Rebuild?
If the structure converts and only the visuals feel dated, a refresh is enough. If your CMS blocks publishing, templates cannot support new products, or mobile journeys break, you need a rebuild.
What Should a Website Redesign Project Plan Include?
At minimum: audit findings, SMART goals with named owners, a sitemap, a content plan, a full redirect map, and a testing schedule. Run it in Scrum sprints so content approvals do not stall engineering.
How Can I Redesign a Website in Figma Before Development Begins?
Build wireframes and a clickable prototype in Figma for your top three user flows. Then run moderated usability testing with five to eight real users. Fix the friction in the prototype, where changes cost hours instead of sprints.
How Do I Preserve SEO Rankings and Traffic During a Website Redesign?
Map every old URL to its new destination with 301 redirects. Keep page titles and meta descriptions on ranking pages, and fix broken links before launch. Submit an updated sitemap and monitor organic traffic daily for two weeks.
Which Metrics Should I Use to Measure Website Redesign Success?
Track conversion rate by page, form, and checkout completion, organic traffic, bounce rate, and site speed against your pre-launch baseline. Pipeline and revenue are the metrics that settle the debate.
