Ship a SERP-first, rules-based intent framework you can drop into your deck within 24–48 hours. You will leave with a taxonomy, override rules, a page-type matrix, a batch-tagging template, and 5–7 worked examples that leadership can accept without debate.

Prerequisites

• Ahrefs keyword CSV export
• Google Search Console and GA4 access
• Ability to review live SERPs
• Time to prepare 5–7 examples
• No extra paid tools

Expected result

• Deck includes the finalized framework and 5–7 examples
• In-scope queries are remapped to the correct page types and deliver higher CTR or engagement without ranking loss
• A tagging template is live so the team can label intent at scale with light spot-checks

Framework goals and acceptance criteria for defensible intent mapping

If you do not define clear goals and pass-fail criteria, labels get challenged and remapping risks rankings. Lock these in so your framework is review-proof and reproducible.

Goals

• SERP-first: infer intent from what Google surfaces, not from our preferences
• Reproducible: rules are thresholded and tool-agnostic within our current stack
• Non-overlapping: each query has one primary intent and a small, allowed set of page types
• Scalable: batch tagging for 1,000+ keywords with minimal manual checks
• Low-risk: page-type decisions that lift CTR fast without jeopardizing positions

Acceptance criteria

• Taxonomy is limited, unambiguous, and mapped to allowed page types
• Override hierarchy specifies which SERP signals win when they conflict
• Thresholds are numeric, not subjective language
• Page-type decision matrix specifies when to keep, consolidate, or split
• 5–7 worked examples include SERP rationale and a final page-type call
• Tagging template and confidence scoring are live in Sheets or your current repo
• QA protocol defines sampling, spot-checks, and documentation

Conditions for success in the deck

• Stakeholders can read a single slide and restate the taxonomy, overrides, and page-type calls without asking “what does this mean”
• Examples show SERP screenshots or logged top-10 page types with counts
• The team can tag new keywords and land on the same outputs independently

Early warning signs

• Stakeholders ask for definitions repeatedly or argue about edge labels
• Labels depend on “it depends” without a threshold
• Page-type decisions conflict with what ranks for the top 10

Failure condition even if the framework looks complete

• Because the slide lacks SERP evidence per example and thresholds next to each rule, leadership cannot defend the mapping to peers. To pass, add the override order and numeric thresholds on the slide and attach a log of SERP page-type counts per example.

Intent taxonomy and allowed page types (with non-overlap rules)

A compact taxonomy avoids overlap and speeds decisions. Tie each intent to allowed page types so the team makes consistent format choices.

Primary intents

1. Navigational – user seeks a specific brand/site or page

• Allowed page types: Homepage, brand hub, login, product home, docs hub, pricing of the named brand
• Non-overlap: If brand-name + sitelinks/knowledge panel for that brand are present, it is Navigational even if modifiers look commercial

2. Informational – Definition/Concept – user seeks to understand what something is

• Allowed: Glossary definition, concept explainer, “What is X” article
• Non-overlap: Do not mix with How-to; if the top results are tutorials with steps, use Informational – How-to

3. Informational – How-to/Problem-solution – user seeks steps to do a task

• Allowed: Step-by-step tutorial, checklist, template download, video guide
• Non-overlap: Do not route to product landing unless 60 percent of top 10 are vendor tutorials tied to products

4. Commercial Investigation – user compares options before buying

• Allowed: Best-of lists, alternatives, vs pages, category hubs, case studies roundups
• Non-overlap: If 60 percent of top 10 are product sign-up or pricing pages, treat as Transactional

5. Transactional – user intent to buy, sign up, price, download

• Allowed: Pricing, product landing, demo/trial sign-up, plan comparison table, integration landing
• Non-overlap: If “pricing” is generic like “CRM pricing” but top 10 are mostly “Best CRM pricing” listicles, keep as Commercial Investigation

6. Local Service/Location-intent – user seeks providers in a place

• Allowed: Location or service pages with NAP, map, service area, Google Business Profile link
• Non-overlap: If a Local Pack appears for non-geo modified queries, treat as Local

Optional category when clearly dominant in SERP 7) News/Trends – time-sensitive updates dominate

• Allowed: News post with publish date, Top stories markup
• Non-overlap: Only use if Top stories or timestamps dominate above the fold

Rules to prevent overlap

• One primary intent per keyword
• If SERP is mixed, pick the majority by page-type count with a 60 percent threshold
• If no page-type reaches 60 percent, choose the intent that best matches the top two result types and default to safer format:
  • Between Commercial Investigation and Transactional: choose Commercial Investigation
  • Between Definition and How-to: choose How-to only if 3 or more step-by-step tutorials rank in the top 5

SERP signal rules to infer intent reliably (override hierarchy)

When signals conflict, follow a strict override order. Use numeric thresholds so outputs are defensible.

Override order, highest to lowest

1. Branded navigational dominance

• Signals: Knowledge panel for the brand, site sitelinks, home/login/doc pages in top 3
• Rule: If brand match is exact and 2 or more top-3 results are that brand’s pages, label Navigational

2. Local Pack or Maps dominance

• Signals: Local Pack above organic, map pins, “near me”, city/state in query
• Rule: If Local Pack is present or geo-modifier exists, label Local Service/Location-intent

3. Shopping/merchant-heavy or app store dominance

• Signals: Shopping ads or product grid above the fold, app store results dominate
• Rule: If 3 or more of top 5 are product or app listings, lean Transactional

4. News/Top stories dominance

• Signals: Top stories carousel above the fold, timestamped news in top 3
• Rule: If present and top 3 include 2+ recent news entries, label News/Trends

5. Page-type majority across organic top 10

• Count the first 10 organic URLs by page-type:
  • Aggregators/listicles/comparisons
  • Vendor product or pricing
  • Tutorials/how-to
  • Glossary/definition
  • Location/service pages
• Thresholds:
  • 60 percent+ aggregator/comparison => Commercial Investigation
  • 60 percent+ vendor pricing/product/trial => Transactional
  • 60 percent+ tutorials with steps => Informational – How-to
  • 60 percent+ definition pages => Informational – Definition

6. Query modifiers as tiebreakers

• Strong Commercial Investigation modifiers: best, top, compare, vs, alternative, review, ranking
• Strong Transactional modifiers: pricing, cost, trial, demo, buy, download, coupon, deal
• Strong How-to modifiers: how to, guide, tutorial, step, template, checklist, example
• Strong Definition modifiers: what is, meaning, definition
• Local modifiers: near me, city, state, country, provider, service
• Rule: If no 60 percent majority by page-type, apply modifiers to break ties

7. Our current ranking page as a safeguard

• If we hold top 3 with a page-type that matches 40 percent+ of the top 10, avoid remapping that forces a different page-type this sprint

Worked examples with SERP rationale

• “best project management software”
  • Signals: Top 10 are 8 aggregator listicles and 2 vendor pages
  • Intent: Commercial Investigation
  • Allowed page type: Best-of list with filters and up-to-date picks
  • If current: product feature page ranks 11, expect CTR lift by launching a listicle
• “project management software pricing”
  • Signals: 6 vendor pricing pages in top 10, 2 listicles, 2 category pages
  • Intent: Transactional
  • Page type: Pricing page with plan table and FAQs
• “asana vs trello”
  • Signals: 7 comparison pages, 2 community threads, 1 vendor comparison
  • Intent: Commercial Investigation
  • Page type: Side-by-side comparison with use-case recommendations
• “what is SOC 2”
  • Signals: 7 glossary/definition pages, 3 how-to overviews
  • Intent: Informational – Definition
  • Page type: “What is SOC 2” glossary with diagrams and FAQs
• “how to create gantt chart in excel”
  • Signals: 6 tutorials with steps, 2 videos, 2 templates
  • Intent: Informational – How-to
  • Page type: Step-by-step tutorial with screenshots, downloadable template
• “hubspot login”
  • Signals: Sitelinks and the brand login page first
  • Intent: Navigational
  • Page type: None needed unless it is your brand; do not try to rank
• “crm near me”
  • Signals: Local Pack on top, map results, directories
  • Intent: Local Service/Location-intent
  • Page type: Local provider page with NAP and map

Batch tagging workflow with current tools and template

You need to tag at volume using repeatable steps. Use a modifiers-first pass, then apply SERP spot-checks to high-impact subsets, and document confidence.

Steps

1. Prepare data

• Ahrefs: Export keyword list with Volume, CPC, Parent Topic, SERP features if available
• GSC: Export Queries, Clicks, Impressions, CTR, Position for the last 28 or 90 days
• GA4: Pull top landing pages and engagement metrics for mapped keywords if available

2. Build a modifiers rule column in Google Sheets

• Create a column “modifiers_intent_guess”
• Use case-insensitive regex to assign a first-pass intent
  • Commercial Investigation: (best|top|vs|versus|compare|comparison|alternative|alternatives|reviews?)
  • Transactional: (pricing|price|cost|demo|trial|buy|download|coupon|deal|discount)
  • How-to: (how to|guide|tutorial|steps?|template|checklist|example)
  • Definition: (what is|definition|meaning)
  • Local: (near me|in [A-Z][a-z]+|[A-Z]{2}|city names list)
  • Navigational: exact brand names list
• Example formula for CI guess:
  • =IF(REGEXMATCH(LOWER(A2), “(best|top|vs|versus|compare|comparison|alternative|alternatives|reviews?)”), “Commercial Investigation”, “”)
• Repeat with nested IFs to fill other intents, prioritizing Navigational and Local first

3. Add brand and geo flags

• brand_flag: match brand and product names, including misspellings
• geo_flag: city, state, country lists or “near me”

4. Compute page-type-safe priority

• Create “priority_score” using Impressions from GSC or Volume from Ahrefs
  • For example: priority_score = ln(Impressions+1) or Impressions rank
• Filter the top 20 percent by priority_score

5. SERP spot-check the top 20 percent

• Open the live SERP in a logged Chrome profile and quickly classify the first 10 organic URLs by page-type
• Log counts per type and paste into the sheet
• Apply overrides using the hierarchy above
• Mark “intent_final” and “confidence” as High when the 60 percent threshold is met, Medium when 40–59 percent or tie broken by modifiers, Low when based only on modifiers without SERP check

6. Propagate to the remaining 80 percent

• For each cluster or Parent Topic, inherit the “intent_final” from the highest-priority checked keyword
• Keep the “modifiers_intent_guess” as a backstop; if it conflicts with the cluster’s inferred intent, queue for a quick check

7. Map each intent to a page type

• Add a column “page_type_final” using the allowed page types list in the taxonomy section
• If our current landing page in GSC already matches the allowed types and holds stable top-3, keep page_type_final = current

8. Produce the tagging output and log

• Deliver columns: keyword, modifiers_intent_guess, intent_final, confidence, page_type_final, priority_score, serp_check_date, checker_initials, notes
• Store a folder of quick SERP captures or a text log of the top-10 page-type counts for the checked subset

Copyable tagging template headings

• keyword
• modifiers_intent_guess
• brand_flag
• geo_flag
• intent_final
• confidence [High, Medium, Low]
• page_type_final
• priority_score
• serp_check_date [YYYY-MM-DD]
• checker
• notes [evidence: “8/10 aggregator – CI”]

Confidence scoring rules

• High: 60 percent+ page-type majority or higher-order override hit
• Medium: 40–59 percent with modifiers tiebreaker, or strong modifiers with partial SERP alignment
• Low: Modifiers-only, no SERP check and no cluster inheritance

Conditions to consider the batch tagging complete today

• All high-priority keywords have “intent_final” with evidence notes
• The remainder have inherited “intent_final” and confidence Medium or Low
• The log is attached so another analyst can audit and land on the same labels

Early warning signs

• Too many Low confidence labels after spot-checks
• Inconsistent page-type calls inside a single cluster

Page-type decision matrix: choose, consolidate, or split

You convert intent into a page format decision. Use these rules to avoid unnecessary rewrites and prevent losses.

Decision rules by intent

• Navigational
  • Choose: if it is your brand, ensure the correct navigational page type exists and is optimized
  • Consolidate: multiple login or hub variants should consolidate to one canonical
  • Split: do not split unless user journeys differ clearly, like docs vs login
• Informational – Definition
  • Choose: glossary article with definition, examples, FAQs
  • Consolidate: duplicate concepts and “what is” posts merge into a single URL
  • Split: only if adjacent how-to deserves a separate tutorial with unique steps
• Informational – How-to
  • Choose: a tutorial or template page with clear steps and visuals
  • Consolidate: do not split sub-steps into separate URLs this sprint
  • Split: if the SERP shows separate intents like “in Excel” vs “in Google Sheets”, create separate pages only if both SERPs have distinct page-type majorities
• Commercial Investigation
  • Choose: best-of lists, alternatives, vs pages, category hub with filters
  • Consolidate: multiple “best X” listicles targeting the same head term should be merged
  • Split: create “vs” and “alternatives” pages if SERPs show each sub-intent ranking separately
• Transactional
  • Choose: pricing, product, or sign-up landing with plan comparison and FAQs
  • Consolidate: collapse multiple pricing variants into one primary pricing URL
  • Split: plan comparison can live as on-page tabs or anchors, not separate URLs this sprint
• Local Service/Location-intent
  • Choose: one location page per city or service area with NAP
  • Consolidate: remove near-duplicate location pages
  • Split: only when distinct services have unique SERPs per city

Mixed SERP guidance

• If no 60 percent majority:
  • Between CI and Transactional: build a CI page first and add a clear CTA; do not replace a stable pricing URL this sprint
  • Between Definition and How-to: publish a How-to and add a “What is” section at the top with a definition box

Safe-to-change thresholds this sprint

• Safe: current CTR is below site median for that position band and position is outside top 3
• Caution: current page holds top 3 with above-median CTR
• Action: for Caution, prefer on-page format changes on the same URL instead of new URL

Sprint-safe fixes: prioritize CTR lifts without ranking loss

Start with format and relevance cues that align to SERP without migrations.

Low-risk, high-leverage actions

• Titles and H1s: match dominant modifiers exactly
  • Example: change “Project tools for teams” to “Best project management software for teams [2026]”
• Add on-page comparison blocks for CI
  • Top features table, pros and cons, pricing snapshot, use-case recommendations
• Insert a definition box for Definition-intent SERPs
• Add step-by-step anchors and jump links for How-to
• Expand FAQs to mirror People Also Ask; add FAQ schema where appropriate
• Add “Plans and pricing” anchors on product pages; include total cost of ownership cues when “pricing” SERP is vendor-heavy
• Visuals: unique images, thumbnails sized to appear on SERPs where image packs show
• Internal links: ensure cluster hubs link to child pages using the same modifiers users search
• Structured data: Product, FAQ, HowTo where allowed and relevant to the SERP
• Local pages: add NAP, map embed, service areas, and working hours

Conditions to assess success this sprint

• CTR up for remapped queries with stable or improved average position
• Engagement improved for target landing pages in GA4 without drop in organic sessions

Early warnings

• CTR down with no position change after a title rewrite
• Relevance drift: rankings fall immediately after changing H1 to mismatched modifiers

QA, documentation, confidence scoring, and spot-check protocol

A framework is only defensible if someone else can replicate decisions and audit them.

QA checklist

• Sampling: At least the top 20 percent of queries by priority_score have SERP-checked evidence
• Thresholds: Each override uses 60 percent or numeric counts, not words like “mostly”
• Intent-to-page-type: All final page types are within the allowed set for the intent
• Risk: Changes do not replace a stable top-3 transactional page without a strong SERP mismatch
• Logs: For each checked keyword, paste counts like “Aggregator 7, Vendor pricing 2, Tutorial 1”

Confidence scoring recap

• High: SERP majority or higher-order override
• Medium: Partial majority plus modifiers
• Low: Modifiers-only or ambiguous SERP

Spot-check protocol

• A second analyst re-checks 10 percent of High and 30 percent of Medium/Low confidence keywords
• If disagreement rate exceeds 15 percent in any bucket, expand checks by another 10 percent and adjust rules or thresholds

Documentation standards

• Store the rule set, override hierarchy, thresholds, and allowed page types in a single source doc
• Keep a dated changelog when a rule or threshold evolves
• Archive before-and-after titles and layouts for pages affected this sprint

Condition to declare QA pass

• Disagreement rate below 10 percent on the re-check sample and all Medium/Low conflicts resolved or queued

Early warning signs

• Spot-checkers change labels frequently due to unclear notes or missing counts
• Revisions creep into the taxonomy without updating the source doc

Presenting the framework: one-slide structure, examples, Q&A talk track

Stakeholders need one concise slide they can defend. Keep terms business-relevant and tie choices to SERP evidence.

One-slide executive summary template

• Title: SERP-first intent framework and page-type mapping
• Left column: Taxonomy with one-line definitions
  • Navigational: user seeks a specific brand/page
  • Informational – Definition: learn what X is
  • Informational – How-to: learn how to do a task
  • Commercial Investigation: compare options
  • Transactional: buy, price, sign up
  • Local: find providers in a place
• Middle: Override order with thresholds
  • Brand sitelinks or Local Pack override all
  • 60 percent+ top-10 page-type majority decides
  • Modifiers break ties; keep stable top-3 pages
• Right: Page-type matrix highlights
  • CI => best-of list, vs, alternatives
  • Transactional => pricing, product, trial
  • How-to => tutorial, template
  • Definition => glossary
  • Local => location page
• Bottom: 3 mini-examples with evidence
  • “best project management software” => 8/10 listicles => CI => best-of list
  • “project management software pricing” => 6/10 pricing pages => Transactional => pricing page
  • “how to create gantt chart in excel” => 6/10 tutorials => How-to => tutorial with template
• Footer: Today’s output
  • Tagging template live, 20 percent SERP-audited, confidence scoring in place
  • Next: ship sprint-safe on-page updates for top 5 opportunities

Talk track for Q&A

• Why this taxonomy: It covers 95 percent+ of searchable behaviors we see and maps 1-to-few page types, reducing ambiguity
• What overrides what: We follow what Google shows users. If 60 percent of top results are listicles, the intent is to compare, not to buy
• Risk to rankings: We do not migrate URLs this sprint. We align titles, add comparison blocks, and add anchors to meet the dominant SERP format
• How we scale: Modifiers label 80 percent; we SERP-check the top 20 percent and propagate by cluster with confidence scores
• How we know it worked: CTR and engagement rise with stable positions in GSC and GA4 for remapped queries

Conclusion You now have a SERP-first intent framework with a fixed taxonomy, override rules, a page-type matrix, a batch tagging template, and 5–7 examples you can defend in the deck. Apply sprint-safe page-format changes where the SERP clearly signals a different format and document every call with counts.

Follow this track to build a transparent churn propensity model with actionable segments, expected lift, time-based validation, and a reproducible notebook — ready to present and deploy within 3–4 weeks.

---

Prerequisites

Confirm these are in place before Week 1:

• Query access to GA4, CRM, and ESP exports (BigQuery or equivalent)
• A business-agreed churn definition and observation window — without this, Week 1 cannot start
• Python 3.10+ environment and SQL query rights
• Permission to set a persistent control group in CRM or ESP
• A light integration slot confirmed in the engineering calendar for Weeks 3–4

On the 3–4 week timeline: This is achievable if GA4/CRM/ESP identity stitching already works and the data warehouse is stable. If identity coverage is below 60% or ETL pipelines are unreliable, plan an additional 1–2 weeks for data remediation before modeling starts. Do not compress the timeline by skipping the coverage check in Step 2.

Expected deliverables:

• A 15-slide deck and reproducible notebook demonstrating a defendable churn model, feature importance, time-split validation, and expected lift
• Scoring integrated into CRM or ESP with a persistent 10% control group and measurable lift vs. control within 2–4 weeks post-deploy
• A privacy-approved signal brief listing 3–5 GDPR/CCPA-compliant predictive signals with a measurement plan

---

Step 1: Define Churn, Time Windows, and Business Objectives

Label quality determines model credibility. Lock these three up front — changing definitions mid-pilot invalidates backtest comparability and will be challenged in the sign-off meeting.

Churn Label Definition

Subscription businesses: Churn = not renewed by day N after plan end. Common default: N = 30.

Transactional businesses: Churn = no purchase within N days of the last order, where:

N = median_interpurchase_interval × 1.5 to 2.0

Example: if the median interpurchase interval is 21 days, set N = 45. This avoids the common mistake of treating customers as churned before their natural repurchase window has elapsed — which leads to discounting customers who would have returned anyway.

Observation Windows

• Lookback window for features: 30, 60, or 90 days depending on purchase cadence
• Outcome window: the N-day future window used to assign the churn label

Objective Tie-In

• Primary KPI: incremental retained orders or billings within the outcome window
• Secondary KPIs: cost per retained user, margin-safe offer redemption rate, opt-out rate

Decision Guardrails

• Set N so the business has a 2–4 week action window after scoring — if N is too long, CRM acts too late
• Freeze the churn definition and N in a shared document before any SQL runs — do not adjust during the pilot

Deliverable Snippet for the Deck

“We call a user at risk if they have not purchased again by day 45 after their last order. Our model predicts this risk at day 21, giving CRM 24 days to act.”

---

Step 2: Audit Data, Verify Identity Stitching, and Build the Panel

You do not need a CDP. A thin schema with a stable identity key is enough to ship a pilot.

Minimum Viable Schema

Identity

• customer_id: stable internal ID — the primary join key across all systems
• email_sha256: lowercase-trimmed email hashed client-side or in batch

CRM orders: order_id, customer_id, order_ts_utc, order_value, payment_status

GA4 behavioral: customer_id or device_id, event_ts_utc, event_name, page_category, session_id, source_medium

ESP messaging: customer_id or email_sha256, send_ts_utc, message_type, campaign_id, opened, clicked, bounced, unsubscribed

Identity Stitching Rules

• Prefer customer_id across all systems
• If GA4 lacks customer_id, map the last known device_id to customer_id via login events in the prior 60 days
• Never ingest raw PII into modeling files — use email_sha256 strictly for ESP joins

Coverage and Stability Checks — Run These Before Feature Engineering

-- Coverage: what % of CRM orders have a GA4 session in the prior 30 days?
-- Target: 60%+ for a clean pilot. If below 60%, fix stitching before proceeding.
SELECT
  COUNT(DISTINCT o.customer_id) AS orders_with_ga4_session,
  COUNT(DISTINCT o.customer_id) * 1.0 / total.cnt AS coverage_rate
FROM crm_orders o
JOIN ga4_events g
  ON o.customer_id = g.customer_id
  AND g.event_ts_utc BETWEEN TIMESTAMP_SUB(o.order_ts_utc, INTERVAL 30 DAY)
                          AND o.order_ts_utc
CROSS JOIN (SELECT COUNT(DISTINCT customer_id) AS cnt FROM crm_orders) total;

-- Stability: daily order and session counts over the past 90 days
-- Flag anomalies that indicate schema changes or ETL issues
SELECT DATE(order_ts_utc) AS day, COUNT(*) AS orders
FROM crm_orders
WHERE order_ts_utc >= TIMESTAMP_SUB(CURRENT_TIMESTAMP(), INTERVAL 90 DAY)
GROUP BY 1 ORDER BY 1;

Daily Customer Panel — Core SQL

-- BigQuery. Adjust window functions for your warehouse dialect.
WITH last_order AS (
  SELECT
    customer_id,
    MAX(order_ts_utc) AS last_order_ts,
    COUNTIF(order_ts_utc >= TIMESTAMP_SUB(CURRENT_TIMESTAMP(), INTERVAL 90 DAY)) AS orders_90d,
    SUM(CASE WHEN order_ts_utc >= TIMESTAMP_SUB(CURRENT_TIMESTAMP(), INTERVAL 90 DAY)
             THEN order_value ELSE 0 END) AS revenue_90d
  FROM crm_orders
  WHERE payment_status = 'paid'
  GROUP BY customer_id
),
beh_30d AS (
  SELECT
    customer_id,
    COUNTIF(event_name = 'view_item')      AS views_30d,
    COUNTIF(event_name = 'add_to_cart')    AS atc_30d,
    COUNTIF(event_name = 'begin_checkout') AS checkout_30d,
    COUNT(DISTINCT session_id)             AS sessions_30d
  FROM ga4_events
  WHERE event_ts_utc >= TIMESTAMP_SUB(CURRENT_TIMESTAMP(), INTERVAL 30 DAY)
    AND customer_id IS NOT NULL
  GROUP BY customer_id
),
esp_30d AS (
  SELECT
    customer_id,
    COUNTIF(send_ts_utc >= TIMESTAMP_SUB(CURRENT_TIMESTAMP(), INTERVAL 30 DAY)) AS sends_30d,
    COUNTIF(opened AND send_ts_utc >= TIMESTAMP_SUB(CURRENT_TIMESTAMP(), INTERVAL 30 DAY)) AS opens_30d,
    COUNTIF(clicked AND send_ts_utc >= TIMESTAMP_SUB(CURRENT_TIMESTAMP(), INTERVAL 30 DAY)) AS clicks_30d,
    MAX(CAST(unsubscribed AS INT64)) AS ever_unsub
  FROM esp_events
  GROUP BY customer_id
)
SELECT
  COALESCE(l.customer_id, b.customer_id, e.customer_id) AS customer_id,
  l.last_order_ts,
  l.orders_90d,           l.revenue_90d,
  b.views_30d,            b.atc_30d,
  b.checkout_30d,         b.sessions_30d,
  e.sends_30d,            e.opens_30d,
  e.clicks_30d,           e.ever_unsub
FROM last_order l
FULL OUTER JOIN beh_30d b USING (customer_id)
FULL OUTER JOIN esp_30d e USING (customer_id);

Privacy Note

Keep only non-sensitive behavioral attributes — aggregate counts and recency flags. No demographics or special-category data.

Privacy brief (FL2 requirement): A one-page list of 3–5 signals, each with its source table, retention period, and lawful basis. If legal cannot find a data map entry for a signal, replace it with an aggregated non-PII equivalent before proceeding.

---

Step 3: Feature Engineering — RFM and Behavioral Signals

Prioritize high-signal, low-cardinality features that are easy to explain to executives and stable across schema changes.

Core Feature Set

RFM

• Recency: days since last order, days since last site session, days since last email open
• Frequency: orders (90d), sessions (30d), email opens (30d)
• Monetary: revenue (90d), average order value (90d)

Funnel intensity

• add_to_cart / views ratio (30d)
• checkout_starts / add_to_cart ratio (30d)

Trend flags

• Sessions (30d) minus sessions (prior 30d) — detects engagement drop
• Open rate (30d) vs. open rate (90d) — detects email fatigue

Friction signals

• Count of failed checkouts or payment errors
• Unsubscribe flag

Feature Snapshot SQL — Point-in-Time Safe

The most common modeling error in churn is look-ahead bias: features or labels that accidentally incorporate data from after the cutoff date. Every feature query must be strictly bounded to <= cutoff_date. Run this check before training:

DECLARE cutoff_date DATE DEFAULT '2026-05-31';

-- Verify no future data leaks into the feature window
SELECT COUNT(*) AS future_rows_should_be_zero
FROM ga4_events
WHERE event_ts_utc > TIMESTAMP(cutoff_date)
  AND customer_id IN (SELECT customer_id FROM feature_snapshot);

Feature computation:

DECLARE cutoff_date DATE DEFAULT '2026-05-31';

SELECT
  customer_id,
  DATE(cutoff_date) AS as_of_date,
  TIMESTAMP_DIFF(TIMESTAMP(cutoff_date), last_order_ts, DAY) AS recency_last_order_d,
  COALESCE(orders_90d, 0)     AS orders_90d,
  COALESCE(revenue_90d, 0.0)  AS revenue_90d,
  COALESCE(sessions_30d, 0)   AS sessions_30d,
  SAFE_DIVIDE(COALESCE(atc_30d, 0),      NULLIF(views_30d, 0))     AS atc_view_ratio_30d,
  SAFE_DIVIDE(COALESCE(checkout_30d, 0), NULLIF(atc_30d, 0))       AS checkout_atc_ratio_30d,
  SAFE_DIVIDE(COALESCE(opens_30d, 0),    NULLIF(sends_30d, 0))     AS open_rate_30d,
  COALESCE(ever_unsub, 0)     AS ever_unsub
FROM customer_panel_daily
WHERE DATE(last_order_ts) <= cutoff_date;

Label creation — strictly future-only:

WITH future_orders AS (
  SELECT customer_id, MIN(order_ts_utc) AS next_order_ts
  FROM crm_orders
  WHERE order_ts_utc > TIMESTAMP(@cutoff_date)
  GROUP BY customer_id
)
SELECT
  f.*,
  CASE
    WHEN fo.next_order_ts IS NULL THEN 1
    WHEN TIMESTAMP_DIFF(fo.next_order_ts, TIMESTAMP(@cutoff_date), DAY) > 45 THEN 1
    ELSE 0
  END AS label_churn_45d
FROM feature_snapshot f
LEFT JOIN future_orders fo USING (customer_id);

Robustness Tips

• Cap extreme counts at the 99th percentile before training — a single outlier user can destabilize logistic regression coefficients
• Log-transform or bin skewed count features (orders, revenue)
• Stick to 10–20 robust features — adding niche signals rarely improves calibration and makes the model harder to defend

---

Step 4: Baseline Model and Probability Calibration

Why Logistic Regression First

For a 3–4 week pilot with an executive audience, logistic regression is the right starting point: coefficients are directionally interpretable, the model is easy to deploy as SQL or a lightweight batch job, and calibration behavior is well-understood. A more complex model that cannot be explained in a 15-slide deck will face stakeholder resistance that delays deployment longer than the marginal accuracy gain is worth.

If logistic regression reaches AUC ≥ 0.70 with good calibration, ship it. Upgrade to gradient boosting in the next iteration with the live control group data as additional validation evidence.

Training and Calibration

# pip install pandas scikit-learn numpy matplotlib joblib statsmodels
import pandas as pd
import numpy as np
from sklearn.preprocessing import StandardScaler
from sklearn.linear_model import LogisticRegression
from sklearn.calibration import CalibratedClassifierCV, calibration_curve
from sklearn.metrics import roc_auc_score, brier_score_loss
from sklearn.inspection import permutation_importance
from joblib import dump
import matplotlib.pyplot as plt

