How to Move WordPress to a Different Domain – A Practical Guide

Changing your domain is one of the riskier technical operations you can perform on a WordPress site – unlike a simple server migration, this one directly affects your visibility in Google. A poorly executed domain change can wipe out years of SEO work within days. In this article, we walk through the process step by step, minimizing the risk of losing traffic and rankings.

How a Domain Change Differs from a Regular Server Migration

With a server migration, the site's address (URL) stays the same – only the underlying infrastructure changes. A domain change is different: every URL across the site changes, which means Google has to "relearn" where your content now lives. Without the right steps – most importantly, 301 redirects – you risk losing rankings, organic traffic, and backlinks built up over years.

When a Domain Change Is Necessary

The most common reasons companies decide to change domains:

• company rebranding and a name change,
• consolidating several brands under one domain,
• moving from a temporary/testing domain to the final one,
• changing the domain extension (e.g. from .com.pl to .pl),
• merging two sites into one after a merger or acquisition.

Step-by-Step Process for Changing a WordPress Domain

1. Create a full backup – of files, the database, and the wp-content directory, before changing anything.
2. Set up a staging environment on the new domain – ideally protected from indexing, so you can test everything before switching production.
3. Update URLs in the database – every reference to the old domain (in content, settings, metadata) needs to be replaced with the new one, ideally using a search-and-replace tool that works directly on the database rather than editing individual posts by hand.
4. Update wp-config.php – the WP_HOME and WP_SITEURL values need to point to the new domain.
5. Configure DNS for the new domain – well in advance, so propagation has time to complete before you switch traffic over.
6. Deploy 301 redirects from the old domain to the new one – for every URL individually (1:1 mapping), not just blanket redirects to the homepage. This is the single most important step for protecting SEO throughout the process.
7. Update Google Search Console – add the new domain as a separate property and use the "Change of Address" tool to notify Google of the migration.
8. Update internal links – links within content, menus, and widgets should point directly to the new domain rather than relying solely on redirects.
9. Check the SSL certificate on the new domain – it needs to be active before switching traffic, otherwise visitors will see an "unsafe connection" warning.
10. Test everything after the switch – forms, payments (for a WooCommerce store), transactional emails, the admin panel, the sitemap.xml, and indexing in Google Search Console.

Common Mistakes When Changing Domains

• Blanket redirects to the homepage instead of 1:1 mapping – every article or page should redirect to its exact equivalent on the new domain, not to one generic address.
• Forgetting to update sitemap.xml – an outdated sitemap pointing to old addresses confuses search engine crawlers.
• Notifying Google Search Console too late – the sooner Google knows about the migration, the faster it transfers your earned authority to the new domain.
• Dropping redirects from the old domain too soon – 301 redirects should stay active for at least a year, ideally longer, to preserve traffic from outdated external links and bookmarks.
• Skipping payment and form testing after migration – especially critical for WooCommerce stores, where a configuration error can directly block sales.

Changing Domains on a WooCommerce Store – Extra Caution Required

If the site handles sales, there's added risk: payment integrations, webhooks, transactional emails, and syncs with external systems (ERP, CRM, marketplace) often have the old domain address saved in their configuration. Before switching over, check the settings of every payment gateway and integration individually – changing the address in WordPress alone won't automatically update the configuration on the external systems' end.

When It's Not Worth Doing Yourself

Changing the domain on a site with real organic traffic, a WooCommerce store with payment integrations, or a site generating regular sales inquiries is a situation where the cost of a mistake (lost rankings, interrupted sales, technical errors) usually far outweighs the cost of hiring specialists. This kind of migration should be planned like a full technical deployment – with a backup, staging, a cutover schedule, and post-migration monitoring, rather than a one-off task done "on the side."

If you're not confident you can carry this out safely on your own, it's worth reaching out to the WP Desk Care team – as part of ongoing technical support, they help with migrating sites to a different server and can advise on how to change domains as safely as possible without losing rankings or traffic.

Summary

Changing a WordPress domain is a process where protecting your established Google visibility matters most – precisely mapped 301 redirects, updating Search Console, and thorough post-migration testing determine whether the move goes smoothly or ends in lost traffic and rankings.

FAQ

Does changing domains always hurt SEO?

Ot necessarily, if the process is done correctly – with precisely mapped 301 redirects and the change reported in Google Search Console. Problems mostly arise from blanket redirects or a sitemap.xml that isn't updated.

How long should redirects from the old domain stay active?

It's recommended to keep 301 redirects active for at least a year, ideally indefinitely – they protect traffic coming from external links and bookmarks that still point to the old domain.

Do I need to report a domain change in Google Search Console?

Yes, it's worth using the "Change of Address" tool after adding the new domain as a property – this speeds up Google's re-evaluation and indexing process.

Does a WooCommerce store require extra steps when changing domains?

Yes – you need to check and update the configuration of payment gateways, webhooks, and integrations with external systems, which may still have the old domain address saved.

Does WP Desk offer help with moving a site?

Yes – as part of the WP Desk Care service (delivered technically by WordCare.eu), the team helps with migrating a site to a different server and with ongoing technical support. WP Desk also supports migrating entire stores from other platforms (e.g. Shoper, Shopify) to WooCommerce. If you're planning a domain change and want to make sure it goes smoothly, it's worth contacting the WP Desk Care team to discuss the scope of support for your specific case.