LEYUN · SITE SPEC & COMPONENT LIBRARY独立站技术规范手册

Writing POI Local Entity Schema: Distinguishing Storefront Entities from Product Entities

Section:GEO & AI RETRIEVAL · Reviewed:2026-11-20

Key takeawayPOI (Point of Interest) entities and product entities are semantically entirely different: the former is a place with a fixed address that can be navigated to and visited, the latter is an object that can be purchased or used. Marking a product as a POI, or a storefront as a product, pollutes the entity type.

When this applies

  • Brand sites with offline showrooms or stores that also sell products online
  • Business sites that need to appear in maps and local search
  • Sites where product catalog pages and store pages share one template
  • Sites whose structured data tests report type mismatches
POI entities versus product entities
DimensionPOI entityProduct entity
SemanticsA navigable, visitable placeAn object that can be purchased or used
Key attributesAddress, coordinates, opening hours, phoneModel, specifications, price, availability
Schema typeLocalBusiness and its specific subtypesProduct
Common misuseMarking a product page as LocalBusinessMarking a service company as Product
Applicable pagesStore pages, experience-center pagesProduct detail pages, service plan pages

Step-by-step diagnosis

  1. Inventory every page on the site and classify each as a place, an object, or an abstract service.
  2. For place-type pages, use the matching LocalBusiness subtype and complete address, coordinates, and opening hours attributes.
  3. For product detail pages, use Product schema with object attributes: model, specifications, brand, availability.
  4. For purely service-oriented pages (plans, consulting), do not apply Product; use Service or Organization instead.
  5. Validate each type with a rich results test tool, checking for missing attributes or type conflicts.
  6. Review template reuse across semantically different pages and split templates where necessary.
  7. Keep brand identifiers consistent in structured data so entities can be linked through the brand.

Common mistakes

  • Marking the whole site as LocalBusiness - non-place pages trigger type mismatches.
  • Marking consulting plan pages as Product - there is no purchasable object semantics.
  • Inserting place attributes such as opening hours into Product schema.
  • Filling fields with inaccurate information just to complete them - complete but false data is worse than gaps.
  • Reusing one schema across pages without distinguishing semantics.
  • Ignoring the Organization layer, leaving product entities unattributed to a brand.

FAQ

Can one site have both POI and Product entities?
Yes. A common brand-site combination is Organization for the company, LocalBusiness for stores, and Product for goods. The key is not to mix them.
Is LocalBusiness needed without a physical store?
Usually not. For online-only businesses, Organization plus Product is more accurate.
What happens when the schema type is chosen wrong?
Search engines may ignore the markup or weaken their understanding of the page entity, and the page loses the corresponding presentation in scenarios that need that type, such as local search or product display.
Version notes2026-11-20: first release, compiled from official Google documentation and public technical sources; updated as engine rules change. Engine behaviour details follow the latest official Google documentation.

Note: this page is a summary of publicly documented search-engine rules and is for self-check reference only. Engine behaviour is subject to the latest official Google documentation; verify against your own Search Console data.