Website Redesign SEO Checklist: Protect Traffic and Improve the New Site

1. Record what works before changing the site

Export a list of live URLs, titles, headings, canonical URLs and internal links. Use Google Search Console to find pages with clicks and queries, analytics to see engaged traffic and leads, and your own sales records to identify pages that bring qualified enquiries. Note pages with valuable links from other sites. A page that looks old may still be doing important work.

Decide whether each page will stay, be improved, merge with another page or be retired. Write down the reason. This turns the redesign into a measured project and helps you avoid deleting a useful article or service page because it no longer fits a visual template.

2. Plan the new structure and URL map

Give each important service a clear destination. Keep existing URLs when they already describe the right topic. When a URL truly needs to change, pair the old address with the closest relevant new one in a redirect map. Do not send every old article to the homepage; a visitor expecting an answer should land on a page that supplies it.

Use descriptive navigation and contextual links so a person can move from a guide to a relevant service and then to contact. A redesign is a good time to repair disconnected articles and confusing menus, but each link should serve a reader. Motif Design's website design service plans navigation and content paths alongside layout.

3. Build pages that answer real questions

Retain facts, examples and proof that make your best pages useful. Rewrite thin or outdated material where there is a clear reader need. Give each page one purpose, a helpful title and descriptive headings. A service page should explain what is included, who it helps, where it is offered and how to enquire.

Clear organization can also help search and answer systems interpret your content. Add structured data only where it accurately reflects visible information. For an AI search perspective, see the AI SEO audit checklist and our technical SEO service.

4. Test the staging site before launch

• Review layouts on phones and desktops, including readable text and usable navigation.
• Test contact forms, confirmation messages, phone links and email delivery.
• Verify titles, descriptions, headings, image text and canonical tags on the final templates.
• Confirm important pages can be crawled and that preview URLs will not become the canonical public pages.
• Check page speed and Core Web Vitals as part of the overall experience, especially heavy images and unnecessary scripts.
• Check tracking and consent behavior where applicable so leads can be measured after launch.

Google says its ranking systems use Core Web Vitals but a good score alone does not guarantee top rankings. Test the actual experience and the complete path to enquiry.

5. Launch with redirects and clear signals

Publish the new site and test every important old URL. Use permanent server-side redirects for pages that moved, pointing to the most relevant replacement. Update internal links so they go directly to the new URLs. Check that canonical tags, the XML sitemap and robots directives describe the public site, not the staging site. If the domain itself changed, follow the additional steps in Google's site migration guidance.

A change of design or platform on the same domain still deserves careful URL and content checks. Domain migration steps apply when the hostname changes. Google recommends planning redirects and watching both the old and new URLs during a move; its redirect documentation explains the supported methods.

6. Watch performance after launch

In the first days, check the live site, forms, analytics, mobile pages and key redirects. Review Search Console indexing and crawl issues, and compare queries and landing-page traffic with the baseline. Allow time for search engines to recrawl changes, and investigate sustained losses by page rather than assuming every variation is caused by the redesign.

Keep the redirect map and measurements with the project. If the new site is receiving traffic but fewer leads, examine the contact journey, calls to action and forms. If a former top page has disappeared from search, check its redirect, replacement content, indexability and internal links first.

A short decision checklist for the project team

• Which pages currently earn clicks, links or enquiries?
• Which URLs remain, and where does each changed URL go?
• Does every key service have a useful page and contact path?
• Are staging restrictions removed only from the live site?
• Do redirects, canonicals, internal links and the sitemap agree?
• Are forms, tracking, mobile usability and page speed tested?
• Who checks Search Console and leads after launch?

Frequently asked questions

Will a website redesign automatically improve SEO?

No. Better structure, content and performance may help, but changing the design alone does not guarantee higher rankings. Protect useful existing pages and test the launch.

Should all old URLs redirect to the homepage?

No. Redirect a changed URL to the most relevant replacement. A blanket homepage redirect can confuse visitors and discard the context of the original page.

Can we keep the current URLs on a new platform?

Often, yes. Keeping useful URLs can simplify the move. If the platform requires changes, map old URLs to relevant new pages and test the redirects.

What should I check immediately after launch?

Test key pages, old URL redirects, forms, tracking, canonical tags, indexability, sitemap entries and the mobile experience. Then monitor Search Console and qualified leads.