Lovable SEO: get your app indexed and ranking

12 more guides

• What 82 Lovable TanStack apps actually server-render

  Lovable TanStack SSR, measured: in 82 Lovable apps, only 4.4% of pages load their data on the server. The layout reaches the HTML; the data usually doesn't.

• Getting a Lovable app cited by ChatGPT and Perplexity

  Lovable AI search visibility depends on what is in your raw HTML. Which bots fetch what, why SSR alone does not settle it, and how to measure citations.

• Making a Lovable app crawlable

  Lovable crawlability comes down to links as much as rendering: real anchors, history routing, honest status codes, and a crawl you can run yourself.

• Canonical tags in Lovable: the rules and the traps

  Google's canonical rules, then the SPA traps that ruin a Lovable canonical tag: one baked URL on every route, trailing-slash forks, and lovable.app vs your domain.

• Fix broken link previews on a Lovable site

  Lovable link preview not working? Unfurlers parse raw HTML, and in practice none of them run your JS. The mechanism, the fix per stack, and how to re-scrape.

• Local SEO for a site you built with Lovable

  Lovable local SEO in practice: your Business Profile does the ranking, and the site supports it with schema crawlers receive, safe location pages and grid tracking.

• Per-page titles and meta descriptions in Lovable

  Every route of a client-rendered app ships the same title. How to set Lovable meta tags per route on TanStack Start and Vite, and where the built-in checks stop.

• Lovable site not showing up on Google

  A Lovable app not indexed on Google is usually not a rendering bug, but check anyway. Seven causes ranked by likelihood, with the curl test that proves which one.

• Pre-rendering a Lovable app: when you need it

  Lovable prerendering, honestly: SSR puts your page layout in the HTML but usually not your data. Why that happens, and a 30-second test for your own site.

• sitemap.xml and robots.txt on a Lovable site

  Lovable generates sitemap.xml and robots.txt automatically, but not always up front. Verify your Lovable sitemap, kill invented URLs, and ship a correct robots.txt.

• SSR vs SPA for SEO: what actually changes

  SSR vs SPA SEO, settled: Googlebot renders your SPA, but unfurlers and AI crawlers read raw bytes, and SSR only helps if your data is fetched in a route loader.

• TanStack Start SSR vs prerendering

  TanStack Start SSR vs prerendering: SSR only includes data a route loader fetched. Whether crawlers see content depends on where the fetch lives. How to check yours.