Website Redesign: The Complete Checklist 2026
When is a website redesign worth it? The complete checklist with 30+ items — from analysis to launch. Nothing forgotten.

Your website is three years old. Maybe five. The design feels dated, your bounce rate keeps climbing, and your competitors launched something modern last month. You're thinking about a redesign.
Good instinct — but a redesign done wrong can tank your rankings, break your conversion funnel, and cost twice as much as it should. I've seen it happen. Company spends 20k on a beautiful new site, traffic drops 40% because nobody thought about SEO migration, and six months later they're back to square one.
This checklist covers every phase: from "should I even redesign?" to post-launch monitoring. 30+ concrete points. Print it out if you want.
Phase 0: Do you actually need a redesign?
Not every aging website needs a full redesign. Sometimes a targeted optimization does more for less money. A professional website audit helps you figure out which one you need.
Signs you need a full redesign
- Your site is not mobile-responsive (still happens in 2026)
- Page load times exceed 4 seconds on mobile
- Your CMS is abandoned or severely outdated (old WordPress, Joomla 3.x, Drupal 7)
- The tech stack prevents you from adding features you need
- Your brand has fundamentally changed — new positioning, new audience, new products
- Conversion rate is below industry average despite decent traffic
- The site is a patchwork of plugins, workarounds and technical debt
Signs you just need optimization
- The design is fine but performance is slow — that's a performance optimization project, not a redesign
- Content is outdated but structure is solid — update the content
- Individual pages don't convert — A/B test those pages
- SEO is weak — an SEO overhaul is cheaper than a full rebuild
Phase 1: Analysis (Week 1 – 2)
Before you touch a single pixel, you need data. Opinions are cheap — data tells you what actually matters.
Checklist: Analysis
- Google Analytics audit: Which pages get traffic? Which convert? Where do people leave?
- Core Web Vitals check: LCP, FID/INP, CLS — your baseline numbers
- SEO crawl: Current rankings, indexed pages, broken links, redirect chains
- Heatmap analysis: Where do users click? How far do they scroll? (Hotjar, Microsoft Clarity)
- Competitor analysis: What are the top 3 – 5 competitors doing better?
- User feedback: What do customers say about the site? Support tickets, reviews, direct feedback
- Content audit: Which content performs, which doesn't? What's missing?
- Technical inventory: All integrations, forms, tracking scripts, third-party tools
The result: a document that tells you exactly what works, what's broken, and what needs to change. Every design decision later should reference this analysis.
Phase 2: Strategy & planning (Week 2 – 3)
Checklist: Strategy
- Define goals: What should the redesign achieve? More leads? Higher AOV? Lower bounce rate? Pick 2 – 3 measurable goals
- Target audience: Who are you building for? Create or update user personas
- Sitemap: New page structure based on analytics data and business goals
- Content plan: Which pages stay, which go, which are new? Who writes the content?
- Tech stack decision: Same platform with a new theme? Or a full rebuild on modern tech?
- Budget and timeline: Realistic, with buffers. Content always takes longer than expected
- SEO migration plan: URL mapping, redirect plan, content preservation (this is non-negotiable)
- Tracking setup: Which KPIs will you measure? Set up tracking before launch, not after
Phase 3: Design (Week 3 – 5)
Checklist: Design
- Wireframes first: Layout and information architecture before visual design
- Mobile-first: Design for the smallest screen first, then expand. 60%+ of traffic is mobile
- Design system: Colors, typography, spacing, components — documented and consistent
- Accessibility: Contrast ratios, font sizes, keyboard navigation, alt texts — from the start, not retrofitted
- Performance budget: Max image sizes, font count, JS bundle limits — set these before design starts
- CTA placement: Every page needs a clear next action. Above the fold, visible, compelling
- Trust elements: Reviews, logos, certifications — where to place them for maximum impact
- Prototype testing: Show the design to 5 – 10 real users before development starts
Phase 4: Content migration (Week 4 – 6)
This is where most redesigns fall apart. The design is ready, development can start, but the content is still the old stuff. Don't just migrate content — improve it.
Checklist: Content
- URL mapping: Old URL → New URL for every page. No exceptions. This document prevents SEO disaster
- 301 redirects: Every old URL that changes must redirect to its new location
- Content rewrite: Don't copy-paste old texts. Rewrite for the new structure and goals
- Image optimization: WebP format, proper sizing, lazy loading, meaningful alt texts
- Meta data: Title tags, meta descriptions, OG images — for every page
- Internal linking: Update all internal links to the new URL structure
- Forms: Test every form. Check that submissions go where they should
- Legal pages: Privacy policy, imprint, terms — update dates and company info
Phase 5: Development (Week 5 – 8)
Checklist: Development
- Staging environment: Develop on a separate URL, never on the live site
- Performance: Lighthouse scores 90+ on every page. Test during development, not at the end
- Responsive testing: iPhone SE, standard Android, iPad, Desktop — at minimum
- Browser testing: Chrome, Safari, Firefox. Edge if your audience skews corporate
- Structured data: Schema.org markup for organization, products, FAQ, breadcrumbs
- XML sitemap: Auto-generated, includes all new URLs
- Robots.txt: Correct — staging was blocked, production is not
- Cookie consent: GDPR-compliant banner that actually blocks scripts until consent
- Error pages: Custom 404 and 500 pages that help users, not confuse them
- Security headers: HSTS, X-Frame-Options, CSP — set from day one
Phase 6: Pre-launch testing (Week 8)
Checklist: Before you flip the switch
- Full crawl: Run Screaming Frog or Sitebulb on the staging site. Zero broken links
- Redirect test: Test every 301 redirect. All of them
- Form testing: Submit every form. Check emails arrive, data stores correctly
- Speed test: PageSpeed Insights on all key pages. Mobile and desktop
- Analytics check: Is tracking firing on every page? Goals and events working?
- Search Console: Prepare for URL change if domain changes
- Backup: Full backup of the old site. Database, files, everything
- DNS TTL: Lower TTL 48 hours before launch for faster propagation
- Rollback plan: If everything goes wrong, how do you get the old site back in 15 minutes?
Phase 7: Launch day
Checklist: Launch
- Deploy during low traffic: Tuesday or Wednesday morning, never Friday
- DNS update: Point domain to new hosting
- SSL certificate: Verify HTTPS works on all pages
- Redirect activation: All 301s active and working
- Remove staging blocks: robots.txt allows crawling, noindex tags removed
- Submit sitemap: Submit new sitemap to Google Search Console
- Monitor: Watch error logs, analytics, and server metrics for the first 2 hours
Phase 8: Post-launch (Week 9 – 12)
The redesign is not done when the site goes live. The first 4 weeks after launch are where you catch problems and optimize.
Checklist: Post-launch
- Daily monitoring (week 1): Rankings, traffic, errors in Search Console, conversion rates
- 404 monitoring: Check for crawl errors daily and add redirects for any missed URLs
- User testing: Watch 10 – 20 real sessions (Hotjar recordings). What trips people up?
- Performance baselines: Document your new Lighthouse scores and Core Web Vitals
- A/B testing: Start testing your key pages against variations. The redesign was a hypothesis — now validate it
- Content gaps: Which new pages are underperforming? Add content, internal links, or restructure
- Team training: If you have a CMS, make sure your team knows how to use it properly
The one mistake everyone makes
They focus on how the new site looks and forget about what it does. A beautiful website with 40% slower load times and broken SEO is a downgrade, not an upgrade.
The design matters, obviously. But the performance, SEO migration, and content strategy matter more. Get those right, and even a modest design improvement will outperform a stunning redesign that ignores them.
Need help with your redesign? I offer complete website rebuilds that cover every phase — from analysis to post-launch optimization. Or start with a free website audit to find out what your current site actually needs.
Frequently Asked Questions
How long does a website redesign take?
A typical redesign takes 8 – 12 weeks from kickoff to launch. The biggest time factor is content — if you need new copy, photography, and translations, add 2 – 4 weeks. A minimal redesign (same content, new design) can be done in 4 – 6 weeks.
How much does a redesign cost?
For a standard business website with 10 – 20 pages: 5,000 – 15,000 EUR with a freelancer, 15,000 – 50,000 EUR with an agency. The cost depends on complexity, custom features, and whether you need content creation. A rebuild on modern technology typically costs less in the long run because of lower maintenance.
Will I lose SEO rankings during a redesign?
If you follow the SEO migration checklist above — no. Some temporary fluctuation in the first 2 – 4 weeks is normal as Google re-crawls your site. But with proper redirects, URL mapping, and content preservation, your rankings should stabilize or improve within a month.
Should I redesign on the same platform or switch?
If your current platform limits you (slow, no features, expensive maintenance), switch. If it works well and only the design is outdated, stay. Switching platforms during a redesign adds complexity and cost, but it can be worth it if the old platform is holding your business back.
Can I redesign in phases instead of all at once?
Yes, and for larger sites I recommend it. Start with the homepage and your top 5 – 10 traffic pages. Measure the impact. Then roll out to the rest. This reduces risk and lets you learn from real data.
Related Articles
Need support?
I help you choose the right technology for your project — and build it.
Book a consultation