Schema.org markup: the language AI understands
Why Schema.org is the foundation of AEO
If you want AI models to understand your content and use it as a source, structured data is your most important tool. Schema.org is a shared vocabulary maintained by Google, Microsoft, Yahoo and Yandex. It provides a standardized way to describe information about your website in a format that machines can interpret.
Without Schema.org markup, AI models have to figure out for themselves what your page represents. Is it an article? A product page? A company profile? With JSON-LD markup you make this explicit, allowing AI models to process your content faster and more accurately. That is exactly what AEO aims to achieve: making your content optimally machine-readable.
JSON-LD: the preferred format
There are three ways to implement Schema.org markup: Microdata, RDFa and JSON-LD. Google recommends JSON-LD as the preferred format, and there are good reasons for this. JSON-LD is completely separate from your HTML structure, making it easier to implement and maintain. You place it in a script tag in the head or body of your page.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Kobalt Digital",
"url": "https://www.kobaltdigital.nl",
"logo": "https://www.kobaltdigital.nl/images/logo.png",
"description": "AEO and SEO consultancy specialized in AI visibility",
"foundingDate": "2020",
"address": {
"@type": "PostalAddress",
"addressLocality": "Amsterdam",
"addressCountry": "NL"
},
"sameAs": [
"https://www.linkedin.com/company/kobaltdigital",
"https://twitter.com/kobaltdigital"
]
}
</script>Dive deeper: SameAs links for digital identity | ContactPoint schema | E-E-A-T optimization
Essential schema for every website
There are several Schema.org types that every website should implement to be well discoverable by AI models. The three most important ones are Organization (or LocalBusiness), WebSite and Article.
Organization schema
The Organization schema tells AI models who you are. It contains your company name, logo, contact details and links to social profiles. This is the foundation for all other schemas on your site. Use the sameAs field to connect your digital identity with your profiles on LinkedIn, Twitter and other platforms.
WebSite schema
The WebSite schema describes your website as a whole. It contains the name, URL and an optional search function (SearchAction). This helps AI models identify your site as a coherent whole rather than a collection of loose pages.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "WebSite",
"name": "AEO Expert",
"url": "https://aeo-expert.nl",
"potentialAction": {
"@type": "SearchAction",
"target": "https://aeo-expert.nl/search?q={search_term_string}",
"query-input": "required name=search_term_string"
}
}
</script>Article schema for blog posts
For every blog post or article on your website, the Article schema is essential. It tells AI models exactly what the article contains, who wrote it and when it was published. The publication date and dateModified are particularly important for AI models that assess the freshness of sources.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Schema.org markup: the language AI understands",
"author": {
"@type": "Person",
"name": "Jan de Vries",
"url": "https://www.kobaltdigital.nl/team/jan"
},
"publisher": {
"@type": "Organization",
"name": "Kobalt Digital",
"logo": {
"@type": "ImageObject",
"url": "https://www.kobaltdigital.nl/images/logo.png"
}
},
"datePublished": "2026-04-15",
"dateModified": "2026-04-20",
"description": "Learn how Schema.org markup makes your website understandable for AI",
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://www.kobaltdigital.nl/blog/schema-org-markup"
}
}
</script>Advanced schema types for AEO
Beyond the basic schemas, there are advanced types that significantly increase your AI visibility. These are particularly valuable if your content is informational or educational in nature.
FAQPage schema
If your page contains frequently asked questions, use FAQPage schema. This helps AI models extract specific question-answer pairs, increasing the chance that your content is cited for direct questions.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is Schema.org?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Schema.org is a shared vocabulary for structured data markup."
}
}
]
}
</script>HowTo schema
For step-by-step guides, HowTo schema is ideal. It structures your instructions so that AI models can individually cite and present each step.
Common mistakes in Schema.org implementation
When implementing Schema.org markup, we regularly see the same mistakes. These errors can cause AI models to ignore or misinterpret your markup.
- Missing required fields: each schema type has fields that Google considers mandatory. Always check the documentation.
- Inconsistent data: the information in your JSON-LD must match what is visible on the page. AI models detect discrepancies.
- Outdated dates: if you do not update dateModified when you change content, AI models lose trust in the freshness.
- Too generic: use the most specific schema type available. Use Article instead of CreativeWork, and NewsArticle for news articles.
- No nesting: flat JSON-LD without nested objects misses much context that AI models need.
- Multiple separate script tags without @graph: if you have multiple schemas on a page, consider a @graph array to make the relationships explicit.
Use the Google Rich Results Test (search.google.com/test/rich-results) to validate your JSON-LD. This tool shows not only syntax errors but also missing recommended fields.
Validating and testing Schema.org
Validation is essential in Schema.org implementation. There are multiple tools you can use to check your markup.
- Google Rich Results Test: tests whether your markup qualifies for rich results and identifies errors.
- Schema.org Validator (validator.schema.org): checks whether your markup complies with the Schema.org specification.
- Google Search Console: shows which rich results are actually displayed for your pages.
- Browser DevTools: use the Elements tab to verify that your JSON-LD is correctly inserted in the page.
Schema.org and the future of AI search
The role of Schema.org is only growing as AI models become more sophisticated. Google actively uses structured data for AI Overviews, and other AI platforms are following suit. By investing in comprehensive Schema.org markup now, you build a foundation that will benefit your website for years to come in AI visibility.
Think beyond the basic schemas. Also consider FAQ, HowTo, Product and Review schemas if these are relevant to your content. The more context you give AI models, the better they can use and cite your content in their answers. Combine Schema.org with strong E-E-A-T signals and a well-maintained AEO strategy for the best results.
Key takeaways
- Schema.org is the universal language your website uses to communicate with search engines and AI models; JSON-LD is the preferred format.
- Every website needs at minimum Organization, WebSite and Article schema as a foundation for AI visibility.
- Advanced schema types like FAQPage and HowTo increase the chance that your content is specifically cited by AI.
- Always validate your markup with the Google Rich Results Test and the Schema.org Validator before publishing.
- Avoid common mistakes such as missing required fields, inconsistent data and outdated dates.
Frequently asked questions
How many Schema.org types should I implement?
Start with the three essential types: Organization, WebSite and Article. Then gradually add extra types relevant to your content, such as FAQPage, HowTo, Product or Person. There is no maximum, but ensure that each type you add actually corresponds to the content on the page.
Can Schema.org markup negatively affect my rankings?
Correctly implemented Schema.org markup never has a negative effect on your rankings. Incorrect markup (for example, schema that does not match the visible content) can lead to warnings in Google Search Console and can disable rich results. So always ensure accurate, verified markup.
Is there a difference between Schema.org for Google and for AI models?
The Schema.org specification is the same, but AI models and Google use it in different ways. Google focuses on specific types for rich results (Article, Product, FAQ). AI models use the markup more broadly to understand context. A well-implemented schema benefits from both: you get rich results in Google and better context for AI citations.
How do I implement Schema.org in WordPress?
The easiest way is through a plugin like Yoast SEO, Rank Math or Schema Pro. These plugins automatically generate JSON-LD markup for your pages. For more control, you can manually add JSON-LD through your theme's header.php or with a custom plugin. Always verify the result with the Google Rich Results Test.
Should I also add Schema.org to non-public pages?
No, Schema.org markup is only useful on publicly accessible pages that you want to be indexed. Pages behind a login, admin panels and test environments do not need Schema.org markup. Focus your efforts on the pages you want to be found by both search engines and AI models.
Schema.org is the Rosetta Stone of the modern web: it translates human content into a language that machines understand.
How does your website score on AI readiness?
Get your AEO score within 30 seconds and discover what you can improve.
