Schema markup is code you add to your website that helps search engines understand what your content is about. It uses a standardised vocabulary from Schema.org to label things on your pages – products, articles, businesses, events, people – so that search engines don’t have to guess. The result: your pages become eligible for rich results, Knowledge Graph entries, and increasingly, citations in AI-generated search responses.
That’s the quick version. The practical version involves knowing which schema types are worth implementing, how to write them properly, and how to measure whether they’re doing anything useful. That’s what this guide covers. If you’re looking for where structured data fits within a broader technical SEO strategy, we cover that in detail separately.
What Is the Difference Between Schema Markup and Structured Data?
The terms get used interchangeably, but they’re not quite the same thing. Structured data is the broader concept: any data organised in a consistent, machine-readable format. Schema markup is a specific type of structured data that uses the Schema.org vocabulary – a collaborative project launched in 2011 by Google, Bing, Yahoo, and Yandex to create a shared language for describing web content.
Schema.org defines hundreds of “types” (like `Product`, `Article`, `LocalBusiness`) and “properties” (like `name`, `price`, `author`). When you add schema markup to a page, you’re using these types and properties to describe your content in a way search engines can parse directly, rather than inferring meaning from the surrounding HTML.
Think of it this way: without schema, Google reads your page and makes educated guesses about what’s there. With schema, you’re handing it a labelled inventory.
JSON-LD, Microdata, and RDFa: Which Format Should You Use?

