Change hosting and domain without losing SEO: migration guide

Published on 2026-11-14 by frfrand

Checklist for 301 redirects, canonical tags, internal links, DNS, sitemaps, and Search Console tracking when migrating a website.

# Change hosting and domain without losing SEO: migration guide

A poorly planned migration can turn hundreds of ranked URLs into 404 errors. Changing servers without changing URLs is not the same as changing domains: separate the two scenarios and avoid introducing unnecessary modifications.

1. Take an inventory before touching DNS

Export from Search Console the pages with clicks and impressions; record landing pages, titles, canonicals, important backlinks, paths, language, HTTP status, and sitemap. Create a table with old URL → new URL → expected response type. Save a working copy of files and databases. Also review forms, email, payments, and scheduled processes.

2. If you only change hosting

Keep domain, paths, content, tags, structure, and protocols. Deploy on a new server, check the website with a protected test domain or local hosts resolution without accidental indexing, prepare TLS certificates, and validate dependencies. Lower the TTL before the change when appropriate. Update DNS only after verifying the new hosting. You do not need new redirects or the change of address tool if public URLs do not change.

3. If the domain changes

For each old URL with a real equivalent, create a direct permanent 301 or 308 redirect to the corresponding destination. Do not redirect all pages to the home page; irrelevant correspondences can be considered soft 404s. Keep the old domain and its redirects operational for an extended period.

Illustrative Nginx example only for full host change:

server {
    listen 443 ssl;
    server_name antiguo.ejemplo.com;
    # Configura certificados válidos y directivas TLS.
    return 301 https://nuevo.ejemplo.com$request_uri;
}
This only works if all routes keep the same path and query string; if they change, create specific rules before a general rule.

4. Canonical, sitemap, and internal linking

On the new site, each page should use a canonical tag for its own preferred URL. Update internal links, menus, images, structured data, hreflang tags, open graph, and sitemap. Verify that noindex used in staging has disappeared. Submit the new domain's sitemap to Search Console and verify properties for both domains. For a compatible domain or subdomain migration, use Change of Address in Search Console; it does not apply to all protocol or path changes.

5. Testing plan

curl -I https://antiguo.ejemplo.com/ruta
curl -IL https://antiguo.ejemplo.com/ruta
curl -I https://nuevo.ejemplo.com/ruta
Verify origin 301 code, absence of long chains, and 200 at destination. Sample high-traffic pages, 404 errors, and loops; check login and API separately. If there are database writes, plan synchronization and a cutover window to avoid losing changes.

6. Tracking and rollback

Observe coverage, clicks, impressions, queries, and server logs by URL. A temporary transition is normal, but a persistent drop with 404s or incorrect canonicals requires correction. The rollback must include web, database, and DNS; do not revert production data without analyzing subsequent writes.

Related: migrate the Lovable domain and DNS diagnosis with dig. ArduMaker allows approaching the transfer as a controlled technical operation, not a simple file copy.

Frequently asked questions

Do I lose SEO if I only change IP? Not necessarily; keep URLs and availability. Does a 301 guarantee maintaining rankings? No; it minimizes errors, but positioning may vary. Should I let the old domain expire? No, as long as it is necessary to serve redirects.

Sources: https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes ; https://support.google.com/webmasters/answer/9370220

  • migración web
  • SEO
  • DNS
  • redirecciones 301
  • Search Console

Keep reading

All articles · VPS plans