# Why Your Lovable Site Isn't Showing on Google (and How to Fix It)

Canonical: https://figment.so/blog/lovable-site-not-showing-on-google

A Lovable site is usually missing from Google because it is unpublished, blocked by noindex or robots.txt, absent from the sitemap, or missing per-route titles. Check each in Search Console, in that order.

**There is rarely one single cause.** A Lovable site can be missing from Google because it was never published, a page is blocked from indexing, the sitemap doesn't list it, titles and descriptions are missing per route, or rendering delays how fast Google sees the content. Check them in that order with Google's own tools instead of guessing.

## Is the site published and indexable at all?

Confirm you are checking a live, published, public URL before you do anything else. Lovable's SEO documentation says: "Only publicly published apps can be indexed by search engines" ([Lovable Documentation, "Optimize your app for SEO and AI search"](https://docs.lovable.dev/features/seo-aeo)). The same page says private or unpublished projects, and branded workspace URLs of the form `app-name.workspace-subdomain.lovable.app`, are never indexable.

## How does Google see a Lovable site's content?

It depends on when your app was created, per Lovable's documentation:

- **Apps created from May 13, 2026 onward** use TanStack Start with server-side rendering, so every request returns fully rendered HTML (Lovable Documentation, SEO and AI search page). These apps have no client-side rendering gap.
- **Older React + Vite apps** use "on-request pre-rendering on deployed public URLs, served only to verified search and AI crawlers (Google, Bing, social-preview bots, and AI engines like ChatGPT, Perplexity, Claude, Gemini)," and "pre-rendering runs at request time, so dynamically loaded content is included" (same source). A third-party SEO scanner that isn't on Lovable's verified-crawler list may see the bare single-page app instead. That is expected, and does not mean your real Google visibility is broken.

Google's own documentation describes how it handles JavaScript-rendered pages: "Googlebot queues pages for both crawling and rendering," and after the initial crawl, "once Google's resources allow, a headless Chromium renders the page and executes the JavaScript." Google indexes "the rendered HTML," but rendering is a separate, sometimes delayed step: "the page may stay on this queue for a few seconds, but it can take longer than that" ([Google Search Central, "JavaScript SEO basics"](https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics)). If your app predates the TanStack Start change and its pre-rendering isn't reaching Googlebot, this two-step process is the most likely place for things to stall.

## Does this mean Google can't read JavaScript?

No. Google does not say it cannot index JavaScript-rendered sites. It describes indexing "the rendered HTML," produced by "an evergreen version of Chromium" running your JavaScript. The issue is a timing and reliability gap for content that depends on client-side rendering, not a hard wall. Check Search Console yourself rather than trusting a scanner that says "Google can't see your JS."

## How do I check whether the page is indexed?

Use Search Console's URL Inspection tool, not a `site:` search. A `site:yourdomain.com` search is a starting point, but Google says its limits: "the `site:` operator doesn't necessarily return all the URLs that are indexed under the prefix specified in the query," and if a URL doesn't show up, Google advises you to "use the URL Inspection tool to make sure the URL can be indexed and to submit the URL to indexing" ([Google Search Central, "How to use the site search operator"](https://developers.google.com/search/docs/monitor-debug/search-operators/all-search-site)). The **URL Inspection** tool "shows what Google knows about a specific page on your site" and can test the live version against indexing requirements ([Google Search Console Help, "URL Inspection tool"](https://support.google.com/webmasters/answer/9012289)).

## Is a noindex tag or a robots.txt block hiding the page?

Check your published site's response headers or rendered `<head>` for a `noindex` meta tag, and check `/robots.txt` for a `Disallow` rule that stops Google crawling the page. A leftover noindex tag from a staging or preview stage is a common, easy-to-miss cause.

Google's documentation on the `noindex` rule says: "When Googlebot crawls that page and extracts the tag or header, Google will drop that page entirely from Google Search results." A `robots.txt` block is not a safe substitute. Google warns "if the page is blocked by a robots.txt file or the crawler can't access the page, the crawler will never see the noindex rule, and the page can still appear in search results, for example if other pages link to it" ([Google Search Central, "Block Search indexing with noindex"](https://developers.google.com/search/docs/crawling-indexing/block-indexing)).

## Does the sitemap list my pages?

Submit a current sitemap in Search Console and make sure it lists your live domain's routes. Google's sitemap documentation says sitemaps matter more as sites grow: beyond a handful of pages, "you will need to generate the sitemap," and sitemaps particularly help sites that are "complex to maintain the mapping on larger sites, or sites where the URLs change often" ([Google Search Central, "Build and submit a sitemap"](https://developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap)). The Sitemaps report in Search Console "will allow you to see when Googlebot accessed the sitemap and also potential processing errors" (same source).

Lovable's SEO review also checks for sitemap problems: a "missing sitemap, invalid XML, placeholder routes, relative URLs, host mismatches, or out-of-sync URLs between your routes and sitemap" (Lovable Documentation, SEO and AI search page). A sitemap that still lists a Lovable preview domain instead of your live custom domain will not help Google find the right URLs.

## Does every route have its own title and description?

Give each route a distinct title and meta description. Lovable's review flags "duplicate titles, placeholder text, weak descriptions, or incorrect canonical URLs," and checks whether "social previews aren't customized for this site" (Lovable Documentation, SEO and AI search page). If every route shares the same generic title and description, which is common in single-page apps that never got per-route metadata, fix it. It isn't by itself an indexing blocker.

## What if the app predates May 2026 and pages still don't appear?

Check the rendering path last. If your app predates the May 2026 TanStack Start change and pages still aren't appearing after the checks above come back clean, the pre-rendering Lovable serves to verified crawlers is the remaining variable. Confirm that your production domain, not a preview URL, is the one being crawled, and give it time. Google acknowledges the render queue "can take longer" than a few seconds, sometimes substantially longer for a newer or lower-authority site.

## What is the short checklist?

- [ ] Confirmed you are checking a live, published, public URL, not a private project or a branded workspace URL.
- [ ] Ran the page through Search Console's URL Inspection tool, not just a `site:` search.
- [ ] Checked the rendered page and HTTP headers for a stray `noindex` tag.
- [ ] Checked `/robots.txt` for a `Disallow` rule blocking the page.
- [ ] Submitted a current sitemap in Search Console and confirmed it lists your live domain's routes, not a preview domain.
- [ ] Confirmed each route has a distinct title and meta description.
- [ ] If the app predates May 13, 2026, judged pre-rendering by the production domain, not by a scanner.

## What if I move the app off Lovable?

Your new host's rendering setup replaces Lovable's pre-rendering, so recheck every step above against the new production URL. For what an AI tool can and can't do once you edit a live site directly, see [How to Have ChatGPT, Claude, Codex or Cursor Edit an Existing Website](/blog/can-ai-edit-my-website). If you plan to rebuild the marketing pages around this app in a different tool instead of patching the single-page app's SEO, [Can AI Build My Website?](/blog/can-ai-build-my-website) is a plain look at what an AI-first rebuild does and doesn't solve.
