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.
29 posts across 3 topics. New here? Start with the overview marked in each topic.
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.
Lovable Cloud vs Supabase is close to a one-way door. The documented tradeoffs, the credit pool that bills your hosting, and what switching later really costs.
Two routes to download Lovable code (a ZIP from the code editor and Git sync) the plan gate on both, and the backend pieces neither one exports.
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.
Lovable crawlability comes down to links as much as rendering: real anchors, history routing, honest status codes, and a crawl you can run yourself.
There is no one-click Lovable Cloud to Supabase migration. The honest manual runbook: export, schema, RLS, edge functions, storage, secrets, auth and rollback.
A Lovable contact form needs an endpoint to POST to. Compare an edge function plus Resend, a hosted form backend, and a keyless HTML endpoint.
Lovable GitHub sync is two-way but only one branch at a time, and it can never import an existing repo. Every rule, limit and failure mode.
Lovable integrations come in six connection types, and picking the wrong one is why wiring fails. What each type does, what exists, and how secrets flow.
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.
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.
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.
Lovable MCP servers are chat connectors: personal, build-time only, and they do not run in your published app. The six connector types, and what's worth wiring.
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.
A Lovable migration is really three migrations: frontend, backend, hosting. What each export path moves, which one-way doors break sync, and the safe order.
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.
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.
The Lovable Resend setup that actually ships: what the shared connector can't do, the DNS you verify first, and the deliverability work nobody documents.
Lovable SEO splits across two stacks, and SSR alone does not put your data in the HTML. Test both on your own routes, then close the gaps Lovable leaves to you.
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.
Lovable Stripe is set up through prompts, and it's a different thing from Lovable's built-in payments. How to choose, plus the webhook code you own.
Lovable vs Cursor decided on the axes that matter: what you're building, how you pay, who wires the backend, and how to run both on one repo safely.
Using Lovable with Claude Code or Codex: wire up git sync, clone locally, and adopt the branch discipline that stops two agents fighting over one branch.
Transferring the repo breaks Lovable sync. Move Lovable project to another repo or GitHub org safely: what breaks, what you lose, and when support has to re-attach it.
Blank white screen after export? Run Lovable app locally without the guesswork: pick the right Node, fix the missing env vars, and handle the backend that stayed behind.
Save Lovable credits by understanding what a credit actually buys: per-message billing, three kinds of usage in one pool, and the rollover rules.
How to self host Lovable app code on Vercel, Cloudflare Pages or Netlify: build settings, SPA rewrites, and the crawler pre-rendering you leave behind.
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: SSR only includes data a route loader fetched. Whether crawlers see content depends on where the fetch lives. How to check yours.