Skip to main content
A custom domain lets you use your own domain or subdomain for your published Lovable project. When you connect a custom domain, visitors can access your app using a branded URL instead of the default xxx.lovable.app project URL. Connecting a custom domain improves your site’s:
  • Brand identity - look more trustworthy and professional
  • Search engine visibility - better SEO and discoverability
  • Memorability - easier for users to share and remember

​
Prerequisites

To connect a custom domain, ensure that:
  • You are on a paid Lovable plan.
  • Your project is published. See Publish your app for more information.
  • You own a domain name. You can purchase one directly within Lovable (through IONOS).
  • You have access to the DNS settings for the domain or subdomain you want to connect. Ownership verification requires adding DNS A and TXT records provided by Lovable during setup.
  • There are no AAAA records set for the domain you are connecting. Having an AAAA record can interfere with domain setup and cause traffic to be routed incorrectly.
Note on domain terminology
  • DNS determines where your domain points on the internet.
  • A DNS provider is the service where you manage DNS records for your domain, such as A, TXT, or AAAA records.
  • An A record points a domain or subdomain to an IP address.
  • A TXT record is used to verify domain ownership.
  • An AAAA record points a domain to an IPv6 address and can interfere with domain setup if present.
  • An SSL certificate enables HTTPS and allows browsers to securely connect to your site.

​
Connect a custom domain

You can connect a domain to your published Lovable project using automatic setup (powered by Entri) or manual DNS configuration. Both methods require verifying ownership of your domain. You can connect a domain from two locations:
  • Project → Settings → Domains
  • Publish modal → Custom domain (can be done after publishing your project)
Follow the steps below to connect a custom domain:
  1. Click Connect domain.
  2. Enter your domain or subdomain (for example, yourdomain.com or blog.yourdomain.com), click Connect domain, then click Continue.
    When adding a domain, Lovable does not automatically add the www subdomain. You can add it separately if you want both.
  3. Now, you can connect your domain in two ways:
    • Automatic setup with Entri: Select your domain provider from the list, log in, and authorize Entri to update your DNS records.
    • Manual setup: If your DNS provider is not listed, scroll to the bottom of the Select your domain provider modal and choose Go to our manual setup. Copy the A record and TXT record and input them directly into your domain registrar or DNS provider.
      Note about the A record host nameWhen connecting a domain, we suggest a default host name for the A record. However, some DNS providers handle this differently. Depending on your provider, the host name may need to be:
      • @
      • left blank
      • or set to your domain name (for example, example.com)
      For example, Amazon Route 53 requires the host name to be left blank or set to the domain name.
  4. Click Done. Wait for verification and SSL certificate to be issued. When complete, the domain will become Live and your Lovable app will be live at your custom domain.
DNS changes may take up to 72 hours to propagate, though most updates are live within a few hours.

​
Advanced: Using a CDN or reverse proxy

Lovable can be used behind your own CDN or reverse proxy, such as Cloudflare, CloudFront, or Fastly. A CDN (Content Delivery Network) or reverse proxy is a service that receives requests for your domain and then forwards those requests to your app. It sits between your users and Lovable, and can be used to cache responses, add security controls, or customize how traffic is routed. When Allow traffic through a CDN or proxy is enabled, you are responsible for configuring and maintaining this setup after domain verification. Lovable does not configure, validate, or monitor your CDN or proxy. This option is available under Advanced when connecting a custom domain. If you are using a CDN or reverse proxy, follow these steps:
  1. Expand Advanced and enable Allow traffic through a CDN or proxy when connecting a domain.
  2. Complete the initial domain setup as described in Connect a custom domain.
    • If using the Automatic setup with Entri: You don’t need to change anything during the initial domain setup. Your domain’s A record will automatically point to Lovable’s IP address.
    • If using the manual setup: Ensure your domain’s A record points directly to Lovable’s IP address and that proxying is disabled (DNS-only).
  3. Wait for the domain status to show Live.
    Lovable verifies the domain and issues SSL certificates during this step.
  4. Update your domain’s A record to point to your CDN or proxy.
    Traffic will now flow through your infrastructure before reaching Lovable.

​
Domain statuses

Domains have clear statuses that reflect verification progress, DNS propagation, SSL certificate readiness, and required user action.
StatusDescriptionUser action
UnpublishedShown only for your xxx.lovable.app project URL when the project is not yet published.Publish the project.
ReadyThe domain is ready but the project was unpublished. When published again, the status automatically becomes Live.Publish the project.
Action requiredThe custom domain setup was not completed.Click Complete setup to finish connecting.
VerifyingWaiting for DNS records to propagate.Click Check status to check the latest status and verify the DNS records.

Check that your A and TXT records are added correctly at your DNS provider, especially the full TXT value.
Unable to verifyDNS verification did not complete within one hour. This usually means your DNS records are incorrect or still propagating.

Note: DNS propagation can take up to 72 hours, although most updates are applied within a few hours.		Click Check status to refresh the status and re-verify your DNS records.

