Skip to content
Get started

Is Your Lovable Site Findable by ChatGPT and Claude?

Lara Hill
Lara Hill

What the May 2026 update means for anyone building or buying a B2B website right now

If you built your website on Lovable in the last year, there's a good chance your site was invisible to AI assistants like ChatGPT, Claude, and Perplexity. That's not a guess. It was a known technical limitation of how the platform rendered pages.

As of May 13, 2026, that's no longer true. Lovable shipped an update that addresses the problem for new and existing projects. Here's what changed, what you need to do if you built before the update, and what the whole story tells us about evaluating any AI website builder for marketing.

The old problem

Until mid-May, every site built on Lovable was a React single-page application with client-side rendering. The short version of why this matters: when a search engine or AI crawler visited the site, it received a nearly empty HTML shell. The actual content (your headlines, your value proposition, your service descriptions) was generated by JavaScript after the page loaded in a browser.

A human visitor didn't notice. A bot often saw a blank page.

This wasn't a Lovable-specific bug. It's the default behavior of any platform built on modern JavaScript frameworks without server-side rendering. But it had real consequences for marketing sites. Google indexed pages slowly or not at all. AI crawlers, which mostly don't run JavaScript, saw nothing.

For B2B companies hoping for organic search traffic or AI citations, this was a meaningful problem.

What Lovable shipped on May 13

According to Lovable's own announcement, new projects created on or after May 13, 2026 are now built on a framework called TanStack Start with server-side rendering enabled by default. Every page request returns fully rendered HTML to both humans and crawlers.

For older projects, Lovable shipped a different fix. Per Lovable's documentation, legacy React and Vite projects now use on-request pre-rendering on deployed public URLs. When a verified crawler arrives (Google, Bing, social-preview bots, and AI engines including ChatGPT, Perplexity, Claude, and Gemini), Lovable renders the page on the fly and returns the resulting HTML.

The release also bundled in an SEO and AI search review tool, Semrush integration in chat, and one-click fixes for common metadata issues. SEO consultant Till Freitag's analysis called it Lovable shifting from app builder to app distribution layer.

In plain terms: the rendering problem is largely solved, both for new projects and for older ones that previously had it.

If you built on Lovable before May 13

If your project predates the update, you don't get full SSR. You get automatic pre-rendering instead, and there are a few things worth knowing.

The pre-rendering is automatic. You don't have to enable, configure, or migrate anything. Per Lovable's documentation, static HTML snapshots are generated automatically when verified crawlers (Google, Bing, ChatGPT, Claude, Perplexity, Gemini, and social-preview bots) request a page on your deployed public URL. You also don't need to pay for or install any third-party prerendering service.

But you can't verify that by looking at your site. Because pre-rendering only serves to verified crawlers, the view-source experience in your browser will still look like a single-page app. To see what crawlers actually see, you need to check from a crawler's perspective. Here's how I'd approach it.

Use Google Search Console first. This is an important (and free!) AEO and SEO diagnostic tool, regardless of where your site is hosted. If you haven't already, verify your domain in Search Console and submit your sitemap. Then use the URL Inspection tool to view your live URLs and confirm Google is seeing the rendered content (headlines, body copy, meta tags, structured data). Search Console will also surface indexing issues, coverage problems, and which queries are surfacing your site. For most websites, Search Console is the closest thing to ground truth on whether you're actually findable.

Cross-check with Semrush or another SEO platform. Search Console tells you what Google sees. Semrush (or Ahrefs, or similar) tells you how your site is performing competitively: which keywords you're ranking for, what your competitors are ranking for that you aren't, and where you have backlink and content gaps. For AEO specifically, Semrush has added features that track AI assistant visibility, including whether your domain is being cited in AI Overviews and similar AI-generated answers. This is where the strategic AEO conversation actually happens, not in the platform's built-in tools.

Use link debuggers to verify social previews. LinkedIn Post Inspector, Facebook Sharing Debugger, and similar tools show you the metadata that bots actually receive when your link is shared. These are quick, free, and useful for confirming that Open Graph tags, page titles, and preview images are coming through correctly.

