How to Change Your Coaching Website Domain: 7 SEO Checks
Nour
Founder, Coachful

Changing your coaching website domain is a site migration, not just a branding update. Keep the old domain under your control, map each important old URL to its new equivalent, arrange permanent redirects, and test the booking journey before announcing the move. You can reduce avoidable damage, but nobody can promise unchanged Google rankings.
The expensive mistake is changing the address, redesigning every page and switching booking systems in the same weekend. When enquiries disappear, you cannot tell which change caused it. Move the address first where practical. Improve the design later.
This guide is for a coach moving an established website to a new domain, perhaps after a name change or a move from a personal brand to a practice brand. It is not a guide to transferring domain registration between registrars, and it does not migrate client records or payment subscriptions.
Before you start: do you actually need a new domain?
A new offer rarely requires a new address. If you are adding executive coaching to an existing career practice, a new service page may be enough. Changing domains adds work without automatically adding authority, traffic or trust.
There are sensible reasons to move: your legal or public business name has changed, the old name materially misrepresents the practice, or you have acquired a clearer address worth using long term. A slightly prettier spelling is a weaker reason, especially if existing articles already attract enquiries.
Write down the reason, the person doing the technical work and the condition for postponing launch. For example: “We will not announce the new address until the main service pages, enquiry form and booking route pass an outside-account test.” A calendar date is not evidence of readiness.
1. Keep control of both domains and record your starting point
Keep access to the old domain registration, its DNS settings and the service that will handle redirects. Also confirm access to the new domain, your website editor, analytics and Google Search Console. Check who actually owns each login. Your former designer's email address should not be the only recovery route.
Do not cancel the old website service before you know how old URLs will redirect. You might eventually replace expensive hosting with a suitable redirect service, but verify that it supports the exact paths and HTTPS you need. Registrar “forwarding” is not automatically a complete migration solution.
Before changing anything, save a copy of the current site and export a list of its pages where your tools allow. Record your main landing pages, organic search clicks, enquiries and completed bookings over a representative period. Note campaigns, seasonality and any unusually large referral source. You need a comparison, not a fabricated forecast.

For a coaching practice, the revenue-critical list often includes the homepage, individual service pages, discovery-call page, lead-magnet download, workshop registration and the handful of articles that produce relevant traffic. An old PDF can matter as much as a blog post if referral partners still share it.
2. Build an old-to-new URL map before the switch
Create a simple spreadsheet with six fields: old URL, new URL, page purpose, redirect action, test result and owner. Include complete addresses in your working document so you can distinguish domains, subdomains and paths. Keep access appropriately restricted if the inventory includes private links.
Match the destination to the original intention. Someone following an interview-preparation article should reach that article or its genuinely relevant replacement, not a generic homepage. Someone opening a booking link should arrive at the matching booking route, not an unrelated programme checkout.

If only the domain changes, keeping page paths unchanged makes the mapping simpler. If paths must change, record each exception. Where several old articles become one stronger resource, a relevant consolidated destination may make sense. Do not redirect unrelated removed pages merely to avoid showing an error.
Google's site-move documentation recommends returning a proper 404 or 410 when content has been removed without a suitable replacement. Ask your technical provider to handle those cases deliberately. A page saying “not found” while returning a successful status is not the same thing.
Keep public marketing URLs separate from authenticated client routes. A signed-in session page or a private document may have access rules that a website redirect must not bypass. Confirm those routes with the platform rather than treating every link as public content.
3. Separate DNS, HTTPS, redirects and email
DNS tells browsers which server should answer for a domain. HTTPS establishes a secure connection. A redirect tells the browser that a particular URL has moved. Connecting the new domain does not, by itself, make the old URLs redirect.

Ask your website provider or developer to confirm who controls each part. Google recommends server-side permanent redirects for permanent moves. Common implementations use 301 or 308 responses, but use the method your hosting stack supports correctly rather than pasting server rules from an unrelated tutorial.
Old HTTPS URLs still need a valid secure connection before the redirect can happen. If the certificate for the old address expires, a visitor may see a security warning before they can reach your new site. Check the old host, not just the shiny new homepage.
Email is another separate dependency. Changing website records should not mean deleting mail-related DNS records. Before editing DNS, identify the records used by your business mailbox and authenticated email sender. If you are also changing your email address, plan mailbox continuity, forwarding where supported and sender authentication as a separate task.
Do not publish a universal DNS recipe for your assistant to follow. The correct values come from your actual website and email providers. Save the existing configuration, apply only the required changes and have a recovery contact ready if the wrong service stops resolving.
4. Prepare the destination without changing the whole practice
Make the new pages substantively equivalent to the old ones during the domain move where practical. Keep the offer, important copy and main page structure recognisable. Google advises changing one thing at a time rather than combining a domain move, CMS change and new layout.
If a rebrand is the reason for the move, update the visible business name carefully. Check the homepage, footer, contact details, booking page and payment-facing information. A domain change should not leave a prospect wondering whether they have landed at a different coach's business.

Ask the technical owner to check self-referencing canonical URLs, internal links, sitemap URLs and any language annotations. The new page should not keep identifying the old address as its preferred version. Remove development-only noindex instructions or crawler blocks when the public pages are ready, without exposing material that should remain private.
Coachful can provide the destination website and related coaching surfaces, but do not assume that connecting a custom domain also creates a complete redirect map from another host. Check the domain options and account-specific plan eligibility in your workspace, and confirm redirect responsibilities with support or your existing host before switching.
That distinction matters if you are moving from another website platform. A successful new-domain connection proves that the destination can load. It does not prove that old article links, PDFs, email links and partner referrals will arrive there correctly.
5. Test the visitor journey, not just the homepage
Use an incognito window or a browser without your administrator session. Start with an old service URL, follow its redirect, read the new page and use its primary action. Repeat on a real phone or a mobile browser viewport. Signed-in editor previews can hide public access problems.

