Local SEO audit: profile, citations, reviews and local pages

This page is for the managing director or marketing director of a business with one or more locations whose visibility in Google Maps and in geolocated results stays unstable. It helps you decide what a local SEO audit has to check (local pages, business profile, citations, reviews, local authority), how to make its findings verifiable, and in what order to fix what it reveals.

What a local visibility audit checks, and over what scope

If your local search optimization strategy is progressing without stabilizing visibility, the audit establishes a verifiable diagnosis. Every check serves to (1) prove a problem, (2) attribute it to a probable cause, (3) prioritize a fix with a measurable effect. It extends an SEO audit to what no crawl picks up on its own: a business profile, third-party citations, a review profile.

Two surfaces do not reward the same things: the local pack (the three results with the map) and Google Maps on one side, the geolocated organic results on the other. Two rankings, therefore two families of causes.

Frame the scope first, otherwise the report will be "technically correct" but unusable:

• Type of organization: single location, multi-location network, service area (no public premises) or hybrid.
• Areas actually served, and "unserved" areas, to be excluded so as not to blur the signals.
• Measurable objectives: calls, quotes, directions, appointments, visits, B2B leads.

For a service area, the address hidden on the public profile stays filled in and situates the business; only the visible NAP is reduced to name and phone number. Nor are the declared areas the only geographical signal: the content of the site, the citations and the user's real proximity weigh as well.

Local demand already exists: 46% of Google searches have local intent (Webnyxt, 2026), a benchmark sourced in the SEO statistics. The audit therefore checks the clarity of "offer ↔ area ↔ proof" in the areas actually served.

Finally, set the rule of the diagnosis: one entity, one single point of truth; any difference in address or phone number from one medium to another weakens the findings. The deliverables follow from it:

• findings, each with its probable cause;
• quick fixes;
• structural work;
• indicators that separate visibility, actions and conversions.

Measuring local visibility: the SERP, the gaps, the baseline

Mapping starts from a list of local queries (service, service and town, proximity), crossed with potential: a query that is weak in one town becomes structural across a network. Attach each query to one target page and one only.

What the local SERP shows, and why it changes from one area to another

Analyse the SERP on an "activity + town" query: presence in the local pack, the players displayed, the elements that dominate the screen, the position of organic. Crossing the two surfaces points to the family of causes:

Observe from several locations and at different times: an "average" reading hides the areas where you are absent… and those where you already dominate.

The three gaps to record, and the baseline that will make them verifiable

Identify three high-yield gaps:

• High impressions, low CTR: often a problem of title, promise or intent.
• Good visibility, wrong page served: the home page comes up in place of a "service + town" page, a signal of architecture or internal linking.
• Positions in the middle of the first page on strategic queries: the page is indexed and understood, the gap plays out on local relevance and trust signals.

Check cannibalization: if two pages compete for the same intent, Google alternates the URLs, and the audit decides between consolidating, differentiating or clarifying the internal linking to "elect" a target page.

Then freeze a baseline over 28 days (or a representative business cycle), from three sources:

• Search Console: impressions, clicks, local queries.
• Analytics: conversions per local page.
• Google Business Profile: calls, directions, site clicks.

It avoids a seasonal false positive and separates "visibility" KPIs from "business" KPIs: impressions can rise while clicks fall.

Local architecture: which pages must exist, and which ones Google sees

A page that exists "in the CMS" but is absent from internal linking is an orphan, and therefore useless.

Choosing the page model: location, service area, service + town, FAQ

The model depends on intent and on how you operate:

• a location page if you have premises open to the public;
• a service-area page if you work at the customer's site;
• a service page if the intent is "offer";
• an FAQ page if it is informational.

The audit does not for all that call for a page per declared area: a local page is justified by content of its own, and near-identical area pages produce the opposite effect. For each intent, it compares the page that answers and the proof it provides:

Depth, hubs, invisible pages and town/district duplication

Audit what internal linking lets Google see:

• the click depth of local pages: too deep, they receive fewer internal signals and are recrawled less often;
• the "services" and "areas" hubs that distribute authority;
• contextual links from high-traffic pages;
• the accuracy of the anchors;
• in a network, the links from each location to its own local pages, not to the home page;
• canonicals wrongly set on "town" pages, list pages ("our branches") out of crawl, facet URLs that get ahead of the area pages.

The indexing rules for these URLs belong to the technical SEO audit. That leaves local duplication: faced with near-identical town pages, the audit decides between consolidation, real differentiation (proof, cases, constraints) and clean removal, listing template by template the fields that are unique and those that stay shared.

Local pages: what has to be unique, verifiable and extractable

A local page is judged on two qualities: unique and proven for the user, readable and extractable for the engines, without looking for "more keywords".

What has to be unique and proven on a local page

Check what carries the intent:

• Titles: unique, intent-driven, with a location, within a 50–60 character constraint so they stay readable in the SERP.
• Hn structure: a single H1, then H2s and H3s that answer the local questions (lead times, area, terms).
• Precise areas covered: districts and neighbouring towns, consistent with the profile; lead times and terms of service.
• Proof that cannot be copied: work delivered, feedback, photos, local customer cases, constraints, anything that cannot be carried over from one town to the next; where relevant, price or method benchmarks, with no promise you cannot keep.

Local E-E-A-T is verified through the absence of ambiguity: who operates, where, with what qualifications. On the SERP side, the meta description carries the local promise: it is the one you rework when a page combines high impressions and low CTR.

Reassurance and extractability: readable contact details, answer blocks, local markup

Many losses come from simple friction (a phone number that is not tappable on mobile, missing opening hours, a barely visible CTA): check for a readable contact block above the fold, especially on an "emergency" page.

Add an extractability check: the page says about the entity what the profile and the citations say, in a form an engine can pick up:

• short answer blocks: lead times, areas, terms;
• verifiable data: address, opening hours, phone number;
• concrete proof rather than generic assertions.

Finish with the markup: the consistency between the schema (LocalBusiness, Organization, Address, Review, FAQPage) and what the user sees on the page. It serves to describe the entity unambiguously, not to obtain a display: the FAQ one is reserved for few sites, and the reviews a business awards itself on its own site no longer earn stars.

The Google Business Profile: what the audit checks

The Google Business Profile (formerly Google My Business) is often the first landing page in local search, and part of the searches end there without a visit to the site: an incomplete profile costs calls.

Critical information and risky practices

The audit checks what governs entry into the local pack:

• NAP: strictly consistent with the site and the citations.
• Opening hours, special hours included.
• Primary category and secondary ones: a frequent source of relevance gaps.
• Attributes: accessibility, appointment booking, terms of service.
• Risky practices: avoid keyword stuffing in the business name.

A NAP inconsistency or a badly chosen category is sometimes enough to prevent appearance in the local pack. Then read the conversion sections (services, recent photos, up-to-date posts) as a journey: is the reassurance immediate?

Service areas: consistency between profile, site and proof

The audit aligns three terms: the service areas declared on the profile, the local pages on the site and the proof (jobs actually done, local cases). Their divergence weakens positions in Maps.

A clear and proven service area is worth more than a wide perimeter. The record fits on one line per area: what attests to it, and the page that answers it if there is enough to fill it. The absence of a page is not a ground for withdrawal; the absence of real activity is.

Duplicates, ownership and profile governance

Two problems block visibility in Maps: duplicate profiles (variants of address or of a former trading name), which fragment the signals, and risky signals (a non-compliant name, uncontrolled edits), which expose you to restrictions.

Then check the ownership, the access rights and the edit history of each profile: an unclaimed profile is one anybody can edit. Across a network, the audit adds governance:

• naming rules;
• a shared information template;
• a process for updating opening hours;
• control of user-suggested edits.

Citations and NAP consistency: classify the gaps before fixing them

Local citations are the mentions of your business across the web (directories, platforms, partner pages), NAP included. List the ones that come up in your local SERP, a good proxy for what Google "sees", and their NAP and URL variants.

The point is not "adding more directories", but classifying the inconsistencies that create doubt about the entity:

A NAP fix is validated against the baseline: it can limit the loss of calls and directions without an immediate rise in organic positions.

Across a network, the audit produces a data standard (address format, naming, main number against local lines, destination URL) and a mapping table linking location, official NAP, local page and profile. Without standardization, every new location adds to the debt.

Reviews: what the audit reads in them, and what it draws from them

A review is both a local ranking signal and a piece of proof that can be reused on a page.

Reading the review profile, and what it reveals about the local pages

Reviews are read as a flow:

• volume and momentum: steady acquisition or in fits and starts;
• recency;
• the spread of ratings from 1 to 5;
• response rate.

A rating above 4 stars remains a trust benchmark in many markets, but above all the audit establishes whether the profile is "alive" and whether you respond systematically.

Then turn the reviews into data: themes to reuse, irritants, and above all missing proof (a "fast call-out" praised in the reviews but absent from the pages). Some content helps conversion without weighing on ranking: the audit links "reviews → content → conversion".

Responding and acquiring: a protocol you can check

The response protocol can be observed on the profile, location by location:

• a response to 100% of reviews, positive and negative, with a target turnaround;
• a professional tone, without disclosing personal information;
• negative reviews handled in three stages: acknowledgement, solution, offline contact;
• reporting only if the review breaches the rules.

On the acquisition side, regularity weighs more than one-off pushes. The audit checks three practices:

• choosing 2 to 3 touchpoints: end of the job, follow-up e-mail where permitted, QR code at the point of sale;
• helping the customer write a useful review with 2 factual questions: "what did we work on?", "what helped you most?";
• tracking a cadence indicator per location.

Two safeguards frame this collection, and the audit checks them: no paid incentive (a discount, a gift, a prize draw), and no solicitation reserved for satisfied customers, since this sorting distorts the profile as much as it exposes you to the platforms' rules.

Local authority, and in what order you fix things

Five criteria assess a local link without confusing volume with relevance:

• trust in the site;
• topical relevance;
• geographical relevance: a local player, an event, an association, the regional press;
• editorial context;
• destination URL, ideally the local page concerned.

A few contextual links to the right page can make the difference: the audit checks the alignment of "link → page → intent → area" and entity inconsistency (a partner displaying an old address). The overall authority of the domain belongs to the link building audit.

Finally comes the order of correction, in three ranks:

Within a rank, decide with the impact × effort × risk grid of the SEO audit.

Monitoring then takes over: reviews, profile and critical inconsistencies are tracked continuously, within the monthly tracking routine; the full audit comes back every year or on an event, in batches for multiple locations. Allow 2 to 6 months to observe results; the tooling is chosen with the SEO audit tools.

Continue reading

Depending on what the audit has established, one read takes over:

• The local diagnosis is done and you now have to run it: the method to perform an SEO audit leads through to the prioritized backlog.
• You want to know whether your local pages are being picked up: the AI GEO audit measures share of voice, sources cited and the accuracy of answers.
• The problem concerns image rather than ranking: e-reputation analysis looks at what the SERP and the platforms say about the brand.
• The fixes are delivered and you have to prove their effect: SEO tracking sets out KPIs, annotations and the control of gains.
• The profile is incomplete and you have to make it live: claiming, posts and photos belong to the Google Business Profile.

Bringing the crawl, Search Console and Analytics together in a single record, for local pages spread across several locations, is the task covered by the audit and mapping module.

FAQ on the local SEO audit

How do you run a complete local SEO audit, step by step?

A complete local SEO audit is run object by object, in the order in which each one governs the next: local SERP, architecture, local pages, Google Business Profile, citations and NAP, reviews, local authority. A 28-day baseline is frozen before any fix, and every finding is given a probable cause.

Which points are the most urgent, between the website and the Google Business Profile?

The most urgent points are those that cancel out the efforts that follow: an incomplete or badly categorized profile, NAP inconsistencies between site, profile and citations, local pages that are not indexable or are orphaned. Then comes trust (citations, reviews, responses), then the yield of pages close to the first page.

Why does a Google profile not come up in the local pack despite an optimized site?

A profile can stay out of the local pack despite an optimized site, because the pack and geolocated organic are two distinct rankings. Look for the cause in the profile: categories, completeness, NAP, reviews, areas. Against more prominent competitors, it is proof your entity lacks, not tags your pages lack.

Which on-page checks are essential for a "service + town" page?

A "service + town" page must carry a unique title with the promise and the location, a clear H1 and H2/H3s that answer the local questions. Add proof specific to the town, a contact block readable on mobile, internal linking from the hubs and markup that is faithful to the page.

How do you audit NAP consistency and fix citations at scale?

NAP consistency is audited by listing the platforms visible in your local SERP, then classifying the gaps: minor, structural, duplicates. Structural gaps and visible platforms come first. Across a network, a data standard and a mapping table make the correction manageable.

Which review indicators have an observable impact on local SEO (volume, recency, themes)?

The review indicators that are useful in an audit are recency, regularity of acquisition, the spread of ratings, responses and recurring themes. Some themes improve conversion without weighing on ranking: the audit treats them as proof to publish, not as a ranking lever.

How often should a local audit be redone, for a single location versus multiple locations?

A full local audit is redone every year or on an event: opening, relocation, change of area, redesign. Between two audits, tracking is monthly, and reviews, profile and critical inconsistencies are monitored continuously. Across multiple locations, profile control becomes permanent and the re-audit is done in batches.

How do you tie the local SEO audit to lead and revenue objectives in B2B?

You tie the local audit to revenue by attaching local KPIs (calls, forms, directions) to pages and areas, then validating each batch of fixes with a before/after against the baseline. The ROI of local SEO for SMEs is x3 compared with other channels (HubSpot, 2025).