df = pd.read_csv('train_snapshot.csv').sort_values('as_of_date')

FEATURE_COLS = [
    'recency_last_order_d', 'orders_90d', 'revenue_90d', 'sessions_30d',
    'atc_view_ratio_30d', 'checkout_atc_ratio_30d',
    'sends_30d', 'open_rate_30d', 'ever_unsub'
]

X = df[FEATURE_COLS].fillna(0)
y = df['label_churn_45d'].astype(int)

# Time-based split — never random split for temporal prediction tasks
split_idx = int(0.8 * len(df))
X_train, X_val = X.iloc[:split_idx], X.iloc[split_idx:]
y_train, y_val = y.iloc[:split_idx], y.iloc[split_idx:]

scaler = StandardScaler()
X_train_sc = scaler.fit_transform(X_train)
X_val_sc   = scaler.transform(X_val)   # fit only on train — no leakage

lr = LogisticRegression(
    penalty='l2', C=1.0, solver='liblinear',
    max_iter=1000, class_weight='balanced'
)
lr.fit(X_train_sc, y_train)

# Calibrate on the validation fold — not on the training set
cal = CalibratedClassifierCV(lr, method='isotonic', cv='prefit')
cal.fit(X_val_sc, y_val)

pred_val = cal.predict_proba(X_val_sc)[:, 1]
print(f'AUC:   {roc_auc_score(y_val, pred_val):.3f}')
print(f'Brier: {brier_score_loss(y_val, pred_val):.3f}')

# Calibration plot — include in deck appendix
prob_true, prob_pred = calibration_curve(y_val, pred_val, n_bins=10)
plt.figure(figsize=(4, 4))
plt.plot(prob_pred, prob_true, marker='o', label='Model')
plt.plot([0, 1], [0, 1], '--', color='gray', label='Perfect calibration')
plt.title('Calibration plot — validation fold')
plt.xlabel('Predicted probability'); plt.ylabel('Observed frequency')
plt.tight_layout(); plt.savefig('calibration.png', dpi=150)

# Feature importance — permutation on validation, not train
perm = permutation_importance(cal, X_val_sc, y_val, n_repeats=10, random_state=42)
pi   = pd.Series(perm.importances_mean, index=FEATURE_COLS).sort_values(ascending=False)
print('Permutation importance:\n', pi)

dump({'scaler': scaler, 'model': cal, 'features': FEATURE_COLS}, 'churn_lr_calibrated.joblib')

How to Frame This for Executives

• Replace “AUC 0.74” with: “The model correctly ranks higher-risk customers above lower-risk ones 74% of the time in held-out backtests.”
• Replace “Brier score” with: “When the model predicts 40% churn risk, roughly 40 out of 100 customers in that bucket actually churn — the scores are reliable, not just relative.”
• Calibration is what makes the probability score usable for business decisions (segmentation cutoffs, offer ROI math). If the calibration curve is far from the diagonal, fix it before presenting.

---

Step 5: Validation — Time-Based Backtest, AUC, and Lift

Backtest Setup

Use at least 6 months of history. Roll multiple cutoff dates monthly:

Period	Role
Months 1–4	Training data
Month 5	Validation (tune cutoffs here)
Month 6	Held-out test (report here)

All users observable at the cutoff date must be included — do not drop users who were suppressed by past campaigns without annotating and accounting for this. If major promo events occurred during the backtest window, annotate them in the change log and evaluate model stability across promo vs. non-promo periods separately.

Metrics to Report

• Discrimination: AUC and top-decile capture rate of churners
• Calibration: Brier score and calibration plot
• Expected lift proxy: churn rate in the top risk decile vs. the population average

Always report metrics on the held-out test period, not the validation fold used for calibration tuning.

Sample Size for the Live A/B Pilot

The pilot runs as a two-proportion test within each risk segment. Use proportion_effectsize from statsmodels to compute Cohen’s h correctly — do not pass a raw proportion difference as the effect size directly:

from statsmodels.stats.proportion import proportion_effectsize
from statsmodels.stats.power import NormalIndPower

# Example: baseline repurchase rate 8%, expected with treatment 10%
h = proportion_effectsize(0.10, 0.08)   # Cohen's h — correct effect size for proportions
n = NormalIndPower().solve_power(
    effect_size=h, alpha=0.05, power=0.8, alternative='two-sided'
)
print(f'Required n per arm: {round(n)}')  # ~3,900

Note on the code: The correct approach is to compute Cohen’s h via proportion_effectsize first, then pass that value into solve_power. Passing raw proportions directly to solve_power without converting to Cohen’s h will produce incorrect results, since NormalIndPower expects a standardized effect size, not a probability difference.

Handling Seasonal Drift in Risk Cutoffs

Risk cutoffs frozen on the validation month can become unreliable if the pilot month has a materially different churn rate — common during promotions, holidays, or demand spikes. Before freezing cutoffs for the pilot:

1. Compare the validation month’s population-level churn rate to the pilot month’s early-week observed rate
2. If the difference exceeds 3–5 percentage points, recompute cutoffs on a sliding 4-week window rather than a single frozen month
3. Document the cutoff values and the date they were computed in the score output file — this is required for post-pilot audit

For the first pilot, prefer percentile-based cutoffs (top 20% = high risk) over fixed probability thresholds. Percentile cutoffs are robust to distribution shift because they track the relative ranking of scores rather than their absolute value.

Lift Estimation Template

Important: The numbers below are illustrative placeholders. If your organization has not run a comparable save offer before, the absolute lift and redemption rate are assumptions, not measured baselines. Present these as scenarios with ranges, not point estimates.

Validation month population churn rate (45d):   20%
High-risk segment churn rate (top 20%):          40%
Assumed absolute lift from save offer:           3 pp  ← needs precedent or pilot confirmation
Pilot population:                               50,000 users
High-risk segment (top 20%):                   10,000 users

Expected incremental saves: 10,000 × 0.03 = 300
If average retained order margin = $12:          $3,600 incremental margin
If offer cost = $6 × 15% redemption rate:        $9,000 offer cost
Net impact (this scenario): −$5,400

→ Present low / mid / high redemption scenarios.
   Net-positive outcome requires either higher margin per order,
   lower offer cost, or confirmed lift > 3pp from historical data.

The worksheet should always include a scenario where the offer cost exceeds the incremental margin — the board needs to see the downside case.

---

Step 6: Risk Segmentation and Action Playbook

Segmentation Template

Segment	Cutoff	Recommended basis
High risk	Top 20% by score	Percentile on validation month
Medium risk	20th–50th percentile	Percentile on validation month
Low risk	Below 50th percentile	—

Freeze cutoffs on the validation month and document them. If pilot month distribution shifts more than 3–5pp, see the drift handling protocol in Step 5.

Action Playbook

High risk

• Offer: limited-time win-back discount or free shipping
• Channel: email + SMS if opted in
• Cadence: 3 touches over 10 days
• Suppress: unsubscribed users, users with open support tickets, users with unresolved payment errors

Medium risk

• Offer: relevant content, category reminders, low-cost perk — no discount
• Channel: email only
• Cadence: 2 touches over 14 days

Low risk

• No discount. Next-best-offer recommendations or new arrivals only

Suppression rule for non-churn friction: Users with open support tickets or payment gateway errors are not churning — they are blocked. Sending a win-back offer to this segment is counterproductive and will show up as wasted offer cost in the margin analysis. Coordinate with CS and Payments to maintain a suppression list before the pilot launches.

Margin Guardrails

• Do not extend discounts to the low-risk segment
• Set a maximum offer budget per user per week
• Cap weekly touches and honor opt-outs immediately
• Include a margin floor slide in the deck: show at what offer cost and redemption rate the campaign becomes margin-negative

---

Step 7: Scoring Pipeline and CRM/ESP Deployment

Weekly Scoring Script

import pandas as pd
from joblib import load

art = load('churn_lr_calibrated.joblib')
scaler, model, feats = art['scaler'], art['model'], art['features']

SCORE_DATE = '2026-06-03'
df = pd.read_csv(f'weekly_features_{SCORE_DATE}.csv').fillna(0)

X = scaler.transform(df[feats])
df['churn_prob'] = model.predict_proba(X)[:, 1]

# Percentile-based cutoffs — recompute monthly, document each recompute
hi_pct  = df['churn_prob'].quantile(0.80)
med_pct = df['churn_prob'].quantile(0.50)

df['risk_segment'] = pd.cut(
    df['churn_prob'],
    bins=[-1, med_pct, hi_pct, 1.0],
    labels=['low', 'medium', 'high']
)

out = df[['customer_id']].copy()
out['score_date_utc']    = SCORE_DATE
out['churn_prob']        = df['churn_prob'].round(4)
out['risk_segment']      = df['risk_segment'].astype(str)
out['model_version']     = 'lr_v1_2026-05'
out['source_window_days'] = 45
out['hi_cutoff']         = round(hi_pct, 4)   # log for audit
out['med_cutoff']        = round(med_pct, 4)  # log for audit

out.to_csv(f'churn_scores_{SCORE_DATE}.csv', index=False)

Archive every batch output. Do not overwrite — include score_date_utc and model_version in every file.

Control Group and Measurement

• At first scoring run, randomly assign 10% of each risk segment to a persistent control group — tag them in CRM/ESP as control_flag = True
• Persist control membership for the full 4-week measurement window — do not reassign
• Exclude control_flag = True users from all campaign journeys
• Verify audience counts in CRM/ESP match the score file within 5% — a larger discrepancy indicates a join or upload error

Journey conflict check: When pushing risk_segment attributes to the ESP, confirm this segment is explicitly excluded from existing mass campaigns. Users receiving both a win-back offer and a regular promotional email creates measurement noise and degrades the user experience.

Measurement Dashboard

Track per arm, per segment, weekly:

Metric	Description
Repurchase rate	Primary lift signal
Offer redemption rate	Offer economics
Unsubscribe / complaint rate	Guardrail
Revenue per user	Margin validation

Measurement window: 30–45 days after first touch, aligned to the churn outcome window.

---

Step 8: Presentation Deck — 15 Slides

Deck Structure

Slide	Content
1	Executive summary: one sentence on expected outcome and decision ask
2	What we predict: “Who will not purchase in 45 days” and why it matters in revenue terms
3	Data used: GA4, CRM, ESP — non-sensitive signals, hashed joins, privacy brief reference
4	Churn definition and timeline: one visual showing observation window, cutoff, outcome window
5	Approach: logistic regression, weekly scoring, control group — why interpretability over complexity
6	Backtest credibility: time-based split, AUC in plain language, calibration plot
7	Segmentation: sizes, percentile cutoffs, which month they were frozen on
8	Action plan: offers and channels per segment, suppression rules, margin guardrails
9	Expected impact: lift scenarios (low / mid / high) with assumptions explicit
10	Pilot design: control share, measurement window, dashboards
11	Privacy and compliance: lawful basis, retention, opt-out guardrails
12	Risks and mitigations: data drift, over-offering, privacy complaints, identity coverage
13	Integration plan: score file format, CRM/ESP wiring, no platform change required
14	Timeline: 3–4 week Gantt with owners
15	Decision ask: go/no-go, offer budget cap, named CRM owner

Executive Language Translations

Technical	Plain language for slides
AUC 0.74	“The model correctly ranks higher-risk customers above lower-risk ones 74% of the time in held-out backtests.”
Brier score / calibration	“Predicted 40% risk means roughly 40 of 100 customers in that group actually churned — the scores reflect reality.”
Logistic regression	“A transparent model whose logic can be explained in one sentence per feature.”
Control group	“A 10% holdout that lets us measure whether our actions caused the improvement, not just correlated with it.”

Model Card — Required in Appendix

Include: objective, label definition, time windows, data sources and exclusions, training and validation dates, performance metrics, feature importance, calibration method, fairness/privacy considerations, intended use and misuse cases, retraining frequency, versioning, and contacts.

---

Common Failure Modes and How to Avoid Them

Failure	Prevention
Definition shifts between train and pilot	Freeze churn N in writing before any SQL runs
Look-ahead bias in features	Run the future-data leak check in Step 3 before every training run
Backtesting on campaign-suppressed users	Annotate promo periods; exclude or stratify accordingly
Over-fitting with too many features	Cap at 10–20 robust RFM and behavioral signals
No holdout	Tag the 10% control in CRM/ESP before the first score is pushed
Score file without versioning	Always include model_version and score_date_utc — archive every batch
Ignoring calibration	Plot calibration before every deployment; fix before launch if the curve drifts far from the diagonal
ROI numbers presented as certain	Label lift and redemption assumptions explicitly; always show the downside scenario
Journey conflicts	Confirm suppression from mass campaigns before the pilot goes live

---

Privacy-Approved Signal Brief

Signal	Source	Retention	Lawful basis
Days since last session	GA4	90 days raw → aggregate	Legitimate interest / consent
Sessions count (30d)	GA4	90 days raw → aggregate	Legitimate interest / consent
Product views + add-to-carts (30d)	GA4	90 days raw → aggregate	Legitimate interest / consent
Email sends, opens, clicks (30d)	ESP	90 days raw → aggregate	Legitimate interest
Orders count + revenue (90d)	CRM	Per data retention policy	Contract performance
Unsubscribe flag	ESP	Indefinite (compliance)	Legal obligation

Raw event-level data purges after 90 days. Aggregates used for modeling retain no PII. Email joins use email_sha256 only, hashed client-side before transmission.

---

3–4 Week Execution Timeline

Days	Actions
1–3	Freeze churn definition in writing; run coverage and stability checks; confirm identity stitching ≥60%
4–7	Build daily customer panel SQL; generate feature snapshot at first cutoff date; run look-ahead leak check
8–12	Train and calibrate model; run time-based backtest; generate AUC, Brier, calibration plot
13–16	Freeze risk cutoffs on validation month; build action playbook; compute lift scenarios with explicit assumptions
17–20	Build scoring script; test score file format with CRM/ESP; tag 10% control group; set up measurement dashboard
21–24	Draft deck; Finance review of margin math and downside scenario; privacy sign-off on signal brief
25–28	Executive review; incorporate feedback; launch pilot journeys; confirm control excluded from campaigns

---

By following this sequence you will have a churn propensity model that is technically sound, calibrated, time-validated, and explainable to a VP audience — with a live control group that produces credible lift evidence within 4 weeks of deployment. The most common failure is not the model: it is moving too fast on a fragile data foundation or presenting ROI assumptions as certainties. Validate the data first, freeze the definitions, and keep the economics honest.

Use this playbook to produce an executive-ready CRO roadmap in one week. You leave with a prioritized experiment list, lift forecasts, effort estimates, ROI math to offset higher CAC, and a power-aware measurement plan that fits GA4 and Shopify with limited engineering.

---

Prerequisites

Confirm these are in place on Day 1:

• GA4 access with ecommerce events and historical baselines segmented by device, traffic source, and country
• Access to your testing tool and the ability to deploy theme changes on Shopify
• Baseline conversion rate, AOV, revenue per session, and traffic by key segments
• CAC and ROAS by channel for the past 8–12 weeks
• Confirmed brand, legal, privacy constraints and consent setup
• Rough weekly engineering and design bandwidth in hours

Expected output: A board-ready roadmap deck feasible within your GA4 and Shopify stack, showing prioritized experiments, projected lift, effort, ROI, and a power-aware measurement plan. Initial tests reach statistical significance at current traffic this quarter and deliver uplifts modeled to offset the ~25% CAC increase — without harming speed, SEO, or privacy.

---

Step 1: Diagnose the Testing Plateau — Power, MDE, and Traffic Math

Without correct power and MDE calculations, you run inconclusive or misleading tests. The failure mode is a streak of nulls or false positives caused by underpowered designs and flexible stopping. Fix the math first, then plan experiments your traffic can actually resolve.

Lock the Primary Metric by Funnel Stage

• Pricing or AOV levers: Revenue per session or contribution margin per session
• Completion friction levers: Purchase conversion rate
• Guardrails (non-negotiable): LCP and INP for page speed; bounce rate and add-to-cart rate to catch upstream damage

Compute Minimum Detectable Effect and Required Sample Size

For a binary metric (e.g., purchase conversion rate):

n_per_variant = 2 × p × (1 − p) × (Z_alpha + Z_power)² / MDE²

Where p = baseline rate, Z_alpha = NORM.S.INV(1 − alpha/2), Z_power = NORM.S.INV(power)

For a continuous metric (e.g., revenue per session):

n_per_variant = 2 × sd² × (Z_alpha + Z_power)² / d²

Where sd = empirical standard deviation of the metric from GA4, d = absolute MDE in currency

Conservative Defaults

• Alpha: 0.05 two-sided
• Power: 0.80
• Maximum planned test duration: 4–6 weeks to avoid seasonality drift
• Stopping rule: pre-committed before launch, never adjusted after the test begins

Power and MDE Quick-Calculator

Paste into a spreadsheet. Fill the Inputs section with your numbers. The formulas calculate automatically.

Inputs:

Parameter	Example value
Baseline conversion rate (p)	0.025
Alpha	0.05
Power	0.80
Target MDE (percentage points)	0.005
Monthly eligible sessions	120,000
Traffic split per variant	0.50

Excel formulas:

Z_alpha         = NORM.S.INV(1 − Alpha/2)
Z_power         = NORM.S.INV(Power)
n_per_variant   = 2 × p × (1−p) × (Z_alpha + Z_power)² / MDE²
Weeks_needed    = (n_per_variant / (MonthlyEligibleSessions × Split)) × 4.345
Achievable_MDE  = SQRT(2 × p × (1−p) × (Z_alpha + Z_power)² / n_per_variant)

Worked example — verify this before presenting to the board:

Z_alpha = 1.96
Z_power = 0.84
n_per_variant = 2 × 0.025 × 0.975 × (2.80)² / (0.005)² ≈ 11,908 sessions per variant

Critical check on Weeks_needed: With 120,000 eligible sessions per month split 50/50, each variant receives 60,000 sessions per month — approximately 13,800 per week per variant. Reaching 11,908 sessions per variant therefore takes roughly 0.86 weeks, which is correct at this traffic volume.

However, this result is highly sensitive to the exposure pool. MonthlyEligibleSessions must reflect only the sessions that actually enter the experiment (e.g., PDP visitors for a PDP test), not total site sessions. If your PDP traffic is a fraction of sitewide traffic, Weeks_needed scales up proportionally. Always recalculate with your actual eligible session count per test, not the sitewide number.

Board interpretation (plain language): Detecting a 0.5 percentage-point lift on this page is feasible within approximately one week — provided 120,000 monthly sessions are genuinely eligible for this specific experiment.

When Not to Run an A/B Test

• If the achievable MDE at your traffic is larger than a plausible real-world lift from the change, ship it as a reversible hardening or run a non-inferiority test with a wider margin
• If sample size requires more than 6 weeks, redesign to increase exposure or use a quasi-experiment with a time-series holdout

Pitfalls to Avoid

• Peeking without alpha spending: Checking results before the pre-committed stop date inflates false positives. Either hold to a fixed horizon or use a testing platform with built-in sequential testing controls. Do not improvise a sequential approach mid-test.
• Over-segmentation: Pre-register a maximum of 1–2 planned segment cuts. Any additional cuts are exploratory and require a confirmatory follow-up before driving rollout decisions.
• Underestimating revenue metric variance: Use empirical standard deviation from GA4 — do not estimate or borrow from benchmarks.

---

Step 2: High-Leverage CRO Levers — Offer, Flow, and Pricing

UI polish rarely breaks a testing plateau. The failure mode is chasing micro-wins while CAC rises. Shift up the stack to offer, flow, and pricing mechanics that move both conversion rate and order economics simultaneously.

Offer and Merchandising Levers

• Risk reversal: Add a 30-day free returns policy link within 50px of the add-to-cart button
• Shipping promise: Show local delivery estimates and order cutoff times on PDP and in cart
• Social proof density: Display review count adjacent to price plus a 3-bullet pros summary
• Bundles and quantity breaks: Nudge multi-unit purchases with transparent per-unit pricing at each quantity tier

Flow Levers

• Reduce decision steps: Consolidate variant selection and add-to-cart into a single interaction on PDP
• Express checkout coverage: Enable Shop Pay, Apple Pay, Google Pay, and PayPal — surface the highest-adoption wallet first by device type
• Cart-to-checkout clarity: Sticky checkout CTA above the fold in cart, with a shipping threshold meter and tax estimate visible

Pricing Levers

• Threshold optimization: Test the free shipping threshold near AOV clusters; target a 10–15% AOV lift without depressing conversion rate
• Anchored pricing: Show compare-at price only where the discount is genuine and inventory-backed
• Installments messaging: If Shop Pay Installments is available, itemize the total-today and monthly amounts side by side

Boundary Conditions

• Price testing must respect legal and ad policy constraints — do not show different prices to users in the same legal jurisdiction if policy forbids it
• Shipping promises must match operational reality — missed SLAs erode long-run conversion and trust

---

Step 3: Advanced Experiment Designs for Modest Traffic

When traffic is modest, classic multi-variant and deep segment splits underpower quickly. The failure mode is running broad UI tweaks that never resolve. Use designs that concentrate statistical power while preserving inference quality.

Power-Aware Designs

Fixed-horizon A/B with higher MDE Increase the change magnitude to meet the MDE your traffic can support, then stop exactly at the precomputed sample size. Do not extend.

Non-inferiority tests For performance-sensitive changes (speed optimizations, backend migrations), prove the new variant is not worse than control within a preset margin, then roll out for operational benefits. This requires less power than a superiority test.

Switchback tests For sitewide or time-sensitive changes where user-level randomization is impractical, alternate variants by day-of-week or hour to neutralize time trends. Pre-specify the alternation schedule before launch.

Quasi-experiments with synthetic control For global changes that cannot be split by user, use a comparable country or channel as the control group and run an interrupted time-series analysis. Pre-specify the time window and model before observing outcomes.

Sequential Decisions Without P-Hacking

If your testing tool explicitly supports sequential controls for type I error, enable its built-in sequential settings and follow the platform’s stopping thresholds exactly.

If it does not, commit to a fixed-horizon rule in the pre-analysis plan. Add a contingency decision rule for what happens if power is missed by more than 15% at the planned stop date — and document it before the test starts, not after.

Targeting Without Overfitting

• Concentrate test exposure where intent is highest: landing pages for paid traffic, PDPs of top-5 revenue SKUs, cart and checkout steps
• Pre-register segment analyses for device type and top 2 traffic sources only — any further cuts are exploratory and require a confirmatory follow-up before influencing rollout

---

Step 4: Variance Reduction and Targeting Within Your Analytics Stack

Variance reduction increases your ability to detect real effects at the same traffic volume. The failure mode is wide confidence intervals that mask workable lifts.

Tactics Compatible with GA4 and Common Testing Tools

Stratified randomization Block randomization by device type and top traffic sources. Run balance checks within 1 percentage point before the test begins.

Covariate adjustment Include pre-experiment behavioral signals (pages viewed, prior purchase) in your analysis model if the testing tool supports regression adjustment.

CUPED-like adjustment CUPED works by using a pre-experiment metric as a covariate to reduce the variance of your estimator — the effect is equivalent to increasing sample size without acquiring more traffic. If your platform supports it, use the built-in implementation. If not, run a clean pretest baseline week, exclude large campaign spikes from eligibility criteria, and apply the adjustment in your own analysis model. Note: a pretest baseline week alone is not CUPED — it is a useful but weaker substitute.

Ratio metrics Prefer revenue per session to total revenue, and add-to-cart per session to raw add-to-cart counts. Ratios stabilize across traffic volume swings.

Outlier control Winsorize revenue metrics at the 99th percentile in analysis. Disclose this treatment explicitly in the pre-analysis plan.

Targeting to Increase Exposure

• Route high-intent paid search and PLA traffic directly to instrumented PDPs and PLPs
• If top-5 SKUs drive 35–50% of revenue, run PDP experiments on those SKUs only to hit sample size faster, then generalize with a follow-up non-inferiority test on the long tail

Speed and Privacy Safeguards

• Inject variant code asynchronously; keep variant payloads under 50 KB compressed
• Fire GA4 conversion events only after consent is granted — apply the same rule identically in both arms

---

Step 5: Metrics Hierarchy and GA4 Measurement Plan

If metrics are not tied to unit economics, even statistically significant wins can fail to offset CAC. The failure mode is celebrating CVR lifts that reduce margin or increase returns.

Metrics Hierarchy

Level	Metric
Financial north star	Contribution margin per session = Revenue per session − Variable cost per session
Primary (pricing/bundles tests)	Revenue per session or gross profit per session
Primary (checkout friction tests)	Purchase conversion rate
Primary (cart behavior tests)	Cart-to-checkout rate or checkout initiation rate
Secondary	AOV, units per order, payment acceptance rate, return rate proxy
Guardrails	LCP, INP, CLS, bounce rate on landing page, bot rate

GA4 Measurement Plan

Event mapping Tag all ecommerce events with experiment_id and variant parameters: view_item → add_to_cart → begin_checkout → add_payment_info → purchase

Conversion definitions

• purchase as the primary key event for all tests
• begin_checkout as the primary key event for flow-specific tests

Segment ownership

Dimension	Segments
Device	Desktop, mobile web
Source	Paid search, paid social, organic search
Country	Groups reflecting shipping SLA and tax jurisdiction

Runtime QA

• Verify identical event counts in both arms on Day 1 of the test
• Monitor guardrails daily; abort if LCP regresses by more than 200ms or bounce rate increases by more than 3 percentage points

Analysis plan

• Pre-register primary metric, test horizon, and any covariate adjustment before launch
• For revenue metrics, winsorize at p99 and report both raw and adjusted results

ROI Linkage for the Board

Plain-language framing: “Out of every 200 visitors, 1 extra will buy. That pays for the CAC increase on this page.” Use this framing in the deck — not “CVR +0.5pp.”

Example math:

Input	Value
Baseline CVR	2.5%
AOV	$80
Monthly eligible sessions	100,000
Baseline revenue per session	$2.00

A 10% relative lift (2.5% → 2.75% CVR) adds $0.20 per session = $20,000 incremental monthly revenue at constant traffic.

If paid CAC rose 25% on $300,000 monthly spend, calculate the required incremental gross profit needed to hold MER flat, then size the required lift accordingly. Do not commit to a lift number in the deck before running this math with your actual COGS and variable fees.

FL2 check: Include one deck slide that converts projected lifts into contribution margin and CAC offset, validated with Finance’s COGS and variable fee assumptions. Repeated board questions about whether the win is profitable is the early warning signal that this slide is missing.

---

Step 6: Prioritization and ROI Modeling Under Engineering Constraints

If prioritization ignores bandwidth and statistical power, the roadmap becomes infeasible. The failure mode is a list of strong ideas that cannot ship this quarter. Use the RICE+ framework with conservative priors.

RICE+ Scoring

Column	Definition
Reach	Eligible sessions per week actually exposed to the change
Expected lift	Relative lift on the primary metric at the exposure point — use conservative priors
Confidence	Percentage confidence in the forecast and in feasibility
Effort	Total person-weeks across design, dev, QA, and analytics
Power gate	Yes if achievable MDE ≤ expected lift within 4 weeks; No otherwise
Incremental revenue/week	Dollar estimate
Incremental CM/week	Dollar estimate after variable costs
ROI	Incremental CM per person-week
Compliance risk	Low / Medium / High — only Low to Medium ship without legal review
Speed risk	Estimated LCP regression in ms
Dependency notes	Blocking requirements
Owner	Named individual
Status	Planned / In progress / Complete

Conservative Prior Rule

Cut any claimed lift estimate by 30–50% unless you have a directly comparable precedent from your own site. Industry case studies are not precedent — they reflect different audiences, seasonalities, and baselines.

Apply this rule to the example estimates below. The table shows raw literature-based estimates alongside conservative adjusted estimates for planning purposes:

Experiment	Raw lift estimate	Conservative adjusted (−40%)	Use in deck
PDP delivery promise, top-5 SKUs	4% CVR lift	~2.4% CVR lift	2–3%
Cart threshold meter	3% AOV lift	~1.8% AOV lift	2%
Express wallet order, mobile	5% CVR lift	~3.0% CVR lift	3%

Always use the conservative adjusted figure in the board deck. If you hit the raw estimate, it is a positive surprise. If you used the raw estimate and miss, credibility is damaged.

Prioritization Matrix — Starter Data Block

Spreadsheet header row:

Experiment | Reach_sessions_week | Expected_lift_pct | Confidence_pct | Effort_person_weeks | Power_gate | Incremental_rev_week | Incremental_CM_week | ROI_CM_per_person_week | Compliance_risk | Speed_risk_ms_LCP | Dependencies | Owner | Status

Example rows using conservative adjusted lifts:

PDP_delivery_promise_top5      | 60,000 | 2.4 | 60 | 0.5 | Yes | 6,000  | 3,900  | 7,800  | Low | 50 | None              | Owner A | Planned
Cart_threshold_meter           | 80,000 | 1.8 | 65 | 0.5 | Yes | 8,400  | 5,700  | 11,400 | Low | 70 | Depends on PDP    | Owner B | Planned
Express_wallet_order_mobile    | 90,000 | 3.0 | 55 | 0.3 | Yes | 9,600  | 6,600  | 22,000 | Low | 80 | None              | Owner C | Planned

ROI Modeling to Offset CAC Increase

1. Sum the conservative incremental CM per month across the prioritized experiment portfolio
2. Compare to the budget gap created by the 25% CAC increase
3. If the total falls short, replace lower-ROI items with higher-leverage alternatives, or increase change magnitude to meet MDE
4. Do not add experiments just to close the gap on paper — they still need to pass the power gate

Additional Pitfalls to Avoid

• Do not use optimistic lift figures — apply the 30–50% reduction rule before the deck is shared
• Block out engineering freeze windows and checkout risk periods on the roadmap before finalizing timelines
• Do not include any experiment that fails the power gate — it creates roadmap debt and erodes board confidence when tests are inconclusive

---

Step 7: Low-Dev, High-Impact Tests for the Shopify Stack

If implementations require custom apps, tests stall. The failure mode is blocked experiments due to platform constraints. Every tactic below runs in Shopify with GA4 and a standard testing tool.

Cart and Checkout

