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.

Why does my domain show a 404 or 403 error?

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.

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.

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 aren't my latest changes appearing live?

Last checked 31 Aug 2026

Short answer

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.

Two separate causes, same symptom

"Changes not appearing live" almost always comes down to one of two things:

You haven't republished. Every chat edit updates Preview immediately, but the live URL only changes when you hit Publish again. Lovable doesn't auto-publish on every message.
Caching. Browsers, and sometimes intermediate CDNs, cache pages and assets. A visitor (or you) can be looking at a stale copy even after a successful republish.

Steps to fix

Open the Publish panel and confirm the latest deploy timestamp is after your last chat change. If not, click Publish again.
Hard-refresh the live page (Ctrl/Cmd+Shift+R) or test in a private window.
If you're on a custom domain, allow a short window for DNS/CDN caches to catch up after a fresh publish — this is usually seconds to minutes, not hours.
Ask other people who reported the issue to also hard-refresh; end users are the most likely to be stuck on a cached copy.

What usually goes wrong

Assuming Preview = live. They're deliberately decoupled so you can experiment safely before shipping.
Publishing from an old browser tab that still has an earlier project state loaded — refresh the editor tab itself before republishing.
Confusing "Version history" (which affects what's in the editor/chat) with "Publish" (which is what goes live). Reverting a version doesn't republish automatically; you still need to hit Publish.

Verifying it worked

After republishing and clearing your cache, check the live URL's page source or a specific new element you added to confirm it's genuinely serving the new build, not just visually similar.

Related: why does my published site look different from preview covers the same root causes from the opposite angle.

Sources

Publish your Lovable project

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.