Why isn't my vibe-coded app showing up on Google?

You launched. You search Google for your app's name, and nothing comes up. Or a random preview link shows up instead of your real site.

This is really common. When we checked 76 live vibe-coded apps, 67% had at least one problem that makes it harder for Google to find them. Most of these are quick fixes. Here's how to work out what's going on with yours.

First: is it just too new?

Google doesn't find new sites instantly. A brand-new site with no links pointing to it can take days or a few weeks to show up, even when everything is set up right.

Do a quick check: search Google for site:yourdomain.com (use your real address). If nothing shows up, Google hasn't added your site yet. If some pages show up, Google knows about you, and the question is why it's not showing the pages you want.

Either way, the next step is the same.

Step 1: Tell Google your site exists

Google has a free tool called Search Console for site owners. It shows whether Google can see your site and lets you ask it to visit.

1. Go to Google Search Console and add your domain.
2. Prove you own it. The usual way is adding a short TXT record wherever you bought your domain.
3. Once you're in, paste your homepage address into the search bar at the top (that's URL Inspection) and click Request indexing.
4. Submit your sitemap under Sitemaps (see step 3 below if you don't have one).

It's the single most useful thing you can do for search, and it costs nothing.

Step 2: Tell Google which address is the real one

This was the most common search problem in our study: 54% of apps didn't tell Google which address counts.

Your app may answer at several addresses: the plain domain, www., a .lovable.app or .netlify.app address, with and without a slash at the end. To Google, those can look like copies of the same page, and it may pick the wrong one or split your ranking between them. A canonical tag is a hidden line on each page that says "this is the real address."

Add a canonical link tag to every page that points to that page's own main https address on my real domain (not a preview or .app address). Make sure each page's canonical is its own address, not always the homepage. If my site also answers on www or a platform subdomain, redirect those to my main domain.

Step 3: Give Google a list of your pages

28% of apps in our study had no sitemap. A sitemap is a simple list of your public pages that Google reads. Without one, Google has to find pages by following links, which is slow for a new site with few links.

A few apps (8%) also had no robots.txt, the small file that tells search engines what they may look at and where the sitemap is.

Create a sitemap.xml at the root of my site that lists every public page with its full https address on my real domain, and a robots.txt that allows search engines and points to the sitemap. Leave out login, dashboard, and account pages. Tell me the sitemap address so I can submit it in Google Search Console.

Step 4: Give every page a real title and description

The title and description are what people see in Google results. If your page title still says "Vite + React" or your app's name with nothing else, Google has very little to go on.

In our study, 13% of apps had a search description that was too short or too long, and a few had none at all.

Give every public page its own title (under 60 characters, saying what the page is for in plain words, then my app name) and its own meta description (about 120 to 155 characters, written for a person deciding whether to click). Don't reuse the homepage title on other pages.

Step 5: Make sure Google isn't being told to stay away

Sometimes a site is quietly telling Google to ignore it. This can happen when a "noindex" setting meant for a test version gets left on, or when robots.txt blocks everything.

Check my live site for anything that stops search engines from listing it: a robots meta tag or X-Robots-Tag header with noindex, or a robots.txt that disallows everything. Remove anything like that from public pages, but keep login, dashboard, and account pages out of search.

Step 6: Make sure Google sees words, not an empty page

Many vibe-coded apps build the whole page in the browser with JavaScript. Google can usually read those pages, but it can take longer, and if your homepage shows a spinner or a login screen first, there may be almost nothing for Google to read.

The fix is simple: make sure your homepage shows real text about what your app does, without logging in. A clear headline and a few sentences go a long way. In Search Console, URL Inspection → View tested page shows you what Google actually sees.

The short version

• New sites can take a few weeks. Check with site:yourdomain.com.
• Add your site to Google Search Console, request indexing, and submit your sitemap.
• Add canonical tags pointing at your real domain.
• Have a sitemap.xml and robots.txt.
• Give every page its own title and description.
• Make sure nothing says "noindex" on public pages, and the homepage has real words on it.

Our study only checked homepages, so your other pages may have their own issues. Our launch checklist covers the rest of the basics. Want to check your canonical tag, sitemap, robots.txt, title, and description in one go? Throttle Bird has a free scan, with paid reports for deeper fixes.