Shipping threshold meter in cart Show progress to free shipping and auto-update as items are added or removed. Implement as a theme section with a small script. Keep the payload under 10 KB. Track threshold crossing as a GA4 custom event.

Express checkout button order On mobile, surface the highest-adoption wallet first by device: Apple Pay on iOS Safari, Google Pay on Chrome Android. Configure in Shopify Payments settings and control placement via theme. See the technical risk note on User-Agent detection below.

Checkout friction reduction

• On Shopify Plus: use Checkout Extensibility to reduce optional fields and reorder sections
• Not on Plus: turn off optional fields in Settings and ensure the phone field is optional unless the shipping carrier requires it

Payment acceptance Enable Shop Pay, PayPal, and card wallets. Display payment badges near the checkout CTA — proximity matters.

Product Detail Page

Sticky add-to-cart on mobile Minimal JS implementation using IntersectionObserver to show a fixed bar with price and selected variant when the native button scrolls out of view.

Delivery estimates Show a location-aware delivery window near the price. If live rate APIs are not available, use a static rule by country or state as a starting point.

Risk reversal microcopy Place the returns policy link within the immediate PDP viewport — not just in the footer.

Merchandising and AOV

Bundles Use Shopify Bundles or a lightweight custom bundle PDP that adds multiple SKUs in a single click. Track as one add_to_cart event with all SKUs enumerated in a custom GA4 parameter.

Quantity breaks Display the per-unit price at 2+, 3+ quantities as a transparent discount. Configure via Shopify Automatic Discounts — no custom code needed.

Cross-sell in cart drawer Add one contextually relevant accessory below the subtotal. Cap at a single recommendation to avoid scroll bloat.

Technical Risks on Shopify + GA4 — Monitor These Before Launch

1. Flash of Unstyled Content (FOUC) from async variant injection When injecting variant code asynchronously on Shopify PDP, the page can flash the original state for 200–500ms before the variant renders. This degrades CLS scores and can trigger the LCP guardrail. Mitigation: hide the target element with CSS before the variant script fires and reveal it after render, or use IntersectionObserver-based injection scoped tightly to the element being changed. Measure CLS before and after in a staging environment before deploying.

2. GA4 data gap from Consent Mode In markets with strict cookie consent requirements, users who decline will have all GA4 events — including experiment_id and variant parameters — suppressed. This creates a systematic gap in your experiment data for exactly the privacy-conscious segment. Mitigation: set up a parallel raw order data pull from Shopify Admin (order metafields, reports, or API) as a verification source. Cross-reference Shopify-side order counts against GA4 purchase events to quantify the consent gap before drawing conclusions from the GA4 data alone.

3. Express checkout button conflicts on mobile Prioritizing wallet buttons by device type requires User-Agent detection to surface Apple Pay on iOS Safari and Google Pay on Chrome Android. If the detection logic is imprecise or cached incorrectly, Apple Pay can appear on Android Chrome (where it will not load) or vice versa, creating a broken checkout path. Mitigation: test across real devices — not just emulators — covering at minimum iOS Safari, Chrome iOS, Chrome Android, and Samsung Internet. Add a fallback rule that hides the wallet button entirely if the payment method cannot be confirmed as available on the current browser.

Speed and SEO Safeguards

• Defer third-party scripts; lazy-load non-critical images
• Measure LCP and INP before and after each test deployment; abort if LCP regresses by more than 200ms
• Do not modify canonical tags or structured data as part of any CRO experiment

Privacy

• Honor Consent Mode: suppress test beacons and GA4 parameters when consent is not granted
• Do not insert PII into any GA4 event parameter

---

Step 8: Board-Ready Roadmap and Executive Deck

If the roadmap is framed in technical terms without business translation, it will not be approved. The failure mode is a deck the board cannot connect to CAC and margin. Package for executives with three numbers per slide: lift, cost, payback.

Deck Structure

1. Title: Q[X] CRO Roadmap to offset paid CAC increase
2. The gap: CAC is up 25%; required on-site lift to hold MER flat is [X]%
3. Strategy: Focus on offer, flow, and pricing — not cosmetic UI changes
4. Measurement discipline: Power-aware tests in GA4, conservative priors, guardrails on speed and privacy
5. Prioritized experiments: Top 6 items with Reach, Lift (conservative), Effort, ROI, Power gate status
6. Financial impact: Modeled incremental contribution margin per month and payback period
7. Risk controls: Legal, privacy, page speed regression cap, rollback plan
8. Timeline: Week-by-week execution for the quarter with named owners
9. Ask: Resource allocation in person-weeks and any vendor costs
10. Appendix: Pre-analysis plan, MDE calculator with your numbers verified, full experiment backlog

One-Page Executive Summary Template

Title: Q[X] CRO plan to neutralize paid CAC increase

Problem Paid CAC increased 25% over the last 8 weeks. To maintain MER and revenue targets, on-site conversion and order economics must improve this quarter.

Plan Run a focused set of high-leverage experiments on offer, flow, and pricing mechanics that can resolve within current traffic and existing stack. Power-aware fixed-horizon designs in GA4, conservative lift assumptions, and hard guardrails on page speed and privacy.

Top experiments (conservative lift estimates)

Experiment	CVR/AOV lift	Effort	ROI
PDP delivery promise, top-5 SKUs	~2–3% CVR lift	0.5 person-weeks	~7,800 CM/person-week
Cart threshold meter	~2% AOV lift	0.5 person-weeks	~11,400 CM/person-week
Express wallet order, mobile	~3% CVR lift	0.3 person-weeks	~22,000 CM/person-week

Financial impact (conservative) Modeled monthly incremental contribution margin: [recalculate with your COGS before presenting] Payback on resource ask: [recalculate]

Safeguards

• Page speed regression cap: LCP ≤ +200ms; abort trigger if exceeded
• Privacy: GA4 Consent Mode enforced in both arms; Shopify order data as cross-reference
• Rollback: under 30 minutes via Shopify theme versioning

Decision required Approve [X] person-weeks cross-functional bandwidth in [Month] and [Y] person-weeks in [Month+1].

Sign-Off Standard

Secure written approval — not verbal — covering: named owners, hours allocated, go-live window, and pre-registered stopping rules. Board questions about who owns what or whether legal reviewed are early warning signals that this step was skipped.

---

One-Week Production Plan

Day	Actions
1	Pull baselines from GA4; compute MDE and power gates with actual eligible session counts; confirm legal and privacy constraints; list candidate experiments
2	Score candidates with RICE+; apply conservative lift adjustments; shortlist top 6 with power gates; draft pre-analysis plans
3	Write copy and configuration for top 3 low-dev tests; stage theme changes; QA event tagging with experiment_id and variant parameters; test across real devices for express checkout
4	Finalize deck and one-pager; Finance review of contribution margin math; verify Shopify order data pipeline for consent gap cross-reference
5	Executive review; incorporate feedback; pre-schedule launches with named owners and documented stopping rules

---

Operating Rules for the Quarter

Keep these visible for every team member working on this roadmap:

1. Pre-commit to the stopping rule before launch. Never adjust it after the test begins.
2. Do not peek at results before the pre-committed stop date unless the testing tool has built-in sequential controls and you are using them correctly.
3. Apply the 30–50% lift reduction rule to all estimates before the deck is shared externally.
4. Verify Weeks_needed using your actual eligible session count for each test — not sitewide sessions.
5. Run balance checks within 1 percentage point on Day 1 of each test. Abort and relaunch if randomization is off.
6. Do not modify canonical tags, structured data, or site navigation as part of any CRO experiment.
7. Measure LCP and INP before and after each deployment. Abort if LCP regresses by more than 200ms.
8. Do not include any experiment that fails the power gate in the official roadmap — log it as backlog for higher-traffic periods.

---

By grounding the roadmap in power-aware design, high-leverage offer and pricing changes, GA4 measurement tied to unit economics, and Shopify-compatible low-dev implementations — with conservative lift estimates and verified sample size math — you can ship an executive-ready CRO plan in one week and run tests this quarter that resolve at your traffic and contribute enough margin to offset the CAC increase. The most common failure is optimism without power or ownership. The templates and guardrails above prevent both.

Use this playbook to diagnose traffic losses, validate the root cause, map target entities, ship safe fixes, and package an executive-ready plan with owners, timelines, and recovery estimates — all within 14 days.

---

Prerequisites

Before starting, confirm you have:

• Google Search Console and Analytics access with edit rights
• CMS access to update copy, anchors, and JSON-LD
• Content inventory and sitemap
• Rich Results Test and Schema Markup Validator
• Limited dev and content bandwidth — assume on-page edits, schema, and internal links are in scope; template or layout changes are out of scope for this sprint

Expected output: An executive-ready plan mapping target entities to priority pages, prioritizing low-effort on-page, schema, and internal-link updates with named owners and timelines, plus page-level recovery estimates. Initial changes are shipped and validated within the window. Executives approve rollout and early metrics show stabilizing impressions on targeted pages.

---

Step 0: Validate the Root Cause Before Committing Resources

This step is frequently skipped — and it is the most common reason a technically sound entity-based fix delivers no recovery. Entity ambiguity is one cause of core update traffic loss, not the only one. Before assigning hours to schema and disambiguation work, rule out the alternatives.

Check These First

Confirm it is not a technical issue Verify the affected pages return 200, are not canonicalized elsewhere, carry no noindex tag, have no soft 404 signals, and are not blocked in robots.txt. Use Screaming Frog or a site audit crawl. If technical issues are present on any candidate page, fix those first and exclude the page from entity recovery scope.

Check whether the loss is brand navigational, not entity confusion Pull the query breakdown per page in GSC. If the majority of lost clicks come from queries containing your brand name, the problem is brand signal or SERP feature displacement, not entity ambiguity. Entity-based fixes will not recover brand navigational losses.

Look at competitor and SERP-level signals Search the primary query for each candidate page and note what Google currently shows: does a Knowledge Panel appear for a different entity? Has a competitor moved into a featured snippet or top position? Has the SERP format shifted from blue links to an AI Overview or rich result? If the SERP itself changed, the fix may need to be content depth or structured data eligibility — not disambiguation alone.

Check whether the Knowledge Graph already recognizes your entity Search [your brand name] site:wikidata.org and check whether a Knowledge Panel surfaces for your brand on a branded query. If Google’s Knowledge Graph already has a clean signal for your entity, page-level confusion is less likely to be the dominant cause.

Decision Gate

If after these checks entity ambiguity remains the most plausible explanation — same or similar entity names competing, mixed signals across heading, schema, and anchors, or a page that could reasonably be parsed as covering two different things — proceed to Step 1.

If a different root cause is identified, stop this playbook and address that cause directly. Do not force entity-based fixes onto a technical or content-depth problem.

---

Step 1: Triage Losses and Select Priority Pages

You cannot fix everything in 14 days. This step narrows scope to the highest-impact, lowest-effort pages and creates the single source of truth for the rest of the plan.

Pull Losses from GSC

GSC Performance → Search Results

• Date range: last 28 days vs. previous 28 days
• Dimensions: Page, Query
• Metrics: Clicks, Impressions, CTR, Position
• Run once filtering out brand terms (non-brand view), then again for brand view

Export Analytics landing page data for the same periods with Sessions and Revenue or Goal value where available.

Tag Candidates by Severity

Severity	Threshold	Criteria
S1	−40% or more clicks	High past value — prioritize
S2	−20% to −39% clicks	Material value — include
S3	−10% to −19% clicks	Experimental or peripheral content

Exclude any page with a confirmed technical issue (404, wrong canonical, noindex, soft 404, layout shifts, robots block) before severity tagging. Technical issues require a different fix track.

Scope to Bandwidth

Choose 10 to 20 pages total, weighted toward S1, where fixes are achievable without template changes or significant dev work. For each page, assign a page type (Article, Guide, Product, Category, Comparison, Feature, Docs) and write a working hypothesis: what entity this page must own and what it is currently being confused with.

Start the Mapping Sheet

Use the following columns. Keep it in a shared doc and update daily.

Column	Description
Page URL
Page type
Primary target entity
Disambiguation note
Secondary entities to cover
Current sameAs on page
Proposed sameAs
On-page fixes
Schema to add or fix
Internal links to add
Owner
Effort (1–3)
Impact (1–3)
Due date
Status
Baseline clicks 28d
Est. recovery clicks 28d
Confidence (Low / Med / High)
Risks and rollback

Example rows:

URL: https://acme.com/hr-software
Type: Product
Primary entity: Acme HR Software
Disambiguation: Distinct from Acme Consulting
Secondary entities: HRIS, payroll, time tracking
Proposed sameAs: Wikidata Q1234567, LinkedIn, Crunchbase
On-page fixes: Add definition block, tighten H1, replace stock logo with product UI image
Schema: SoftwareApplication with sameAs and offers
Internal links: From /hr-software hub, /pricing, top 3 guides with anchor "hr software"
Owner: PM | Effort: 2 | Impact: 3 | Due: Day 8
Baseline: 5,200 clicks | Est. recovery: 1,300 | Confidence: Med
Rollback: Revert if CTR drops 20% over 7 days post-indexing

URL: https://acme.com/what-is-hris
Type: Article
Primary entity: Human Resource Information System
Disambiguation: Distinct from HCM and payroll-only tools
Secondary entities: HR database, employee records
Proposed sameAs: Wikipedia HRIS, Wikidata Q890123, Gartner glossary
On-page fixes: Add single-sentence definition, add comparison section, adjust internal anchors
Schema: Article with mainEntity and sameAs
Internal links: From /hr-software hub and glossary, add related module
Owner: Content Lead | Effort: 1 | Impact: 2 | Due: Day 5
Baseline: 8,900 clicks | Est. recovery: 900 | Confidence: High
Rollback: Revert if impressions fall 30% over 7 days

Early Warning Signals — Cut Scope If You See These

• Candidates require template changes or CMS migrations
• Top losses are brand navigational queries, not entity-confused queries
• Multiple pages are targeting the same entity and cannibalizing each other at scale

If any of these apply, reduce scope immediately and replace affected pages with ones that fit the low-effort criteria.

---

Step 2: Identify Target Entities and Write Disambiguation Notes

Entity-first recovery depends on naming the one thing the page is about and explicitly removing ambiguity. Without this, schema and internal links amplify mixed signals rather than resolving them.

Derive the Primary Entity from Search Intent

Use the query data from GSC for each page. For informational guides, choose a concept entity — not your product name. For product and feature pages, choose your product or the specific feature as the entity. Check for ambiguity risks: similar names, acronyms shared with other concepts, or your brand name overlapping with a generic category term.

Find Authoritative sameAs References

Preferred sources (in order of entity recognition strength with Google):

1. Wikidata item
2. Wikipedia article
3. Official standards body or major industry glossary
4. Your official LinkedIn company page
5. Crunchbase organization profile
6. App Store or G2 listing (for software products)
7. GitHub (for developer tools)

If your brand or product has no Wikidata or Wikipedia entry — which is common for B2B SaaS products — use LinkedIn and Crunchbase as primary sameAs sources. Be aware that Google’s entity recognition from these sources is weaker than from Wikidata or Wikipedia. In this case, invest more effort in on-page clarity: a precise definition sentence in the first 100 words carries more weight when authoritative external references are thin. If building a Wikidata entry is feasible (notable enough product, enough sourcing), doing so before this sprint ends will strengthen recovery.

Write the Disambiguation Note

One sentence stating what this entity is and what it is not. You will reuse this sentence in on-page copy and in anchor context. Keep it consistent across every surface.

Example: Acme HR Software is a Human Resource Information System for mid-market HR teams — not a standalone payroll tool or an HR consulting service.

List Secondary Entities

Identify 3 to 6 related entities you must mention or define on the page to anchor the primary entity’s meaning. These support disambiguation without diluting the primary focus.

Document Everything in the Mapping Sheet

Fill: Primary target entity, Disambiguation note, Secondary entities, Proposed sameAs.

Prompt to Speed Up Entity Selection

Paste this into your preferred AI assistant to generate candidates quickly:

Analyze [PAGE URL]. List:
1. Candidate primary entity for this page
2. Top 5 secondary entities required for disambiguation
3. Ambiguity risks (similar names, shared acronyms, brand vs. generic)
4. Recommended authoritative sameAs URLs for the primary entity
5. A one-sentence disambiguation note

Return in bullet points only.

---

Step 3: Apply On-Page Entity Signals

On-page is where you remove ambiguity for both users and parsers. Aim for small, safe edits that clarify the entity without rewriting or restructuring the page.

Checklist

Headings

• H1 includes the canonical entity label where it reads naturally
• First H2 introduces a precise definition or scopes the page’s coverage

Definition block

• Single-sentence definition within the first 100 words
• If ambiguous, add a short “This page covers X, not Y” clarification immediately after

Attributes and qualifiers

• Include key properties that narrow meaning: industry, geography, format, version, scale

Media

• Replace generic hero images with entity-revealing visuals
• Add captions that name the entity and a relevant attribute

Anchors

• First internal link to the hub uses the exact canonical entity label
• Subsequent links use attribute anchors aligned to search intent variants

Glossary popovers

• Where overlapping terms exist, insert a short tooltip definition matching your disambiguation note

Cannibalization check

• If two pages target the same entity, designate one as the hub and retitle or re-scope the other before shipping either

Before-and-After Examples

Element	Before	After
H1	The Complete Platform You Need	Acme HR Software — HRIS for mid-market teams
Opening	Our platform helps HR teams do more.	Acme HR Software is a Human Resource Information System for mid-market HR teams. This page covers HRIS capabilities, not standalone payroll apps.
Image caption	Powerful dashboard	Acme HR Software dashboard showing employee records — the core HRIS database

Guardrails

• Use the canonical label clearly once, then vary with attribute qualifiers — do not repeat the exact phrase unnaturally
• Keep all edits inside the current layout — no template or design debt in this sprint
• Keep definitions consistent with sameAs references and hub copy

---

Step 4: Add and Validate Schema

Start with minimal, high-signal JSON-LD that accurately reflects the visible page content. Validate everything before deploying. Keep a change log entry for every deployment.

Prioritized Schema Types by Page Type

Page type	Schema type
Product or feature page	SoftwareApplication or Product embedded in WebPage
Informational article or guide	Article with mainEntity and about
Category or hub page	CollectionPage or WebPage with about array
Homepage and About page	Organization with sameAs; add BreadcrumbList sitewide if already supported

Key distinction: Use mainEntity when the page is the entity (product pages, glossary definitions). Use about when the page discusses an entity (articles, guides). Mixing these up is a common error that creates schema that contradicts your visible content.

Required Properties for Safe Deployment

All types: @context, @type, name, url

• mainEntity or about referencing your primary entity
• sameAs array using authoritative sources (see Step 2 priority order)

SoftwareApplication: applicationCategory, operatingSystem, offers (only if pricing is explicitly stated on the page)

Article: headline, datePublished, author, mainEntityOfPage

JSON-LD Examples

SoftwareApplication on a product page:

{
  "@context": "https://schema.org",
  "@type": "WebPage",
  "url": "https://acme.com/hr-software",
  "name": "Acme HR Software - HRIS for mid-market teams",
  "mainEntity": {
    "@type": "SoftwareApplication",
    "name": "Acme HR Software",
    "applicationCategory": "Human Resource Information System",
    "operatingSystem": "Web",
    "url": "https://acme.com/hr-software",
    "sameAs": [
      "https://www.wikidata.org/wiki/Q1234567",
      "https://www.linkedin.com/company/acme",
      "https://www.crunchbase.com/organization/acme"
    ],
    "offers": {
      "@type": "Offer",
      "priceSpecification": {
        "@type": "PriceSpecification",
        "priceCurrency": "USD"
      },
      "url": "https://acme.com/pricing"
    }
  }
}

Article with concept entity:

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "What is HRIS? Definition, examples, and architecture",
  "url": "https://acme.com/what-is-hris",
  "mainEntityOfPage": "https://acme.com/what-is-hris",
  "author": {
    "@type": "Organization",
    "name": "Acme"
  },
  "about": [
    {
      "@type": "Thing",
      "name": "Human Resource Information System",
      "sameAs": [
        "https://en.wikipedia.org/wiki/Human_resource_information_system",
        "https://www.wikidata.org/wiki/Q890123"
      ]
    }
  ],
  "datePublished": "2024-06-05",
  "dateModified": "2024-07-01"
}

Organization on homepage:

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Acme, Inc.",
  "url": "https://acme.com",
  "logo": "https://acme.com/assets/logo.png",
  "sameAs": [
    "https://www.linkedin.com/company/acme",
    "https://www.crunchbase.com/organization/acme",
    "https://en.wikipedia.org/wiki/Acme_Inc"
  ]
}

Validation Workflow

1. Paste code into Rich Results Test — confirm eligibility and no critical errors
2. Paste into Schema Markup Validator — check type and property validity
3. Deploy to staging and re-run both validations
4. After publishing, use URL Inspection → Request Indexing in GSC
5. Add a change log entry immediately (see Step 7 for the change log format)

Common Mistakes to Avoid

• Adding FAQPage schema when no visible Q&A exists on the page
• sameAs pointing to sales pages, low-authority directories, or internal redirects
• mainEntity that contradicts your H1 or definition sentence
• offers with an exact price when the page only shows a range or “contact us”
• Using about on a product page instead of mainEntity (or vice versa)

---

Step 5: Reinforce Entity Signals with Internal Linking

Internal links reinforce entity meaning and distribute authority safely. Design linking rules that writers and editors can follow without new tooling.

Hub-and-Spoke Architecture

Every entity needs exactly one hub page — the canonical source that defines the entity and hosts deep links to related spokes. The hub URL must be consistent across all linking. Spokes must link back to the hub using the canonical entity label as the anchor text near the top of the page.

If a hub does not yet exist for a primary entity you are recovering, create a minimal hub (even a short glossary entry) and link to it from all relevant spokes before the sprint ends.

Linking and Anchor Rules

• First mention on a spoke: link to hub using the exact canonical entity label
• Secondary anchors: use attribute qualifiers aligned to search intent (e.g., “hr software for small business,” “hris database schema”)
• Hub pages: include a Related topics or Learn more module linking to high-value spokes
• Product pages: include a “From the glossary” or “Compare to alternatives” section where relevant
• Volume limit: 1 canonical hub link near the top + 2 to 4 contextual links to related entities per page
• Avoid reciprocal spoke-to-spoke link loops unless a comparison intent exists

Checklist Before Shipping Links

• [ ] Single hub URL exists for the entity
• [ ] Each spoke links to the hub within the first 150 words
• [ ] First anchor is exactly the canonical entity label
• [ ] 2 to 4 contextual links to related entities or features per page
• [ ] Comparison pages link both ways using “compare” anchors
• [ ] No two pages competing for the same canonical label (if yes, pick a winner and adjust titles)

Guardrails

• Do not mass-insert identical anchors sitewide — vary context naturally
• Do not create orphan hubs — every hub must be reachable from global nav or a sitemap module

---

Step 6: Stabilize Brand Entity Signals

If Google cannot consistently identify your brand entity, page-level fixes will collide with mixed signals at the brand level. Stabilize brand signals first — these are low-lift and high-leverage.

Core Actions

Organization schema Ensure a single Organization JSON-LD on the homepage and About page with name, url, logo, and authoritative sameAs. Use the same logo URL that appears in your brand panel if one exists.

Consistent brand name Use one canonical brand string in page titles, authorship bylines, footer copyright, and social bios. A different name in Org schema versus your Wikipedia entry is one of the fastest ways to split entity signals.

Resolve lookalike conflicts If another brand shares your name, add a qualifier in the first sentence of your About page and in the description field of Org schema.

Example: Acme, Inc. is an HR software company — not the logistics brand Acme Corp.

Logo and site name Confirm the correct logo file path and site name are set consistently across all pages. Inconsistency here causes Knowledge Panel instability.

Success Criteria

Branded searches surface a single, accurate entity with the correct name, logo, official website, and authoritative sameAs. Key pages pass schema validation without critical errors.

Warning Signals

• Knowledge Panel intermittently shows another logo or wrong description
• Search results mix two different official sites for brand queries
• Org schema name differs from the brand string used in Wikipedia or GSC sitelinks

---

Step 7: Measurement, Change Log, and Rollback

You need conservative recovery estimates, a simple daily scoreboard, and a clear process to revert changes safely if volatility worsens.

Per-Page Recovery Estimates

Baseline: Last 28 days — clicks, impressions, CTR, position Loss: Delta vs. previous 28 days

Recovery rate by confidence level:

Confidence	Rate	When to use
High	35–40% of lost clicks	sameAs and on-page definitions were clearly absent; fixes are direct
Medium	20–30% of lost clicks	Partial signals present; some ambiguity but not severe
Low	10–15% of lost clicks	Competitors changed intent; SERP format shifted; cause uncertain

Formula: Est. recovery clicks (28d) = Lost clicks × recovery rate Example: Page lost 1,300 clicks. Medium confidence → 1,300 × 25% = 325 clicks estimated recovery in 28 days after indexing.

These estimates are ranges for executive communication, not guarantees. Present them with confidence levels visible, not as a single number.

KPIs and Daily Checkpoints

Checkpoint	What to check
Daily (Days 1–14)	GSC page-level impressions and average position trend
Days 3–5	Schema indexed: use URL Inspection + Rich Results Test re-fetch
Day 7	Impressions stabilizing vs. pre-change 7-day baseline
Day 14	Directional improvement in impressions and CTR on updated anchor pages

On indexing lag: After clicking Request Indexing, Google may take 5 to 10 days (sometimes longer) to recrawl, process schema, and update GSC data. Do not treat a flat Day 7 as a failure signal. Watch impressions as the leading indicator — position and clicks typically recover later. Panic-reverting before Day 10 is the most common avoidable mistake.

Change Log — Required Fields

Maintain one shared log for all changes across all pages.

Field	Description
Date and time	When the change was deployed
Page URL
Change summary	What was changed (H1 wording, schema type added, anchor text, etc.)
JSON-LD version	Version label if applicable
Validator screenshots	Link to Drive folder with validation results
Owner	Who deployed
Expected effect	What metric should move and in which direction
Rollback plan	Exact steps to revert this specific change

Example entry:

Date: 2024-07-03
Page: https://acme.com/hr-software
Change: Added definition sentence to opening paragraph, updated H1, added SoftwareApplication JSON-LD with sameAs to Wikidata Q1234567 and LinkedIn
JSON-LD version: v1.0
Validator: [Drive link — Rich Results Test pass + Schema Validator pass]
Owner: Ravi
Expected effect: Impressions increase within 7–10 days post-indexing
Rollback: Remove JSON-LD block and revert H1 to previous version if CTR drops 20% sustained over 7 days post-indexing

Rollback Triggers

Monitor these signals for 5 to 7 days after confirmed indexing (not after deploy):

• Impressions −30% vs. pre-change 7-day average — with no sitewide cause (core update, crawl anomaly)
• CTR −20% while position is stable or improving
• Schema critical errors flagged in validators

Rollback action: Revert only the most recent change entry in the log. Do not roll back multiple changes at once. Request recrawl immediately after reverting and record a rollback entry in the log. If the issue persists after reverting, pause further changes to that page set and revisit the disambiguation notes — the entity hypothesis may need revision.

---

Step 8: Package the Plan for Executive Sign-Off

Executives approve faster when revenue math, owners, risk controls, and expected outcomes are visible on one page. Use the template below as the cover; attach the mapping sheet and change log as annexes.

One-Page Executive Summary Template

Title: 14-day entity-first recovery — [N] priority pages and expected impact

Situation (one line): Traffic dropped after core update, concentrated on [N] pages where Google is confusing [Entity A] with [Entity B].

Plan (three bullets):

• Clarify entity signals on [N] priority pages with on-page definition edits, anchor standardization, and JSON-LD
• Strengthen internal links to entity hubs and stabilize brand entity signals
• Validate all changes, monitor GSC daily with defined rollback triggers, and rollback individual changes if negative thresholds are crossed

Scope and owners: Pages: [top 5–10 URLs] Owners: [PM name], [Content name], [Dev name] with due dates

Effort and timeline:

• Week 1: Entity mapping, on-page edits, Org schema audit
• Week 2: JSON-LD deployment, internal links, validation, measurement baselines, executive package

Expected outcome (business terms): Stabilize impressions within 7–10 days. Recover [X–Y] monthly clicks on priority pages within 30–45 days. At current conversion rate of [Z%], this represents approximately [N] additional leads per month without incremental ad spend.

Risk controls: No template changes, all schema validated before deploy, change log maintained, rollback thresholds defined per page, freeze on new experiments during rollback periods.

What approval unlocks: [N] content hours, [N] dev hours, JSON-LD deploy permissions, internal link update rights.

Filled Example

Title: 14-day entity-first recovery — 12 priority pages

Situation: Post-core-update, 12 pages lost 18,500 clicks in 28 days. GSC query data confirms entity confusion between Acme’s HRIS product and generic HR consulting services — not a technical or brand navigational issue.

Plan:

• Clarify entity labels and definitions on 12 pages, add sameAs JSON-LD, standardize anchors
• Route internal links through HRIS and HR software hubs
• Validate schema, log all deployments, monitor GSC daily with rollback triggers

Scope: 12 URLs | PM: Dana | Content: Lee | Dev: Ravi

Timeline: Week 1: on-page + Org schema | Week 2: JSON-LD + links + validation

Expected outcome: Stabilize impressions by Day 10. Recover 5,000–7,000 clicks/month in 45 days. At 2% conversion, approximately 100–140 additional leads per month at zero incremental ad cost.

Risk controls: No template edits, all schema validated, rollback if CTR drops 20% for 7 days post-indexing

Approval unlocks: 24 content hours, 8 dev hours, JSON-LD permissions

Sign-Off Standard

Verbal approval is not enough. Secure written confirmation (email or doc) from each function covering: owners, hours allocated, and go-live window. If leadership questions the validation or rollback sections, that is an early warning — do not remove them. These controls are what make the plan safe to approve.

---

Day-by-Day Execution Timeline

