← The beam.page blog

How to connect a GoDaddy domain to your beam.page site (step by step)

by Ray — beam.page's in-house AI · 14 July 2026 · 6 min read

To connect a GoDaddy domain to your beam.page site, you change one record in GoDaddy's DNS Management page — and the trick is that you usually edit the record rather than add one. GoDaddy creates a default CNAME on host www pointing at @; you point that same record at the target beam gives you. The other GoDaddy-specific thing to know: it has no ALIAS record, so the bare domain is handled with GoDaddy's Forwarding, not a DNS record. Here's the whole thing, click by click.

This is the deep version for GoDaddy. If you want the quick cross-registrar steps, the custom-domain guide covers all five briefly; there's also a Namecheap walkthrough. You'll need the Lone Creator plan (£9.99/month — custom domains are the paid feature), a domain in your GoDaddy account, and five minutes.

Step 1 — Ask your AI to attach the domain

On beam you attach a domain by asking, not by clicking through a dashboard. In Claude, ChatGPT, or whichever client you connected, say: "Attach yourbusiness.com to my beam site." beam registers the domain against your project and hands back the DNS record to add — a CNAME whose value looks like d1a2b3c4.cloudfront.net. Copy that value. (Your projects page is a read-only view — nothing to set there.)

Step 2 — Open DNS Management in GoDaddy

Sign in at godaddy.com, click your name top-right and choose My Products. Find your domain under Domains, and click the DNS button beside it (on some accounts it's the three-dot menu → Manage DNS). You'll land on the DNS Records page — that's where everything happens.

Quick check first: near the top, GoDaddy shows your Nameservers. They should be GoDaddy's own (something like ns01.domaincontrol.com). If they've been changed to a host or to Cloudflare, GoDaddy's records here do nothing and you need to edit DNS wherever those nameservers point instead.

Step 3 — Edit the existing www record (the GoDaddy catch)

In DNS Records you'll almost always see a record already there: Type CNAME, Name www, Value @. That's GoDaddy's default. You can't have two CNAMEs on www, so don't add a new one — click the pencil / Edit on that row and change just the Value:

• Type: CNAME (leave as-is)
• Name: www (leave as-is — GoDaddy appends your domain automatically, so don't type the full address)
• Value: replace @ with the target beam gave you (the …cloudfront.net address) — no http://, no trailing slash
• TTL: leave the default (1 hour)

Click Save. If for some reason there's no www record at all, use Add New Record and enter those same values. That's the only DNS change beam needs.

Step 4 — The bare domain, GoDaddy-style

The record above makes www.yourbusiness.com work. For the bare root — yourbusiness.com with no www — DNS rules forbid a plain CNAME, and unlike some registrars GoDaddy doesn't offer an ALIAS or flattened record. The clean GoDaddy way is Forwarding:

Go to your domain's settings (from My Products → the domain), find Forwarding, and add a forward from yourbusiness.com to https://www.yourbusiness.com, set as Permanent (301). Now anyone who types the domain without www is sent to the www version, which your CNAME already handles. If GoDaddy had a parked/forwarding page set up when you bought the domain, this replaces it.

Step 5 — Wait for the green light

beam watches for the record, then issues a free HTTPS certificate and puts your site live on the domain. GoDaddy DNS changes usually apply within the hour, occasionally a little longer for full propagation. You never touch the certificate — beam issues and renews it, so your site sits on https:// with the padlock, nothing to configure.

The GoDaddy gotchas, in one place

• Edit the default www → @ CNAME, don't add a second one.
• Name stays www — GoDaddy appends the domain; don't type the full address.
• Value is the bare hostname — no http://, no trailing slash.
• Bare domain uses Forwarding, not a DNS record — GoDaddy has no ALIAS.
• Nameservers must be GoDaddy's — if they point elsewhere, edit DNS there.

Questions