Start with the pages that already bring visitors.
In Search Console, review the pages and queries that receive impressions and clicks. In your analytics tool, check landing pages and the actions visitors complete. Use both views: a page with little traffic may still explain a service that produces useful inquiries.
Save the page URLs, titles, main content, and contact actions. Note external links and downloads you need to keep. Decide which pages will remain, which will be improved, and which are no longer useful. Do this before choosing a new navigation menu.
Make a URL map before you publish.
For every important old URL, record the intended new destination. Keep a working URL when there is no reason to change it. If it changes, confirm that the host or platform responsible for the old address can redirect it to the relevant new page.
A redesign preview does not configure all legacy redirects for you. Identify who will set them up and test the result. Avoid sending unrelated old service pages to the homepage by default; use a destination that answers the same customer need.
| Old page | Planned action | Launch check |
|---|---|---|
| A useful service page | Keep the URL or map to its replacement | Page loads and explains the service |
| A changed page address | Configure a permanent redirect | Old address reaches the relevant new page |
| A removed offer | Decide whether a relevant replacement exists | No misleading or broken internal links |
| A booking or download link | Preserve or replace the destination | The customer can complete the action |
Check what a crawler and a visitor receive.
Public pages should load at the intended URL, describe their own content, and be available for indexing. Check for accidental noindex directives, blocked pages, incorrect canonical URLs, or links to a staging domain. Make sure the sitemap lists the public pages you want discovered.
Review the rendered page as well as its metadata. Keep headings readable, image descriptions accurate, and internal links descriptive. Structured data should reflect facts visible on the page. It does not substitute for clear content or guarantee an enhanced search result.
Watch the move with a recorded baseline.
After launch, check important old and new URLs, submit or confirm the sitemap in Search Console, and test forms on the live domain. Watch indexing reports and investigate missing destinations. Google notes that ranking fluctuations can happen while it recrawls and reindexes changed sites.
Keep search and conversion questions separate. More impressions do not necessarily mean more suitable customers; a form submission is not necessarily a sale. Compare landing pages, search queries, and qualified inquiries over time, and record the date of the redesign so changes have context.
Keep this list handy
Before the domain switch
- Record search landing pages and useful customer actions.
- Map old URLs to their intended destinations.
- Confirm who will configure and test redirects.
- Review titles, canonicals, robots rules, and sitemap URLs.
- Test the live contact journey and monitor after launch.
Sources and further reading
- Google Search Central: site moves and URL changes
- Google Search Central: sitemap guidance
- Google Search Central: redirects and search
- Google Search Central: canonical URLs
Reviewed November 3, 2026.