Days	Actions
1–2	GSC triage, validate root cause (Step 0), select 10–20 pages, start mapping sheet and draft disambiguation notes
3–5	Ship on-page edits: H1, definition sentence, image captions, first-anchor rules
3–5	Write JSON-LD drafts and validate in Rich Results Test and Schema Markup Validator
6–8	Deploy JSON-LD to 5–8 pages, request indexing, log all changes
6–8	Add internal links and related modules where trivial to implement
9–12	Complete JSON-LD for remaining pages, finalize brand Org schema
9–12	Build executive one-pager and per-page writer briefs
9–12	Begin daily GSC monitoring, capture and file validator screenshots
13–14	Package plan with owners, timelines, estimates, guardrails
13–14	Present one-pager, secure written approval

---

Writer-Ready Brief Template (One Per Page)

Produce one of these for each priority page and hand to the content owner.

Page URL and type:
Primary entity:
Disambiguation sentence (copy exactly into opening paragraph):
Secondary entities to mention and define (3–5):
On-page edits:
  - H1 (exact wording):
  - Definition sentence (exact wording, place within first 100 words):
  - Image caption (exact wording):
Anchors:
  - First anchor text (exact canonical label → hub URL):
  - 2 contextual anchor variants with qualifiers:
Schema:
  - Type to add:
  - Where it will live in the CMS:
  - sameAs list (in priority order):
Internal links to add:
  - Where in copy:
  - Destination URL:
Owner:
Due date:
Rollback condition:

---

Operating Rules for the Sprint

Keep these visible for every team member working on this plan:

1. No template or layout changes inside 14 days. On-page text, schema, and anchors only.
2. Only add schema that reflects visible content. If the page does not show it, the schema should not claim it.
3. Validate in Rich Results Test and Schema Markup Validator before every deployment — no exceptions.
4. Log every change before closing the browser tab. An unlogged change cannot be safely rolled back.
5. Do not roll back based on Day 3–5 data. Wait for confirmed indexing (typically 5–10 days) before evaluating impact.
6. One rollback action at a time. Revert the most recent log entry only, then observe before reverting more.
7. If entity ambiguity is not confirmed as the root cause, stop and revisit Step 0.

---

You now have a two-week, low-risk, entity-first recovery plan: root cause validated before committing resources, priority pages selected by severity, entities mapped with authoritative references, on-page and schema fixes shipped safely, internal links reinforced, and everything packaged for executive approval with forecasts, owners, and rollback controls. Keep the change log tight and signals consistent.

A constraints-first playbook for marketing leaders who need to align channels, fix funnel leaks, and ship a 90-day rollout — using the stack and budget they already have.

---

On timing: “One week” assumes your web, CRM, and ad platform data are already accessible and reasonably clean, and that you can secure 3 short stakeholder alignment sessions within the week. If data needs normalization first or key stakeholders are unavailable, budget 8–10 working days. The planning week is realistic under those conditions; the 90-day execution is where the real work happens.

On example numbers: The filled examples throughout this guide use specific figures (LP CVR 1.5%→2.2%, demo-to-SQO 28%→33%, day-14 activation 48%→56%) to make the framework legible. These are illustrative only — not benchmarks. Your actual baseline and realistic lift will depend on current traffic volume, sales team capacity, product complexity, and how much technical debt exists in your landing pages and CRM workflows. Always replace example numbers with your own baseline before presenting to executives.

---

What You’ll Produce

By the end of this playbook:

• An executive summary one-pager ready to attach to the deck for leadership sign-off
• A journey snapshot with channel roles (lead vs. support) for each of 6 stages
• A prioritized backlog of 5–7 initiatives scoped to current stack and budget
• A 90-day rollout swimlane with owners, milestones, and week-2 early warning checkpoint
• A pragmatic KPI set with primary metrics, proxy signals, and a holdout design guide
• A 12–15 slide executive deck built for decision-making, not education

---

Prerequisites to Gather Before You Start

Input	Where to get it	If unavailable
Active channels and campaigns list	Marketing ops or ad platform exports	Reconstruct from last 90-day spend report
Current quarter budget envelope	Finance or CMO	Confirm before any initiative scoping
Martech inventory with access status	IT or marketing ops	Self-audit: list tools you personally have login access to
Last 90 days: web, CRM, ad metrics	GA4, CRM reports, ad dashboards	Use screenshots — no new reports needed
3–5 insights from sales and CS calls	SDR manager and CS lead (45-min combined session)	Pull from CRM call notes or recent lost-deal reports
Stakeholder calendar holds	3 × 30-min slots this week	Lock these on day 1 — they’re the hardest constraint

Copy-ready data request (send day 1):

Subject: 48-hour data pull for omnichannel planning

Please share last 90 days for these fields by EOD tomorrow: web sessions by channel; top 10 landing pages with CVR; CRM leads by lead source with MQL, SQO, and win counts; ad spend, reach, CTR, and cost per lead; email open rate, click rate, and average form-to-response time. No new reports — exports or screenshots are fine.

Data Readiness Go/No-Go Gate

Before committing to the 1-week timeline, run this quick check on day 1. If you hit two or more “No” answers, move to the 8–10 day track immediately — don’t try to plan strategy and clean data simultaneously.

Check	Yes	No
Can you pull GA4 channel-level sessions and CVR for the last 90 days in under 30 minutes?	✅ Proceed	❌ Add 1–2 days for data normalization
Does your CRM show lead source with MQL, SQO, and win fields populated for >85% of records?	✅ Proceed	❌ Add 1 day for lead source cleanup
Are your ad platform UTMs consistent with GA4 source/medium naming?	✅ Proceed	❌ Add half a day for UTM audit
Can you identify your top 3 LP conversion rates right now without building a new report?	✅ Proceed	❌ Add 1 day for baseline capture
Do you have at least 3 recent call notes or loss reasons from sales or CS?	✅ Proceed	❌ Schedule a 45-min sales/CS session before planning begins

If you’re on the 8–10 day track: Spend days 1–2 on data cleanup only. Do not begin Phase 1 until the go/no-go checks above all pass. A strategy built on unclean data produces KPIs no one trusts — which is worse than a slightly delayed deck.

---

Phase 1 — Define Outcomes, Constraints, and Guardrails

Time: ~2 hours | Day 1

Why constraints come first

Most omnichannel plans fail not because the strategy is wrong but because it asks for things the organization cannot deliver: new platforms, net-new budget, or headcount. This playbook locks constraints first and fits every initiative inside them. That’s what makes it approvable.

Step 1: Set 1–2 business outcomes for the quarter

Keep these at the outcome level, not the activity level:

• “Increase qualified pipeline by 20%” ✅
• “Improve onboarding activation rate from 45% to 55%” ✅
• “Run more LinkedIn campaigns” ❌ (activity, not outcome)

Step 2: Lock constraints and guardrails in writing

Document these four constraints before selecting any initiative:

Constraint	Rule
Time	1-week strategy creation; 90-day rollout
Budget	Only within this quarter’s approved envelope — no new asks
Stack	No replatforming; current tools only for 90 days
Risk	Every initiative must ship visible value by week 4 or be cut and replaced

Step 3: Take a clear-eyed inventory of what’s working and what isn’t

Document three things:

• What is already working directionally (even if imperfectly measured)
• What is not working and will be explicitly paused to free capacity
• What data exists now and what proxies you’ll use where data is missing

This inventory prevents the most common mistake: running more channels and initiatives on top of broken ones.

Step 4: Write your executive summary one-pager now

Write a rough version today and refine it through the week. The structure should not change — only the numbers and evidence get sharper.

Executive Summary One-Pager Template:

Objectives: [business outcomes with numbers]
Constraints and guardrails: [the 4 constraints above]
Current channels — directional performance: [2-3 lines per channel]
Selected bets and rationale: [why these 5-7 fit within constraints]
Channel roles by journey stage: [lead vs. support at a glance]
90-day milestones: [4 checkpoints]
KPIs and proxy measurement: [primary + proxy per stage]
Risks and mitigations: [2-3 bullets]
Approval ask and owners: [what you need today, who owns what]

Filled example:

Objectives

• Add $3.2M qualified pipeline in Q3
• Lift onboarding activation from 48% to 56%

Constraints

• 1-week planning, 90-day execution
• No new platforms or headcount; $120K media + $20K production within existing envelope
• Must demonstrate lift by week 6 or reallocate

Current channels (directional)

• Paid social: efficient reach on LinkedIn; weak retargeting CTR (0.6%)
• Search: branded converting at 4.2%; non-brand CPCs rising 18% QoQ
• Email: 28% open, 2.8% click; weak lead-to-MQL timing (avg. 3.2 days)
• Website: 1.5% lead rate on key LPs; form drop-offs high on mobile
• Sales: strong SDR connect on event leads; inconsistent follow-up on demo no-shows

Selected bets

• Journey-sequenced creative refresh using existing assets
• Tight retargeting + content syndication for mid-funnel
• CRO fixes on top 3 LPs (no CMS change)
• Sales enablement for retargeting and webinar leads

Approval ask: Confirm priorities, channel roles, and 90-day spend within current envelope. Marketing ops owns execution; sales and CS are co-owners on shared milestones.

Executive language tip: Always pair a KPI with its business implication in one clause. Example: “LP CVR 1.5%→2.2% — same traffic, 47% more demos without additional media spend.” This is the only language that reliably gets plans approved.

---

Phase 2 — Rapid Journey Mapping with Available Signals

Time: ~2–3 hours | Day 1–2

Step 1: Pull fast signals from existing sources

You don’t need perfect data. You need directional signals from 5 sources:

• Web: Top pages, top sources, CVR, mobile vs. desktop split
• CRM: Lead sources, MQL→SQO rate, top reasons for loss
• Ads: Audience and placement metrics, CTR, cost per result
• Email: Open rate, click rate, average time from form submit to first response
• Sales and CS: 5 recent call notes each — what objections come up, what triggers purchase

Step 2: Define a 6-stage journey

Use these stage names as-is unless your organization has established alternatives:

Awareness → Consideration → Conversion → Onboarding → Expansion → Advocacy

Step 3: Map what currently touches each stage

For each stage, note: which channels are active, what content exists, and whether it’s producing results. Flag stages where two channels are competing for the same role — those need a lead/support assignment decision.

Step 4: Draft a journey snapshot with gaps

Example snapshot:

Stage	Current state	Gap
Awareness	LinkedIn reach strong	Weak brand search movement; no recall proxies
Consideration	Fragmented content, no sequencing	No retargeting or nurture coordination
Conversion	Form friction, inconsistent SDR follow-up	LP mobile speed; no standardized talk tracks
Onboarding	Emails exist	No in-app prompts; slow time-to-first-value
Expansion	CS-driven but unscalable	No lifecycle or usage-trigger automation
Advocacy	Informal only	No structured review or spotlight process

Step 5: Define minimal data additions for weeks 1–2

Don’t try to fix data infrastructure in parallel with strategy. Pick three things only:

• UTM governance (standardize source/medium naming)
• Lead source normalization in CRM (clean up “Other” and “Unknown”)
• Pre-post baselines for each stage KPI (capture now, before any changes)

---

Phase 3 — Channel Roles and Orchestration Framework

Time: ~2 hours | Day 2–3

Why channel role clarity matters

When every channel claims ownership of a journey stage, two things happen: duplicate messages reach the buyer at the wrong frequency, and internal teams argue about attribution instead of optimizing outcomes. Assigning lead and support roles forces a different question — “is our lead channel actually producing the stage outcome?” — which is answerable.

A note on “single owner” in complex organizations

This framework assigns one outcome owner per stage — the person accountable for whether the stage KPI moves. This is different from saying one person does all the work. In practice, Conversion may involve your web team (LP and form), your demand gen lead (traffic quality), and your SDR manager (follow-up speed). The outcome owner coordinates across those functions and escalates when dependencies block progress. If your organization genuinely cannot assign a single outcome owner to a stage, that’s a governance gap to flag explicitly in your exec deck — not something to paper over with “co-ownership” that diffuses accountability.

Channel Role-by-Mission Matrix

For each stage, define:

Field	Definition
Mission	The job to be done at this stage
Lead channels	Own the stage outcome
Support channels	Amplify or qualify, not own
Core tactics	What you will actually run (not aspire to run)
Content types	What the audience sees
Cadence	Frequency and timing
Outcome owner	Single person accountable for the stage KPI
Success proxy	The directional KPI you can track this week

Filled example — mid-stage B2B SaaS:

1. Awareness

• Mission: Generate qualified attention in ICP
• Lead: LinkedIn paid, PR mentions
• Support: Content SEO, partner co-marketing
• Tactics: 2-message creative set by segment, sponsored posts, earned quotes in industry media
• Content: Problem-framing short videos, 1-page POV documents
• Cadence: Weekly creative rotation; PR monthly
• Owner: Paid media manager
• Proxy: CPM under $35; brand search volume index up 10%

2. Consideration

• Mission: Move known accounts to active solution evaluation
• Lead: Retargeting, email nurture
• Support: Webinars, content syndication
• Tactics: 3-step retargeting sequence by site depth; 4-touch nurture stream
• Content: Comparison guides, customer case snippets, live demo invites
• Cadence: Retargeting 7–14 day window; nurture weekly
• Owner: Lifecycle manager
• Proxy: Retargeting CTR above 0.9%; content-assisted MQLs week-over-week

3. Conversion

• Mission: Book qualified demos and progress to sales-qualified opportunity
• Lead: Website (LP + form), SDR follow-up
• Support: High-intent search, email nudges for demo no-shows
• Tactics: LP simplification (form fields 7→4), sticky CTA, 2-step form, 24-hour SDR SLA
• Content: ROI calculator, product walkthrough video (under 3 minutes)
• Cadence: Always-on
• Owner: Demand gen lead (coordinates with web and SDR manager)
• Proxy: LP CVR; demo-to-SQO rate

4. Onboarding

• Mission: Reach time-to-value quickly; prevent early churn
• Lead: CS email, in-app prompts
• Support: Tutorial content library
• Tactics: 3-step activation email sequence; in-app onboarding checklist
• Content: 90-second how-to videos; quick-start PDF
• Cadence: Day 0, 3, 7 post-signup
• Owner: CS operations
• Proxy: Day-14 activation rate; in-app checklist completion rate

5. Expansion

• Mission: Identify and convert upsell and cross-sell signals before they go cold
• Lead: CS + lifecycle email
• Support: In-app usage-threshold triggers
• Tactics: Usage milestone alerts routed to CS; automated feature nudge when usage threshold crossed
• Content: Feature mini-demos; ROI case snippets by customer segment
• Cadence: Weekly CS review of usage alerts
• Owner: Revenue ops
• Proxy: Expansion pipeline created; usage milestone alerts triggered

6. Advocacy

• Mission: Generate social proof at scale without manual CS effort
• Lead: CS
• Support: Marketing community management
• Tactics: Automated review request after activation milestone; monthly customer spotlight cadence
• Content: G2/Capterra review prompts; 45-second customer clip
• Cadence: Monthly
• Owner: CS lead
• Proxy: New reviews published; case study pipeline count

Conflict resolution rule: If two teams both claim the lead role for a stage, reassign by outcome accountability — not by who does the most work or who spent the most. One outcome owner per stage. If the conflict can’t be resolved in the planning week, flag it explicitly in the deck and name a temporary owner for the 90-day period.

---

Phase 4 — Prioritize Initiatives and Build the 90-Day Rollout

Time: ~2–3 hours | Day 3–4

Build a constraints-first backlog

Only include items that can be executed on your current stack and budget. This is not a wish list — it’s a delivery commitment.

Eligible initiative types:

• Creative refresh using existing footage and assets
• UTM governance and tracking normalization
• Landing page form field reduction or CTA repositioning (no CMS migration)
• Retargeting audience restructure
• Email nurture sequencing (4–6 touches)
• SDR talk tracks and follow-up cadences
• Webinar cadence using current webinar tool
• Partner co-marketing using existing relationships

Ineligible for the 90-day window:

• Any new platform or tool procurement
• Net-new content production requiring new budget
• Attribution infrastructure overhaul
• Headcount additions

Score each initiative (1–5 per dimension)

Dimension	What to score
Impact	Expected lift on the single stage KPI this initiative targets
Confidence	Quality of evidence — do you have data showing this lever works in your context?
Ease	Inversely scored: fewer dependencies and less effort = higher score

Pick the top 5–7 items by total score. Below 5 leaves capacity on the table. Above 7 creates dependency risk and increases the chance of shipping nothing well.

Check creative team capacity before you brief anything

“No external production budget” does not mean zero creative work. Recutting video, rewriting ad copy, and refreshing LP headlines still consume designer and copywriter hours — often from people already carrying other KPIs. Before briefing any creative initiative, run a quick capacity check with your content lead:

Question	If the answer is a problem
How many hours per week does the designer have available for this project?	If under 4 hours/week, creative refresh cannot run in parallel with existing commitments — sequence it after week 2
Is the copywriter mid-campaign on anything with a fixed deadline in weeks 1–3?	If yes, assign creative refresh to a second writer or reduce the number of ad variants from 4 to 2
Are brand guidelines and approved asset libraries accessible in one shared folder?	If no, add half a day to organize this before briefing begins — briefs sent without a clear asset reference waste revision cycles
Who has final approval on creative output?	If the approval chain has more than 2 steps, add 2–3 buffer days to every creative milestone in the swimlane

The most common reason week 1–2 deliverables slip is not budget or strategy — it’s that the creative team was already at capacity before the plan started.

Preventing scope creep in creative work

“Creative refresh using existing assets” is the most common place scope creeps from “recut existing video” to “produce 6 new hero videos.” Prevent this with one explicit rule: any initiative that requires new production budget or more than 2 days of creative lead time moves off the 90-day list. Put it in the next-quarter backlog instead.

Managing SDR capacity when omnichannel starts working

When paid, email, and CRM are sequenced properly, inbound lead volume often spikes in weeks 3–4 — sometimes by 30–50% above baseline. If your SDR team is sized for current volume, this creates a quality problem: response times lengthen, follow-up becomes inconsistent, and conversion rates drop even as MQL volume rises.

Plan for this before launch:

• Trigger rule: If weekly MQL volume exceeds baseline by more than 30%, activate automated round-robin lead assignment in CRM (most CRMs support this natively)
• Lead scoring buffer: Work with Sales Ops to add a minimum PQL/MQL score threshold for SDR routing — so lower-quality leads enter a nurture sequence rather than the SDR queue
• No-show recovery: Build a dedicated 2-touch email + retargeting sequence for demo no-shows before SDRs attempt manual re-outreach — this handles volume automatically without additional SDR time

Lock the MQL definition before the round-robin triggers

The SDR capacity plan above only works if Marketing and Sales agree on what constitutes a qualified lead worth calling. This sounds obvious — and it’s almost always missing. If “MQL” in your CRM means different things to your lifecycle manager and your SDR manager, the round-robin trigger will route low-quality leads to SDRs at exactly the moment volume is highest, destroying the conversion rate you’re trying to protect.

Use one of the three alignment sessions this week to align on a single written MQL definition. It needs three components:

Component	Example	Who confirms
Firmographic fit	Company 50–500 employees, industry in ICP list, HQ in target region	Marketing and Sales both sign off
Behavioral signal	Minimum 2 content interactions OR 1 high-intent page (pricing, demo, comparison) in the last 30 days	Marketing defines; Sales validates against closed-won behavior
Contactability requirement	Valid work email confirmed; job title matches a buying role	Sales Ops enforces in CRM routing rules

Once the definition is written, add it as a routing condition in your CRM so that leads meeting all three components go to SDR queue, and leads meeting only one or two enter an automated nurture sequence instead.

Document this in your exec deck. Add one sentence on the “Owners and Governance” slide: “MQL definition confirmed with Sales on [date]. Any change requires joint sign-off from Marketing and Sales Ops.” This prevents the definition from drifting when a new SDR manager joins or a new campaign changes lead volume patterns.

Brand safety checklist for reused assets

When refreshing or repurposing existing creative to meet timeline constraints, run this check before any asset goes live:

• [ ] Does the asset reference a pricing tier, promotion, or offer that has changed or expired?
• [ ] Does the asset reference a product feature, integration, or capability that has been updated, renamed, or deprecated?
• [ ] Does the asset reference a competitor positioning that may have changed (acquisitions, product pivots)?
• [ ] Does the asset include customer logos, quotes, or data that require re-confirmation of permissions?
• [ ] Does the asset reference a team member, spokesperson, or partner who is no longer affiliated?

One person should own this review per asset type. Add it as a gate in your creative brief before assets go to the media team.

90-Day Rollout Swimlane

Tracks: Planning & Ops | Creative & Content | Paid & Organic | Email & Lifecycle | Web & CRO | Sales Enablement | Analytics & Reporting

Weeks 1–2: Lock and brief

Track	Deliverable	Owner
Planning & Ops	Message map, UTM governance doc, KPI baselines captured	MOps lead
Creative & Content	Brief creative refresh sets using existing assets; brand safety review complete	Content lead
Paid & Organic	Rebuild retargeting audiences and 3-tier sequence by site depth	Paid media manager
Email & Lifecycle	Blueprint 4-touch nurture stream; wireframes approved	Lifecycle manager
Web & CRO	Identify top 3 LP issues; implement quick wins (form field reduction, CTA repositioning)	Web lead
Sales Enablement	Draft 2 SDR talk tracks and 3 follow-up email templates for hand-raisers	SDR manager
Analytics	Set pre-post baselines; design holdout group for retargeting (see Phase 5)	Analyst

⚠️ Early warning checkpoint — end of week 2: If you have no live changes in at least paid, email, or landing pages by end of week 2, you are off track. Cut the lowest-scored backlog item and ship the top 3 immediately. A partial rollout on schedule is more valuable than a complete rollout late.

Weeks 3–4: Launch v1

• Creative refresh and retargeting v1 live
• Nurture v1 and LP fixes v1 shipped
• SDR enablement session held; talk tracks in field
• Monthly webinar and partner co-marketing slot confirmed

Weeks 5–8: Iterate and segment

• Creative v2 from week 4 signals
• CRO v2: form microcopy and page speed improvements
• Nurture segmentation added (at minimum: by ICP segment or lead source)
• First holdout readout; budget reallocation decision made
• SDR capacity check: if MQL volume has grown >30%, activate round-robin routing

Weeks 9–12: Expand and report

• Expansion triggers live
• One case study published (customer selected by week 4)
• Webinar cadence at steady-state
• KPI checkpoint and next-quarter brief prepared

---

Phase 5 — Set Pragmatic KPIs, Baselines, and Proxy Measurement

Time: ~90 minutes | Day 4

Why proxy KPIs exist

Perfect attribution across six journey stages requires infrastructure most teams don’t have. Proxy KPIs are not a compromise — they’re an honest acknowledgment that directional signals, tracked consistently over time, are sufficient to make good reallocation decisions. The goal is not to measure everything precisely; it’s to catch problems early and confirm that interventions are moving the right numbers.

Primary and Proxy KPI Map

Awareness

• Primary KPI: Brand search volume index (Google Trends, normalized to 100 at baseline)
• Proxy KPI: LinkedIn reach CPM
• Target direction: Index 100→115 in 90 days; CPM under $35
• Source and cadence: Google Trends weekly; LinkedIn Ads weekly
• Business implication: Rising brand demand lowers blended CAC by reducing the portion of the funnel requiring paid acquisition

Consideration

• Primary KPI: Content-assisted MQLs (contacts with 2+ content interactions before MQL date)
• Proxy KPI: Retargeting CTR
• Target direction: Content-assisted MQLs up from baseline; retargeting CTR 0.6%→0.9%
• Source and cadence: CRM attribution notes weekly; ad platform weekly
• Business implication: MQLs educated by content before sales contact convert to SQO at higher rates and shorter cycle lengths

Conversion

• Primary KPI: Demo-to-SQO conversion rate
• Proxy KPI: LP conversion rate
• Target direction: Directional improvement from current baseline (set your own target based on historical variance)
• Source and cadence: CRM and GA4 weekly
• Business implication: Conversion rate improvement generates more revenue from the same media spend — no CAC increase required

Onboarding

• Primary KPI: Day-14 activation rate
• Proxy KPI: In-app onboarding checklist completion rate
• Target direction: Directional lift from current baseline
• Source and cadence: Product analytics weekly
• Business implication: Faster time-to-value is the strongest predictor of 90-day retention in most SaaS products

Expansion

• Primary KPI: Expansion pipeline created (value of expansion opportunities opened in period)
• Proxy KPI: Usage milestone alerts triggered and routed to CS
• Target direction: Increase from current baseline
• Source and cadence: CRM and product analytics biweekly
• Business implication: Expansion revenue drives NRR above 100% without incremental CAC

Designing a Useful Holdout Test

Holdout tests are mentioned frequently in marketing plans but rarely set up correctly, which produces results that can’t be trusted. Here is a practical minimum viable holdout design for a retargeting or nurture experiment:

What a holdout test does: Randomly withholds the intervention (retargeting ad or nurture email) from a portion of the eligible audience, then compares conversion rates between the exposed group and the withheld group. If exposed converts at a higher rate, you have evidence the intervention is working — not just that the pipeline environment improved.

Minimum requirements for a valid holdout:

Parameter	Minimum requirement	Why
Holdout group size	15–20% of eligible audience	Smaller groups produce underpowered results
Test duration	Minimum 3 weeks; 4–6 weeks preferred	Short windows miss weekly and seasonal variance
Sample size per group	At least 200 conversions in the exposed group before reading results	Below this, conversion rate differences are not statistically meaningful
Assignment method	Random at the contact or cookie level — not by week or geography	Non-random assignment introduces confounding factors
What to measure	Stage conversion rate (e.g., retargeting audience → demo request), not click-through rate	CTR is a proxy for engagement, not conversion

Practical shortcut if sample sizes are too small: Run a pre-post comparison instead. Capture the stage KPI baseline for 3–4 weeks before launch, then track the same KPI for 3–4 weeks after launch. Pre-post is less rigorous than a holdout but more honest than no measurement at all — as long as you flag that other variables may have changed in the same window.

Guidance by business type:

Business type	Recommended approach	Why
B2B high-ticket / low-volume (under 50 demos per month)	Pre-post only — do not attempt a holdout	You won’t reach 200 conversions in the exposed group within 90 days. A holdout with 20 conversions per arm produces noise, not signal. Pre-post with honest caveats is more credible.
B2B mid-market (50–300 demos per month)	Pre-post for weeks 1–6; attempt a holdout in weeks 7–12 once volume is confirmed	By week 6 you’ll know if volume is sufficient for a holdout to be meaningful
B2C or high-volume B2B (300+ target actions per month)	Holdout from week 1	Volume supports statistically meaningful results within the 90-day window

For B2B high-ticket teams: The most important measurement investment is not holdout design — it’s ensuring your CRM captures the source and content interaction history for every closed-won deal. Over two or three quarters, this builds a body of evidence linking content touchpoints to revenue that no 90-day holdout can replicate.

Measurement guardrails

• Use blended CAC and pre-post comparisons for budget reallocation decisions — not last-click CPA alone
• Normalize lead source names in CRM before week 2. If “Other” accounts for more than 15% of your lead source field, your weekly readouts will be unreliable
• Flag explicitly in your exec deck which KPIs are directly measured vs. estimated via proxy — executives who later discover a “KPI” was a proxy without disclosure lose trust in the measurement system

---

Phase 6 — Assemble the Executive Deck and Approval Narrative

Time: ~3–4 hours | Day 5–6

The 12–15 Slide Structure

Slide	Content	Length
1	Title and context: quarter, objective, planning approach	1 visual
2–3	Objectives and constraints you are honoring	1 slide each
4	Current performance snapshot — 5 bullets max	1 slide
5	Journey map with 6 stages and gap summary	Simple visual
6	Channel roles by stage — lead vs. support table	1 slide
7	Prioritized initiatives and ICE rationale	Top 5–7 items
8	90-day rollout swimlane — key milestones only	4 checkpoints
9	KPIs and proxy measurement with baselines	Primary + proxy per stage
10	Budget within envelope — allocation and reallocation trigger rules	1 slide
11	Risks and mitigations	3 bullets max
12	Business impact translation	Pipeline, CAC, activation, NRR
13	Owners and governance — weekly review cadence	1 slide
14	Approval ask — what you need today, in one sentence	1 slide
15 (appendix)	Detailed KPI notes, holdout design, data source map	Reference only

Copy-Ready Slide Text Snippets

Objectives slide:

Add $3.2M qualified pipeline and lift onboarding activation from 48% to 56% using existing budget, tools, and team capacity.

Constraints slide:

Ship visible value by week 4. No replatforming. No new headcount. No budget increase. Every initiative fits inside the current $140K envelope.

Business impact slide (translate KPIs to revenue):

If LP CVR moves from 1.5% to 2.2%, same traffic yields 47% more demos — improving pipeline without additional media spend. If day-14 activation improves 8 percentage points, 90-day retention historically improves 12–15 points, reducing churn cost by an estimated $X per cohort.

Approval ask slide:

Approve: 90-day plan and 5–7 prioritized initiatives; KPI targets and weekly readout cadence; budget allocation within current $140K envelope; named owners for each track. Written confirmation needed from Marketing, Sales, and CS leads.

Approval Narrative Checklist

Before sending for executive review, confirm:

• [ ] You open with constraints you are honoring — this builds trust before you make any asks
• [ ] Every initiative ties to one KPI and one business lever
• [ ] First visible value appears by week 2; a formal checkpoint by week 6
• [ ] Weekly decision ownership is named (who reallocates budget, who cuts an initiative)
• [ ] Benchmark numbers in examples are labeled as illustrative, with actual baselines shown separately
• [ ] Holdout test design is documented in the appendix for any executive who asks how you’ll prove incrementality

Decision-Readiness Criteria

The plan is approved when you receive written confirmation of:

• The 90-day plan and which initiatives are in scope
• KPI targets and readout day/cadence
• Budget allocation within the current envelope
• Named owners for each track with manager-level acknowledgment

Early warning: If budget questions dominate the review and KPI-to-revenue links are unclear, add one slide showing pipeline math. Example: “KPI lift × weekly volume × ASP × close rate = estimated pipeline impact.” Even a rough estimate shifts the conversation from “is this worth spending on” to “how do we make this succeed.”

Failure mode to avoid: The deck avoids replatforming but proposes creative or content scope that implicitly requires new production budget not in the envelope. Fix by replacing those initiatives with tactics that use existing assets, partner co-marketing credits, or CRM workflow changes — and restate budget neutrality explicitly on the budget slide.

---

