Plan in concrete output and cadence
Plan the cycle as concrete deliverables spread across the weeks. The Month-1 shape is the model:| Week | Output |
|---|---|
| Week 1 | Research and strategy; generate the first landing pages and 3 blog posts |
| Week 2 | Publish: first blog posts and a batch of landing pages go live; index them; collect data |
| Week 3 | Analytics setup (PostHog); keep publishing on schedule |
| Week 4 | Review and calibrate next cycle from data |
Indexing is the real bottleneck
Generating pages is fast; getting them indexed is what limits your pace. Your manual GSC crawl budget starts small (roughly a handful to a couple dozen URLs per day) and grows as the domain earns trust. So:- Front-load indexing on the priority pages, and keep a backlog you submit over the following days (2.5.3).
- Don’t publish 200 pages in a day expecting them all indexed by tomorrow; sequence them.
- IndexNow (Bing) is automated on publish and helps. Google indexing is the slower, manual path.
Planning a cycle’s output
- Decide the cycle’s committed output (landing pages plus blog posts) with the client at the review.
- Split it across the weeks, front-loaded, so wins land early.
- Sequence indexing so the crawl budget isn’t the thing that stalls you.
- Park overflow keywords and pages in the backlog rather than forcing them into the cycle (3.4 edge cases).
❓ [needs Raymond] The standard committed output per cycle (how many landing pages + posts a typical package includes, and how it splits across weeks) to anchor this. The client-review SOPs 3.7/3.8 reference an “Output Plan” — confirm the canonical numbers. (Express purely as pages/posts per week — no billing-unit language.)Related: 3.2 Monthly planning · 3.15 Agency standardization