Insights › Builder guides

Why your Lovable app isn't showing up on Google

Lovable apps created since 13 May 2026 render on the server; older ones render in the browser and rely on Lovable serving pre-rendered copies to verified crawlers. Here's what each receives, how to check it in 30 seconds, and the five fixes in the order that matters.

· 7 min read

The short version

Per Lovable's FAQ (docs.lovable.dev/introduction/faq, checked 15 November 2026), apps created on or after 13 May 2026 are server-rendered (TanStack Start), and older apps render in the browser but Lovable serves pre-rendered copies to verified search engines, social preview bots and AI crawlers. If your app still isn't showing up, check what an ordinary request receives and fix what the crawler receives, not what you see.

What a crawler receives depends on when your app was created

Lovable apps created on or after 13 May 2026 are server-rendered, so the first response already contains your content. Older apps are React single-page apps that render in the browser: an ordinary request gets one small HTML file with an empty root element, and the browser fills it in by running JavaScript. Lovable serves pre-rendered copies of those older apps to verified search engines, social preview bots and AI crawlers, so the verified ones are not meant to see the empty shell.

A crawler that is not on Lovable's verified list, and any plain request such as curl, still gets the shell. Google *can* render JavaScript, but on a second pass that can lag days behind, and some AI crawlers don't run JavaScript at all. For an older app, an ordinary request looks like this:

what an ordinary request downloads from an older apphtml
<!doctype html>
<html>
  <head><title>Vite App</title></head>
  <body>
    <div id="root"></div>
    <script src="/assets/index-a1b2c3.js"></script>
  </body>
</html>

No headline, no copy, no links, and a default Vite App title. If a crawler is served this, there is nothing on the page to index, so nothing ranks.

Check what an ordinary request receives in 30 seconds

Don't trust the rendered page in your browser — check the raw response. Two ways:

  1. 1

    View source, not inspect

    Open your live app, then use View Page Source (Cmd/Ctrl+U). This shows the HTML the server sent, before JavaScript. Inspect Element shows the rendered DOM, which hides the problem.

  2. 2

    Fetch it like a crawler

    Run curl -s https://yourapp.com | head -40 in a terminal. If you see an empty <div id="root"> and little else, that's what an ordinary request gets, and what any crawler outside Lovable's verified list will get too.

Search Google for site:yourapp.com. Zero results (after the app has been live a week or two) confirms it: nothing has been indexed.

The five fixes, in the order that matters

Do these top to bottom. The first one is the difference between invisible and indexable; the rest compound on it.

1. Serve real HTML (pre-render or SSR)

The root fix is to send content in the first response. A newer, server-rendered Lovable app already does. For an older app, put your marketing and content pages on static HTML or server-side rendering so the title, headings and copy are present before JavaScript runs. A logged-in app dashboard can stay client-rendered — it's the public, shareable pages that need to be crawlable.

2. Set a real title and meta description per page

Vite App is not a search result anyone clicks. Give every public page a specific <title> and <meta name="description">, and an Open Graph image so shared links don't unfurl blank.

html
<title>Split expenses with friends — Tabby</title>
<meta name="description" content="Track shared bills, settle up in a tap, no signup for guests.">
<meta property="og:image" content="https://yourapp.com/og.png">

3. Generate a sitemap.xml

A sitemap lists your indexable URLs so Google doesn't have to discover them by luck. Generate one, list your public routes, and reference it from robots.txt. Without it, a JavaScript app with few inbound links can stay undiscovered indefinitely.

4. Set a canonical tag on every page

A canonical tag tells Google which URL is the real one when the same page is reachable at several addresses (with and without www, with tracking parameters, trailing slashes). Missing canonicals split your ranking signals across duplicates.

The rules are worth getting exactly right — see Canonical tags: the rules that actually matter.

5. Verify in Search Console and request indexing

Add the site to Google Search Console, submit the sitemap, and use URL Inspection to request indexing on your key pages. Search Console is also where you'll see whether Google rendered the page or gave up on the empty shell.

Symptom to cause to fix

What you seeThe causeThe fix
site:yourapp.com returns nothingCrawler was served an empty HTML shell, nothing to indexPre-render / SSR (fix 1)
Ranks for your brand name onlyOnly the homepage got rendered and indexedSitemap + per-page HTML (fixes 1, 3)
Link previews are blankNo title, description or OG imagePer-page metadata (fix 2)
Duplicate URLs competingNo canonical tagCanonical per page (fix 4)

How long until it ranks

Once real HTML is served and the sitemap is submitted, indexing usually starts within days. Ranking for anything competitive takes longer and depends on links and content — but you can't rank at all while the crawler gets a blank page, so serving crawlable HTML is the step that unblocks everything else.

Every fix above maps to a check Actuant runs against your deployed app. It loads the live URL in a real browser, reads the pre-JavaScript HTML an ordinary request receives, and returns each of these as pass or fail with the exact line to change.