How do I publish a Lovable website?

Click Publish in the top-right of the Lovable editor; it deploys your current version to a live `*.lovable.app` URL (or your connected custom domain) in under a minute.

How do I connect my own domain to Lovable?

In Project settings, go to Domains, add your domain, and create the DNS records Lovable gives you (usually an A record or CNAME) at your domain registrar or DNS host — then wait for verification, which can take anywhere from minutes to a few hours.

Can I use a .com.au domain with Lovable?

Yes — Lovable's custom domain feature works with any domain you own, including .com.au, as long as you can add DNS records at wherever the domain's nameservers point.

How do I connect a Cloudflare domain to Lovable?

Add the DNS records Lovable gives you in Cloudflare's DNS panel, and set the proxy status to 'DNS only' (grey cloud) rather than proxied (orange cloud) so Lovable can verify and serve the domain correctly.

What DNS records does Lovable need?

Lovable shows the exact records to add when you connect a domain — typically an A record for the root/apex domain and a CNAME for `www` (or a subdomain), plus any verification record it asks for.

Why isn't my custom domain connecting?

Most failures come down to DNS records that don't exactly match what Lovable asked for, edits made in the wrong place, or not waiting long enough for DNS to propagate — check the records first, then give it time.

How long does a Lovable domain take to connect?

Usually a few minutes to a couple of hours once the DNS records are correctly added, but full global DNS propagation can technically take up to 48 hours in rare cases.

How do I connect www and non-www versions?

Add DNS records for both the root domain and the `www` subdomain in Lovable's Domains panel, then choose one as your primary — Lovable typically redirects the other to it automatically.

How do I choose my primary domain?

In Project settings → Domains, set which connected domain (e.g. root vs `www`, or which of several domains) is primary; Lovable serves and redirects other connected domains to that one.

Does Lovable provide SSL?

Yes. Every Lovable-published site gets HTTPS automatically, including the free lovable.app subdomain and any custom domain you connect through Lovable.

Why does my published site look different from preview?

Usually it's a stale cache — your browser or a CDN is showing an older published version. Hard-refresh, check you actually clicked Publish, and confirm you're viewing the live URL, not a cached preview link.

Why aren't my latest changes appearing live?

Most likely you haven't clicked Publish since the last edit, or you (or a viewer's browser/CDN) are looking at a cached copy of the old page.

How do I unpublish a Lovable project?

Open the Publish panel in your project and choose the unpublish/take-down option — this removes the live site while keeping your project and its code intact in Lovable.

How do I change the favicon?

Ask Lovable in chat to update the favicon, and upload or link the image you want — Lovable will swap the icon file and reference it in the page head for you.

How do I change the website title?

Ask Lovable to change the page title, or edit the tag in index.html directly in the Code editor — this is the text shown in the browser tab and search results.

How do I change the social sharing image?

Ask Lovable to update the Open Graph image, or edit the og:image meta tag in your page head and upload the image asset — this controls the preview card shown when your link is shared on social platforms.

Why does my domain show a 404 or 403 error?

Last checked 31 Aug 2026

Short answer

A 404/403 on a connected domain usually means DNS is pointed correctly but the app hasn't been published, the domain is linked to the wrong project, or the SSL/routing hasn't finished setting up yet — it's a different problem from DNS not resolving at all.

What's different about this from "not connecting"

If your domain shows a 404 or 403 rather than a browser error like "can't reach this site", DNS is actually resolving — the request is reaching a server, it's just not being routed to your live app correctly. That points to configuration, not DNS propagation.

Common causes

Project not published. A connected domain routes to your published app; if you haven't clicked Publish (or published since major changes), it can 404.
Domain attached to the wrong project. If you manage multiple Lovable projects, confirm the domain is listed under the intended one in Project settings.
Only one of www/non-www configured. You connected www.mydomain.com but visitors are hitting the bare mydomain.com (or vice versa), and only one route is set up.
SSL/certificate still issuing. A brief window between DNS verifying and the certificate being ready can produce errors.
Access restrictions. If you've password-protected or restricted the published app in Project settings, that can present as a 403 to visitors.

Steps to fix

Confirm the project is published (see how-do-i-publish-a-lovable-website).
Check Project settings → Domains shows the domain as connected, not pending.
Check both www and root variants — see how-do-i-connect-www-and-non-www-versions.
Check publishing/access controls in Project settings for password protection you may have forgotten was enabled.

Publish this project and confirm my custom domain mydomain.com is pointing at the published version, not a draft.

What usually goes wrong

People assume a 404/403 means DNS is broken and keep re-adding DNS records, when the real fix is publishing or reattaching the domain to the right project.

Sources

Was this answer helpful?

You might also need

GuideHow to Connect a Custom DomainPoint your own domain at a published Lovable project, with the DNS records explained in plain terms.