How to Read a Local SEO Report: A Worked Example
· 6 min read
Published by AKSIS · general educational information
How AKSIS handles editorial review
AKSIS publishes practical website and search guidance for small business owners. Our editorial policy covers source support, claim boundaries, clarity, human responsibility, and small-business usefulness.
General information only—not legal, financial, medical, or platform policy advice.
Read the AKSIS editorial policy.
Read a local SEO report by separating three questions: did useful search visibility change, did people take an action, and did your business verify an inquiry or sale? Start with the source and dates beside each number. A better average position, a website click, and a call-button tap answer different questions.
The worked example below shows how total clicks can increase while click-through rate falls, even when the rates within each query group stay the same. It gives you a way to question a report before paying for a rewrite or assuming a campaign succeeded.
Keep the source attached to the number
- Search Console: website search visibility
- Impressions record appearances of your site in Google results; clicks record visits from those results. CTR is clicks divided by impressions. Average position blends observed appearances and is not a fixed ranking everyone sees. Google explains these boundaries in its search metrics guide.
- Business Profile: interactions with your profile
- Google defines the Calls metric as clicks on the profile’s call button, and Website clicks as clicks on its website link. A tap does not establish an answered call, booking, or sale. Its performance data can include organic and Google Ads interactions; availability varies by business. See Google’s Business Profile metric definitions.
- Business records: what happened after contact
- Your team can separately record whether an inquiry was genuine, within the service area, and about work you offer. Keep that evidence distinct from a tracking event or button click. If the source of an inquiry is unknown, retain that uncertainty instead of attributing it to SEO.
Do not add website clicks, profile interactions, and inquiries into a single “customers generated” total. One person may take several actions, and the systems do not establish a shared count of unique customers.
Worked example: more clicks, lower CTR
Imagine two equal 28-day periods for a local service website. The following numbers are made up to demonstrate the calculation. They are not AKSIS or client results, a forecast, or a target. For this example only, the two groups contain the complete set of observations.
| Query group | Earlier impressions / clicks | Later impressions / clicks | CTR: earlier → later |
|---|---|---|---|
| Branded: searches naming the business | 200 / 40 | 100 / 20 | 20% → 20% |
| Non-branded: service searches without its name | 300 / 15 | 900 / 45 | 5% → 5% |
| Combined illustrative total | 500 / 55 | 1,000 / 65 | 11% → 6.5% |
Earlier combined CTR is 55 ÷ 500 = 11%. Later it is 65 ÷ 1,000 = 6.5%. Both groups kept their own CTR, but the lower-rate non-branded group now makes up more of the impressions. Averaging the two percentages would produce 12.5% and misrepresent both periods.
The combined CTR decline therefore does not, by itself, prove that a title or page became less appealing. The branded group also lost clicks, which deserves its own question. The next useful step is to inspect the actual queries and receiving pages in each group, then check whether those service searches match the business. The example establishes no change in inquiries, sales, or return on spending.
Apply the comparison without forcing the totals
Ask for the exact property, search type, date range, and page, country, device, and query filters. Compare equal completed periods with the same settings; note seasonal context and changes such as a site move or tracking change. Search Console’s daily dates use Pacific time, so another system’s calendar boundaries may differ.
Real Search Console query rows are incomplete: privacy protections omit some queries, and reporting limits retain top rows rather than every observation. Do not sum the visible query list as if it were the complete two-group example above. Google’s data documentation explains these limits and reporting delay.
Page and property aggregation also differ. Check the actual UI when data is unavailable: Google warns that unavailable markers can become zeros in downloads. Its Performance report guide also identifies preliminary chart data with dotted lines. A sparse or incomplete comparison needs a stated limit, not a precise success or failure claim.
Turn the finding into one justified next action
If the same useful service queries and pages lose clicks across a comparable period, investigate that group rather than rewriting the whole site. Check whether impressions, query mix, indexing, or the search results changed. Google’s traffic-drop guidance describes several possible causes and cautions against radical changes for small ranking fluctuations.
If website clicks rise but the team sees fewer suitable inquiries, check the measurement definition and the actual contact path before declaring that search traffic improved the business. If profile call taps rise, compare them with answered-call records where available. Missing records leave the outcome unknown; they do not turn every tap into a lead.
A useful report ends with the finding, its evidence and limits, the next action, and the date the result will be reviewed. For the wider context, read what local SEO includes and how SEO workstreams fit together.
Discuss the question behind your report
If your report leaves a specific question unanswered, identify the number, its source, and the business decision you need to make. Our local SEO service outlines the existing service scope. Keep passwords and private customer records out of an initial inquiry.
Discuss your search reporting