Domain change is a different project from a host move
A host move keeps every URL the same and changes only where the domain points. A domain change rewrites every URL members, search engines, payment providers and old emails know about. Google's site move guidance treats it as a move with URL changes and warns that the visibility of your content in Search may fluctuate temporarily during the move.
For course and membership sites, the list of things that hold the old URL is long: bookmarks to lessons, links inside past receipts and renewal reminders, password reset emails already in inboxes, links in course PDFs, the Stripe webhook endpoint, OAuth or single sign-on callbacks, and affiliate or partner pages. Redirects cover most of these, but not all of them, so the plan needs an inventory before any switch.
Build the redirect map
Google says it's important to map your old site's URLs to the URLs for the new site, and recommends server side permanent redirects from the old URLs to the new URLs, using HTTP permanent redirects such as 301 and 308 where possible. It advises keeping the redirects for as long as possible, generally at least 1 year.
If the path structure stays the same and only the hostname changes, the map can be a single rule that preserves the path and query string. If you are restructuring at the same time, export every published URL from the old site, including lessons, course landing pages, membership pricing pages and account pages, and map each one. Change the internal links on the new site to the new URLs, as Google recommends, rather than relying on redirects internally. For the database side, see the URL search-replace rehearsal guide; WordPress's own migration documentation warns never to change the contents of the GUID column, and that a blind database-wide search and replace can cause issues with data serialization.
Search Console Change of Address: requirements
Google says that if you're changing domain names, submit a Change of Address in Search Console for the old site. The tool has specific requirements, listed below. It is not needed for HTTP to HTTPS moves or for switching between www and non-www.
- Submit the new sitemap in Search Console, as Google recommends.
- Remove any noindex or robots.txt blocks that were only needed for the migration.
| Requirement or limit | What Google documents |
|---|---|
| Ownership | You must be an owner of both the old and new properties in Search Console |
| Property type | Can be used only on properties at the domain level |
| Path-level properties | Cannot move properties at the path level, such as http://example.com/petstore/ |
| Subdomains | Does not move any subdomains below the specified domain (including www) |
| Redirect | Implement a 301 redirect from your old homepage to your new homepage |
| Duration | Notifications shown for 180 days; maintain redirects for at least 180 days, longer if Google Search still sends traffic |
| Not for | Changing address from http to https |
Members, logins and payments
WordPress sets a wordpress_logged_in_[hash] cookie after login, and its cookie documentation advises that after moving a website you should try deleting cookies if login problems appear. Plan for every member to log in again on the new domain, and tell them in advance. Send the notice from the new domain's mail setup, link to the new login page, and make sure password reset works there before you send it.
Do not count on redirects for payment notifications. Stripe treats redirect responses to webhook requests as failures, so the webhook endpoint must be updated to the new domain; the Stripe webhooks guide covers MemberPress and WooCommerce steps. Also update any return URLs, success pages and customer portal links configured in the payment provider.
Email links already sent will point at the old domain. Redirects handle those only if the old domain keeps resolving and serving redirects, which means keeping the old domain registered and its DNS active for the life of the redirects.
Sequence for the switch
- Inventory every place the old domain appears: site content, plugin settings, payment provider, email templates, external integrations.
- Build and test the redirect map on staging; check that lesson URLs, account pages and query strings redirect correctly.
- Verify both domains as domain-level properties in Search Console with the same Google account.
- Switch: update WordPress site URLs, enable the redirects, update payment webhooks and return URLs.
- Submit Change of Address for the old property and the new sitemap.
- Tell members about the new address and the need to log in again; keep the old domain renewed and redirecting for at least a year.
Questions before you decide
How long should I keep the old domain redirecting?
Google's site move guide says generally at least 1 year, and the Change of Address help says at least 180 days, longer if Search still sends traffic. Old emails and bookmarks are a reason to keep them much longer.
Can I use Change of Address when moving from www to non-www?
No. Google says the tool is not needed for www or non-www switches or HTTP to HTTPS moves, and that it does not move subdomains below the specified domain.
Sources & verification
Product details and prices can change. Check the linked provider before buying.
- Google Search Central: Site moves with URL changes Accessed 13 Oct 2026
- Google Search Console Help: Change of Address tool Accessed 13 Oct 2026
- WordPress Advanced Administration: Cookies Accessed 13 Oct 2026
- WordPress Advanced Administration: Moving WordPress Accessed 13 Oct 2026
- Stripe Docs: Receive Stripe events in your webhook endpoint Accessed 13 Oct 2026
Sources link directly to providers. Product buttons may use separately labeled affiliate links. Read our disclosure.