Structured data using Schema.org’s LocalBusiness type or an appropriate subtype to describe a local business.
LocalBusiness schema is structured data using Schema.org’s LocalBusiness type or an appropriate subtype to describe a local business. It can represent details such as a name, address, telephone number and opening hours. JSON-LD is one possible way to express that data, rather than part of the type’s definition.
The markup should agree with the business information visible on the page and represent the correct location or entity. It is not independent proof that the business exists, a replacement for Business Profile verification or an automatic link between a website and a profile.
Vocabulary, validation and search eligibility are different questions. A structurally valid description may still lack properties required for a particular Google feature or fail its policies. Even eligible structured data does not guarantee a specific display or ranking improvement.
Takeaway: Use structured data to describe accurate public information, not to add unsupported claims. Choose the entity and page context before copying a generic template.
Example
A business with two customer-facing branches has separate location pages. Each page’s markup should describe the corresponding branch rather than reuse one address and set of hours everywhere. The business still needs to maintain its profiles and visible website information separately.
What to check
Validate the markup and inspect the actual values after publication. Do not invent or expose a private service-area address just to satisfy a template. Where an address or other requirement cannot appropriately be supplied, assess feature eligibility rather than fabricating data.
For more detail, see LocalBusiness structured data.