Connect your domain at GoDaddy
Add the certificate and www records in GoDaddy DNS and forward your root domain, since GoDaddy has no ALIAS records.
Provider steps checked November 18, 2026. Provider dashboards change; if a button has moved, the official help links at the bottom have the current wording.
You’ll add two or three records in your GoDaddy account: one that proves you own the domain, and the ones that point it at your site. It takes about 10 minutes, it can be undone, and it doesn’t touch your email.
Your Staticbot deployment page shows the exact values to paste, with a copy button next to each, and checks whether GoDaddy is already answering with them. Keep it open next to this guide.
Before you start
- GoDaddy usually starts you with a www record pointing at @. A name can hold only one CNAME, so edit that record instead of adding a second www.
- An A record on @ showing “Parked” is GoDaddy’s placeholder page. Forwarding (below) replaces it.
Open the DNS records at GoDaddy
- Sign in to GoDaddy and open your Domain Portfolio.
- Select your domain and open the DNS tab.
- Click Add New Record and choose the type.
Name and Value are GoDaddy’s names for the two boxes you fill in. In Name, type only the part before your domain (for example www). GoDaddy adds the domain itself. A CNAME can’t use @.
Server-rendered app hosted on Cloudflare? Its deployment page lists TXT records and a CNAME on www pointing at apps.staticbot.app instead of the records below. Add them in the same form, with the same Name rule.
Step 1: Add the certificate record
This record lets Amazon issue the HTTPS certificate for your domain. It doesn’t change where your site or email points. Add one record per certificate record shown on the deployment page:
Save, then go back to the deployment page and click Check my records. Staticbot asks GoDaddy’s own servers, so you see the answer within seconds. Once it shows Found, the certificate is usually issued within a few minutes.
Step 2: Point your domain at your site
The deployment page shows these records once the certificate is issued. If your site lives on a subdomain such as app.yourdomain.com, you only add one CNAME for it.
GoDaddy has no ALIAS or ANAME records, so yourdomain.com (without www) can’t point at your site directly.
- Point www at your site with the CNAME record Staticbot shows.
- Go to DNS → Forwarding → Add Forwarding. Forward yourdomain.com to https://www.yourdomain.com as a Permanent (301) redirect. GoDaddy adds HTTPS to forwarding automatically and locks the @ record while forwarding is on.
- Or change nameservers to Staticbot (see below). Then yourdomain.com works over HTTPS directly.
For www.yourdomain.com:
Check it worked
The deployment page checks each record and tells you what it sees: Found, Not found yet, Wrong value, or Domain typed twice (the domain was typed into the Name box). Most records show up within a minute. Your browser may keep showing the old page for a while after that; a private window shows the new one sooner.
Working with an AI agent connected to Staticbot? Ask it whether your DNS records are live; it runs the same check.
Common problems at GoDaddy
- GoDaddy says the record name is already in use
- Another record already uses that Name (often the default www record). Edit it instead of adding a new one.
Make the domain itself work: change nameservers
Instead of adding records, you can point the domain’s nameservers at Staticbot. You then add no records at all: the certificate and the site, the domain itself included, are set up automatically. GoDaddy can’t point the domain itself at your site, so this is the way to make yourdomain.com work, not only www.
It’s the right choice when you don’t use the domain for anything else yet: no email on it, no other subdomains. The deployment page recommends it in that case. If the domain has email, Staticbot copies the email records it can see on the domain itself before you switch; records on other names (such as blog.yourdomain.com or email signing keys) have to be re-created, so adding records is usually the safer route there. The deployment page only offers the switch when it’s safe to.
At GoDaddy:
Open your Domain Portfolio and select the domain. Go to DNS → Nameservers, choose “I’ll use my own nameservers”, remove GoDaddy’s defaults and enter the Staticbot nameservers. Save. Turn off DNSSEC first if it is on.
More about what moves and what to check: changing nameservers.
