Lovable Custom Domain Not Working: Fix by Status
A Lovable domain problem is easier to fix when you match the visible status to publication, verification, DNS, proxy, IPv6, or SSL behavior.
Publish the project first, then compare the DNS records at your provider with the exact records shown in Lovable. Keep the supplied verification records unchanged, disable proxying while verification is pending, remove conflicting AAAA records when the wrong site loads, and allow DNS time to propagate. Custom domains require a paid plan under Lovable’s current documentation.
This troubleshooting guide follows Lovable’s documented domain states rather than assuming that every project deploys through another host. It covers Pending, Ready, Verifying, Live, wrong-site routing, SSL, primary-domain redirects, and the final SEO checks after recovery.
Quick Questions
Lovable may still be waiting for its exact A and verification records. Modified records or an enabled proxy can prevent verification and SSL issuance.
Lovable documentation identifies conflicting IPv6 AAAA records as one possible routing cause. Review all records for the hostname.
Yes. A correctly configured domain can show Ready but will not serve the project until it is published.
Check your website in under 30 seconds for free.
Run a quick AI visibility scan to uncover crawl access, sitemap, robots.txt, and AI search readiness issues.
Start free scanMain Explanation
Start in Project Settings → Domains and read the state. Pending can mean registration or automatic setup is still running. Ready means DNS is correct but the project is not published. Verifying means Lovable has not confirmed the manual records. Live means Lovable considers the connection and SSL active, so a remaining problem may be browser cache, routing, or application behavior.
If you bought the domain through Lovable, much of the DNS and SSL setup is automatic. Confirm registrant email verification and use Check status if setup exceeds the normal window. If you connected a domain from another provider, use only the records Lovable displays for that project; do not copy IP addresses or CNAME targets from an unrelated tutorial.
During manual verification, do not alter the supplied A record or place a CDN proxy in front of it. Lovable says proxying can prevent ownership verification and certificate issuance. Use DNS-only mode until the domain becomes Live. Advanced reverse proxy or CDN setups should follow Lovable’s separate instructions after the base domain works.
If the wrong website or an outdated version loads, inspect all A, CNAME, and AAAA records. Remove records left by an old host when they conflict with the current setup. Lovable specifically documents AAAA records as a cause of traffic bypassing the intended destination.
DNS changes are distributed, not instant. Check authoritative and public resolver results instead of refreshing only one browser. Lovable states that propagation can take up to 72 hours in some cases. If the exact records are visible globally and the status remains stuck, remove and re-add the domain or contact support with the status and DNS evidence.
Once Live, set the intended host as primary. Test apex, `www`, and the default Lovable URL. They should redirect consistently and the page canonical should use the primary host. Update OAuth callbacks, email links, analytics, sitemap URLs, and Search Console properties that still refer to the preview domain.
Finish with a crawl check. Open robots.txt and sitemap.xml on the primary host, verify HTTPS and the canonical, and scan the final URL with TruboRankAI. Domain connectivity is not the same as indexing, but fixing the host correctly prevents duplicate versions and broken discovery paths.
Practical Steps
- Confirm the plan supports custom domains and publish the project.
- Read the exact domain status in Lovable.
- Copy the project-specific DNS records without modification.
- Disable proxying during verification.
- Remove conflicting legacy or AAAA records when appropriate.
- Wait for propagation and verify with a DNS lookup.
- Set a primary domain and test every host redirect.
- Update canonical, sitemap, callbacks, and Search Console.
Get scan-based SEO advice from the AI SEO Consultant.
Turn your page context into practical SEO, AEO, GEO, and AI search recommendations you can act on.
Try the consultantUse the free AI visibility tools now.
Explore free tools for keyword ideas, AI visibility checks, answer-ready content, and discoverability signals.
Open free toolsFAQ
How long can Lovable DNS take?
Many changes complete quickly, but Lovable notes that DNS propagation can take up to 72 hours. Check whether records are correct before assuming delay.
Should I point Lovable to Vercel records?
Not unless Lovable itself gives those records for your setup. Use the exact values shown in your Lovable domain settings.
Why is HTTPS still pending?
SSL issuance usually waits for correct DNS and successful verification. A wrong record or proxy can keep the certificate from being issued.