Then decide whether to migrate or stay. This is the real strategic question for legacy users. Pre-rendering is good. SSR is better. The difference matters most if you're publishing a lot of new content, or if you're noticing that dynamically loaded content (think filtered listings, search results, or anything that updates after page load) is not getting indexed. For a static marketing site that publishes occasionally, pre-rendering is likely enough. For a content-heavy site or one where AEO is core to your strategy, rebuilding on TanStack Start is worth considering. There is no automatic migration path from legacy projects to the new stack; you would need to rebuild.

If you're not sure which side of that line you're on, your Search Console data plus a Semrush check of your AI visibility is usually enough to tell you. If the indexing is clean and you're being cited where it matters, stay. If you're invisible in AI answers despite good content, the migration starts to make sense.

What this changes

If you've been considering Lovable for a marketing site, the conversation is different now than it was a month ago. Specifically:

  • New Lovable projects ship with real SSR by default. No workarounds, no prerendering services, no migration. The thing your buyers' AI assistants need to see your content is in the response from the first request.
  • Existing Lovable projects get automatic pre-rendering for verified crawlers. This is not as clean as native SSR (third-party SEO scanners and unverified bots still see the SPA shell), but it solves the practical visibility problem for Google and the major AI engines.
  • Setup-side AEO basics are getting easier. Meta tags, Open Graph data, and structured data are flagged in the review tool and fixable in one click.

There are still caveats. Per Lovable's FAQ, full SSR is currently only available for new projects on TanStack Start, not retroactively for legacy projects. And the technical foundation being solid is not the same thing as having a good content strategy, the right schema markup for your industry, or content that AI engines actually want to cite.

But the central problem with Lovable's AEO foundation is, for most practical purposes, fixed.

Why this matters beyond Lovable

The pattern here is what's interesting, not just the specific platform.

Three things are worth taking from this:

One: the underlying concept (server-side rendering vs. client-side rendering) is now a question you should be asking about every platform you evaluate. Not every AI website builder defaults to SSR. Some still serve empty HTML shells to AI crawlers. The question isn't whether the platform is fashionable. It's whether your content reaches the bots that decide whether you exist in an AI-generated answer.

Two: AI-built tools are evolving faster than most evaluation cycles. A piece accurate three weeks ago can be outdated today. That happens now. If you're doing platform evaluations on a quarterly or annual cadence, you're probably making decisions on stale information. This is one of the real second-order effects of the current AI tooling pace, and it deserves more attention in B2B marketing operations than it currently gets.

Three: "fixed by default" is not the same as "configured well." Even with Lovable's update, the platform doesn't automatically set up canonical tags, meta descriptions, structured data, llms.txt, or content optimized for AI citation. Those still take real work. The rendering problem is solved. The strategic work isn't.

What to ask before you commit to any AI website builder

If you're choosing a platform right now (Lovable or anything else), the diligence questions worth asking have shifted. They're now:

  1. Does the platform serve fully rendered HTML to crawlers by default, or only with additional setup?
  2. If my project is older, does the platform pre-render for AI crawlers automatically, or do I need a third-party service?
  3. What does the platform handle automatically (metadata, schema, sitemaps, llms.txt) and what's left to me?
  4. How do I verify what AI crawlers actually see when they visit my site?
  5. What's the migration path if I outgrow the platform or it changes direction?

These are the questions that matter for AEO. The platform marketing won't always answer them clearly. Lovable's recent update is a good example of a platform getting this right. Other platforms in the same category still haven't.

The bigger pattern

The job of a marketing leader hasn't changed. It's still to ask the annoying questions before the contract gets signed, and to keep asking them after, because the answers change.

AI-built websites can absolutely be made to work for AEO. Lovable's update is proof. But "built by AI" and "findable by AI" are still not automatically the same thing, and platforms move at different speeds. Knowing the difference, and knowing what to ask, is the work.

That's where smart B2B marketing teams have an edge right now. Not by picking the trendiest tool, and not by avoiding new platforms entirely, but by understanding the technical fundamentals well enough to evaluate any of them on the things that actually matter.

Sources

Falls River Media helps B2B and corporate training companies build AI-augmented marketing systems that are designed to be found, by search engines and by AI assistants. If you're rethinking your website or wondering whether your current setup is AEO-ready, we'd love to talk.

Share this post