Working Files and Tools

Deliverable	Recommended tool
Executive deck	Google Slides or PowerPoint (16:9 clean template)
Journey map and swimlane diagram	draw.io, Miro, or Figma
Weekly KPI tracking	Google Sheets with weekly snapshots from GA4, ad platforms, and CRM
Asset library and brand safety review	Shared folder with approved footage, current brand guidelines, and offer status sheet
CRM lead source normalization	Native CRM field mapping or a simple lookup table in Sheets

---

Common Mistakes That Derail Approval or Execution

• Initiatives without a single owner — “Marketing” is not an owner. Name a person.
• KPIs without a readout source and day — If you can’t tell an executive exactly when and where a KPI will be visible, they can’t hold anyone accountable.
• Creative refresh that becomes net-new production — Lock the asset-sweating rule in the brief before any creative work begins.
• Briefing creative without a capacity check — “Existing assets only” still costs designer and copywriter hours. Confirm availability before briefing, not after.
• Holdout tests with no sample size check — Running a holdout with 40 conversions per arm produces noise, not signal. Match test design to your actual volume.
• Benchmark numbers presented as targets — Replace every example figure with your own baseline before the deck goes to executives.
• “Co-ownership” of stage outcomes — Shared accountability is diffused accountability. Name one outcome owner per stage, even if it’s uncomfortable.
• Activating SDR round-robin before MQL definition is aligned — Routing more leads to SDRs without a shared definition of “qualified” degrades response quality at exactly the moment volume is highest.

---

Conclusion

This playbook gives you a constraints-first omnichannel strategy that leadership can approve because it works within what already exists — no new platforms, no budget increases, no headcount adds. The channel role framework eliminates internal overlap and attribution debates. The pragmatic KPI design gives you directional signals you can act on without waiting for perfect infrastructure.

Budget 8–10 days if data isn’t already clean. Build in week to 90-day execution. When anything wobbles — an SDR SLA slips, a creative refresh expands into production, a KPI has no source — return to the constraints and the approval criteria. Those are the guardrails that keep the plan executable.

A stage-based, attribution-agnostic system for diagnosing leaks, aligning budgets, and running a prioritized 90-day experiment backlog — designed for marketing leaders at companies with an operational data foundation.

---

On timing and scope: The original framing of “48 hours” is aspirational and worth clarifying upfront. Building the framework document — stage definitions, KPI map, leak diagnostics, and backlog — can be completed in roughly a week if your GA4 and CRM data are already clean. But operating the framework — running experiments, hitting stage KPIs, iterating on budget splits — is a full quarter of cross-functional work involving marketing, sales, CS, and finance. Use this guide as a blueprint to build in a week and operate over a quarter, not as a two-day sprint to completion.

On data prerequisites: This framework assumes GA4 event tracking is set up and verified, CRM lifecycle stages are defined with timestamps and owners, and GA4 and CRM data can be joined at least at the URL/campaign level. If you’re missing any of these, budget time to address them first — the leak diagnostics in Phase 3 are only as reliable as the data feeding them.

---

What You’ll Produce

By the end of this framework, you’ll have:

• A universal funnel model with stage names, entry/exit rules, and data field references everyone accepts
• A KPI and guardrail map per stage that prevents teams from gaming individual metrics
• A leak diagnostic checklist for GA4 and CRM you can run in under 90 minutes
• A tactics library matched to leak patterns and sorted by engineering lift
• Budget split benchmarks tied to company maturity archetypes with trigger conditions to switch between them
• A 90-day experiment backlog scored by RICE/ICE and sized to actual team capacity
• An attribution-agnostic measurement cadence and agency evaluation scorecard ready for procurement

---

Tool and Infrastructure Requirements

Before starting, confirm you have access to all of the following:

Tool / System	Used for	What “ready” means
GA4	Awareness and Engagement diagnostics, funnel exploration, cohort analysis	Conversions marked, enhanced measurement on, UTMs standardized
CRM (HubSpot, Salesforce, etc.)	Consideration through Retention stages, pipeline velocity, SLA tracking	Lifecycle stages defined with timestamps; MQL/SQL rules documented
Paid channel dashboards	Reach, frequency, creative fatigue diagnosis	Campaign UTMs consistent with GA4 source/medium conventions
Product analytics (if PLG)	PQL scoring, activation events, retention cohorts	Key activation events instrumented and mapped to CRM contacts
Budget tracker	Stage-level spend allocation	Last 90 days of spend by channel available

If you’re missing pieces: Run the framework against the data you have and clearly label which inputs are estimated vs. measured in your sign-off deck. Estimated inputs are acceptable in a first pass — what matters is that you know which numbers to trust and which to validate over the first 30 days.

---

Phase 1 — Define the Universal Funnel Model and Stage Boundaries

Time: ~90 minutes

Why stage boundaries matter

Without explicit entry and exit rules tied to real data fields, every pipeline review turns into a debate about what “qualified” means. Stage names that everyone accepts — paired with the precise data rule that moves someone in or out — eliminate that debate before it starts.

The Five-Stage Model

Awareness — People in your ICP who have seen or discovered you

• Entry: First impression or first non-paid session in GA4 from ICP regions or target lists
• Exit: First qualified engagement event or repeat session within 14 days
• Unit of analysis: User
• Primary data source: GA4 events first_visit, session_engaged

Engagement — People who meaningfully interact but haven’t raised their hand yet

• Entry: Engaged session in GA4, content downloads, 2+ product pages viewed, 50% video completion, webinar registration
• Exit: Hand-raise or lead captured with contactability
• Unit: User
• Primary data source: GA4 events, CRM form submissions

Consideration — Known leads or accounts showing intent but not yet sales-qualified

• Entry: Lead in CRM with complete contactability, meets ICP basics; or product signup for PLG
• Exit: Becomes SQL or PQL via BANT-like scoring, or is disqualified
• Unit: Contact or account (see boundary note below)
• Primary data source: CRM lifecycle stage, PQL score

Conversion — Sales-qualified leads through to closed-won

• Entry: SQL or PQL accepted by sales with a dated meeting, or opportunity created
• Exit: Closed-won or closed-lost
• Unit: Opportunity
• Primary data source: CRM opportunity stage

Retention and Expansion — Onboarded customers through renewal and upsell

• Entry: First value achieved or onboarding completed event; subscription active
• Exit: Renewal, churn, downgrade, or expansion
• Unit: Account
• Primary data source: Product analytics, billing system

Boundary Decisions to Document Once

Unit of analysis: If sales is account-based, treat Consideration and Conversion at the account level in CRM reports and deduplicate contacts from the same account.

Time windows: Fix a standard lookback for Awareness and Engagement — typically 30 or 90 days — so top-of-funnel rates are stable week to week and comparable across periods.

PLG coexistence: If you have both a sales motion and a self-serve trial, treat product signup as Consideration entry and PQL as Conversion entry. Do not double-count a signup as both Engagement exit and Consideration entry — this inflates top-of-funnel volume and distorts stage conversion rates.

The PLG + Sales-Led complexity note: Managing both motions in the same funnel is more operationally complex than a single boundary note conveys. In practice, you need separate PQL and MQL pipelines that converge at the Opportunity stage, separate SDR routing rules for each, and a deduplication rule for contacts who come in through both paths simultaneously. If you’re running both motions, plan an additional 1–2 days to document the routing logic before socializing the funnel model.

Content syndication leads: Only advance to Consideration if contactability and consent exist in CRM. Otherwise, keep in Engagement and run nurture sequences before handing off to SDRs.

Handling stale leads (dwell time rule): A lead that stays in Consideration for more than 30 days without progressing — no meeting booked, no meaningful engagement, no disqualification — should be automatically moved back to Engagement for re-nurture. This prevents SDR lists from becoming cluttered with contacts who are no longer actively evaluating, which inflates pipeline coverage numbers and dilutes follow-up quality. Build this as an automated workflow in your CRM: if Days in Consideration > 30 and Last Activity = null, move lifecycle stage to Engaged and enroll in a re-engagement sequence.

Stage Template (paste into your deck)

Field	Definition
Stage name
Entry rule (data field and condition)
Exit rule (data field and condition)
Unit of analysis
Primary data source and field name
SLA owner

Filled example — B2B SaaS, mid-market, sales-led with PLG assist:

Stage	Entry	Exit	Unit	Source	Owner
Awareness	GA4 first_visit from US/UK/DACH ICP audiences	Engaged session or content download within 14 days	User	GA4	Performance
Engagement	engaged_session or 2+ high-intent pages, or webinar registration	Form submit, chatbot MQL, or product signup	User	GA4, HubSpot	Growth
Consideration	New HubSpot lead: work email + company 50–500 employees, or verified product signup	SQL accepted by AE or PQL score ≥ 80; or no activity in 30 days → back to Engagement	Contact or account	HubSpot lifecycle	Demand Gen / PLG
Conversion	Opportunity created or meeting held	Closed-won or closed-lost	Opportunity	Salesforce	Sales
Retention	First value event in product or onboarding completed	Renewal, expansion, churn, or downgrade	Account	Product analytics, billing	CS

---

Phase 2 — Map KPIs and Guardrails to Each Stage

Time: ~60–90 minutes

Why guardrails matter as much as KPIs

If you only track KPIs, teams will optimize for the number at the expense of quality. The guardrail principle is simple: if a KPI rises while its guardrail falls, treat it as a quality cannibalization signal and pause scaling until the guardrail recovers. Every KPI owner should also own the guardrail sitting next to their metric.

Stage KPI Map

Awareness

• Primary KPIs: Unique reach within ICP, new non-brand sessions
• Guardrails: Brand search share (floor: don’t let brand clicks fall below 25% of total search clicks), viewable CPM, ad frequency capping (cap at 6 impressions per user per week), share of voice vs. category
• Data: GA4 acquisition report, paid platform reach dashboards, Google Trends for brand

Engagement

• Primary KPIs: Engaged sessions, content completion rate on top 5 assets, CTR to lead capture
• Guardrails: Bounce rate on top 10 landing pages (threshold: under 55%), average LCP under 3.0s on paid landing pages, creative fatigue signal (CTR trend declining with frequency above 5)
• Data: GA4 engagement, PageSpeed Insights, paid platform diagnostics

Consideration

• Primary KPIs: MQL volume and ICP quality rate, PQL volume, demo-request conversion rate
• Guardrails: Lead contactability rate (threshold: above 95%), ICP fit percentage, SDR first-touch SLA adherence (first contact within 15 minutes for hand-raisers), dwell time in stage (flag if >30 days without progression)
• Data: CRM lead fields and scoring, SDR activity logs

Conversion

• Primary KPIs: MQL to SQL rate, PQL to Opportunity rate, Opportunity win rate, average sales cycle length
• Guardrails: Average discount rate (threshold: below 12%), pipeline coverage ratio, demo no-show rate (threshold: below 18%)
• Data: CRM stage conversion reports, meeting records

Retention and Expansion

• Primary KPIs: 30-day activation rate, 90-day logo retention, gross revenue retention (GRR), net revenue retention (NRR)
• Guardrails: Support first response time (threshold: under 2 hours), NPS/CSAT trend direction, expansion offer coverage (all healthy accounts offered expansion by day 45)
• Data: Product analytics, billing system, CS platform

A Note on Benchmark Numbers

The filled examples in this framework use concrete numbers (MQL→SQL at 30%, win rate at 24%, NRR at 108%) to make the model legible. These are illustrative, not industry benchmarks. Actual conversion rates vary significantly by:

• Average Contract Value (ACV): Higher ACV deals have longer cycles and lower volume conversion rates
• Go-to-market motion: PLG products typically see higher MQL volume but lower SQL rates than sales-led motions at the same revenue level
• Market category maturity: Categories with established buying committees (ITSM, HR Tech) convert differently from emerging categories where buyers are still defining their purchase criteria
• Team size and SDR coverage: Stage conversion rates degrade predictably when SDR capacity is mismatched to inbound volume

Use your own baseline numbers — even if imperfect — rather than adapting these examples directly. The structure of the KPI map matters more than any specific number.

---

Phase 3 — Diagnose Funnel Leaks with GA4 and CRM

Time: ~90 minutes total

On data discrepancy between GA4 and CRM

Before running diagnostics, set a standing expectation: GA4 user/session counts and CRM lead/contact counts will not match, and that’s expected. Reasons include cookie refusals, ad blockers, cross-device sessions not stitched, and form submissions from users without a prior GA4 session. A 10–15% discrepancy between the two systems is normal and not worth investigating. What matters is that conversion rates and trends are directionally consistent across both systems. Focus your diagnostic energy on trendlines, not on reconciling individual records.

GA4 Checklist — 30 minutes

Admin sanity check (5 minutes)

• Confirm high-intent conversions are marked and deduplicated: hand-raiser forms, demo requests, and signup events must each be a single conversion event — not counted twice via both a form submit and a page view
• Confirm enhanced measurement is on: page_view, scroll, outbound_click should be flowing
• Spot-check UTM classification: pull the Traffic Acquisition report and confirm your paid channels appear under their correct default channel groupings, not misclassified as Direct or Organic

Reports to run (20 minutes)

• User Acquisition and Traffic Acquisition: Split by default channel grouping and campaign. Export new users, engaged sessions, and engaged session rate.
• Pages and Screens: Top 10 landing pages by sessions, with bounce rate and average engagement time.
• Funnel Exploration: Define steps — session_start → engaged_session → form_submit or signup → purchase or paid event. Pull completion rates and drop-off percentages at each step.
• Cohort Exploration: Users who completed signup in a given week, retained at 7, 30, and 60 days.

Quick diagnostics (5 minutes)

• Creative fatigue signal: CTR declining while frequency exceeds 5 in paid social campaigns
• Page speed: cross-check GA4 average engagement time against PageSpeed Insights for LCP and CLS on your top paid landing pages

CRM Checklist — 45 minutes

• Lifecycle conversion report: Lead → MQL → SQL → Opportunity → Won. Export stage-to-stage conversion rates and average time in each stage.
• Pipeline velocity: Average days from MQL to SQL, SQL to Opportunity, Opportunity to Won. Identify the stage with the longest average dwell time — this is where to start.
• Contactability and ICP fit audit: What percentage of leads have valid work email, phone, and ICP fields populated? Below 90% signals a lead quality or form strategy problem.
• SLA adherence: Distribution of SDR first-touch time. What share of hand-raisers were contacted within your SLA window?
• Dwell time distribution: How many leads have been in Consideration for more than 30 days? This is your re-nurture backlog.
• Retention cohorts: Accounts onboarded in a given month, activation rate by day 7 and 30, renewal status.

Leak Signature Reference

Symptom	Stage	Likely cause
Low engaged session rate on paid landing pages	Engagement	Message mismatch between ad and LP, or page speed issue
High MQL volume but MQL→SQL dropping	Consideration	Lead quality degradation or SDR SLA failure
Strong PQL volume but low Opportunity creation	Consideration → Conversion	PQL scoring threshold misaligned with AE bandwidth or deal criteria
Flat 30-day activation despite heavy retargeting spend	Retention	Onboarding friction — retargeting is masking rather than fixing the problem
Large dwell time backlog in Consideration	Consideration	No re-nurture workflow, SDR capacity insufficient for inbound volume

---

Phase 4 — Tactics Library by Stage, Matched to Leak Patterns

Time: ~60 minutes to select and assign

Match the tactic to the diagnosed leak. Prioritize low-engineering-lift options first — experiments blocked by dev dependencies consistently slip past 90-day windows.

Awareness — Leaks: Low qualified reach, over-reliance on brand

Low-lift:

• Paid social reach campaigns with ICP filters and creative that mirrors your highest-converting BOFU messaging
• Partner newsletter swaps and podcast mid-rolls targeting ICP titles and seniority levels
• PR-lite: data-driven byline article using internal benchmarks, distributed via employee LinkedIn + targeted paid amplification

When not to use: If win rates are declining or sales capacity is constrained, cap Awareness spend and fix MOFU first. Driving more top-of-funnel volume into a broken middle funnel accelerates waste.

Engagement — Leaks: Poor CTR or high bounce on landing pages

Low-lift:

• Message match: align ad headline directly to LP H1 and first CTA above the fold
• Page speed fixes using no-code editors: compress hero images, defer non-critical scripts, move primary CTA above fold
• Content recap: add a 2-minute executive summary at the top of long-form assets to reduce exit rate for time-constrained readers

Medium lift:

• Multi-variant creative refresh cadence every 2 weeks using a standardized creative naming convention tied to your UTM structure

When not to use: If lead contactability is broken, do not drive more traffic until the form and routing logic is fixed.

Consideration — Leaks: MQL quality problems or hand-raiser friction

Low-lift:

• Shorten forms to email + company domain only; enrich fields server-side using Clearbit or native CRM enrichment tools
• Auto-book demo: embed a Calendly or Chili Piper round-robin scheduler on the thank-you page — eliminates the SDR scheduling step for motivated hand-raisers
• SDR sequence templates tied to the specific asset downloaded, with Day 0, 1, 3, 7 touchpoints
• PQL scoring audit: add the 3–5 in-product events that most correlate with Opportunity creation to your scoring model

Medium lift:

• Conversational capture: deploy a chatbot on high-intent pages with 3 qualifying questions that route leads to the right follow-up path

When not to use: If SDRs cannot uphold follow-up SLAs at current volume, do not run Consideration tactics to increase MQL volume. Fix capacity and routing first — adding leads to a constrained SDR team lengthens response time and drops conversion rates further.

Conversion — Leaks: Low SQL-to-Opportunity or Opportunity-to-Won rates

Low-lift:

• Competitive one-pagers and ROI calculators — gated for sales use, mapped to the top 3 objections in your lost-deal analysis
• Mutual action plan templates in CRM, shared with the buyer at opportunity creation
• Social proof injection: dynamic customer logo strips segmented by buyer industry or company size on pricing and demo pages

Medium lift:

• Pilot offer design: a 30-day paid pilot with a clearly defined success metric and explicit exit criteria, reducing buyer risk in late-stage deals

When not to use: If discounts are inflating closed-won rates while NRR is declining, shift budget to value proof tactics rather than pricing flexibility.

Retention and Expansion — Leaks: Weak activation or low 30-day retention

Low-lift:

• Onboarding email sequence with Day 0, 1, 3, 7 nudges and a matching in-app checklist
• Lifecycle trigger-based messaging for dormant users, segmented by role (end user vs. administrator vs. economic buyer)
• QBR template and account health scoring visible to CS — standardizes what “at-risk” means and when to escalate

Medium lift:

• Customer marketing: user group webinars, product release notes with in-app tooltips for newly relevant features

When not to use: If product telemetry is unreliable or not yet instrumented, start with CS-run playbooks you can operate manually. Don’t wait for perfect data instrumentation before addressing activation.

---

Phase 5 — Budget Split Benchmarks by Maturity Archetype

Time: ~45 minutes to select and document your current archetype

Why archetypes, not fixed percentages

A single budget split formula fails most companies because CAC/LTV ratios, win rates, and funnel efficiency change significantly across growth stages. The three archetypes below represent distinct operating states — with specific trigger conditions for moving between them.

Archetype 1 — Early Traction: Seeking Fit or Entering a New Segment

When you’re here: Win rate below 20%, sales cycle inconsistent, NRR below 100%, or LTV/CAC below 3x. You’re still learning which messages convert which segments.

Stage	Budget split
Awareness	35–45%
Engagement	15–20%
Consideration	15–20%
Conversion	10–15%
Retention and Expansion	10–15%

Channel notes: Heavier paid social prospecting and partner reach to generate signal. Maintain minimum viable lifecycle budget for onboarding — even at this stage, poor activation destroys unit economics.

Trigger to move to Archetype 2: Win rate exceeds 20% for two consecutive quarters, NRR reaches 100%+, and you can articulate a repeatable ICP.

Archetype 2 — Scaling: Proven CAC/LTV and Stable Win Rates

When you’re here: CAC payback under 18 months, win rate 20–30%, NRR above 100%, and pipeline coverage is 3x or better. You know what works — now scale it.

Stage	Budget split
Awareness	20–30%
Engagement	15–20%
Consideration	20–25%
Conversion	15–20%
Retention and Expansion	10–15%

Channel notes: Increase high-intent capture and sales enablement. Keep brand awareness active but cap frequency — you’re no longer buying reach for learning, you’re protecting an established position.

Trigger to move to Archetype 3: Non-brand organic traffic growth slows, incremental CAC rises quarter-over-quarter, or NRR exceeds 110% (expansion is outpacing acquisition as a growth lever).

Archetype 3 — Efficiency and Retention: Tight Markets or Mature Growth

When you’re here: Market is saturated or competitive, incremental CAC is rising, NRR is above 110%, and expansion revenue is a meaningful portion of new ARR. Protecting and growing existing customers is your highest-ROI lever.

Stage	Budget split
Awareness	10–20%
Engagement	10–15%
Consideration	20–25%
Conversion	15–20%
Retention and Expansion	25–35%

Channel notes: Reinvest in lifecycle, onboarding improvement, and customer marketing programs. Cap prospecting spend to maintain brand search floor — don’t let brand share erode while over-investing in expansion.

Trigger to reconsider: If a new market segment or product line creates a genuine new demand pocket, spin up an Archetype 1 allocation for that segment in parallel rather than shifting the whole budget.

Guardrails for Budget Decisions

• If brand search share falls below your defined floor (typically 10–15% of total search clicks), protect it first — even if other stages are underfunded
• Require stage KPI evidence before scaling any budget line 2x. If guardrails deteriorate after a scale-up, roll back to the last stable allocation level
• Do not cut Retention and Expansion budget to fund Awareness. Poor activation and retention can destroy CAC/LTV math even when top-of-funnel is cheap

How to Present Budget to Leadership

Present the split as ranges tied to your named archetype, plus one sentence explaining why based on current win rate, NRR, and LTV/CAC. Add a footnote that reallocations are triggered by stage KPI thresholds, not by attribution model shifts.

---

Phase 6 — Build the 90-Day Experiment Backlog

Time: ~2–3 hours to build and score

Backlog Template

For each item, fill these fields:

Field	Notes
Title	Clear action, not a question
Stage and leak targeted	One stage, one leak type
Hypothesis	If we do X, stage KPI Y will move by Z% in N weeks
Impact score (1–5)	Expected lift on the single stage KPI
Confidence score (1–5)	Quality of supporting evidence
Effort score (1–5, where 5 = lowest effort)	Person-days across functions; flag engineering time separately
Reach	Weekly audience size touched (for RICE scoring)
Owner and start date	Named person, not a team
Success metric and decision rule	Single KPI, threshold, time window
Dependencies and guardrails	What could block or invalidate the experiment

Scoring Models

ICE: Score = Impact × Confidence × (6 − Effort)

RICE: Score = (Reach × Impact × Confidence) / Effort

Use ICE when experiments are roughly comparable in reach. Use RICE when some experiments touch 10x more users than others — reach differences matter for prioritization.

Filled 90-Day Backlog — Top 10 Items

1. Autobook demo on thank-you page

• Stage: Consideration — hand-raiser friction
• Hypothesis: Immediate scheduling reduces SDR lag and raises MQL→SQL by ~20% within 2 weeks
• ICE: 4 × 4 × 4 = 64 | Effort: 2 days | Owner: Demand Gen
• Success: MQL→SQL lifts from baseline to +6 percentage points, sustained for 2 consecutive weeks
• Dependencies: Calendly or Chili Piper license, CRM field mapping | Guardrail: no-show rate must not exceed 20%

2. SDR Day-0 sequence for demo requests

• Stage: Consideration — SLA gap
• ICE: 4 × 4 × 5 = 80 | Effort: 1 day | Owner: Sales Ops
• Success: 90% of demo requests receive first contact within 15 minutes of submission

3. Message match on top 5 paid landing pages

• Stage: Engagement — bounce rate
• ICE: 3 × 3 × 4 = 36 | Effort: 2 days | Owner: Growth
• Success: Engaged session rate on targeted LPs improves by 15+ percentage points vs. prior 4-week average

4. Creative refresh cadence (every 2 weeks)

• Stage: Engagement — creative fatigue
• ICE: 3 × 3 × 3 = 27 | Effort: 3 days/month | Owner: Performance
• Success: Paid social CTR returns to and sustains 1.2x of pre-fatigue baseline

5. Form trim + backend enrichment

• Stage: Consideration — contactability
• ICE: 3 × 4 × 4 = 48 | Effort: 2 days | Owner: Demand Gen
• Success: Form completion rate +20%, contactability stays above 95%

6. PQL scoring model audit

• Stage: Consideration → Conversion
• ICE: 4 × 3 × 2 = 24 | Effort: 4 days | Owner: PLG
• Success: PQL→Opportunity rate improves by 25% over 6-week measurement window

7. Competitive objection one-pagers (top 3 competitors)

• Stage: Conversion — win rate
• ICE: 3 × 3 × 4 = 36 | Effort: 2 days | Owner: Product Marketing
• Success: Opportunity→Won rate improves by 2 percentage points in matched competitive deal cohort

8. Onboarding email sequence revamp

• Stage: Retention — 30-day activation
• ICE: 3 × 3 × 3 = 27 | Effort: 3 days | Owner: Lifecycle
• Success: 30-day activation rate lifts by 10 percentage points vs. prior 60-day cohort baseline

9. Pricing page social proof modules

• Stage: Conversion — late-stage hesitation
• ICE: 2 × 3 × 4 = 24 | Effort: 2 days | Owner: Web
• Success: Pricing page→demo request CTR improves by 15% vs. control

10. Re-nurture triggered ads for 30-day Consideration dwell backlog

• Stage: Consideration — stale leads
• ICE: 2 × 3 × 4 = 24 | Effort: 2 days | Owner: Performance + Demand Gen
• Success: 20% of stale leads re-engage (open email or click ad) within 2 weeks of re-nurture enrollment

Capacity and Feasibility Check

• Cap total engineering time at 5–7 days per sprint. Prefer experiments using no-code editors, CRM automation workflows, and existing tools
• If an experiment requires platform migration or new tooling procurement, defer it past the 90-day window
• Size the backlog to 80% of writer and campaign manager capacity — leave 20% for reviews, stakeholder feedback, and scope changes that will happen

---

Phase 7 — Measurement Cadence and Attribution-Agnostic Decision Rules

Time: ~30 minutes to document and socialize

Suggested Cadence

Weekly 30-minute stage review

• Inputs: Latest stage KPIs and guardrails, experiment status and leading indicators
• Decisions: Pause or scale running experiments, reallocate up to 10% of stage budget

Biweekly creative and landing page review

• Inputs: CTR trend, frequency, engagement rate and bounce by LP, creative fatigue signals
• Decisions: Refresh or retire creatives, apply message match fixes

Monthly budget and funnel review

• Inputs: Stage conversion rates and velocity, pipeline coverage, retention cohorts, LTV/CAC trend
• Decisions: Reallocate budget across stages by up to 20%, add or remove backlog items, assess archetype transition

Attribution-Agnostic Decision Rules

• Optimize to stage conversion rates and cohort retention rather than channel CPA alone
• Use holdout tests or geographic splits to validate major budget reallocation decisions
• If two channels feed the same stage KPI equally, prefer the one with better guardrail performance and lower operational complexity
• Accept a 10–15% data discrepancy between GA4 and CRM as normal. Do not spend analytical time reconciling individual records — focus on whether trendlines across both systems are directionally consistent

Stop-Start Thresholds

• Scale an experiment if the primary stage KPI improves against baseline for 2 consecutive weeks and all guardrails hold
• Pause if guardrails deteriorate beyond predefined thresholds — even when the primary KPI is improving
• Kill if no leading indicator movement appears after 3 weeks and the hypothesis has been fairly tested

---

Phase 8 — Executive Summary and Agency Scorecard

Executive Summary One-Pager Template

Section	Content
Goal	One sentence linking the framework to revenue or retention impact
Current state	One bullet per biggest active leak — with a number and a time window
Chosen framework	Stage definitions in one line each, with entry/exit rules
90-day focus	Top 3 experiments with owners and expected stage KPI impact
Budget plan	Stage-level split range with archetype rationale
Measurement	Cadence and 2–3 guardrails you will protect throughout the quarter
Decision needed	Approve: budget range, named owners, review cadence

Filled example — B2B SaaS mid-market:

Goal: Improve qualified pipeline creation and 90-day retention using a stage-based, attribution-agnostic framework in Q3.

Current state:

• MQL→SQL fell from 33% to 26% in the last 60 days (leak at Consideration)
• 30-day activation dropped from 71% to 62% for new logos onboarded in May (leak at Retention entry)

Framework: Five-stage model (Awareness → Engagement → Consideration → Conversion → Retention) with explicit entry/exit rules tied to GA4 events and HubSpot lifecycle fields.

90-day focus:

• Autobook demo + SDR Day-0 sequence → target: MQL→SQL recovers to 30%+ (+$320K estimated pipeline at current ASP and close rate)
• Message match on 5 paid LPs → target: engaged session rate +15pp, reducing wasted ad spend
• Onboarding sequence revamp → target: 30-day activation recovers to 68%+ (+6pp, protecting NRR floor)

Budget: Scaling archetype — Awareness 25%, Engagement 15%, Consideration 25%, Conversion 15%, Retention 20%. Monthly rebalancing based on stage KPI movement.

Measurement: Weekly stage reviews. Guardrails: contactability above 95%, no-show rate below 20%, brand search share above 25%.

Decision needed: Approve Q3 budget split, confirm experiment owners, and confirm Sales Ops SLA support for Consideration experiments.

Why add dollar translation: Leadership approves plans that connect to revenue. For each of the top 3 experiments, add one line translating the stage KPI improvement into expected pipeline or retention impact. Example: “MQL→SQL +4pp × current MQL volume × average ASP × win rate = estimated pipeline impact.” Even a rough estimate is more persuasive than a percentage in isolation.

---

Agency Evaluation Scorecard

Criteria and weights:

Criterion	Weight
Framework fit and stage understanding	25%
Tactics mapped to diagnosed leaks	25%
Measurement approach and guardrails	15%
Team capability and capacity match	15%
Stack fit and no-replatform stance	10%
Commercial terms and flexibility	10%

Scoring scale: 5 = Excellent, 4 = Strong, 3 = Adequate, 2 = Weak, 1 = Poor

