Organization and identity
Organization
The publisher or formal organization.
Corporation
A company accurately represented as a corporation.
LocalBusiness
A local business or appropriate local-business subtype.
Person
An author, staff member, founder, professional, or public profile.
Website and page
WebSite
The website as a whole.
WebPage
A general page.
AboutPage / ContactPage
Specialized pages with those visible purposes.
CollectionPage / ProfilePage
A collection or an individual profile page.
Content
Article / BlogPosting / NewsArticle / TechArticle
Editorial content; choose the most accurate subtype.
HowTo
A visible sequence that accomplishes a result; valid vocabulary does not guarantee a general search feature.
FAQPage
Visible site-authored questions and answers; current search-feature eligibility is separate from vocabulary validity.
QAPage
One question with user or community answers, not a site-authored FAQ.
Commerce and services
Product
A product or model.
Offer / AggregateOffer
A purchasable offer or summarized set of offers.
Service
A service provided by a person or organization.
OfferCatalog
An organized catalog of services or offers.
Consumer-specific review
After selecting the accurate Schema.org type, review the current documentation for the consumer you care about. Google publishes a current gallery of structured-data features and separate requirements for each supported feature.
Entity fit for Schema type selection map
Use Schema type selection map 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 Schema type selection map
- Syntax validation, type/property validation, consumer testing, and post-deployment inspection.
- Record the page template, generator, source fields, responsible owner, and release reference.
- Avoid publishing properties that are unsupported, hidden, stale, or inconsistent with visible content.
- Parse the deployed json-ld, validate the graph, compare it with visible content, and test any target consumer requirements.
- Schedule review when visible content, offers, ownership, locations, products, or consumer documentation changes.
Expand the reach of Schema type selection map
Search visibility and user value improve when schema type selection map 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 entity type and page purpose.
- Inspect required and recommended properties.
- Inspect identifier relationships across the JSON-LD graph.
- Inspect agreement between markup and visible content.
Strengthen the answer
Select the narrowest accurate entity type.
Build the topic cluster
Connect organization, website, webpage, and primary entities.
Prove the outcome
Validate syntax and eligibility after deployment.
Turn schema type selection map into an accountable record.
A maintainable structured-data graph for schema type selection map with stable identifiers and ownership.