Local SEO measurement: a 30-day enquiry audit for UK businesses

Start with a useful enquiry, not a map position

Define what a suitable customer needs before choosing a local SEO metric. A repair shop may want an enquiry about a service it can perform within its genuine coverage area. A booked appointment is a different outcome from a tap on a phone number. Keep those stages separate so a busy profile does not conceal weak lead quality.

This is a measurement companion to our UK Google Business Profile setup guide. The thirty-day schedule is a proposed working cycle, not a promise that rankings will change within a month. The example later in the article is fictional and supplies no client results.

Record the baseline before changing the profile

Choose a date range, location and service scope, then retain the original report. Google describes local ranking in terms of relevance, distance and prominence [1]. A search performed at your desk cannot represent every customer location. Record the observation context when checking a result, and treat a single screenshot as an observation rather than an area-wide ranking score.

Use comparable days of the week when looking at short periods. Keep missing information marked unknown. If no earlier enquiry log exists, start one now instead of reconstructing customer histories from memory.

Understand what the profile numbers actually mean

Google defines calls in profile reporting as clicks on the call button and website clicks as clicks on the website link [2]. A call-button click does not prove the call connected, was answered or led to a booking. Profile reporting can include activity from organic search and Google Ads; it is not automatically an organic-only acquisition report.

Use the metrics that actually appear for your business. Keep each system’s definitions beside the report and avoid adding overlapping counts together as though they represented unique people.

Identify visits from the profile website link

A consistent campaign-tagged website URL can help distinguish profile-link traffic in Analytics. Google documents UTM parameters for identifying referring campaigns [4]. Use an agreed naming convention, keep it stable and test the resulting page. Parameters are labels, not proof of a booking or permission to collect additional personal data.

Illustrative pattern: your existing destination URL with utm_source=google&utm_medium=organic&utm_campaign=business_profile. If the URL already has a query string, append parameters correctly rather than adding a second question mark. Preserve any required booking parameters. Test that the link opens the intended page and that reporting labels appear as expected.

Keep customer names, email addresses and enquiry text out of campaign URLs. Bookmarks, consent choices, redirects and later visits can complicate attribution. Retain an “unknown” source option rather than forcing every enquiry into a channel.

Test the journey from phone screen to real response

Open the profile website destination on a phone and perform a clearly marked test enquiry through your own normal process. Check whether the service area, opening times and next step are clear. The test should verify both the customer-facing confirmation and the team’s receipt. A button that looks correct is not enough if the enquiry never reaches a responsible person.

• Confirm the correct location or service area.
• Check the destination service matches the profile.
• Read the page without horizontal scrolling.
• Use the phone or enquiry route.
• Confirm receipt and assign an owner.
• Exclude the test from commercial outcome reporting.

Do not send test enquiries to competitors. Use your own process and avoid unnecessary personal details. A short record of the device, date, route and failure is more useful than an unlabelled screenshot of a page that happened to load.

Keep a minimal enquiry-quality log

Record a small set of operational outcomes in your existing system: date, route, service requested, whether the location is served, whether the business can help and the next step. The report needs enough structure to reveal problems without copying entire conversations into a marketing sheet. Use your established access and retention process for any customer records.

Google Analytics allows important website actions to be treated as key events [5]. Validate the action first: a successful enquiry should not be inferred merely because someone clicked Submit. Mark duplicate and internal test entries so they do not distort the result.

Use the pattern to choose the next fix

Look for an operational explanation before changing every profile field. If suitable enquiries arrive but remain unanswered, the immediate problem may be response coverage. If many requests concern an unavailable service, inspect the category, description and landing page. Accurate real-world representation is central to Google’s profile guidelines [3].

These are diagnostic hypotheses, not proven causes. Record the suspected issue, the evidence and one proposed correction. Avoid changing the category, page, hours and offer at once when you want to understand which change helped.

Work through a fictional repair-shop audit

Imagine an independent appliance-repair business that serves two genuine nearby towns. The owner notices website clicks but has no reliable enquiry record. In the proposed audit, the first action is to test the mobile form and the team’s receipt. The second is to distinguish requests within its actual service area from enquiries it cannot serve. No numbers or improvement results are asserted.

If the form confirmation appears but the team receives nothing, record and repair that failure before seeking more traffic. If the route works but the page suggests nationwide coverage, correct the wording to the real service area. Then retain the change date and review comparable periods. This sequence makes the next decision depend on evidence rather than an assumed ranking problem.

The example is deliberately modest: it does not claim a top-three position, increased revenue or an achieved conversion rate. Its useful output is a test record, an accurate page and a clearer enquiry log.

Improve trust without manipulating reviews or locations

Ask for genuine feedback through your normal customer process. Google prohibits incentivised and fake engagement [6]. Do not buy reviews or fabricate a location to appear closer to customers. Correct outdated details with evidence and keep an internal note of the source. If your eligibility or address is uncertain, resolve it using the official guidance before making changes.

Review the website for pages that add no local value beyond swapping a town name. Google’s spam policies describe doorway abuse involving pages created for similar searches that funnel users onward [7]. A useful service-area page should explain the actual service, coverage and practical customer questions. Creating a page for every postcode is not a measurement strategy.

Use a thirty-day working cycle

Use the first week to establish definitions and test the contact route. In the second, fix the highest-confidence fault. In the third, check the enquiry log and response process. In the fourth, review the evidence with the same scope and definitions. Extend the period when volumes are low; thirty days is an organising device, not a reliable test duration for every business.

For website search context, Search Console provides clicks, impressions and page/query filters [8]. Keep that report separate from Business Profile actions and enquiry outcomes. They answer different questions. Use the combined evidence to choose the next practical improvement, while retaining unknowns and avoiding causal claims the records cannot support.

Frequently asked questions

Sources and editorial method

Primary documentation checked on 17 October 2026. The worksheets and scenarios are original editorial teaching aids, not customer results, vendor benchmarks or a claim of legal compliance. Prepared with AI assistance and source verification. No search-volume, ranking or keyword-difficulty estimate is asserted.

1. Google: Local ranking — Relevance, distance and prominence.
2. Google: Business Profile performance — Interaction definitions; includes organic and ads activity.
3. Google: Business representation guidelines — Accurate business identity and location.
4. Google Analytics: Custom campaign URLs — UTM parameters for source identification.
5. Google Analytics: Key events and conversions — Distinguishes important website actions.
6. Google: Reviews and prohibited content — Genuine reviews and manipulation restrictions.
7. Google Search: Spam policies — Doorway abuse and substantially similar pages.
8. Google Search Console: Performance report — Search clicks, impressions and page/query filters.