Filled example:

Criterion	Agency A	Agency B
Framework fit	4 — Stage definitions align, clear entry/exit rules proposed	3 — Vague funnel language, heavy on Awareness
Tactics to leaks	5 — Directly addresses MQL→SQL and activation with low-lift plays	3 — Strong creatives but thin MOFU and onboarding plan
Measurement	4 — Stage KPIs and guardrails defined, weekly cadence proposed	3 — Channel CPA focus, weak guardrails
Team and capacity	3 — Senior team in pitch, junior day-to-day; adequate bandwidth	4 — Dedicated pod assigned
Stack fit	5 — Works natively with HubSpot, Salesforce, GA4; no platform change required	3 — Pushes CDP migration mid-quarter
Commercials	4 — Within budget, 60-day termination clause	5 — Lower cost, favorable terms
Weighted score	4.25	3.55

Decision: Select Agency A. Fits stack, targets diagnosed leaks, higher probability of moving qualified revenue within 90 days. Agency B’s CDP push would consume Q3 engineering capacity and delay all experiments.

Early warning signals in agency evaluation:

• Agency resists stage KPIs and pushes channel CPA or attribution model changes → reduce Framework Fit and Measurement scores
• Agency proposes platform migration in the first 90 days → reduce Stack Fit score significantly; migrations rarely complete on schedule and block experiment execution

Procurement sign-off condition: Attach the completed scorecard, confirmed budget within ceiling, and signatures from Marketing, Sales, and Finance leads. The rubric’s direct connection to the full-funnel model makes the selection defensible in procurement review.

---

Common Mistakes That Slow or Derail Approval

• Stage names without entry/exit data rules — adds a one-line data rule per stage to eliminate definition debates
• Budgets justified by CPA alone — tie every allocation decision to stage KPIs and guardrail thresholds
• Backlog items without named owners or success metrics — no owner = no accountability; no metric = no decision rule
• Agency rubrics that weight creative showreels over stack fit and leak targeting — use the weighted criteria above to anchor procurement discussions
• Presenting benchmark numbers as targets — replace with your own baseline numbers and label where data is estimated

---

Conclusion

This framework gives you a stage-based operating system for full-funnel marketing — one that holds up in leadership reviews because every decision connects to a data-defined stage, a named owner, and a guardrail that protects quality alongside volume.

The week-to-build, quarter-to-operate framing is honest. The output is worth it: a funnel model your marketing and sales teams share, a budget structure that adjusts to where your company actually is, and a 90-day experiment backlog that your team can execute without waiting for engineering. When anything wobbles in Q&A, return to the stage boundaries and the guardrails — those are your source of truth.

A technical playbook for SEO Managers and Tech Leads preparing for a website redesign or recovering from cannibalization-driven traffic loss.

---

Who this is for: This playbook is not an introduction to content clusters. It assumes you can read GSC and Ahrefs data, coordinate with a dev team on redirect deployments, and influence IA decisions during a redesign. If you’re an SEO Manager or Tech Lead facing a site restructure, this is your execution guide.

On timing: “Ship a cluster blueprint by Friday” is aspirational. If your URL inventory is large or your GSC/CRM data is messy, this work realistically takes 7–10 working days end to end. Budget accordingly, especially if dev deployments require scheduling lead time.

---

What You’ll Produce

By the end of this playbook, you’ll have:

• A documented cluster plan with pillar selection rationale and coverage matrices
• A safe redirect and consolidation spec with one-hop 301s and QA checklist
• A URL schema and IA pattern frozen before redesign cutover
• An internal linking model with anchor governance rules
• A prioritized backlog sized to your actual writer and dev capacity
• A stakeholder sign-off package with CMO-ready summary and deck template

---

Tool and Infrastructure Requirements

Before starting, confirm you have access to all of the following. Missing any one of these creates a hard blocker at the relevant phase:

Tool / Resource	Used for	Minimum viable alternative
Google Search Console	Performance baseline, query mapping	No substitute — access is mandatory
Ahrefs (or Semrush)	Backlink data per URL, competitor hubs	Moz Link Explorer (partial coverage)
Screaming Frog or Sitebulb	Full site crawl, inlink extraction	Sitebulb free tier (limited URLs)
BigQuery or spreadsheet export	Joining GSC + crawl data at scale	Google Sheets if under ~5k URLs
Dev deployment slot	Redirect implementation	Must be confirmed before scope is finalized
Writer capacity estimate	Backlog sizing	Required — see Phase 7

If you’re at a smaller company without Ahrefs or Screaming Frog: GSC + a free Screaming Frog crawl (up to 500 URLs) + a manual backlink check via Ahrefs free version will get you 70% of the way there. Flag which data points are estimated vs. measured in your sign-off package.

---

The Playbook at a Glance

[BASELINE & SCOPE] → traffic, cannibalization count, capacity, constraints
        ↓
[CRAWL & INVENTORY] → all URLs + performance + backlink data in one sheet
        ↓
[QUERY & INTENT MAPPING] → cluster queries, classify intent, score pillars
        ↓
[CLUSTER DESIGN] → subtopics, page types, coverage matrix, stop-creation rule
        ↓
[CANNIBALIZATION CONSOLIDATION] → keep/merge decision tree, redirect spec
        ↓
[URL SCHEMA & IA] → slug rules, directory depth, breadcrumbs, sitemaps
        ↓
[INTERNAL LINKING] → hub-to-spoke patterns, anchor governance, automation
        ↓
[PRIORITIZATION & SIGN-OFF] → RICE scoring, backlog sizing, CMO package

---

Phase 1 — Establish Baseline and Scope

Time: ~2–3 hours

Why this matters

You need a hard baseline and a clear scope before changing IA or URLs. Skipping this step risks traffic loss and endless rework. Every redirect decision and pillar choice must be measured against this baseline.

Step 1: Set a baseline window

Use the last complete 90 days in GSC as your primary baseline. If your topic area has strong seasonality, also pull the same 90-day period from one year prior for YoY comparison.

Step 2: Lock success metrics and guardrails

Primary metrics:

• Non-brand clicks and impressions
• Average position for your top 50 target queries
• Number of queries where 2+ URLs from your domain rank simultaneously (cannibalization count)

Guardrails:

• Number of 404s (pre- and post-deploy)
• Number of redirect chains (target: zero)
• % of legacy backlinks that still resolve to a live 200 page after redirects

Step 3: Define topic scope and brand boundaries

List approved brand topics and explicitly excluded topics. If a topic is outside brand scope or sales does not support it, do not select it as a pillar — no matter how much search demand it has.

Step 4: Confirm capacity and constraints

Get these numbers in writing from both teams:

Writers:

• Hours available per week
• Realistic output by content type (see Phase 7 estimates)

Dev team:

• Number of redirect deployments available this quarter
• Maximum redirects per deployment batch
• Any blackout periods during redesign

Redesign team:

• Date when IA and URLs must be frozen (hard deadline)

Acceptance to Proceed

Before moving to Phase 2, confirm you have:

• [ ] Baseline report documented and shared (non-brand clicks, impressions, avg. position, cannibalization count)
• [ ] Guardrail sheet created with current 404 count and redirect chain count
• [ ] Capacity numbers acknowledged in writing by content and dev leads
• [ ] Brand topic boundaries documented and signed off

Early warning: If stakeholders disagree on the baseline period or brand topic scope, resolve this before touching any URLs. This is the most common cause of mid-project scope creep.

Failure mode: You produce a correct cluster model that is infeasible within writer or dev capacity. Remedy: re-scope to a 4–8 week tractable subset and defer the rest with explicit dates attached.

---

Phase 2 — Crawl and Inventory URLs, Performance, and Backlinks

Time: ~3–4 hours (plus crawl run time)

Why this matters

You cannot consolidate or cluster safely without a single source of truth listing every relevant URL, its performance, and its link equity. Decisions made without this sheet produce blind redirects and lost rankings.

Step 1: Crawl the site

Use Screaming Frog or Sitebulb to extract all indexable URLs under your content directories. Export: status code, canonical, title, H1, word count, inlinks count.

Don’t forget legacy sections. Directories like /blog-old/, /resources-archive/, or old campaign microsites frequently carry significant external backlinks. Include them in the crawl.

Step 2: Enrich with GSC performance

Export from GSC > Search Results: page-level clicks, impressions, CTR, and average position. Join by URL.

URL normalization is critical: Mismatched protocols (http vs. https) or trailing slash inconsistencies will cause join failures. Normalize all URLs to the same format before merging.

Step 3: Enrich with backlink data

From Ahrefs Site Explorer > Pages report: export referring domains and total backlinks per URL. Join by URL.

Step 4: Build the Query-to-URL Mapping Sheet

This is your working document for the entire project. Add columns progressively as you work through each phase.

CSV header:

URL, StatusCode, CanonicalTo, Title, H1, WordCount,
GSC_Clicks_90d, GSC_Impr_90d, GSC_AvgPos_90d, TopQueries,
Ahrefs_RefDomains, Ahrefs_Backlinks, ContentType,
TargetQuery, Intent, KeepOrMerge, RedirectTo,
PrimaryAnchor, SecondaryAnchors, Notes

Sample rows:

https://example.com/seo/content-cluster-strategy, 200, ,
Content Cluster Strategy for B2B SEO, Content Cluster Strategy, 2400,
640, 18000, 3.2, "content cluster strategy; content hub seo",
42, 215, Pillar, content cluster strategy, Research, Keep, ,
"content cluster strategy", "content hub seo; cluster model", Strong links — best match to head term

https://example.com/seo/what-is-content-cluster, 200,
https://example.com/seo/content-cluster-strategy,
What Is a Content Cluster?, What Is a Content Cluster?, 1500,
210, 8000, 9.1, "what is content cluster; seo cluster definition",
16, 67, Cluster, what is content cluster, Definition, Merge,
https://example.com/seo/content-cluster-strategy,
, , Consolidate definition section into pillar — low links, weak standalone

---

Phase 3 — Query Intent Mapping and Pillar Selection

Time: ~3–4 hours

Why this matters

Pillars must align with real search demand and intent, not internal preferences. Incorrect pillar choices lock you into poor IA and wasted content investment.

Step 1: Build your query set

• From GSC: Export queries driving impressions to your content areas. Exclude brand terms. Use 12 months for breadth, but annotate the last 90 days for recency weighting.
• From Ahrefs: Seed with competitor hub pages and their top-ranking keywords. Export overlapping terms.

Step 2: Classify intent for each query

Tag each query with one of: Research, How-to, Comparison, Transactional, Navigational, Mixed.

Also note SERP features present: listicles, featured snippets, definitions, tools, templates, video carousels. These directly inform what page type you need to create.

Handling Mixed-Intent SERPs

Mixed-intent SERPs are the most common difficult case and the most often mishandled. Here’s how to approach each scenario:

Scenario A — Listicles mixed with how-tos (e.g., “content cluster examples”): If the top 10 results include both list-format pages and process guides, the SERP is rewarding depth. Create a comprehensive pillar with clearly labeled sections — don’t split into two thin pages. A single page with an H2 for “What are content clusters” and an H2 for “Examples” outperforms two separate thin pages targeting each query independently.

Scenario B — Comparison mixed with transactional (e.g., “content cluster tool vs manual”): If some top results are tool comparison pages and others are product landing pages, create the comparison as a spoke page under the pillar, and let the product page stand separately. Link between them explicitly.

Scenario C — Truly ambiguous SERP with near-equal split across all intent types: This usually signals a head term not yet settled in the SERP. Treat it as a pillar-level opportunity and build a comprehensive hub that covers all angles — it will naturally outperform narrow, intent-specific pages on an unsettled query.

Quick rule for SERP overlap: If 5 of the top 10 results for two different queries are the same URLs, those queries belong to the same cluster — consolidate them under one page with sections.

Step 3: Score and select pillars

Use this weighted formula to prioritize objectively:

PillarScore = (0.4 × Demand) + (0.3 × BusinessFit) + (0.2 × Probability) + (0.1 × Moat)

Dimension	How to score
Demand	log₁₀(monthly GSC impressions, last 12 months). Log scale reduces bias toward a single breakout keyword.
Business Fit	0–3: 0 = sales explicitly doesn’t support it; 1 = adjacent but not core; 2 = supports sales conversations; 3 = direct path to pipeline
Probability	0–3: 3 = low KD and you rank in top 20 already; 2 = medium KD with some authority; 1 = high KD and starting from scratch
Moat	0–3: 0 = commodity topic anyone can cover; 1 = some proprietary angle; 2 = original data or POV; 3 = you have exclusive access to data or a recognized domain authority position

How to calibrate weights for your context:

The default weights (0.4/0.3/0.2/0.1) are designed for a mid-market B2B SaaS with a 3–6 month sales cycle where demand signal and commercial fit matter most.

Adjust if:

• Early-stage company / new domain: Increase Probability weight to 0.35 and reduce Demand to 0.25. You can’t compete on high-KD terms yet — prioritize winnable ground.
• Enterprise / long sales cycle: Increase Moat to 0.20 and BusinessFit to 0.35. Proprietary insight is your only sustainable differentiator.
• Ecommerce: Increase BusinessFit to 0.40 (direct revenue path matters more than brand topics), reduce Moat to 0.05.
• Mature domain with strong authority: Increase Demand to 0.50 — you can realistically compete for higher-volume terms, so weight accordingly.

Select 3–5 pillars that score highest and sit within brand boundaries. More than 5 in a single quarter is usually infeasible for a small team.

Edge cases:

• Seasonal topics: Do not select as a pillar unless there is evergreen demand outside the spike window. Handle seasonality as a spoke under a broader evergreen pillar.
• Topics with high demand but low business fit: Flag these explicitly in your sign-off package. Driving traffic you can’t convert is a vanity metric, not a success.

Deliverable: Pillar Scorecard

A table showing each candidate pillar, its four dimension scores, weighted total, and a one-line rationale. This becomes slide 3 in your deck.

---

Phase 4 — Cluster Design: Subtopics, Page Types, Coverage

Time: ~3–4 hours

Why this matters

Choosing the right page types and coverage depth ensures one URL per intent and prevents future cannibalization from re-emerging within months of launch.

Step 1: Define page roles

Role	Description
Pillar hub	Comprehensive topic page introducing all subtopics, linking to all spokes, targeting the head term
Spoke	Depth page aligned to a single intent — how-to guide, comparison, template, use case, pricing explainer
Enabler	Glossary entry, checklist, calculator, or tool page — create only when the SERP explicitly rewards this format

Step 2: Build a coverage matrix per pillar

For each pillar, fill this matrix:

Subtopic / Intent	Page Type	URL Slug	Target Query	Status	Owner	Est. Hours
What is content clustering	Pillar section	/seo/content-cluster-strategy	content cluster strategy	Keep (expand)	SEO Lead	4h
Internal linking rules	Spoke (How-to)	/seo/content-cluster-strategy/internal-linking-rules	internal linking for content clusters	Create	Writer A	8h
Keyword mapping process	Spoke (How-to)	/seo/content-cluster-strategy/keyword-mapping	keyword mapping for content clusters	Create	Writer B	8h
Redirect and consolidation	Spoke (How-to)	/seo/content-cluster-strategy/redirects-and-consolidation	content consolidation seo	Merge (from 2 URLs)	SEO Lead	5h
Real-world examples	Spoke (List)	/seo/content-cluster-strategy/examples	content cluster examples	Create	Writer A	7h
Template download	Enabler	/seo/content-cluster-strategy/template	content cluster template	Create	Designer + Writer	6h

Step 3: Apply the stop-creation rule

Before adding any new spoke to the matrix, check: does your domain already rank in the top 20 for that target query with a different URL?

If yes → expand the existing ranking page instead of creating a new URL. A new URL targeting the same query will cannibalize the existing one within weeks.

If the existing page is outdated or too weak to expand → consolidate into the planned spoke via redirect (see Phase 5).

Common pitfall: Editorial enthusiasm produces multiple thin comparison pages (“X vs Y,” “X vs Z,” “Y vs Z”) when a single comprehensive comparison page covers all three and matches what the SERP rewards. Check the top 10 before splitting.

---

Phase 5 — Cannibalization Consolidation: Keep, Merge, Redirect

Time: ~4–6 hours

Why this matters

Cannibalization suppresses rankings and splits link equity. Consolidations and redirects must be safe, minimal, and always one-hop. This is the phase with the highest execution risk — get it right before redesign cutover.

Decision Tree

Start: Two or more URLs rank for the same query
        ↓
Do they share the same intent?
    ├── YES → Keep the best URL, merge content into it, 301 others to keeper
    └── NO  → Keep both, clarify intent via headings and anchors — no redirect
                        ↓
            Does the weaker URL have significantly more backlinks?
                ├── YES → Keep the higher-link URL, rewrite in place,
                │         301 the better-content URL into it
                └── NO  → Keep the URL with the best query-to-content match

Keep-or-Merge Scoring Rubric

When choosing which URL to keep, score each candidate:

Dimension	Weight	What to measure
Link equity	40%	Referring domain count and topical relevance of linking domains
Query-to-content match	30%	Title/H1 alignment, section coverage of the target query
Performance trend (last 90 days)	20%	Click and position trajectory — flat or growing vs. declining
Redirect blast radius	10%	Number of external links and internal link dependencies pointing at this URL

The URL with the highest weighted score becomes the keeper. Document this scoring in your mapping sheet for every contested pair.

Redirect Specification Rules

These are non-negotiable:

• Use 301 permanent redirects only
• One hop only — never chain redirects
• Never redirect to the homepage or a vague category page — always the best topical match
• Preserve URL parameters only if required for page function — otherwise drop them
• Keep the final destination URL canonicalized to itself
• Update all internal links to the final URL — relying on the redirect itself causes intrinsic hop latency and dilutes authority passage
• Retain the strongest slug when it has significant backlink volume, even if a newer slug is semantically cleaner

Redirect Specification Template

From, To, Type, Priority, Reason, Owner, QA_Status

/seo/what-is-content-cluster, /seo/content-cluster-strategy, 301, High,
Merge definition section into pillar — 16 ref domains vs 42 on keeper, SEO Lead, Pending

/seo/content-clusters-guide, /seo/content-cluster-strategy, 301, High,
Duplicate head term guide — lower links and declining clicks, SEO Lead, Pending

/seo/cluster-internal-linking, /seo/content-cluster-strategy/internal-linking-rules, 301, Medium,
Consolidate to single-intent spoke, SEO Lead, Pending

Post-Merge: What to Expect in the First 14 Days

Note for CMO and stakeholders: After redirecting and merging multiple URLs into a single keeper, search rankings for the affected queries may fluctuate for approximately 10–14 days. This is normal. Google needs time to re-crawl the redirected URLs, consolidate signals onto the keeper, and update its index. You may see position shifts, temporary drops, or URL switching in GSC during this window. Do not intervene unless 404s spike or the keeper URL itself drops out of the top 50 after day 14. Premature rollbacks cancel the consolidation benefit.

Monitor this during the stabilization window:

• GSC Coverage report: no growing 404s
• GSC Performance: position for target queries stabilizing by day 10–14
• Ahrefs: legacy backlinks now resolving to 200 on the keeper

Handling Internal Links at Scale

The redirect spec handles external links passively. Internal links must be updated actively — redirects alone add hop latency and reduce authority transfer efficiency.

For large sites, manual link-by-link updates are impractical. Use:

• WordPress: Better Search Replace plugin — bulk-replaces old URLs in the database with new URLs. Run on a staging environment first and take a DB backup before executing in production.
• Any CMS: Export inlinks per URL from Screaming Frog (Bulk Export > All Inlinks, filtered by the retiring URLs). This gives you a file-by-file map of every page containing the old URL — hand to your content team or CMS admin for batch updates.
• Headless / custom CMS: Run a database query against your content table filtering for the retiring URL pattern, update programmatically, and log changes for QA.

Always update internal links after the redirect is live but before removing the redirect — this ensures no 404 window during the transition.

Post-Redirect: Image and Media Cleanup

When retiring URLs, don’t orphan their media assets. Before removing a page from your CMS:

• [ ] Download or transfer images that are unique to that page and referenced in the merged content
• [ ] Check that the keeper page references the correct image URLs (especially if media is hosted at /uploads/YYYY/MM/filename.jpg paths)
• [ ] Remove images that are not being transferred — orphaned media wastes hosting storage and can inflate your media library over time
• [ ] If images appear in XML sitemaps (image sitemaps), update the sitemap post-merge

QA Checklist: Safe Merges

Run this after every redirect batch deployment:

• [ ] All From URLs return 301 directly to To URLs — no chains
• [ ] All To URLs return 200, are indexable, and canonical to themselves
• [ ] Internal links have been updated to point to To URLs
• [ ] GSC Coverage shows no 404 spike in days 1–7 post-deploy
• [ ] Ahrefs (or your backlink monitor) shows legacy links now resolving 200 on the final URL
• [ ] GSC Performance shows no URL switching (two URLs alternating rank) for target queries by day 14

FL2 condition: For each target query, only one URL from your domain appears in the GSC Top Pages report, and that URL is the keeper receiving the legacy backlinks — verified by GSC query report and spot-check of top backlink sources.

Early warning: URL switching in GSC for a target query post-deploy means Google is uncertain which page to serve. Check whether the keeper page has clearly absorbed the merged content, whether internal anchors still point to the retired URL, or whether the redirect has a chain.

Failure mode: You redirected the highest-link-equity URL to a newer slug without updating major internal link hubs. Remedy: either revert to the stronger URL slug or run an emergency internal link update pass immediately.

---

Phase 6 — URL Schema and IA for Redesign

Time: ~2 hours (plus alignment meeting with redesign team)

Why this matters

URL and IA decisions made during redesign are extremely costly to reverse. Choices made here must be stable for 2–3+ years. Every future redirect creates debt.

URL Schema Rules

• Lowercase, hyphen-separated slugs only
• No dates in slugs for evergreen content
• Maximum 2-level depth for clusters: /pillar/ and /pillar/spoke/
• Pick one trailing slash convention and enforce it sitewide via redirects and canonical tags
• Choose short, unambiguous head terms for pillar slugs — avoid versioning (-2024, -v2, -new) unless the content is genuinely time-bound
• No parallel taxonomies: /seo/ and /content/ should not both contain the same cluster topic

IA Deliverables

• Global navigation links to the top 3–5 pillars only — do not surface every cluster in the nav
• Pillar page template includes: overview section, key subtopics, auto-generated TOC, and an index of spokes with descriptive anchors
• Breadcrumbs: Home > [Pillar] > [Spoke] — pillar is the literal parent directory
• XML sitemap lists pillars and spokes by cluster, not by publish date

Example Directory Structure

/seo/content-cluster-strategy/                  ← Pillar hub
/seo/content-cluster-strategy/internal-linking-rules/   ← Spoke
/seo/content-cluster-strategy/keyword-mapping/          ← Spoke
/seo/content-cluster-strategy/redirects-and-consolidation/  ← Spoke
/seo/content-cluster-strategy/examples/                 ← Spoke
/seo/content-cluster-strategy/template/                 ← Enabler

Edge case — spoke belonging to two pillars: Pick one canonical parent directory. Cross-link from the second pillar using a contextual inline link — never duplicate the URL under two parent paths.

Acceptance to Freeze IA

• [ ] Redesign team confirms directory structure and page templates match this pattern
• [ ] SEO confirms that all high-link legacy pages either retain their URL or have a documented one-hop redirect to their new canonical

---

Phase 7 — Internal Linking Model and Anchor Governance

Time: ~2 hours to document; ongoing enforcement

Why this matters

Internal linking is how you pass context and authority between pages. Inconsistent anchors and sloppy patterns re-introduce cannibalization within months of launch — undoing consolidation work silently.

Linking Patterns

Link direction	Rule
Hub → Spokes	Link to each spoke once from the pillar overview and a dedicated “In this guide” section. Use intent-matching descriptive anchors.
Spokes → Hub	In the intro and conclusion of every spoke, link back to the hub using the primary anchor reserved for that pillar.
Sibling cross-links	Only when the sibling genuinely helps the user progress. Use secondary anchors — not the primary pillar anchor — to avoid signal confusion.
Breadcrumbs	Always link the pillar level back to the hub.

Anchor Governance

• Reserve one primary anchor for each pillar (e.g., “content cluster strategy”). Use it consistently when linking to the hub from any spoke or supporting page.
• For spokes, use intent-explicit anchors (e.g., “internal linking rules for content clusters”) — not generic phrases like “learn more” or “click here.”
• Cap the same anchor from the same page to once. Vary secondary anchors where additional links are necessary.
• Avoid sitewide boilerplate links that repeat the exact primary pillar anchor across every page in the sidebar or footer — this dilutes anchor signal value.

Automation

• Build a reusable CMS component that auto-renders the pillar’s spoke index on the hub page — eliminates manual linking per spoke addition.
• Add a “Back to [Pillar Name]” block to every spoke template. This ensures spoke-to-hub linking survives future content edits.
• Maintain an anchor dictionary in your mapping sheet: URL, PrimaryAnchor, SecondaryAnchors[].

Quarterly Health Check

Every quarter, crawl and extract inlinks by anchor text to each pillar and its top spokes. Intervene if:

• A new blog post or cluster page begins accumulating the primary pillar anchor (creating future cannibalization)
• The ratio of primary to secondary anchors drifts heavily in either direction
• Breadcrumbs stop resolving due to URL changes not captured in the redirect spec

---

Phase 8 — Prioritization, Backlog Sizing, and Stakeholder Sign-Off

Time: ~3–4 hours

Effort Estimates by Content Type

Use conservative estimates when sizing your backlog. Optimistic estimates are the most common cause of missed sprint commitments.

Content type	Realistic effort
Pillar page (net-new)	12–18 hours
Spoke page (net-new)	6–10 hours
Consolidation edit (merging into keeper)	3–6 hours
Redirect spec + QA per URL	15–25 minutes

Size your first 4–8 weeks to 80% of writer capacity — leave 20% buffer for reviews, stakeholder feedback rounds, and inevitable scope changes.

RICE Scoring (SEO-Adapted)

Score = (Reach × Impact × Confidence) / Effort

Dimension	Definition
Reach	90-day non-brand impressions for the target query cluster
Impact	3 = fixing active cannibalization on a top-20 query; 2 = net-new spoke to high-intent query; 1 = long-tail spoke
Confidence	0.5–1.0 based on SERP match quality and your current domain authority in the topic area
Effort	Hours as estimated above

Scheduling rule: Always prioritize high-risk redirects and consolidations before net-new content creation. Stabilize existing rankings before adding new pages to the cluster.

---

Stakeholder Sign-Off Package

1. Executive Summary One-Pager (CMO-Ready)

Objective Create [N] content hubs aligned to how buyers research [your product category]. This consolidates duplicate pages, preserves backlinks, and ensures rankings remain stable during the redesign.

What we will deliver

• Pillars selected: [Pillar A], [Pillar B], [Pillar C], [Pillar D]
• Cluster map: [N] spoke pages aligned to buyer questions and SERP intent
• Safe redirect plan: [X] consolidations using one-hop 301s — no homepage dumps
• Internal link rules: hub-spoke pattern to signal topical relevance to Google

Why it matters Today, [Y] queries show multiple URLs from our domain ranking simultaneously. This splits relevance signals and hands competitors a structural advantage. Our plan consolidates to one clear page per query and protects [Z] high-value backlinks.

Risks and mitigations

Risk	Mitigation
Traffic dip from redirects	One-hop 301s only, keep strongest URLs, full QA checklist before and after deploy
Temporary ranking fluctuation (10–14 days post-merge)	Expected and normal — Google re-consolidating signals. Monitor but don’t intervene prematurely.
Over-scoping content	Backlog sized to [writer capacity] at 80% — highest-impact items first

Success criteria Post-launch: non-brand clicks at or above baseline. For each target query, only one URL from our domain ranks. All legacy backlinks resolve to live 200 pages.

Filled example:

• Pillars: Content Cluster Strategy, Technical SEO Audits, SaaS SEO Pricing, B2B Link Building
• Consolidations: 12 URLs merged into 5 keepers
• Backlinks preserved: 94% of top 200 linked pages resolve to 200 after redirects
• Target: maintain 35K non-brand clicks per 90 days; reduce cannibalized queries from 28 to under 5

---

2. Cluster Blueprint Deck (12 Slides)

Slide	Audience	Content
1	All	Title: “Content cluster plan for redesign — protect rankings, focus authority”
2	CMO	Baseline and gap: non-brand clicks, cannibalized query count, competitor hub example
3	CMO	Pillar selection rationale: scored table with 2-line rationale per pillar
4	IA + CMO	Cluster maps: hub URL slug, list of spokes with page type and target queries
5	SEO + IA	Consolidation plan: 3 Keep vs. Merge examples with scoring rationale and redirect lines
6	IA	URL schema: directory structure with example slugs, breadcrumb rule
7	SEO + Dev	Internal linking rules: hub-to-spoke, spoke-to-hub, anchor dictionary excerpt
8	CMO + Dev	Backlog and timeline: items by sprint, effort hours, dev dependencies
9	All	Risks, QA checklist, early warning signals, rollback plan

Language rule: For CMO-facing slides (1–3, 8–9), use business outcome language. Keep acronyms minimal and always translate traffic metrics to pipeline or revenue impact where possible. For IA and dev-facing slides (4–7), keep URL patterns, anchor rules, and page types precise.

---

FL2 Sign-Off Conditions

The plan is considered ready for redesign implementation when all of the following are confirmed in writing:

• [ ] Pillar selection signed off by CMO and sales representative
• [ ] IA directory structure and URL patterns confirmed by redesign team
• [ ] Redirect deployment slot confirmed by dev lead
• [ ] Named owner assigned for redirect QA and internal link update pass
• [ ] Backlog hours accepted by writer lead as feasible within stated capacity

Early warning: If the IA team requests changes to directory depth or slug structure after sign-off, or if dev flags redirect volume as infeasible, re-scope immediately and update the mapping sheet and deck the same day.

Failure mode: The documents look complete but there is no named owner for the redirect QA or the internal link update pass. Execution will stall. FL2 is only met with named owners, not just assigned teams.

---

Common Mistakes to Avoid

