WEBSITESfor Normal People2026

Part III: Before You Go Live (now the domain)07

Chapter 07

Before launch: Buy your domain on Cloudflare

9 min read, 2 cheat sheets, 3 things to tick

The preview works? Now pick the address.

Buy it on Cloudflare: search the name, then buy it in your Cloudflare dashboard (the steps are below). There's no markup: you pay what the registry (the company behind .com or .ca) charges, and a .com is US$11.17 a year as of November 2026. And the domain's DNS, the settings that say where it points, is on Cloudflare from the start, so your AI agent can connect it to your site without you.

Already own a domain? Don't buy another. Keep it where it is and point it at Cloudflare instead; that's further down. Either way, do this once your site works on its free workers.dev preview address. Build first, then buy the address you'll put on the business card.

Why Cloudflare, and not GoDaddy or Wix or Squarespace?

Three reasons. The first two are about money. The third is the one that makes this guide work, and you get it whether you buy the domain here or not.

1. No registrar markup. Cloudflare charges the registry and ICANN cost for registration and renewal. The underlying price can still change. Check the renewal price before you buy. Cloudflare Registrar explains its pricing.

2. No upsells. No "premium DNS", no "domain protection bundle", no "business email trial" pre-ticked at checkout. You buy a domain and that's the whole transaction.

3. Your DNS is in the same account as your site. DNS is the settings page that says where your domain points and where its email goes. When it's on Cloudflare, your hosting, DNS, forms, email sending and file storage all sit in the same account. So when the agent needs to point the domain at your site, add a record to verify Google Search Console, or set up email so your contact form doesn't land in spam, it just does it.

With DNS somewhere else, every one of those becomes "log in to your registrar and add this record", a screenshot, a wrong field, a four-hour wait, and a "did it work?". Multiply that by every service in this guide.

The part that matters is DNS on Cloudflare, not where you paid for the domain. Buying on Cloudflare gets you both in one step. Already own a domain? Pointing it at Cloudflare gets you the same result.

How to buy a domain on Cloudflare

Check the name and the price first on Cloudflare's domain search. No account needed. Then buy it in your dashboard. These are Cloudflare's own steps, checked 3 November 2026:

  1. Make sure your Cloudflare account email is verified. Cloudflare won't register a domain without it. (No account yet? Make one first.)
  2. Cloudflare dashboard → Domains → Buy domain, or go straight to Register domains. Search for the name and select Purchase.
  3. Pick how many years. One is fine. Auto-renew is on by default; keep it on and keep your card current.
  4. Add your real contact details. The registry requires them, and Cloudflare hides them from the public lookup wherever the registry allows. Use plain letters only: the form takes no accents, so it's Montreal, not Montréal.
  5. Choose how to pay, read the agreements, then select Complete purchase. It takes up to 30 seconds.
  6. Verify your contact email when you're asked. ICANN requires it. Until you do, the domain goes on hold and stops pointing anywhere useful.

Done. It's already on Cloudflare DNS, ready for the agent.

Watch itSearch → buy → domain shows as Active.

Personal details are covered or swapped for examples. Press play, it's silent and loops.

What it costs

Most endings cost the same to renew as to buy. A few registries discount the first year, and that's where people get caught. From Cloudflare's domain search on 3 November 2026, in US dollars:

EndingFirst yearEvery year after
.com$11.17$11.17
.ca$9.19$9.19
.online$4.99$27.70
.store$4.99$42.20

.online and .store are the trap. A $4.99 domain that renews at $42.20 isn't cheap, it's a teaser. Read the renewal column, not the big number. For a business that plans to be around next year, .com or .ca wins on price and on trust.

The catches

  • The domain stays on Cloudflare DNS. A domain registered at Cloudflare can't use another provider's nameservers. For this guide that's the point. If you ever want your DNS somewhere else, you move the domain to another registrar first.
  • A .ca needs a Canadian connection. Cloudflare sells .ca, but CIRA's Canadian Presence Requirements still apply. You or your business has to fit one of CIRA's categories, such as a Canadian citizen, a permanent resident or a Canadian company.
  • It's a domain, not an inbox. No mailbox comes with it. Forms and email sets up a free hello@ address that lands in the inbox you already use.

