LocalBusiness schema: mark up the place you can open the door to

Choose the most specific type that is true

A shop, a clinic, or a professional office can use a more specific type under LocalBusiness. Do not use LocalBusiness on a city page where you have no premises.

The name and address in the JSON-LD must match the visible NAP. A keyword-stuffed schema name is a policy risk and an entity mess.

One location node per branch page

If you have three branches, each page can mark up its own location. Do not emit three postal addresses on the homepage and hope a parser picks the right one.

Include the URL of that branch page, the phone, and the hours if you show them. sameAs can point at the matching Business Profile.

• Markup on the matching branch page.
• Address visible and identical.
• No fake locations to cover more districts.

Leave service-area businesses honest

If you travel to customers and have no public counter, follow the service-area pattern and say so on the page. Inventing a shop address in schema to look more local is how listings get into trouble.

Validate a branch URL after any NAP change. Stale schema is often left behind when the footer was updated and the component was not.

Should the homepage include every branch in schema?

Prefer one node per branch page. A homepage can reference the organisation without pretending all branches share one address.

Can LocalBusiness schema target several cities?

Only if those places are real locations you mark up truthfully. A list of cities is not a list of businesses.