Lovable SEO: what Google actually sees, and what is still on you

The problem Lovable had, and what changed

A Lovable project is a React application. Until this year, that meant the HTML Google fetched was a near-empty page with a script tag; the content appeared only after the browser ran the JavaScript. Google does run JavaScript, but later, less often and less reliably than it reads plain HTML, and most AI crawlers and social-preview bots do not run it at all. “My Lovable site is not showing up on Google” was the most common Lovable complaint for a reason.

On 13 May 2026 Lovable shipped what it calls Discoverability. Two things are true now:

• Projects created since 13 May 2026 use TanStack Start with server-side rendering. Every request returns fully rendered HTML, for people and for crawlers.
• Older React + Vite projects provide on-request pre-rendering to their public URLs. Users are shown the single page app (SPA) while verified crawlers (e.g. search engines: Google, Bing; social previews; and AI platforms: ChatGPT, Perplexity, Claude and Gemini) are shown pre-rendered HTML.

Both are properties of Lovable’s hosting. Download the code and host it on Netlify yourself and an older project is client-rendered again.

Why your SEO tool still says the page is empty

Because it is not Googlebot. Lovable serves the pre-rendered version only to crawlers it can verify. Others, including the crawlers in the SEO audit tools, get the single page app. Therefore, a “no content found” result from one of those tools shouldn’t be alarming. Same with the prerendering services that post test results showing the single page app. Their crawlers and services get the same single page app. The single page app is all they see.

How to check what Google actually gets

1. Add the site to Google Search Console. Lovable’s SEO docs walk through this and verification. Only public projects can be indexed. Previews and private projects are not indexed.
2. To see the HTML Googlebot fetches, select the URL of the page in question, do a URL inspection, test the URL, view the tested page, and select HTML. If your headers and body text appear in this source, the problem is not rendering.
3. In the Pages report, check for pages that are “Discovered, currently not indexed” and “Crawled, currently not indexed.” In the case of a site that is rendering correctly, these pages are likely thinner or duplicate pages.

What is still on you

Rendering was the hard part and Lovable now handles it. Other areas of SEO are relatively straightforward, and they don’t automate that on Lovable. Lovable’s own documentation says sitemaps, robots.txt, metadata and other SEO elements “are not always generated up front.” Their in-app SEO review and AI search tools, which are included in all plans and check for issues and provide suggestions to resolve issues, use up credits in the process.

• A unique title and description for every route
• A sitemap.xml that lists the real pages, and a robots.txt
• Canonical URLs, Open Graph tags per route, structured data (JSON-LD)
• image alt text and sensible heading structure

Every one of those is a prompt, a regeneration and a check that nothing else moved, and every one has to be redone when the page changes. On a five-page site that is an afternoon. On a site that publishes weekly it is a job.

See what the rebuild would cost for your site

Scan my Lovable site

Free. Under a minute. Fixed price at the end.

“Lovable HTML” and LovableHTML

Two different things share the name. People searching “Lovable to HTML” usually want plain pages they can host anywhere; there is no such export, because the project is an application (see how to download your Lovable project). LovableHTML is a prerendering product listed on lovable.dev that serves rendered HTML to crawlers for sites that need it, the same job third-party services such as Prerender.io do. Since May 2026 most Lovable-hosted projects get that from the hosting itself; a prerendering service is for the cases the built-in rendering does not cover, such as an older project with content that arrives from a database after the page loads.

When a rebuild is the honest answer

If your Lovable site is an app, do the checklist above and stay. If it is a business website, the SEO work is a symptom of a bigger mismatch: you are running a marketing site inside an app builder, and every routine job (a new page, a blog post, a title change, a redirect) is a prompt. On WordPress the pages are server-rendered on any host, and titles, descriptions, sitemaps, schema and redirects are fields and settings your team fills in. The design you settled in Lovable comes with you.

Questions people ask

Is Lovable good for SEO?

Adequate, as of mid-2026, for a site hosted on Lovable and set up carefully. Rendering is handled; metadata, sitemaps and structure are on you and cost credits to maintain. It is not a platform designed around publishing, and it shows once the site has more than a handful of pages.

Why is my Lovable site not indexed?

Most likely it is not public. Previews are not indexed. Google may not have found it because it is not linked and there is no sitemap. Pages may be thin or duplicates. On an older project with database-driven content, the pre-render may not include what loads after the page. Search Console’s URL inspection will give more information.

Does Lovable have a sitemap?

Not automatically. You can have the SEO review generate one if necessary. Check the output. A generated sitemap should only include the existing pages.

Do I need Prerender.io or LovableHTML?

Check first. If the HTML from Search Console shows the content, you don’t have to do anything. If it is a older project, and the pages are generated and filled in by a database after the page is loaded, then a prerendering layer will help, or you can rebuild the project as a server-rendered project and stop using the workaround.

Checked on 28 September 2026 against Lovable’s Optimize your app for SEO and AI search documentation and Google’s Search Console help. Lovable’s rendering changed on 13 May 2026; if it changes again, this page will.