Off to Press Start a project

Guide No. 4Lovable and Google

Is Lovable good for SEO? The 2026 answer, by project age

By
Off to Press
Updated
Reading
About 8 minutes

Yes, for projects created from 13 May 2026. Older projects show up in Google too, but they have a few documented weak spots.

Lovable changed how it builds sites in May 2026, so most advice written before then is out of date. This guide gives the current answer, shows you how to tell which kind of project you have, and lists what to check.

Every fact below comes from a source we read in November 2026, mostly Lovable’s and Google’s own documentation. The links are in Sources, at the end.

Short answerAs of November 2026

Created from 13 May 2026
Good. Every visitor and every crawler gets the finished page.
Created before that
Workable. Google gets the page. Other tools may not, and the whole site shares one title and description.
Any project
Check the sitemap, the main domain and the page titles yourself.
On Enterprise accounts the date is 22 June 2026.

Lovable ships changes every month. Everything here matches Lovable’s documentation as of November 2026. If you read this much later, check the dates in Sources first.

Part 1The short answer

New projects are fine. Older ones have weak spots.

Lovable builds sites in one of two ways, and which one you have depends on when the project was created.

  • Created from 13 May 2026 (22 June 2026 on Enterprise). Lovable builds these with TanStack Start. The server sends a finished page on every request, to people and to crawlers alike. Google gets the same page your visitors do.
  • Created before that. These are React + Vite projects. A visitor’s browser receives a mostly empty page and builds the content with JavaScript. Lovable sends search engines a finished copy instead, so Google can still read the site.

So the common line that Google can’t see a Lovable site is wrong today, and it was never quite right: Google can read JavaScript pages. What remains for older projects is a short list of weak spots, covered in Part 3.

One caution applies to both: a site that is easy to read is not the same as a site that ranks. Lovable’s documentation says passing its technical checks doesn’t mean high rankings. Content, links and competition still decide.

Part 2Which kind of project you have

Three ways to tell

  1. Check the date. If you created the project on or after 13 May 2026, it is the new kind. On an Enterprise account the date is 22 June 2026.
  2. Ask Lovable. Type this in the project chat: What stack is this project on? The answer is either TanStack Start (new) or React + Vite (older).
  3. Look for the upgrade option. Open Settings › General › Project actions. If you see Migrate to TanStack Start, the project is the older kind. Lovable only shows that option on projects that can be upgraded.

Looking at the page source in your browser is not a reliable test. Part 5 explains why.

Part 3Older React + Vite projects

Three weak spots Lovable documents itself

1. One title and description for the whole site

Lovable’s documentation says: “Older React + Vite apps carry one set of metadata for the whole site.” On new projects you can set a title and description for a single page.

In practice, your pricing page, your about page and your home page can all show the same title in search results. If the browser tab still reads Lovable App, the site kept the text its template came with.

2. A generic image when someone shares a link

When a new project has no share image of its own, Lovable uses a recent screenshot of the site. Older projects are the exception. In Lovable’s words, an older app “carries a generic Lovable image, which is what a shared link shows until you ask Lovable to replace it.”

You can fix the image with one prompt. It will still be the same image for every page.

3. Only some crawlers get the finished page

Lovable sends the finished copy of an older site only to crawlers it has verified: search engines such as Google and Bing, AI search crawlers, social preview bots and some SEO tools. Everything else gets the mostly empty page.

  • Content that loads late may be missing from the copy, according to Lovable.
  • An SEO checker that isn’t on Lovable’s list may report an empty page even though Google sees the content.
  • Google has a name for sending crawlers a different page from visitors: dynamic rendering. Its documentation calls it “a workaround and not a long-term solution” and recommends rendering on the server instead.

None of this stops an older Lovable site from appearing in Google. It makes the site harder to check and gives you less control over each page.

Part 4New or old

Three things that are true for every Lovable project

Redirects between your domains are temporary

