NAP data is consistent across the site
Why it matters
NAP inconsistency — variations in your business name, address, or phone number across footer, contact page, JSON-LD schema, and config files — is one of the most heavily weighted negative factors in local search ranking algorithms. Citation aggregators and Google's local index cross-reference every mention of your NAP data; even minor format differences like Main St vs Main Street or (555) 555-1234 vs +15555551234 create conflicting signals that suppress local pack placement. This is a schema-org LocalBusiness correctness issue with direct revenue impact for any location-dependent business.
Severity rationale
Critical because NAP inconsistency directly suppresses local pack rankings by creating conflicting entity signals across the citation graph that Google uses to determine local search placement.
Remediation
Centralize all NAP data in a single source-of-truth module and import it everywhere it's rendered or serialized.
// src/lib/business-info.ts
export const BUSINESS = {
name: "Springfield Plumbing",
phone: "+15555555555",
phoneDisplay: "(555) 555-5555",
address: {
street: "123 Main Street",
city: "Springfield",
state: "OH",
zip: "45501",
country: "US",
},
} as const;
Replace every hardcoded NAP string in src/components/footer.tsx, app/contact/page.tsx, and any JSON-LD generator with imports from this file.
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Local SEO Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
External references
- schema-org · LocalBusiness — NAP fields on LocalBusiness
Taxons
History
- 2026-04-18·v1.0.0·Initial import from marketing-local-seo·automated