Save the baseline before the work
Record the business, exact location, target pages, keyword groups and measurement dates. Keep original exports rather than only screenshots. If you use a local grid, preserve its center, dimensions, pin spacing and total area. A later scan becomes comparable when those settings remain consistent.
Choose the area based on the question. A close-in view can show performance near the business; a wider view can show how coverage changes across the service area. If both matter, maintain both as separately labeled series. Do not change the grid mid-comparison and present the result as if the measurement stayed the same.
Use a record with distinct measures
| Record | Include | Why it matters |
|---|---|---|
| Baseline | Date, business, URL, query set, location and original export. | Defines the starting point. |
| Campaign | Tool, selected modes, engine, schedule and delivered activity. | Shows what was actually done. |
| Other work | Site edits, reviews, links, promotions and profile changes. | Preserves competing explanations. |
| Visibility | Consistent rank or grid measurements by query. | Tracks the search outcome independently. |
| Business outcomes | Qualified calls, forms, bookings and sales where attributable. | Shows whether the work helped the business. |
| Decision | Continue, revise or stop, with reasons. | Connects measurement to an action. |
Review delivery on its own terms
Planned activity and delivered activity are different fields. If a campaign planned 100 actions and delivered 80, record both. That is an 80% delivery ratio in this illustrative example. It says nothing by itself about how many positions changed or how many customers were acquired.
For Mad Maxx, keep Live Drive activity separate from verified customer visits. For Kraken and Chronos, keep campaign activity separate from genuine organic acquisition. Where a report cannot distinguish a type of activity, state that limitation instead of assigning an assumed source.
Compare the same search questions
Keep branded and unbranded queries separate. Retain engine-specific results rather than merging Google, Bing, Brave and DuckDuckGo into one trend. Record whether the campaign used text, voice, branded or mixed searches; a combined result cannot isolate the contribution of each component.
Local visibility is a pattern across locations and queries. Review the weaker areas as well as the strongest screenshot. If you change the measurement tool, keep an overlap period or clearly mark the break in the series. Otherwise a tool change may be mistaken for a real ranking change.
Connect the review to customer value
Agree what qualifies as an inquiry and a sale before comparing periods. A call can be a wrong number, an existing-customer request or a qualified prospect. A form submission can be spam. Counting everything as a lead inflates the outcome and makes the next decision less reliable.
Keep attribution uncertainty visible. If a customer heard about the business in several places, record what is known instead of awarding the full sale to one campaign. Use the result to decide whether the current setup deserves more time, needs a different destination page or should be reconsidered.
Annotate updates and concurrent changes
A Google update, a competitor change and your own website improvements can overlap. Keep them on the same timeline as the campaign. Google’s Search Status Dashboard identifies confirmed system events; community reports can add context but do not establish the cause of a particular site’s movement.
A report should make those limits readable. “Visibility improved during this period” is different from “this campaign caused the improvement.” Use the case-study checklist before turning a campaign review into a public result.