When you set one domain as primary, your other connected domains redirect to it. Lovable’s documentation says it “uses a 302 temporary redirect for page visits” and that “Lovable hosting does not support 301 permanent redirects between connected project domains.”

A 301 tells search engines a move is permanent. A 302 says it is temporary. Lovable’s reason is that a primary domain can be changed later.

The lovable.app address stays

Lovable’s documentation says: “Currently, there is no way to remove the xxx.lovable.app project URL from your project.” Connect your own domain and set it as primary, so visitors and search engines end up on one address.

Lovable makes the first custom domain primary by itself only for domains added after 29 October 2025. If you connected yours earlier, check that a primary domain is set. Without one, every connected domain shows the same site. Custom domains need a paid Lovable account.

A sitemap is not always there

Lovable’s documentation says it “creates a robots.txt with every new project, but not always a sitemap, and the starting metadata is generic.” Open yourdomain.com/sitemap.xml and see whether one exists.

Lovable’s SEO review (the SEO & AI tab) reports a missing sitemap, duplicate titles and placeholder text, and can fix most of them. Fixes use credits like any other edit.

Part 5Google, AI tools and link previews

What each crawler gets

What each kind of crawler receives from a new and an older Lovable project
Who asks for the pageNew projectOlder project
Google and BingThe finished pageA finished copy made for them
AI search (ChatGPT, Perplexity, Claude, Gemini)The finished pageA finished copy, for the crawlers Lovable has verified
Link previews (LinkedIn, Slack, WhatsApp, X, Facebook)A title and image you can set page by pageThe one title and image the whole site shares
Other bots, link checkers and unverified SEO toolsThe finished pageThe mostly empty page
You, with “view source”The finished pageThe mostly empty page

Why “view source” misleads on older projects

Your browser is not a verified crawler, so it gets the mostly empty page. Google gets the finished copy. An empty page source on an older Lovable site therefore tells you nothing about what Google received.

To see what Google has, use Google Search Console:

  1. Paste the page address into URL Inspection.
  2. Click View crawled page. It shows the HTML Google fetched.

Lovable points to the same tool: “To check the pre-rendered output yourself, use Google’s URL Inspection tool or a social platform’s link debugger.”

Can Google read JavaScript at all?

Yes. Google’s documentation says “Googlebot queues all pages with a 200 HTTP status code for rendering”, and that a page can wait in that queue. It also says rendering on the server “is still a great idea because it makes your website faster for users and crawlers, and not all bots can run JavaScript.”

AI crawlers

A study by Vercel and MERJ, published in December 2024, found that “none of the major AI crawlers currently render JavaScript”, with Google’s Gemini as an exception because it uses Googlebot. The study is two years old, so treat it as a snapshot.

This matters less on Lovable than it used to. New projects send finished HTML to everyone, and older projects send a finished copy to the AI search crawlers Lovable has verified.

Part 6Fixing an older project

The upgrade to TanStack Start, and what it costs

Since July 2026, an older project can be upgraded in place. After the upgrade, Lovable renders pages on the server, the same as a new project.

Where
Type / in the project chat and choose Migrate to TanStack Start, or use Settings › General › Project actions.
Cost
“Most upgrades cost 10 to 35 credits, depending on how large your project is.” (Lovable, as of November 2026.)
Who
Anyone who can edit the project, on any Lovable account type.
Safety
Your live site doesn’t change until you publish. You can undo the upgrade from version history.

What can go wrong

  • A page breaks. Lovable warns: “Some code libraries only work in the browser and can break server rendering in ways the upgrade’s checks do not catch.” Open every page before you publish.
  • A large project pauses partway. Lovable tells you what is done and continues when you ask.
  • Link previews look unchanged. Publish first. Slack and LinkedIn also keep old previews for a while.

You don’t have to upgrade. Lovable says older projects keep working and search engines can still read them.

Part 7Ten minutes, any project

