Introduction
A website redesign is a chance to fix how your site actually works for the people using it and for the business goals riding on it. A new color palette alone will not get you there.
Most redesign projects start because something specific is broken. Maybe navigation confuses visitors, mobile pages feel clunky, or forms quietly fail to convert. Maybe your CMS can't keep up with how fast your product changes. Search rankings might be slipping while nobody can explain why.
This guide walks through the full process:
- Auditing your current site
- Researching real users
- Protecting the SEO equity you've already earned
- Validating design decisions before you build
- Launching without breaking things
- Keeping the site healthy long after launch
We'll draw on evidence from NN/g, Google, and W3C, along with lessons from our own work redesigning complex B2B platforms.
Key Takeaways
- Base redesign decisions on analytics, user research, and accessibility audits—not internal opinions
- Set measurable outcomes first, then let them drive scope and budget
- Protect SEO with a URL inventory, redirect map, and post-launch monitoring
- Build accessibility and mobile usability in from day one, not as a final polish step
- Assign post-launch ownership so improvements don't stop at go-live
What a Website Redesign Includes
A real redesign touches structure, content, user experience, visual design, technology, accessibility, and performance together. That's different from a content edit or a visual refresh where the layout stays the same but colors and fonts change.
NN/g draws a useful line here: some projects labeled "redesigns" are purely visual reskins, while others rework taxonomy, information architecture, and usability from the ground up. Neither approach is universally correct; the right scope depends on what's actually broken.
Three Levels of Redesign
- Surface redesign: Updates typography, color, and imagery. Fast and low-risk, but it won't fix structural problems.
- Structural redesign: Reworks navigation, page hierarchy, and content organization around how users search and think.
- Operational redesign: Covers surface and structure, plus content workflows, governance, and who owns updates after launch.
Not every problem needs a full rebuild. If your issue is isolated, like one confusing form or a single outdated page, a targeted UX improvement often solves it faster and cheaper than starting over.
When the product is a complex B2B or SaaS platform, scope usually runs deeper than page design. Data-heavy products with technical or specialized users often need workflow mapping, information architecture testing, and integration planning before any wireframes. Dashboards, permissions, and third-party data feeds still have to work after the new design ships.
Signs Your Website Needs a Redesign
Some signals point to isolated fixes. Others suggest the whole structure needs rethinking. Here's how to tell the difference.
User Experience Warning Signs
- Visitors can't find core information without using search
- Multiple calls to action compete for the same click
- Terminology confuses users unfamiliar with internal jargon
- Task paths dead-end or require too many steps
- Support tickets repeat the same questions the website should answer
Business and Messaging Signals
Rebrands, new products, or a shift in target audience can make an existing site actively misrepresent the company. Common signals include:
- Homepage copy that still describes discontinued products
- Messaging aimed at an audience you no longer serve
- Brand voice or visuals that clash with current positioning
Technical and Performance Signals
- Pages behave poorly on mobile devices
- Load times lag, especially on key landing pages
- The CMS makes routine updates difficult or requires developer involvement
- Integrations feel fragile or break during updates
- Outdated platforms raise security concerns
Accessibility Indicators
Accessibility gaps are more common than most teams assume. WebAIM's review of one million homepages found detectable WCAG failures on 95.9% of sites, with low-contrast text on nearly 84%. Watch for:
- Missing alt text on images
- Weak color contrast on buttons and body text
- Forms that don't work with keyboard navigation
- Poor heading structure that confuses screen readers
Prioritizing What to Fix First
Separate issues that block access or essential tasks from issues that are simply dated. A redesign makes sense when several problems trace back to the same underlying weakness, like an information architecture that never accounted for how your product line grew.
How to Plan a Website Redesign
Planning happens before anyone opens a design tool. Skip this stage and you'll spend the build phase relitigating decisions that should've been settled up front.
Establish the Business Case
Connect every goal to a measurable user action. Vague goals like "modernize the site" don't hold up during scope discussions. Better examples:
- Increase qualified demo requests by a specific percentage
- Reduce time-to-complete for a core signup workflow
- Achieve WCAG 2.2 AA conformance across priority pages
- Cut repeat support tickets tied to confusing navigation
Audit the Current Website
A thorough audit covers analytics, content, information architecture, technical performance, SEO, accessibility, integrations, CMS usability, and brand consistency. Document what gets kept, revised, consolidated, redirected, or cut entirely.
A UX audit should be a data-backed evaluation of friction points across your key user flows, with a prioritized roadmap—not a stylistic critique or a list of opinions.
Research the People Who Actually Use Your Site
Skipping user research is the most common way redesigns go sideways. Combine:
- Stakeholder interviews to surface internal assumptions and constraints
- Customer interviews and surveys to hear language and pain points directly
- Support-ticket analysis to spot recurring confusion
- Session recordings and usability testing to watch real behavior, not reported behavior
Structural testing pays off. In an NN/g case study of a B2B manufacturer, tree testing on a revised navigation structure raised the site's findability score from 4.0 to 7.4 out of 10. Testing navigation before launch catches problems no amount of internal debate would surface.
Map Information Architecture Before Designing Pages
Show how navigation, page hierarchy, search, and calls to action support the tasks users actually need to complete. High-fidelity design should come after this map is validated, not before.
Build a Realistic Scope and Budget
Once the IA is validated, lock scope and budget around it. Account for content creation, migration, accessibility work, development, integrations, QA, SEO, stakeholder review cycles, and post-launch support. Redesigns that skip budgeting for content migration tend to blow past their timelines.
For B2B software teams with complex workflows, decide early whether an outside research-led UX audit is warranted. An external read can separate real user friction from internal politics or sunk-cost attachment to existing design decisions, and that clarity keeps scope honest before build work starts.
The Website Redesign Process
Once planning is locked, the actual build follows a sequence. Skipping steps is how most expensive rework starts.
Strategy and Discovery
Confirm goals, audiences, requirements, and success measures in a shared brief. This document becomes the reference point that keeps design opinions from overriding evidence later in the project.
Content and SEO Planning
Complete a content inventory, keyword and search-intent review, page-mapping exercise, and URL redirect plan before anyone rewrites or removes a page. Google's site-move guidance is direct: map old URLs to new destinations, use permanent redirects where URLs change, and avoid routing unrelated old pages to a single homepage. Skipping this step is the fastest way to lose search visibility at launch.
UX and Interaction Design
Journey maps, sitemap revisions, wireframes, and prototypes come next. For a recent higher-education intranet project, our team replaced department-based navigation with a needs-based structure after card sorting and tree testing. Research wrapped in under two weeks, then the redesigned site launched in beta for real-world testing.
Accessibility and Inclusive Design
Build in semantic structure, keyboard access, readable typography, sufficient contrast, and descriptive labels from the start. Retrofitting accessibility after launch costs more and fixes less. Our WCAG 2.2 AA audits cover:
- Automated tooling plus manual screen-reader testing with NVDA or VoiceOver
- Keyboard-only navigation and focus order
- Color contrast, text alternatives, and semantic structure
- Forms, embedded media, and video players
Development and Integration
Translate approved designs into maintainable templates, then lock in the operational basics:
- Connect forms and third-party systems
- Preserve existing analytics and tracking
- Let content editors manage pages without a developer for every update
Validation and Iteration
Test representative tasks with real users, review with subject-matter experts, and run accessibility checks before treating "approved" as "finished." Validation findings should drive a prioritized revision list, not just a rubber stamp.
Launch, Measure, and Maintain the New Website
Launch day isn't the finish line. It's the point where you find out if the planning held up.
Pre-Launch Checklist
- Redirects and canonical URLs confirmed
- Metadata and structured content migrated
- Internal links updated to new page structure
- Forms and integrations tested end-to-end
- Backups completed and permissions assigned
- Analytics and Search Console connected
- Performance, accessibility, and mobile layouts verified across browsers
Launch Safely
Protect the cutover with a few non-negotiables:
- Staging environment for final verification
- Content freeze or documented migration plan
- Rollback process if something breaks
Assign ownership for the first few weeks so someone is actively watching errors, ranking shifts, conversion changes, and user feedback, not just hoping everything holds.
Measure Against Your Baseline
Compare post-launch results with the baseline established during your original audit. Don't assume every traffic dip or conversion change is caused by the redesign itself; investigate before reacting.
Even a well-planned migration can surface broken redirects after launch. Fix those quickly, then look for the gains that show up once the noise settles.
Establish Ongoing Governance
- Assign content owners for each major section
- Set review intervals for outdated pages
- Document design and accessibility standards for future updates
- Monitor broken links and performance monthly
- Maintain a prioritized backlog instead of letting small issues pile up
A redesign that launches well but has no ownership plan tends to drift back into the same problems within a year or two.
For B2B software teams that need more than a visual refresh, an end-to-end partner covering research, validation, accessibility, design, and development helps the site keep working as the product evolves.
Frequently Asked Questions
What is a website redesign?
A website redesign is a substantial improvement to an existing site's structure, content, user experience, visual design, technology, accessibility, or performance. It goes beyond changing appearance alone.
What are the 7 C's of website design?
The seven C's are context, content, community, customization, communication, connection, and commerce. The framework came from e-commerce customer-interface research; some authors swap in terms like clarity or credibility.
What are the five golden rules of a website?
Five practical rules are a clear purpose, intuitive navigation, readable content, responsive and accessible design, and fast, trustworthy performance. Keep the homepage simple and make what you offer obvious within seconds.
How do I know if my website needs a redesign?
Look for poor usability, outdated content or branding, weak mobile performance, accessibility barriers, declining search or conversion results, and CMS limitations that block routine updates. When several of these stack up, you likely need a structural redesign, not a cosmetic refresh.
How do I redesign a website without losing SEO?
Build a URL inventory and page-mapping plan, apply relevant 301 redirects, preserve metadata and internal links, and update your XML sitemap before launch. Monitor Search Console closely for the first few weeks after going live to catch issues early.