There are three formats for adding schema markup to a page. Here’s how they compare:
| Format | Where it goes | Readability | Google’s preference |
|---|---|---|---|
| JSON-LD | In a `
``` Clean, readable, and entirely separate from your page content. What Are Rich Results and Why Do They Matter?Rich results are the enhanced search listings that appear when Google can read and validate your structured data: star ratings on product listings, FAQ dropdowns, event dates and venues, breadcrumb trails replacing raw URLs. They take up more visual space and draw the eye. Pages with rich results consistently see higher click-through rates than standard blue links at the same position. Not every schema type triggers a rich result. Google supports them for a specific set, including Article, Product, FAQ, Event, Recipe, HowTo, Review, LocalBusiness, BreadcrumbList, and VideoObject. If your schema is valid but isn't for a supported rich result type, it can still help search engines understand your content – it just won't produce a visual enhancement in the SERPs. Which Schema Types Should You Implement?This depends entirely on what's on your site. There's no universal checklist, but there is a decision framework that works for most sites. Every Site Should HaveOrganization – on your homepage. Covers your business name, logo, contact details, and social profiles. This feeds directly into Google's Knowledge Graph and helps establish your entity identity. BreadcrumbList – on every interior page. Replaces ugly URLs in search results with a readable navigation trail. Low effort, high visual impact. WebSite – on your homepage. Includes your site name and (optionally) search action markup. Content-Heavy Sites (Blogs, Publishers, Agencies)Article or BlogPosting – on every blog post or editorial page. Includes headline, author, publish date, and modified date. Helps Google understand your publishing activity and can trigger article-specific SERP features. Person – for author pages. Links content to named individuals with credentials. This connects to E-E-A-T signals – if you've got an article on that already published, it covers the relationship between author credibility and search quality in full. VideoObject – on any page with embedded video. Helps videos appear in video search results and can generate video-rich snippets in standard results. E-Commerce SitesProduct – on every product page. Price, availability, reviews, SKU. This is the single most impactful schema type for e-commerce SEO because it directly triggers rich results with pricing and stock information. Review/AggregateRating – alongside Product schema. Star ratings in search results are one of the strongest CTR drivers available. Offer – nested within Product. Specifies price, currency, availability, and seller details. Service Businesses and Local CompaniesLocalBusiness (or a more specific subtype like `Dentist`, `Restaurant`, `LegalService`) – on your homepage or location page. Address, opening hours, phone number, service area. Essential for local SEO because it reinforces your Google Business Profile data and helps search engines connect your site to a physical location. Service – on service pages. Describes what you offer, service areas, and pricing where applicable. Events, Courses, and How-TosEvent – date, location, performer, ticket availability. Triggers event-rich results with date and venue prominently displayed. HowTo – step-by-step instructions with optional images per step. Google scaled back HowTo rich results in late 2023, limiting them primarily to desktop, but the schema still helps search engines understand instructional content and can improve visibility in AI-generated responses. The pattern here is simple: match your schema to your content. Don't add schema types that don't reflect what's actually on the page, and don't skip the types that describe your core content. How Schema Connects to the Knowledge GraphGoogle's Knowledge Graph is a database of entities – people, places, organisations, things – and the relationships between them. When you add Organization schema to your homepage with your name, logo, founding date, and social profiles, you're giving Google structured evidence to build or reinforce your entity in the Knowledge Graph. This powers those information panels on the right side of search results and feeds into how Google understands brand queries and disambiguates similar names. The more connected your schema is – linking articles to authors, authors to organisations, organisations to locations – the more context you're providing. Search engines build a picture from the relationships between schema blocks, not just individual ones. An article written by a named person who works for a recognised organisation at a specific location creates a web of structured connections that's far more useful than any single schema type alone. Schema Hierarchy: How Types Relate to Each OtherSchema.org is built on a hierarchy. At the top sits `Thing` – the most generic type. Below it sit types like `CreativeWork`, `Organization`, `Place`, and `Event`. Below those: `Article` is a child of `CreativeWork`, `Restaurant` is a child of `LocalBusiness`, which itself is a child of `Organization`. Being as specific as possible gives search engines more precise information. Marking up a dentist's practice as `Dentist` rather than just `LocalBusiness` tells Google exactly what kind of business it is. Marking up a recipe as `Recipe` rather than just `Article` triggers recipe-specific rich results. Start at the most specific type that accurately describes your content. It's worth noting that Schema.org markup is separate from Open Graph tags. Open Graph (developed by Facebook) controls how your content appears when shared on social media – the title, description, and image in a link preview. Schema markup and Open Graph serve different purposes, and most sites need both. They don't conflict; they just talk to different systems. Schema and AI Search: Why Structured Data Matters More NowThis is where things get genuinely interesting for SEO. Google's AI Overviews, Bing's Copilot, ChatGPT's web browsing, and Perplexity all rely heavily on structured data to understand, verify, and cite web content. Schema markup has gone from a "nice-to-have" SERP enhancement to a signal that directly influences whether AI systems reference your content. AI models process enormous amounts of web content and need to determine what's accurate, authoritative, and relevant. Structured data provides machine-readable context that plain HTML doesn't. When your content includes schema identifying the author, their credentials, the publishing organisation, and the publication date, AI systems can evaluate it with more confidence. Microsoft confirmed in 2025 that schema markup directly helps its large language models interpret web content for Bing's Copilot. Sites with well-implemented structured data have shown measurably higher visibility in AI-generated responses. Schema alone won't get you cited in AI Overviews – the content itself still needs to be authoritative and genuinely useful. But a page with Article schema linking to a named author with Person schema, published by a recognised organisation, is far easier for an AI system to evaluate than an anonymous page with no structured data at all. For SEO content strategies going forward, structured data isn't optional. It's part of the foundation. How to Implement Schema Markup (Without a Developer)You don't need to write JSON-LD by hand for every page. There are several approaches depending on your platform and technical comfort level. WordPress PluginsYoast SEO, RankMath, and Schema Pro all generate schema markup automatically based on your content. Yoast adds Organization, WebSite, Article, and BreadcrumbList schema out of the box, and you can configure Person schema for authors. RankMath offers similar coverage with a few more schema types available in its settings. These plugins handle the basics well. Where they fall short is on highly customised schema – Product schema with detailed offer data, Event schema with multiple performances, or nested schema connecting several entities. For those, you'll likely need either a more advanced plugin or manual JSON-LD. Google Tag ManagerIf you're comfortable with Tag Manager, you can inject JSON-LD scripts through custom HTML tags. This is a useful middle ground – you get more control than a plugin without needing to edit your site's source code directly. It's particularly handy for adding schema to pages where your CMS doesn't give you template access. Manual ImplementationFor custom sites or situations where you need full control, writing JSON-LD and adding it directly to your page templates is the most flexible approach. You can use Google's Structured Data Markup Helper to generate a starting template, then refine it to match your exact content. Schema GeneratorsTools like Merkle's Schema Markup Generator, technicalseo.com's Schema Builder, and Hall Analysis's JSON-LD Generator let you fill in a form and produce valid JSON-LD to copy into your pages. They're a quick way to generate accurate markup without memorising the Schema.org vocabulary. Testing and Validating Your SchemaImplementing schema is only worthwhile if it's valid and error-free. Invalid markup typically gets ignored – or worse, triggers errors in Search Console that make it harder to spot real issues. Google's Rich Results TestThe primary tool. Paste a URL or a code snippet, and it tells you whether your schema is valid, which rich result types it qualifies for, and any errors or warnings. This should be your first stop after implementing any new schema. Schema Markup ValidatorRun by Schema.org, this validates your markup against the full Schema.org vocabulary rather than just Google's supported subset. Useful for catching structural issues that the Rich Results Test might not flag. Google Search ConsoleThe Enhancements section in Search Console reports on schema health across your entire site. It groups issues by schema type, showing you errors (must fix), warnings (should fix), and valid items. Check this regularly – it's the only way to spot site-wide schema problems before they affect your search performance. Common Validation ErrorsThese come up repeatedly: Missing required properties – each schema type has mandatory fields. An Article without a `headline`, or a Product without a `name`, will fail validation. Incorrect nesting – schema types often need to be nested correctly. A Review must reference the thing being reviewed. An Offer must sit inside a Product. Mismatched types – using `@type: "Article"` on a product page, or `@type: "Product"` on a blog post. The schema must match the content. Invalid URLs – broken image URLs in logo or image properties. Google validates these and flags them. How to Audit Your Existing SchemaIf you've already got some structured data on your site (or suspect your CMS has been adding it automatically), a structured audit tells you what's working, what's broken, and what's missing. Here's a repeatable process: Crawl your site with a tool like Screaming Frog, configured to extract structured data. This gives you a complete inventory of every schema type on every page. Check for consistency. Is Organization schema on every page, or just the homepage? Is Article schema on all blog posts, or only some? Inconsistencies suggest the implementation wasn't systematic. Validate a sample. Run 10-15 representative pages through the Rich Results Test. Look for patterns – if the same error appears on multiple pages, it's likely a template-level issue. Cross-reference with Search Console. Check the Enhancements reports for each schema type. Are there errors you weren't aware of? Are valid items actually generating impressions? Identify gaps. Compare what you have against what you should have based on your page types. Product pages without Product schema, location pages without LocalBusiness schema, blog posts without Article schema – these are missed opportunities. Check for deprecated types. Google deprecated several schema types in January 2026, including Practice Problem, Dataset (for general search), Sitelinks Search Box, and SpecialAnnouncement. If you're still using any of these, they won't cause harm, but they're no longer generating rich results. Review schema connectivity. Are your schema blocks connected? Does your Article schema reference the author's Person schema? Does your LocalBusiness schema link to your Organization? Isolated schema blocks are less valuable than connected ones. Measuring Schema ImpactAdding schema isn't a "set and forget" task. You should be measuring whether it's actually making a difference. Search Console Performance DataAfter implementing new schema, monitor these metrics in Search Console's Performance report: Click-through rate (CTR) – filter by pages where you've added schema. Rich results typically increase CTR by making your listing more prominent. If you're seeing a noticeable uplift in CTR without a significant change in ranking position, that's likely the rich result doing its work. Impressions for rich result types – the Enhancements reports show how many impressions each schema type is generating. If a schema type shows zero impressions over several weeks, something's wrong. Rich result appearance – use the Search Appearance filter in Performance to see clicks and impressions specifically from rich results versus standard results. Before-and-After ComparisonRecord your CTR and impression data for a set of pages before implementing schema, then compare after 4-8 weeks. Control for other changes (ranking shifts, seasonal trends, algorithm updates) as best you can. Schema doesn't move rankings directly – Google has been clear about that. What it does is improve how your existing rankings perform: higher CTR from richer listings, better entity understanding from connected schema, and stronger signals for AI-generated responses. If you're expecting a ranking jump from schema alone, you'll be disappointed. If you're expecting your existing positions to work harder, that's realistic. Common Schema Mistakes (and How to Avoid Them)Marking Up Content That Isn't VisibleYour schema must reflect what users can actually see on the page. Adding Product schema with a price that doesn't appear on the page, or Review schema for reviews that aren't displayed, violates Google's structured data guidelines and can result in manual actions. Using Self-Serving Review SchemaYou can't add Review or AggregateRating schema to your own business's homepage to display star ratings for yourself. Google's guidelines explicitly prohibit self-serving reviews. Review schema should reflect genuine third-party reviews of a product, service, or business. Over-Marking with FAQ SchemaFAQ schema should only be used on pages where the questions and answers are genuinely part of the page content and visible to users. Tacking FAQ schema onto every page as a CTR tactic will, at best, get ignored and, at worst, trigger a manual action. Ignoring Schema After ImplementationSchema breaks. CMS updates change template structures. Plugins conflict. Pages get redesigned. If you don't periodically validate your schema, you won't know it's broken until you notice your rich results have disappeared from Search Console. Copying Schema Between Pages Without Updating ItSomeone copies a JSON-LD block from one page to another and forgets to update the properties. You end up with Product schema listing the wrong name, or Article schema with the wrong publish date. Every schema block should accurately describe the specific page it's on. What Google Deprecated in 2026 (and What It Means)In January 2026, Google removed rich result support for several schema types: Practice Problem, Dataset (for general search), Sitelinks Search Box, SpecialAnnouncement, and Q&A. Google's John Mueller clarified that this isn't a move away from structured data – it's a cleanup of types that were underused, outdated, or being folded into core functionality. If you're using any of these, don't panic. They won't cause penalties or ranking drops. They simply won't generate rich results any more. Remove them for cleaner code, or leave them – it's housekeeping, not an urgent fix. The schema types that drive real SEO value – Product, Article, LocalBusiness, Organization, FAQ, Event, BreadcrumbList, HowTo, Review, VideoObject – remain fully supported and actively recommended. Making Schema Part of Your SEO WorkflowSchema markup isn't something you bolt on once and walk away from. It should be part of your standard publishing process: New page template? Define the schema that goes with it before the template goes live. New blog post? Ensure your CMS or plugin is automatically generating Article schema with the correct author, date, and publisher details. New product? Check that Product schema includes price, availability, reviews, and SKU. Validate before publishing. Site redesign or migration? Audit schema before and after. Template changes are the most common cause of schema breaking silently. Quarterly review. Run a site-wide schema audit. Check Search Console Enhancements for errors. Validate a sample of pages. Look for new schema opportunities based on content you've added since the last review. The sites that get the most from structured data are the ones that treat it as an ongoing part of their technical health, not a one-off project. If your Core Web Vitals are already in shape (covered in a separate article), schema is the next layer of technical refinement that compounds over time. At Gorilla Marketing, structured data analysis is built into every technical SEO audit we deliver. We review what's implemented, what's missing, what's broken, and what's worth adding – then translate that into clear actions your team or developers can act on without needing to learn the Schema.org documentation themselves. |




