Local Business Schema: What to Include
Choose an accurate description
Use an appropriate schema type and stable identifiers for the business and website. Check Google’s current LocalBusiness documentation for required and recommended properties relevant to the feature you want. An organisation offering remote services should not invent a public storefront address to satisfy a schema example.
- Name, website and contact information must match the real entity.
- Address and opening hours should reflect a legitimate public business operation.
- Use official profiles for sameAs links rather than unrelated directory mentions.
- Keep services and area descriptions consistent with visible information.
Validate the rendered result
Inspect the production HTML to confirm the JSON-LD exists and parses. Use the Rich Results Test for Google-supported features and review warnings in context. A syntactically valid object can still describe inaccurate facts. Check the page after deployment and after changes to business data.
Avoid unsupported ratings
Do not add invented review counts, customer scores or hidden testimonials. Follow the applicable feature policies instead of marking up every claim simply because a schema property exists. In an illustrative single-business site, one shared identity record is easier to maintain than conflicting addresses across every service page. Keep factual business information in one source and derive the markup from it.