An annual review should explain what your team learned, not simply display the largest upward chart. This framework examines SEO decisions across a full year. It is guidance for conducting a review, not a claim about Gavek's historical performance.
Reconstruct the decisions
List important releases, content changes, technical fixes and discontinued experiments. Record why each was approved and what information was available at the time. A decision can be reasonable even when the eventual outcome disappoints; hindsight should not erase the original uncertainty.
Separate delivery from outcomes
Compare completed work with observable changes in qualified visits, enquiries and revenue where attribution is reliable. Keep algorithm updates, seasonality, tracking changes and paid campaigns in a separate context column. Avoid assigning all annual growth to SEO because several changes happened during the same year.
Choose lessons that change behaviour
Translate findings into operating decisions. Retain a useful template, stop a low-value reporting task or require a brief before commissioning articles. Give each lesson an owner and review date. A smaller list of changes is easier to implement than an exhaustive account of every meeting.
Put the method to work
Illustrative review: a service business finds that its busiest publishing month produced little relevant demand, while clearer service pages helped prospects ask better questions. The next plan reduces article volume and funds service-page research. This is a planning example, not a measured customer result.
Your next steps
- Export the year's dated change log
- Mark measurement breaks before comparing periods
- Write one retained lesson per major project
- Assign next-year changes to named owners
Questions & answers
Should we publish every internal finding?
No. Publish only material you can substantiate and share lawfully. Keep personal information, confidential commercial figures and access details out of public retrospective documents.
What if we cannot attribute results?
Describe the observation and uncertainty. A review can improve delivery quality without pretending to prove which single change caused growth.
Documentation & further reading
- developers.google.com · › search › docs › fundamentals › seo-starter-guide
- developers.google.com · › search › docs › fundamentals › get-started-developers
Explore the related in-depth guide ↗ · Build an action plan ↗