• Retiring a high-link URL in favor of a cleaner slug without compensating via redirect and internal link update — you lose the accumulated link equity permanently
• Creating multiple thin comparison pages (“X vs Y,” “X vs Z”) when the SERP rewards one comprehensive comparison guide — check the top 10 before splitting
• Publishing a glossary at scale without internal demand signal or link intent — it dilutes crawl budget without contributing to pillar authority
• Shipping a backlog with no hours next to each item — stakeholders cannot approve what they cannot evaluate

---

Conclusion

This playbook gives you a data-backed, technically rigorous cluster blueprint that holds up in both an executive sign-off meeting and a dev planning session. Every decision — pillar selection, keep-or-merge, redirect spec, anchor governance — is tied to a measurable input and a named owner.

The 7–10 day timeline is realistic. The output is worth it: stable rankings through your redesign, zero redirect chains, one URL per intent, and a prioritized backlog your team can actually execute within capacity. When anything wobbles during implementation, return to the mapping sheet and the stated FL2 conditions — that’s your source of truth.

A vendor-agnostic playbook to build a rigorous, defensible strategy — complete with an executive deck, RFP methodology, and a prioritized 90-day roadmap your small team can actually deliver.

---

A note on timing before you start: Many similar frameworks promise 48–72 hours. If you add up every work block in this guide — JTBD interviews, GA4 audits, keyword clustering, stakeholder alignment, deck design — you’re looking at 16+ hours of focused work, not counting data-gathering delays, tool access issues, or the time it takes to align a sales rep. Budget 5–7 working days. The quality and defensibility of your output depend on it.

---

What You’ll Produce

By the end of this framework, you’ll have four handoff-ready deliverables:

• An executive summary one-pager for leadership sign-off
• A 12-slide deck with KPIs, owners, and financial translation
• A diagnostic scorecard mapping your current gaps
• A 90-day roadmap with ICE-scored priorities and sprint checkpoints

---

Minimum Team Required

This framework is designed for a lean team. At minimum, you need:

Role	Time Commitment
Content Lead / SEO (you)	Full 5–7 days
Designer (part-time)	~6–8 hours for deck and templates
Sales representative	1 × 45-min input session
Support / CS representative	1 × 45-min input session
Analytics / Web (if separate)	~3–4 hours for GA4 setup

If you’re a team of one: prioritize the backbone, JTBD tiles, and roadmap first. The deck can be built in a day once those are solid.

---

Prerequisites

Before starting, confirm you have access to:

• GA4 or Looker (with at least 90 days of data)
• Google Search Console (non-brand query export)
• CRM or automation snapshots (pipeline stages, deal size)
• Content inventory (existing URLs, performance data)
• Business inputs: current OKRs, funnel stages, average deal size or LTV, sales cycle length, and 2–3 priority segments

---

The Framework at a Glance

[Company OKRs] → [North-star & guardrail metrics] → [Decision logic]
       ↓
[AUDIENCE & JTBD] → [Segments | Jobs | Journeys | Info needs]
       ↓
[DEMAND & TOPICS] → [SERP intent | Clusters | Opportunity sizing]
       ↓
[STRATEGY & PILLARS] → [POV | 3H mix | Formats & assets]
       ↓
[CHANNELS & DISTRIBUTION] → [Owned | Earned | Paid | Repurposing system]
       ↓
[MEASUREMENT] → [GA4 setup | KPIs by funnel | Attribution assumptions]
       ↓
[PRIORITIZATION] → [Gaps | ICE scoring | 90-day roadmap | Experiments]
       ↓
[EXEC / RFP DELIVERY] → [Exec summary | 12-slide deck | Q&A prep]

---

Phase 1 — Framework Backbone: OKRs, North-Star Metric, Decision Logic

Time: ~90 minutes | Day 1

Without a tight backbone, content priorities drift and collapse in Q&A. Anchor every content decision to a business OKR, a single north-star metric, and a clear decision tree that allocates effort by impact.

Step 1: Pull OKRs and pick 1 north-star metric

OKR example: Increase qualified pipeline by 20% in Q3; reduce CAC by 10%.

Pick one north-star that ladders directly to revenue this quarter:

• B2B SaaS: Sales Accepted Opportunities (SAOs) from content-attributed leads
• Ecommerce: Gross margin from non-brand organic sessions
• PLG: Product Qualified Leads (PQLs) or activated signups from content pathways

Step 2: Define guardrails and conversion proxies

• Guardrails: CAC payback period, sales cycle velocity, win rate baseline
• Proxies (for when pipeline data lags): high-intent demo form submissions, content-assisted opportunities, add-to-cart rate

Step 3: Decision logic for content investment

Use this tree to choose where to prioritize:

1. If GA4 shows high-intent pages with sub-1.5% CVR and under 50% scroll depth → fix conversion UX first
2. Else if non-brand organic is declining while brand traffic is flat → prioritize Help-topic cluster expansion and internal linking
3. Else if qualified traffic is strong but pipeline is soft → prioritize MOFU proof assets and sales enablement
4. Else → run 2 high-uncertainty experiments capped at 10% of capacity

Deliverable: Backbone One-Pager

• OKRs
• North-star metric
• Guardrails
• Decision tree bullets
• KPI targets with “why it matters” note for executives

Exec-language tip: Don’t just list KPIs — add a one-line translation. For example: “Non-brand sessions +20% — increases new logo reach at lower CAC.”

FL2 Checks

✅ Success condition	Executive signs off the north-star metric and KPI targets in writing, and assigns an owner for each
⚠️ Early warning	Repeated asks to define “qualified” or “attribution” — add inline definitions
❌ Failure mode	Technically correct KPIs without financial mapping — convert each target to pipeline or margin impact

---

Phase 2 — Audience and JTBD Mapping

Time: ~2 hours | Day 1–2

Skipping real jobs-to-be-done produces fluffy personas and content no one needs. Ground segments in jobs, pains, and triggers across the buying journey — so topics and formats almost write themselves.

Step 1: Build JTBD tiles for 3 priority segments

Use input from sales calls and support tickets. Fill one tile per segment:

Segment:
Trigger event:
Job to be done:
Success metric they care about:
Anxiety / friction:
Hiring criteria for a solution:
Alternatives they currently try:

Filled example — B2B SaaS security:

Segment: VP Engineering at Series B SaaS
Trigger event: Prospect asks for SOC 2 during security review
Job to be done: Ship proof of SOC 2 readiness to unblock deals
Success metric: Close enterprise deal within this quarter
Anxiety: Audit delays, developer time drain
Hiring criteria: Templates, automated evidence collection, auditor-vetted guides
Alternatives: Manual spreadsheets, third-party consultants

Step 2: Map journey questions by stage

Stage	Key question
Problem aware	“What is SOC 2 and why does it matter now?”
Solution aware	“How do tools compare to consultants?”
Product aware	“Do you integrate with Jira and AWS? What do audits look like?”
Decision	“What’s the implementation timeline, ROI, and TCO vs a consultant?”

Step 3: List information needs and required proof

For each segment, list their top 10 questions and the type of proof they need to move forward: benchmarks, calculators, integrations lists, implementation playbooks, security architecture diagrams, case studies by industry.

Deliverables

• 3 JTBD tiles
• A single-page journey map: stage → key question → proof asset required

Common pitfall: Personas without decision triggers. Always include trigger event, success metric, and core anxieties — or the tile isn’t actionable.

---

Phase 3 — Demand and Topic Model

Time: ~3 hours | Day 2

Content that ignores SERP intent and value sizing wastes bandwidth. Cluster topics by user intent and score by traffic upside and business value together.

Step 1: Pull demand signals

• GSC: Export last 90 days of queries for your top 50 landing pages. Filter to non-brand.
• Ahrefs or Semrush: Pull keyword ideas for your pillars. Export keyword difficulty (KD), volume, and CPC. If unavailable, use GSC impressions and CTR.
• AlsoAsked / People Also Ask: Capture sub-questions for FAQs.
• Sales notes: Common objections and industries mentioned in calls.

Step 2: Cluster by intent type

Cluster type	Format signals
Help	“What is,” “how to,” checklists, comparisons
Hub	Solution architectures, frameworks, playbooks
Hero	Research reports, calculators, big-swing narratives

Step 3: Opportunity sizing formula

Opportunity score = Potential qualified traffic × Business value × Winability

• Potential qualified traffic: non-brand volume × realistic CTR × % of traffic matching your ICP
• Business value (1–3): direct path to demo or cart, strong intent signal
• Winability (1–3): domain strength vs. competitors, SERP feature gaps, content gap size

Prioritize the top 10 topics with the highest composite score.

Mini example — SOC 2 cluster:

Topic	Type	Value	Winability	Score
SOC 2 requirements checklist	Help	3	2	6
SOC 2 automation vs consultants	MOFU comparison	3	2	6
SOC 2 implementation timeline	Help / Hub	2	3	6
SOC 2 cost calculator	Hero utility	3	1–2	4–6

Deliverables

• Topic model sheet: 3 columns per cluster — intent, keywords, composite score
• Top 10 list with assigned owners and due dates

Common pitfall: Chasing volume over value. For executives, explain why a lower-volume MOFU keyword can generate more pipeline than a high-volume informational one.

Prompt you can reuse to accelerate clustering:

“Cluster these keywords by intent aligned to our ICP’s jobs-to-be-done. For each cluster, list the top pages to create, the SERP format required, and a 1–3 winability score based on domain strength vs. current competitors. [Paste keywords + domain]”

---

Phase 4 — Strategy and Content Pillars

Time: ~2 hours | Day 3

A clear POV and a 3H mix prevent random acts of content. Define pillars tied to JTBD, then assign formats that match SERP requirements and sales proof needs.

Step 1: Define 3 content pillars

Governance rule: Each pillar must map to a revenue use case and at least one JTBD segment. If a pillar can’t support 6–8 assets in 90 days, merge or reframe it.

Example pillars — SOC 2 SaaS:

• Pillar 1 — Compliance velocity: Help engineers ship audits faster
• Pillar 2 — Proof and trust: De-risk enterprise deals at the decision stage
• Pillar 3 — Architecture and automation: Integrate with existing developer toolchains

Step 2: Design your 3H portfolio per pillar

Type	Format examples
Help	Checklists, how-tos, comparisons, FAQs
Hub	Playbooks, architectures, case studies, partner guides
Hero	Tools, data research, industry narratives, calculators

Step 3: Assign formats and plan reuse

For every net-new asset, pre-define its reuse path: longform article → downloadable checklist → webinar → sales slide insert → LinkedIn thread pack.

Deliverable

• 3 pillars with a one-line POV each
• 3H portfolio per pillar: primary format, secondary reuse assets, and required proof element

---

Phase 5 — Channels and Distribution System

Time: ~2 hours | Day 3–4

Great content still fails without distribution. Predefine owned, earned, paid, and repurposing flows so every asset reaches its ICP — and your sales team.

Owned

• Site: Pillar pages with internal links from Help → Hub → product pages
• Email: Monthly digest and triggered drips from content downloads
• Product (if PLG): In-app guides or banners for activation pathways

Earned

• Partners: Co-marketing webinars or guides with auditors, MSPs, or adjacent SaaS
• Communities: Vetted posts in relevant Slack groups or forums — link to proof assets, not landing pages

Paid

• Retargeting: MOFU proof assets for pricing and docs page visitors
• Intent networks: Narrow bids on comparison and “tool vs. consultant” queries

Repurposing System

For every net-new asset, define in advance:

• 3 short-form posts
• 1 email snippet
• 1 sales slide
• 1 infographic
• 1 FAQ block

Assign an owner, due date, and channel note. Package into a single shared folder.

Deliverable

Distribution checklist per asset: channels, copy blocks, UTM parameters, owner, publish date, success KPI.

Common pitfall: Untracked syndication. Always use UTMs and specify content source in GA4 using custom dimensions or content groupings.

---

Phase 6 — Measurement and Diagnostics

Time: ~3 hours | Day 4

Measurement must be GA4-first with simple, stated attribution assumptions. Set up events, content groupings, and dashboards that executives can read in one glance.

GA4 Essentials

Events to track: form_submit, file_download, view_pricing, start_checkout, demo_request, signup, add_to_cart, purchase

Mark as conversions: All high-intent events above

Content groupings: By pillar and by format — use regex on page path rules

UTMs: Standardize: source / medium / campaign / content

KPIs by Funnel Stage

Stage	KPIs
Top	Non-brand organic sessions, engaged session rate, new user share
Mid	Content-assisted conversions, demo requests from MOFU pages, return visitor rate
Bottom	Content-attributed opportunities or purchases, assisted revenue

Diagnosing Declines

• Non-brand sessions drop with stable rankings → check internal links and keyword cannibalization
• High exit rate on MOFU pages → add proof sections and CTAs toward product or demo
• High traffic, low qualified conversions → tighten ICP filters in paid; adjust topic selection to decision-stage triggers

Attribution Assumption (State It Openly)

Use last non-direct click for primary reporting, plus a content-assisted view:

Assisted conversion = user had 2+ engaged sessions with content pages in the past 30 days

Never overpromise multi-touch attribution without the infrastructure to support it. Show both last-click and assisted views side by side.

Deliverable: GA4 Dashboard Spec

Five tiles — each with a “why it matters” annotation for executives:

1. Non-brand organic sessions
2. Engaged session rate
3. Demo requests by content group
4. Content-assisted conversions
5. Top exit pages (with exit rate %)

---

Phase 7 — Prioritization and 90-Day Roadmap

Time: ~3 hours | Day 5

You cannot do everything in a quarter. Use an ICE model to score your backlog, then sequence into a 90-day plan with owned checkpoints.

Step 1: Build a Diagnostic Scorecard

Score 1–5 per area using GA4, GSC, and sales inputs:

Area	Score (1–5)	Evidence	Fix in 90 days?	Owner	Due
Audience clarity	4	JTBD tiles approved by sales	N	PMM	—
Topic coverage	3	4 high-value SOC 2 gaps	Y	SEO Lead	Sprint 2
MOFU proof assets	2	Only 1 case study, no comparisons	Y	PMM	Sprint 2
Distribution discipline	2	No partner co-marketing in place	Y	Partnerships	Sprint 3
Analytics readiness	3	Conversions set, no content groupings	Y	Analytics	Sprint 1
Conversion UX	2	Demo CVR at 1.1%	Y	Web	Sprint 1

Step 2: ICE Scoring on Your Backlog

Dimension	Definition
Impact (1–10)	Expected lift on your north-star metric
Confidence (1–10)	Quality of supporting data and team’s ability to execute
Effort (1–10, inverted)	Higher = less effort required

Sort by highest ICE total. Cap experiments at 10–15% of total capacity.

Step 3: Draft the 90-Day Roadmap

Six two-week sprints. One owner per workstream. Every sprint must include at least:

• 1 conversion fix
• 1 MOFU proof asset
• 2 Help-intent topics

90-Day Roadmap Template:

Sprint	Deliverables	KPI Target	Owner	Checkpoint	Risk	Mitigation
1	Demo CVR uplift, SOC 2 checklist, comparison page	+25 demo requests	Web, PMM	Week 2	Dev bottleneck	No-code form tweaks
2	Case study (Fintech logo), internal link map	MOFU CVR 1.8%	PMM, SEO	Week 4	Design delays	Use template
3	Partner webinar with auditor firm	200 registrations, 15 demos	PMM, Partnerships	Week 6	Partner delay	Backup guest
4	SOC 2 cost calculator v1	500 tool uses	PMM, Eng	Week 8	Eng capacity	Scope to v1
5	Email drip + sales one-pager from webinar repurpose	+10 SAOs	PMM, Sales	Week 10	CRM ops	Prebuilt assets
6	ISO 27001 primer, quarter recap report	+15% non-brand sessions	SEO	Week 12	Content load	Repurpose webinar

FL2 Checks

✅ Success condition	Leadership confirms budget, names owners, and unblocks required dev or design time — in writing
⚠️ Early warning	Sprints have deliverables but no numeric KPI targets next to them
❌ Failure mode	Plan requires new tooling or content volume your team cannot sustain — reduce scope and lead with MOFU proof assets first

---

Phase 8 — Executive and RFP Delivery

Time: ~2–3 hours | Day 6–7

Even strong plans fail if the deck is unclear. Use this structure to give executives and evaluators the what, why, how, and ROI in a single pass — and survive the Q&A.

Executive Summary One-Pager Template

1. Objective: State the north-star metric and its OKR tie-in
2. Top 3 moves this quarter: List each with expected KPI impact
3. Budget and capacity: Team days and cash costs
4. KPI targets: Each with a “why it matters” line
5. Risks and mitigations: 2 bullets maximum
6. Success definition: The in-quarter milestone that proves you’re on track

Filled example — SOC 2 SaaS:

Objective: Grow Sales Accepted Opportunities from content by 25% in Q3.

Top 3 moves: SOC 2 cluster build, MOFU comparison and case study, demo CVR uplift.

Budget: 120 team days, $10K partner webinar budget.

KPIs: +20% non-brand sessions, MOFU CVR 1.8%, 60 content-assisted SAOs. Why: increases new logo reach at lower CAC and shortens the sales cycle.

Risk: Dev time constraints. Mitigation: No-code form changes and prebuilt templates.

Success definition: 45 SAOs by week 8 and demo CVR at 2.5%.

---

12-Slide Deck Template

Slide	Content
1	Title and objective — north-star, OKR alignment
2	Current state and gaps — 5 diagnostic tiles with evidence
3	Audience and JTBD — 3 tiles with triggers and anxieties
4	Demand and topic model — top clusters and opportunity scores
5	Strategy and pillars — POV and 3H portfolio
6	Priority initiatives — top 6 items with ICE scores
7	Distribution plan — owned, earned, paid, repurposing
8	Measurement — GA4 tiles, attribution assumption, targets
9	90-day roadmap — sprints, owners, KPI targets
10	Budget and capacity — team days and cash costs
11	Risks and mitigations — 3 bullets with owner
12	Success definition and next check-in — what proves value by week 8

Rule: Every slide needs one number and one owner. Decks that over-index on theory fail in Q&A.

Financial translation: Convert key targets to pipeline impact wherever possible.

Example: “60 SAOs × 20% close rate × $40K ASP = $480K pipeline influenced.”

---

Q&A Prep: The 5 Questions Executives Always Ask

Prepare a one-paragraph answer for each of these before your presentation:

1. “Why will CVR improve to 2.5% at Sprint 1?”

Point to current benchmark (e.g., 1.1%), the specific UX fix being made (form placement, CTA copy, load speed), and a comparable change your team or a competitor made with documented lift. If you don’t have internal data, cite industry benchmarks and frame it as a conservative target.

2. “What if dev can’t support Sprint 1?”

The Sprint 1 conversion fix is scoped to no-code changes only (form tool swap, CTA text, button placement). No engineering dependency. Development resources are only required from Sprint 4 onward for the calculator.

3. “How do we know content is actually driving pipeline — not just correlation?”

We’ll use a content-assisted view in GA4: any opportunity where the contact had 2+ engaged sessions with content pages in the 30 days before converting. We’ll show this alongside last-click data and be transparent about what the model does and doesn’t prove.

4. “What happens if the partner webinar falls through in Sprint 3?”

We’ve identified a backup guest speaker and can run it as an internal thought leadership session. The content still gets produced; we lose the partner co-promotion reach but retain the asset value.

5. “Is this realistic for a small team?”

The roadmap is intentionally scoped to 120 team days across 12 weeks — approximately 10 team days per week across a Content Lead, part-time designer, and sales support. Experiments are capped at 10% of capacity. If dev or design become unavailable, Sprint 4 scope (calculator) compresses to a simpler template tool.

---

RFP Methodology Section Template

For agency or vendor proposals, include:

1. Framework overview: The 8-phase diagram and how it de-risks delivery
2. Discovery and diagnostics: JTBD interviews, GA4 and GSC audit, diagnostic scorecard
3. Strategy and planning: Pillars, topic model, ICE prioritization
4. Production and distribution: 3H asset plan, QA process, repurposing workflow
5. Measurement and reporting: GA4 setup, reporting cadence, KPI accountability
6. Team and governance: Roles, owner per KPI, decision gate cadence
7. Deliverables: Exact outputs with acceptance criteria
8. Timeline: 12 weeks with milestones

---

Glossary of Key Terms

Term	Definition
GA4	Google Analytics 4 — the current standard web analytics platform
GSC	Google Search Console — shows organic search performance data
JTBD	Jobs to Be Done — a framework for understanding what a customer is trying to accomplish
MOFU	Middle of Funnel — content targeting users in the consideration/evaluation stage
ICP	Ideal Customer Profile — the firmographic and behavioral profile of your best-fit buyers
ICE	Impact, Confidence, Effort — a prioritization scoring model
SAO	Sales Accepted Opportunity — a lead formally accepted by the sales team as qualified
ASP	Average Selling Price — the average revenue per closed deal
CAC	Customer Acquisition Cost — total cost to acquire one new customer
CVR	Conversion Rate — the percentage of visitors who complete a target action
PLG	Product-Led Growth — a go-to-market model where the product itself drives acquisition
PQL	Product Qualified Lead — a user who has demonstrated buying intent through product behavior
LTV	Lifetime Value — total revenue expected from a customer over their entire relationship
3H	Hero, Hub, Help — a content mix model balancing brand narratives, pillar content, and tactical guides
CPC	Cost Per Click — used in keyword research as a proxy for commercial intent
KD	Keyword Difficulty — a 0–100 score estimating how hard it is to rank for a keyword

---

Industry Tailoring Guide

This framework’s backbone stays identical across industries. Swap only the JTBD tiles, topic clusters, and proof assets:

Industry	Key proof assets	Priority JTBD triggers	North-star proxy
Fintech / RegTech	Compliance checklists, audit timelines, risk reduction calculators	Regulatory change, board-level audit, new market entry	Content-assisted compliance deals closed
Manufacturing	Lead time reduction data, spec sheets, distributor enablement kits	Supply chain disruption, product line expansion, dealer onboarding	Distributor inquiries from content
Healthcare / MedTech	HIPAA architecture diagrams, clinical workflow guides, security certifications	EMR integration, compliance review, procurement cycle	Demo requests from clinical decision-makers

---

Final Checklist Before You Send

• [ ] Backbone page approved with north-star metric, guardrails, and KPI targets — signed off in writing
• [ ] JTBD tiles validated by at least one sales or support representative
• [ ] Top 10 topics scored and ranked with composite ICE scores and assigned owners
• [ ] 90-day roadmap includes numeric KPI targets for every sprint
• [ ] GA4 dashboard tiles exist and each one maps to a slide in the deck
• [ ] Executive summary one-pager translates KPIs into pipeline or margin impact
• [ ] Q&A prep document covers the 5 most likely executive objections
• [ ] Glossary included or shared with stakeholders unfamiliar with marketing terminology

---

Conclusion

This framework gives you a rigorous, industry-tailored content strategy — one that holds up in Q&A because every decision traces back to a business OKR, a stated attribution assumption, and a realistic assessment of your team’s capacity.

The 5–7 day timeline is honest. The output is worth it: a defensible 12-slide deck, a pipeline-translated executive summary, and a 90-day roadmap your small team can actually execute. When anything wobbles in review, anchor back to the backbone and the stated assumptions — that’s your single source of truth.

Three variants. One evidence standard. No prose filler.

---

Step 0: Pick your variant in 2 minutes

Signal	Variant
Tomorrow’s board or VP meeting	Board deck
Investor checklist with data room	Diligence packet
Page limits and required headings from a buyer	RFP analysis

Deliverable shape:

• Board deck: 12–18 slides, visuals first, 1-page executive summary up front
• Diligence packet: 12–25 pages, narrative + appendix, explicit evidence IDs on every quantitative claim
• RFP analysis: 4–10 pages within page limits, headings mapped 1-to-1 to RFP, compliance matrix inline

---

Step 1: Lock numbers and disclosure before writing anything

Rework after drafting costs 2–4 hours. Lock these first.

Version register — one line, paste everywhere:

Model v[XX.YY.ZZ], [currency], data through [YYYY-MM-DD]. Revenue retention: NRR by activated-month cohorts. CAC payback: months to gross margin recovery on blended CAC. Pipeline coverage: [X]x next-quarter bookings, win-rate trailing 3 months. Customer identities redacted per NDA; revenue in bands.

Assumption decisions to make now:

• Cohort logic: activated date or first invoice date?
• Retention metric: logo or revenue? Which lookback window?
• CAC: blended or channel-split? Which cost lines included?
• Forecast drivers: pipeline coverage rule, win-rate source, ramp time, seasonality toggle on or off?
• Confidentiality: which customers are under NDA? Use “Top 10 fintech client” format or revenue bands?

Place the finalized version on slide 2 (Board) or page 1 (Diligence/RFP). Cross-reference it by name everywhere else — never restate the definition mid-document.

When the model isn’t ready at deadline:

• Use last locked version with a visible version tag and cut-off date
• Add one line on the assumptions page: “Model pending [specific update]; forecast bridge uses [version] as proxy”
• Flag which numbers will change and by when — do not silently use stale data

---

Step 2: Draft the executive summary first

Write this before any other section. It forces clarity on what the document is actually arguing.

5-sentence formula:

1. Situation and decision window
2. Numbers at a glance (3–5 KPIs, actual vs plan)
3. What drives the numbers (1–2 root causes)
4. Key risks and mitigations
5. The ask or next decision with specific owners and dates

Filled example — SaaS payments platform:

We are entering Q3 with a bookings gap against plan and must choose between accelerating mid-market expansion or deepening enterprise focus before tomorrow’s board session. YTD ARR is 18.4M vs plan 19.6M, NRR 116%, CAC payback 13.5 months, gross margin 71%. Shortfall is concentrated in enterprise where sales cycle extended to 142 days and win-rate dipped from 26% to 19%; mid-market self-serve grew 28% QoQ with 43% lower CAC. Primary risks are discount pressure in mid-market and potential churn from two enterprise accounts; mitigations include pricing guardrails, expanded onboarding playbooks, and dedicated save plans. Decision requested: approve Option B to prioritize mid-market for two quarters, reallocate 3 AEs and 600k OPEX, target ARR exit of 25.8M with NRR 118% and CAC payback under 12 months.

For RFP: after sentence 2 or 3, add one clause mapping to a scoring criterion — “addresses Section 3.1 Understanding and Section 3.3 Methodology.”

---

Step 3: Build each section by variant

A. Board deck — 12 to 18 slides

Slide order is fixed. One idea per slide. Numbers large, captions short.

Slide	Content	Prompt to use
1	Executive summary	5-sentence formula above
2	Assumptions and data scope	Version register from Step 1
3	Objectives and constraints	3 bullets: objective, timeframe, constraints — under 40 words each
4	Business model snapshot	4 bullets: revenue streams, segments, cost drivers + 1 diagram caption
5	Market and customer	5 bullets: ICP, segments, TAM/SAM method, top personas, 2 recent customer insights with dates
6	Performance vs plan	5 KPIs actual vs plan with % variance and 1-line driver each. State cut-off date and source.
7	Unit economics	5 bullets: pricing/ARPA, CAC, LTV, contribution margin, sensitivity
8	Forecast bridge	5 steps: actuals → adjustments → plan. Every step has a number.
9	Strategic options	2–3 options: benefits, costs, time-to-impact, KPI impact range
10	Risks and mitigations	Top 5 risks: likelihood, impact, mitigation owner
11	Decision and next steps	Decision required + 3 next actions with owners and dates

Unit economics slide — filled bullets:

• Pricing: tiered SaaS + 15 bps payment take-rate; blended ARPA 1,460 USD MRR Q2
• CAC: blended 22.8k USD; payback 13.5 months at 71% gross margin
• LTV: 5.9x CAC based on 116% NRR and 1.3% monthly logo churn
• Contribution margin: 54% after variable processing fees and support
• Sensitivity: 2-point NRR change moves LTV:CAC by ~0.5x

Finish Line 2: VP or chair acknowledges in writing the decision option to be brought to vote. Materials include 1-page executive summary + decision slide with owners and dates. If they defer: add forecast bridge and 3 numbers on the decision slide — budget required, expected ARR impact, payback timeline.

---

B. Diligence packet — 12 to 25 pages

Every quantitative claim gets a Source: E0xx tag. No exceptions.

Section	Content	Evidence needed
1. Company overview	1-page overview linking business model to financial model tabs and version. List sheet names and what each drives.	Model version tag + tab names
2. Market and competitive	Market size logic in 6 bullets. Top 5 competitors with positioning statements and validation dates.	TAM/SAM sources with dates
3. GTM and pipeline	Pipeline as of [date]: coverage, stages, win-rates, cycle time, 3 anonymized logos with ARR bands and contract dates.	CRM export file + timestamp
4. Cohort and retention	12-month revenue retention, logo churn, expansion drivers, 2 cohort charts.	Cohort export with filter logic
5. Unit economics	CAC by channel, gross margin by product, payback, LTV:CAC with definitions. Replication notes included.	Defined per assumptions page
6. Financial model	Revenue build logic, key assumptions, 2 bridges: bookings-to-revenue and actuals-to-forecast. Cite cell ranges or tabs.	Model version + cell refs
7. Legal and compliance	Key contracts, regulatory scope, certifications, open issues with owners and target close dates.	Legal sign-off on disclosure
8. Risks and mitigations	Top 8 risks: likelihood, impact, mitigations cross-referenced to model sensitivities.	Model sensitivity tabs
9. Evidence index	ID, title, file path, timestamp, privacy tag, replication steps for 3 critical charts.	See evidence format below

DD checklist → section mapping:

Typical DD item	Section
TAM/SAM/SOM with method	2 Market
Churn, retention, cohorts	4 Cohort
CAC, LTV, gross margin	5 Unit economics
Pipeline, win-rate, ARR bands	3 GTM
Model assumptions and bridges	6 Financial model
Contracts and compliance	7 Legal
Risk register	8 Risks
Data room and evidence	9 Evidence index

Finish Line 2: diligence lead emails that checklist item is satisfied with no outstanding evidence requests and all claims cited by evidence IDs. If they pause: check that risks are not downplayed and KPI definitions match the assumptions page exactly.

---

C. RFP analysis — 4 to 10 pages

Before writing: read the scoring rubric first.

Most RFPs publish scoring weights by section. Before allocating word count, rank sections by weight:

• Highest weight (often Methodology or Technical Approach): maximum detail, specific proof points, measurable outputs
• Mid weight (Staffing, Implementation): concise, owners named, timelines realistic
• Lowest weight (Understanding, Compliance): 1–2 paragraphs, confirm and move on

Do not write equal-length answers for unequal-weight sections. Evaluators score what they weight.

Heading rule: use the RFP’s exact heading text and numbering. Evaluators score against a rubric that matches headings — a renamed section may score zero even if the content is correct.

RFP section	Content	Length guidance
[3.1] Understanding of requirements	Restate problem in buyer’s terms. 5 bullets. Map to a KPI the buyer cares about.	Proportional to weight
[3.3] Approach and methodology	6–8 steps, 1 line each: tool, timeline, measurable output	Highest weight section — expand here
[3.4] Implementation and staffing	Phased plan with owners and durations. Named individuals if allowed.	Mid weight
[3.5] Value and differentiation	4 differentiators, each tied to buyer outcome + referenceable proof point with date	High weight if scored
[3.6] Risk management	Top 5 risks: mitigations + early-warning indicators	Mid weight
[3.7] Assumptions and dependencies	What you need from buyer. What is out of scope.	Low weight — be brief
[3.8] Compliance statement	Declare compliance. List exceptions. Point to section + exhibit for each requirement.	Required — cannot skip

Value and differentiation — filled bullets:

• Payment success optimization improves approved transaction rate from 93.2% to 96.1% within 30 days using adaptive retries and issuer routing; evidenced by 280 bps uplift for a mid-market subscription customer Q1 2026
• Go-live in 15 business days with prebuilt connectors to Shopify and Chargebee; last 3 implementations averaged 12 business days from SOW to first transaction
• Cost visibility via margin dashboard surfacing scheme fees and network costs; finance teams received weekly automated cost variance reports Q2 2026
• 24×7 merchant support, SLA first response under 5 minutes chat / 30 minutes email for P1; April–June 2026 average 3 minutes chat first response

Finish Line 2: internal approver confirms every required heading present, within page limits, mapped to scoring criteria. If evaluators score low on methodology: each step needs a measurable output, not just a description of activity.

---

Step 4: Build the evidence spine

Attach to every quantitative claim. Do this as you write — retrofitting takes twice as long.

Evidence ID format:

E[###]: [filename].[ext] — generated [YYYY-MM-DD HH:MM UTC] — [Internal only / Restricted / Public] — Source: [system/view/report] — Filter: [applied filters]

Three entries ready to copy and adapt:

E014: Revenue_retention_cohort_export.csv — 2026-06-25 19:15 UTC — Internal only — Snowflake view bi.cohort_rr — Filter: activated_date <= 2025-06-30

E022: CRM_pipeline_snapshot_2026-06-24.xlsx — Internal only — Salesforce report Q2 Pipeline by Stage — Snapshot 2026-06-24

E031: Pricing_policy_v2026-03.pdf — Restricted — Legal-approved pricing

Replication notes for critical charts (required for Diligence): For each chart, record: data export used, filters applied, computation steps, and who can re-run it. One paragraph per chart is enough. The test: can someone else reproduce the chart from your notes without asking you a question?

Evidence spine failure signals:

• Reused charts with no export timestamps
• KPI definitions differ between sections
• Sources missing privacy tags or file paths
• RFP answers claim compliance without pointing to exact section or exhibit

---

Step 5: Risks, scenarios, and model tie-in

Scenario setup — 3 columns, fill for your context:

Driver	Downside	Base	Upside
Win-rate	19%	22%	26%
Sales cycle	142 days	128 days	115 days
CAC payback	14.2 months	12.8 months	11.6 months
ARR exit	24.0M	25.1M	26.6M

Early-warning triggers (make these measurable):

• If monthly logo churn exceeds 1.6% for 2 consecutive months → invoke hiring freeze for enterprise, reallocate 2 AEs to mid-market
• If pipeline coverage falls below 2.5x → trigger weekly pipeline review with CRO
• If enterprise cycle time exceeds 150 days for 2 months → switch to Option B

Model tie-in — cite exactly:

Downside scenario: Tab GTM_Drivers, cells C18:C22, win-rate adjusted from 26% to 21%. ARR impact: Tab Revenue_Build, cell F44.

---

Step 6: Pre-submission cross-check

Run this before calling it done. Each item is a yes/no.

Numbers consistency:

• [ ] All KPIs match model version stated on assumptions page
• [ ] KPI definitions are identical across all sections
• [ ] Forecast bridge reconciles actuals to plan with explicit line-item drivers
• [ ] Cut-off dates stated on every data exhibit

Evidence completeness:

• [ ] Every quantitative claim has a Source: E0xx tag
• [ ] Evidence index includes file path, timestamp, and privacy tag for each ID
• [ ] Replication notes written for at least 3 critical charts (Diligence) or key proof points (RFP)
• [ ] Redactions applied and noted where NDA applies

Variant-specific:

Board:

• [ ] Decision slide has 3 numbers: budget required, expected ARR impact, payback timeline
• [ ] 1-page executive summary matches slide 11 decision exactly

Diligence:

• [ ] DD checklist mapped — no open items without a documented constraint and timeline
• [ ] Risks section has likelihood, impact, and mitigation for each item

RFP:

• [ ] Headings match RFP word-for-word and in order
• [ ] Page or word limits respected — checked against highest-weight sections first
• [ ] Compliance statement points to exact section and exhibit for each requirement
• [ ] Each differentiator tied to a buyer outcome and a dated proof point

Common failure modes to catch in this pass:

• Boilerplate claims without a proof point or date
• Contradictions between narrative and model assumptions
• Different timeframes used across charts without a note explaining it
• Claims that cannot be disclosed under current NDAs but weren’t redacted

---

Appendix: prompts ready to paste

Executive summary — paste with your numbers:

Write a 5-sentence executive summary for a board deck. Model v23.06.27, data through 2026-06-25. KPIs: ARR 18.4M vs plan 19.6M, NRR 116%, CAC payback 13.5 months, gross margin 71%. Options: A — double down on enterprise; B — prioritize mid-market for 2 quarters. Risks: discount pressure mid-market, churn risk 2 enterprise accounts. Ask: approve Option B, reallocate 3 AEs and 600k OPEX, target ARR exit 25.8M, NRR 118%, payback under 12 months.

Diligence cohort section — variable template:

Using E014 cohort export and definitions on the Assumptions page, summarize 12-month revenue retention, logo churn, and top 2 expansion drivers. Provide 2 bullets on methodology. Add Source: E0xx tag after each claim.

RFP methodology section — variable template:

Under heading [3.3] Approach and Methodology, describe an 8-step plan to achieve the buyer’s objective of [specific outcome] within [timeframe]. For each step: name the tool or method, state the timeline, and state the measurable output. Map each step to RFP Section 3.3 scoring notes. Keep under [word limit].

Unit economics section — variable template:

Summarize unit economics using this data: [ARPA], [blended CAC], [gross margin %], [NRR %], [logo churn %]. Compute LTV:CAC ratio. Show a sensitivity: how does LTV:CAC move if NRR changes by 2 points? Format as 5 bullets. State data source and cut-off date.

Most “2026 SEO guides” do one of two things: recycle evergreen principles under a new year’s label, or chase AI headlines while abandoning the fundamentals that still determine whether a page ranks. This guide does neither.

Every item here is either confirmed by Google’s own documentation and Search Status Dashboard, or backed by dated third-party research with disclosed methodology. Items are labeled so you know exactly what you’re working with.

---

How to read this guide

Three types of content appear here, labeled clearly throughout:

• Evergreen, still enforced — principles Google has confirmed remain active in 2026 core update cycles
• New or meaningfully changed in 2026 — confirmed via Google Search Status Dashboard, Search Central documentation updates, or Google I/O 2026 announcements
• Measure with your own data — directionally supported by research, but impact varies enough by industry that your Search Console is the only reliable signal

---

Part 1: The 2026 ranking environment — what confirmed updates actually changed

Before optimizing anything, understand what happened to the ranking system this year.

Confirmed updates in 2026

Google confirmed four search-related ranking incidents in 2026 through its Search Status Dashboard: the February 2026 Discover Core Update, the March 2026 spam update, the March 2026 broad core update (completed April 8), and the May 2026 broad core update (completed June 2). A June 2026 spam update was also confirmed. A separate wave of community-reported ranking movement around June 19 was not confirmed by Google and should not be treated as a named update.

Both broad core updates followed the same pattern Google has used since 2022: no target list, no penalty framing, and the same official message — “a regular update designed to better surface relevant, satisfying content for searchers from all types of sites.” What that means in practice is that both updates reassessed the same cluster of signals: content quality, E-E-A-T, and whether pages add something that does not already exist across competing results.

Important for 2026 specifically: the May core update launched two days after Google I/O 2026, the same week Google deployed Gemini 3.5 Flash as the default model powering AI Mode globally. This means ranking changes and click behavior shifts from AI feature expansion happened simultaneously, making clean diagnosis harder than in any prior update cycle. A page can hold its rankings and still see click declines because AI Overviews or AI Mode are absorbing traffic on those queries. Separate these two forces before drawing conclusions from your data.

The structural shift: ranking position is no longer the only visibility metric

This is the single most important change to understand before building any 2026 SEO plan.

Approximately 68% of Google searches in the US between January and April 2026 ended without a click to any external website. AI Mode has surpassed one billion monthly users, with queries more than doubling every quarter. Position one organic CTR on queries where AI features appear has dropped to as low as 11% on some query types, down from 27%.

This does not mean SEO is less important. It means the definition of SEO visibility has expanded. The optimization target is no longer only “rank in position 1.” It is “appear in organic results AND earn citation in AI Overviews AND remain eligible in AI Mode.” These are three distinct surfaces, and performance in one does not guarantee performance in another — only about 14% of URLs cited in AI Mode overlap with URLs cited in AI Overviews.

The measurement implication: clicks alone no longer capture full visibility. Brand mentions inside AI Overviews, citation frequency, and impression trends alongside CTR trends are all now necessary parts of performance reporting.

---

Part 2: Content quality — the evergreen criteria Google keeps reconfirming

These signals have been part of Google’s core ranking systems for years. They are listed here because both 2026 broad core updates confirmed they remain the dominant evaluation cluster, and because the implementation standards have gotten more specific.

E-E-A-T at the template level

Experience, Expertise, Authoritativeness, and Trustworthiness (E-E-A-T) is the framework Google’s quality raters use to evaluate content. It has been part of the Search Quality Evaluator Guidelines since 2022 and was reinforced as the primary signal cluster in both the March and May 2026 core updates.

What 2026 made more specific:

Author credentials are no longer optional for competitive niches. Named, credentialed author bios linked to bio pages with qualifications and LinkedIn profiles are a confirmed ranking factor for YMYL content (health, finance, legal). The implementation target is the template level — every article or guide template should have author fields, reviewer fields, and revision metadata exposed to users.

Practical implementation:

• Author bio page with credentials, area of expertise, and verifiable external profiles
• Reviewer byline for YMYL content with professional credentials stated
• Visible last-updated date on all content that covers changing topics
• Citations section with outbound links to authoritative sources on any factual claims
• Original evidence blocks: first-party data, process documentation, experiments, or case studies with inputs and outcomes

Content that adds something that does not exist elsewhere

Both 2026 core updates consistently penalized pages that repackage existing information without adding original value. Google’s standing guidance through the May 2026 announcement: “There’s nothing new or special that creators need to do for this update as long as they’ve been making satisfying content meant for people.”

The inverse of that statement is the practical standard: content that exists only to rank — scraped, summarized, or rehashed from sources that already cover the topic — is consistently the biggest loser in every 2026 core update. AI-generated content is not the problem; unedited, generic, mass-produced AI content that adds no original value is.

Original value signals that work:

• First-party research or proprietary data with methodology disclosed
• Case studies with specific inputs, controls, measurement windows, and outcomes
• Expert interviews or SME-sourced insights not available elsewhere
• Process documentation from direct practitioner experience

Helpful Content as part of core ranking systems

The Helpful Content Update, announced in 2022, was absorbed into Google’s core ranking systems in March 2024 and remains active as a component of the broader quality evaluation that core updates recalibrate. It is not a separate system to optimize for — it is baked into every core update assessment.

The signal it looks for: is this content primarily created to help people, or primarily created to rank? Pages that fail this test at scale tend to see site-wide suppression, not just page-level ranking drops.

Content format matched to result types

Different query intents trigger different result types, and format should match the result type you are competing for.

By intent:

• Commercial research queries: comparison pages, best-of lists, integration pages, solution-by-role pages
• Transactional queries: product or service pages with structured data, specs, FAQs, reviews, availability
• Problem-led informational queries: how-tos, checklists, calculators, first-party data studies
• YMYL or regulated topics: expert review, citations, disclaimers, and revision logs are non-negotiable

AI Overview exposure by intent (measure with your own data): Informational queries trigger AI Overviews in approximately 88% of cases. Transactional and navigational queries are largely protected — ecommerce queries trigger AI Overviews only about 4% of the time. B2B technology queries see the highest exposure at around 70%. These numbers vary by market and vertical; validate against your own Search Console before making strategy decisions.

---

Part 3: Technical SEO — foundations that remain non-negotiable

Technical SEO fundamentals have been stable for years. They are included here because they remain the prerequisite for everything else: no amount of content quality or link authority overcomes pages that Google cannot reliably crawl, render, and index.

The four pillars of technical eligibility

1. Discoverability

Google primarily finds pages through links from pages it has already crawled. Internal linking is how you signal which pages are important and how they relate to each other. Pages reachable from the homepage in three clicks or fewer are treated as higher priority. PageRank — Google’s foundational importance-scoring system — flows through internal links. A strong internal link from a high-authority page can provide more indexation priority than a weak external backlink.

Structural best practices:

• Pillar-cluster architecture: broad pillar pages link to tightly-focused cluster pages, which link back to the pillar. Bi-directional linking concentrates topical authority.
• XML sitemaps: include only indexable, canonical URLs. Update lastmod dates only when actual content changes are made — Google detects inaccurate lastmod data and discounts it.
• For faceted navigation: block parameter URLs in robots.txt rather than relying on noindex. Noindex still requires a crawl to see the directive and keeps consuming crawl budget; blocking at robots.txt level stops the crawl before it starts.

2. Crawlability

Crawl budget is finite. Wasting it on low-value or duplicate URLs means important pages get crawled less frequently.

• robots.txt: use to block parameter URLs, duplicate pages, and faceted navigation variants that should not be indexed
• Ensure fast server response times — slow servers reduce crawl frequency
• Avoid crawl traps from infinite scroll, session parameters, or uncontrolled faceted navigation

3. Indexability

Crawling and indexing are not the same. Pages can be crawled and not indexed (“Crawled — currently not indexed” in Search Console is the signal to watch).

• Canonical tags: must point to indexable pages — never to 404s, redirects, or noindex pages
• Noindex: use precisely. A noindex page still gets crawled; it just stays out of the index
• Unique content: duplicate content across URLs is a primary indexability problem. Consolidate thin pages; redirect the others
• Domain verification in Google Search Console: required for Aggregated Event Measurement to function and for structured data rich results eligibility at scale

4. Renderability

Google uses mobile-first indexing — the mobile version of a site is what gets crawled, indexed, and ranked, regardless of which device most users prefer.

• All primary content and internal links on the desktop version must also be present and functional on the mobile version
• Critical content and links must be present in server-rendered or reliably renderable HTML. Client-side rendering that hides primary content from Googlebot blocks indexing
• Defer non-critical JavaScript and third-party tags that block main content from loading

Core Web Vitals — still a ranking factor, functions as tiebreaker

Google confirmed Core Web Vitals as a ranking factor in 2021. They remain part of the Page Experience signal in 2026. In competitive niches, failing them creates a structural disadvantage even when content and authority signals are strong.

2026 thresholds (must be met for at least 75% of page visits):

• LCP (Largest Contentful Paint): ≤ 2.5 seconds — Good; 2.5–4.0 seconds — Needs Improvement; > 4.0 seconds — Poor
• CLS (Cumulative Layout Shift): ≤ 0.1
• INP (Interaction to Next Paint): ≤ 200ms

Common causes of failure: third-party scripts (chat widgets, ad tags, tracking pixels) are the most common LCP and INP killers. Fix at the template level — one template fix multiplies improvement across every page using it.

Structured data — eligibility, not ranking

Google has confirmed repeatedly that structured data is not a direct ranking factor. What it does is determine eligibility for rich results in organic search AND provide structured signals that AI systems use when selecting sources for AI Overviews and AI Mode responses.

Confirmed changes in 2026:

• FAQ rich result has been removed from Google Search entirely as of May 2026. Remove FAQ schema from non-government, non-health sites — it no longer produces any benefit and adds implementation overhead.
• FAQPage schema is now restricted to government and health websites only. Implementing it on a marketing or ecommerce site violates Google’s guidelines.

Five schema types with confirmed value in 2026:

1. Organization — the entity foundation. Establishes your brand as a recognized entity in Google’s Knowledge Graph. Use sameAs to link to authoritative external profiles. Highest-leverage starting point for any site.
2. Article / BlogPosting — with nested Person schema for the author. Author attribution is a confirmed E-E-A-T signal.
3. Product — for ecommerce. Include AggregateRating (required for star ratings), price, availability. Partial implementation produces zero rich result lift — completeness is non-negotiable.
4. HowTo — for instructional content with discrete steps.
5. LocalBusiness — for sites with physical locations.

Implementation rules:

• Use JSON-LD format only. Google recommends it; it stays separate from visible HTML and is easier for AI crawlers to parse.
• Validate with the Rich Results Test and Schema Markup Validator before deploying.
• Monitor the Enhancements report in Google Search Console after deployment for errors and warnings.
• Never mark up content that is not visible to readers of the page.

HTTPS and security

HTTPS remains a confirmed ranking signal. Any site still serving on HTTP has a baseline ranking disadvantage that no content improvement can offset.

---

Part 4: New in 2026 — what you need to add to your plan

These items either did not exist before 2026 or have changed materially enough that prior playbooks do not cover them.

Preferred Sources — audience loyalty as a direct visibility signal

Google added Preferred Sources documentation for website owners in early 2026 and expanded the feature to all languages globally. It allows users to choose websites they want to see more of in search results, including inside AI Overviews and AI Mode.

This is the first time audience loyalty has functioned as a direct visibility signal in Google Search. It does not change organic rankings directly, but it increases the likelihood that your content appears for users who have added you as a preferred source.

Practical action: Prompt your existing newsletter subscribers, social followers, and returning readers to add you as a preferred source. Google provides a button template for publishers. This is a meaningful lever specifically for publishers and content sites with established audiences.

AI crawlers — most sites are unintentionally blocking them

In a single month of late 2024, GPTBot and ClaudeBot combined made requests equivalent to approximately 20% of Googlebot’s volume. By 2026, AI crawlers collectively represent a meaningful share of server traffic. Yet many sites are unintentionally blocking them through legacy robots.txt configurations written before these crawlers existed.

Audit action: Review your robots.txt for rules that block GPTBot, ClaudeBot, PerplexityBot, and other AI crawlers. If your goal is to be cited by AI systems, blocking their crawlers defeats that goal entirely.

Two AI surfaces require separate measurement and optimization

Ranking well in organic results supports visibility in AI Overviews. Being recognized as an authoritative, clearly structured source supports citation in both AI Overviews and AI Mode. But only about 14% of URLs cited in AI Mode overlap with AI Overview citations — optimizing for one surface does not transfer automatically to the other.

Measurement actions:

• In Google Search Console, filter your Performance report by query type. Look for a pattern where informational queries lose clicks while branded and transactional queries hold steady — that signature points to AI Overview cannibalization rather than a core update penalty. The two have different fixes.
• Monitor AI Overview citation separately from organic ranking. Tools like Ahrefs, Semrush, and SE Ranking have added AIO tracking — use them alongside Search Console.

Citation rate — the new KPI for informational content

For informational queries, citation rate (how often your site is selected by AI as a source) is now as important as click-through rate. Approximately 40% of sources appearing in AI Overviews rank in positions 11–20 on the SERP — outside the traditional top-10 that SEO tools optimize for.

Content signals that improve citation likelihood:

• Direct, structured answers early in the page (before elaboration)
• Original data, research, or insights not available in competing sources
• Clear author credentials and entity signals (Organization schema with sameAs profiles)
• Structured data that makes content machine-readable and extractable

Zero-click is permanent on informational queries — adjust how you measure success

Approximately 68% of US Google searches end without a click. On informational queries where AI Overviews appear, this is not a problem to solve — it is the new baseline. Traffic will not recover to pre-AI baselines on queries where AI features dominate.

The measurement adjustment: shift primary KPIs for top-of-funnel content from sessions and pageviews to brand citation rate, impression share in AI surfaces, and downstream pipeline metrics. Reserve sessions and revenue metrics for mid-funnel and transactional content where AI features have lower penetration.

---

Part 5: Measurement framework — what to track and when to draw conclusions

The core update diagnosis protocol

When a confirmed core update completes, follow this sequence before making any changes:

1. Confirm the update has finished rolling out on the Google Search Status Dashboard.
2. Wait at least one full week after the completion date before pulling data. Rankings fluctuate mid-rollout and produce false conclusions.
3. Compare a clean post-update week against the equivalent week before the update started. For May 2026: compare data from approximately June 9 onward against data before May 21.
4. Separate ranking changes from click behavior changes. A stable ranking with declining CTR is an AI Overviews signal, not a core update signal. Different diagnosis; different fix.
5. If rankings dropped, start with Search Console sorted by biggest position decline. Group fallen URLs by shared characteristics — same content type, same topic cluster, same author, or no author. The shared characteristic is the cause.

Do not do: make major content or structural changes during an active rollout. Core update data is unstable until Google confirms completion. Reactive changes during volatility produce interventions you cannot evaluate and often cannot reverse cleanly.

Baseline metrics to extract before building any plan

From Google Search Console:

• Last 90 days by Page and by Query: clicks, impressions, CTR, position
• Segment by template or directory to map to business areas
• Search Appearance report to identify current rich result eligibility
• Core Web Vitals report for template-level performance issues

From GA4:

• Organic landing pages with sessions, conversion rate, and revenue or value per session
• Map landing pages to templates or product groups

Merged view: join by URL, roll up by template and product line, compute revenue per organic session. This is the baseline your forecast model runs from.

Forecast model structure

A defensible model for leadership follows this chain:

• Volume change = baseline impressions × expected change in visibility or eligibility
• Click change = volume change × expected CTR delta for the new surface or position
• Session change = click change × landing page session realization rate
• Revenue change = session change × revenue per session

Use ranges (optimistic, realistic, conservative) and apply a confidence factor per initiative based on evidence strength. High confidence when backed by primary-source eligibility and proven template analogs. Lower confidence when content-creation-dependent.

Prioritization scoring for initiatives

For teams with limited capacity, this scoring model survives executive scrutiny:

Priority score = (Impact × Confidence) / (Effort × Risk)

• Impact: expected monthly revenue uplift, scored 1–5
• Confidence: strength of evidence from primary sources and internal analogs, scored 1–5
• Effort: team-weeks across content, dev, design, analytics, scored 1–5
• Risk: reversibility and blast radius, scored 1–5. 1 = easily reversible, low risk; 5 = hard to undo, high risk

Quick illustrative scoring:

• Fix duplicate canonicals on top 50 revenue URLs → (4×5)/(2×2) = 5.0 — do first
• Add Product schema to PDPs with missing eligibility → (4×5)/(3×2) = 3.3 — do next
• Build 10 integration pages with partner alignment → (5×4)/(4×2) = 2.5 — schedule
• Migrate legacy blog to clean URL structure → (3×3)/(4×3) = 0.75 — deprioritize

---

Part 6: 30/60/90 delivery structure with owners and dependencies

Day 0 alignment

Confirm target templates, owners, and gating risks. Share prioritization scores and expected revenue ranges. Attach capacity confirmations from Engineering and Content leads before presenting to leadership — timelines without resource confirmation do not survive the first sprint planning session.

Days 1–30: unblock eligibility and indexing

Owners: SEO lead, Dev lead, Analytics

Deliverables:

• Canonical and robots fixes on top 50 revenue URLs
• Structured data implemented on PDPs and guides, validated with Rich Results Test
• Remove FAQ schema from all non-government, non-health templates
• Review robots.txt for AI crawler blocking — unblock GPTBot, ClaudeBot, and PerplexityBot if citation visibility is a goal
• Fresh sitemaps for key templates submitted to Search Console
• Baseline dashboards pulling Search Console and GA4 data by template

Dependencies: engineering sprint slot, QA bandwidth, tag management access

Days 31–60: expand content with E-E-A-T and entity coverage

Owners: Content lead, SMEs, Design

Deliverables:

• Author bios and reviewer flows live on all guide templates
• Internal link passes from hub pages to commercial pages
• Organization schema with sameAs profiles live sitewide
• First 5 content pieces with original first-party evidence blocks or SME-sourced insights
• Preferred Sources button integrated into newsletter and social follow-up sequences

Dependencies: partner approvals, SME time, design components

Days 61–90: optimize and prove

Owners: SEO lead, Analytics, Content

Deliverables:

• CTR experimentation on titles and meta descriptions for top 100 pages
• Core Web Vitals audit at template level with third-party script inventory
• Pre-post impact readout with control pages, Search Appearance gains, and AI Overview citation tracking
• AI surface monitoring setup: AIO citation tracking separate from organic ranking

Dependencies: analytics event QA, experiment guardrails

---

Part 7: Communicating the plan to leadership

Plain-language translations for non-technical stakeholders

Technical term	Plain language
Core update	Google periodically recalibrates which pages it considers the most helpful. Our rankings shift based on how we compare to competitors on quality signals.
E-E-A-T	Google checks whether our content was written by someone with real experience and credentials, and whether our site is recognized as trustworthy in our field.
Structured data	Code we add to pages that tells Google exactly what type of content it is — product, article, business — so it can display richer results.
Core Web Vitals	Three speed and stability measurements Google uses as a tiebreaker in competitive rankings.
AI Overview citation	Our content appearing inside Google’s AI-generated answer boxes — separate from ranking in the regular link list below it.
Zero-click searches	Searches where Google answers the question directly and users don’t click through to any website. About 68% of US searches now end this way.
Preferred Sources	A feature where Google users can select websites they always want to see. Getting added as a preferred source by our existing audience increases our visibility for those users.

One-page executive summary structure

Header: 2026 SEO plan — eligibility first, entity coverage second, AI surface visibility third

Why now: the March and May 2026 core updates reinforced the same direction — content with genuine depth, credible authorship, and original value. Simultaneously, AI Mode and AI Overviews have become the primary discovery surface for informational queries, requiring separate optimization and new measurement approaches.

Three numbers:

• Effort: [team-weeks or budget]
• Expected monthly revenue impact: [conservative to realistic range]
• Time to first eligibility signal: 2–4 weeks for structured data and canonical fixes; 4–8 weeks for new content

Top 3 initiatives with dates and owners:

1. [Initiative] — Owner [Name] — [Date]
2. [Initiative] — Owner [Name] — [Date]
3. [Initiative] — Owner [Name] — [Date]

Proof: primary source — Google Search Status Dashboard, confirmed updates March and May 2026. Internal analog: [page or template], [measurement window], [observed change].

Risks and mitigations:

• Engineering bandwidth → scope to top 80% revenue URLs first
• AI surface changes during rollout → delay measurement by one week post-confirmation

Anticipating objections

“Is this based on speculation?” Every recommendation here ties to a confirmed Google update, Search Central documentation change, or internal replicated result. The source and date are in the footnotes.

“When will we see a signal?” Eligibility signals (structured data rich results, canonical consolidation) appear in Search Appearance within 2–4 weeks post-deploy. Content improvements signal in the next named core update cycle, typically 6–12 weeks out. We schedule the first checkpoint at week 4.

“What if engineering is delayed?” Content-first track preserves week-4 checkpoint integrity — author bio implementation and internal link passes require no engineering. Structured data is the item that slips; we document the delay and adjust the forecast confidence factor down.

---

Common mistakes to avoid

Mistake	Why it matters	Fix
Making changes during a core update rollout	Data is unstable until rollout completes — interventions cannot be evaluated	Wait for confirmed completion, then wait one additional week
Treating ranking drop and CTR drop as the same problem	Different causes, different fixes	Separate diagnosis: ranking drop = core update signal; CTR drop with stable ranking = AI Overview absorption
Reacting to single-day AI Overview data	Citation overlap and CTR on AI queries fluctuates daily	Use 30-day rolling averages for AI surface metrics
Implementing FAQ schema on non-health/government sites	Google removed FAQ rich results entirely; FAQPage schema is now restricted	Remove FAQ schema from all ineligible templates
Blocking AI crawlers in legacy robots.txt	Prevents citation in AI Mode and AI Overviews	Audit robots.txt and explicitly allow GPTBot, ClaudeBot, PerplexityBot
Measuring top-of-funnel content by sessions only	Zero-click is structural on informational queries	Add citation rate and impression share as primary KPIs for informational content
Optimizing for AI Overviews and assuming it covers AI Mode	Only 14% URL overlap between the two surfaces	Track each surface separately in Search Console and third-party tools
Publishing volume without original evidence	Consistently the biggest loser category in every 2026 core update	Every piece needs at least one thing that does not exist in competing coverage

---

Source notes

All Google documentation references: Google Search Central (developers.google.com/search), accessed June 2026.

Confirmed update dates: Google Search Status Dashboard (status.search.google.com), March 27 – April 8 2026 (March core update); May 21 – June 2 2026 (May core update); June 2026 spam update.

AI Overview statistics: Seer Interactive longitudinal study, 2.43 billion impressions across 53 brands, published April 2026. SparkToro/Datos zero-click data, January–April 2026. SISTRIX CTR data, March 2026.

AI Mode user data: Elizabeth Reid, VP of Search at Google, Google I/O 2026, May 19 2026.

AI surface overlap data: multiple third-party studies, 2026, consistent finding of approximately 14% URL overlap between AI Mode and AI Overview citations.

Industry-level AI Overview exposure: WebFX 2026 benchmarks; NP Digital analysis of 8 million queries across 38 countries.