A short check list

  1. The site is published and public. Unpublished projects never appear in search.
  2. Your own domain is connected and set as primary. Look in Settings › Domains.
  3. The browser tab doesn’t say “Lovable App”. Ask Lovable to write a real title and description.
  4. A sitemap exists at /sitemap.xml and lists addresses on your own domain.
  5. Google Search Console is connected and the sitemap is submitted. Lovable can do both from the chat.
  6. Google has the content. Inspect two or three important pages with URL Inspection and open View crawled page.
  7. A shared link looks right. Paste a link into LinkedIn or Slack and look at the title and image.
  8. You’ve run Lovable’s SEO review and dealt with what it found.

Then wait. Google says crawling “can take anywhere from a few days to a few weeks”, whatever the site is built with.

Part 8What to do next

Stay on Lovable, or move to WordPress

When you don’t need us

  • Your project is the new kind. Rendering is no longer a reason to leave Lovable.
  • Your older project upgrades cleanly. Spend the credits, test every page, publish.
  • It’s really an app. Logins, dashboards and data belong on Lovable. WordPress is the wrong tool for them.
  • One person edits the site and is happy doing it by prompt.

When WordPress is the better home

  • Several people edit the site. In Lovable, edits use credits, and that includes changing a title or description. In WordPress your team edits text and images in the editor.
  • You publish often. WordPress has a blog built in, and SEO plugins such as Yoast SEO or Rank Math give every page its own title, description and share image.
  • The site has many pages, and you want to manage them from a list instead of a chat.
  • You want one address and permanent redirects. On your own WordPress hosting you can set 301 redirects, and there is no second builder address.

WordPress also sends every page as finished HTML and makes its own sitemap at /wp-sitemap.xml. It doesn’t rank a site by itself. It takes technical obstacles away, and the content still has to earn its place.

Where we fit

We rebuild a Lovable site as a custom WordPress theme that looks the same, with all your content imported, for $299. Our own AI agents do the conversion and a person checks every page against your original. See Lovable to WordPress for what’s included.

Still weighing it up? Read Lovable vs WordPress for content teams. If you decide to move, the migration SEO checklist covers how to keep your search traffic, and the export guide shows how to get your code out.

Part 9Short answers

Frequently asked questions

Is Lovable good for SEO?

For projects created from 13 May 2026, yes: Lovable renders pages on the server, so Google and every other crawler get finished HTML. Older React + Vite projects can be indexed too, but the whole site shares one title, description and share image.

Can Google index a Lovable site?

Yes. New projects send finished HTML to everyone. For older projects, Lovable sends verified search engines a finished copy of each page. The site has to be published and public, and Google can take days or weeks to crawl a new site.

Why does my Lovable page look empty in view source?

Your project is the older React + Vite kind. Browsers and unverified tools get a mostly empty page that JavaScript fills in. Google gets a finished copy. Use URL Inspection in Google Search Console and open View crawled page to see what Google has.

Did Lovable fix its SEO problem?

Mostly. Projects created from 13 May 2026 render on the server. Older projects can be upgraded in place since July 2026, and Lovable says most upgrades cost 10 to 35 credits (as of November 2026). Temporary 302 redirects and the permanent lovable.app address remain.

Do I need a pre-rendering service for a Lovable site?

Lovable says no: sites hosted on Lovable don’t need an outside pre-rendering service for search engines or AI crawlers. New projects render on the server, and older ones get pre-rendered copies for verified crawlers.

Will moving to WordPress improve my rankings?

Not by itself. WordPress gives every page its own title and description, permanent redirects and an editor for your team. Rankings still depend on your content and on who links to you.

SourcesAll read on 17 November 2026

Sources

Want your Lovable site on WordPress?

Send us the zip with your code, or a GitHub link. We check your code and reply with a start date and the invoice for $299: an identical WordPress copy, with all your content imported.

Start your project