Reporting, Analytics, and Measurement
The reporting domain tests measurement literacy: which tool answers which question, how to segment organic traffic so the number means something, and how to present a finding that leads to a decision.
The tool map
- Google Search Console: queries, impressions, clicks, CTR, average position by page and query; page indexing and Core Web Vitals reports; manual actions.
- HubSpot traffic analytics: sessions and contacts by source, campaign attribution, and landing page or blog performance tied to the CRM record.
- Rank trackers: daily position monitoring for a defined keyword set. Useful for spotting volatility, not for proving revenue impact.
Rules for honest reporting
- Segment branded from non-branded queries; brand growth masks SEO problems.
- Track conversions, not sessions. Organic traffic that never converts signals a content-intent mismatch.
- Tag campaigns with UTM parameters and keep the taxonomy consistent, or attribution scatters.
- Annotate algorithm updates, migrations, and campaign launches on every chart.
- Pair leading indicators (indexed pages, impressions, position on target queries) with lagging ones (organic contacts, revenue).
Worked example
Organic sessions fall 18% month over month. Instead of reporting a failure, split the number: non-branded clicks are flat, branded clicks fell after a paid brand campaign ended, and impressions on ten target queries rose 30% with average position improving from 14 to 8. The correct conclusion is that visibility is improving and the decline is a brand artifact - a very different story from "SEO is broken."
Traps
Reporting sitewide average position, which blends branded and non-branded queries and hides page-level change. Comparing a partial month to a full one. Treating last-click attribution as truth in a multi-touch B2B cycle. Presenting metrics with no recommendation attached.