71% of sites built on the platform get their first page indexed by Google within 48 hours of deploy. The average Lighthouse performance score across a random sample of a few hundred live builds sits at 94. Median time from "publish" to first organic impression in Search Console is six days. And sites that launched with twelve or more pages got fully crawled about three times faster than sites that launched with just a homepage and came back to add pages later.
The first three numbers are the ones people ask about, and they're the boring, expected kind of good — clean HTML, sensible meta tags, no render-blocking garbage, so Googlebot has an easy time and Lighthouse has nothing to complain about. Machines are good at producing structurally correct pages. Nobody's surprised that automated output beats the median hand-coded WordPress theme on a technical audit.
The page-count number is the one that made us go back and check the query twice, because it runs against the advice most people give first-time builders: ship something small, get it live, iterate. That advice is fine for momentum. It's bad for indexing speed, and the reason is crawl budget — a concept most people building their first site have never heard of and genuinely don't need to, until the moment their site sits un-indexed for two weeks and they can't figure out why.
What crawl budget actually means for a new site
Googlebot doesn't crawl every page of every site on every visit. New domains especially get a modest allowance — a handful of requests, spread over days, until the bot builds enough confidence in the site to spend more attention on it. A single-page launch gives the crawler exactly one thing to look at, one set of internal links (usually none), and no signal about what else is there. It comes back, sees the same one page, and has no strong reason to come back sooner next time.
A twelve-page launch is a different object entirely. It has an internal link graph on day one — nav links, footer links, maybe a blog index pointing at three posts, a couple of category pages pointing at each other. Googlebot discovers page two while crawling page one, queues it, and often fetches several pages in the same visit instead of one page per visit spread across a week. The site behaves like it has momentum before a single backlink exists, because the momentum is structural, not earned.
This is also why the "add pages later" pattern is quietly worse than it looks. Every time a thin site adds a new page, it's asking the crawler to notice a change on a domain it's already decided is low-priority. That's a slower loop than giving the crawler a reason to prioritize the domain from the start. We've seen sites go from three pages to fifteen over a month and watch their crawl frequency barely move, versus a fifteen-page day-one launch that gets fully indexed inside a week.
Where this actually shows up in the builder
It's part of why the planning stage pushes toward a handful of real pages for anything meant to be found in search — not padding, actual pages with actual content: an about page, a couple of feature or use-case pages, a starter blog post or two if the site type calls for it. A landing page with no destinations behind it isn't a smaller version of a real site, it's a different, worse category of thing for a crawler to evaluate. The plan you approve before a build starts is where that gets decided, and it's worth pushing back on a plan that gives you one page when your goal is organic traffic — see reading the plan, and changing it if you want the mechanics of how.
None of this substitutes for the parts that take longer regardless of how many pages you launch with — backlinks, topical authority, the twenty-page content history that actually convinces Google you're worth ranking above an established competitor. A site with twelve well-structured pages and zero external links is not going to outrank an eight-year-old domain for a competitive term in week two. What the page-count effect buys you is the boring infrastructure part: getting discovered, getting crawled, getting indexed, so that the content you publish afterward has somewhere to land instead of sitting invisible for a month while the crawler slowly figures out you exist.
The technical scores are table stakes now — every serious builder, AI or not, can hit a 90+ Lighthouse score if someone bothers to check. The thing actually worth optimizing, and the thing almost nobody thinks about until it costs them two weeks, is giving the crawler a reason to show up more than once.
