ChatGPT GrowPoint your blog at your own domain
Your blog lives at the address we give you. Moving it to your own domain takes one CNAME record, added wherever that domain’s DNS is managed — certificates, routing and hosting stay with us.
Last checked: 2026-09-28
Three steps
One record in total: enter your domain here, then copy two values into your DNS provider.
- 1
In My blog → Custom domain, enter the subdomain you want, for example blog.yourdomain.com.
- 2
Copy the record it shows you — Type, Name and Target.
- 3
Add that record where your domain’s DNS is managed. Once the certificate is issued, your blog is on your domain.
The record looks like this
- Type(always CNAME)
- CNAME
- Name(Host)
- blog
- Target(Value / Points to)
- cname.chatgptgrow.com
Use the Name value our card gives you — that is the first part of the subdomain you entered here. The examples below all use blog.
Field names differ per provider: Name may be called Host, Target may be called Value or Points to. The type is always CNAME.
Do it in your DNS provider
Menu names below are kept exactly as they appear in each console, so you can match them on screen.
Cloudflare
- 1.Open Cloudflare, select your domain, then DNS → Records in the left sidebar.
- 2.Click Add record: set Type to CNAME, Name to blog, Target to cname.chatgptgrow.com.
- 3.Switch Proxy status from Proxied to DNS only — the cloud turns from orange to grey.
- 4.Click Save. Cloudflare changes usually go live worldwide within a minute.
Keep this record grey. On orange, requests pass through your own zone’s cache and security first: after you publish, visitors may keep seeing an old page — and that kind of problem is invisible from our side.
- Overview
- DNS
- SSL/TLS
- Rules
- Caching
Add record
GoDaddy
- 1.In GoDaddy, go to My Products → your domain → DNS.
- 2.Click Add New Record and set Type to CNAME.
- 3.Set Name to blog, Value to cname.chatgptgrow.com, and leave TTL on the default 1 Hour.
- 4.Click Save. GoDaddy’s panel sometimes takes a moment to refresh — that is normal.
DNS Records
Namecheap
- 1.In Namecheap, go to Domain List → Manage next to your domain.
- 2.Open Advanced DNS and click Add New Record → CNAME Record.
- 3.Set Host to blog, Target to cname.chatgptgrow.com, and leave TTL on Automatic.
Advanced DNS
Amazon Route 53
- 1.In the AWS console, go to Route 53 → Hosted zones and select your domain.
- 2.Click Create record: Record name is blog, Record type is CNAME, Value is cname.chatgptgrow.com.
- 3.Click Create records. The default TTL of 300 seconds is fine.
- Dashboard
- Hosted zones
- Health checks
Create record
Google Cloud DNS
- 1.In the Google Cloud console, go to Network services → Cloud DNS and select your zone.
- 2.Click Add record set: DNS name is blog (it completes to blog.yourdomain.com. for you), Resource record type is CNAME, Canonical name is cname.chatgptgrow.com.
- 3.Click Create.
- Compute Engine
- Network services
- Cloud DNS
Create record set
Wix
- 1.In Wix, go to Domains → your domain → DNS Records.
- 2.Click Add Record, choose CNAME: Host name is blog, Value is cname.chatgptgrow.com.
- 3.Save.
DNS Records
Squarespace Domains
- 1.In Squarespace, go to Domains → your domain → DNS → DNS Settings.
- 2.Click Add Record, choose CNAME: Host is blog, Data is cname.chatgptgrow.com.
- 3.Save.
DNS Settings
Hostinger
- 1.In hPanel, go to Domains → your domain → DNS / Nameservers.
- 2.Click Add record, choose CNAME: Name is blog, Target is cname.chatgptgrow.com.
- 3.Save.
DNS records
Other providers
- 1.Find the page your provider calls DNS records, DNS zone or domain resolution.
- 2.Add a CNAME: host (Name) is blog, value (Target / Points to) is cname.chatgptgrow.com.
- 3.If your provider has a proxy, CDN or acceleration switch, turn it off — DNS only.
- 4.Save, then give it a few minutes.
DNS records
Confirm it on our side
The card under My blog → Custom domain shows the live status of this record.
My blog
Custom domain
Add this record in Cloudflare
Set this record to DNS only (grey cloud). Proxying it puts your caching and security settings in front of ours.
Once the certificate is issued the badge reads Live, and the blog address at the top of the page switches to your domain in the accent colour.
Checking it yourself
- Open the address: if the blog loads, you are done.
- From a terminal: dig blog.yourdomain.com (nslookup on Windows) and see whether it points at cname.chatgptgrow.com.
- The first minute or two after saving can still fail — the certificate is being issued.
If it stalls
It stays on “Waiting for you to add this record”
Check that the record is in the DNS of this domain and that the name prefix matches what you entered here, then use Check again on the card. If you changed nameservers recently, wait for that to take effect first.
The record went on the wrong domain, or the domain is misspelled
The record only works on a domain whose DNS you control. If the provider named on the card is not the one you use, re-check the spelling — one letter off and it is somebody else’s domain, where no record you add will ever take effect.
You left Cloudflare on orange (Proxied)
Switch it to DNS only. On orange, your cache and security settings run in front of ours, and after publishing you may keep seeing a cached page.
The target was pasted as a whole line
Only cname.chatgptgrow.com belongs in that field. Some panels reject anything longer, and blog CNAME cname.chatgptgrow.com is not a value.
You entered a bare domain (example.com)
Use a subdomain such as blog.example.com. A bare domain cannot point here, and a CNAME cannot be created on it anyway.
The card says “Needs attention” with an English message
That text comes from Cloudflare, and it usually means certificate validation kept failing. Check that the record is still there and unchanged, then use Check again. If you moved DNS providers, delete this domain and add it again.
You want a different domain
One brand can hold one custom domain at a time. Remove the current one first, then add the new one — the blog address falls back to ours in between.
My blog → Custom domain