Building an app with Lovable, Bolt, Base44 or Cursor now takes a weekend. Getting strangers to find it and sign up is harder. We wanted to see how ready the apps people actually ship are for that part.
So in the first days of November 2026 we ran our launch check on 312 apps that their makers had shared in public: showcase sites like Made with Lovable and Made with Bolt, and launch posts in Reddit’s builder communities. One check per homepage, the same one anyone can run for free.
Key findings
- Only 1 in 5 (19%) scores 90 or more out of 100 for launch readiness, the level we’d call ready to launch.
- 68% have no analytics, so the maker can’t see whether anyone visits.
- 53% of the apps on their own domain aren’t set up to send email, so sign-up emails are more likely to land in spam.
- 49% send an almost empty page to anything that doesn’t run JavaScript.
- 42% have a headline that doesn’t say what the app does or who it’s for.
- 37% take more than 4 seconds to show their main content on a phone.
- No analytics found68%
- Own domain not set up for email53%
- Almost empty page without JavaScript49%
- Headline doesn’t say what it is or who it’s for42%
- Main content takes more than 4 seconds on a phone37%
- No sitemap37%
- Page title missing, default, unclear or too long30%
- Link preview empty or without an image20%
Most of these don’t show up when you click around your own app. They’re the problems you only find out about from a stranger, a search engine or a spam folder.
Half the apps look empty without JavaScript
Many AI-built apps arrive in the browser as a near-empty page and fill in with JavaScript a moment later. You see your app. Anything that reads the raw page sees a few words and a script tag.
| Builder | Almost empty page | Only a little text |
|---|---|---|
| All 312 apps | 49% | 10% |
| Lovable (159) | 55% | 13% |
| Base44 (33) | 48% | 18% |
| Bolt (42) | 76% | 5% |
| Other tools (78) | 21% | 5% |
What this does and doesn’t mean: Google runs JavaScript, later and not always completely. Link previews on WhatsApp, Slack and LinkedIn don’t, and most AI assistants’ crawlers don’t either. Some builders also send a pre-rendered page only to crawlers they recognise. Lovable does this for older apps (apps created since 13 May 2026 render on the server), and so does Base44. Our check isn’t Google, so for those apps Google may see more than we did. The number is what a visitor without JavaScript gets.
Apps on their own domain were no better: 57% of Lovable apps on their own domain looked almost empty, against 52% on lovable.app.
To see what Google itself gets, use Search Console’s URL Inspection and View crawled page. The guide why your app isn’t showing on Google walks through it, and the prompt to render your pages for search engines fixes it in most builders.
Two thirds can’t see their visitors
68% of the apps had no analytics we could find. Base44 apps were the extreme, with 94% showing none.
Without analytics, a launch is a guess. You post somewhere, nothing seems to happen, and you can’t tell whether nobody came or everybody came and left. Even a simple, cookieless counter tells you whether people came and where they came from. The launch checklist has it as one of the first things to set up.
Half the custom domains aren’t set up for email
Of the 213 apps on their own domain, 53% were missing SPF or DMARC, the DNS records that tell Gmail and Outlook an email really comes from you. Without them, sign-up confirmations and password resets are more likely to go to spam, and the person who tried to sign up just looks like a visitor who left. Bolt apps on their own domain were the most often affected, at 66%.
It’s three DNS records and about half an hour. The guide why your sign-up emails go to spam has the steps, and the prompt to send emails from your domain does the builder side.
A headline a stranger doesn’t get
For the 171 pages with enough text to read, we looked at whether the headline says what the app does and who it’s for. 42% didn’t. Base44 stood out, with 15 of 18 readable headlines missing one or the other.
Most of the misses were about the audience: 59 of the 71 headlines said what the app does but not who it’s for. A first-time visitor gives a page a few seconds to decide whether it’s meant for them. Why visitors don’t sign up covers the fix, and the prompt to rewrite your headline gives your builder the brief.
Slow on phones, and missing basics
- Speed: 37% of the apps took more than 4 seconds to show their main content on a phone, measured with Google’s own speed test. Lovable apps were the slowest group, at 42%.
- Sitemap: 37% had none, and 64% of Bolt apps. A sitemap is how Google finds pages it would otherwise miss.
- Page titles: 30% had a title that was missing, still the builder’s default, too long, or didn’t say what the app offers. The title is the blue link in Google’s results. The prompt for SEO titles and descriptions fixes titles and descriptions together.
- Link previews: 20% showed an empty card or no image when the link was shared. Base44 apps were affected most, at 48%, and Lovable apps least, at 8%. The Open Graph preview tool shows what yours looks like.
Two things were almost always right. No app blocked AI crawlers, and only 2% blocked search engines.
Launch readiness by builder
Each check’s findings add up to a launch readiness score out of 100.
| Builder | Score 90 or more | Score under 70 |
|---|---|---|
| All 312 apps | 19% | 16% |
| Lovable (159) | 19% | 9% |
| Base44 (33) | 3% | 33% |
| Bolt (42) | 5% | 43% |
| Other tools (78) | 32% | 8% |
“Other tools” is mostly apps shared in r/SideProject and r/vibecoding where we couldn’t tell the builder. They scored best.
How we did it
- Which apps: 337 homepages shared publicly by their makers between 2025 and November 2026: the newest 150 on Made with Lovable, every live app on Made with Bolt, and apps linked in launch posts in r/SideProject, r/Base44, r/vibecoding, r/lovable, r/boltnewbuilders, r/replit and r/cursor. 312 could be checked. 20 couldn’t: the site was down, answered with an error, or is listed by a safety filter as an adult or unsafe site, which our check doesn’t open. 5 asked crawlers to stay away in robots.txt, so we skipped them.
- Builder: detected from the page where possible, otherwise taken from where the maker listed it.
- The check: the same 15 checks as our free launch check, one per homepage, run one site at a time with a pause between sites, as our crawler page describes.
- Privacy: we publish totals only. Individual results were deleted once the totals were counted, and no app is named.
- Limits: showcased apps aren’t all apps, and makers who share their work may be ahead of the rest. One check is one moment. Our check reads each page’s HTML as it arrives, without running its JavaScript, the way link previews and most AI crawlers do. For builders that pre-render pages for crawlers they verify, Google may see more. The speed numbers come from Google’s own test, which does run JavaScript.