QAlaunch

Lovable site not showing on Google: causes and fixes

A Lovable site usually stays out of Google for one of four reasons: the latest version was never published, the lovable.app address is still the one Google treats as canonical, the pages carry generic starter metadata with no sitemap, or an older React + Vite project serves crawlers a thin snapshot. Lovable can rank: projects created from 13 May 2026 are server-rendered with TanStack Start, and older ones are pre-rendered for verified crawlers. Publish, set your custom domain as primary, run the SEO & AI scan, connect Search Console and request indexing.

Opens your site in a real browser on desktop and phone. Free, about two minutes, no signup. Full report from $19.

What you'll see

You search Google for your brand or a phrase from your homepage and nothing comes up, or the only result is yourproject.lovable.app instead of your own domain. In Search Console the pages sit under "Discovered – currently not indexed" or "Crawled – currently not indexed", or URL Inspection reports that Google picked the lovable.app address as the canonical.

Why it happens

1. Nothing is actually live on the custom domain

If the project was never published, or the domain shows Ready in Project > Settings > Domains, the domain is configured but not serving a published build. Google cannot index a version that only exists in the editor.

2. Google prefers the lovable.app address

The lovable.app subdomain keeps working after you connect a domain, and Lovable redirects secondary domains to the primary with a 302 (temporary) redirect because it does not offer 301s between project domains. If the custom domain is not marked primary, Google can settle on the lovable.app URL and ignore yours.

3. An older React + Vite project serves a thin snapshot

Projects from before 13 May 2026 are client-rendered single-page apps. Lovable pre-renders them on request for verified crawlers, but content that loads late, such as text fetched from the database after a delay, can be missing from that snapshot.

4. Starter metadata, no sitemap

Every page can still share the title from the template, and Lovable creates robots.txt with each project but not always a sitemap. A robots.txt without a correct Sitemap: line leaves Google to discover pages on its own.

How to fix it

  1. Click Publish (or Update if it was published before) so the live build matches the editor, then open Project > Settings > Domains and confirm the custom domain reads Live, not Ready or Verifying.
  2. On the same Domains screen, open the three-dots menu next to your custom domain and choose Set as primary. The lovable.app address and any other domains will then redirect to it.
  3. Open More > Analytics, select the SEO & AI tab and click Run SEO scan. Work through the sitemap, robots.txt, metadata and canonical findings with Try to fix, then click Scan again to confirm they pass.
  4. On the Google searches card, click Finish setup to connect Google Search Console. Lovable adds the verification tag and submits the sitemap; if you changed domains recently, verify the new domain and resubmit the sitemap there.
  5. If the project predates May 2026 and holds important text that loads from the database, consider Upgrade to TanStack Start so every page is server-rendered. Nothing changes on the live site until you publish again, so test the preview first.
  6. In Search Console, run URL Inspection on the homepage and two key pages and click Request indexing. Then leave it alone for a week or two; repeated requests do not speed Google up.

Prompt to paste into Lovable

Make every public page SEO-ready for my custom domain https://example.com. Give each route its own <title> under 60 characters and its own meta description, a canonical URL on https://example.com (never lovable.app), and Open Graph tags. Generate /sitemap.xml listing every public route with absolute https://example.com URLs, and make sure robots.txt allows crawling and contains "Sitemap: https://example.com/sitemap.xml". Do not change page content or layout.

How to check it's fixed

  • Open https://yourdomain.com/robots.txt and https://yourdomain.com/sitemap.xml in a browser. Both should load, and every URL in the sitemap should start with your custom domain.
  • Press Ctrl+U (View Source) on two different pages and check that each has its own title, description and a canonical pointing at your custom domain.
  • After a couple of weeks, search site:yourdomain.com and look at the Google-selected canonical in URL Inspection; it should be your domain, not the lovable.app one.

What a QAlaunch scan shows for this

  • Missing or generic title and meta description in the rendered homepage, and whether a canonical tag is present and which host it points at.
  • A robots noindex tag left on the page, which keeps it out of Google no matter what else you fix.
  • Console errors or a blank render, the visitor-side sign that content depends on scripts that are failing.
  • It does not query Google's index, so it tells you whether the page is ready to be indexed, not whether Google has done it yet.

See exactly what a full report contains in the sample report.

Frequently asked questions

Can a Lovable site rank on Google at all?

Yes. Older advice that Lovable apps are invisible to search predates Lovable's own pre-rendering and the move to TanStack Start. New projects return fully rendered HTML on every request, and older ones serve verified crawlers a rendered copy, so you no longer need an outside pre-rendering service.

Why does Google show my lovable.app address instead of my domain?

Both addresses serve the same pages, and until the custom domain is set as primary and Google has recrawled, it may keep the first one it found. Set the primary domain, make canonicals point at it, resubmit the sitemap on the custom domain and give it time.

Should I upgrade my old project to TanStack Start just for SEO?

Only if your important content loads late or the SEO scan keeps reporting thin pages. A simple marketing site with text written straight into the components is usually captured fine by the crawler snapshot. Upgrade on a quiet day and test every route before you republish.

How long does indexing take after I fix everything?

Days for the homepage on a site Google already knows about, and often several weeks for a brand-new domain with no links pointing to it. Getting one or two genuine links from sites you already own or directories you belong to helps more than pressing Request indexing again.

Done for you · not automated

Rather have a QA engineer test it by hand?

If this is a site you're launching or handing to a client, I'll go through it by hand, including the Lovable-specific issues a scan can't reach, like logged-in flows.

$299one-time · 3 business days
  • Up to 10 key pages tested by hand, not a scan
  • Every flow a customer uses: forms, sign-up, checkout, booking
  • Real mobile and desktop browsers
  • A written report in plain language, with screenshots
  • A 15-minute call to walk you through it
  • 10 years of professional QA experience

Tell me about your site and I'll reply personally, usually the same day.

No payment now. I'll confirm scope and price first.

Related fixes

More for Lovable: all Lovable fixes · Lovable testing · 9 bugs every AI-built site ships with

Written by Waqas Ahmad, QA engineer with 10 years of professional testing experience. Last checked October 26, 2026.

Sources: Lovable docs: SEO and AI search · Lovable docs: custom domains · Axon Build: Lovable site not showing on Google