LocalBusiness schema that fights your Business Profile

LocalBusiness schema that fights your Business Profile

Reported across local audits: LocalBusiness JSON-LD whose name, address, or phone disagrees with the Google Business Profile and the visible page. Inconsistent NAP across markup, profile, and footer fragments the entity, and Google trusts the verified Business Profile over your schema — so the mismatch costs you, not it.

What it means for you: your address, telephone, and name must match the Business Profile character-for-character, and the more specific subtype (Dentist, Restaurant) beats generic LocalBusiness. openingHoursSpecification that contradicts the profile is a trust ding.

Watch this: geo coordinates copied wrong from another location are a quiet entity-poisoner — verify lat/long against the actual pin, not a geocoder guess.