NAP consistency describes whether a business's name, address, and phone number agree wherever those details are represented. A public Revvye scan can compare visible page text with machine-readable declarations on the submitted surface, not every external directory by default.
NAP Consistency
The operational definition, the public evidence boundary, and the nearby concepts an operator needs before using the term in a diagnosis.
Definition before diagnosis.
What the term can—and cannot—support.
Read the definition as a contract. It keeps a useful public observation from expanding into an outcome the scan cannot see.
- 01
Name, address, and phone details help visitors and machines connect a page to the right business and location. Differences between visible contact details and structured data can create ambiguity even before an external listing is considered.
- 02
A complete directory audit requires the relevant profiles or source records. Without those inputs, Revvye limits the finding to what the submitted page and its public declarations expose and does not claim network-wide consistency.
The term travels with its limit.
- 01Observe
Inspect the submitted public surface and the declarations it returns.
- 02Preserve
Keep the rule, page signal, severity, and stated limitation together.
- 03Exclude
Do not infer private revenue, conversion, delivery, or customer behavior.
Inspect the public path. Keep the private result private.
The free scan begins with the page you submit and routes its result through a private email-linked intake. It does not access private analytics or CRM data.
Public pages only. The $97 report comes after the result.