Chapter 29 — Further Reading

Reporting is a topic where the primary sources are the tools themselves: the two free platforms that produce almost every number you should report, plus the free dashboard builder that assembles them. Read Google's own documentation for what each metric actually counts — because the whole discipline of honest reporting rests on knowing that, and on being able to explain why two tools disagree. Treat every vendor's "KPI framework" and "authority score" as a claim to be checked against how the business actually makes money. The items below are grouped by how much you can trust them, in the spirit of the chapter.

Tier 1 — Canonical (start here; free and authoritative)

• Google Search Console — the Performance report documentation. What impressions, clicks, click-through rate, and average position mean, and how the data is filtered and (sometimes) anonymized. This is the source of the search-side half of your dashboard and the ground truth for branded-vs-non-branded query analysis.
• Google Search Console — the Page Indexing (Index Coverage) report documentation. The authoritative source for the "indexed pages" KPI: what "indexed," "crawled — currently not indexed," and "discovered — currently not indexed" mean, and why more indexed pages is not automatically better. Read with Chapters 14 and 27.
• Google Search Console — the Core Web Vitals report documentation. The field-data (CrUX) status for LCP, INP, and CLS — the source for the CWV KPI and the honest note that it is a page-experience floor, not a growth lever (Chapter 16).
• Google Analytics Help — GA4 documentation on events, key events (conversions), engagement metrics, and attribution. The source for the site-side half of your dashboard: how GA4's event model works, how a "key event" is defined, what engagement rate/engaged sessions measure, and how attribution models credit a conversion. Essential for reporting an organic conversion honestly (Chapter 28).
• Google Analytics Help — consent mode and data thresholds. Why measured conversions undercount reality and why the number you report is a floor, not a full count — the privacy caveat §29.3 insists on (conceptual only; this is not legal advice on GDPR/CCPA).
• Looker Studio Help — connecting Search Console and Google Analytics 4 data sources. How to build the free, auto-updating one-screen dashboard of §29.3, and how to blend or (better) clearly separate the two sources so their different numbers are each labeled.
• Google's announcement of the Universal Analytics sunset (March 2022) and the GA4 migration guidance. The public record behind Case Study 1: the dates, the event-based model, and why historical UA data did not carry forward. A permanent lesson in why a baseline is infrastructure you must protect.
• Google Search Central — guidance on how long SEO takes / "how to handle a decline in Google Search." Google's own framing that search changes take time and that recovery is about genuine improvement over weeks and months — the Tier-1 backbone of the long-game expectations conversation (§29.6) and the "results in 30 days" myth.

Tier 2 — Reputable secondary (useful, but verify against Tier 1)

• Analytics thought leadership on actionable vs. vanity metrics — for example, Avinash Kaushik's long-running writing on the "so what?" test and on tying metrics to business outcomes (acquisition, behavior, outcomes). Excellent for building the instinct behind §29.1–§29.2; read it as a way of thinking, not a fixed metric list.
• SEO tool vendors' guides to KPIs, dashboards, and share of voice (Ahrefs, Semrush, Moz). Genuinely useful for dashboard mechanics and for definitions like share of voice — but read with the chapter's skepticism intact: these same vendors sell Domain Authority / Domain Rating, so confirm any claim that a score reflects how Google ranks against Google's own docs, and keep vendor scores off the value report.
• Practitioner writing on SEO reporting and stakeholder communication — the better first-hand accounts of reporting to owners, managers, and CFOs, the long-game conversation, and the discipline of reporting misses. Read them for the operational reality of §29.4–§29.7, not for numbers.
• Google's Search Quality and Search Central material on core updates (Chapter 6) — background for honestly explaining an update-driven dip in a report rather than hiding it (§29.7).

Tier 3 — Constructed teaching material (this book)

• Rivertown Home Services — the running project; the Chapter 29 one-page monthly report template (Figure 29.3, the Strategy File), all figures illustrative and labeled.
• The vanity dashboard and the honest report (Figures 29.1 and 29.2) — constructed contrasts showing a report that is true-but-useless versus one that reports wins, misses, and the update-driven wobble straight.
• "The Dashboard That Looked Great While the Business Shrank" (Case Study 2) — a labeled composite built from the real, common pattern of vanity-metric reporting plus attribution overclaim; every number illustrative.
• The Universal Analytics → GA4 migration (Case Study 1) — a real, public event; dates and mechanics are documented, and any reconstruction of a typical reporting experience is labeled, with no invented statistic.
• The constructed report excerpts in the exercises (Figures E.29a vanity dashboard, E.29b tool discrepancy, E.29c mixed month) — all labeled constructed teaching examples.

Suggested order

1. Read the Search Console Performance and Page Indexing docs first — they define most of the KPIs you will report and the branded/non-branded split that separates real growth from noise.
2. Read the GA4 key-events / conversions and attribution docs next, so "organic conversion" and "organic-attributed" mean something precise when you write them on a report.
3. Read the consent-mode / data-thresholds note so you never report a conversion count as if it were a complete census.
4. Skim a good actionable-vs-vanity-metrics essay to lock in the "what decision would this change?" reflex from §29.2.
5. Build the dashboard using Looker Studio's connector docs — the fastest way to make §29.3 concrete on your own site.
6. Save the UA→GA4 sunset story (Case Study 1) for when you want to feel why a protected baseline and measurement literacy are survival skills, not box-ticking.

A habit to carry forward: before any number reaches the person who funds your work, ask the two questions this chapter turns into a reflex — would moving this number change a decision? and am I reporting this honestly, including what it doesn't prove and what didn't work? If the answers are "yes" and "yes," it belongs on the page. If not, it belongs in your workspace, or nowhere.