Picking the name

  • Short and sayable. If you have to spell it out on the phone, it's too long.
  • .com or your country's ending. For a Canadian business, .ca is great and people trust it. Avoid .biz, .site, .online and friends for a real business.
  • No hyphens, no numbers unless they're part of your actual business name.

Already own a domain somewhere else?

Don't buy a second one, and you don't need to move it either. Keep paying for it where you bought it. All you change is where its DNS lives, which is free. The agent can prepare this now. If the domain already serves a site or email, have it check those records before you change anything:

  1. The agent adds your domain to Cloudflare, copies over your existing DNS records (including email), and gives you two nameservers (the addresses that tell the internet to ask Cloudflare about your domain), like ada.ns.cloudflare.com.
  2. You log in to wherever you bought the domain (GoDaddy, Namecheap, Wix, Squarespace...), find Nameservers, choose custom nameservers, and paste in Cloudflare's two. If DNSSEC is on there, turn it off a day before. (Shopify doesn't let you change them; the table below has the way around it.)
  3. Wait. Minutes to a day. The agent can check for you and tell you when it's Active.
Watch itChanging nameservers at a registrar (GoDaddy as the example).

Personal details are covered or swapped for examples. Press play, it's silent and loops.

How to transfer a domain to Cloudflare

Should you? Only if it saves you money. Transferring moves where you pay for the domain each year. It doesn't change what the agent can do, because the DNS is already on Cloudflare after the step above.

  • Renewal coming up in the next month or two? Transfer it then. For .com and most common endings, the transfer adds a year at Cloudflare's price, so you skip your registrar's renewal price.
  • Renewal is a long way off? Leave it, unless your registrar's renewal price is well above Cloudflare's. Nothing in this guide needs it moved.
  • Bought it, moved it or changed its owner details in the last 60 days? ICANN's rules block a transfer for 60 days. Wait.

Cloudflare's transfer guide, checked 15 November 2026, puts it at about 30 minutes of your time and up to 10 days end to end.

What does it cost? One year at Cloudflare's price, added to your current expiry date, so you don't lose the time you've already paid for. A .com is US$11.17. A few country endings work differently: a .uk transfer adds no year and costs nothing.

Can I transfer without changing nameservers? No. Cloudflare only lets you enter the transfer code once the domain is Active on Cloudflare, which means its nameservers already point there. So the nameserver switch above always comes first, and a domain registered at Cloudflare has to keep Cloudflare's nameservers.

Before you start

  • The domain is active on Cloudflare (the section above).
  • DNSSEC was turned off at your old registrar at least 24 hours before you changed the nameservers. Left on, it can break the domain and blocks the transfer.
  • The domain hasn't expired. If it expired and you renewed it, wait 45 days past the old expiry date, or the registry may not add the year.
  • Your Cloudflare email is verified and there's a card on file.

The steps

  1. At your old registrar, unlock the domain. Some registrars have more than one lock (domain lock, transfer lock, privacy lock). Turn off every one.
  2. Request the authorization code. It's also called an auth code, EPP code or transfer code. Ask for it when you're ready to use it, because it expires.
  3. In Cloudflare, go to Transfer domains. Pick the domain, paste the code and confirm the payment.
  4. Enter your contact details and select Confirm transfer. Cloudflare hides them from the public lookup by default.
  5. Approve the transfer at your old registrar. It emails you. Approving speeds it up; otherwise most registrars release the domain within five days.
  6. Got a .ca? Watch for a separate email asking you to verify your contact details after the transfer. Miss it and the domain can be suspended.

Where the lock and the code are at your registrar

