Local rankings depend on Google seeing one consistent business identity, yet most sites quietly declare different phone numbers or addresses across pages. This tool reads the real local identity your site tells Google and checks it for consistency before you spend on citations.

Local SEO audits the on-site local signals in your structured data, checks Google Business Profile readiness, and flags name/address/phone inconsistencies.

Why teams choose it

What you get

Local signals from your markup

Your on-site local signals, read from JSON-LD — so the details engines use to rank you locally are correct.

GBP readiness

A checklist for Google Business Profile completeness, the biggest local ranking lever.

Consistent NAP

Name, address and phone consistency checked across your site, because mismatches quietly sink local rankings.

Capabilities

Inside Local SEO

01

Real local identity extraction

The canonical business name, phone, address and geo coordinates are read directly from the Organization and LocalBusiness structured data on your crawled pages. Coverage is reported for each local schema type, including PostalAddress, GeoCoordinates and ContactPoint, with the share of pages that declare each one. Detected sameAs profiles such as Facebook, LinkedIn, YouTube and Instagram are surfaced from the same real markup.

Organization and LocalBusiness identity
PostalAddress, GeoCoordinates and ContactPoint coverage
Canonical name, phone and address
sameAs social profiles detected in schema

02

Site-wide NAP consistency check

Pages carrying a telephone are sampled across the site and their canonical phone and street-address values are tallied to count how many distinct variants exist. Phone numbers are normalized with RFC 3966 telephone rules and addresses are compared by vCard address components, so genuine differences are caught rather than formatting noise. Multiple phone or address variants are raised as findings before you build external citations on an inconsistent identity.

Distinct phone-number variants across pages
Distinct street-address variants across pages
RFC 3966 phone normalization
vCard address-component comparison

03

GBP-readiness checklist and gaps

A nine-point readiness checklist scores the identity fields your schema declares, covering name, phone, street address, locality, geo coordinates, opening hours, logo, email and social profiles. Each missing field returns a specific fix atom describing exactly what to add to the LocalBusiness markup. Live Google Business Profile reviews, posts and local-pack rankings need an external connection, so those stay honest empty-states and are never guessed.

Nine-point GBP-readiness score
Specific fix atom per missing field
Geo coordinates linked to a Google Maps check
Live GBP and rank data kept as honest empty-states

Real data

What you can see

Concrete signals this system surfaces — measured, never fabricated.

Organization or LocalBusiness schema presencePostalAddress, GeoCoordinates and ContactPoint coverageCanonical business name, phone and addressDistinct phone and street-address variantsOpening hours, logo and email in schemasameAs social and directory profilesGeo coordinates with a Google Maps check linkGBP-readiness checklist score

How it works

From signal to action

1

Crawl the schema

Every JSON-LD business node on your pages is read for local identity types.

2

Resolve identity

The canonical name, phone, address and geo are taken from the primary Organization or LocalBusiness graph.

3

Check consistency

Phone and address values are sampled site-wide and normalized to count distinct NAP variants.

4

Score readiness

The nine-point GBP checklist runs and returns a fix for each field the schema is missing.

What's included

Google Business ProfileNAP Citations

In your plan

On every plan · install from the App Center

Compare plans →

On-site local signals are crawl-derived and real; operator-entered rank and citation tables show an honest empty state until you add data.

Who it's for

Built for how you work

Local business owner

Confirm the site tells Google a single, consistent name, phone and address before investing in local visibility.

Multi-location marketer

Spot pages that declare a different phone number or street address and reconcile them to one canonical identity.

SEO consultant

Prepare a Google Business Profile by seeing exactly which identity fields the site's structured data is still missing.

The honest difference

Built to be trusted

It reads the NAP your site actually declares to Google in structured data, rather than a form you have to retype.

Live GBP reviews, posts and local-pack rankings stay honest empty-states until you connect them, so nothing is fabricated.

NAP comparison uses real normalization standards, including RFC 3966 for phones and vCard address components, to catch true differences.

The platform

Works well with

Site Trust & SecurityA trust and security scorecard for your site — … Decision LadderAudit the journey from search click to conversion — …

FAQ

Common questions

Does this connect to my Google Business Profile?

Not yet. Live GBP reviews, posts, categories and local-pack rankings require an external connection and are shown as honest empty-states until then.

Where does the NAP come from?

It is read from the Organization and LocalBusiness JSON-LD on your own crawled pages, so it reflects what your site actually declares.

What if my site has no local schema?

It flags that no Organization or LocalBusiness identity was detected and tells you exactly what markup to add to the homepage.

Can it track local-pack rankings?

Not on this data source; the rank and third-party citation tables stay empty until a SERP or GBP connection is added, and are never faked.

Local SEO, and the whole platform behind it.

Request your invite to start, or see exactly what's included at each tier.

Request invite Compare plans