Track local SEO by the leads it produces, not vanity rankings: calls, form fills, and direction requests first, with Map Pack and organic positions as the leading indicators.
- Lead metrics are the goal; rankings are the early signal.
- Single ranks mislead locally; track by location.
- Report monthly against leads and revenue.
The point of tracking local SEO is leads, not vanity rankings. A number-one position that produces no calls is worth less than a steady stream of enquiries from a handful of solid rankings. This guide covers the metrics that actually matter, the Google Search Console basics, how local rank tracking works, and how often to report, so the programme stays tied to revenue. Clear reporting is built into our local SEO service. For the detail, see Why Your Service Business Is Not Ranking on Google (and How to Fix It).
The Metrics That Actually Matter
Group local SEO metrics into three, and weight them in this order.
Leads
Calls, form fills, and direction requests. These tie directly to revenue and are the real measure of success.
Rankings
Map Pack positions and local organic clicks. The leading indicator that predicts lead growth.
Engagement
Profile views, clicks to call, and website visits from local search. Useful context behind the leads.
Google Search Console Basics
Search Console is the free starting point. It shows the queries a site appears for, plus clicks, impressions, and average position, broken down by page. Filter by local terms and by the service-plus-town queries that matter, and watch which pages gain or lose clicks over time. It does not show the Map Pack, but it is the clearest view of local organic performance.
Three limits decide how far Search Console can be trusted as the record of local organic performance. Data is kept for the last 16 months, so a year on year comparison is possible and a two year one is not. The interface exports a maximum of 1,000 rows, while the Search Console API returns up to 25,000 rows per request and 50,000 rows per day per site per search type. Queries issued by only a few dozen people over a two to three month period are anonymised and left out of the query table, yet they are still counted in the chart total unless a query filter is applied, which is why the rows almost never sum to the headline number. Figures also arrive 48 hours after Google collects them, so the last two days of any month are incomplete when the report is written.
What Google Business Profile Reports
Search Console covers organic results. The Google Business Profile performance report is where the Map Pack side of local search is measured, and Google names the metrics it provides: interactions, searches, views, directions, calls, website clicks, messages and bookings. Two of those names mislead if taken at face value. Calls counts presses of the call button on the listing, not every call the business receives, so it is a floor and not a total. Searches lists the terms people used to find the listing, which is the closest thing in local SEO to a free keyword report.
Two timing details change how the report should be read. The searches metric updates at the start of each month and can take up to five days to appear, so a month to date check on the 2nd looks empty when nothing is wrong. The Business Profile Performance API serves a maximum range of 18 months from the date of the request, two months longer than Search Console keeps its data, which is why both should be exported every month rather than read from the interface when a report is due. Getting the profile itself in order comes first, and that is covered in Google Business Profile optimisation.
Where Each Number Comes From
No single tool reports a local programme. Four hold different parts of it, and each forgets its data on its own schedule.
| Metric | Source | History it keeps |
|---|---|---|
| Calls, direction requests, website clicks, searches | Google Business Profile | 18 months by API |
| Map Pack position, by location | Grid rank tracker | Only what you have tracked |
| Local organic clicks, impressions, average position | Search Console | 16 months |
| Form fills, sessions, the path to the enquiry | Google Analytics | 2 or 14 months, by setting |
| Phone calls from the website | Call tracking number | Whatever the provider stores |
The Google Analytics row is the one that catches people out. A property keeps event data for either 2 months or 14 months, and the shorter setting quietly removes the ability to compare this November with last November. Check it reads 14 months before the first report rather than after a year has aged out. Age, gender and interest data is held for two months whatever that setting says.
Local and Grid Rank Tracking
A single national rank is misleading locally, because results change with the searcher location. Grid or geo rank tracking checks positions from multiple points across a service area, which shows where you rank well and where you do not. This is also the only reliable way to track the Google Map Pack, since its order shifts by proximity.
A tracker is worth no more than the keyword set inside it. Track the service plus town terms a buyer would actually type, the ones already earning impressions in Search Console, and the three or four services worth the most per job, rather than a long list of variations that all return the same local pack. Building that list is covered in local keyword research.
Map Pack and local pack are two names for the same result set, and it shows three listings by default. That one number sets the bar for every tracked term: position four on a service plus town keyword reads like a top five result in a report and is invisible on the phone of the person searching. Track position one to three as the only outcome that counts, and treat everything below it as progress rather than performance.
Monthly Metrics and Quarterly Audits
Not everything worth measuring moves monthly. Splitting the two keeps a report from filling with numbers that have not changed since the last one.
| Check monthly | Audit quarterly |
|---|---|
| Calls, form fills and direction requests | NAP consistency across the main citations |
| Map Pack position across the tracked keyword set | Backlinks won and lost, and referring domains |
| Search Console clicks, impressions and position | Duplicate or unclaimed listings |
| New reviews, current rating and reply rate | The tracked keyword set itself |
Reviews sit in the monthly column because both volume and recency move, and because a stalled review count explains a stalled Map Pack position more often than anything on the website does. Count new reviews rather than the total, and record the reply rate next to them, as in Google reviews strategy. Citations and NAP sit in the quarterly column for the opposite reason: they change only when somebody changes them, so a monthly citation report is noise dressed as diligence. Link building belongs there too, because a quarterly count of referring domains carries a signal that a monthly backlinks figure moving by one or two does not. Both are covered in local citations and NAP and local link building.
Reporting Cadence
Monthly reporting fits the pace of local SEO. A useful report shows leads and rankings together, separates leading indicators (rankings, impressions) from lagging ones (calls, bookings), and notes what was done and what comes next. Weekly reporting shows noise rather than trend, given the timeline local SEO runs on.
One reporting fault is worth naming because it flatters SEO rather than the client. Where a business runs Google Ads alongside organic work, the two have to be separated in Google Analytics before any lead is credited to SEO, or the Google Ads budget pays for results that appear in the SEO report. Keep them on separate rows, and when both are running, compare them on cost per booked job instead of lead count, which is the comparison set out in SEO versus Google Ads.
Last Thoughts on Measuring Local SEO
Good measurement ties rankings to leads and revenue, and keeps the programme honest. Watch rankings as the early signal, but judge the work on calls and enquiries. If the reporting cannot connect the activity to booked jobs, it is measuring the wrong things. Reports built this way for real clients are published in our case studies.
- Judge local SEO on leads, not vanity rankings.
- Rankings and impressions are leading indicators; calls are the result.
- Search Console is the free base for local organic data.
- Use grid or geo tracking for accurate local and Map Pack ranks.
- Report monthly, tying activity to enquiries.
Frequently Asked Questions (FAQs)
What is the most important local SEO metric?
Booked leads, the calls and enquiries that turn into work. Rankings and traffic matter only insofar as they produce them.
How often should rankings be checked?
Weekly to monthly. Weekly catches big movements; monthly is the right cadence for reporting trends rather than day-to-day noise.
How do I track calls from Google?
Use call tracking numbers and the Google Business Profile insights, which report calls, direction requests, and clicks from the listing.
Why is a single ranking position misleading?
Local results change with the distance between the searcher and the business, so one rank cannot describe a whole service area. A grid tracker checks the same keyword from a spread of points and reports a position for each, which is the only way to see that the local pack holds near the premises and not at the edge of the area.
Does Search Console show the Map Pack?
No. Search Console covers organic search. The Map Pack needs a local rank tracker or the Business Profile insights to monitor.
What is grid rank tracking?
Checking your rank from a grid of points across your service area, so you see how visibility varies by location rather than from one fixed spot.
What should a local SEO report include?
Leads and rankings together, leading versus lagging indicators, the work done, and the next actions, in plain terms tied to enquiries.
What are good local SEO KPIs?
Calls, form submissions, direction requests, Map Pack positions for key terms, and local organic clicks. Lead metrics lead the list.
Are impressions a useful metric?
As a leading indicator, yes. Rising impressions show growing visibility that should convert to clicks and leads as positions improve.
How soon will tracking show results?
Impressions in Search Console move before leads do, and Google publishes those figures 48 hours after collecting them, so the first signal is readable within days of it happening. Lead volume follows over the months covered in the local SEO timeline.
How far back does local SEO data go?
Search Console keeps 16 months. The Business Profile Performance API serves up to 18 months from the date of the request. Google Analytics holds event data for 2 or 14 months depending on the property setting. Export every month if you want a record longer than the shortest of those.
Why do my Search Console totals not add up?
Queries used by only a few dozen people over two to three months are anonymised and left out of the query table, while still counting towards the chart total unless a query filter is applied. The table also stops at 1,000 rows in the interface, so the visible rows are a subset.
- Google Business Profile Help, metrics in the performance report, for the metric names and the timing of the searches metric.
- Google Business Profile Performance API, BasicMetricsRequest, for the maximum range of 18 months from the request date.
- Google Search Central, a deep dive into Search Console performance data filtering and limits, for the 1,000 row export cap, the API row limits and anonymised queries.
- Google Analytics Help, connect Search Console to Google Analytics, for the 16 month retention and the 48 hour delay.
- Google Analytics Help, data retention, for the 2 and 14 month event data options.
