How to Test a Lovable Site After Publishing: A Step-by-Step Checklist

Updated 19 Oct 2026

Check your app now: free 30-second health check

Paste your live URL. We'll show what visitors and Google actually see. No signup.

Passive check only. We never submit forms or log in.

You clicked Publish, Lovable said Your website is live, and everything looked fine in the preview. That doesn't yet tell you what a real visitor gets. This checklist walks through what to test on your published Lovable site, in order, so you find the broken signup form or dead checkout button before your visitors do. The full run takes about half an hour the first time and a few minutes after each later publish.

Why testing the preview isn't enough

Lovable's preview docs describe the preview as your staging environment: it always runs your latest work, while visitors see the published version, a snapshot that only changes when you publish. The publishing docs say the same thing from the other side: the live site keeps showing the version you published, and later changes stay off it until you publish again.

Three more differences matter for testing:

  • Lovable's own browser testing checks the preview, not your live URL. The browser testing docs say it always runs against the preview of the project you're working on.
  • You're not a normal visitor. In the editor you're usually signed in as the owner. Real visitors arrive signed out, on a different address, often on a phone, sometimes with old files cached.
  • The data is shared. The preview docs note that the preview and your published site share the same backend and data. Anything you create while testing is real, so use test accounts and clean up afterwards.

If the live site is already behaving differently from the preview, start with Lovable Site Works in Preview but Not When Published? Find the Difference. This page is the routine check you run after every publish.

Before you publish: let Lovable test the preview

Use Lovable's built-in tools first, because they're quick and catch a lot. The testing overview explains that browser testing clicks buttons, fills forms, moves between pages and reads console logs and network requests. Ask in the project chat, for example:

Use browser testing to verify the sign-up flow works.

Two tips from Lovable's docs: build first and test in a follow-up prompt, rather than asking for a big change and a test in one message; and say clearly if there are buttons or areas the test should not click. When the preview passes, publish, then do the steps below on the live URL.

Set up a clean test

  • A private window on your computer, with DevTools open (F12). Keep the Console tab visible for red errors and the Network tab for failed requests, with "Preserve log" ticked so redirects don't wipe the list.
  • Your phone on mobile data, not your office Wi-Fi.
  • A test email address you can read, for example a plus address such as you+test1@yourdomain.com, so every signup is a brand-new user.
  • A short list of your key flows: homepage, main pages, signup, login, password reset, your main form, and checkout if you sell something.

Step 1: confirm the publish finished and you're on the right version

  1. The Publish dialog shows Your website is live for a first publish or Your website was updated after later changes. A Publishing failed or Fix build errors message means nothing new reached visitors.
  2. Look at the Publish button. Lovable shows a small dot on it when you have changes that are newer than the live version.
  3. Open the exact published address. The publishing docs point out that your lovable.app address uses the project's URL subdomain, which can differ from the project's display name.
  4. Check one thing you just changed. If it isn't there, do a hard reload (Ctrl+Shift+R, or Cmd+Shift+R on Mac) before assuming the publish failed.

Step 2: load every public page as a stranger

In the private window, visit each page from your menu and footer. For each one, check:

  • the page shows real content, not a white screen or a spinner that never stops
  • no red errors in the Console
  • no failed requests (4xx or 5xx) in the Network tab
  • images, fonts and icons load

Then type a deeper address directly into the bar, for example /pricing, and press refresh on it. A page that works when you click to it can still fail when loaded directly. If it does, see 404 when you refresh a page? Add an SPA rewrite. Also try a made-up address such as /this-does-not-exist: you want a friendly "not found" page, not a blank screen.

A white page with a console error about a missing URL or key usually means a setting didn't reach the published build. See Blank page after deploy? Check your production env vars.

Step 3: check every address people will use

