Guide

NAP Consistency Guide

NAP consistency is often reduced to name, address, and phone across citations. In practice, modern local consistency also includes domain, service emphasis, map linkage, and entity alignment across owned assets.

Key takeaways

Phone mismatches weaken trust and attribution.
The GBP website link should point to the canonical domain.
The site should visibly connect back to the map profile.
Service emphasis on the profile and site should reinforce the same commercial story.

Phone and domain are the first consistency checks

If the website header, schema, footer, and GBP use different numbers, the business sends mixed trust signals. The same applies when the profile points to a different site version or old domain.

Choose one live business domain and one main number, then normalize all owned assets around them.

Map integration matters

The website should not feel disconnected from the profile. A visible maps link, contact-page map reference, and hasMap schema field all strengthen the relationship between the two assets.

Users also benefit because they can jump from the site to the map profile without friction.

Consistency is also about offer alignment

If the website pushes one service and the GBP focuses on another, Google gets mixed intent signals.

The strongest local setups keep categories, services, page titles, review prompts, and trust content aligned to the same priority offers.