Schema markup is one of the few things you can add to a page that directly tells search engines what your content means. Not what it says. What it is.
A recipe page without schema is just text. With the right markup, Google knows the ingredients, cook time, calorie count, and ratings. That distinction matters more now than ever, because AI search engines rely on the same structured understanding when choosing which sources to cite.
This guide covers what schema markup is, which types actually move the needle, how to implement it correctly, and why structured data is becoming a critical signal for AI visibility.
What is schema markup?
Schema markup is code you add to your pages that labels your content in a way machines can read. It uses a shared vocabulary maintained by Schema.org, which currently defines 823 types and 1,529 properties covering everything from recipes to medical conditions to software applications.
When you add schema markup, you’re creating a structured description of your page content. A product page might declare its name, price, availability, review ratings, and shipping details. An article page might specify its author, publication date, and publisher. An organization page might include its legal name, address, social profiles, and logo.
Search engines read this structured description alongside the visible content on your page. When both align, they can present your content in richer, more useful ways in search results.
How schema markup works in Google Search
Google uses structured data to understand page content and to “gather information about the web and the world in general, such as information about the people, books, or companies that are included in the markup,” according to Google’s developer documentation.
That second part is the one most guides skip. Schema doesn’t just trigger rich results for individual pages. It feeds Google’s Knowledge Graph, the structured database that powers knowledge panels, entity cards, and the contextual understanding behind AI Overviews.
When you mark up your organization with its legal name, founding date, address, and social profiles, you’re not just decorating a page. You’re telling Google “this entity exists, here are its verified attributes.” That information gets cross-referenced with other sources and, if consistent, strengthens your brand’s presence as a recognized entity.
The rich results payoff
The immediate benefit of schema is rich results: enhanced search listings that show ratings, prices, images, FAQs, and other details directly in the search results page.
The performance data backs this up. According to Google’s developer documentation, Rotten Tomatoes added structured data to 100,000 unique pages and measured a 25% higher click-through rate for pages with structured data compared to pages without. The Food Network converted 80% of their pages to enable search features and saw a 35% increase in visits. Nestlé measured that pages showing as rich results have an 82% higher click-through rate than non-rich result pages.
These aren’t edge cases. They’re what happens when search engines can confidently present your content in a format that answers questions before the click.
The three schema formats
Google supports three formats for structured data markup:
- JSON-LD (recommended). A JavaScript block you place in your page’s
<head>section. It’s separate from your HTML, which makes it easier to add, maintain, and debug. Google explicitly recommends JSON-LD. - Microdata. HTML attributes woven into your existing page markup. Harder to maintain because the structured data is tangled with your presentation code.
- RDFa. Similar to Microdata but uses different attribute names. Less common in practice.
Use JSON-LD unless you have a specific reason not to. It keeps your structured data cleanly separated from your page content, and it’s what most CMS plugins and schema generators produce.
Here’s what a basic Organization schema looks like in JSON-LD:
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Your Brand",
"url": "https://yourbrand.com",
"logo": "https://yourbrand.com/logo.svg",
"description": "What your company does.",
"foundingDate": "2020",
"address": {
"@type": "PostalAddress",
"addressCountry": "AU"
},
"sameAs": [
"https://linkedin.com/company/your-brand",
"https://x.com/yourbrand"
]
}That block goes in a <script type="application/ld+json"> tag. The page loads normally for users while search engines read the structured layer underneath.
Schema types that matter for SEO
Schema.org defines hundreds of types. Most don’t trigger anything in search results. Here are the ones that directly impact visibility, organized by what they do for you.
Organization
Establishes your brand as a recognized entity. Properties include your legal name, logo, address, contact information, social profiles, and company identifiers. This information can appear in knowledge panels and other visual elements in search results.
Organization schema is foundational. It connects your brand to Google’s Knowledge Graph, which AI engines query when answering questions about companies and products. If you only implement one schema type, start here.
Product
Tells Google about individual products including price, availability, review ratings, shipping information, and more. Product structured data can trigger product snippets, popular products carousels, shopping knowledge panels, and annotations in Google Images.
Google distinguishes between two uses: product snippets for pages where people can’t purchase directly (editorial reviews, comparison pages) and merchant listings for pages where customers can buy from you. Merchant listings support additional properties like apparel sizing, shipping details, and return policies.
Article
Marks up news, blog, and sports articles. Can trigger rich result features including the article title and larger-than-thumbnail images. Article schema helps Google understand your content’s publication date, author, and publisher, all signals that feed recency and authority assessments.
FAQ
Identifies a page that contains questions and answers about a specific topic. FAQ schema can display expandable Q&A directly in search results, giving you significantly more real estate on the results page.
LocalBusiness
Critical for any business with a physical location. Displays business details in Google’s knowledge panel including open hours, ratings, directions, and actions to book appointments or order items. For local SEO, this is non-negotiable.
Review and AggregateRating
Shows star ratings and review counts directly in search results. Can apply to products, recipes, movies, local businesses, and software apps. Review snippets are among the most visually impactful rich results because they immediately signal quality and social proof.
Breadcrumb
Replaces the raw URL in search results with a readable navigation trail showing the page’s position in your site hierarchy. Small change, big usability improvement. Breadcrumb schema helps both users and search engines understand your site structure.
Schema markup and AI search
This is where schema goes beyond rich snippets.
AI search engines like ChatGPT, Perplexity, and Google AI Overviews don’t just return links. They retrieve sources, synthesize information across those sources, and generate answers with citations. To do this well, they need to understand what your content is, not just what it says.
Schema markup provides that understanding. When your page declares itself as a Product with a specific price, availability status, and aggregate rating, an AI engine can extract those facts directly rather than inferring them from paragraph text. When your page identifies its author, publication date, and publisher organization, an AI engine can assess its recency and authority.
Google’s developer documentation states that structured data should match the visible text on the page, and lists structured data as part of its SEO best practices for AI features. This makes sense: structured data that accurately reflects page content gives AI engines a verified, machine-readable layer to work with.
How schema feeds the Knowledge Graph
Google’s Knowledge Graph is a structured database of entities (people, companies, products, places) and the relationships between them. When you ask Google AI Overviews about a company, the response draws heavily from this database.
Schema markup is one of the primary ways entities get into the Knowledge Graph. Your Organization schema declares your brand’s attributes. Your Product schema declares what you sell. Your Person schema (for author pages) establishes who writes your content. When this data is consistent across your site and matches third-party sources, Google can confidently include your entity in the Knowledge Graph.
That matters for AI citations because AI ranking factors include entity recognition. AI engines build internal representations of brands and associate them with topics. Strong entity signals, reinforced by schema markup, increase the chance your brand gets cited when someone asks about your space.
Schema as a structured data layer for LLMs
Beyond Google, structured data helps any system that crawls your pages. An LLM reading your site encounters two layers: the visible text content and the structured data markup. The structured layer provides unambiguous facts. There’s no need to parse “Starting at $49/month” from a pricing paragraph when the Product schema declares "price": "49.00" and "priceCurrency": "AUD".
This works alongside other machine-readable signals like llms.txt, which gives AI models a curated overview of your site. Schema handles the page-level detail. llms.txt handles the site-level map. Together, they make your content as accessible as possible to AI systems.
Implementation best practices
Start with the basics
Don’t try to implement every schema type at once. Start with Organization schema on your homepage, then add Article schema to your blog posts and Product schema to your product pages. Build from there based on what content types you publish.
Use Google’s recommended properties
Each schema type has required and recommended properties. Meeting the minimum requirements makes you eligible for rich results, but adding recommended properties gives Google more to work with. For Product schema, that means going beyond name and price to include images, reviews, availability, brand, and SKU.
Validate before deploying
Google provides the Rich Results Test for checking whether your structured data is eligible for rich results and previewing how it will appear. Use it every time you add or change schema markup. Syntactically correct JSON-LD that violates Google’s quality guidelines won’t trigger rich results.
Keep structured data aligned with visible content
Google’s structured data guidelines are explicit: “Don’t mark up content that is not visible to readers of the page.” If your JSON-LD describes a performer, the HTML body must describe that same performer. If your Product schema shows a price of $49, the page must show that same price. Mismatches can result in a manual action that strips your rich result eligibility.
Place JSON-LD in the head
While JSON-LD technically works anywhere in the HTML document, placing it in the <head> ensures search engine crawlers find it immediately. This is especially important for JavaScript-heavy sites where body content may load asynchronously.
Nest related schemas
Rather than creating separate JSON-LD blocks for every entity on a page, nest related schemas. A Product schema can include an Organization as the brand, AggregateRating for reviews, and Offer for pricing. This creates clearer relationships between entities and reduces redundancy.
Common mistakes
Marking up invisible content. Adding schema for products, reviews, or events that don’t appear on the page. Google’s guidelines prohibit this, and violations can trigger manual actions.
Forgetting to update schema when content changes. Your Product schema says $49/month but the page now says $59/month. This mismatch undermines trust, both with Google and with AI engines that cross-reference structured data against visible content.
Using the wrong schema type. A blog post marked up as a NewsArticle when it’s not from a news organization. A service page marked up as a Product when no purchase is possible. Choose the type that accurately represents your content.
Over-marking. Adding schema to every page regardless of whether it makes sense. A contact page doesn’t need Article schema. A 404 page doesn’t need anything. Schema should describe genuine, substantive content.
Ignoring nested entities. Declaring a Product without connecting it to an Organization (brand), without including Offers (pricing), or without linking to Reviews. Flat, disconnected schemas provide less value than properly nested ones.
How to audit your existing schema
Before adding new markup, check what you already have. Most CMS platforms and themes add some schema automatically, sometimes incorrectly.
- Run your pages through Google’s Rich Results Test to see what structured data Google detects and whether it’s valid.
- Check the Enhancements reports in Google Search Console for structured data errors and warnings across your site.
- Look for duplicate or conflicting schemas. Some themes add Organization schema that conflicts with what your SEO plugin generates.
- Verify that every fact in your schema (prices, ratings, availability) matches what’s visible on the page.
What to implement first
If you’re starting from zero, here’s the order that gives you the most impact:
- Organization on your homepage. Establishes your entity in the Knowledge Graph.
- Breadcrumb across your site. Improves search result appearance and helps engines understand your site structure.
- Article on blog posts and guides. Enables article-specific rich results and signals authorship and recency.
- Product on product or service pages. Triggers shopping-related rich results and gives AI engines structured facts about what you sell.
- FAQ on relevant pages. Expands your search result footprint with expandable Q&A.
- LocalBusiness if you have a physical location. Powers your knowledge panel.
Each of these feeds both traditional rich results and the structured understanding that AI engines rely on for AI search optimization.
Schema in 2026: beyond rich snippets
The traditional pitch for schema markup has always been rich results. More stars, more clicks, more real estate on the search results page. That’s still true, and the data from Google’s case studies confirms it works.
But the bigger shift is happening underneath. As AI search grows, with Google AI Overviews now used by over a billion people globally, the structured layer of the web becomes more important. AI engines need to understand entities, verify facts, and assess authority at scale. Schema markup is how you declare those things in a format machines can trust.
The brands that treat schema as a core technical requirement, not an optional nice-to-have, will have a meaningful advantage in both traditional and AI-driven search. Not because schema is a ranking factor on its own, but because it makes every other signal clearer: your authority, your content, your products, your entity.
Start with Organization. Add Product and Article where they apply. Validate everything. Then track whether your pages start appearing in rich results and AI visibility checks. The data will tell you what to expand next.