Moving a domain registration to another registrar does not automatically move the website, email or DNS service. The effect on search performance depends on what else changes and whether the site remains accessible.
Begin with a change plan, not a promise of zero SEO loss. Identify the services involved, check transfer eligibility and protect the configuration that keeps the current site working.
Separate the operations before you start
| Operation | What changes | Main preparation |
|---|---|---|
| Registrar transfer | The registration’s administering provider. | Authority, eligibility, approvals and continuing services. |
| Change of registrant | The registered holder’s details or rights. | Authorisation and any resulting restrictions. |
| DNS or hosting move | Where records are served or the site runs. | Configuration, testing and a controlled service switch. |
| Website address change | Visitor-facing domain or page URLs. | URL mapping, redirects and migration monitoring. |
A project can involve several operations, but they need their own instructions. Changing the registrar alone is not a reason to rewrite page URLs or redirect every page.
Check authority and transfer eligibility
Confirm the exact domain, current registrar and receiving provider. Make sure the authorised holder can access the relevant account and approval messages.
The implemented ICANN Transfer Policy governs covered inter-registrar transfers and changes of registrant. Relevant locks, disputes and registration state can affect eligibility. Country-code extensions may follow a different registry process.
Ask the current registrar to explain any restriction before changing settings. Check the effect of a proposed contact update before making it; some changes can affect the timing of a later transfer. Our transfer-process guide covers the administrative stages.
Identify who supplies DNS, hosting and email
Record the current nameservers and DNS provider, then confirm whether that service continues after the registration leaves. Also identify the hosting and email providers, important subdomains and account-recovery dependencies.
Namecheap’s transfer instructions say nameservers remain unchanged when transferring to it, but warn that the previous registrar’s default DNS may stop after completion. Preserving the nameserver labels is therefore insufficient if the underlying service ends.
Receiving providers can have different requirements. Cloudflare Registrar’s FAQ, for example, says its domains use Cloudflare nameservers. Check your chosen provider rather than assuming every registrar allows the existing configuration.
Export or record the DNS zone, including website, mail and verification records. If DNSSEC is active, plan it with the relevant providers’ instructions. Avoid copying security-related settings into a changed DNS arrangement without checking how they must be maintained.
Prepare a continuity plan for any service change
For a hypothetical business site, the registrar is changing while hosting and the mail provider remain. The old registrar also supplies DNS. That project needs a replacement DNS service configured with the required records, even though no website files or mailboxes are moving.
Test the replacement arrangement and agree who will make and verify the switch. Keep a record of the previous working settings and the recovery steps your providers support.
If hosting also changes, follow Google’s hosting-move guidance: prepare and test the new infrastructure, monitor traffic during the switch and retire the old service only when the move has been verified.
Our DNS guide explains the configuration roles. Registration completion and service continuity require separate checks.
Carry out the registrar’s supported transfer process
Confirm the receiving provider’s fees, term effects and extension support. Obtain any required authorisation code through the current registrar’s genuine account process and keep it private. Unlock the applicable transfer setting when eligible, then initiate the request with the receiving registrar.
Follow the actual approval and verification steps. Check unexpected messages through the real account rather than trusting a link or forwarded payment screenshot. Retain confirmations and any explanation of a delay.
Use the providers’ current status information to track completion. A universal fixed duration cannot account for every extension, restriction or account issue.
Verify the site and investigate changes in search evidence
After completion, confirm the domain in the receiving account, expiry, renewal settings and contact details. Test the homepage, important landing pages, forms, HTTPS and email. Check that necessary DNS records and verification methods remain present.
If visitor-facing URLs genuinely change, use Google’s separate URL-migration guidance. That is where mapping and redirects belong, rather than being automatic steps in every registrar transfer.
Review Search Console performance alongside availability and server evidence. A change in clicks alone does not identify its cause. Investigate inaccessible pages, unexpected redirects or altered content before attributing the result to the registrar.
Our cost guide helps record the ongoing commitment. A well-prepared transfer preserves control and makes service changes reviewable; it cannot guarantee an unchanged search position.