What the type represents
A retail store with a physical or local-business identity.
Use it when
- The page represents an actual store
- Store details are visible and current
Properties to evaluate
- @id
- name
- url
- image
- telephone
- address
- openingHoursSpecification
- paymentAccepted
JSON-LD example
{
"@context": "https://schema.org",
"@type": "Store",
"@id": "https://example.com/#store",
"name": "Example Store",
"url": "https://example.com/"
}Common mistakes
- Selecting the type only because a search feature is desired.
- Publishing facts that are not visible or supported by the site.
- Creating conflicting copies of the same entity instead of using a stable @id.
- Failing to update markup when the visible page or source data changes.
Official references
Schema.org defines the vocabulary. Search platforms publish separate documentation for the structured-data features they currently support.
Entity fit for Store
Use Store only when the page visibly represents the corresponding entity or relationship. Begin with the page purpose and the entity graph, then select the most specific supported type. Do not let the available vocabulary dictate claims the page does not make.
Visible support
Every material property should be supported by visible, current, and accurate page content.
Stable identity
Use consistent identifiers when the same organization, person, place, product, service, or webpage appears across the graph.
Consumer requirements
Treat Schema.org validity and search-consumer eligibility as related but separate checks.
Deployment record for Store
- Local visibility and conversion evidence separated by location and service intent.
- Record the page template, generator, source fields, responsible owner, and release reference.
- Avoid publishing inconsistent business information across the website and external profiles.
- Inspect the live page, business profile, structured data, citations, and location-specific conversion tracking.
- Schedule review when visible content, offers, ownership, locations, products, or consumer documentation changes.
Expand the reach of Store
Search visibility and user value improve when store answers the real questions people bring to the page. For business owners, marketers, seo practitioners, and developers, that means covering the decision context, observable signals, implementation boundaries, and proof that the result works in production—not repeating a keyword or publishing a longer version of the same incomplete explanation.
Use the page as part of a connected topic cluster. Link the broad concept to focused implementation guides, definitions, checklists, examples, and the Asuruas workflow that can identify affected URLs. The goal is to help a reader move from discovery to a confident next action while giving search systems clear entities, relationships, and page purpose.
- Inspect business identity and location consistency.
- Inspect service-area and location-page usefulness.
- Inspect local entity markup and citations.
- Inspect reviews, contact paths, and conversion clarity.
Strengthen the answer
Create useful location context instead of doorway pages.
Build the topic cluster
Connect services, locations, and proof.
Prove the outcome
Measure qualified local actions rather than rankings alone.
Turn store into an accountable record.
A justified type-selection decision for Store with visible-content support and validation evidence.