Lovable SEO: why your site is not indexed

If your Lovable site is not indexed, the cause is usually one of five things: the site is not public, Google has found the pages but not crawled them yet, a noindex tag or robots.txt rule is blocking them, Google cannot see the content because the page is rendered in the browser, or the pages look like duplicates. As of 2 October 2026, Lovable apps created from 13 May 2026 use server-side rendering (SSR), so the rendering cause mostly applies to older projects. The fix is to check Google Search Console first, name the exact status it reports, and fix that one cause.

This guide is for founders whose Lovable marketing site or SaaS front door does not show up in Google. Platform facts come from Lovable's and Google's documentation as of 2 October 2026, listed under Sources.

Why is my Lovable site not showing up on Google?

Start with the facts Google gives you, not with guesses. Add your domain to Google Search Console, open the Pages report, and look at why each page is not indexed. Each status points to a different cause, and most of them have nothing to do with Lovable.

Google's help page says it does not guarantee that every page will be indexed. It also says a new page or site can take a week or so before Google starts crawling it. So a quiet first week is not proof that anything is wrong.

Is your Lovable site actually public?

Check this before anything else. As of 2 October 2026, Lovable's documentation says only publicly published apps can be indexed. Private or unpublished projects, and branded workspace addresses, are never indexable. On Business and Enterprise plans you can also restrict a published app so visitors have to log in. Google lists a page that needs a login as one it cannot reach, so keep the pages you want found open to everyone.

Also check that your latest changes are published. Google reads the live site, not the editor. If you fixed a title or added a page but did not publish, Google still sees the old version.

Does Google see your content or an empty page?

It depends on how your project was built. Lovable apps are React apps. In the older setup, React and Vite, the server sends a mostly empty HTML page and the browser builds the content with JavaScript. That is called client-side rendering.

Google can run JavaScript. Its JavaScript SEO guide, last updated 4 March 2026, describes three phases: crawl, render and index. Pages wait in a render queue, which can take a few seconds or longer. Google still calls server-side rendering or pre-rendering a great idea, because it makes a site faster and not all bots can run JavaScript.

Lovable now handles this in two ways, according to its documentation as of 2 October 2026:

• Apps created from 13 May 2026 use TanStack Start with server-side rendering. Every visitor and every crawler gets a fully rendered page.
• Older React and Vite apps get pages pre-rendered on request on their published public addresses, but only for verified crawlers: Google, Bing, social preview bots and AI engines such as ChatGPT, Perplexity, Claude and Gemini.
• Third-party SEO scanners are not verified crawlers, so they may report an older app's pages as empty even when Google sees them fine.

So an SEO tool that says your page is blank is not proof that Google sees it blank. Use the URL Inspection tool in Search Console and look at the rendered HTML. That is what Google's guide and Lovable's documentation both suggest.

One caveat: Lovable describes this pre-rendering as part of its own hosting. If you host an older project somewhere else, check how its pages are rendered there.

Should you upgrade an older Lovable project to TanStack Start?

You do not have to. Lovable's documentation says older projects keep working and search engines can still read them through pre-rendering. It suggests upgrading when you want full server-side rendering, reliable link previews and faster first loads. If search or link previews bring you customers, that is usually reason enough.

The upgrade runs inside your project. Lovable converts the page structure, carries over titles, descriptions, social preview tags and analytics scripts, then builds the project and loads every page to check it works. Your published site keeps serving the old version until you publish again, and you can revert the upgrade from version history.

The documentation also lists risks. Libraries that only work in a browser can break server rendering in ways the upgrade's checks do not catch. Visitors who installed the app on their device may keep a saved copy of the old version, which Lovable usually removes for them. Most upgrades cost 10 to 35 credits, depending on the size of the project. Treat it like any other big change: test every page and every sign-in flow before you publish. Our guide to taking a Lovable app to production covers what else to check before real users arrive.

What blocks indexing even on a server-rendered site?

Rendering is only one cause. These problems stop indexing on any stack:

