Local signals from your markup
Inspect the local business fields captured from your JSON-LD without claiming how a search engine will rank them.
Get found in your area, local signals, Google Business readiness and NAP consistency.
Local SEO audits the on-site local signals in your structured data, checks Google Business Profile readiness, and flags name/address/phone inconsistencies.
On every plan, install from the App Center
On-site local signals are crawl-derived and real; operator-entered rank and citation tables show an honest empty state until you add data.
Why it is useful
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.
Inspect the local business fields captured from your JSON-LD without claiming how a search engine will rank them.
Use Novaverb's own checklist for operator-entered Google Business Profile fields; the checklist is not a Google verdict.
Compare name, address and phone values found on captured project pages and review the exact mismatches.
Data and evidence
Local SEO reads the business identity your own pages declare: Organization or LocalBusiness schema, PostalAddress, GeoCoordinates and ContactPoint coverage, and every distinct phone number and street address found across the crawl. It reports what your site says about you, which is what a search engine has to work with.
Crawl and optional GBP API
Canonical NAP resolver
Local consistency fix queue
On-site local signals are crawl-derived and real; operator-entered rank and citation tables show an honest empty state until you add data.
Core capabilities
You get identity extracted from real markup, a site-wide consistency check that lists each variant of your name, phone and address and the pages carrying it, and a Google Business Profile readiness checklist with the gaps named. Inconsistency is shown as the specific pages that disagree, so it can be fixed.
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.
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.
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.
How the work moves
Crawl the schema, resolve the canonical identity, check consistency across the site, then score readiness. Each re-crawl re-derives the identity from the pages as they now stand, so a correction on one template is confirmed rather than assumed to have propagated.
Every JSON-LD business node on your pages is read for local identity types.
The canonical name, phone, address and geo are taken from the primary Organization or LocalBusiness graph.
Phone and address values are sampled site-wide and normalized to count distinct NAP variants.
The nine-point GBP checklist runs and returns a fix for each field the schema is missing.
Built around real work
Confirm the site tells Google a single, consistent name, phone and address before investing in local visibility.
Spot pages that declare a different phone number or street address and reconcile them to one canonical identity.
Prepare a Google Business Profile by seeing exactly which identity fields the site's structured data is still missing.
Resources
Written by the team that built it, and free to read without an account.
What the terms on this page actually mean.
Run the idea on a real URL, no account needed.
Connected products
Frequently asked questions
Clear answers about data, availability and how the product fits into the wider workflow.
Not yet. Live GBP reviews, posts, categories and local-pack rankings require an external connection and are shown as honest empty-states until then.
It is read from the Organization and LocalBusiness JSON-LD on your own crawled pages, so it reflects what your site actually declares.
It flags that no Organization or LocalBusiness identity was detected and tells you exactly what markup to add to the homepage.
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.
Trust & Experience
Start with a real project, keep unavailable data visible and follow the connected workflow when the result is ready for action.