SHIPPING
Lovable Custom Domain Setup and DNS Checks
Connect the address to the published project, then confirm the hostname and HTTPS separately. Use the DNS records shown for your domain; another project’s records are not a template.
On this page
LovablePublic URL → DNS records → HTTPS
01Domain registration stays with the registrar when connecting an existing domain.
02Ownership verification and certificate readiness can complete separately.
03A failed recheck alone does not prove a working domain stopped serving.
Start with one practical task
Write down the desired host and the records the project provides. After making the changes, test the custom address in a new session and check where the other host variants lead.
Prepare access before changing DNS
The documented setup requires project editing permission and access to the domain's DNS settings. Connecting an existing domain does not transfer its registration away from your registrar.
Use the records supplied for your domain
Lovable supports automatic connection through Entri and manual DNS setup. For manual setup, use the exact records shown by your project's domain flow. Avoid copying another project's addresses or deleting unrelated mail records.
Check the live result before troubleshooting
Ownership verification and HTTPS readiness may complete separately. Confirm the intended hostname loads the published app. Read the reported status before changing DNS; Lovable notes that a failed recheck alone does not establish that a working domain has stopped serving.
A few more details
Does connecting a domain automatically make it rank?
No. The public page still needs useful content, crawlable links and appropriate indexing settings. A working hostname is a deployment result, not evidence of search visibility.
Sources & maker notes
This guide is based on the cited documentation and maker sources. vibeforthat has not run an independent installation or end-to-end product test for this article.
Related guides & projects
View allLovable SEO Checklist for Published Apps
Check the published page before adding a rendering workaround. Lovable’s newer and older stacks have different native rendering paths; the next work is useful content, clear URLs and links that lead to them.
Read more
SaaS Launch Checklist for the First Customer Journey
Before announcing the product, walk through what the first customer will do—and what happens when it fails. Cover account access, paid states, recovery and the public domain with observable checks.
Read moreSaaS SEO Checklist for Pages, Indexing and Links
For a new product, make a few useful public pages easy to understand and find. Give each URL a distinct answer, check indexing controls and connect related pages before expanding the content library.
Read moreLovable vs Bolt for Building the Same App
Decide by the app you need to ship and the services you will maintain afterward. Both offer GitHub integration; moving source code still leaves data, identities and deployment to account for.
Read more