• A noindex tag left on from development. Google warns that if it sees noindex, it may skip running JavaScript, so removing the tag with JavaScript later may not work.
• A robots.txt rule that blocks the pages, or the script files Google needs to render them. Google says it will not run JavaScript from blocked files.
• Every page sharing one title and description. Google asks for a unique title on each page, and Lovable's own SEO review flags duplicate titles.
• Missing pages that show a friendly not-found message but return a success code, which Google reports as soft 404s.
• Links that use # fragments instead of normal addresses. Google says it cannot reliably resolve those URLs.
• Two addresses for the same page, such as your lovable.app subdomain and your own domain, with no canonical tag saying which one is the real one.

The last one matters more than it looks. Lovable's documentation says a custom domain helps consolidate your brand and search presence under a domain you control. You choose one primary domain, and Lovable redirects the other connected domains to it. Make every canonical tag point to that primary address too.

Your customers may want the same. Looph, a customer-feedback product shaped in Lovable and engineered by our team, lets customers put their public board on their own domain, served through Looph's own edge. That went live on 17 September 2026; see the Looph case study.

How do you get Google to index your pages faster?

1. 01Run Lovable's SEO reviewOpen the SEO & AI search tab. Its review checks your sitemap, robots.txt, titles, canonical tags and indexing, and can apply most fixes for you.
2. 02Connect Search ConsoleVerify your domain. For publicly published sites, Lovable can connect Search Console, verify the site and submit the sitemap from the project chat.
3. 03Submit a sitemapList every page you want indexed. Publish your latest changes first, because Google fetches the sitemap from the live site.
4. 04Inspect key pagesRun your home page and your most important pages through URL Inspection and read the rendered HTML Google sees.
5. 05Request indexing onceUse Request Indexing for a few key pages. Google says repeat requests for the same address do not speed things up.
6. 06Link the pages togetherMake sure every page is reachable through normal links from your home page, not only from the sitemap.
7. 07Wait and recheckGoogle says crawling can take from a few days to a few weeks, and that a request does not guarantee indexing.

If a page is still listed as crawled but not indexed after that, look at the page itself. Google says its systems prioritize high-quality, useful content. A page with a few lines of text, or one that repeats another page, gives Google little reason to index it.

Do AI assistants read your site the same way?

Not always. Google's guide notes that not all bots can run JavaScript. On an older Lovable app, verified AI crawlers get the pre-rendered page. Lovable says link checkers and other agents get the plain app shell. A server-rendered page gives every reader the same complete HTML, whoever asks.

This site is an example. Plutonapps.com is served server-rendered with TanStack Start. On 2 October 2026, a plain request for our pricing page returned its full text, prices included, with no JavaScript run. If you are new to the category, our glossary explains what an AI app builder is.

When is SEO a sign of a bigger problem?

When the fix needs changes Lovable cannot make on its own: moving hosting, splitting a marketing site from the app, or rebuilding pages that depend on browser-only code. Those are engineering changes with real risk to sign-in, payments and data. If you are also thinking about leaving Lovable's built-in backend, read our guide to migrating off Lovable Cloud first.

Starter costs $2,999 a month paid annually, or $3,999 month to month; Growth is custom. See pricing. To see where your app stands first, take the free production-readiness check: 19 questions, a score out of 100 and your three biggest risks.

Sources

Each platform fact above comes from one of these pages, checked on 2 October 2026.

• Lovable documentation: Optimize your app for SEO and AI search (docs.lovable.dev/features/seo-aeo).
• Lovable documentation: How Lovable hosts your app (docs.lovable.dev/features/hosting).
• Lovable documentation: Upgrade a project to TanStack Start (docs.lovable.dev/features/upgrade-to-tanstack-start).
• Google Search Central: Understand the JavaScript SEO basics (developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics).
• Search Console Help: Page indexing report (support.google.com/webmasters/answer/7440203).
• Google Search Central: Ask Google to recrawl your URLs (developers.google.com/search/docs/crawling-indexing/ask-google-to-recrawl).
• Case-study facts: our Looph case study, as published on this site.
• Our own site: a plain request for www.plutonapps.com/pricing, made on 2 October 2026.