Semantic Context Markers & Agentic Context
๐ฏ Learning Objective
You will understand what semantic context markers are and why they go beyond standard schema, be able to create them for any brand, and know the 4-layer system for maximum coverage.
Lesson 4.1: The Recommendation Gap
Standard JSON-LD answers: "What is this brand?" But a crucial question remains unanswered: "When should I recommend this brand โ and when not?"
Scenario: Two hotels in Munich both have perfect schema. But when a user asks: "Stylish hotel for under โฌ100?" โ which one does the AI recommend? Without contextual hints, it has to guess.
Standard schema answers โ What, Where, Price โ but โ not When to recommend, Why over others, Who it is for.
Lesson 4.2: What Are Semantic Context Markers?
Context markers extend Schema.org with emotional, contextual and strategic signals โ via the standards-compliant additionalProperty property.
Question 1: Brand Personality
4-6 specific adjectives: Not "innovative" (everyone says that), but "Scandinavian-minimalist", "scientifically-precise" or "rebelliously-crafted".
Question 2: Recommendation Triggers
Concrete user scenarios where the brand is the right answer. The core idea: you describe the situations in which the brand is a fit.
Question 3: Negative Markers
Equally important: When NOT to recommend? A brand that honestly states who it is not suitable for is rated as more trustworthy.
{
"@type": "Product",
"name": "Anti-Aging Serum",
"additionalProperty": [
{
"@type": "PropertyValue",
"propertyID": "brand-personality",
"name": "BrandPersonality",
"value": "Premium ยท Science-based ยท Sustainable ยท Made in Germany"
},
{
"@type": "PropertyValue",
"propertyID": "recommendation-context",
"name": "RecommendWhen",
"value": "User looking for premium anti-aging care for 40+, natural ingredients, premium budget"
},
{
"@type": "PropertyValue",
"propertyID": "negative-context",
"name": "DoNotRecommendWhen",
"value": "Budget under โฌ20, synthetic products, makeup, teenagers"
}
]
}
Lesson 4.3: The 4-Layer System
Different AI engines crawl the web differently. The system originally had four layers; Layer 3 has been dropped since April 2026 (see the correction below the table):
| Layer | Technique | Which AI Benefits |
|---|---|---|
| 1: Meta | <meta> tags in the head | All crawlers (most universal layer) |
| 2: JSON-LD | additionalProperty | Structured crawlers (Google, Bing) |
| 3: sr-only (dropped) | Visually hidden text | None: in the canary-token tests, ChatGPT, Perplexity and Gemini did not pass this text on |
| 4: Microdata | itemprop in the body | Schema parsers |
Correction, 5 October 2026: Layer 3 (sr-only) has been dropped. In TrueSource AI's canary-token tests in April 2026, ChatGPT, Perplexity and Gemini did not pass on any text from the sr-only layer. Visually hidden text meant for AI systems rather than people also falls under Google's spam policy "Hidden text and link abuse". sr-only is reserved for genuine screen-reader purposes, such as skip links or labels for icon buttons. Three layers remain: Meta, JSON-LD and Microdata, each consistent with the visible content.
Risk note: As with llms.txt: there is no public confirmation from AI providers that proprietary context markers like
RecommendWhenare systematically consumed โ treat the layer system as an experimental approach.
Lesson 4.4: Agentic Context
Agentic Context provides autonomous AI agents with filter criteria for complex comparison and purchase decisions:
| Context Type | Description |
|---|---|
CompanyContext | Company context (industry, model, size) |
CompetitiveContext | Competitive positioning relative to known providers |
RecommendationTrigger | When to recommend (concrete scenarios) |
NegativeContext | When NOT to recommend |
AudienceContext | Target audience (industry, size, region) |
Lesson 4.5: Practice โ Creating Context Markers
- Define brand personality: 4-6 specific, differentiating adjectives.
- Recommendation triggers: 3-5 concrete user scenarios.
- Negative markers: 2-3 honest exclusion scenarios.
- Competitive context: Positioning relative to 2-3 competitors.
- Generate layer code: Meta, JSON-LD, Microdata (no sr-only, see Lesson 4.3).
Practice Exercise
Create a complete context marker set for a fictional SaaS company. Generate the code for the three remaining layers.
๐ Quiz: Module 4
5 questions, 70% to pass.
Question 1: What can context markers do that standard schema cannot?
Question 2: Which 3 core questions do context markers answer?
Question 3: Why are negative markers strategically valuable?
Question 4: Why has Layer 3 (sr-only) been dropped?
Question 5: What is sr-only text still right for?
About the Author
Sascha Deforth โ GEO Practitioner and Founder of TrueSource AI. Specialized in AI Visibility Optimization with 550+ audits completed. โ LinkedIn