Why Most Redesigns Go Wrong
A website redesign sounds straightforward: the current site looks outdated, so build a new one that looks better. Except the finished product arrives 4 months late, $15,000 over budget, and somehow converts worse than the old site.
This happens because redesigns fail in the planning phase, not the design phase.
The common failure pattern:
- Someone decides "we need a new website"
- They find a designer/agency and say "make it look modern"
- Design happens without defined goals or content strategy
- Content migration is an afterthought
- SEO considerations are an afterthought
- The site launches looking beautiful but performing worse
- Everyone blames the designer
The designer isn't the problem. The process is.
Before You Start: Do You Actually Need a Redesign?
Not every website problem requires tearing the whole thing down.
A redesign IS necessary when:
- The site is on outdated technology that can't be maintained or extended
- The information architecture is fundamentally broken (users can't find what they need)
- The site is not mobile-responsive and can't be retrofitted
- Your business has changed so significantly that the site no longer represents what you do
- Page speed is critically poor and the architecture prevents improvement
- Security vulnerabilities exist that can't be patched
A redesign ISN'T necessary when:
- The logo/colours look dated → refresh the visual design on the existing site
- Conversion rates are low → optimise landing pages, CTAs, and forms first
- Content is outdated → update the content, not the container
- "It doesn't look like competitor X" → this isn't a strategy
- A new hire wants to "put their stamp on it" → ego isn't a business case
Optimising your existing site is faster, cheaper, and lower risk than rebuilding. Always ask: can we fix this without starting over?
Phase 1: Define Success (Weeks 1-2)
The single most important phase. Everything that follows depends on getting this right.
Set Measurable Goals
A redesign without defined goals has no way to measure whether it succeeded. "Look better" is not a goal. These are:
- Increase monthly contact form submissions from 12 to 30
- Reduce bounce rate from 65% to 45%
- Improve page load speed from 6 seconds to under 2 seconds
- Increase organic traffic by 40% within 6 months of launch
- Achieve WCAG 2.1 AA accessibility compliance
- Support a new service line that doesn't exist on the current site
Write down 3-5 specific, measurable goals. Every design decision should support at least one of them.
Audit the Current Site
Analytics audit:
- Which pages get the most traffic? (Don't accidentally remove your best performers)
- Where do users enter the site? (Top landing pages)
- Where do users leave? (High-exit pages need attention, not just redesign)
- What's the current conversion rate? (Baseline to improve against)
- How does mobile compare to desktop? (Conversion, bounce rate, session duration)
Content audit:
- List every page on the current site
- For each page: keep, update, merge, or delete
- Identify content gaps (what should exist but doesn't)
- Review which content drives conversions vs. which is dead weight
SEO audit:
- Current keyword rankings (what are you ranking for that you can't afford to lose?)
- Backlink profile (which pages have earned links?)
- URL structure (will URLs change? You'll need redirects)
- Metadata, heading structure, internal linking
Technical audit:
- Current CMS and hosting
- Page speed scores (Core Web Vitals)
- Security issues
- Broken links and errors
- Third-party integrations that must survive the redesign
Define the Scope
Document exactly what's included:
- Number of page templates (homepage, service page, blog post, contact, about, etc.)
- Number of unique pages
- New functionality (forms, calculators, booking systems, client portals)
- Integrations (CRM, email marketing, analytics, payment processing)
- Content creation (who writes the new copy?)
- Photography/video (who provides visual assets?)
- Mobile-specific design requirements
- Browser support requirements
Scope creep is the #1 budget killer. If it's not in the scope document, it's a change request with a new timeline and cost.
Phase 2: Strategy and Planning (Weeks 2-4)
Information Architecture (IA)
How your site is structured — the pages, the hierarchy, the navigation.
Map the user journey:
- Who are the primary audiences?
- What do they need to accomplish?
- What's the shortest path from landing page to conversion?
Create a sitemap:
- Visual map of every page and how they connect
- Primary navigation structure
- Secondary navigation and footer links
- Keep it flat — most users shouldn't need more than 3 clicks to reach any page
Card sorting (for complex sites): Ask 5-10 real users to organise your content into groups that make sense to them. Their mental model often differs from your internal organisation.
Wireframes
Low-fidelity layouts showing content placement and hierarchy — before any visual design happens.
- Homepage wireframe: What appears above the fold? What's the primary CTA? How does a new visitor understand what you do in 5 seconds?
- Key landing page wireframes: Service pages, product pages, conversion-focused pages
- Blog/content wireframes: How articles are displayed, sidebar vs. no sidebar, related content
Wireframes prevent the most expensive mistake in web design: designing something beautiful that doesn't accommodate the actual content.
Content Strategy
Content before design. Always.
The most common redesign failure is designing page layouts before the content exists. The designer creates beautiful templates with Lorem Ipsum placeholders. Then the real content doesn't fit — the headline is too long, the description is too short, there aren't enough product photos.
- Write (or plan) the content for your top 5 pages before design begins
- At minimum, define the content blocks: what type of content goes where
- Assign content ownership: who writes each page, by when?
- Include content in the project timeline — it always takes longer than expected
Phase 3: Design and Development (Weeks 4-10)
Design Process
Style tile or mood board first: Before designing full pages, align on visual direction — colours, typography, photography style, UI elements.
Design key templates: Not every page needs a custom design. Typically 4-8 templates cover an entire site:
- Homepage
- Primary service/product page
- Secondary content page
- Blog listing page
- Blog post page
- Contact/conversion page
- About/team page
Review in context: Don't review designs as static mockups in a PDF. Review them in a browser at different screen sizes. A design that looks beautiful at 1920px wide might fall apart at 375px.
Development
Build mobile-first: Design and build for mobile screens first, then expand to desktop. Over 60% of traffic is mobile — it shouldn't be an afterthought.
Performance from the start: Don't build a fast site later — build speed into the architecture from day one. Image optimisation, lazy loading, minimal JavaScript, efficient CSS.
CMS flexibility: Your team will need to update content after launch. Make sure the CMS is intuitive enough that non-technical staff can make changes without developer assistance.
Staging Environment
All work happens on a staging site (not live). This allows:
- Ongoing review and feedback without affecting the live site
- SEO testing before launch
- Content population and review
- Cross-browser and device testing
- Performance testing
Phase 4: Content Migration (Weeks 8-12)
This is the phase everyone underestimates.
What Needs to Happen
- All pages from the content audit marked "keep" or "update" need to be migrated
- Blog posts — potentially hundreds — need to move to the new structure
- Images need to be optimised and uploaded
- Metadata (titles, descriptions) need to be set for every page
- Internal links need to be updated
- Forms need to be tested
- Integrations need to be connected and tested
URL Mapping and Redirects
This is non-negotiable for SEO.
Create a spreadsheet mapping every old URL to its new URL:
| Old URL | New URL | Redirect Type | |---------|---------|---------------| | /services/web-design | /services/website-design | 301 | | /blog/old-post-slug | /insights/old-post-slug | 301 | | /about-us | /about | 301 |
Every old URL that changes must have a 301 redirect to the new equivalent. Missing redirects = lost rankings, lost traffic, and broken backlinks.
Phase 5: Testing and Launch (Weeks 10-14)
Pre-Launch Checklist
Functionality:
- [ ] All forms submit correctly and send to the right recipients
- [ ] All links work (no 404s)
- [ ] CTA buttons work and go to correct destinations
- [ ] Search functionality works (if applicable)
- [ ] E-commerce checkout works (if applicable)
- [ ] Third-party integrations connected (CRM, analytics, email)
SEO:
- [ ] All 301 redirects in place and tested
- [ ] XML sitemap generated and submitted
- [ ] Robots.txt correct (staging site often blocks crawlers — remove that)
- [ ] Meta titles and descriptions set for all pages
- [ ] Canonical tags correct
- [ ] Google Analytics / GA4 tracking installed
- [ ] Google Search Console updated
- [ ] Schema markup implemented
Performance:
- [ ] Page speed tested (target: under 3 seconds on mobile)
- [ ] Images optimised
- [ ] Core Web Vitals passing
- [ ] Tested on slow connections
Cross-browser/device:
- [ ] Chrome, Safari, Firefox, Edge
- [ ] iOS Safari, Android Chrome
- [ ] Various screen sizes (phone, tablet, desktop, ultrawide)
Content:
- [ ] All content proofread
- [ ] No placeholder text remaining
- [ ] All images have alt text
- [ ] Contact information correct
- [ ] Legal pages current (privacy policy, terms)
Launch Strategy
Don't launch on Friday. If something breaks, you want weekdays to fix it. Tuesday or Wednesday is ideal.
Monitor aggressively for 2 weeks:
- Google Search Console for crawl errors
- Analytics for traffic changes
- Form submissions (are they still coming in?)
- Page speed in real-world conditions
- User feedback
Choosing a Web Designer/Agency
What to Look For
- Portfolio of similar projects — have they built sites for businesses like yours?
- Process documentation — do they have a defined process, or is it "we'll figure it out"?
- SEO awareness — do they mention SEO in their process, or is it an afterthought?
- Post-launch support — what happens after the site goes live?
- Transparent pricing — fixed price or hourly? What's included vs. extra?
Red Flags
- They start designing before asking about your goals
- No mention of content strategy or migration
- No mention of redirects or SEO preservation
- "We'll make it fast later" (performance is architectural, not cosmetic)
- They can't explain their process clearly
- Portfolio is all visual flash with no mention of results
Realistic Timelines
| Site Complexity | Timeline | |----------------|----------| | Simple (5-10 pages, template-based) | 4-8 weeks | | Medium (15-30 pages, custom design) | 8-14 weeks | | Complex (50+ pages, custom functionality) | 14-24 weeks | | E-commerce (product catalogue, checkout) | 12-20 weeks |
Add 2-4 weeks if content creation is part of the project.
Common Mistakes
- No defined goals — redesigning for aesthetics without measurable objectives
- Design before content — creating layouts for content that doesn't exist yet
- Ignoring current performance data — removing high-performing pages or content
- No redirect plan — destroying SEO equity built over years
- Scope creep — "Can we also add..." without adjusting timeline or budget
- Testing only on desktop — most visitors are on mobile
- Launching without monitoring — problems caught in week 1 are recoverable; problems caught in month 3 aren't
- Not involving the people who'll maintain it — if your team can't update the site without a developer, it will become outdated within months
Start Here
- Define 3-5 measurable goals for the redesign
- Audit your current site (analytics, content, SEO, technical)
- Document the scope in writing before engaging a designer
- Plan your content before designing layouts
- Map all URLs for redirects
- Review designs on mobile, not just desktop
- Test everything before launch (forms, links, speed, redirects)
- Monitor daily for 2 weeks post-launch
A website redesign is a significant investment. Protect that investment with a process that ensures the new site isn't just prettier than the old one — it performs better, converts better, and positions your business for the next 3-5 years of growth.