Create topical authority without content sludge

You are assisting a human B2B SaaS SEO and AEO operator with Module 04: Create topical authority without content sludge.

Current lesson: Choose a revenue-connected topic
Objective: The cluster must strengthen a product or use-case page.
Required artifact: 90-day editorial map

BUSINESS CONTEXT I WILL PROVIDE
- Product, category, target market, pricing model, sales motion, and geography
- The priority customer segment and the commercial outcome for this 90-day cycle
- Topic universe exported from Ahrefs / Semrush
- Page/query baseline exported from GSC
- Definitions for any internal fields, stages, scores, and abbreviations

TASK
1. Start with one priority money page from Module 03.
2. List the prerequisite questions, implementation questions, mistakes, benchmarks, and objections around that decision.
3. Discard ideas that cannot naturally help the buyer reach or succeed with the product.
4. Anchor: Choose the revenue page and buyer decision the cluster must strengthen.
5. Produce: Capture expert input before drafting and retain source notes for fact checking.

REQUIRED OUTPUT
Return a table using these exact columns: Revenue page | Buyer job | Supporting questions | Current coverage | Pipeline fit | Cluster decision.
For every recommendation, cite the source row, URL, call note, or data point that supports it.
Add a confidence column in your analysis: High, Medium, or Low.
List missing evidence separately instead of guessing.
Finish with a section named HUMAN DECISIONS REQUIRED.

RULES
- Do not invent search volume, revenue, customer statements, product capabilities, or competitor facts.
- Do not treat correlation as causation.
- Preserve contradictory evidence and explain why it conflicts.
- Do not make the final priority or publishing decision. Prepare the evidence for a human owner.
- Use this example only as a format reference, not as evidence: For agency reporting software: client reporting KPIs, dashboard templates, reporting automation, and data-quality checks.

You are assisting a human B2B SaaS SEO and AEO operator with Module 04: Create topical authority without content sludge.

Current lesson: Find the information gap
Objective: A page needs a reason to exist beyond rewriting the current results.
Required artifact: 90-day editorial map

BUSINESS CONTEXT I WILL PROVIDE
- Product, category, target market, pricing model, sales motion, and geography
- The priority customer segment and the commercial outcome for this 90-day cycle
- Page/query baseline exported from GSC
- Content crawl exported from Screaming Frog
- Definitions for any internal fields, stages, scores, and abbreviations

TASK
1. Review the top results and cited AI sources for recurring sections and unsupported claims.
2. Interview a subject-matter expert for practical constraints, exceptions, and examples.
3. Choose an information gain: original data, workflow, template, test, or expert synthesis.
4. Research: Review search results, AI citations, communities, sales calls, and internal expertise for gaps.

REQUIRED OUTPUT
Return a table using these exact columns: Topic | SERP pattern | AI source pattern | Missing evidence | Information gain | Expert.
For every recommendation, cite the source row, URL, call note, or data point that supports it.
Add a confidence column in your analysis: High, Medium, or Low.
List missing evidence separately instead of guessing.
Finish with a section named HUMAN DECISIONS REQUIRED.

RULES
- Do not invent search volume, revenue, customer statements, product capabilities, or competitor facts.
- Do not treat correlation as causation.
- Preserve contradictory evidence and explain why it conflicts.
- Do not make the final priority or publishing decision. Prepare the evidence for a human owner.
- Use this example only as a format reference, not as evidence: Instead of another KPI list, publish anonymized benchmark ranges by agency size and client model.

You are assisting a human B2B SaaS SEO and AEO operator with Module 04: Create topical authority without content sludge.

Current lesson: Create evidence-led briefs
Objective: A brief should direct research and decisions, not dictate a word count.
Required artifact: 90-day editorial map

BUSINESS CONTEXT I WILL PROVIDE
- Product, category, target market, pricing model, sales motion, and geography
- The priority customer segment and the commercial outcome for this 90-day cycle
- Content crawl exported from Screaming Frog
- Expert brief inputs exported from CRM / Gong
- Definitions for any internal fields, stages, scores, and abbreviations

TASK
1. Name the reader, situation, question, and action the page must enable.
2. List required first-party and external sources before outlining.
3. Specify answer-first sections, examples, visual proof, internal links, and claims requiring review.
4. Differentiate: Commit to original data, a real workflow, a tool, a visual teardown, or expert synthesis.
5. Distribute: Plan sales enablement, community participation, partner outreach, and newsletter reuse.
6. Refresh: Update based on rankings, citations, conversions, product change, and evidence decay.

REQUIRED OUTPUT
Return a table using these exact columns: Section | Question | Evidence | Visual | Internal link | Reviewer | Pass condition.
For every recommendation, cite the source row, URL, call note, or data point that supports it.
Add a confidence column in your analysis: High, Medium, or Low.
List missing evidence separately instead of guessing.
Finish with a section named HUMAN DECISIONS REQUIRED.

RULES
- Do not invent search volume, revenue, customer statements, product capabilities, or competitor facts.
- Do not treat correlation as causation.
- Preserve contradictory evidence and explain why it conflicts.
- Do not make the final priority or publishing decision. Prepare the evidence for a human owner.
- Use this example only as a format reference, not as evidence: The brief requires one real dashboard, a downloadable QA checklist, and review by the analytics lead.

You are assisting a human B2B SaaS SEO and AEO operator with Module 04: Create topical authority without content sludge.

Current lesson: Publish at the quality cadence
Objective: One defensible piece beats five interchangeable posts.
Required artifact: 90-day editorial map

BUSINESS CONTEXT I WILL PROVIDE
- Product, category, target market, pricing model, sales motion, and geography
- The priority customer segment and the commercial outcome for this 90-day cycle
- Expert brief inputs exported from CRM / Gong
- Topic universe exported from Ahrefs / Semrush
- Definitions for any internal fields, stages, scores, and abbreviations

TASK
1. Estimate research, expert, design, writing, and review capacity honestly.
2. Sequence content so supporting articles link into the priority money page as they publish.
3. Refresh based on performance and changed evidence, not an arbitrary date.
4. Brief: Specify answer sections, evidence, examples, visuals, internal links, reviewer, and conversion path.

REQUIRED OUTPUT
Return a table using these exact columns: Asset | Research hrs | Expert hrs | Design hrs | Review hrs | Ship week | Owner.
For every recommendation, cite the source row, URL, call note, or data point that supports it.
Add a confidence column in your analysis: High, Medium, or Low.
List missing evidence separately instead of guessing.
Finish with a section named HUMAN DECISIONS REQUIRED.

RULES
- Do not invent search volume, revenue, customer statements, product capabilities, or competitor facts.
- Do not treat correlation as causation.
- Preserve contradictory evidence and explain why it conflicts.
- Do not make the final priority or publishing decision. Prepare the evidence for a human owner.
- Use this example only as a format reference, not as evidence: Ship four expert pieces in 90 days, each supporting one page and one sales objection, instead of 30 generic posts.