Skip to main content

SEO for Lovable Sites: A Fix Checklist You Can Run

SEO for Lovable sites: rendering, titles, schema, sitemap, llms.txt and links, in order, with before and after code and a free check.

By Kaivalya Deshpande, Founder, RankBrain AI·Published ·6 min read·1 source cited

Lovable builds React apps. React apps render in the browser with JavaScript. When Google's crawler visits a Lovable site cold, it often receives an almost-empty HTML shell and moves on before the page renders. That is why the site looks fine in a browser and is invisible in Google.

There are ten things to fix, in this order. Each one is a small code change. This checklist covers each with the before and after, so you can paste each fix into the AI tool you already have.

Run the free check first: Website SEO Checker.

What this checklist covers

What this checklist covers
FixWhat it changes
RenderingHTML reaches Google before JavaScript runs
Page titleGoogle reads the page topic
Meta descriptionSearch results show your summary
Heading structureGoogle reads the page hierarchy
Canonical URLGoogle indexes the right version
SitemapGoogle discovers all your pages
robots.txtGooglebot can enter the site
Schema markupGoogle and AI assistants understand the business
Link textAnchor text signals topic to crawlers
llms.txtAI assistants can describe your business

Last checked: 2026-11-16 | Publisher: Maitreya Labs

Check what Google receives

Before changing anything, see what the crawler sees.

View Source. Open your site in Chrome, right-click, and choose View Page Source. This shows the raw HTML Google receives — the HTML before JavaScript runs. If the <body> holds only <div id="root"></div> and the <title> tag is empty, the page is client-rendered. Google is reading a blank document.

Free tool. Paste your URL into the Website SEO Checker. It checks up to 40 factors and shows what a crawler would read.

Look for:

  • An empty or missing <title> tag
  • <div id="root"></div> as the entire body
  • No <meta name="description"> tag
  • No <h1> on the page

If you find any of these, start at Fix 1.

The fix list in order

Fix 1: Rendering

A Lovable site ships a client-rendered React app by default. Static HTML reaches Google immediately. Client-rendered HTML waits in a crawl queue.

For a marketing page or blog, Lovable's AI editor can convert the page to static output. Paste this into the editor:

Add server-side rendering so the full page content is in the HTML before JavaScript runs.

Check View Source after the change. The body should contain real headings, paragraphs and text.

Fix 2: Page title

Before:

<title></title>

After:

<title>Your Product Name — What It Does | Brand</title>

Keep it under 60 characters. Put the page topic first.

Fix 3: Meta description

Before:

<!-- missing -->

After:

<meta name="description" content="One sentence, under 155 characters, saying what this page is and who it is for." />

Fix 4: Heading structure

One <h1> per page. Section headings use <h2> and <h3>.

Before:

<div class="hero-title">My Product</div>

After:

<h1>My Product — What It Does</h1>

Fix 5: Canonical URL

Tells Google which version of a URL to index.

<link rel="canonical" href="https://yourdomain.com/this-page" />

Add this to <head> on every page.

Fix 6: Sitemap

A sitemap gives Google every URL you want indexed. Generate one at XML Sitemap Generator, upload it as /sitemap.xml, and reference it in robots.txt.

Fix 7: robots.txt

After:

User-agent: *
Allow: /
Sitemap: https://yourdomain.com/sitemap.xml

A missing robots.txt can stop Googlebot at the door.

Fix 8: Schema markup

Schema is structured data that tells Google and AI assistants what your business is. Add a JSON-LD block to every page. Use the Schema Markup Generator, then paste the output inside a <script type="application/ld+json"> tag in the <head>.

After:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Business Name",
  "url": "https://yourdomain.com",
  "description": "One sentence about what you do."
}
</script>

Before: <a href="/pricing">Click here</a>

After: <a href="/pricing">See pricing plans</a>

Replace every "click here" and "read more" with the actual topic.

Fix 10: llms.txt

AI assistants like ChatGPT look for /llms.txt at your domain root. It describes your company and pages in plain text. Generate one at llms.txt Generator and upload it to your root.

Worked example

A founder built a landing page for a project management tool on Lovable. The site had no organic visits after launch.

View Source showed <title></title> and <body><div id="root"></div></body> — no content in the HTML at all.

