Skip to main content

Your Working Session: Present & Interpret the Baseline

This is the core of the program — and it is an interpretation session, not a build session. Every report referenced here was already run during pre-work.

Don't try to select a brand, build a question list, run Citation Monitor, review competitors, analyze pages, test chatbot answers, and build an action list all live in one sitting — reports are asynchronous, and trying to generate a baseline from nothing while your team watches either runs long or produces a shallow result. Do the reporting in Getting Ready first. This block is where your team's own context turns prepared findings into a prioritized plan.

Step 1: Present the Headline Baseline​

Open with Citation Monitor's score and verdict tier (Emerging / Present / Strong / Dominant) — it's the single number to anchor the session on. Don't read the full PDF out loud; state the number, the tier, and one sentence on what it means.

Real example to reference: in a real run, the headline score was 32/100 ("Emerging"), but the useful finding wasn't the number — it was that the one branded query landed in the Amplify quadrant (ranked and cited) while all three unbranded category queries landed in Full Gap or Content Gap, with a named competitor (Ada) cited instead on every one of them.

Step 2: Go Deep on 1–2 Pre-Selected Findings​

Before the session, pick the one or two findings from pre-work that are the most concrete or most likely to surprise your team — a weak page from URL Analysis, a missing signal from Agent-Readiness or AI Footprint, or (if you have usage history) a specific conversation from Q&A Insights. Walk through it in real depth instead of skimming every report.

What to point out live: a page can rank in Google and still fail nearly every GEO signal — a real trust-center example scored 52.4/100 overall despite ranking reasonably, because it had zero FAQ schema, no visible dates, and vague claims like "industry-standard encryption" instead of named standards. That's the exact kind of gap this step should land.

Step 3: Get Your Team's Reaction and Context​

Ask directly: "Does this match what you'd expect? Is this actually a priority page? Is there context we're missing?" This is the part a report alone can't do — people closer to the business know things no audit surfaces, and their input here is what turns a generic finding into a correctly-prioritized one.

Step 4: Build the First Prioritized List, Together​

Take the findings from Steps 1–3 and sort them into Critical / High / Medium / Low using the deliverable template — live, with the room weighing in. Don't wait for every report to get equal treatment; a focused list from what was actually discussed is a legitimate first version, and it becomes the raw material for The 30-Day Roadmap block that follows.

Output by the End of This Block​

  • Baseline citation rate — the Citation Health Score and verdict tier, written down and dated
  • A confirmed, prioritized gap list — built with the team's own input, not just the raw report output
  • The team's own reaction on record — which findings were confirmed, pushed back on, or given more context
  • A clear next test date — put an actual date on the calendar before the session ends; a baseline nobody re-tests is not a loop, it's just a report

What Makes This Credible​

  • Uses real questions and live answer behavior — nothing in the underlying reports is simulated; every score reflects an actual model call against actual content
  • Creates re-testable lists — the Citation List and/or Keyword List built during pre-work persists after the session and can be re-run with zero setup next time
  • The team's context is captured, not just the score — Step 3 is what separates this from reading a PDF alone
Last updated on