Skip to content
StatusBird Studiofor AI-built stores

Independent research · StatusBird LLC · updated 2026-11-01 08:24 UTC

The AI-Built Store Index

How many web stores built with Lovable, Bolt, v0, Replit and similar tools exist in public sources, and what search engines, AI assistants and shoppers actually receive from them. Aggregates only. No store is named.

235AI-built stores measured, from 901 live AI-built sites and 2120 candidates
51.9%hand search engines and AI crawlers an empty page (fewer than 60 words before JavaScript)
97.9%have no Product structured data on the homepage, of those rendered
82.6%have no sitemap.xml
3.8%ship a missing or builder-default title
0.4%carry a credential-shaped string in a public JavaScript bundle (576 bundles scanned, detection only)

By builder

Builders with at least ten measured stores. A store is counted for a builder when its public HTML carries that builder's markers.

BuilderStoresEmpty to crawlersNo sitemapDefault titleNo product dataMedian a11y failuresLCP over 2.5 sJS errors on loadCredential pattern
Lovable23151.9%83.5%3.9%97.8%524.2%13.4%0.4%
All stores23551.9%82.6%3.8%97.9%524.3%14.0%0.4%

More measurements, all stores

Homepage tells search engines not to index it (noindex)0.9%
No meta description2.1%
No canonical tag80.9%
robots.txt blocks at least one AI crawler0.9%
Median words a crawler receives from the homepage13
At least one image without alt text11.9%
Median largest contentful paint1.9 s
Advertising trackers fire before any interaction7.7%
Public API key that needs restrictions or row level security28.5%

Data: index.json. Aggregate counts may be quoted with attribution to the AI-Built Store Index by StatusBird LLC and a link to this page.

Method

Where the sites come from
Certificate transparency logs for builder-hosted domains, and public code repositories that a builder synced and that contain commerce code (cart, checkout, payment provider, product). A repository's published site is taken from its homepage field or README, or inferred from its name and verified by fetching. Common Crawl's URL index is added when it answers. This finds a sample, not the population; it is biased toward stores whose owners publish code or use a builder-hosted address.
What counts as a store
The rendered homepage shows a cart, checkout or buy control, or carries Product structured data, or shows three or more prices on a site whose code contains commerce logic. Placeholder projects (builder welcome pages) are excluded.
What a crawler receives
One plain HTTP fetch of the homepage with an identified user agent, no JavaScript. Words are counted after removing scripts, styles and markup. Fewer than 60 words with an application root element counts as an empty shell. Titles matching a builder's default (for example "Vite App") count as default.
What a shopper sees
One load in headless Chromium with a settle period: rendered text, Product structured data, images without alt text, axe-core WCAG 2.1 A and AA failures (critical and serious), largest contentful paint, JavaScript errors, trackers requested before any interaction.
Credential patterns
Up to three of a site's own JavaScript files are matched against documented key prefixes (Stripe secret, AWS, SendGrid, OpenAI, Anthropic, private key blocks) and JSON web tokens are decoded only to read their role claim. Values are never stored. No database, API or data endpoint belonging to any site is ever queried.
What is published
Aggregates only. No store is named on this page or in the data file. A store owner who wants their own measurements can run the free check. Builders named here are identified from public page markers; StatusBird LLC is not affiliated with any of them.
Refresh
Monthly. Each edition re-fetches every site so the trend is like for like.

Questions, corrections, or a builder's response: studio@statusbird.io. Responses from builders are published verbatim alongside the next edition.