Steps taken in order:

  1. Asked Lovable's AI editor to output static meta tags and add server-side rendering.
  2. Added a page title under 60 characters with the product name and main topic.
  3. Added a meta description under 155 characters.
  4. Generated a sitemap with the XML Sitemap Generator and submitted it in Search Console.
  5. Added an Organization JSON-LD schema block.

After the changes, View Source showed full page text in the HTML. Google Search Console showed the page as crawled and indexed after the sitemap was submitted.

Sitemap and Search Console

After uploading your sitemap:

  1. Open Google Search Console and add your property.
  2. Under Sitemaps, paste your sitemap URL and submit.
  3. Check the Coverage report for pages marked Excluded.
  4. Use URL Inspection to request indexing on your main page.

Indexing on a new domain can take days to weeks. The fixes above remove the technical blocks. The timeline is Google's.

Do it with an AI coding tool

If you use Cursor, Claude Code or Codex, one prompt applies several fixes at once:

Add a <title> tag, <meta name="description">, <link rel="canonical">, and an Organization JSON-LD schema block to the <head> of this page. Use the product name, domain and a one-sentence description from the project's README or landing page copy.

Check View Source after to confirm the tags appear in the HTML before JavaScript runs.

Do it with RankBrain AI

RankBrain AI connects to Cursor, Claude Code or Codex with one paste. It scans your site, produces the exact fixes — titles, descriptions, schema blocks, link text — and applies each one after you approve the before and after.

Your site looks identical to visitors. The changes go into the HTML where Google and AI assistants read it. Free for 3 days, then $5 a month.

Check my site free

When prerendering is the better route

Some Lovable builds use a heavily dynamic frontend where server-side rendering would require rebuilding most of the app. For those, a prerender service caches static HTML for crawlers and delivers the normal React app to visitors.

This route fits sites where:

  • Real-time data changes per user session
  • Server rendering would break existing functionality
  • The current build must stay exactly as it is

A prerender service sits in front of your app. Crawlers receive cached HTML. Visitors get the full React experience.

Check my site free

Publisher: Maitreya Labs. Rankings are not guaranteed.

Frequently asked questions

Does Lovable include SEO setup by default?

Lovable provides tools for building React apps. Meta tags, schema and sitemap generation are part of the SEO setup you add to the project. What is automatic in a Lovable build changes as the platform updates. Check View Source on your own site to see what is currently in the HTML.

How long until a Lovable site appears in Google?

After fixes are applied and a sitemap is submitted, Google typically indexes a new page within days to a few weeks. Use the URL Inspection tool in Search Console to request indexing and track status. The timeline depends on your domain's history and the crawl queue.

Does fixing titles and schema guarantee a ranking?

No ranking is guaranteed by any technical fix. Titles and schema help Google understand what the page is — a prerequisite for ranking. Where a page ranks depends on many factors beyond the page itself.

Can I do this without writing code directly?

Most fixes above need a small change in the <head> of the HTML. In Lovable's AI editor, you can describe the change in plain text and the editor makes it. RankBrain AI does the same through the AI tool you already use — it writes the fix and waits for your approval before applying it.

What is llms.txt and does it affect Google?

llms.txt is a file at /llms.txt on your domain. It describes your business in plain text for AI assistants like ChatGPT and Perplexity. Google's crawler handles it in its own way; AI assistants use it to describe your business accurately when a person asks about you.

When should I use prerendering over server-side rendering?

Use prerendering when the app has real-time, per-user data that server rendering would break, or when a full rebuild is too costly. Use server-side rendering when the page is mostly static marketing content — a Lovable landing page or blog is a good candidate for SSR.

Sources

Every figure on this page traces to one of these. Dates are when we last read each page: prices and features change, so check anything older than a few months. The last entry is a product page, listed so you can find the tool, not as evidence.

  1. [1]
    Build and Submit a Sitemap

    Google Search Central · developers.google.com · Official documentation · read 2026-09-18

  2. [2]
    Google Search Console

    Google · search.google.com · Product page · read 2026-09-18

Keep reading

Lovable builds React apps. React apps render in the browser with JavaScript. When Google's crawler visits a Lovable site cold, it often receives an almost-empty HTML shell and moves on before the pag…