Skip to content

[Registrar] Improve domain transfer guide with missing steps and troubleshooting#28723

Merged
dcpena merged 7 commits into
cloudflare:productionfrom
mhsu:mhsu/registrar-transfers-update
Mar 4, 2026
Merged

[Registrar] Improve domain transfer guide with missing steps and troubleshooting#28723
dcpena merged 7 commits into
cloudflare:productionfrom
mhsu:mhsu/registrar-transfers-update

Conversation

@mhsu

@mhsu mhsu commented Mar 3, 2026

Copy link
Copy Markdown
Contributor

Rewrites the "Transfer your domain to Cloudflare" page to address gaps identified by comparing it against the internal support knowledge base. Users were getting stuck because the page did not explain that zones must be active before entering an auth code, and common failure scenarios had no troubleshooting guidance.

  • New step 3 (Disable DNSSEC): Surfaced directly in the numbered flow instead of buried in a partial
  • New step 6 (Add domain and activate zone): Explains that Cloudflare requires an Active zone before you can enter an auth code — the biggest gap in the original page
  • Step 4 (WHOIS privacy): Simplified — most transfers work with privacy enabled, only check if issues arise
  • Step 5 (Auth code): Added note that code is not needed immediately, with link forward to step 8 and expiration warning
  • Step 7 (Initiate transfer): Added payment failure warning, moved registration year exceptions into collapsible <Details> with new entries (.co 5-year max, .ai 2-year minimum, 10-year general limit)
  • Step 9 (Contact info): Added caution about .ca, .mx, .nz registrant verification emails
  • Step 10 (Approve transfer): Clarified timing — most registrars wait up to 5 business days, some TLDs (.mx) up to 10
  • New section: Transfer from website builders — Wix/Squarespace/Shopify intermediate registrar workaround (no competing registrar names)
  • New section: Troubleshoot transfer issues — 8 common failure scenarios (locked domain, DNSSEC still active, invalid auth code, zone not active, 60-day lock, restricted status, payment failure, slow transfer)
  • Transfer statuses intro: Updated stale dashboard navigation path
  • Removed outdated lines ("select x to remove domains", "You will not be billed at this step")
  • Steps renumbered from 1–8 → 1–10

…bleshooting

Address gaps identified from support knowledge base: add DNSSEC disable step,
zone activation requirement, website builder workaround, transfer timing
details, and 8 common troubleshooting scenarios.
@mhsu
mhsu requested a review from dcpena as a code owner March 3, 2026 01:47
@mhsu
mhsu requested a review from a team March 3, 2026 01:47
@github-actions github-actions Bot added product:registrar Related to Registrar product size/m labels Mar 3, 2026
@dcpena

dcpena commented Mar 3, 2026

Copy link
Copy Markdown
Contributor

Hey @mhsu, thanks so much for the contribution!

I think the troubleshooting section that was added would be a great fit for the page that currently exists at https://developers.cloudflare.com/registrar/troubleshooting/

@dcpena dcpena left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Move the Troubleshooting content to the troubleshooting page

… page

Per reviewer feedback, move the 8 transfer troubleshooting scenarios from
the transfer guide to /registrar/troubleshooting/, merging with existing
content. Add a link from the transfer page to the troubleshooting page.
@mhsu

mhsu commented Mar 4, 2026

Copy link
Copy Markdown
Contributor Author

@dcpena good sugggestions. Didn't realize that page existed. Just moved it over explicitly referenced /linked to that section from this page.

mhsu added 5 commits March 3, 2026 17:05
…oubleshooting entry

Add Block (formerly Squarespace domains) to the website builder list. Reword
the intermediate registrar workaround to be clearer. Add 'Cannot update
nameservers' entry to the troubleshooting page for discoverability.
Users often request an auth code before their zone is active on Cloudflare,
then the code expires while they wait. Add a dedicated troubleshooting entry
explaining the timing and recommending they wait for Active status first.
…o enter code'

