An early B2B SaaS site does not need one hundred pages. It needs a clear answer to a small set of customer questions. The useful unit is not a keyword by itself. It is a search job: who is searching, what decision are they trying to make, and what would make the page useful enough to keep?
Start with decision stage
Use four stages: learn, compare, implement, and measure. A person searching for “what is customer feedback routing” needs a definition and examples. A person searching for “Dify vs n8n for content operations” needs a comparison with trade-offs. Treating both queries as the same content job creates a vague article that satisfies neither reader.
Map one primary page to one job
For each topic, write five fields before drafting:
- Reader role and company context.
- Decision they need to make.
- Primary question in their own words.
- Evidence or examples required to answer it responsibly.
- The next useful page or action, if any.
This is also a quality gate for AI-assisted drafting. If the model cannot state the buyer decision, it should not draft the page.
Do not treat impressions as validation
Search impressions, clicks, and rankings are observations. A low-impression page may be new, unindexed, misaligned with demand, or technically blocked. Diagnose index coverage and intent fit before rewriting. Google’s Search Console documentation is the primary reference for the metrics, not a shortcut to causal conclusions.
A first-site rule
Publish fewer pages, but give each a distinct job. Record the query family, target reader, source check, editor, publication date, and next review date. This is enough structure to learn from the first six weeks of data.