For a coaching booking journey, confirm the session type, time zone, price if applicable and destination account. Use a test arrangement approved by the person who manages the calendar. Do not create real charges, contact real clients or reserve unwanted appointment slots as a casual technical check.

If you use forms, submit a clearly labelled test with an address you control and confirm where the response lands. Check any confirmation page, resource delivery and follow-up link that belongs to that flow. If you cannot safely test a payment, ask the payment owner for a provider-supported test method rather than entering somebody else's card.

Ask the technical owner to record the old URL's response, final destination and any redirect chain. Prefer a direct hop to the relevant final URL rather than several historical domains bouncing visitors between them. Check that the final page genuinely works; an HTTP success response alone does not mean its form or button works.
Also test the version with and without “www,” old HTTP links and old HTTPS links according to the intended configuration. Do not assume that testing one variant covers the others. Record failures and fix the broken route before announcing the migration.
6. Launch the redirects and tell search engines what changed
Choose a quieter period when someone responsible can monitor the move. Avoid switching just before a webinar, partner promotion or booking deadline. If the technical person is unavailable until Monday, Friday evening is not a clever launch window.
Verify the old and new properties in Search Console, submit the new sitemap and use Google's Change of Address tool when the move is eligible. Follow Google's current instructions for your specific move. That tool supplements the migration; it does not replace functioning redirects.
Inspect important new URLs and monitor indexing, redirects and errors. Google's documentation warns that rankings can fluctuate while pages are recrawled and reindexed. There is no honest guarantee that a coaching site will settle within a specific number of days.
Tell existing clients only what they need to know: the official new address, whether their current booking or portal link changes, and where to contact you if something looks wrong. Avoid sending unfamiliar payment instructions as part of a vague “new website” message.
A short notice can say: “Our public website is moving to [new address] on [date]. Your coaching arrangement is unchanged. [Explain any actual change to the booking or portal link.] If you are unsure about a message or payment request, contact me using the number or address you already have.” Replace every bracket with verified information before sending.
7. Update shared links and keep the old address working
Redirects are a safety net, not a reason to leave every visible link outdated. Update your own website navigation, social profiles, email signatures, downloadable materials and link-in-bio destinations. Ask important referral partners and directories to update their links when appropriate.

Keep a small external-link register: location, old link, new link, person responsible and date checked. Prioritise links that already send enquiries. A neglected booking link in a partner's newsletter archive can be more commercially important than a barely used social profile.
Google recommends keeping redirects for at least a year. Consider keeping the old domain and useful redirects longer where clients, printed materials or backlinks still depend on them. Maintaining redirects also requires the old address to remain registered and the serving configuration to keep working.
Monitor both search and the business outcome. If organic clicks drop, inspect indexing and redirect errors. If traffic is stable but bookings fall, test the booking journey and form delivery. If a promotional campaign ended on launch day, do not automatically blame the domain. Diagnose the stage that changed.
A small-practice migration checklist you can hand to a developer
- Ownership: Confirm who controls old and new registration, DNS, hosting, website publishing and mail settings.
- Inventory: List public pages, downloads and high-value incoming links; keep private client routes separately controlled.
- Mapping: Assign each important old URL a relevant destination or an intentional removal response.
- Destination: Check content, internal links, canonical URLs, HTTPS and intended indexing permissions.
- Continuity: Confirm old-domain HTTPS and redirects, plus separate mailbox and sender requirements.
- Testing: Exercise old links through service pages, forms, bookings and confirmations with controlled test details.
- Launch: Set a responsible owner, monitoring window and explicit postponement conditions.
- Aftercare: Check Search Console, update shared links and retain the old-domain redirect service.
This is a responsibility checklist, not a server configuration file. Ask for actual test results against your URLs. “The migration is done” is less useful than a record showing that your most important old links reached the right pages and completed the intended actions.
Frequently asked questions
Will changing my coaching domain hurt SEO?
It can cause temporary ranking fluctuations and can cause more serious problems if redirects, indexing instructions or page mappings are wrong. A careful migration reduces avoidable risk; it does not guarantee unchanged rankings. Preserve relevant content and follow Google's current site-move guidance.
Should I move my domain and redesign my website together?
Separate them where practical. If you change the domain, page structure, copy and booking system at once, failures are harder to isolate. If a combined move is unavoidable, use a more detailed URL map, test plan and technical owner rather than skipping the controls.
Can I cancel my old website after connecting the new domain?
Only once you have confirmed how the old URLs will continue to redirect. You may be able to use another suitable service instead of the original host, but first verify HTTPS, path handling and the duration of the arrangement. Do not cancel the old domain registration.
Does my business email automatically move with my website?
No. Website hosting, domain registration and email hosting are different services, even when one supplier sells them together. Confirm the mail records and mailbox plan separately. If the email address itself changes, manage that transition explicitly.
Give the new address a working destination
Before moving anything, test the website and booking experience you want people to reach. If you are considering Coachful as that destination, use the demo to inspect the website, link page and scheduling surfaces, then confirm your domain and redirect requirements for your own setup.
Try the interactive demo. It is a way to evaluate the destination experience, not a promise of automatic SEO migration. Keep the old address working until the real routes have been verified.







