NAP consistency: why your business name, address and phone must match everywhere

NAP stands for name, address and phone number. NAP consistency means these details are exactly the same on your website, your Google Business Profile, directories such as Justdial and Sulekha, maps apps and social profiles. Consistent details help search engines confidently connect every mention to one real business, and stop customers calling old numbers or travelling to the wrong address.

Why does NAP consistency matter for local SEO?

Search engines build their picture of a local business from many sources. When those sources agree, it is easier to trust that the business is real and to show the right details. Google does not publish how much weight it gives to directory listings, so treat consistency as basic hygiene rather than a ranking trick. The most direct cost of inconsistency is lost customers: a wrong phone number on a popular directory means missed admission enquiries.

What counts as an inconsistency?

Any difference that could make a person or a machine wonder if it is the same business. Small formatting differences matter less than wrong or outdated information, but the safest approach is one standard version used everywhere.

Where should your NAP appear?

Your NAP should appear wherever customers and search engines look for you. Start with the sources you control, then move to the biggest directories.

• Your website: the contact page, footer and a separate page for each branch.
• Google Business Profile; see how to rank in Google Maps.
• Bing Places and Apple Business Connect.
• Indian directories that matter in your field, such as Justdial, Sulekha and IndiaMART.
• Education listings and portals relevant to your courses.
• Facebook, Instagram, LinkedIn and YouTube profiles.

How do you add NAP to your website with structured data?

Add LocalBusiness markup in JSON-LD to each branch page, using the same name, address and phone shown on the page. Google's local business structured data documentation lists the supported properties.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Sharma Classes",
  "url": "https://www.example.com/indore",
  "telephone": "+91-731-0000000",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "Shop 4, Mahatma Gandhi Road",
    "addressLocality": "Indore",
    "addressRegion": "Madhya Pradesh",
    "postalCode": "452001",
    "addressCountry": "IN"
  },
  "openingHours": "Mo-Sa 08:00-20:00"
}
</script>

You can use a more specific subtype from Schema.org if one fits. Add sameAs links to your official profiles to help connect your brand entity. If the markup reports errors, see how to fix structured data errors.

How do you fix inconsistent listings?

Agree one standard version of your details, find every listing that differs and update or remove it, starting with the sources you control.

1. Write down your standard NAP for each location in one shared document.
2. Search for your business name, old phone numbers and old addresses to find every listing.
3. Claim the listings you can, and update them to the standard version.
4. Ask directories to remove duplicates or listings for closed branches.
5. Update your website, Business Profile and social profiles first, since you control them.
6. Repeat the search every few months, and after any move or number change.

What if you move or change your number?

Update your website and Google Business Profile on the day of the change, then work through directories in order of how many customers they send you. Keep the old number forwarding for a while if you can. For a move, mark the old location as moved rather than creating a second profile.

Common mistakes

• Adding keywords or city names to the business name in some listings.
• Using a call-tracking number on some sites and the main number on others without a plan.
• Leaving listings for closed branches live.
• Showing the address only as an image, which search engines cannot read reliably.
• Putting NAP in markup that does not match the visible page.

How to check this with Spider

Spider does not audit third-party directories. Run a page audit on your contact and branch pages to check that LocalBusiness structured data is present and valid, and use a site crawl to confirm every branch page is indexable.