Release
What was actually published, when, and on which routes or templates?
Establishes the interventionGUIDE 02 / SEO REPORTING
A dashboard can be accurate and still be useless. Reporting becomes operational when the reader can tell what changed, what was observed, what remains uncertain and whether to keep, revise, investigate or stop the work.
SIGNAL STACK
Strategy supplies the decision. Technical SEO establishes the released state. An ongoing scope retains that context across releases.
What was actually published, when, and on which routes or templates?
Establishes the interventionHow did impressions, clicks, CTR and average position change by query, page, country, device and time?
Establishes observed Google Search behaviorWhat did attributed organic sessions do on the site under the current analytics definition?
Establishes measured onsite behaviorWhich qualified enquiries, sales or other approved events occurred, and how does the business value them?
Establishes the commercial outcome supplied by the operationCOMPARISON DESIGN
A line rising after a release is an observation. Its usefulness depends on whether the time range, page set, query family, market and competing changes make the comparison relevant to the original decision.
Name the exact pages, queries, country, device, search type and business event.
Record the verified release date and every material change that shares the window.
Use a comparable period and expose seasonality, incomplete data or changed tracking.
Check demand, result composition, site-wide effects, migrations and measurement failures.
Separate what the data directly shows from the cause or forecast being inferred.
THE REVIEW MEMO
What did we believe should happen, and under which condition?
What exact public state was verified?
What changed in search and business data at the correct scope?
Keep, revise, investigate or stop, and name the next decision.
Send the site, the released work and the business decision.