Show the visitor something instantly; show Google nothing until the page is actually good. Two different audiences, two different clocks.
When network growth builds a new site on demand, two things are true at once and they pull in opposite directions:
and must not stare at a spinner while an AI writes 800 words.
indexed, is how you earn a scaled-content demotion (see the SEO cliff).
Most builders serve one clock and lose the other: either the visitor waits for the AI, or the crawler catches the site mid-bake.
Build the skeleton synchronously, generate the substance asynchronously, and gate indexing on quality. The visitor gets an instant, real-looking page from the data we already have (name, photos, hours, map). The heavy work — AI content, photo vision, deep research — is queued, never run inside the visitor's request (that request-time discipline is also what keeps us off the 521 cliff). And the page carries noindex until it clears a quality score (place_resolver_min_score); only then does it become indexable. Google meets the site as a finished thing or not at all.
The clever part is realizing the visitor and the crawler are different audiences on different clocks, and refusing to compromise either. Fast for the human, invisible until good for the machine. It is the same instinct as the store-link confidence gate: better to show nothing than to show something not-yet-right. Nothing about "build a page" tells you to split those two timelines. Noticing that you must is the whole trick.