KNOWLEDGE LIBRARY
Measuring SEO Results Without Mixing the Numbers
A useful SEO report should make the next decision easier. It should show what changed, where it changed and what the evidence can actually tell you. An impressive percentage without its period or baseline does none of those things.
The method below is our working approach. The IRFĒ examples are historical project evidence, not benchmarks that another business should expect to reproduce.
Quick answers about SEO reporting
Are search impressions the same as website visits?
No. Impressions describe appearances in search results; clicks describe clicks from those results. Analytics visits and business inquiries are separate measurements. A rise in impressions can be useful evidence of visibility, but it does not by itself prove more visitors or customers.
Does twice as much traffic mean 200% growth?
No. Twice the original amount is a 100% increase. The percentage increase is the difference divided by the original amount, multiplied by 100. Keep the dates, metric and baseline explicit, and do not imply precision beyond the original report.
Can I add several monthly and six-month reports together?
Only when their periods do not overlap and their metrics and scope are compatible. A month already included in a six-month total must not be counted again. Use overlapping views to explain a trend, not inflate a cumulative result.
First identify the measurement
Search impressions describe appearances in results; search clicks describe clicks from them. They are not a count of unique people. Analytics users and sessions describe activity measured by a different system. An inquiry, an order and its value answer another question again. Google explains the reporting controls and metrics in its Search Console performance documentation.
Use explicit labels in the headline. “265K Google Search clicks in the selected period” is meaningful. “265K customers” is a different claim and would need different evidence.
A reporting table can stay simple:
| Layer | Example question | Useful evidence |
|---|---|---|
| Visibility | Was the site appearing for relevant searches? | Search impressions, query and page groups |
| Acquisition | Did people reach the website? | Search clicks and separately measured visits |
| Business action | Did the visits lead to useful activity? | Verified inquiries, orders and other agreed actions |
Do not use a result in the first row as proof of the last row.
Make the comparison explicit
Name the channel, selected dates, comparison dates and important filters. A change over 28 days should not be casually compared with a calendar month of a different length. A country-filtered result should not be placed beside an all-country result without an explanation.
For seasonal businesses, an adjacent period and the corresponding period a year earlier may answer different questions. Keep the question visible: are we assessing recent momentum, a seasonal comparison or the longer development of a program?
Relative date labels also need context. An archived screenshot saying “Last 6 months” does not mean the six months before today. Preserve its report date and the original label. Do not infer exact endpoints when the selector is not shown.
Calculate growth without changing its meaning
In IRFĒ’s February 6, 2025 report, Search Console shows 173K clicks for the last six months against 8.01K for the previous six months. Dividing those displayed values gives approximately 21.6 times as many clicks.
That is a strong result without calling the starting point zero. The values are rounded by the interface, so the calculated multiplier should be approximate too. A precise-looking decimal can imply accuracy the source does not contain.
A multiplier is also not the same as a percentage increase. Twice the previous result means a 100% increase, not a 200% increase. When quoting an Insights percentage, label it as the percentage shown in that reporting view instead of rebuilding a hidden baseline from rounded totals.
Keep overlapping windows out of the total
A three-month view and a six-month view often include some of the same dates. Adding their clicks double-counts that activity. Use them as different observations of the program, not pieces of one cumulative total.
The same applies to a sitewide number and its top pages. The pages are part of the sitewide result, not an additional audience. A page table helps explain the total; it should not inflate it.
A useful evidence register gives every item a source, period, metric, scope and intended role. One item may support the headline, another the trend and another a specific content decision.
Separate Search, Discover and AI observations
Google describes Discover as a feed based on a user’s interests, distinct from query-led Search, and provides its own reporting guidance. Treat its performance as a separate channel in the analysis. Google Discover guidance
In IRFĒ’s archive, a six-month Discover comparison records 219K clicks. Those are not the same measurement as the selected 2025 Google Search total. Showing both can strengthen a case; combining them without aligned dates and an explanation would make it less clear.
For AI Search, a citation screenshot is an observation of an answer, not a traffic report. Referral visits belong in their own dataset. The AI measurement guide explains how to preserve that distinction.
Read beneath the sitewide average
A sitewide average can hide changes in the mix of pages and queries. A program might gain visibility on broader queries while a small set of important commercial pages remains unchanged. Conversely, one useful service page can improve while a large informational section dominates the total.
Start with the business’s priority pages and questions. Where the available data supports it, separate brand searches, non-branded subjects, service families, countries and devices. Record what was filtered rather than treating a filtered view as the whole site.
Choose the comparison because it answers a question, not because its line rises more sharply.
A total for the site is also different from the rows for individual search queries. Google omits some queries to protect privacy; those anonymized queries can remain in unfiltered chart totals. It also limits the query rows it stores and shows. A table that adds up to less than the headline total therefore does not, by itself, reveal missing customers or a reporting error. A query filter changes the scope again. Google's query-data limitations
For a business decision, a selected set of service questions can help explain a change, but it should be labeled as a selected set. Its clicks are neither an additional audience to add to the site's clicks nor proof that every customer used one of the visible queries.
Preserve the evidence and the conclusion separately
A saved result can demonstrate that a page appeared above another publisher for the visible query. It cannot by itself establish an enduring ranking or overall superiority across the category.
Keep the original screenshot intact, with the query and relevant interface labels. Put the interpretation in the caption or surrounding text. Do not redraw a graph to make the trend smoother or remove context that changes the meaning of the number.
The final report should end with an action: continue a useful content direction, investigate a technical issue, improve an important page or gather missing conversion evidence. Measurement earns its place when it helps decide what to do next.
To apply these distinctions when reviewing a provider's work, the 90-day local SEO acceptance guide includes a worksheet for evidence, unresolved tasks and the next decision.
Follow an inquiry far enough to understand its value
Local SEO can help a business be discovered by people seeking its services, and clearer pages can help those people decide whether to make contact. Revenue follows only if a suitable prospect becomes a paying customer. Each step can fail for a different reason. Better visibility cannot supply an unavailable appointment or turn an out-of-area request into work the business can accept.
A form submission is an observable action. A qualified inquiry is a business judgment about that contact: does the person need an offered service, in a place the company serves, on terms the business can consider? For a specialist supplier, the relevant product requirements may matter more than distance. The criteria should reflect the business rather than a reporting tool's default event name.
Repeat contacts need context as well. One person who submits a form and then calls may represent one sales opportunity, not two new prospects. Spam, employment inquiries, existing-customer support and requests for discontinued services can all appear in contact totals. They may require attention, but grouping them with new sales inquiries makes acquisition performance harder to understand.
Following the sequence can explain a disappointing result. If relevant inquiries increased but appointments did not, availability or response handling may deserve investigation. If appointments increased but completed work did not, cancellations or customer fit may matter. These observations identify where to look; they do not establish a cause without further evidence.
Keep open opportunities separate from completed outcomes. A project inquiry received this month may take months to become a signed engagement, while this month's collected revenue may come from an earlier inquiry. A report can follow a group of inquiries received in the same period through later outcomes, noting which remain unresolved. Comparing this month's contacts directly with this month's revenue can conceal that delay.
Where records do not connect a contact with its source or eventual outcome, the report should show that gap. It can still describe search visibility and measured website actions. It cannot responsibly rename those actions as confirmed customers or assign them a value the business has not established.
A request for directions is not a store visit
For a physical location, local search can help someone discover the business, find its address, check its hours or choose a route. These actions are useful parts of a possible visit. They measure different things from a person arriving at the premises and purchasing.
Google's Business Profile performance definitions make the boundaries explicit. Calls count clicks on the profile's call button; website clicks count clicks on its website link; directions count requests for directions. A call-button click does not establish that the call connected. A directions request does not establish an arrival. Available metrics vary by business, and Google says the performance data can include activity from both organic results and Google Ads.
This matters when a local SEO report uses all profile interactions as evidence of organic growth. If the company also advertised, the scope of the dataset needs to be understood before crediting the total to unpaid work. The report should identify the source and any separation it can actually support.
Evidence of physical visits must come from a source capable of observing or estimating them, with its own limits. A store's footfall counter can record entries without identifying how people discovered it. Point-of-sale records describe purchases rather than everyone who entered. A customer survey can provide useful context, while depending on who responded and what they remember. These sources can inform the same business question without being interchangeable counts.
If direction requests and store sales both rise, that is a reason to examine the relationship, not proof that every extra sale came from Google. A promotion, changed hours, nearby event or seasonal demand may also affect the result. The useful conclusion states which observations agree and which part of the connection remains uncertain.
Revenue, contribution and the cost of acquiring the work
More revenue does not necessarily mean more profit. A service can generate a large invoice while requiring substantial labor, materials or outside help. To assess an acquisition investment, the business needs an economically useful value for the completed work, together with the costs of the program being assessed.
Consider a hypothetical service business following 20 new inquiries associated with a measured organic-search source. Eight fit its service and location requirements. Three have become completed, paid jobs; the rest are unsuccessful or still open. Those three jobs produced $6,000 in collected revenue and $2,400 in contribution after the direct costs of delivering them. The figures are an illustration, not a client result or an expected close rate.
| Illustrative amount | What it describes |
|---|---|
| $6,000 revenue | Money collected for the three completed jobs |
| $2,400 contribution | Revenue remaining after the stated direct delivery costs; fixed business overhead has not been deducted |
| $1,500 acquisition-program cost | The defined provider, implementation, content and other program costs included in this illustration |
| $900 difference | $2,400 minus $1,500, before other relevant costs and any conclusion about what would have happened without the program |
Subtracting the program cost from revenue would produce $4,500, but it would ignore the cost of doing the jobs. The $900 difference uses a more relevant contribution figure. It still is not proof of incremental profit caused by SEO: some customers might have arrived without this investment, and the example has not deducted fixed overhead or established that counterfactual.
Program costs need an equally clear boundary. An agency invoice may omit development, separately purchased writing, software or the business's own time. A report can use a narrower cost figure for a specific question, but it should name the exclusions. Comparing a fully costed proposal with a fee-only return calculation would distort the decision.
Attribution and incrementality answer different questions. Attribution assigns an observed outcome to a source under stated rules. Incrementality asks what additional business happened because of the investment. A source label helps follow an observed journey; it does not reveal the outcome that would have occurred in the program's absence. Repeat customers, branded searches and journeys involving several channels make that distinction especially important.
The calculation may also mature over time. Unfinished opportunities can close later; refunds or further delivery costs can change the value of completed work. Estimated future repeat purchases should stay separate from money already collected and carry their assumptions. A report need not resolve every uncertainty before it is useful. It needs to distinguish the amount known today from the amount still being forecast.
These distinctions explain how local search can contribute to profits without promising that every increase in visibility will do so. The business benefits when discovery produces suitable customers at an acceptable total cost, and when it can deliver their work profitably. A report that follows those conditions gives an owner a stronger basis for renewing or changing the engagement than a larger traffic total alone.
Related work
Continue reading
Next: Service Pages and Supporting Content: Give Each Page a Job
