Lovable gets you from idea to a published app fast. The preview working doesn't mean the live app works for a stranger on a phone, or that Google can read it. These are the problems we see most often once a Lovable app goes live, and how to check for each one.
1. The app isn't showing up on Google
Lovable's docs say only publicly published apps can appear in search. Unpublished projects, projects with restricted website access, and branded workspace URLs never do. After that, the usual causes are a stray noindex, a missing sitemap, or no inbound links on a brand-new domain.
→ Full walkthrough: Lovable app not showing on Google?
2. Older projects: crawlers and the "blank page" question
Per Lovable's docs, apps created from May 13, 2026 use TanStack Start with server-side rendering. Older React + Vite apps get on-request pre-rendering, but only for verified crawlers such as Google, Bing and the major AI search crawlers. Third-party tools that aren't verified crawlers may see an empty single-page-app shell instead. → Background: Why is my React SPA not indexed?
3. Login works in preview, breaks on the live domain
Email confirmation links go to localhost, Google sign-in bounces, or users loop back to the login page. The cause is almost always Supabase's Site URL or Redirect URLs, especially after you connect a custom domain.
→ Fix it: Supabase auth broke after deploy
4. Stripe checkout does nothing, or payments don't update the app
Popup blockers, test and live keys mixed up, missing function secrets, or a webhook returning 401 or 400. → Step by step: Lovable Stripe checkout not working?
5. Every page has the same title
If your routes all share one <title> and description, Google may treat them as duplicates. Each public page needs its own title, description and self-referencing canonical. Watch for canonicals that still point to lovable.app after you move to a custom domain.
6. Something a prompt changed quietly
Each prompt can change code you never read. A link in the nav now points to a page that was renamed, a form no longer renders, or a console error appears on load. Nothing alerts you until a user complains.
What Lovable already checks, and what FlowCanary adds
Lovable's Quick security scan runs on every publish and covers database access rules, dependency vulnerabilities and unauthenticated MCP servers. Its Deep scan reviews your code. Its browser testing runs against your project preview. Its SEO & AI review checks search readiness.
FlowCanary checks your live, published URL from the outside, the way a first-time visitor and Google see it. It's a quick second opinion, not a replacement for any of those.
What FlowCanary's free check looks at
- Homepage status, speed, redirects and HTTPS
- Key pages found: signup, login, pricing, checkout, contact, privacy, terms
- Broken links on your homepage
- Raw HTML vs a real browser, with a "Google may see a blank page" warning
- robots.txt, sitemap,
noindex, and a missing title, description, canonical or og:image on your homepage - JavaScript console errors and failed requests on your homepage and key pages
- Forms that appear after load, and pages that overflow on phones
FlowCanary looks for hosting and code fingerprints to tell which builder you used. When it spots Lovable, every issue comes with a paste-ready prompt for Lovable's chat. The prompts work when pasted into Lovable's chat either way.