A website redesign can improve usability and brand presentation, but it can also remove valuable content, change URLs and break the signals search engines rely on. SEO should be included from planning through post-launch monitoring, not added after the new site is live.
Use this checklist to connect a website redesign with the organic visibility the existing site has already earned.
Benchmark the current website
Before changing anything, export indexable URLs, organic landing-page performance, conversions, backlinks, rankings and crawl data. Record important templates and navigation paths. This baseline makes it possible to identify losses and verify improvements after launch.
Create a complete URL inventory
Combine crawl data, XML sitemaps, analytics, search-platform reports and backlink sources. No single source will contain every useful URL. Classify each page as keep, improve, consolidate, redirect or retire.
Protect pages that generate qualified visits, links or important customer information even when their visual design feels outdated.
Plan the new information architecture
Organise services and resources according to customer needs. Important pages should be reachable through logical navigation and contextual links. Avoid hiding valuable content behind internal search or interactive controls alone.
A pre-launch SEO audit can reveal architecture and indexation risks before they are built into the new system.
Preserve strong content and metadata
Do not replace useful, established copy with short placeholder text. Transfer page titles, headings, body content, image alternatives and structured data where they remain accurate. Improve content deliberately, with clear ownership and review.
Map redirects page by page
When a URL must change, redirect it to the closest relevant new destination. Avoid routing every removed page to the home page. Test the map for loops, chains and destinations that will not exist at launch.
Keep redirects in place long enough for users, search engines and external links to transition.
Control the staging environment
Prevent staging pages from being indexed, but do not rely on robots blocking as the only security measure. Use access controls. Before launch, make sure staging restrictions and noindex rules will not be copied accidentally to production.
Test technical SEO before release
Crawl the staging site and check status codes, canonicals, robots directives, sitemaps, structured data, hreflang where used and internal links. Compare the old and new inventories. Confirm that important content is available in crawlable HTML.
Validate performance and mobile use
Test representative templates on real devices and slower connections. Optimise images, fonts and scripts. Check forms, menus, cookie controls and interactive elements with keyboard navigation. A redesign should improve experience without making core pages slower or harder to use.
Preserve analytics and conversions
Carry forward campaign parameters, event definitions and consent behaviour. Test every important conversion in the production environment. A controlled analytics setup helps teams distinguish a traffic change from a tracking failure.
Monitor closely after launch
Crawl the live site immediately, submit the new sitemap and review errors, indexation, organic landing pages and conversions. Check redirect logs and repair missed URLs. Expect some fluctuation, but investigate large or persistent losses by page group.
A successful redesign preserves what already works while improving the structure and experience for future growth.