You published your Lovable app, searched for it, and got nothing back. Usually there's one specific, fixable reason, and you can find it by checking things in order instead of guessing.
First, separate "not indexed" from "not ranking"
A search for your brand name doesn't tell you which problem you have. Open Google Search Console, verify your domain, and paste one important URL (your homepage or pricing page) into URL Inspection.
- "URL is on Google" means the page is indexed. Your problem is ranking: titles, content, links, and domain age.
- "Discovered – currently not indexed" means Google knows the URL exists but hasn't crawled it yet.
- "Crawled – currently not indexed" means Google fetched the page and chose not to index it for now. Thin or duplicate content is a common reason.
- "Excluded by 'noindex' tag" means your page is telling Google to stay away.
The site: operator gives you a rough idea, not a verdict. Google itself says it doesn't necessarily show every indexed URL.
1. Is the app actually published and public?
Lovable's documentation says only publicly published apps can appear in search. These never show up:
- unpublished projects
- projects with website access restricted to workspace members
- branded workspace URLs (
app-name.workspace-subdomain.lovable.app)
If you want real search presence, connect a custom domain.
2. Check for a stray noindex
Open your live page, view source, and search for noindex. Also check the X-Robots-Tag response header in DevTools → Network. A leftover noindex from a staging setup will remove the page from Google completely.
3. Check robots.txt
Visit yourdomain.com/robots.txt. A line like Disallow: / blocks crawling of the whole site. A robots.txt block also hides any noindex tag from Google, so don't use robots.txt to "de-index" pages.
4. Submit a sitemap
Lovable creates a robots.txt for new projects but doesn't always create a sitemap. Ask Lovable to generate sitemap.xml listing every public route. Then submit it in Search Console under Sitemaps.
5. Make sure Google sees content, not an empty shell
Lovable's docs say apps created from May 13, 2026 use TanStack Start with server-side rendering. Older React + Vite apps are pre-rendered on request, but only for verified crawlers such as Googlebot.
- In Search Console, run Test live URL → View tested page → HTML. If you see your headings and copy, rendering is fine.
- If the HTML is basically
<div id="root"></div>, Google is getting a blank page. Upgrade the project to TanStack Start (Lovable's server-rendered stack; Lovable's docs say most upgrades cost 10–35 credits), or contact Lovable support about pre-rendering.
A generic SEO tool that isn't a verified crawler may still see the bare SPA shell on older apps. That's expected. Trust Google's live test.
6. Give each route its own title, description and canonical
If every page shares the same <title> and description, Google may treat them as duplicates. Each public route needs:
- a unique title
- a unique meta description
- a self-referencing canonical URL
Watch for canonicals that point back to the lovable.app subdomain after you've moved to a custom domain.
7. Request indexing and be patient
After fixing the above, click Request indexing in URL Inspection. New domains with no inbound links can take days or weeks to index. A couple of genuine links help Google discover the site, for example from your Product Hunt page, X bio, or a directory listing.
How FlowCanary's free check detects this
FlowCanary fetches your page twice: once as a normal browser and once with a Googlebot user agent. It then reports:
- whether the raw HTML has real text or an empty root
div(the "Google sees a blank page" check) noindexin meta tags or theX-Robots-Tagheader- whether
robots.txtblocks crawling and whethersitemap.xmlexists - a missing title, description, canonical or og:image on your homepage
Every finding comes with a paste-ready Lovable prompt you can drop straight into the chat to fix it.
Run the free 30-second check → No signup needed to see your report.