Rebuild the experience with a clear transition plan.

Record the pages and journeys that matter

Build an inventory of current URLs, important service pages, useful resources and contact routes. Include pages people reach from search, advertising, business profiles and external links. Save a baseline of available search and lead data so later comparisons have context. The goal is to make deliberate decisions about existing value, even when the new site will have a different structure.

Review the content with the people who deliver the service. Mark what remains accurate, what needs rewriting and what should be retired. A fresh design is an opportunity to remove confusing navigation and unsupported claims. It should also preserve the practical explanations that already help customers decide whether the business can meet their needs.

Map the new structure before polishing the design

Choose a canonical page for each major service and distinct customer need. Define how service, city and guide pages connect, then write a direct mapping for old URLs that have relevant replacements. Google’s migration guidance recommends permanent server redirects and warns against sending unrelated old URLs to a single destination. Keep the destination meaningful to the visitor.

Plan honest 404 or 410 responses for content with no suitable replacement. Check internal links, canonical URLs and sitemap entries against the new structure. If separate language versions exist, include them in the transition plan. Avoid leaving these decisions until launch day, when a missing page can be harder to distinguish from a hosting problem.

• Map relevant old URLs directly to their new destinations.
• Confirm each canonical page has a clear purpose.
• Record intentional removals and check their response codes.

Verify the candidate before public activation

Use a preview to review the actual generated pages on desktop and mobile. Check navigation, readability, image sizing and keyboard access. Confirm that search engines are prevented from indexing the preview and that its pages identify the intended production URLs. A preview should not quietly collect real enquiries that the team cannot retrieve.

Test the application’s failure states as well as the happy path. A visitor should receive a clear outcome if a form cannot connect, and a retry should not create multiple leads. Check that chat is clearly identified, that an informal conversation is not presented as a submitted enquiry and that the person reviews contact details before sending them.

Treat the launch as a complete service check

After activation, open the public domain independently and confirm that it serves the intended release. Test important pages, redirects, the sitemap, robots instructions and the preferred hostname. Check that production pages can be indexed and that the preview remains separate. Google’s guidance also calls for updating internal links and canonical references when URLs change.

Run a clearly labelled controlled enquiry through the public form and verify the record reaches the intended team. Distinguish a saved lead, an email accepted by a provider and an email actually delivered. Review analytics only under the site’s consent choices, and ensure event payloads do not include the visitor’s private message or contact fields.

Review the transition after launch

Keep a launch log describing the release, major URL changes, known limitations and follow-up owners. Monitor important pages for access or indexing problems and review broken destinations that real visitors reach. Search engines need to process changes, so avoid treating every short-term movement as proof that a specific design choice succeeded or failed.

Use the baseline to ask focused questions. Did a valuable page disappear? Are new visitors reaching the correct service? Did a mobile form become harder to use? Prioritize problems that interrupt a real journey, then evaluate broader content improvements. A clean launch is the beginning of measurement, not evidence that a new site has already achieved its ranking goals.