The Launch Batch: 10 to 15 Pages, Shipped in Waves
Launch 10-15 core pages first — codes, tier, guide queries first — then 10+ weekly with drafts flipped one by one. Stage three graduates here.
A true scene first
On day four of content production the urge arrives: have AI generate 50 pages and fill the site. The hard-won lesson — too many pages in version one dilutes quality and drags the whole site’s rankings. Google grades a site holistically; 20 weak pages inside 50 drag the 30 good ones down with them.
The three-line schedule
- A first release of 10-15 core pages is enough — codes, tier list, guide queries first. That’s precisely the output of the last four lessons: 1 codes page + 1 beginner guide + 3 boss guides + 1 tier list + 1 FAQ page + 3 window-query pages (Lesson 8’s list, cashed in).
- Add 10+ pages weekly —
draft: truedrafts verified and flipped one by one; new query pages keep following the Lesson 8 list downward. - Batch production obeys the same rule — when you later mass-produce dozens of pages (Lesson 27’s pipeline), the discipline stands: generate in batches, ship in batches.
When the batch is green, walk away
First release all green? Move to the next stop (launch) — don’t polish forever. The practical reason: unpublished content lives in a vacuum; you have no idea how players and Google respond. Post-launch data (which queries got impressions, which pages got clicks) is the best navigation for the next batch. Perfectionism is procrastination with better handwriting.
Three classic mistakes (made for you in advance)
- Dumping every draft at once: dilutes quality, drags rankings — batching is a discipline, not a suggestion.
- Hitting a page count at quality’s expense: can’t fill 15 good ones? Ship 10. The Lesson 16 quality line doesn’t bend.
- Flipping drafts without verifying: bulk-flipping drafts is bulk bare-shipping. Flipping follows verification; only generation comes with a button.
Three words to know (just these)
- First release: the opening batch of core pages, 10-15 — the site’s storefront and starting line.
- In waves: a fixed rhythm of 10+ weekly — slower is fine, messy never.
- Flip live: verification-then-publish, one draft at a time — never one button.
✅ Acceptance (all must hold)
- ☐ The first release of 10-15 pages all passed the Lesson 16 pipeline
- ☐ Remaining drafts all carry draft flags, with a weekly flip hour on your calendar
- ☐ You decided to stop and move to launch — this line matters most
Stage three — graduated
Stage three is done: the content engine runs — queries become pages, pages pass the gate, the schedule has a rhythm. But everything lives on your computer; players and Google still can’t see you. Next stop: put the site on the global shelf. Go to Lesson 18 · Put Your Site Online