Key takeaways
- Google says to define each real local business location as a LocalBusiness type, using the most specific truthful subtype.
- A market page is not a location entity merely because the company can sell services there.
- Structured data must match visible page content and must not invent addresses, hours, ratings, departments, or reviews.
- A remote or service-area organization can use accurate Organization and Service information without fabricating a storefront.
01
Markup describes the operation; it does not upgrade it
LocalBusiness structured data is useful when a page describes a real business location: its address, hours, phone, department, and other factual details. It is not a regional targeting switch. Adding a city and postal address to JSON-LD while the visible page says “we serve clients remotely” creates a contradiction rather than a local signal.
If the company has no customer-facing location in a market, say so through the service model. Use Organization markup for the business identity and Service markup where it accurately describes an offer. Keep the regional page focused on availability and delivery.
02
Match every property to something a person can verify
Use the most specific subtype that truthfully fits the location. Provide the same name, address, phone, URL, hours, and images a visitor sees. If a property is operationally unstable or unsupported, leave it out until the source of truth exists.
- Do not add an aggregateRating unless the markup and review use comply with the relevant guidelines.
- Do not mark a coworking mailbox as a branch when it is not staffed and customer-facing.
- Do not clone the organization’s founding date, employees, or awards into invented location entities.
- Do not place one local entity on every regional page when only one real location exists.
03
Model real relationships instead of multiplying entities
A genuine multi-location business can give each location a stable identifier and connect it to the parent organization. Each location page should carry the details and customer actions for that branch. A remote service network can connect regional pages to the organization and relevant services without declaring a physical branch.
The smaller graph is often the better graph. Search engines can only use properties they understand and trust; customers must live with every property you publish. More types and fields do not compensate for weak identity data.
04
Validate syntax, then audit reality
Run the relevant schema validator and inspect the rendered HTML, but do not stop at a green tool. Call the number, check the map pin, confirm the hours, compare the name with signage, and verify the destination page. Search features remain at Google’s discretion even when markup is technically valid.
Assign an owner for location facts and remove stale markup when a branch closes or the operating model changes. Structured data is a maintained factual interface, not a one-time SEO decoration.
Primary sources and further reading
Use the source material to validate details against your own context and current platform configuration.
- Google Search Central: LocalBusiness structured data
- Google Search Central: Structured data introduction and guidelines
- Google Business Profile: Guidelines for representing your business
- Schema.org: LocalBusiness
This field note follows the XenGrowth editorial policy: primary sources where available, visible limitations, material review dates, and no invented first-hand experience.
Stay with the problem