Users expect to enter their auth code upfront like other registrars. Cloudflare
requires the zone to be active first. Reframe the section around this confusion
rather than code expiration.
…ansfer

Add context that Cloudflare requires the zone to be active first so the site
benefits from performance and security features from the moment the transfer
begins. Merge 'Zone is not active' into the auth code troubleshooting entry
to reduce duplication.
Move 'Request an authorization code' from step 5 to step 7, immediately
before 'Input your authorization code' at step 8. Clarify headings: step 7
happens at your current registrar, step 8 happens in the Cloudflare dashboard.
Renumber steps 5-8 and update internal links.
@mhsu

mhsu commented Mar 4, 2026

Copy link
Copy Markdown
Contributor Author

A few more improvements for clarify and to match user journeys. Here's the updated list:

Troubleshooting page (/registrar/troubleshooting/)

  • Moved all 8 transfer troubleshooting scenarios here, merged with existing content where there was overlap (locked domain, auth code invalid, WHOIS privacy)
  • Added new section: "Cannot find where to enter your authorization code" — explains that unlike other registrars, Cloudflare requires the zone to be active first, and why (performance and security). Common problem.
  • Added new section: "Cannot update nameservers at your current registrar" — covers website builders (Block, Shopify, Squarespace, Wix) with a link back to the transfer page workaround. This is a major support issue today.
  • Removed the separate "Zone is not active" section (merged into the auth code section to reduce duplication)

Transfer page (/registrar/get-started/transfer-domain-to-cloudflare/)

  • Replaced the inline troubleshooting section with a link to the troubleshooting page
  • Reordered steps: moved "Request an authorization code" from step 5 to step 7, right before "Input your authorization code" at step 8 — so users request the code when they actually need it, not several steps before. Also prevents issue of auth code potentially expiring if users are stuck at nameserver updates.
  • Updated step headings to clarify where each action happens: "Request an authorization code from your current registrar" (step 7) vs. "Input your authorization code in the Cloudflare dashboard" (step 8)
  • Added context on why Cloudflare requires zone activation first (performance and security)
  • Added Block to the website builder platforms list, reworded the intermediate registrar workaround to be clearer

@dcpena
dcpena enabled auto-merge (squash) March 4, 2026 16:04
@dcpena
dcpena merged commit a37d8e3 into cloudflare:production Mar 4, 2026
5 checks passed
@mhsu

mhsu commented Mar 5, 2026

Copy link
Copy Markdown
Contributor Author

Thanks for the feedback @dcpena! I have moved the troubleshooting content to the existing troubleshooting page and made several other improvements based on your review. Here is a summary of the changes in the latest commits:

Troubleshooting page (/registrar/troubleshooting/)

  • Moved all 8 transfer troubleshooting scenarios here, merged with existing content where there was overlap (locked domain, auth code invalid, WHOIS privacy)
  • Added new section: "Cannot find where to enter your authorization code" — explains that unlike other registrars, Cloudflare requires the zone to be active first, and why (performance and security)
  • Added new section: "Cannot update nameservers at your current registrar" — covers website builders (Block, Shopify, Squarespace, Wix) with a link back to the transfer page workaround
  • Removed the separate "Zone is not active" section (merged into the auth code section to reduce duplication)

Transfer page (/registrar/get-started/transfer-domain-to-cloudflare/)

  • Replaced the inline troubleshooting section with a link to the troubleshooting page
  • Reordered steps: moved "Request an authorization code" from step 5 to step 7, right before "Input your authorization code" at step 8 — so users request the code when they actually need it, not several steps before
  • Updated step headings to clarify where each action happens: "Request an authorization code from your current registrar" (step 7) vs. "Input your authorization code in the Cloudflare dashboard" (step 8)
  • Added context on why Cloudflare requires zone activation first (performance and security)
  • Added Block to the website builder platforms list, reworded the intermediate registrar workaround to be clearer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

product:registrar Related to Registrar product size/m

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants