How Google sees your Lovable app
According to Lovable’s documentation, apps created from 13 May 2026 use TanStack Start with server-side rendering, so every page arrives as finished HTML that search engines and AI crawlers can read. Older React and Vite apps are pre-rendered when a verified crawler visits, so Google gets a readable page too, though content that loads late can be missing. You can upgrade an older app to the new setup. The live site only changes when you publish again.
Only publicly published apps can appear in search. Anything behind a login stays invisible to Google, whichever setup you use.
What Lovable does for you
- Serves readable pages to search engines and AI crawlers
- Creates a
robots.txtfor new projects - Runs an SEO and AI search review of your code, preview and live site, and can fix most findings when you click Try to fix
- Adds the Google Search Console verification tag for you
What’s still up to you
- A unique title and description for every page. Lovable’s starting metadata is generic, and duplicate or placeholder titles are a common finding.
- A sitemap. Lovable doesn’t always create one. Publish first, then submit it in Search Console, because Google reads it from your live site.
- Your own domain. Lovable recommends a custom domain if you want to be found in search, with all other addresses redirecting to one primary domain. If you change domains later, verify the new one in Search Console and submit the sitemap again.
- Re-running the review. It doesn’t run automatically on every publish.
Prompt to paste into Lovable
Give every public page a unique title (under 60 characters), a meta description (under 160 characters) and its own og:title, og:description and og:image, all matching what the page actually says. Create a sitemap.xml with full URLs on my main domain and add it to robots.txt.
Your data and keys
Lovable apps usually keep their data in Supabase, through Lovable Cloud or your own project. Lovable runs a security scan before you publish, but check yourself that Row Level Security is on for every table, with rules so people only see their own data, and that no secret keys reach the browser. Our security guide has the prompts.
Sign-up emails
If people sign up with an email link or code, make sure those emails come from your own domain through a real email provider, with SPF, DKIM and DMARC set up. Otherwise they often land in spam. See why sign-up emails go to spam.
Your Lovable launch checklist
- Published publicly, on your own domain
- Unique title, description and social image on every page
- Sitemap submitted in Google Search Console, and Bing Webmaster Tools connected
- SEO and AI search review run after your latest publish
- Row Level Security on every table, no secret keys in the browser
- Sign-up emails arriving in the inbox
- Two or three communities picked where your users already talk
Sources
Builders change fast. If something here no longer matches what you see, the builder’s own docs win.