Track rankings, citations, and pipeline

You are assisting a human B2B SaaS SEO and AEO operator with Module 09: Track rankings, citations, and pipeline.

Current lesson: Separate leading and outcome metrics
Objective: Shipping and visibility move at different speeds.
Required artifact: Search visibility scorecard

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
- Demand visibility exported from GSC + rank tracker
- AEO visibility exported from Citation tracker
- Definitions for any internal fields, stages, scores, and abbreviations

TASK
1. Track leading work: fixes shipped, pages improved, passages added, source wins, and reviews earned.
2. Track visibility: index coverage, ranking distribution, non-brand clicks, answer inclusion, citation share, and accuracy.
3. Track business outcomes: qualified CTA actions, assisted opportunities, sales usage, and influenced pipeline.
4. Define: Agree on metric name, formula, source, grain, window, owner, and decision before building a dashboard.
5. Review weekly: Use leading indicators to catch implementation and discovery problems.

REQUIRED OUTPUT
Return a table using these exact columns: Metric | Definition | Formula | Source | Grain | Window | 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: A new comparison page may show indexation and source pickup before it produces a closed opportunity.

You are assisting a human B2B SaaS SEO and AEO operator with Module 09: Track rankings, citations, and pipeline.

Current lesson: Build stable cohorts
Objective: Aggregate sitewide numbers can hide what changed.
Required artifact: Search visibility scorecard

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
- AEO visibility exported from Citation tracker
- Behavior cohorts exported from GA4 / product analytics
- Definitions for any internal fields, stages, scores, and abbreviations

TASK
1. Group pages by type, topic, segment, and publish/improvement date.
2. Group prompts by tier, archetype, segment, and engine.
3. Compare the same cohorts over time and annotate releases, campaigns, and major search changes.
4. Baseline: Freeze priority page, query, prompt, source, conversion, and pipeline cohorts.

REQUIRED OUTPUT
Return a table using these exact columns: Cohort | Start date | Pages | Queries / prompts | Baseline | Target | Notes.
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: Track the eight improved comparison pages separately from 300 historical blog URLs.

You are assisting a human B2B SaaS SEO and AEO operator with Module 09: Track rankings, citations, and pipeline.

Current lesson: Connect search to pipeline honestly
Objective: B2B journeys are multi-touch and dark.
Required artifact: Search visibility scorecard

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
- Behavior cohorts exported from GA4 / product analytics
- Pipeline cohorts exported from HubSpot / Salesforce
- Definitions for any internal fields, stages, scores, and abbreviations

TASK
1. Capture landing page, self-reported source, known content touches, and sales-confirmed influence.
2. Report sourced and assisted pipeline separately.
3. Review relevant account journeys qualitatively each month to find repeatable paths.
4. Instrument: Validate analytics events, CRM capture, consent behavior, and campaign metadata.
5. Review monthly: Evaluate visibility, citations, actions, opportunities, and confounders.
6. Decide: Record continue, expand, repair, test, or stop decisions with the evidence used.

REQUIRED OUTPUT
Return a table using these exact columns: Layer | Metric | Baseline | Current | Delta | Threshold | 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: An opportunity reports “podcast,” first visited a comparison page, and later returned through brand search; preserve all three signals.

You are assisting a human B2B SaaS SEO and AEO operator with Module 09: Track rankings, citations, and pipeline.

Current lesson: Write the monthly decision narrative
Objective: A dashboard without interpretation does not operate the program.
Required artifact: Search visibility scorecard

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
- Pipeline cohorts exported from HubSpot / Salesforce
- Demand visibility exported from GSC + rank tracker
- Definitions for any internal fields, stages, scores, and abbreviations

TASK
1. State what moved, why you believe it moved, confidence level, and what did not move.
2. Show the evidence chain from shipped work to visibility to buyer behavior.
3. Choose three next actions and one thing to stop or defer.
4. Join: Connect work shipped to affected assets and demand families.
5. Explain: Report uncertainty, lag, model volatility, and attribution limits directly.

REQUIRED OUTPUT
Return a table using these exact columns: Review date | Evidence | Confounder | Decision | Owner | Next check | Confidence.
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: “Citation share rose after two source wins” is a hypothesis; name the matching prompts and URLs, then retest.