Website redesign projects often begin with visual goals: a more modern interface, better mobile layout, new brand positioning or an easier content-management system. SEO risk appears when teams treat the existing site as disposable.
If a current page already ranks, earns links or generates enquiries, its URL and content carry value. A redesign should preserve that value wherever possible, then improve the experience around it.
1. Crawl the existing website before changing it
Create an inventory of indexable URLs, titles, headings, canonicals, response codes and internal links. Combine this with Search Console and analytics data so you know which pages receive organic traffic, impressions, conversions or backlinks. The redesign team should not decide which URLs matter based only on navigation visibility.
2. Decide which URLs will be preserved
If a page still serves the same intent, preserving the existing URL is often safer than changing it for cosmetic reasons. When a URL must change, map the old page to the closest relevant new page. Avoid redirecting every removed URL to the homepage.
3. Build a redirect map before launch
Prepare one-to-one 301 redirects for changed URLs. Check for redirect chains and loops, and make sure internal links point directly to the new destination instead of relying on redirects forever. Product and category migrations may require larger automated maps, but they should still follow relevance.
4. Preserve or improve successful content
A redesign sometimes reduces copy because the new layout looks cleaner. That can remove the very detail helping a page rank. Compare old and new content before launch. If text needs to be shortened, keep the important service information, definitions, local context, FAQs and internal links that satisfy search intent.
5. Rebuild metadata intentionally
Titles and meta descriptions should not disappear when templates change. Preserve strong metadata or improve it based on current keyword mapping. Make sure pages do not accidentally share the same title or receive generic sitewide descriptions.
6. Check heading structure
Each page should have a clear primary heading that reflects its purpose. Avoid turning every decorative component into an H2 or skipping heading levels simply for styling. CSS should control appearance; headings should describe document structure.
7. Verify canonical tags and robots directives
Staging sites are often set to noindex. That is correct during development, but the noindex directive must be removed from production at launch. Canonical tags should reference the intended live URL, not the staging domain or an old hostname.
8. Review XML sitemaps
The new sitemap should include canonical, indexable URLs and exclude redirects, errors and noindex pages. Submit or refresh it in Search Console after launch. Do not rely on the sitemap to compensate for weak internal navigation.
9. Test mobile UX and Core Web Vitals
Large hero videos, unoptimised images, animation libraries and page builders can make a redesign slower than the old site. Test realistic mobile conditions. Prioritise the largest visible content, avoid unexpected layout shifts, and delay non-essential scripts where practical.
10. Keep conversion tracking intact
Forms, phone links, ecommerce events and thank-you flows can change during a rebuild. Update GA4, Google Tag Manager and ad-platform conversions before launch so performance reporting does not break at the same moment the website changes.
11. Test structured data
If the old site uses valid schema, make sure useful markup is not dropped. If the new site adds schema, it should describe visible content accurately. Do not add fake reviews, unsupported LocalBusiness locations or FAQ schema for questions that are not present on the page.
12. Run a full pre-launch crawl
Crawl the staging or pre-production site and look for missing titles, duplicate metadata, broken links, placeholder pages, orphaned URLs, missing images, unexpected noindex directives and canonical mistakes. Compare the crawl with the old-site inventory.
13. Monitor immediately after launch
Check server logs or crawl behaviour where available, Search Console coverage, top landing pages, redirects, 404s, rankings and conversion tracking. Some fluctuation can occur after a migration, but unexpected losses should be investigated quickly.
14. Avoid changing everything at once when it is not necessary
A redesign already changes templates, code and UX. If possible, avoid simultaneously changing every URL, rewriting all content, moving domains and replacing the analytics stack unless there is a clear reason. Fewer simultaneous variables make problems easier to isolate.
Website redesign SEO checklist summary
| Area | Before launch | After launch |
|---|---|---|
| URLs | Inventory, preserve, map changes | Test 301s and 404s |
| Content | Compare old vs new, protect intent | Check indexation and rankings |
| Technical SEO | Canonicals, robots, sitemap, schema | Search Console and crawl QA |
| Performance | Mobile speed and Core Web Vitals | Real-user monitoring |
| Tracking | Update events and conversions | Verify forms, calls and sales |
Our web design services include SEO migration planning when a redesign involves existing search visibility. This is one of the main advantages of keeping design, development and SEO in the same delivery process.