Site Migration Guide: DNS, HTTPS and SEO Redirect Checks

When migrating a site, copying the files to the new account is only one step. The database, application address, e-mail, scheduled tasks and old links are also part of the process. A plan that treats a hosting change and a domain name change separately reduces problems for both visitors and administrators.

What's in this guide?

• Define the scope of the migration
• Test the new environment before changing DNS
• Map URL changes one by one
• Update application addresses and DNS
• Monitor errors after launch

Define the scope of the migration

If the server changes but the domain name stays the same, the URL structure can be preserved. If the domain name or page paths change, the old and new addresses need to be mapped to each other. Make a list of files, databases, media, e-mail and integrations. For a site that takes orders or memberships, plan how new data created during the migration will be transferred.

Test the new environment before changing DNS

On the new server, check software versions, file permissions and the database connection. Keep your testing method separate from real visitor traffic. Test forms, login, search, the cart and notifications. Manage integration settings carefully to prevent notifications or payment transactions from being sent to real customers from the test environment.

Map URL changes one by one

Google’s site move guide covers redirecting changed URLs to the appropriate new addresses and updating site information. Instead of redirecting every old page to the home page, map each one to its topical equivalent. Use appropriate permanent redirects for permanent moves. Check for redirect chains and loops; do not add unnecessary redirects to a page that still exists.

Update application addresses and DNS

The base site address, internal links, canonical tags and sitemap should be consistent with the new structure. When changing the domain name inside the database, use a tool suited to the application's data format; a blind find-and-replace can break some settings. Verify DNS, the www preference and the HTTPS certificate together.

Monitor errors after launch

Check important old addresses, new pages and error logs. Monitor the relevant properties and the sitemap in Search Console. For a domain name change, consider the Change of Address tool where appropriate. There may be temporary fluctuations in search results; do not set expectations that guarantee a specific ranking or transition time.

Example of moving from a test area to the live domain

When a site is moved from a test subdomain to the main domain, old links in the footer, the logo and the admin panel can be overlooked. The check covers not only the home page but also menus, forms, automation addresses and e-mail templates. If test pages were previously indexed, an appropriate redirect plan is prepared; old addresses are not left publicly accessible without control.

Practical checklist

• Make an inventory of files, databases and integrations.
• Test critical flows before changing DNS.
• Map changed URLs to their correct equivalents.
• Check canonical tags, the sitemap and old links.

Frequently asked questions

Is SEO affected if the hosting changes but the domain name stays the same?

Accessibility, speed and the technical setup matter. Preserving URLs and testing the migration properly reduces unnecessary problems.

Is it enough to redirect all old addresses to the home page?

Mapping each page to its relevant equivalent is a more accurate migration plan. Evaluate the status of deleted content separately.

Related guides

• DNS Propagation and TTL: Why Don't Changes Appear for Everyone at the Same Time?
• Domain Name Transfer: A Migration Plan for Your Website and Email
• How to Check an SSL Certificate and the “Not Secure” Warning

Technical reference: Google Search Central Site Move Guide. Check the current official documentation for product and version details.

Contact us about a site migration plan →