For a standard Lovable domain setup, use the A record Lovable provides — it’s required for domain ownership verification and SSL provisioning. A CNAME only applies if you’re intentionally routing traffic through Cloudflare or a similar proxy using Lovable’s advanced setup option.
Setting Up Your First Lovable Project?
Get your app built and your domain settings in front of you before diving into DNS records.
Why This Decision Matters
Every Lovable project starts on a default xxx.lovable.app URL. It works, but it carries Lovable’s branding, and search engines credit any SEO authority you build to lovable.app, not to you.
Connecting a custom domain fixes this — a branded URL, a free auto-provisioned SSL certificate, and SEO equity that stays under your own control. Custom domains require a paid Lovable plan and won’t serve your app until you publish your project.
Get the record type wrong, though, and you can end up with a broken site, an unprovisionable SSL certificate, and a launch delayed by up to 72 hours of DNS propagation. This guide covers exactly which record to use, when, and how to fix it if something goes wrong.
A Record vs CNAME: The Core Difference
An A record maps a domain directly to an IP address. When someone visits yourdomain.com, DNS looks up the A record and routes them straight to that server. A records work for root domains and subdomains alike, and it’s the record type Lovable uses by default for both purchased and manually connected domains.
A CNAME record maps one domain name to another domain name instead of an IP. It’s common for subdomains (www.yourdomain.com pointing to yourdomain.com) or for routing through a CDN — most DNS providers won’t let you use a CNAME on a root domain since it conflicts with MX and other record types.
Which One Lovable Actually Uses
- Standard setup, existing domain: Lovable provides an A record plus a TXT verification record. This is the default path for most users.
- Domain purchased through Lovable: Fully automatic — A records and TXT verification are created for you, nothing to configure.
- Advanced setup with Cloudflare or another proxy: The only scenario where Lovable issues a CNAME instead, via the “Domain uses Cloudflare or a similar proxy” option.
Buying a Domain Through Lovable
If you don’t already own a domain, this is the fastest path:
- Go to Domains. Project → Settings → Domains → Buy new domain. Requires workspace admin or owner access.
- Search for your domain. Prices show in USD. Most major gTLDs are supported, plus .ai, .io, .co, .me, and .tv.
- Review your order. Set the registration term (1–10 years), toggle auto-renew, and enter ICANN contact details carefully — these can’t be changed after purchase.
- Verify your email if prompted. Automatic if it matches your verified Lovable account email.
- Check out via Stripe. Lovable auto-registers the domain, creates the A and TXT records, provisions SSL, and connects both yourdomain.com and www.yourdomain.com.
Domains bought this way belong to the workspace, not a single project — manage them under Workspace Settings → Workspace Domains and connect any of them to any project at any time.
Connecting a Domain You Already Own
- Open Domain settings. Project → Settings → Domains → Connect domain.
- Enter your domain (e.g. yourdomain.com or blog.yourdomain.com) and click Connect domain to open the Entri configuration modal.
- Choose your setup method. Automatic setup via Entri detects your DNS provider and configures records for you. Manual setup shows the exact A and TXT values to copy into your provider’s panel.
- Add the records correctly. The host name may need to be @, blank, or the full domain depending on your provider — Route 53, for example, wants it blank or set to the domain name.
- Remove any AAAA records. This is the step most guides skip. Leftover AAAA records will misroute traffic and break the setup — delete them before or right after adding the A record.
- Verify and wait. Propagation can take minutes to 72 hours. Once verified, SSL issues automatically and status flips to Live.
One catch: connecting a domain you already own doesn’t add the www subdomain automatically. Add both yourdomain.com and www.yourdomain.com separately if you want both to work.
What Each Domain Status Means
| Status | What It Means | What to Do |
|---|---|---|
| Pending | Registration/DNS/SSL setup in progress | Wait. Click “Check status” if a warning appears. |
| Live | Fully configured and serving your project with SSL | Nothing — you’re done. |
| Ready | DNS and SSL correct, but project not published | Publish your project. |
| Action Required | Setup wasn’t completed | Click “Complete setup.” |
| Verifying | Waiting on DNS propagation | Check status periodically; verify A/TXT records. |
| Unable to Verify | Didn’t verify within an hour | Double-check both records; can take up to 72 hours. |
| Setting Up | Verified — SSL being issued | Wait; auto-resolves to Live or Failed. |
| Failed | Verified but SSL couldn’t provision | Click “Retry.” |
| Offline | Was Live, but DNS is no longer valid | Click “Recover” and fix DNS at your provider. |
| Removed | Removed — reused elsewhere or never verified | Click “Reconnect” to start over. |
Advanced Setup: Cloudflare or a Reverse Proxy
If you need traffic routed through Cloudflare, CloudFront, Fastly, or similar before it reaches Lovable, expand the Advanced section during domain connection and enable “Domain uses Cloudflare or a similar proxy.” Lovable then gives you a CNAME instead of an A record.
Critical warning: never enable Cloudflare’s proxy (orange cloud) on the A record before verification completes during a standard manual setup — doing so leaves your domain stuck in “Verifying” indefinitely. Only use the proxy option if you’re intentionally on the CNAME-based advanced flow from the start.
You’re responsible for configuring and maintaining your own CDN/proxy layer — Lovable doesn’t monitor or validate it, so any misconfiguration there affects your site’s availability directly.
Primary Domains and Multiple Subdomains
You can connect multiple domains and subdomains to one project, but only one can be primary at a time. The domain must be Live first — then Project → Settings → Domains → (three dots) → Set as primary. All other connected domains redirect to the primary automatically, which is the correct setup for SEO since it consolidates canonical authority.
You can connect different subdomains (blog.yourdomain.com, app.yourdomain.com, shop.yourdomain.com) to different projects in the same workspace, each configured individually — but the exact same domain can’t be attached to two projects at once.
Want This Set Up Correctly the First Time?
If you’re managing multiple client domains or just don’t want to troubleshoot DNS yourself, we handle full Lovable domain configuration end to end.
Troubleshooting Common Problems
Domain Never Becomes Live
Use a DNS lookup tool (dnschecker.org) to confirm your A record resolves to Lovable’s IP. Verify your TXT record matches exactly what Lovable requires under Project → Settings → Domains. Clear your browser cache or try incognito. If nothing works, remove the domain and re-add it.
Domain Shows the Wrong Site or an Old Version
Almost always an AAAA record silently overriding your A record. Check your DNS provider, delete any AAAA records tied to the domain, wait for propagation, then retry the connection in Lovable.
Stuck in “Verifying” During Manual Setup
Usually means the A record was proxied or modified before verification finished. Disable Cloudflare’s orange-cloud proxy mode, switch to DNS-only, wait for propagation, then recheck status.
SSL Not Issued After 72 Hours
If the domain is verified but SSL still hasn’t issued after 72 hours, that’s not normal — contact Lovable Support directly rather than continuing to wait.
SEO Impact of Connecting a Custom Domain
This is one of the highest-leverage SEO moves at launch. Every backlink to yourdomain.com builds your own domain authority instead of lovable.app’s.
Once your domain shows Live, run Lovable’s built-in SEO review (checks indexing, canonical URLs, sitemap, and metadata against the correct host), then verify the domain in Google Search Console and submit your sitemap — either via Lovable’s connector or directly in Search Console. Don’t skip this step; a correct-looking site in the browser doesn’t mean search engines have picked up the right signals yet. If you change your primary domain later, rerun the SEO review so everything re-checks against the new host.
When to DIY vs Hire It Out
If you’re comfortable logging into your DNS provider, copying a couple of record values, and waiting out propagation, the steps above are enough to handle a standard setup yourself.
Professional help earns its cost when you’re managing domains across multiple clients, your registrar has an unusual interface, you need a CDN/proxy layer configured alongside Lovable, your domain has existing email DNS records that can’t be disrupted, or a previous failed attempt has left things in an inconsistent state.
FAQ
Can I set up a domain before publishing my Lovable project?
Yes. You can buy or connect a domain at any time — it shows a “Ready” status instead of “Live” until you publish, then begins serving automatically.
Can I connect multiple domains to one Lovable project?
Yes. Connect as many domains and subdomains as you need, set one as primary, and all others redirect to it automatically for clean SEO consolidation.
Do I need a CNAME record for a standard Lovable domain setup?
No. Standard setups use an A record plus a TXT verification record. CNAME only applies if you’re intentionally using Lovable’s advanced Cloudflare/proxy setup.
Why is my domain stuck on “Verifying”?
Almost always because the A record was proxied (e.g. Cloudflare’s orange cloud) or modified before verification completed. Switch to DNS-only mode, wait for propagation, and recheck.
What’s the most commonly missed step in Lovable domain setup?
Removing leftover AAAA records. They silently override your A record and route traffic to the wrong place, and most setup guides don’t mention checking for them.
Ready to Launch on Your Own Domain?
Start building free, then connect your custom domain when you’re ready to go live.