Topic: `schema-org`

18 entries tagged schema-org.

Rules (2)

ruleRULE: One Service schema per vertical when offerings genuinely differ. Multi-audience Service when offering is identical.
ruleRULE: Always ship schema as hygiene. Never expect it alone to move AI citations.

Reference entries (16)

referenceGoogle retired ClaimReview rich results in June 2025; schema persists for non-Google AI ingestion
referencePronto Marketing: Elementor FAQ Accordion + Element Caching breaks FAQPage JSON-LD ("Missing field text")
referenceElementor does not generate schema markup by default — Schema Pilot: "None of the layouts or widgets add structured data"
referenceAubrey Yung: "audience captures relevance; areaServed captures coverage"
referenceSchema.org canonical pattern: one Service entity with audience: { type: Audience, name: ... } + areaServed
referenceSchema.org: Service.audience accepts Audience | PeopleAudience | BusinessAudience with audienceType as free-text
referenceWebMCP + UCP: schema = nouns, WebMCP = verbs, UCP = wallet (Chrome 146 / Google I/O 2026)
referenceDigital Applied 5K-site audit (Apr 2026): only 22% of schema implementations pass Google Rich Results Test (r=+0.34 with AI citation)
referenceJSON-LD adoption: 41% of pages (Web Almanac 2024); 62M domains, +37% YoY (Schema App / W3Techs)
referenceSuganthan: schema has three lives — index-time, training-time, query-time
referenceSchanbacher (SSRN 2025): FAQPage and Product schema strongly predict ChatGPT visibility (single-domain peer-reviewed)
referenceGoogle (May 2026): "Structured data isn't required for generative AI search"
referenceWhitespark 2026: AI Search Visibility added as a formal local ranking category for the first time
referenceAhrefs (April 2026): adding schema to 1,885 pages produced no AI-citation lift; AI Overviews showed -4.6%
referencePrinceton GEO paper (Aggarwal et al., KDD '24) — the foundational generative engine optimization study
referenceResearch brief: Structured content as a competitive advantage (piece 2 of 15)