Establish the public technical baseline
Begin with what a crawler or answer engine can actually access: status codes, redirects, canonical tags, language, headings, structured data, robots policy, sitemap coverage and stable page identity. These checks can be verified from public responses and repeated after a deployment.
A technical score is directional. It does not establish rankings, qualified traffic or revenue, and it should not be used as a substitute for Search Console or analytics.
- Crawlability and indexability
- Canonical and language signals
- Structured product and article identity
- Sitemap and AI-readable resources
Map demand to the product journey
Keyword volume alone does not decide what to publish. Group queries by market, audience, problem and stage, then compare them with current landing coverage and the product action a visitor can take. Search demand without an appropriate page or conversion path becomes traffic without learning.
Use live search or approved keyword data when available. If no provider is connected, label the output as a research plan rather than claiming current rankings or volume.
- Literal problem and category queries
- Evaluation and comparison intent
- Use-case and workflow questions
- Branded and navigational demand
Design pages for citation and inspection
Pages are easier to cite when their claims, methods, definitions and update dates are explicit. The primary product, workflow or evidence should be visible rather than buried under generic marketing copy. Structured data supports identity but cannot compensate for thin or duplicated content.
Each page needs a reason to exist beyond a swapped keyword. Include an original decision framework, a working tool, a transparent case boundary or a genuinely reusable asset.
- Clear page purpose and literal heading
- Source and evidence labels
- Author or accountable publisher
- Descriptive internal links
- Visible review and update date
Prioritize a connected backlog
Rank technical, content and citation work using impact, evidence, effort, risk and dependency. A missing canonical may block page identity; a new article may depend on live SERP research; a conversion page may need product proof before it should be indexed.
This backlog should connect each item to an owner, source, expected result and verification route rather than becoming a calendar of unreviewed content.
- Fix blockers before expansion
- Avoid thin programmatic pages
- Keep noindex for unready templates
- Link content to Skills, tools and use cases
Measure the right layer
Separate discovery, intent, adoption and business outcome. Search impressions and citations indicate discovery. Relevant page engagement and tool completion indicate intent. Qualified product behavior or revenue requires a first-party join.
After a change, compare the same query, market, page and time window. Preserve seasonality, rollout dates and measurement gaps so movement is not over-attributed to one edit.