Why your AI-built app isn't showing on Google (and how to fix it)

You built your app with Lovable, Bolt, Cursor or another AI tool, published it, searched for its name and got nothing. That's normal for the first few days. If it's been a couple of weeks, something is usually in the way, and it's rarely the thing people guess first.

Three things have to be true for Google to show your app: it must be allowed in and able to read your text, it must know your pages exist, and it needs a reason to show you for a search. Here's how to find which one is missing.

Start with one search

Type site:yourapp.com into Google, with your own address. Every page Google has indexed shows up. An empty result means Google hasn't added a single page yet.

Then open Google Search Console

Search Console is free, and it's the only place Google tells you directly what's wrong. Add your site, verify it (most builders can add the verification tag for you), then paste your homepage address into the search bar at the top. That's URL Inspection, and it answers in one line:

• URL is on Google: you're indexed. If you still can't find yourself, it's a ranking problem (cause 5 below).
• Discovered – currently not indexed: Google knows the page exists but hasn't visited yet. Usually just time.
• Crawled – currently not indexed: Google visited and decided the page wasn't worth adding. Usually thin content, or a page that looked empty.
• Excluded by 'noindex' tag or Blocked by robots.txt: a setting is turning Google away.

While you're there, submit your sitemap (usually yourapp.com/sitemap.xml) under Sitemaps, and add the site to Bing Webmaster Tools too (you can import it from Search Console). Bing matters more than it used to, because several AI assistants pull from its results.

1. A setting is turning Google away

The easiest fix, and a common one: a noindex tag left over from development, a robots.txt with Disallow: /, an app published as private, or content you only see after logging in. Google only indexes what a logged-out stranger can see.

Prompt to paste into your builder:

Check my app for anything that stops search engines from indexing it: a noindex meta tag, a robots.txt rule that blocks crawlers, or public pages that only show content after login. Keep the public pages indexable and keep private pages (dashboard, account, settings) blocked. Tell me what you changed.

2. Google sees an empty page

Lots of AI-built apps send the browser a nearly blank page and fill it in with JavaScript a moment later. You see your app. A crawler may see this and not much else:

<body>
  <div id="root"></div>
  <script src="/app.js"></script>
</body>

Google can run JavaScript, but later and not always fully, and most social networks and many AI crawlers don't run it at all.

To check, use URL Inspection, click View crawled page and look at the HTML. Search for a sentence from your headline. If it isn't there, this is your problem.

How much to worry depends on your builder:

• Lovable: apps created from 13 May 2026 are rendered on the server. Older ones are pre-rendered when a verified crawler visits, and can be upgraded.
• Base44: serves crawlers a pre-rendered page, but its SEO setup is built for apps on a custom domain.
• v0: produces Next.js apps that render on the server by default.
• Replit: recommends Static Deployments for content-heavy sites.
• Bolt: its docs don't say, so check with View crawled page.

3. Your titles and addresses confuse Google

Even a readable page can fail when the details are off:

• Every page is titled "Vite + React", or just your app's name.
• A canonical tag points at the preview address or the homepage, which tells Google "ignore this page, use that one".
• The sitemap lists pages that no longer exist.

Prompt to paste into your builder:

Give every public page a unique title (under 60 characters) and a meta description (under 160 characters) that match what the page says. Make each page's canonical URL point to itself on my main domain, yourapp.com. Create a sitemap.xml that lists only my public pages with full URLs on that domain, and add a Sitemap line to robots.txt.

4. Your app lives at two addresses

If the same app answers at yourapp.lovable.app and yourapp.com, Google has to pick one, and it doesn't always pick yours. Choose your own domain, redirect everything else to it and verify that domain in Search Console. People trust a real domain more when deciding whether to click, too.

5. There's too little to rank for

A homepage with a headline, three feature bullets and a sign-up button gives Google almost nothing to match against searches. Nobody searches for your app's name before they've heard of it. They search for their problem.

So add a few public pages that answer what your future users type: who the app is for, how it works, pricing, and two or three pages on the questions they ask before buying. Write them from what you actually know about the problem. Pages that repeat what's already all over the internet rarely rank.

6. It needs time, and a few links

New sites take days to weeks to appear. Two things speed it up:

• Click Request indexing once for your most important pages, after you've fixed everything above. Clicking it every day doesn't help.
• Get a handful of real links: directories that fit your app, your social profiles, and mentions where your app genuinely helps someone. Links are how Google finds new sites and decides to trust them.

Before you move on

• site:yourapp.com shows your pages
• URL Inspection says "URL is on Google" for your homepage
• Your sitemap is submitted, and Bing Webmaster Tools is set up
• View crawled page shows your real text
• Every page has its own title, description and canonical
• One main domain, with every other address redirecting to it

If you'd rather not dig through Search Console first, the free LaunchPal launch check shows whether crawlers get your real text or an empty page, plus your titles, link preview and sitemap, in about a minute. No sign-up. Builder-specific notes are in the launch checklists.