{"id":2115,"date":"2026-08-03T06:33:12","date_gmt":"2026-08-03T06:33:12","guid":{"rendered":"https:\/\/gigatech.nl\/move-website-without-downtime-seo-loss\/"},"modified":"2026-08-03T06:33:12","modified_gmt":"2026-08-03T06:33:12","slug":"move-website-without-downtime-seo-loss","status":"publish","type":"post","link":"https:\/\/gigatech.nl\/en\/move-website-without-downtime-seo-loss\/","title":{"rendered":"Move a website without downtime or SEO loss: a practical migration guide"},"content":{"rendered":"

Moving a website involves more than copying files and changing a domain record. The site may depend on email, forms, scheduled jobs, external APIs, payment providers, DNS records and search indexing. Careful preparation can make the transition almost invisible. Without a plan, migrations cause missing orders, errors, duplicate content or a drop in organic traffic.<\/p>\n

\"Stappenplan<\/figure>\n

Start with a complete inventory<\/h2>\n

Record every domain and subdomain, the DNS zone, mailboxes, databases, PHP version, scheduled jobs, SSL certificates, redirects and external integrations. Check how much storage is genuinely used and whether large archives or old backups should be left behind. A migration is a useful time to remove unnecessary baggage.<\/p>\n

Create a staging copy first<\/h2>\n

Copy files and the database into the new environment and test through a temporary address or local hosts entry. Keep staging out of search engines with authentication or a clear noindex directive. Test sign-in, forms, email, images, permalinks, basket behaviour, payments and background tasks.<\/p>\n

The new environment may use different PHP versions, modules or security rules. Resolve compatibility issues before the public cutover, not during the busiest hour.<\/p>\n

Lower the DNS TTL in advance<\/h2>\n

TTL defines how long resolvers may cache a DNS answer. Lower the relevant values a day before migration so the final change is adopted more quickly. Not every cache follows the value immediately, so expect a transition period in which visitors may reach either server.<\/p>\n

Plan the final synchronisation<\/h2>\n

For a static website, the first copy may be enough. A shop, forum or membership site keeps changing. Plan a short content freeze or maintenance window, perform a final database and uploads sync, and then switch DNS. This prevents orders or comments from remaining only on the old server.<\/p>\n

Protect SEO signals<\/h2>\n

If only the hosting changes, URLs should remain the same. Verify canonicals, robots.txt, XML sitemaps and status codes. If the structure or domain also changes, create a one-to-one redirect map using permanent 301 redirects. Do not send every old URL to the homepage; that removes relevance and hides mistakes.<\/p>\n