NAP consistency for local SEO
NAP stands for name, address, and phone number. Those three strings are how customers and algorithms decide that two mentions refer to the same place.
Local search is, at heart, an identity problem. A map product, a directory, and your own website all need to agree that “Cedar & Pine Bistro” on Market Street is one business, not three near-matches. Inconsistent NAP data does not always cause a dramatic penalty, but it creates doubt. Doubt makes it harder to merge citations, harder to maintain a Knowledge Panel or Business Profile, and easier for a competitor or an outdated listing to steal attention.
What “consistent” actually means
Consistency is not a demand that every character be identical in every language or every legal document. It means that the public-facing name, the way the street is written, and the primary customer phone number stay stable across the surfaces that matter: your website, your schema.org markup, your Google Business Profile, and the major directories or data aggregators you can still influence.
Write the business name the way it appears on the storefront, not as a slogan. “Cedar & Pine Bistro” and “Cedar and Pine Bistro — Best Brunch in Portland!” are not the same name. The second one may be useful in a heading or an advertisement; it should not replace the official name in the footer, the contact page, or the JSON-LD name property.
Addresses should use a complete, standard form: street number and street name, city, region or state where relevant, postal code, and country. Avoid dropping the unit or floor on one site and including it on another, unless the shorter form is truly how mail is delivered. Abbreviations such as “St.” versus “Street” are usually understood, but picking one style and sticking to it reduces noise. If the business has moved, update every owned property in the same window. A website that still lists the old street, a profile that lists the new one, and schema that mixes both is a classic source of confusion.
Phone numbers should be the number a customer is meant to call. Use an international format in structured data, such as +1-503-555-0142, even if the page displays a local format. Tracking numbers can be useful in ads, but they should not silently replace the official number in your core NAP block or in schema if that would make the business look like it has several primary phones.
Where NAP should appear on your site
Give each location a clear home: a contact page, a location page, or a footer that is accurate for that host. If you have several branches, do not print one shared address in a global footer and a different address in the location schema. Each location page should state its own NAP in visible text and in its own JSON-LD graph. A store locator can link to those pages; it should not be the only place the address exists.
The same care applies to third-party listings. When you claim a directory profile, copy the canonical NAP rather than a shortened marketing version. Close or correct listings you no longer control when a platform allows it. You will not win every unclaimed citation on the internet, and you do not need to. You do need the important, current ones to agree.
How schema fits in
LocalBusiness markup is not a separate identity. It is a structured restatement of the NAP already on the page. If the visible address is “142 Market Street, Portland, OR 97201” and the JSON-LD says “142 Market St.” that is usually fine. If the JSON-LD says a different city, a suite that is not on the page, or a number that belongs to a call center in another country, you have created a conflict. Search engines are instructed to trust the page and to treat structured data that does not reflect the page as ineligible.
When something changes — a rebrand, a new number, a move — update the page first, then the schema, then the Business Profile, then the directories you own. Keep a short internal record of the canonical NAP so future contractors do not invent a fourth spelling. Then re-test the JSON-LD, because a single missed comma or stale telephone field can undo a careful update.
Use the generator to rebuild the snippet from the current canonical NAP rather than editing an old block by hand.