Lovable signup confirmation email not arriving: how to check

When new users of a Lovable app never get the confirmation email, check the email logs, the spam folder, whether email confirmation is on, the hourly email limits, your sender domain status, and the link the email points to.

Short answer: open More, Emails, Analytics and logs in your Lovable project and look up the address that did not get the email. If the log shows it was delivered, the problem is the inbox: check spam and promotions. If it shows a failure or nothing at all, check that email confirmation is on, that the workspace has not hit its hourly email limit, that your custom sender domain is not marked Offline, and that the confirmation link points to your live domain and not the preview.

Step 1: read the email log

Per Lovable's docs, More, Emails, Analytics and logs shows sent, delivered and bounced emails and an activity log per project with an error message for each failure. Search for the test address.

Delivered: Lovable did its part. Go to step 2.
Bounced or failed: read the error. Go to steps 3 to 5.
Not listed: the email was never requested. Go to step 6.

Step 2: the inbox

Check spam, promotions and any quarantine your provider keeps. Sign up again with a Gmail and an Outlook address to see whether one provider filters you. If emails go to spam, a custom sender domain with its records in place usually helps.

Step 3: hourly limits

Lovable's docs list hourly limits per workspace, separate for app emails and auth emails, that depend on your plan, and say new emails are rejected until the hour resets once a workspace hits its limit. Auth emails also have a per-project "Rate limit for sending emails" setting. If many people sign up at once, after a launch post for example, this is a likely cause.

Step 4: sender domain status

If you send from your own domain, Lovable keeps checking its DNS records and marks the domain Offline if they change or are removed. Restore the TXT and NS records the setup asked for (add them to your DNS zone; Lovable's docs say not to replace your nameservers at the registrar), then choose Check again under Project, Settings, Domains.

Step 5: auth emails need the built-in backend

Lovable's docs say authentication emails are sent through Lovable Auth and need the built-in backend. If your project uses your own Supabase project, its auth emails follow that Supabase project's email settings, so check the auth logs and SMTP settings there.

Step 6: was the email ever requested?

If nothing is in the log, the signup did not ask for a confirmation email. Check that email confirmation is turned on for your app's auth. Then sign up on the published URL in a private window: the editor preview may already be signed in. Watch the browser console for errors when you press the button.

Step 7: the link inside the email

When the email does arrive, click the link on a phone. It should open your live custom domain and land on a useful page, not the editor preview, a 404 or a blank screen. A broken link feels to the user like an email that never came. Our guide to why Lovable and Base44 signup flows break lists the other common breaks.

Where Persqo helps

You can run these checks yourself. Persqo runs the signup for you as a stranger, again and again:

Paste the Persqo prompt into Lovable and your app gets a Persqo admin page. An AI visitor walks through signup on the live app on desktop and mobile, and each finding comes with screenshots, a replay and a fix prompt; Open in Lovable puts it in your project's chat and you press send.
Persqo fills in forms but does not submit them unless you opt in. There is no verification step for you: Persqo confirms the site is yours in the background. With that opt-in it completes the signup, so you see the confirmation step a real user sees.
One click: the Persqo fix runtime the prompt adds to your Vite build applies the home page title and description, business and FAQ schema, the viewport tag and llms.txt, each with Undo, live the next time you publish.
Lovable syncs with GitHub both ways. Connect the same repository and Persqo opens a pull request for file fixes such as llms.txt and robots.txt. You merge it; Persqo never merges.

Sources

Custom emails, Lovable docs, checked November 6, 2026
Email FAQ, Lovable, checked November 6, 2026

Last updated: November 6, 2026.

Questions people ask

Where can I see whether Lovable sent the email?

Per Lovable's docs, under More, Emails, Analytics and logs. It shows sent, delivered and bounced emails and a per-project activity log with the error for each failure.

Is there a limit on Lovable auth emails?

Yes. Lovable's docs list hourly limits per workspace, separate for app emails and auth emails, and they depend on the plan. When a workspace reaches a limit, new emails are rejected until the hour resets.

My sender domain shows Offline. What now?

Lovable marks a sender domain Offline when its DNS records change or disappear after verification. Restore the NS or TXT records, then choose Check again from the sender's menu under Project, Settings, Domains.