A plain-English guide to schema markup for business owners - what it is, the most valuable types, and how structured data helps you appear in AI Overviews and rich results.
If you have ever seen a Google search result showing star ratings, a price, an FAQ drop-down, or an event time without clicking through to any website - that is schema markup in action. The website told Google exactly what that information meant, not just what it said, and Google displayed it prominently.
Schema markup is one of the most consistently underused SEO techniques, particularly by small and medium-sized businesses. It requires a small amount of technical effort upfront. But the payoff - richer search results, better click-through rates, and increasingly, visibility within AI-generated responses - makes it well worth understanding.
This guide explains schema markup in plain English, covers the most valuable types for businesses, shows you a real implementation example, and explains why it has become even more important in the age of AI search.
Schema markup is a form of structured data - code added to a webpage that tells search engines what the content means in a machine-readable format.
Without schema: a search engine reads your page and makes its best guess about what the content represents.
With schema: you explicitly declare "this is a product," "this is a review with a 4.5 star rating," "this is a FAQ," "this is an event happening on the 15th March at 7pm."
The vocabulary comes from Schema.org, a collaborative project founded by Google, Bing, Yahoo, and Yandex in 2011. It defines hundreds of content types and their properties. You pick the type that matches your content and add the corresponding code to your page.
Schema markup does not guarantee rich results in search - Google decides whether to show them. But implementing schema correctly makes your pages eligible for them, which they are not without it.
There are three ways to add schema markup to a page: JSON-LD, Microdata, and RDFa. For the vast majority of businesses, JSON-LD is the right choice. Here is why.
JSON-LD (JavaScript Object Notation for Linked Data) is added as a separate <script> block in your page's HTML, usually in the <head> or at the end of the <body>. It does not touch or depend on the existing HTML structure of your page. You can add, edit, or remove it without changing how the page looks or works.
Microdata embeds schema attributes directly into your HTML elements. It is messier to manage, harder to maintain, and requires you to restructure your HTML around it.
RDFa is similar to Microdata in approach. It was more common in older implementations.
Google explicitly recommends JSON-LD. It is cleaner, easier to audit, simpler to update, and less likely to break if your template changes. Unless you are working with a platform that only supports Microdata (some older CMS systems), use JSON-LD.
Not all schema types are equal. Some unlock rich results that directly increase click-through rates. Others are primarily useful for helping AI systems understand your content. Here are the most important ones.
| Schema Type | What It Enables | Best For |
|---|---|---|
| Organisation | Knowledge panel, brand info, logo | All businesses - should be on every site |
| Article / BlogPosting | Article rich results, AI citation eligibility | Blogs, news, content sites |
| FAQ | FAQ drop-downs in search results, AI Overview inclusion | Pages with Q&A sections |
| Product | Price, availability, star ratings in results | E-commerce, product pages |
| Review / AggregateRating | Star ratings in search results | Product, service, or local business pages |
| HowTo | Step-by-step rich results | Tutorial or guide content |
| Event | Event details in search and Google Events | Venues, event organisers, ticketing |
| LocalBusiness | Local pack, map integration, business hours | Any business serving a local area |
| BreadcrumbList | Breadcrumb trail shown in search results | All sites with hierarchical navigation |
| VideoObject | Video thumbnails in search results | Pages featuring video content |
| Person | Author information, knowledge panels | Thought leaders, professionals, writers |
For most businesses, the priority order is: Organisation (always), BreadcrumbList (if you have navigation hierarchy), FAQ (on any page with questions), Article/BlogPosting (on all blog content), and then Product or LocalBusiness depending on your business type.
Let's make this concrete. Here is what FAQ schema looks like in practice. This would go into a <script> tag on a page that includes a FAQ section.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is schema markup?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Schema markup is code added to a webpage that tells search engines what the content means - not just what it says. It uses the vocabulary from Schema.org and is typically added in JSON-LD format."
}
},
{
"@type": "Question",
"name": "Does schema markup improve search rankings?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Schema markup does not directly improve rankings, but it can increase click-through rates by enabling rich results such as FAQ drop-downs, star ratings, and event details - which can indirectly support ranking performance."
}
}
]
}
</script>
That code tells Google: this page contains two frequently asked questions, here are the exact questions and answers. Google may then display them as expandable entries beneath the main search result, increasing the amount of space your result occupies on the page and giving users a reason to click.
This is where schema markup has become significantly more important in 2026.
Google's AI Overviews, Perplexity, and other AI search systems do not just crawl text. They parse structured data to understand relationships between pieces of information. A page with clean FAQ schema is far easier for an AI system to extract and cite than a page where the same questions and answers are buried in paragraphs.
Research from BrightEdge published in late 2025 found that pages with structured data were 2.7 times more likely to be cited within AI Overviews than equivalent pages without it. That is a substantial advantage, and the gap is expected to widen as AI search matures.
"Structured data is becoming the lingua franca between websites and AI systems. The businesses that implement it properly now are building a durable advantage as AI search continues to grow." - Aleyda Solis, International SEO Consultant
The logic is intuitive. AI systems need to extract meaning at scale, very quickly, across millions of pages. Schema markup makes your content machine-readable in a standardised format. It reduces ambiguity. For AI systems that need to decide "is this page a credible source on X topic?", well-implemented structured data is a meaningful signal.
You do not necessarily need to touch code to add schema markup. Several routes exist depending on your setup.
For WordPress sites: Plugins like Rank Math and Yoast SEO include schema generation for articles, products, and local businesses. You configure the schema through the plugin interface and it handles the code output.
For Shopify stores: Shopify automatically generates Product schema on product pages. You may still need to add FAQ, Organisation, or BreadcrumbList schema manually, which can be done through the theme's <head> section or via a plugin.
For custom or other CMS platforms: Use Google's Structured Data Markup Helper to generate the JSON-LD code for your specific content, then paste it into your page template.
After implementation: Validate your schema using Google's Rich Results Test (search.google.com/test/rich-results). It tells you whether your schema is valid, which rich result types you are eligible for, and any errors that need fixing. Also check Google Search Console's Enhancements reports - these show how Google has processed your structured data at scale across your entire site.
Marking up content that is not visible on the page. Google requires that schema markup describes content actually present and visible to users. If your FAQ schema lists questions that do not appear on the page, Google may penalise you for misleading structured data.
Using the wrong schema type. Adding Article schema to a product page, or Product schema to a blog post, confuses search engines. Use the type that most accurately represents your actual content.
Not validating before publishing. Schema errors are invisible to users but damaging to eligibility for rich results. Always run the Rich Results Test before a page goes live.
Forgetting to update schema when content changes. If you update your FAQ section but not the FAQ schema, the markup becomes inaccurate. Treat schema as part of the page, not an add-on you install once.
Adding schema only to the homepage. Schema should be applied at the right content type across the relevant pages of your site - product pages, blog posts, location pages, event pages. A schema implementation that only touches the homepage captures a fraction of the potential value.
If you are starting from scratch, here is a practical implementation order:
For businesses managing SEO at scale, Athenic's AI SEO Engine can generate and maintain schema markup automatically across new and existing content - ensuring every published page has appropriate structured data without requiring manual implementation for each one.
Schema markup is one part of a broader on-page SEO strategy. On its own, it does not overcome thin content, poor keyword targeting, or weak backlink profiles. But combined with strong fundamentals, it gives you an edge that most competitors are not exploiting.
If you have done the basics and want to understand what else you should be working on, our on-page SEO checklist covers the full picture. If you are thinking about how AI-generated search is changing which content gets visibility, our GEO and generative engine optimisation guide is worth reading alongside this one.
Does schema markup directly improve my search rankings?
Not directly. Schema markup does not cause Google to rank a page higher in the traditional sense. It makes pages eligible for rich results (star ratings, FAQ drop-downs, event details, etc.) and increases the likelihood of appearing in AI Overviews. Both of these can improve click-through rates - and sustained improvements in CTR can have an indirect positive effect on rankings over time. Think of it as a visibility enhancer rather than a ranking booster.
How do I know if my schema markup is working?
Two places to check. First, Google's Rich Results Test - paste in your URL or code and it tells you whether your schema is valid and which rich results you are eligible for. Second, Google Search Console's "Enhancements" section shows you how many of your pages have been processed with each schema type, and flags any errors or warnings at scale.
What happens if I implement schema markup incorrectly?
Minor errors typically mean your page is ineligible for rich results, but does not get penalised. More significant violations - such as marking up content that is not visible on the page, or using schema to display misleading information - can lead to manual actions from Google. The Rich Results Test catches most errors before they become a problem.
Do all pages on my site need schema markup?
Not all schema types apply everywhere. The Organisation and BreadcrumbList schema are broadly applicable. Article/BlogPosting schema belongs on all blog content. Product schema belongs on product pages. FAQ schema belongs where you have FAQ content. Privacy policy, thank-you, or utility pages typically do not need schema. Prioritise the pages that drive the most traffic or have the clearest content type.
Is schema markup affected by my CMS or platform?
Yes, in the sense that how you implement it depends on your platform. WordPress with a good SEO plugin, Shopify, and most modern CMS systems either auto-generate basic schema or make it easy to add. Highly customised or legacy platforms may require a developer to add JSON-LD to page templates. In all cases, the underlying JSON-LD code is the same - only the delivery mechanism differs.
Schema markup is one of those SEO techniques that feels technical but is actually accessible once you understand what it does. You are not reinventing your site - you are adding a layer of meaning that makes your existing content more legible to search engines and AI systems. That is a compounding advantage worth building now, before your competitors do.