Most sites can be reached at more than one address. Lovable's custom domain guide recommends testing in a private window and checking that:

  • your domain shows your site with the padlock in the address bar, so HTTPS is active
  • your lovable.app address and the www version (when it's included) redirect to your primary domain
  • signing in and submitting a form work on the new domain

Try each address by hand: with and without www, and the lovable.app one. If one works and another doesn't, see Works on www but not without? Fix DNS.

Step 4: sign up and log in as a brand-new visitor

This is the flow that breaks most often, and the one you never see because you're already logged in.

  1. Sign up with a fresh test address.
  2. Check the confirmation email arrives, and that its link opens your live domain, not localhost or the preview address. If it points somewhere else, see Login emails pointing to localhost? Fix your auth redirect URLs.
  3. Log out, log back in, then refresh a page that needs you to be signed in. You should stay signed in.
  4. Request a password reset and follow the link through to the end.
  5. If you offer Google sign-in, try it on the live domain as well as the lovable.app address.

If any of these fail only on the published site, Supabase Auth Broke After Deploy? The Usual Suspects, in Order walks through the usual settings.

While you're signed in as the test user, open the pages that show data. Lists that look full to you as the owner can be empty for an ordinary account, because database rules decide what each user can see.

Step 5: submit every form and check the data arrived

A form that says "Thanks!" has only proved that the button works. For each contact, waitlist, booking or feedback form:

  1. Submit it with clearly marked test data, such as "TEST, please ignore".
  2. Check where the data should end up: the database table, your inbox, or the connected tool.
  3. Check any confirmation email reached the person who filled it in.

If the thank-you message appears but nothing arrives, see Form says thanks but nothing arrives? Test it live. Because the preview and your live site share data, delete the test entries afterwards.

Step 6: walk the money path

If you sell anything, follow the path a buyer takes:

  • the pricing page loads and shows the right prices
  • the buy button opens checkout, rather than doing nothing
  • checkout shows the right product and amount
  • after paying, the buyer lands back on your live domain, not on a preview address

Stripe's test cards only work in test mode. If your live site uses live keys, either stop at the checkout page or make one small real purchase and refund it from your Stripe dashboard. If the button does nothing or checkout errors, see Lovable Stripe Checkout Not Working? Find Which Link in the Chain Broke.

Step 7: test on a real phone

The preview's device toggle is a good first look, but a real phone on mobile data catches more: slow connections, the on-screen keyboard hiding a button, a menu that won't open, text too small to tap. On your phone, open the homepage, use the menu, and complete signup or your main form once.

Step 8: check what Google and link previews see

  • Open your homepage, view the page source, and check the title and description are the ones you want.
  • Open /robots.txt and /sitemap.xml on your live domain and check they load.
  • Paste your link into a chat or social post draft and check the preview card shows the right title and image. If it's blank or wrong, see Link previews blank or wrong after launch? Fix your Open Graph tags.

The publishing docs also suggest running Lovable's SEO and AI search review again after you publish publicly, because some of its checks only run against the published site. If your pages still don't appear in search after a while, see Lovable Site Not Showing on Google? Here's How to Find the Real Cause.

Step 9: retest after every publish

Each publish replaces the live copy of your site. A prompt that changed one page can quietly break another, so keep a short version of this checklist and run it every time:

  1. Hard-reload the homepage in a private window: content shows, no red console errors.
  2. Sign up or log in once with a test account.
  3. Submit your main form once and check the data arrived.
  4. Open checkout, if you have one.

If a publish breaks something important, Lovable's version history lets you revert the project to an earlier version. Then publish again so visitors get the working copy, and fix the problem calmly in the preview.

For a list of the things that most often break on published Lovable sites, see the Lovable site health check.

Catch it before your users do

You test right after you publish; your visitors use the site every day after that. Run the free FlowCanary check on your live URL after each publish: it loads the published site like a first-time visitor and reports pages that fail to load, console errors, failed requests, broken links and what Google sees, with a fix prompt for each finding. It's a passive check, so it never logs in or submits forms; steps 4 to 6 still need you. For ongoing coverage, FlowCanary offers Daily monitoring of your signup, login and checkout (in development; founding spots $19/month, price locked for life, full refund on request any time before it launches).

Further reading

FAQ

Does Lovable test my published site for me?

Not directly. Lovable's browser testing runs against the preview of your project, not the published URL. Use it before you publish, then check the live site yourself in a private window.

Why doesn't my live site show my latest changes?

The published site is a snapshot of the version you published. Click Publish, then Publish changes, and hard-reload the live page. A dot on the Publish button means there are changes newer than the live version.

Is it safe to test on my live site?

Yes, with care. The preview and the published site share the same backend and data, so use test accounts, mark test entries clearly and delete them afterwards. Avoid real customer details.

Do I need a custom domain to test my site properly?

No. You can test everything on your lovable.app address. If you add a custom domain later, test again on it, because sign-in, payments and redirects can behave differently on a new domain.

How often should I test my published site?

Run the full checklist after your first publish and after big changes. Run the short version (homepage, login, main form, checkout) after every publish.

What should I do if something broke after publishing?

Write down what you saw and any console error, revert to the last working version in version history if visitors are affected, publish again, then fix the problem in the preview and retest before the next publish.

Related guides

Run the free 30-second check

Back to the FlowCanary homepage

FlowCanary on SaaSHub