CrawlCheck

Agent view · Guides · 2026-09-30

NAP consistency: how to check your name, address and phone

This is the response this server returns to a client that asks for Accept: text/markdown at https://crawlcheck.io/guides/nap-consistency-audit-phone-address-and-coordinates: fetched when you opened this page, shown byte for byte. An assistant, a crawler that negotiates markdown, or anything reading our feed gets exactly this. The markdown leaves signed (RFC 9421, key in our key directory), so a crawler can prove the page it read is the page this server sent; the check is shown below.

status200
content-typetext/markdown; charset=utf-8
varyAccept
link<https://crawlcheck.io/llms.txt>; rel="describedby"; type="text/plain", <https://crawlcheck.io/.well-known/api-catalog>; rel="service-desc"; type="application/linkset+json", <https://crawlcheck.io/guides/nap-consistency-audit-phone-address-and-coordinates>; rel="cite-as", <https://crawlcheck.io/.well-known/http-message-signatures-directory>; rel="http-message-signatures-directory"
cache-controlpublic, max-age=900, stale-while-revalidate=2400
bytes16,260
words2,374
sha-256901132f6e488040f09bbadb8dbd3ed9261b3b8727aa1d66004a86ad80914fda6
repr-digestsha-256=:kBEy9uSIBA8Ju62429PtkmGzuHJ6odZgBKhq2AkU/aY=: ← matches the body shown
signature-inputsig1=("@authority";req "@path";req "repr-digest" "content-type");created=1795182378;expires=1795185978;keyid="1hHmE3fo1rg5Ig70wuFtJ5wBc7G-sUTgUJkxyPWFRps";alg="ed25519";nonce="cGokzyUpd7C-wC-6KRmlIA";tag="crawlcheck-page"
signaturesig1=:YvUe9V047RU4eVQMdzibQuJNDQXo9TAAvsTzLWmgeLVeOwpkS9rhrxcrqiJ1DHxu3xC6kn6UBMzZDeK5Al3MAg==:
verifiedyes — signature by key 1hHmE3fo1rg5Ig70… from https://crawlcheck.io/.well-known/http-message-signatures-directory (directory valid), valid for 3600 more s. Checked here exactly as a crawler would; redo it yourself: https://crawlcheck.io/api/tool/wba
Guides · 2026-09-30 · By [VSNARY | Emmanuel Orta](/author) · 1 view

# NAP consistency: how to check your name, address and phone

Five checks on name, address and phone: what your own page declares, what the directories reached by your phone number say back, and how to read a directory that refuses to answer.

Search engines and AI assistants match a local business by its name, address and phone (NAP), and the phone number does most of the work. Check your own page first: an address with no map coordinates, coordinates outside the address's country, and two business records sharing one phone, @id or point. Then search directories for your phone number in a normal browser, and fix listings that print a different name or that your site never links in sameAs. A directory that refuses an automated search has not told you anything.

Check your own site free

Check my site

About a minute. First scan free with your email, nothing installed.

On this page

- What does your own page declare?
- What do the directories say back?
- What if two business records on one page share a phone?
- What a phone search cannot tell you
- Does a listing with a data aggregator change Google?
- How to run it by hand

The phone number is the field that identifies a local business. It is written the same way everywhere and is rarely shared, so a system that finds your number on a directory page has found you, whatever name that page prints. These are the five checks we run on the three [NAP](/glossary/nap) fields, the share of scanned sites each one catches, and how to run them yourself.
Two passes: what your page declares, then what each directory reached by your phone number says back. A refusal is recorded as unchecked.

## What does your own page declare? #

Start with the page’s own [JSON-LD](/glossary/json-ld): the `LocalBusiness` or `Organization` node with its `name`, `address`, `telephone` and `geo`, and compare it with the footer a visitor sees. Two checks need nothing else.

**An address with no map point.** The business node gives a street address and no latitude or longitude, so every system that reads it has to geocode the text itself. That is where a similarly named business on the next street gets picked instead. Share of scanned sites with this finding: **6.1%**.

**A point outside the address’s country.** The declared coordinates land in a different country from the address. One Denver newsroom published a point in northern China: the longitude had lost its minus sign, which still leaves a valid longitude, so no validator objected until something compared the point with the country. Share of scanned sites: **0.5%**.

