Spoke
NAP consistency and citations
Name, address and phone number, identical everywhere. It is clerical work with no creative content, which is exactly why it goes undone and why doing it is an advantage.
That consistent business information supports confident entity resolution follows from how entity matching works and is long-standing local practice. No platform publishes a consistency threshold.
The least interesting work in this field, and reliably among the highest-return. Nobody wants to spend an afternoon correcting directory listings, which is why your competitors have not.
What is NAP consistency and does it still matter?
NAP consistency means your business name, address and phone number appear in exactly the same form everywhere you are listed. It matters because systems resolving which listings refer to the same business look for agreement, and every inconsistency is a reason to hedge rather than merge.
It is the local instance of the general entity problem, and the fix is the same: pick the canonical form, write it down, and correct everything against that record rather than against memory.
Pick the canonical form first
Before touching a single listing, write down the exact strings:
- Name as it legally and publicly is — no appended keywords, no city tacked on.
- Address in one abbreviation style, including the suite format.
- Phone, in one format, and ideally the same number everywhere.
Then that record is the source of truth and the audit becomes mechanical rather than a series of judgment calls made differently by whoever is doing it.
A note on names: adding service terms to a business name in listings is a persistent tactic and it is a misrepresentation of the entity. It also guarantees inconsistency with every other place the real name appears.
The audit
- Search your own name and list every third-party listing in the first several pages.
- Search your old addresses and old phone numbers. This is the step that finds the real damage.
- For each listing: claim it, correct it against the canonical record, note it.
- Hunt duplicates — mergers, moves, aggregator feeds and well-meaning staff all create them.
- Re-run annually. Listings decay and aggregators repopulate.
Step two is the one people skip. Businesses move and nobody tells the directories, so an old address keeps being published to anyone who looks, including systems trying to work out where you are.
Duplicates
Worse than inconsistency, because they split the thing you are accumulating. Reviews land on two records. Prospects reach a page you do not monitor. A system sees two businesses with similar details and has to decide.
Merging is usually a tedious support process rather than a button, which is why duplicates persist. Finding them requires looking rather than waiting.
Where it connects
This is the same work as entity consistency, scoped to local business data. The GEO pillar argues that inconsistent descriptions fragment an entity into several weaker ones; NAP is that argument with a street address in it.
Do them together. The canonical record that fixes your directory listings is the same record that fixes your structured data, and maintaining two versions of the truth reintroduces the problem you just solved.
More in Local SEO
Google Business Profile
For a business that serves people in a place, the profile often brings in more contact than the website does. It's also the thing most likely to have been set up once and never looked at again.
SERP anatomy
Ad units, the map pack and organic results stacked on one screen, ranked by different systems on different inputs. Reading the page correctly is the whole prerequisite for working on it.
Local landing pages
A page per location works when the locations differ. Generated from a template with the city swapped, it is the doorway page pattern, which has been penalized for two decades.
Multi-location
Each office competes in its own market against its own neighbors. Run them off one brand average and you'll never see the two that are quietly failing — which are the two costing you work.