entity-schema

What this datapoint measures

Whether the brand provides machine-readable Organization or entity-level structured data declaring the brand as a coherent entity. Where schema-presence measures the breadth of structured data across page types, entity-schema measures the depth and quality of entity-level declarations specifically.

The distinction matters because Schema.org has many types, but only a subset establishes the brand itself as an entity. Organization, LocalBusiness, Person (for personal brands), and Brand are the primary entity types. A brand can have rich Article schema across content pages while having no Organization schema declaring the brand entity itself, and AI systems cannot ground brand-level claims without entity-level schema.

What high looks like

• Organization (or appropriate parent entity type) declared on the homepage and key brand pages
• Properties completed substantively: name, alternateName (for common variations), url, logo, sameAs (linking to social profiles, Wikidata, knowledge graphs), description, foundingDate, founder, address, contactPoint
• Department or sub-organization properties declared where the brand has internal structure
• Linked-data sameAs connections to authoritative external identifiers (Wikidata Q-numbers, ISNI, ORCID for personal brands, Google Knowledge Graph entries)

What low looks like

• Organization declared but with most properties empty
• Brand name and URL declared without descriptive properties
• No sameAs links connecting the brand entity to external authoritative systems
• Inconsistent entity declarations across pages (different brand names, conflicting addresses, mismatched URLs)

What at floor looks like

A brand at floor on entity-schema has no entity-level Schema.org markup at all. The brand is not declared as a coherent entity in machine-readable form. AI systems encountering the brand have no structured ground to anchor the entity to — only inferred ground from page content and external mentions.

This is among the most common deficits at AS ≈ 0. Even brands with some Article or Product schema often lack Organization schema entirely. The path off floor is to implement Organization (or the appropriate entity type) on the homepage as a priority O-5 sub-task.

What affects this datapoint

• Presence of Organization, LocalBusiness, Person, or Brand schema
• Completeness of properties within the entity declaration
• Presence and quality of sameAs links
• Consistency of entity declarations across pages
• Whether the entity declaration matches the brand’s actual structure (a multi-brand corporation should declare appropriately, not flatten to a single Organization)

OMG actions that influence this datapoint

Action	Influence
O-5 Core Structured Data Foundation	Direct, primary. Entity-level schema is a core deliverable of O-5.
G-1 External Entity Verification, Knowledge Graph & Local Authority	Substantial. G-1 work includes establishing sameAs links to external authoritative sources, which directly enriches entity-schema.
G-11 Wikipedia & Wikidata Optimization	Substantial. Wikidata presence creates a sameAs target for entity-schema, and the Wikidata work is often the moment when sameAs links are added comprehensively.

Multilingual considerations

For multilingual brands, entity-schema requires:

• Consistent canonical name across language variants (the brand’s official name; localized translations go in alternateName, not name)
• availableLanguage property declaring all languages the brand operates in
• Per-language site URLs declared with consistent entity references
• sameAs links to language-specific external entries where they exist (e.g., language-specific Wikipedia articles)

Brands operating in CJK languages should declare names in canonical script form for the primary language site, with romanizations in alternateName. A Japanese brand’s primary site declares the Japanese-script name as name; the romanized version goes in alternateName.

Common failure modes

• Organization declared on the homepage only; template pages lack any entity reference
• Multiple Organization declarations across the site that conflict (different addresses, different founding dates, different logos)
• sameAs links to outdated social profiles, deleted accounts, or wrong entities
• Organization conflated with Brand for product-only sites; Brand is sometimes more appropriate
• Entity declarations that include marketing language (taglines, value propositions) rather than factual properties
• Local business schema used for global brands or vice versa

Diagnostic interpretation

Entity-schema at floor combined with general schema-presence at low indicates a brand that has not done foundational structured-data work. O-5 is the priority action.

Entity-schema at floor combined with reasonable schema-presence indicates a brand that has done page-level structured data but never declared the brand entity itself. Specific O-5 sub-task: add Organization (or appropriate entity type) on the homepage.

Entity-schema at low but with extensive sameAs links to external authoritative sources indicates a brand that has done some G-1 work but the underlying Organization declaration is thin. The remedy is to enrich the Organization declaration with descriptive properties; the sameAs scaffolding is already in place.

Entity-schema at high but with weak knowledge-graph-depth (V3.1) indicates a brand that has declared itself well in its own structured data but has not yet built external knowledge-graph presence to corroborate the declarations. G-1 and G-11 are the next-stage actions.

---