Check that your A and TXT records are added correctly at your DNS provider, especially the full TXT value.
Setting upVerification complete; SSL certificates are being issued.No action required; domain will automatically move to Live or Failed.
FailedOwnership verified, but SSL certificate could not be provisioned.Click Retry to attempt again.
LiveDomain is live and serving your project.No action required.
OfflineDomain was Live but DNS records are no longer valid. Your domain is no longer pointing to your project.Click Recover. Review displayed DNS records and update them at your DNS provider to reconnect your domain.
RemovedThis domain was removed because it was added to another project or DNS verification never completed (DNS records weren’t added correctly or didn’t finish propagating).Click Reconnect to connect the domain again.
You can remove a domain at any point regardless of its status.

​
Primary domain

Lovable allows you to set one domain as the primary domain.
  • The domain status must be Live in order to mark it as primary. Click the three dots menu next to your domain and click Set as primary.
  • The first custom domain you add to a project automatically becomes the primary domain (for domains added after October 29, 2025).
  • If a domain is primary, all other domains redirect to it.
  • Only one domain can be primary at a time.
  • You can unset the primary domain; in that case, all connected domains serve the project equally. Click the three dots menu next to your primary domain and click Unset as primary.

​
FAQ

Yes. When you connect a custom domain to your Lovable app, we automatically generate and install an SSL certificate for it. This ensures your site is served over HTTPS, keeping your visitors’ data secure and improving your site’s SEO ranking. If it hasn’t been issued after 72 hours, please reach out to Lovable Support.
Yes. You can buy a custom domain within Lovable through our partner IONOS. Go to Project → Settings → Domains and click Buy new domain to buy a domain through IONOS. This is available on paid plans only.
Yes, connecting a custom domain affects your SEO positively. A custom domain improves your site’s discoverability in search engines and makes it look more trustworthy to users.See Implement SEO and GEO best practices for more information.
Yes. You can connect a subdomain (for example, blog.yourdomain.com or app.yourdomain.com) instead of the root domain. When entering your domain in the setup flow, just include the subdomain you want to use.
Yes. You can connect multiple subdomains, but each one must be added and configured individually in Project → Settings → Domains. For example, you can connect blog.yourdomain.com, shop.yourdomain.com, and app.yourdomain.com.
You can see your connected domains in two locations:
  • Project → Settings → Domains - here you see all domains, regardless of their status
  • Publish modal - here you see all Live domains
Yes. As long as you can verify ownership, you can connect a domain or subdomain used by another project, even if the project has been deleted.
The domain status must be Live in order to set it as primary.Go to Project → Settings → Domains, click the three dots menu next to a Live domain, and click Set as primary.
Go to Project → Settings → Domains, click the three dots menu next to your primary domain, and click Unset as primary.
You can remove a domain at any time regardless of its status.
  1. Go to Project → Settings → Domains.
  2. Click the three dots menu next to your domain, click Remove, then click Remove again to confirm.
This will disconnect the domain from the project. Make sure to clear DNS settings in your domain provider to completely clear the connection.
Currently, there is no way to remove the xxx.lovable.app project URL from your project. However, you can add a custom domain and set it as your primary domain. This allows visitors to access your app from a branded URL instead of the default xxx.lovable.app project URL.
Yes, you need to add it separately, and it will be listed separately. The www subdomain is not included when you set up your domain.
This setting is not required for most custom domains. Lovable already serves your site through its own infrastructure. Enabling this setting without intentionally routing traffic through a CDN or proxy can cause domain verification failures, SSL certificate issues, or incorrect routing.Only enable this setting if your domain intentionally routes traffic through a CDN or reverse proxy, such as Cloudflare, CloudFront, or Fastly, before reaching Lovable. See Advanced: Using a CDN or reverse proxy for more information.

​
Troubleshooting

This usually means Lovable is still waiting for the correct DNS configuration or for changes to fully propagate.Try the following:
  • Use a DNS lookup tool like dnschecker.org to confirm that your domain resolves to the expected records. DNS changes can take up to 72 hours to propagate.
  • Go to Project → Settings → Domains and confirm the DNS records Lovable expects.
  • Clear your browser cache or test the site in an incognito window.
  • Try removing and re-adding the domain in Project → Settings → Domains.
This often happens when traffic is being routed incorrectly due to an IPv6 (AAAA) record.Check whether your domain has any AAAA records configured. An AAAA record can interfere with domain routing and cause traffic to bypass the expected destination.To resolve this:
  • Review your DNS settings at your DNS provider.
  • Remove any AAAA records for the domain.
  • Retry connecting the domain after the change has propagated.
During manual setup, Lovable provides the exact DNS records required for verification. These records must remain unchanged until verification is complete.If the provided A record is modified before verification finishes, Lovable cannot verify the domain or issue SSL certificates.While verification is in progress:
  • Do not enable proxying on the A record.
  • Do not point the A record to a CDN or reverse proxy.
If either of these happens, the domain remains in the Verifying state.To fix this:
  1. Disable proxying (DNS-only) on the provided A record.
  2. Ensure the A record points directly to Lovable’s IP address.
  3. Wait for the domain status to change to Live.
  4. If you are using a CDN or reverse proxy, such as with Allow traffic through a CDN or proxy, update the A record to point back to your CDN or proxy.