## What do the directories say back? #

Take the phone number your page declares and search the business directories for it. Every search ends one of three ways: a listing found, no match, or a [refusal](/glossary/refusal). Some directories refuse automated requests from datacenter addresses and answer a normal browser at once; [Data Axle](/glossary/data-axle)’s listing search does exactly that, which is why [a scanner reported it as unreachable until a browser asked](/blog/where-google-and-ai-assistants-get-business-data). Run those searches yourself.

**A listing your site never links.** A directory listing carries your number and your JSON-LD has no `sameAs` link to it. An engine can still corroborate that listing, so whatever it prints becomes your name, hours and category in an answer. Share of scanned sites: **3.6%**.

**A listing under a different name.** A listing reached by your phone number prints a name that does not match the one your site declares. Two names on one number look like two businesses to a [retrieval](/glossary/retrieval) system, and the older name usually has more corroboration. Share of scanned sites: **0.6%**.

## What if two business records on one page share a phone? #

The fifth check reads only your page: two `LocalBusiness` or `Organization` nodes that share a phone number, an `@id` or a coordinate pair. It does not mean the business is duplicated. It means a system working out which business the page is about has two candidates for one identity and may pick either or neither. The usual cause is a theme that emits its own business node beside the one a plugin emits. The fix is one node, referenced from the others by `@id`, as [the JSON-LD identifier guide](/guides/json-ld-id-and-iri-errors-what-breaks-and-how-to-fix-them) shows. Share of scanned sites: **2.6%**.

| Check | What to read | What it means | Fix |
| --- | --- | --- | --- |
| Address with no map point | JSON-LD `address` and `geo` | Readers geocode the text and may pick a neighbour | Add `geo` latitude and longitude |
| Point outside the address’s country | `geo` against the address | One record disagrees with itself about where you are | Check the sign on the longitude |
| Listing found, not linked | Directory results by phone, then `sameAs` | A record you do not control speaks for you | Add the listing [URL](/glossary/url) to `sameAs` |
| Listing under another name | Directory name against your declared name | Two entities on one phone number | Correct the listing or claim it |
| Two business nodes share phone, @id or point | Your page’s JSON-LD | No single record is clearly you | Keep one node, reference it by `@id` |

## What a phone search cannot tell you #

No match is not proof the business is unlisted; it means the number, in the format searched, did not match, and formatting alone can cause that. A refusal says nothing about the listing at all, so record it as unchecked. And a match is not proof of ownership: a franchise and its parent, or a business and its former owner, can share a number. Only the owner can say whether a matching listing is theirs.

## Does a listing with a data aggregator change Google? #

Not on the evidence we have. Google’s compiled provider list names several suppliers, Data Axle among them, but it also carries long-retired sources, so a name on the list does not show Google uses that source today. Of nine businesses we checked, eight rank in Google’s map pack with no Data Axle record at all. Fix the listings that print the wrong facts because people and other systems read them; do not expect one directory to move Google. The full picture is in [where Google and AI assistants get business data](/blog/where-google-and-ai-assistants-get-business-data).

## How to run it by hand #

- Open your homepage source and find the business node. Write down the name, phone, address and `geo` values exactly.
- Put the coordinates into a map and confirm they land on your address. Check the sign on the longitude.
- Search each directory you care about for your phone number, once as your site prints it and once as digits only, from a normal browser.
- For every listing found, note the name it prints and whether its URL is in your `sameAs` array.
- Correct or claim listings with the wrong name, and add every listing you own to `sameAs`.

A free scan on [crawlcheck.io](/) runs the page checks and the phone search across the directories it can reach, and shows which ones refused. The share of scans carrying each finding is on [the dataset page](/data).
Read live from the same counters the dataset page uses, at the moment this page was served. Bars are scaled to the largest value shown, not to 100%.

Written by

[Emmanuel Orta](/author) · VSNARY

I build CrawlCheck and write everything published here, from measurements the verification layer took. Where a post got something wrong, the correction stays in the post.

