Local SEO Audit Checklist for Agencies: From Findings to Fixes
Run a local SEO audit that ends in assigned, verifiable work. Includes an agency checklist, issue register, priority rules, and practical client examples.
The short answer
- Agree which business locations, profiles, pages, and customer actions the audit covers.
- Check the enquiry path early. A working form confirmation is different from a request reaching the right team.
- Record pass, issue, not checked, or not applicable for each check. Missing access is not a pass.
- Prioritize a verified customer or discovery problem before minor presentation changes.
- Deliver evidence, assigned actions, and verification tests. Keep ranking observations separate from completed fixes.
If you need the basics before scoping the work, read what local SEO covers across Maps and website results. This checklist takes that foundation into an agency deliverable.
A local SEO audit can flag a missing meta description and still miss the contact form sending every enquiry to an abandoned inbox. For an agency, the useful output is a prioritized issue register: what failed, the evidence, who owns the fix, and how you will check it. Work through the business profile, website, listings, search observations, and enquiry path together. A scan score alone does not finish that job.
On this page
Agree the audit scope before opening a scanner
Start with a client-approved business record: services, real operating locations, current phone numbers, website, customer access, and the people who can approve changes. Confirm access to the relevant Business Profiles, Search Console property, analytics, and enquiry destination. Record gaps rather than filling them with assumptions.
Define the inventory and sampling method. For a small service business, you might review its homepage, contact page, and important service pages individually. For a larger account, combine a crawl with checks of each important page template and branch journey. State which URLs were inspected and which were only sampled.
An agency agreement should distinguish the audit from implementation. Updating a profile, changing a canonical, or submitting a test enquiry needs the client's authorization and a named owner. Confirm whether the engagement includes making those changes or only recommending them.
Use this record for every check:
| Field | What the agency records |
|---|---|
| Asset and scope | Website URL, profile, branch, directory entry, or customer journey |
| Observation | What happened, when, and under which conditions |
| Check status | Pass, issue, not checked, or not applicable |
| Evidence | Screenshot, source finding, report export, or confirmed receipt |
| Action and owner | The specific change and the person responsible |
| Verification | The test that will establish whether the fix worked |
Follow the checklist through the customer journey
1. Test whether an enquiry reaches the right team
Open the important destination on a phone. Can a customer identify the service and area, use the navigation, find the contact action, and complete it without an obstruction?
Arrange a clearly labeled test with the client. Check the form's required fields, confirmation, delivery destination, and follow-up owner. For a phone route, confirm that the number and destination are correct using the agreed test procedure. Record receipt at the destination, not just the website's success message.
Check branch-specific paths separately. A central phone number may be intentional; a branch page that promises direct appointments but reaches the wrong receptionist needs investigation. A conversion event firing is not proof of an accepted appointment.
2. Check the Business Profile against the actual business
Confirm the correct profile, authorized owner, verification or suspension issues, real-world business name, appropriate category, customer-facing details, hours, services, and destination URL. Check the business's operating model before changing an address or service area.
Google's business representation guidelines govern eligibility and accurate information. A lead-generation domain does not make a separate Business Profile eligible. Record a questionable profile for review rather than creating extra listings to match an agency's domains.
Use the guided Business Profile audit to organize a manual review. It does not sign into Google or independently validate the client's listing. Check its answers against the actual profile and business records.
3. Confirm important pages can be discovered and indexed
Check the live response, redirects, robots directives, canonical, sitemap inclusion where appropriate, and crawlable internal links for each important page. A page can return HTTP 200 while declaring noindex or pointing its canonical elsewhere. Decide which URL should represent the service before proposing a change.
In Search Console, use the Page indexing report to investigate patterns. Then inspect important URLs individually. An excluded URL may be intentional, such as an account page; “index every URL” is not a useful objective.
URL Inspection distinguishes Google's recorded information from a live test. A successful live test does not prove that the URL is indexed or guarantee that it will appear in results. Save the inspected URL, indexed/live view, date, and relevant finding. Do not treat a site: search as a complete index inventory.
4. Review service pages for a clear customer decision
For each important service or branch page, compare the title, main heading, opening, actual offering, service area, and contact action. Read the page rather than counting keywords. Does it answer the visitor's likely questions with accurate scope, useful details, and credible business evidence? When the intended destination is unclear, map local searches to the right pages before assigning another service or branch page.
Google's SEO Starter Guide covers descriptive titles, helpful content, headings, and links. A scanner's heading warning needs interpretation; counting H1s is not a substitute for reading the structure. A missing meta description deserves review without being labeled a proven cause of lost enquiries.
Run the free on-page audit on one priority page to inspect its source. It is a single-page check, not a whole-site crawl or an assessment of the client's expertise. For content rendered with JavaScript, compare the source report with the visible page.
If LocalBusiness markup is present, compare it with the real branch and visible page details. Use Google's LocalBusiness documentation and validation tools. Markup does not establish eligibility or guarantee a search enhancement.
5. Compare business information across customer touchpoints
Start with listings customers actually encounter: the Business Profile, major relevant directories, industry sources, and the client's own website. Compare the business identity, phone, address or service area, hours, and destination URL against the approved record.
Log an old phone number, wrong branch link, closed location, or incorrect hours with its source URL. Distinguish an incorrect fact from a harmless formatting variation. A sample of directories does not establish that every listing on the web is accurate.
Follow the listing correction workflow to get approved changes submitted, resolve access dependencies, and confirm the public result.
For citation work, retain the requested correction, assigned owner, and confirmation. A submission receipt proves you asked for a change; check the live entry before reporting the correction complete. More listings than a competitor is not an audit objective by itself.
6. Inspect review requests and relevant mentions
Review the customer's actual review-request process. Check whether requests seek honest feedback and whether incentives, screening, or a positive-rating condition affect who receives the public review link. Google's Maps contribution policy prohibits incentivized reviews and selectively soliciting positive reviews.
Then dry-run your Google review requests with fictional complaints, opt-outs and duplicate events before enabling messages.
Review relevant business mentions and links for accuracy and useful opportunities. Do not turn a third-party “toxic” score into an automatic disavow list. Google says most sites do not need the disavow tool; investigate an actual manual-action or link-scheme concern before recommending that intervention.
7. Record a repeatable visibility baseline
Keep Maps/local-pack observations separate from organic website positions. Record the query, business or URL, search location, device, surface, date, and checked depth. A single observation across town is not a citywide ranking or a diagnosis of why visibility differs.
Google's local ranking guidance describes relevance, distance, and prominence. Use those factors to frame questions, not to invent a numerical audit score. Compare relevant competitors under comparable search conditions; another business appearing higher does not explain the cause. Use the competitor comparison log to turn those observations into owner-confirmed tasks.
Our local rank tracker comparison explains measurement surfaces and scan budgets. Search Console's Performance report adds website impressions, clicks, and average position over a defined period. It does not replace a precise neighborhood Maps check. State the dates and filters, and keep contact activity and booked work separate.
8. Check mobile use and technical exceptions
Test the real phone layout, navigation, forms, readable content, HTTPS behavior, and important redirects. Investigate performance problems on the pages customers use. If you include a lab speed report, retain its settings and separate that test from the experience of actual visitors.
Old checklists still direct agencies to Search Console's Mobile Usability report. Google retired that report and the Mobile-Friendly Test in December 2023. Use current tools and direct device checks rather than sending a client to a retired report.
Escalate a security warning, manual action, or sitewide discovery problem to the responsible specialist. Record what you confirmed, what remains uncertain, and which changes require further investigation.
Prioritize by the consequence you can demonstrate
Keep check status separate from implementation status. An issue can be confirmed while its proposed fix is awaiting approval. “Not checked” belongs in the report with the missing access or next test, not hidden inside a green overall score.
Use a practical priority rule agreed with the client:
| Priority | Typical reason | What makes it actionable |
|---|---|---|
| Urgent | A verified enquiry route fails, the wrong business is reached, or an important public destination is unavailable | Exact failure, affected asset, responsible owner, and safe next action |
| Next | A confirmed discovery, relevance, or business-information problem affects an important journey | Evidence, intended page or business record, proposed fix, and verification test |
| Later | A lower-impact improvement or a hypothesis that needs more evidence | Reason to defer, investigation needed, and a review point |
These are delivery priorities, not predicted ranking gains. A sitewide noindex mistake may warrant urgent attention, while an intentionally excluded account page needs no fix. Context changes the decision.
Agency example: a plumber's form passes the scanner
Imagine a fictional plumbing client with separate repair and drain-cleaning pages. The drain page loads correctly, has a descriptive title, and displays a success message after a form submission. The client's approved test reveals that the request goes to an old inbox.
The agency records the issue against that page, attaches the labeled submission and failed delivery evidence, and assigns the routing correction to the website administrator. Its verification test is a new authorized submission received in the correct inbox and acknowledged by the agreed owner.
After that test, the agency can report enquiry delivery verified. It cannot report more leads or booked jobs from the change without the relevant outcome evidence. This is a fictional workflow example, not a client result.
Agency example: three dental branches share the wrong destination
For a fictional three-branch dental group, imagine that two directory entries send visitors to the central booking page and one sends them to a closed branch. The audit should preserve a separate branch record and affected URL for each finding.
Confirm whether central booking is intentional before recommending a change. Correct the closed-branch route, check the destination on a phone, and obtain confirmation from the booking team. A blanket “NAP inconsistent” finding would hide the actual customer problem and leave the implementation owner guessing.
The handoff distinguishes each observed issue, intended destination, approved correction, and completed verification. It does not describe an untouched branch as fixed because another branch passed its test.
Deliver an issue register the client can act on
Give the client a concise summary of the most consequential findings, then the working register. Include the inspected inventory, sampling limits, unavailable access, evidence links, priorities, owners, approval needs, and verification status. Retain a dated baseline and a record of changes so a later report can distinguish work completed from search movement.
Download the agency issue-register CSV template. It includes fictional examples and a blank row; replace them with the client's approved facts. Keep evidence links in the client's authorized workspace.
In OpenLocalSEO, keep the website, research notes, page plans, and assigned tasks together. This guide is published by OpenLocalSEO and includes our own workflow. Choose tools around the required checks and handoff, rather than adding another scanner because it produces a larger score. Our local SEO software comparison covers that buying decision.
Agree when to revisit the audit: after a migration, location change, major page release, enquiry failure, or a scheduled account review. Recheck the affected work and important journeys; a recurring audit is not a reason to rewrite every page each month.
Keep reading
- Understand local SEO across Maps and website results.
- Choose a local rank tracker for comparable observations.
- Use the free workbook for client scope and handoff worksheets.
Sources and editorial checks
Primary Google guidance checked 20 October 2026 is linked beside the relevant checks. The Local Rank Academy audit lesson informed the campaign scope. This guide replaces its retired report references and does not adopt routine disavowing, arbitrary listing quotas, or scanner warnings as proof of a ranking cause. The checklist, priority framework, issue register, and client examples are editorial working aids. They are not a ranking forecast or a substitute for inspecting the actual client account.
