A Local SEO Audit Baseline You Can Actually Repeat

A useful local SEO audit starts with a dependable description of the business and a saved record of what customers can currently find and do. It should produce a short list of confirmed problems, each with evidence, an owner, and a way to check the fix.

The process below is a proposed baseline for a single business or location. Its worksheet fields and priorities are working recommendations, not Google's ranking formula. For multiple locations, create a separate record for each before combining the results.

Verify the business before checking rankings

Ask an authorized operator to confirm the real business name, website, phone number, normal hours, holiday exceptions, and the services currently offered. Record the date and the person responsible for keeping each fact current.

Then establish how customers are served. Can they visit a staffed location? Does the business travel to them? Which areas are actually covered, and which requests must be declined? Keep a private operational address out of public recommendations when customers are not supposed to visit it.

Google's representation guidelines call for an accurate real-world identity, precise address or service area, and categories that describe the core business. They also warn against unnecessary additions to the business name. Check the applicable eligibility and address rules before proposing profile edits. Google's Business Profile guidelines

The goal is an approved fact sheet. Without it, an auditor can confidently recommend publishing the wrong information in more places.

Keep a profile record and a website record

Save the current public Business Profile fields and the website pages that a customer would use to verify them. Record disagreements rather than choosing whichever version looks more polished.

Check the primary category, listed services, hours, website destination, phone link, and visible reviews. Note missing access to the profile as a limitation. A public inspection cannot establish that ownership, verification, or unpublished settings are correct.

Google describes local ranking through relevance, distance, and prominence, and says businesses cannot request or pay Google for a better local rank. That makes a fixed promise such as “first across the whole city” unsuitable as an audit deliverable. Google's local ranking guidance

A better deliverable is the evidence needed to correct a misleading category, resolve contradictory hours, or improve the page a customer reaches.

Make location part of every search observation

Choose a few real services and several relevant places within the confirmed service area. Write the exact query and location context for each observation. Record the date, device, surface, and whether the location was explicitly set, inferred, or unknown.

Do not describe a search from your office as the business's position everywhere. If you use a geographic rank tool, retain its settings and methodology with the export. Do not compare that output directly with an informal phone search without explaining the difference.

Keep Maps, ordinary web results, and AI answers in separate columns. If you also inspect AI answers, use the AI search visibility audit to distinguish mentions from citations and verify the referenced claims.

Choose repeat locations before making changes. If you move the observation points later, preserve the earlier version. A more favorable sample is not evidence that coverage improved.

Inspect the page after the search result

Open each important service page as a prospective customer. Can you tell what the service includes, where it is offered, and what to do next? Does the page explain any condition that would make the service unsuitable?

Check that the page names a real service and a real coverage area. Ask for operational evidence before drafting a page that implies a local office or availability the business does not have. A city name repeated across a page cannot substitute for accurate service information.

For each page, save the title, main answer, contact route, and any material claim that needs confirmation. A statement about emergency availability should have an operator's approval. A price range should explain what it includes and when it was checked. Testimonials need a legitimate source and permission where required.

Use AEO and SEO together to give these pages clear roles rather than producing many near-identical city pages.

Test the customer's next action

Inspect phone links, forms, booking paths, and confirmation messages. Plan any live test with the business so a synthetic inquiry does not consume staff time or create a misleading lead record. Where possible, use a test environment or a designated test contact.

Record the expected behavior and the actual result. A form may look correct while its confirmation fails. A booking link may open successfully while offering the wrong service. A visible email address may work better than a broken form, but that is a fallback to document, not a reason to leave the form broken.

Separate an attempted action from its outcome. Clicking a phone link does not establish that a call connected. Submitting a form does not establish that the person was qualified. A booked appointment does not establish that the appointment happened.

Build a baseline with interpretable measures

Save a Search Console view for the relevant pages, query groups, dates, country, and device. Its Performance report includes clicks, impressions, click-through rate, and average position. Keep the selected dimensions attached to your export. Search Console documentation

For the website, define which actions matter. Google Analytics lets a business mark important events as key events. The label does not itself verify that the event is correctly implemented or that the lead became a customer. Google Analytics key-event guidance

A small baseline can include search clicks to service pages, measured inquiry submissions, confirmed bookings, and qualified inquiries reviewed by the business. Keep unknowns visible. If analytics is absent or untested, say that the baseline is incomplete rather than entering zero.

Turn the findings into a short repair queue

Here is a synthetic example for a fictional mobile repair business. These are invented audit inputs, not measured customer outcomes.

Fix confirmed customer-facing errors first. Then investigate discovery gaps and decide whether a new page is warranted. Keep speculative ideas in a separate queue with the evidence needed to justify them.

For each completed repair, record the before and after state. Repeat the same search observations later, but avoid attributing every movement to the repair. The immediate proof of success is that the wrong hours, misleading coverage, or broken action was actually corrected.

The Radius 30 toolkit is a starting point for organizing local search work. For a scoped review of the business and its next priorities, see the NorthSignal Growth Audit. Continue with the local SEO guides when you have the baseline in hand.