[Every post, and where I got it wrong →](/author) · [Follow on LinkedIn →](https://www.linkedin.com/in/emmanuelorta)

Share this finding: [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcrawlcheck.io%2Fguides%2Fnap-consistency-audit-phone-address-and-coordinates%3Futm_source%3Dlinkedin%26utm_medium%3Dsocial%26utm_campaign%3Dshare)[X](https://twitter.com/intent/tweet?url=https%3A%2F%2Fcrawlcheck.io%2Fguides%2Fnap-consistency-audit-phone-address-and-coordinates%3Futm_source%3Dx%26utm_medium%3Dsocial%26utm_campaign%3Dshare&text=NAP%20consistency%3A%20how%20to%20check%20your%20name%2C%20address%20and%20phone)[Email](mailto:?subject=NAP%20consistency%3A%20how%20to%20check%20your%20name%2C%20address%20and%20phone&body=https%3A%2F%2Fcrawlcheck.io%2Fguides%2Fnap-consistency-audit-phone-address-and-coordinates)[Follow Emmanuel on LinkedIn](https://www.linkedin.com/in/emmanuelorta)

## Questions this post answers

### Why search directories by phone number rather than business name?

The phone number is written the same way everywhere and is rarely shared, so a directory page carrying it identifies the business whatever name the page prints. A name search finds namesakes; a phone search finds you.

### What is an undeclared listing?

A directory listing that carries your phone number but is not linked from your site's sameAs. An engine can corroborate it without you, so whatever it prints becomes your name, hours and category in an answer.

### What does NAP name drift mean?

A listing reached by your phone number prints a business name that does not match the one your site declares. To a retrieval system that is two entities on one number, and the older name usually carries more corroboration.

### Do I need latitude and longitude in my LocalBusiness schema?

It is worth adding. A business node with a street address and no point forces every reader to geocode the text, which is where confusion with nearby or similarly named businesses comes in. Declaring the point removes the guess.

### Why did a directory refuse the search?

Some directories refuse requests from datacenter addresses and answer a normal browser straight away. A refusal is not evidence about the listing, so search that directory yourself from a browser and record the result.

### Will claiming a Data Axle listing improve my Google ranking?

There is no evidence that it does. Google's compiled provider list names several suppliers and also carries retired ones, and eight of nine businesses we checked rank in the map pack with no Data Axle record. Correct wrong listings for accuracy, not for ranking.

## Related findings

[2026-08-19 AI visibility vendors audited: 11 of 23 have llms.txt We ran SEO and AI-visibility vendors through our own checks: 11 of 23 graded sites publish llms.txt, none an entity map, and two r](/blog/we-scanned-the-tools-that-audit-your-site)[2026-10-03 Rich Results Test vs Schema Markup Validator vs CrawlCheck Rich Results Test, Schema Markup Validator and CrawlCheck compared: what each checks, valid markup that contradicts the page, and](/guides/schema-validators-compared-rich-results-test-vs-schema-markup-validator)[2026-10-21 Google AI Overview sources for Denver tree removal cost What Google's AI Overview cited for a Denver tree removal price question: six sites, what kind of page each is, and what every cit](/blog/google-ai-overview-tree-removal-cost-denver-six-sources)

The main product

Found this on your own site? **We fix it for $100.**

Scan free to see where you stand. The fix is one site, every finding implemented and re-measured, with a sealed before and after.

[Fix it all — $100](https://buy.stripe.com/4gM00j7OjawhdLEdyR2VG0v)
[What it covers](/pricing#fix) · [scan first, it is free](/)

Free browser extension

Check this on any site you open, **without leaving the page.**

CrawlCheck for Chrome grades every site you visit A–F and shows, from your own browser, what search engines and AI assistants are actually served. Free, no account.

[Add to Chrome — free](https://chromewebstore.google.com/detail/plgjengobhbdmbgckiiaaflgiepdbcpi?utm_source=crawlcheck.io&utm_medium=post)
[What it does](/extension)

Write for the library

Measured something yourself? **Submit an article.**

Send your finding, the data and the method. A person reads every submission and replies by email; accepted articles are published under your name with a link to your study. Free to submit. Articles are accepted on merit; no one can pay to have one published.

[Submit an article](/submit-finding#send)
[How it works](/submit-finding) · a reply within about a week

Spotted a mistake or a bug on this page? [Report an error](/report-error?k=article). Confirmed errors are fixed and logged on the [corrections page](/corrections).

## Comments

Comments are read before they appear. Nothing is published automatically, and no account is needed. An AI agent with a published signing key can post without the queue: it signs the request and the signature is checked against its own domain ([how](/api/comment/signed)). Those appear at once, marked *verified*.

Send for review

Writing about this? [Facts, live figures and marks](/press) — every number on that page is dated and traceable to a scan.

[All guides](/guides) · [The dataset](/data) · [How the dataset works](/policy)

We read your site the way crawlers do, from our own network, and every report says exactly what was asked for and what came back. [Who runs this](/author) · [Press kit](/press) · [Videos](/videos) · [Evidence for disputes](/evidence) · [YouTube](https://www.youtube.com/@crawlcheck) · [hello@crawlcheck.io](mailto:hello@crawlcheck.io)

#### How we measure, and our own machine files

CrawlCheck reads every site as itself. Its crawler-identity tests send named user-agent strings from its own network, never from an operator’s published range, so a site that verifies crawlers can tell them apart; every report says so. Results reflect what an anonymous non-browser client receives. [What we collect and how to opt out](/policy) · [how every report is timestamped](/proof) · [who runs this](/author) · [press kit](/press) · [hello@crawlcheck.io](mailto:hello@crawlcheck.io).

**Second vantage:** the [browser extension](/extension) measures what crawlers are served from your own address and after your JavaScript runs — the half this server cannot see. From 1.0.0 it sends the domain you ask about, on one button, and anonymous usage counts you can switch off; from 1.0.3 a footer switch turns off the hostname lookup for the grade on the icon; from 1.0.4 a share switch, on by default, sends a signed Two-vantages reading (status, size, words and a hash per identity; never page text); from 1.0.16 chips send the hostnames of search results and AI citations while the chips and grade switches are on; from 1.0.17 a readings switch, on by default, sends one signed page reading a day (numbers, the hostname and the page address with the query removed; never in incognito; at most 40 a day) and only while the share and grade switches are also on. Earlier versions send nothing.

**Our own machine layer for the agentic web:** [llms.txt](/llms.txt) · [llms-full.txt](/llms-full.txt) · [agents.md](/agents.md) · [SKILL.md](/SKILL.md) · [entitymap.json](/entitymap.json) · [media kit](/.well-known/media-kit.json) · [MCP server card](/.well-known/mcp/server-card.json) · [API catalog](/.well-known/api-catalog) · [OpenAPI](/openapi.json) · [robots.txt](/robots.txt) · [sitemap.xml](/sitemap.xml) · [security.txt](/.well-known/security.txt) — every one named in robots.txt, which is exactly what we check for on yours.

**Pages:** [IP ranges](/data/ip-ranges) · [Keys](/keys) · [/](/) · [Listing check](/listing-check) · [Conduct: Duckduckbot](/agents/conduct/duckduckbot) | **Registry:** [sohu.com](/registry/sohu.com) · [Trade: Phoenix](/registry/trade/roofing/az/phoenix) · [studioxnews.ca](/registry/capabilities/studioxnews.ca) | **Datasets:** [Technologies: Stripe](/datasets/technologies/stripe) · [Problems: Host duplicate 200](/datasets/problems/host-duplicate-200) | **AI crawlers:** [Ccbot vs GPTBot](/ai-crawlers/compare/ccbot-vs-gptbot) | **Blog:** [Six in ten websites already use post-quantum encryption. Whether yours does mostly depends on one thing](/blog/post-quantum-key-exchange-six-in-ten-websites-november-2026)

[Contact](/contact) · [Partnerships](/partnerships) · [Terms of service](/terms) · [Refund policy](/refunds) · [Trust center](/trust) · [Subprocessors](/subprocessors) · [Changelog](/changelog) · [Report an error](/report-error)

Same body as a file: /guides/nap-consistency-audit-phone-address-and-coordinates.md · as data: /feed.json · what we tell agents site-wide: /llms.txt, /agents.md. To see any other site this way, from your own browser, after its JavaScript runs: the browser extension.