structured-content-signals

What this datapoint measures

Presence of machine-readable schema types specifically consumed by AI systems for content grounding — Article, FAQ, HowTo, QAPage, BreadcrumbList, Speakable, and similar content-type schemas that AI systems use to extract citable content units.

This datapoint differs from schema-presence in focus: schema-presence measures all Schema.org markup across all page types; structured-content-signals measures the subset of schemas that specifically aid AI systems in identifying citable content. A brand with extensive Product schema but no Article or FAQ schema scores well on schema-presence but poorly on structured-content-signals.

What high looks like

• Article schema on editorial content with author, datePublished, dateModified, headline, articleBody properties
• FAQPage schema on question-and-answer content with substantive question and acceptedAnswer properties
• HowTo schema on instructional content with step properties
• BreadcrumbList schema providing structural context for every page
• Speakable schema (where appropriate) marking specific content sections for voice/audio AI consumption
• Article and FAQ schemas implemented across the site, not just on flagship content

What low looks like

• Article schema on some content but with sparse properties (no author, no dateModified, abbreviated articleBody)
• FAQ-style content without FAQPage schema markup
• BreadcrumbList missing or inconsistent
• Articles flagged as such but actually being product or category pages

What at floor looks like

A brand at floor on structured-content-signals has no content-type schemas at all, or has only Product schema and similar commerce-focused types. AI systems encountering the brand’s content cannot identify what type of content they are reading — every page presents as undifferentiated text.

This is common at AS ≈ 0. Many brands implement Organization and Product schemas (because the implementation paths are well-known) but never add Article or FAQPage schemas because their CMS doesn’t generate them by default. The remedy is engineering work as part of O-5: add schema generation to the templates for editorial content, FAQ pages, and instructional content.

What affects this datapoint

• Presence of Article schema on editorial content
• Presence of FAQPage schema on question-and-answer content
• Presence of HowTo schema on instructional content
• Property completeness within each content schema
• BreadcrumbList implementation site-wide
• Speakable markup where applicable

OMG actions that influence this datapoint

Action	Influence
O-5 Core Structured Data Foundation	Direct, primary. Content schemas are a core deliverable of O-5 alongside entity schemas.
M-3 Dedicated FAQ & Knowledge Hubs	Substantial. M-3 work includes FAQPage schema as part of building structured FAQ destinations.
M-2 Answer-First Content Architecture	Indirect. M-2 work often surfaces structured Q-and-A patterns that enable FAQPage schema implementation.

Multilingual considerations

Content schemas are largely language-neutral in their markup — Article and FAQPage work the same way across languages. Specific considerations:

• inLanguage should be declared on each content schema to specify the content’s language
• headline and other text properties should match the page’s actual content language
• For Japanese, Korean, and Chinese content, ensure that no text-truncation rules in CMS-generated schema cut multibyte characters incorrectly (a common bug)
• Author names in non-Latin scripts should be preserved in canonical script form, with romanizations as alternateName where needed

Common failure modes

• Article schema generated automatically by CMS with articleBody containing the entire HTML of the page (including navigation, footer, sidebar) rather than just the article content
• FAQPage schema applied to category pages or blog index pages rather than to actual Q-and-A content
• HowTo schema applied to non-instructional content (regular articles, product descriptions)
• Article datePublished and dateModified showing the same date for content that has actually been updated multiple times
• BreadcrumbList implemented as visual breadcrumbs without the corresponding schema markup

Diagnostic interpretation

Structured-content-signals at floor with entity-schema also low indicates broad O-5 work needed. The brand has not done content-type structured-data work.

Structured-content-signals at floor with entity-schema high indicates a brand that has declared itself but not its content. Specific O-5 sub-task: add Article schema to editorial content templates and FAQPage to FAQ content.

Structured-content-signals high but content-depth (V2.1) low indicates a brand that has done structured-data work on shallow content. The schema is correct but the content underlying it is thin. The remedy is M-pillar work to deepen the underlying content; structural-content-signals will retain its high score as the content improves.

---