JSON-LD Structured Data
Concept Definition
Definition
JSON-LD (JavaScript Object Notation for Linked Data) is the recommended format for adding structured data to web pages. It uses Schema.org vocabulary to provide explicit, machine-readable context about your content that LLMs can parse and understand.
Importance
JSON-LD bridges the gap between human-readable content and machine understanding. It provides explicit metadata about entities, relationships, and facts on your page, allowing LLMs to confidently extract and cite information without ambiguity.
Why It Matters
Large language models need structured context to understand what information is authoritative and how it relates to other entities. JSON-LD provides this context in a standardized format that all major AI systems can parse, increasing the likelihood your content will be cited in AI-generated answers.
Common Schema Types
- Article — Blog posts, articles, and written content
- FAQPage — Pages with question-and-answer pairs
- HowTo — Step-by-step instructions and tutorials
- Product — Products and services
- Organization — Company and brand information
- Person — Individual people and authors
- WebSite — Overall website information
- DefinedTerm — Glossary entries and definitions
Example: Article Schema
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Model Context Marketing Guide",
"description": "Complete guide to optimizing content for LLMs",
"author": {
"@type": "Person",
"name": "Stephen Newman"
},
"datePublished": "2025-11-04",
"dateModified": "2025-11-04"
}
</script>Example: FAQ Schema
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [{
"@type": "Question",
"name": "What is Model Context Marketing?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Model Context Marketing is the practice of
creating structured, factual content that LLMs
can understand and cite."
}
}]
}
</script>Implementation
Add JSON-LD scripts to the <head> or top of the <body> of your pages. Use multiple schemas when appropriate—a page can have both Article and FAQPage schemas if it contains both article content and Q&A sections.