Builtiflow
Lovable + SEO

Why your Lovable app isn't showing up on Google

Lovable builds fast, working products — but the default output is a single-page React app that renders in the browser, not on the server. Search engines and AI crawlers frequently see nothing at all.

Symptoms

How to tell if this is happening to you

  • Your app doesn't appear in Google indexing at all, even weeks after publishing — searching "site:youryourapp.lovable.app" returns nothing
  • View Page Source shows only an empty <div id="root"></div> with no real text inside it
  • Every page has the same generic title ("Vite + React" or your project name) in browser tabs and search results
  • Sharing your link on Slack, X, or LinkedIn shows no preview image or description
  • Google Search Console shows pages as "Discovered — currently not indexed" or "Crawled — currently not indexed"
Root cause

Why this happens with Lovable specifically

Lovable generates a Vite + React single-page app. Every route is rendered client-side: the server sends one nearly empty HTML file with a `<div id="root">`, and JavaScript fills it in after the browser downloads and runs your bundle.

Googlebot and Bing can execute some JavaScript, but it's slower, rate-limited, and unreliable for content that depends on client-side data fetching. Most AI crawlers — the ones powering ChatGPT Search, Perplexity, and Claude — don't render JavaScript at all. They read the raw HTML response, which for a default Lovable app is functionally empty.

This is invisible to you because your browser runs the JavaScript and shows you a finished page. It's only visible when you look at what a crawler actually receives.

The fix

What actually fixes it

  • 1. Move the public marketing pages (home, pricing, about, any content meant to rank) to server-rendered or statically pre-rendered HTML — a static export, a lightweight SSR shim, or moving those specific routes to a framework with built-in SSR
  • 2. Add a unique <title>, meta description, and Open Graph tags per route — not one shared tag for the whole app
  • 3. Generate sitemap.xml listing every public route with an accurate last-modified date, and confirm robots.txt allows crawling
  • 4. Add a self-referencing canonical URL to every route so search engines don't treat query-string variants as duplicates
  • 5. Verify the fix by fetching the page without executing JavaScript — if the fix worked, the real content shows up in that raw response

Copy-paste this into Cursor, Claude, or v0 to ship the fix:

lovable-seo-fix.prompt.md
You are working on a Lovable-built app (Vite + React SPA). Audit every public, indexable route — homepage, pricing, and any content pages — and confirm each one server-renders or pre-renders meaningful, route-specific HTML before hydration, not a generic empty <div id="root">.

For each of those routes:
1. Add or fix a unique <title>, a unique meta description, a self-referencing canonical URL, and correct Open Graph tags
2. If the route only renders client-side, add static pre-rendering (e.g. vite-plugin-ssr, a prerender build step, or moving that route to a framework with SSR) so the initial HTML response contains real content
3. Generate or update sitemap.xml to include every public route with an accurate lastmod date
4. Confirm robots.txt allows crawling of all of them

Report back the full list of routes you checked, which ones needed pre-rendering, and what you changed on each.

curl -s https://your-app.lovable.app | grep -i title

Beyond the rendering fix

What Lovable SEO optimization looks like once indexing works

Fixing the empty <div id="root"> gets you indexed. This is what actually helps you rank once crawlers can read your app.

  • 1. Move off the default *.lovable.app subdomain. A shared subdomain dilutes authority and looks less trustworthy in search results. A custom domain is table stakes for Lovable SEO optimization once indexing itself is fixed.
  • 2. Add structured data. Lovable doesn't scaffold Organization, WebSite, or breadcrumb structured data by default. Adding it helps search engines and AI crawlers understand what your app is and who runs it.
  • 3. Compress images and add real alt text. Generated components frequently ship with large, uncompressed images and empty or generic alt attributes. Both hurt page speed and accessibility, and both are ranking factors.
  • 4. Submit your sitemap to Google Search Console. Lovable doesn't ping search engines on deploy. Verifying your domain and submitting sitemap.xml directly gets new and updated pages crawled faster than waiting for organic discovery.
  • 5. Write unique meta descriptions per route. A shared meta description across every page wastes the click-through opportunity search results give you. Each public route should describe what's actually on it.
  • 6. Internal-link with descriptive anchor text. Linking to your own pricing, features, or blog pages with real anchor text (not just "click here" or nav links) reinforces topical relevance for every page you link to.

SEO for Lovable: frequently asked questions

The Lovable SEO problem, what optimization looks like beyond it, and how it compares to other builders.

This is one of 43 checks in a Launch Readiness Audit.

Search visibility is one pillar. Trust, functionality, measurement, launch readiness, and compliance are the other five — and most Lovable apps have gaps in more than one.