Group pages around a decision
A cohort is a deliberately defined group of pages that you evaluate together. Start with the decision: whether to expand integration tutorials, improve comparison articles, or stop producing broad definitions. Useful grouping fields include intent, product area, publication month, and intended customer. Avoid making dozens of tiny groups before traffic exists. A single page can belong to a publication cohort and an intent cohort, but those are different analyses. Store membership in a content inventory so it does not change accidentally when a title changes.
Give cohorts comparable exposure
An article published yesterday has had less time to attract search visits than an article published last quarter. Compare equal ages where possible, such as each cohort's first complete observation period. Keep publication date distinct from first recorded search activity; publishing does not guarantee immediate discovery. Include the number of eligible pages and their live days alongside totals. Otherwise, a larger cohort can appear better solely because it contains more URLs. Decide whether the relevant measure is total contribution, typical page performance, or both.
Connect entrances to meaningful actions
Google recommends using landing-page analysis with organic traffic filters to understand on-site outcomes. For this workflow, define a session-scoped entrance cohort and then inspect relevant actions in those sessions. Keep Google organic separate from all organic search when reconciling with Google Search Console. A session that starts on an article and registers after visiting pricing still belongs in an entrance-based view. That does not prove the article caused the signup, but it gives you a consistent way to compare how different entrances perform.
Use a hypothetical comparison
Suppose a scheduling app publishes integration tutorials in one month and management essays in the next. The essays receive more visits, while the tutorials attract more trial starts from relevant companies. Compare equivalent publication ages, note any promotion, and inspect the actual trial quality. The right editorial response might be to expand integration coverage while improving the essays' connection to the product. It would be premature to declare that every tutorial is better than every essay from one small observation window or a handful of registrations.
Preserve the cohort definition
Save the URL list, inclusion rule, extraction date, and any excluded pages with the report. When a guide is redirected, record its predecessor so a cohort does not silently lose history. Use a clearly named outcome event; Google's key-event documentation provides the underlying Analytics mechanism. Review outliers rather than hiding them in an average. One unusually successful article can fund a strategy, but it should not be mistaken for the typical result. End the analysis with the next content decision and the evidence needed to revisit it.
Practical review checklist
- Export the exact canonical URL membership for every cohort before calculating totals, averages, or rates across the group.
- Record publication age and eligible observation days so a young collection is not judged as a mature one.
- Separate page-cohort outcomes from individual outliers, and inspect the most successful and least successful journeys before extrapolating.
- Retain redirects and retired URLs in the inventory so historical membership remains interpretable after normal site maintenance.
Compare pages with similar intent and exposure, then connect their entrances to relevant outcomes.
Sources & further reading
Official documentation informs this guide. Examples are illustrative, and product interfaces or limits can change.
From search signals to a useful first draft.
SERP.so is in development. Join the waitlist for a workspace that connects research, content review, and publishing.
Join early access ↗