Malcolm Keith 2026 
You can migrate an affiliate website to a new domain with less disruption by preserving your content, redirecting every valuable URL, and testing your tracking. But nobody can promise zero ranking movement during a domain migration.
Your goal is to protect traffic and commissions, not simply get the new homepage working. Now, let’s get the move organized before you change anything visitors or Google can see.
Key Takeaways About Domain Migration
- Keep your content, layout, and URL paths stable while changing domains.
- Use direct, permanent 301 redirects to matching pages, and retain them for at least a year.
- Update internal links, canonical tags, sitemaps, Search Console, and analytics.
- Test affiliate IDs and SubIDs through the complete visitor journey.
- Expect ranking fluctuations, and monitor search visibility separately from confirmed commissions.
Personal Side Note
I should say that I have my other domain migration done for me when I joined the Home Business Academy. The Domain Scout is a built-in tool in The Home Business Academy (HBA) that suggests and registers personalized domain names for your affiliate funnels. It suggests customized domain names based on your first name or brand so your affiliate links look professional rather than sharing long, raw URLs with numbers and symbols
Because I am a committed member of HBA I took it further by adding a custom domain-connected email address to use with marketing campaigns and autoresponders.
The best bit is purchased domains can be connected directly to the HBA funnel builder so you can launch pages using pre-made templates or AI builder tools. The domain is automatically set up with SPF, DKIM, DMARC and all the pre-propagation records in place for you at the press of a button. No tech knowledge or actions needed by you.
Plan Your Domain Migration Before Touching DNS
Record what already brings results
Start with a spreadsheet of your existing URLs, then export the inventory as a CSV for URL mapping and redirect checks. Screaming Frog SEO Spider can crawl the site, but add URLs from your sitemap, Search Console, analytics, and backlink reports too.
For each page, record its organic traffic, backlinks, canonical target, indexability, proposed destination, and reason for that decision. Add affiliate clicks and network-reported commissions where your tracking supports them.
Save at least 28 days of baseline data. Compare similar weekdays, and include last year’s figures if your offers are seasonal. Your busiest reviews and comparison pages deserve attention first.
Keep the move focused
My advice is simple: change the domain without redesigning the whole business at the same time.
Keep your page content, navigation, templates, and URL paths stable where possible. Google’s site-move guidance recommends changing one thing at a time.
Before using the destination domain, review its history, especially if you got it through a business acquisition or it had a previous owner. Check its Search Console Manual Actions and Security Issues reports for problems you didn’t create.
Also, back up your files and database, then test the backup and restore process to confirm you can recover them. A backup you can’t restore won’t help much on launch day.
Build the New Site Without Breaking What Pays
Get the technical basics ready
Copy the website to the new hosting environment, install HTTPS, and test it before sending visitors across.
Keep staging private. If you use noindex during preparation, remove it from pages intended for search when they go live. Don’t remove deliberate exclusions from ad-only landing pages.
Update canonical tags, structured-data URLs, navigation, images, forms, and internal links to the new domain. Your indexable pages should return a 200 response and declare their own new canonical address.
Review your affiliate website robots.txt rules too. Google needs access to the new content and the old redirects.
Follow the affiliate click all the way through
Now, test what earns the money.
Open your priority reviews on desktop and mobile. Click comparison-table links, buttons, and text recommendations. Confirm that the expected affiliate ID, SubID, and tracking parameters survive each redirect.
Keep disclosures visible and retain appropriate rel="sponsored" attributes. Update the website address in affiliate accounts, and complete any required domain approval before launch.
Use program-approved testing rather than self-referral purchases. A working button proves someone can click. It doesn’t prove the merchant credited a sale.
Set Up Page-to-Page 301 Redirects
Send each visitor to the matching destination
A permanent 301 redirect tells users and search engines that a page has moved. Google’s redirect documentation explains how permanent redirects help identify the preferred destination.
Use your URL inventory to decide the correct treatment.
| Existing page situation | Destination rule | Response |
|---|---|---|
| Same content and path | Matching path on the new domain | 301 |
| Path has changed | Exact replacement page | 301 |
| Content was consolidated | Closely matched replacement | 301 |
| Removed with no useful replacement | No unrelated destination | 404 or 410 |
Don’t send every retired review to your homepage. That gives buyers the wrong page and can be treated as a soft 404.
Keep the route short and preserve parameters
For a domain-only move, a host-level redirect can preserve the original path. Add individual rules wherever paths differ.
Every old variation should reach the final HTTPS destination directly. Include HTTP, HTTPS, www, and non-www versions. Avoid chains that bounce visitors through several intermediate addresses.
Preserve legitimate campaign parameters and tracking IDs. Don’t let a broad redirect rule strip the information your affiliate tracker needs.
An old HTTPS link needs a valid certificate before the server can deliver its redirect. Keep the old domain’s HTTPS working too.
Test the full mapping, not just the homepage. The destination should return its intended response without loops.
Connect Search Console and Analytics Before Launch
Tell Google where the website moved
Verify both domains in Google Search Console, and keep ownership verification active. My Search Console setup guide covers the starting setup.
Once redirects are live, use Google’s Change of Address tool in the old property’s settings. This supports the domain change; it doesn’t replace redirects.
Submit the new XML sitemap with canonical, indexable URLs. Leave out redirected addresses, errors, and deliberately noindexed pages.
Inspect the homepage and your strongest affiliate pages. The live test shows current accessibility. The indexed report shows Google’s selected canonical, which may take time to change.
Keep your measurement history connected
For the same website under a new domain, retain your existing GA4 property and web stream to preserve reporting continuity.
Update the stream’s website URL and any domain-dependent Google Tag Manager triggers, filters, referral settings, or consent configuration. Test page views and affiliate-click events in DebugView.
Record the launch date in your reporting log. Keep event names and placement labels consistent so pre-move and post-move comparisons remain useful.
GA4 measures configured website activity. Your affiliate network remains the source for approved sales, reversals, and cleared commissions.
Work Through This Launch Checklist
Before you migrate traffic, complete these cutover steps in order:
- Save tested backups, baseline reports, and the final old-to-new URL map.
- Publish the new site with working HTTPS, correct canonicals, and intended indexing directives.
- Activate redirects and crawl the old URL list to test every destination.
- Update internal links and sitemaps, then submit the Search Console address change.
- Test forms, consent controls, analytics events, affiliate links, and mobile navigation.
If you use WordPress, a database search-and-replace must handle serialized data safely. Don’t replace your website’s domain inside merchant URLs or tracking configurations without reviewing what those values do.
Finally, update controlled links in ads, emails, social profiles, and business listings.
Monitor the Move on a Realistic Timeline
Google processes a domain migration page by page. Smaller and medium-sized sites may take a few weeks for most URLs to move. Larger sites can take longer.
Use a schedule that catches faults without encouraging daily guesswork.
| Period | Main checks |
|---|---|
| First 24 hours | Availability, HTTPS, redirects, crawl access, forms, tracking |
| Days 2 to 7 | Daily checks for errors, missing events, broken offers, and indexing changes |
| Weeks 2 to 6 | Weekly comparisons of combined search traffic, priority pages, clicks, and commissions |
| Months 2 to 12 | Weekly reviews until stable, then monthly crawls and redirect checks |
Add old-domain and new-domain Search Console clicks together when assessing the transition. Falling clicks on the old property are expected when the new one gains them.
For a valuable review that drops, inspect its old redirect, new response, canonical, internal links, and affiliate destination first. Compare the same query, country, and device before rewriting the content.
Separate organic visitors, outbound affiliate clicks, pending sales, approved sales, and cleared commissions. Match date ranges and time zones. Reporting delays and refund windows can explain gaps.
Fix broken redirects or accidental noindex immediately. Ranking movement alone isn’t a reason to reverse the move.
Keep redirects for at least one year, preferably longer. Renew the old domain and retain a working redirect service.
Avoid the Mistakes That Hide Behind a Working Homepage
A homepage loading correctly doesn’t mean the migration worked. Users may still arrive through old backlinks and reach deep review pages, images, or downloads that return errors.
Another common problem is leaving internal links pointing through the old domain. Replace those links with final destinations. Then crawl again to find orphan pages that lost their place in your navigation.
Don’t block the old site in robots.txt. Google needs to crawl old URLs to discover their redirects. Also, don’t leave two indexable copies of the website live.
Finally, don’t change your theme, offers, content, tracking system, and domain together. If commissions fall, you’ll have too many possible causes.
Pause or reduce paid traffic when landing pages or tracking fail. Otherwise, you can pay for clicks while the path to a commission is broken.
Frequently Asked Questions About Domain Migration
Is a registrar transfer the same as changing domains?
No. A domain transfer changes who manages the registration, while the domain name stays the same. Moving a website to a different domain is a separate process that requires page redirects and a Search Console address change.
Transfers commonly take five to seven days, but timing varies. Squarespace gives a range of one to 15 days. This timing is separate from Google’s processing of a website move.
You don’t need to change registrars to launch a new domain.
Can I transfer a domain for free?
Some registrars advertise no separate transfer fee, but the transfer commonly includes a paid one-year registration extension.
For Squarespace, unlock the domain, obtain its authorization code (also called an EPP code or transfer key), enter it, authorize the transfer, and pay the checkout charge.
Existing registration time generally carries over. You aren’t normally paying for that remaining time again. Moving the registration also doesn’t copy your website content.
Protect the Visitor Path, Not Just the Domain Name
A careful domain migration preserves useful pages, sends visitors to matching destinations, and keeps affiliate tracking intact. Rankings can fluctuate while Google processes the change.
Get your redirects and measurement working before you move traffic. Then follow the search data and commission records together, so you fix real problems without dismantling a sound migration.
