Migrate a website with redirects

Preserve the starting point

Before moving, list your existing pages, files and important external links. Use the menu, sitemap and available traffic information to find overlooked pages. Keep a copy of the old website and retain access to the domain and hosting. Record services that operate separately, including email, forms and appointments. A new design does not automatically replace that infrastructure. Agree who makes content decisions and who performs the technical switch so that a missing dependency does not emerge only on launch day.

• Keep existing content and a complete URL inventory.
• Identify domain, hosting and email administrators.
• List forms, downloads and external services.

Choose a relevant destination for each URL

Keep existing URLs when there is no good reason to change them. Where an address must change, map it to a new page serving the same subject and purpose. Do not send every old service page to the homepage. For content that genuinely disappears without a suitable replacement, agree the appropriate handling with your maintainer. Use a simple list of old URL, new URL and action. Check capitalisation, trailing slashes and language versions before anyone generates the configuration.

Test before changing the live destination

Finish the new content and test links between its pages. Flova export includes correct relative page links, while images and fonts still depend on online Flova resources. Pilot publication under /sites carries noindex. Separately agree how the production host handles files, the domain, HTTPS and indexability. Check contact and booking journeys using the external services responsible for them. The pilot does not provide automatic migration or establish that a visible form delivers messages. Include a practical rollback plan before changing the live destination.

• Compare every important old page with its replacement.
• Test menus, downloads and contact options.
• Agree a rollback procedure before changing domain configuration.

Configure redirects where requests arrive

Have the maintainer configure permanent server redirects on the system that receives requests for the old URLs. The exact configuration depends on your host. Test every mapping: the old address should reach the intended new page without a loop or unnecessary intermediate steps. Update internal links and canonical references to use the new addresses as well. A canonical indicates a preferred version; it does not automatically move a visitor in the way a redirect does. Keep these two responsibilities distinct in the handover.

Monitor after the switch

After migration, regularly check missing pages, incorrect destinations and Search Console reports. Update business profiles and important external links where possible. Keep the old domain and redirects available rather than disabling them after the first successful test. Google explains that processing a site move takes time and visibility may fluctuate. A careful migration plan cannot guarantee positions or prevent every possible decline. Review technical faults, content changes and changes in demand separately so that follow-up decisions address evidence instead of assuming one cause.

• Retest important old URLs after launch.
• Monitor indexing reports and missing pages.
• Keep a dated record of fixes and their owners.