A website redesign is one of the highest-risk, highest-reward projects a business can undertake. Done well, it strengthens your brand, improves conversion rates, and accelerates organic growth. Done poorly, it can destroy years of SEO equity, break user journeys that were generating revenue, and create months of recovery work.
The difference between a successful redesign and a damaging one almost always comes down to planning. Businesses that follow a structured checklist avoid the mistakes that cause post-launch traffic drops, broken functionality, and missed opportunities.
This 25-step checklist covers everything UK businesses need to address before, during, and after a website redesign.
Quick Answer
A successful website redesign requires structured planning across five phases: pre-redesign audit (benchmarking current performance), content and SEO migration (preserving rankings and redirects), design and UX review (ensuring improvements are data-driven), pre-launch testing (catching issues before users do), and post-launch monitoring (confirming everything works in production). Skipping the SEO preservation steps is the single most common cause of post-redesign traffic loss.
Phase 1: Pre-redesign audit (steps 1-7)
Before any design or development work begins, you need a complete picture of your current website's performance. This baseline determines what to preserve, what to improve, and what to retire.
Step 1: Benchmark current traffic and conversions
Document your current performance metrics as a baseline for measuring redesign success:
- Monthly organic traffic by page and landing page category.
- Conversion rates for key goals (form submissions, phone calls, purchases, bookings).
- Revenue or lead value attributed to the website.
- Bounce rates and engagement metrics for top pages.
- Traffic sources and their respective conversion rates.
Export this data from Google Analytics 4 and store it securely. You will need it for post-launch comparison.
Step 2: Audit existing SEO performance
Your current SEO position is an asset that must be protected during the redesign:
- Export all indexed URLs from Google Search Console.
- Document ranking positions for target keywords.
- Identify your top 20 organic landing pages by traffic.
- Note all pages with external backlinks (use Ahrefs or Semrush).
- Record current metadata (titles, descriptions) for all key pages.
- Document existing schema markup and rich results.
Step 3: Crawl the existing site
Run a comprehensive crawl using Screaming Frog, Sitebulb, or a similar tool:
- Record all URLs, response codes, and redirect chains.
- Identify existing 301 redirects that must be maintained.
- Note orphan pages and broken internal links.
- Document the current site architecture and URL structure.
- Export the full URL list for redirect mapping later.
Step 4: Identify content to keep, improve, or remove
Not all content deserves to survive a redesign. Categorise every page:
- Keep as-is: High-performing pages with strong traffic and conversions.
- Improve: Pages with good rankings but poor conversion or outdated content.
- Consolidate: Multiple thin pages covering similar topics that should be merged.
- Remove: Outdated, irrelevant, or zero-traffic pages (with proper redirects).
Step 5: Document current functionality
List every functional element on your current site:
- Forms (contact, booking, enquiry, newsletter signup).
- Integrations (CRM, email marketing, analytics, chat).
- E-commerce functionality (if applicable).
- User accounts and login systems.
- Third-party widgets and embedded content.
- API connections and data feeds.
Each function needs to be replicated, replaced, or deliberately retired in the new design.
Step 6: Gather user feedback
Your redesign should address real user problems, not just aesthetic preferences:
- Review analytics data for pages with high exit rates or low engagement.
- Analyse heatmaps and session recordings (Hotjar, Microsoft Clarity).
- Collect feedback from customer-facing teams about common website complaints.
- Review any customer survey data that mentions the website.
- Test current conversion paths to identify friction points.
Step 7: Define redesign goals and KPIs
Every redesign should have measurable objectives:
- Increase organic traffic by X% within 6 months.
- Improve conversion rate from X% to Y%.
- Reduce page load time to under 2.5 seconds.
- Achieve WCAG 2.2 AA accessibility compliance.
- Support specific new business goals (new services, new markets, new products).
Without clear KPIs, you cannot objectively assess whether the redesign was successful.
Key Takeaway
The pre-redesign audit is the most critical phase. Businesses that skip benchmarking, SEO auditing, and content categorisation before starting design work consistently experience post-launch problems. Document everything before you change anything.
Phase 2: Content and SEO migration (steps 8-13)
SEO preservation is where most redesigns fail. A URL structure change without proper redirects can eliminate years of ranking equity overnight.
Step 8: Create a complete redirect map
This is the single most important SEO task in any redesign:
- Map every old URL to its corresponding new URL.
- Include all current redirects (they must be maintained or updated).
- Account for URL structure changes, even minor ones.
- Plan redirects for removed pages to the most relevant alternative.
- Avoid redirect chains (old URL > intermediate URL > new URL). Each old URL should redirect directly to the final destination.
Test your redirect map thoroughly before launch. A spreadsheet with old URL, new URL, and redirect type (301 permanent) is the standard format.
Step 9: Preserve metadata and on-page SEO
Transfer optimised metadata from the old site to the new:
- Page titles and meta descriptions for all key pages.
- Header tag structure (H1, H2, H3 hierarchy).
- Image alt text.
- Internal linking structure.
- Canonical tags.
- Open Graph and Twitter Card metadata.
If you are improving metadata as part of the redesign, document both the original and updated versions so you can attribute any ranking changes to the content changes.
Step 10: Maintain URL structure where possible
Changing URLs is the primary cause of post-redesign ranking loss. If your current URL structure is logical and clean, keep it:
- Preserve existing URL paths for high-ranking pages.
- If you must change URLs, ensure 301 redirects are in place.
- Avoid adding unnecessary subdirectories or parameters.
- Maintain consistent URL patterns (lowercase, hyphens, no trailing slashes or consistent trailing slashes).
Step 11: Transfer and update schema markup
Structured data should be migrated and improved during the redesign:
- Transfer existing schema markup (Organisation, LocalBusiness, FAQ, Product, etc.).
- Update schema to reflect any changes in business information.
- Add new schema types where appropriate (BreadcrumbList, Article, Service).
- Validate all schema using Google's Rich Results Test before launch.
Step 12: Plan content migration
Content migration involves more than copying text:
- Migrate content in a structured format, not manually copy-pasting.
- Update internal links to use new URL paths.
- Resize and optimise images for the new design.
- Review and update any date-sensitive content.
- Ensure all downloadable files (PDFs, documents) are migrated and linked correctly.
Step 13: Preserve backlink equity
External backlinks are among the most valuable SEO assets:
- Identify all pages with external backlinks.
- Ensure those pages either maintain their URLs or have 301 redirects in place.
- Contact linking sites to update their links if major URL changes occur (for your most valuable backlinks).
- Monitor backlink profiles post-launch to catch any broken links.
Key Takeaway
The redirect map is the most important document in any website redesign. Every old URL must map to a relevant new URL via a 301 redirect. Failing to implement redirects correctly is the number one cause of organic traffic drops after a relaunch. Test redirects thoroughly in a staging environment before going live.
Phase 3: Design and UX review (steps 14-17)
Design decisions should be driven by data and user needs, not personal preference.
Step 14: Review information architecture
Your site structure should reflect how users and search engines navigate your content:
- Organise pages by user intent and business priority.
- Limit navigation depth to three clicks from the homepage for key pages.
- Create logical category structures that support internal linking.
- Ensure service pages, location pages, and conversion pages are prominently accessible.
- Plan for scalability: can new pages be added without restructuring?
Step 15: Prioritise mobile experience
Mobile traffic accounts for over 60% of web traffic in the UK. Your redesign must prioritise mobile UX:
- Design mobile-first, then adapt for desktop.
- Ensure tap targets are at least 48x48 pixels.
- Simplify navigation for mobile users.
- Optimise forms for mobile input (appropriate keyboard types, minimal fields).
- Test load times on 4G connections, not just Wi-Fi.
Step 16: Review conversion paths
Every key user journey should be audited and improved:
- Map the path from landing page to conversion for each user segment.
- Ensure CTAs are visible, clear, and consistent.
- Reduce form fields to the minimum necessary.
- Add trust signals (reviews, accreditations, security badges) near conversion points.
- Test checkout or booking flows end-to-end.
Step 17: Check accessibility compliance
WCAG 2.2 AA compliance should be a baseline requirement for UK business websites:
- Ensure sufficient colour contrast ratios (4.5:1 for normal text).
- Add proper alt text for all images.
- Ensure keyboard navigation works for all interactive elements.
- Use semantic HTML elements correctly.
- Test with screen readers (NVDA, VoiceOver).
- Provide visible focus indicators for keyboard users.
Accessibility is not optional. The Equality Act 2010 requires UK businesses to make reasonable adjustments to ensure disabled people can access their services, including digital services.
Phase 4: Pre-launch testing (steps 18-22)
Testing catches issues that are far cheaper to fix before launch than after.
Step 18: Cross-browser and device testing
Test your new site across:
- Chrome, Firefox, Safari, and Edge (latest two versions each).
- iOS and Android devices.
- Tablet, mobile, and desktop screen sizes.
- Both portrait and landscape orientations on mobile.
Use BrowserStack or similar tools for comprehensive cross-browser testing if you do not have access to physical devices.
Step 19: Test all forms and integrations
Every form and integration must be verified:
- Submit test entries through every form and confirm data reaches the correct destination.
- Verify CRM integrations are capturing data correctly.
- Test email notifications (confirmation emails, internal alerts).
- Check payment processing in test mode if applicable.
- Verify analytics tracking fires correctly on all pages and events.
- Test chat widgets, booking systems, and third-party tools.
Step 20: Validate Core Web Vitals
Run performance tests and ensure your new site meets Google's Core Web Vitals thresholds:
- Largest Contentful Paint (LCP): Under 2.5 seconds.
- Interaction to Next Paint (INP): Under 200 milliseconds.
- Cumulative Layout Shift (CLS): Under 0.1.
Test on both staging and, if possible, a production-like environment. Performance can vary significantly between staging servers and production hosting.
Step 21: Verify redirects on staging
Before launch, test every redirect in your redirect map:
- Use a tool like Screaming Frog to crawl the old URL list against the staging site.
- Verify that 301 redirects resolve to the correct destination.
- Check for redirect chains or loops.
- Confirm that old bookmark URLs and commonly shared links redirect correctly.
Step 22: Pre-launch SEO checklist
Run through these final SEO checks:
- XML sitemap is generated and includes all new URLs.
- Robots.txt allows crawling of all intended pages (remove any staging blocks).
- Canonical tags are set correctly on every page.
- Noindex tags are removed from all pages that should be indexed.
- Google Analytics 4 and Search Console are configured and verified.
- Structured data validates without errors.
- Hreflang tags are correct if serving multiple languages or regions.
Key Takeaway
Pre-launch testing should cover cross-browser compatibility, all forms and integrations, Core Web Vitals performance, redirect verification, and a comprehensive SEO checklist. Catching issues in staging is dramatically cheaper than fixing them after launch when they affect real users and search rankings.
Phase 5: Launch day and post-launch monitoring (steps 23-25)
Step 23: Launch day procedures
A structured launch minimises risk:
- Launch during a low-traffic period (typically early morning on a weekday).
- Implement all redirects simultaneously with the new site deployment.
- Verify DNS propagation if changing hosting providers.
- Clear all caches (CDN, server, CMS).
- Run a quick crawl of the live site to check for unexpected errors.
- Test critical conversion paths (contact forms, booking, checkout) on the live site.
- Submit the new sitemap to Google Search Console immediately after launch.
Step 24: First-week monitoring
Monitor these metrics closely during the first week:
- Crawl activity: Check Google Search Console for crawl errors and indexing status.
- Redirect performance: Verify redirects are working by monitoring 404 errors.
- Traffic patterns: Compare daily traffic to the pre-launch baseline.
- Conversion tracking: Ensure all goals and events are firing correctly.
- Core Web Vitals: Monitor real-user performance data through Search Console.
- User feedback: Watch for customer complaints or confusion.
Step 25: 30-day post-launch review
After one month, conduct a comprehensive review:
- Compare organic traffic to the pre-redesign baseline.
- Check ranking positions for target keywords.
- Review conversion rates against pre-redesign benchmarks.
- Identify any pages that lost significant traffic and investigate causes.
- Address any remaining 404 errors or broken links.
- Gather team and customer feedback on the new site.
- Document lessons learned for future projects.
A temporary traffic dip of 10% to 20% in the first two weeks is normal for any significant redesign. If traffic drops more than 30% or does not recover within four weeks, investigate redirect implementation, content changes, and technical issues urgently.
Common redesign mistakes to avoid
Even with a checklist, some mistakes occur repeatedly across projects:
- Changing URLs without redirects: The most damaging and most common mistake.
- Removing high-traffic pages: Pages that seem outdated may still drive significant organic traffic.
- Ignoring mobile: Testing primarily on desktop and treating mobile as an afterthought.
- Launching on a Friday: If something goes wrong, you want a full team available the next working day.
- Not backing up: Always maintain a complete backup of the old site, including database and files.
- Forgetting analytics: Failing to verify tracking on the new site means flying blind during the critical post-launch period.
- Scope creep: Adding features during the redesign without adjusting timeline and budget.
- No content freeze: Continuing to add content to the old site during development, creating a moving target for migration.
Next steps
A website redesign done right is a significant investment that delivers returns for years. Done carelessly, it can set your business back by months. Use this checklist to ensure your redesign strengthens your online presence rather than undermining it.
If you are planning a website redesign and want to ensure your SEO equity is protected throughout the process, we specialise in redesign projects that maintain and improve organic performance.
Web Design
Strategic website redesign for UK businesses. We protect your SEO equity, improve conversion rates, and deliver modern designs that perform.
About the Author
Pankaj Karad
Founder & CEO
Pankaj Karad is the founder of Karad Infotech, a London-based agency specialising in web design, SEO, and software development for healthcare businesses across the UK.
Connect on LinkedInPankaj Karad
Founder & CEO
Pankaj Karad is the founder and CEO of Karad Infotech, a London-based digital agency specialising in web design, software development, and SEO for healthcare businesses. With extensive experience in pharmacy and dental clinic digital solutions, Pankaj leads the strategy and delivery of projects that help UK healthcare providers grow their online presence and patient bookings.
Visit website