NAP Consistency
The state in which a brand's Name, Address, and Phone number are identical across all platforms — a foundational signal for entity confirmation by search engines and LLMs
What is NAP Consistency?
NAP Consistency refers to keeping a brand's Name, Address, and Phone number identical across every platform where the brand is listed — its own website, Wikidata, Wikipedia, LinkedIn, Google Business Profile, press coverage, and any other directory.
The term originated in local SEO, where address and phone consistency across map listings was critical for location-based search ranking. In the LLM era, the concept has expanded to apply to entity confirmation across AI knowledge graphs.
Why does it matter for AI visibility?
LLMs and Knowledge Graphs cross-validate data from multiple sources to confirm entity identity. When the same brand name is spelled differently across sources — "RanketAI Inc." on one site, "Ranket AI" on another, "랭킷AI" in a press article — the model cannot confidently merge them into one entity. The result is fragmented entity authority and inconsistent AI answer behavior.
Even a minor variation — a comma, a legal suffix ("Inc." vs. "LLC"), or a different capitalization — can cause two listings to be treated as separate entities.
What counts as a NAP field in the LLM context?
Beyond the original three, effective entity consistency also covers:
| Field | Example |
|---|---|
| Brand name | RanketAI (not "Ranket AI" or "ranketAI") |
| Founder name | Jeongmin Lee (consistent across all sources) |
| Founding date | 2024 (same year on all platforms) |
| Official URL | https://www.ranketai.com (with www, no trailing slash variation) |
| Social handles | @ranket_ai on all platforms |
How to audit NAP consistency
- Search your brand name on Google — check Knowledge Panel, press mentions, and directory listings for spelling variations
- Compare LinkedIn, Crunchbase, GitHub, and App Store profiles side by side
- Check Wikidata properties against your official site
- If the Google Knowledge Graph Search API returns a conflicting entity description, the inconsistency is severe enough to require immediate correction