RegistrarUnlock and get the codeWatch out for
GoDaddyDomain Portfolio → your domain → Transfer → Transfer to another registrar → Continue with transfer. The code shows on screen and goes to the domain's contact email (GoDaddy's steps)Turn Domain Protection off completely first. Cloudflare says GoDaddy may reject the transfer if Domain Protection or Domain Privacy is still on
NamecheapDomain List → Manage → Sharing & Transfer. In Transfer Out, unlock it, then request the auth code (Namecheap's steps)The code goes to the domain's registrant email, which isn't always your login email
SquarespaceDomains → your domain → switch Domain Lock off → Request transfer code. It's emailed within 24 hours (Squarespace's steps)Squarespace turns DNSSEC on for its domains, and you can't change it once a transfer is pending. A free Squarespace domain stops being free when it leaves. Leaving Squarespace has the full order
WixDomains → the Domain Actions icon next to it → Transfer away from Wix → Transfer Domain → I Still Want to Transfer. The code goes to the registrant email (Wix's steps)Turn off Private Registration first so the emails reach you. Wix says its business email stops working after the transfer until the MX records are set up at the new provider, so check they're on Cloudflare
ShopifyNo direct transfer: Shopify doesn't let you change the nameservers, so the domain can't become active on CloudflareCloudflare's workaround is to transfer to another registrar, wait 60 days, then transfer to Cloudflare. Or stop after the nameserver change at that other registrar. That's all this guide needs

Why a transfer fails

These are the usual causes, from Cloudflare's troubleshooting page:

  • It's still locked. A second lock is still on, or the unlock hasn't shown up yet. That can take up to 5 hours, and up to 24 at some registrars.
  • The code is rejected. It expired, or a space came along when you pasted it. Request a fresh one.
  • The domain isn't on Cloudflare's transfer page. It isn't active on Cloudflare yet, it was registered or moved in the last 60 days, or Cloudflare doesn't sell that ending.
  • The old registrar rejected it. Someone declined the approval email, a "reject all transfers" setting is on, or, at GoDaddy, Domain Protection or Domain Privacy was still on.
  • Too many years. A .com can't be registered more than 10 years ahead. With 9 or more years left, the year the transfer adds pushes it over.

Not sure where yours stands? The agent can check the public records before you start:

PromptCheat sheet 0113 lines
I want to transfer [DOMAIN] to Cloudflare Registrar from [REGISTRAR].
Don't start the transfer and don't pay for anything. First check and
tell me in plain words:

- Is the domain active on Cloudflare in my account?
- From the public RDAP or WHOIS record: when it was registered, when
  it expires, the date of its last transfer if it shows one, its status
  codes (is it locked?) and whether DNSSEC is on.
- Does Cloudflare Registrar support this ending?
- Anything that would block or delay the transfer, and what I need to
  turn off at [REGISTRAR].

Then give me the steps for [REGISTRAR] and Cloudflare, and wait for me.

The domain preparation prompt

PromptCheat sheet 0218 lines
My site is ready on staging. My launch domain is [DOMAIN], registered at
[Cloudflare / REGISTRAR]. Prepare it for launch, but do not publish the new
site or buy or transfer a domain for me.

Use cf with the browser login from my preview. Find the needed zone and
DNS commands with cf cli search and inspect their help/schema. If this
login lacks required access, explain the exact permission before asking
me to approve it. Never ask me to paste a token in chat.

Check whether the domain is active in my account. If DNS is elsewhere, add the zone and compare its records with
the current provider, including the old site's records, MX, SPF, DKIM,
DMARC and verification records. Preserve the existing website and email.
Tell me any DNSSEC steps needed before a nameserver change.

Give me the exact nameservers and registrar instructions if I need to
change them. Wait for me, then check that the zone is active and existing
services still work. Save the domain and zone ID in this project's
CLAUDE.md. List what remains for forms, email, analytics and launch.

Checklist

Next: forms and email, then analytics and the launch check. Your old site stays live until you approve the switch.

On a phone, swipe left and right to turn pages.