Search engines read your page as text and try to work out what it means. Schema markup removes the guesswork: it labels your content in a vocabulary machines already understand, so a price is unmistakably a price, a rating is a rating, and an author is a person. Do it well and you become eligible for the enhanced listings – stars, prices, breadcrumbs – that make results stand out.
But this is a field where most published advice has gone stale, and following it means adding markup for search features that no longer exist. This guide is built on Google’s current documentation. It expands the structured-data section of the technical SEO strategies guide on GrowWithSakib, and assumes the groundwork covered in what technical SEO actually is on GrowWithSakib.
What Schema Markup Actually Is
Schema.org is a shared vocabulary – created jointly by Google, Microsoft, Yahoo and Yandex – of types and properties for describing things: an Article, a Person, a Product, an Event. Schema markup is that vocabulary applied to your page. Structured data is the general term for the same idea. In practice the words are used interchangeably.
The payoff is eligibility, not a ranking boost. Correct markup makes your page eligible for a rich result – the enhanced listing with stars, images, prices or breadcrumbs. Google decides whether to show it. Schema markup is not a direct ranking factor, and any guide promising rankings from schema alone is overselling. What it reliably does is help machines understand your page, and open the door to features that lift click-through.
Why JSON-LD Is the Format to Use
There are three ways to write structured data, and the choice is easy because Google explicitly recommends JSON-LD:
| Format | How It Works | Verdict |
|---|---|---|
| JSON-LD | A self-contained script block, separate from your HTML | Google’s recommended format – use this |
| Microdata | Attributes woven into your visible HTML tags | Works, but tangles markup with content |
| RDFa | Similar to Microdata, attribute-based | Supported, but rarely the practical choice |
JSON-LD wins because it sits in a single block that doesn’t touch your page’s HTML structure. That makes it easy to add, easy to edit, easy to generate from a template or plugin, and impossible to break by redesigning your layout. It can go in the <head> or the <body> – Google reads it either way.
The Schema Types That Still Earn Rich Results in 2026
Schema.org defines over 800 types. You need a handful. Here’s the current picture – including the two that most guides still get wrong:
| Schema Type | What It’s For | Status in 2026 |
|---|---|---|
| Article | Blog posts, news, guides | Active – supports article rich results |
| Organization | Your company identity, logo, profiles | Active – powers knowledge panel signals |
| Product | E-commerce items with price and availability | Active – one of the highest-value types |
| LocalBusiness | Physical businesses with address and hours | Active – key for local search |
| BreadcrumbList | Your page’s position in site hierarchy | Active – replaces the URL in results |
| Review / AggregateRating | Star ratings on products and services | Active – the star snippets |
| Event / Video | Events and video content | Active – both still supported |
| FAQPage | Question-and-answer sections | RETIRED as a rich result on 7 May 2026 |
| HowTo | Step-by-step instructions | DEPRECATED – desktop removed September 2023 |
If you have existing FAQ sections, keep them – well-built questions and answers still serve readers and still get read by search and AI systems. What changed is the visual reward, not the value of clear answers. The deeper dive on that markup lives in the FAQ schema markup guide on GrowWithSakib, which should now be read with this deprecation in mind.
What the Markup Actually Looks Like
Here’s real, copyable JSON-LD. Every block follows the same shape: a context (always Schema.org), a type, and properties.
Article – for blog posts and guides
| <script type=”application/ld+json”> { “@context”: “https://schema.org”, “@type”: “Article”, “headline”: “Schema Markup Guide for Beginners”, “author”: { “@type”: “Person”, “name”: “Your Name” }, “publisher”: { “@type”: “Organization”, “name”: “Your Company” }, “datePublished”: “2026-07-17”, “dateModified”: “2026-07-17” } </script> |
LocalBusiness – for any business with a physical location
| <script type=”application/ld+json”> { “@context”: “https://schema.org”, “@type”: “LocalBusiness”, “name”: “Example Cafe”, “address”: { “@type”: “PostalAddress”, “streetAddress”: “12 High Street”, “addressLocality”: “Manchester”, “postalCode”: “M1 2AB”, “addressCountry”: “GB” }, “telephone”: “+44-161-555-0100”, “openingHours”: “Mo-Fr 08:00-17:00” } </script> |
BreadcrumbList – the quiet high-value win
Breadcrumbs replace the raw URL in your search listing with a readable path, which looks cleaner and helps users understand where the page sits. It’s low-effort and applies to almost every site:
| <script type=”application/ld+json”> { “@context”: “https://schema.org”, “@type”: “BreadcrumbList”, “itemListElement”: [{ “@type”: “ListItem”, “position”: 1, “name”: “Home”, “item”: “https://example.com/” },{ “@type”: “ListItem”, “position”: 2, “name”: “Guides”, “item”: “https://example.com/guides/” }] } </script> |
The Golden Rule: Markup Must Match Visible Content
How to Add Schema Markup (WordPress and Beyond)
Rank Math
- Built-in by default: Rank Math automatically outputs Article, Organization, WebSite and BreadcrumbList schema once configured, so a standard blog is largely covered out of the box.
- Per-page control: the Schema tab in the editor lets you set the type per post – switching an article to Product, Recipe or LocalBusiness and filling in the properties without touching code.
- Where to start: complete the setup wizard’s Organization/Person details first – that’s what powers your site-wide identity markup.
Yoast SEO
- An automatic graph: Yoast builds a connected schema graph for every page – Organization, WebSite, WebPage, Article and Breadcrumb – linked together by IDs, which is technically excellent and needs no manual work.
- Configure the basics: set whether the site represents an organisation or a person, add your logo and social profiles, and Yoast handles the rest.
- For more types: Yoast covers the core well; specialised types (Product, Event) usually come from your e-commerce plugin or a dedicated schema plugin.
Other Platforms and Manual Implementation
- Shopify and WooCommerce generate Product schema automatically from your product data – verify it rather than duplicating it.
- Any site can add JSON-LD manually: paste the script into the page template’s head. Google reads it wherever it appears in the HTML.
- Avoid duplicate markup – a common problem when a theme and a plugin both output Organization schema. Two conflicting blocks confuse Google; keep one source of truth.
How to Validate Your Structured Data
Never deploy markup without testing it. Three tools, each for a different job:
| Tool | What It Does | When to Use |
|---|---|---|
| Rich Results Test | Shows which Google rich results your page qualifies for | Before and after adding markup |
| Schema Markup Validator | Validates syntax against the full Schema.org vocabulary | For types Google doesn’t support |
| Search Console enhancements | Reports errors across your whole site over time | Ongoing monitoring after deployment |
Does Schema Markup Help With AI Search?
This deserves an honest answer, because the claims got wild after the FAQ deprecation – one half of the industry declared schema dead, the other declared it essential for AI. Both overshot.
So treat schema as one part of machine-readability rather than an AI shortcut: it strengthens your entity signals and keeps your facts unambiguous, while the substance of the answer does the heavy lifting. That’s the same conclusion reached in the generative engine optimisation guide on GrowWithSakib and in how to get cited by ChatGPT and Perplexity on GrowWithSakib.
Common Schema Markup Mistakes
| Mistake | Why It Hurts | Do This Instead |
|---|---|---|
| Adding FAQ schema for rich results | The feature was retired in May 2026 | Keep existing markup; stop chasing the dropdown |
| Still implementing HowTo markup | Deprecated on desktop since Sept 2023 | Use active types that still earn features |
| Marking up invisible content | Violates spam policy; risks manual action | Only mark up what’s visible on the page |
| Inventing ratings or reviews | Manual action removes ALL rich results | Mark up genuine, displayed reviews only |
| Using Microdata by default | Tangles markup with your HTML | Use JSON-LD – Google’s recommended format |
| Duplicate schema from theme + plugin | Conflicting blocks confuse Google | Keep one source of truth per type |
| Deploying without validating | Silent syntax errors mean no eligibility | Test in the Rich Results Test first |
| Expecting schema to lift rankings | It’s not a direct ranking factor | Use it for eligibility and clarity, not rankings |
Frequently Asked Questions
What is schema markup and why does it matter?
Schema markup, also called structured data, is code you add to a page that describes its content using a standard vocabulary from Schema.org – explicitly labelling a price as a price, a rating as a rating, an author as a person. It matters because it removes guesswork for machines and makes your page eligible for rich results: the enhanced listings with stars, images, prices or breadcrumbs that stand out in search. It isn’t a direct ranking factor, but the eligibility it unlocks can meaningfully improve click-through rates.
Is FAQ schema still worth using in 2026?
Not as a way to win rich results – Google retired FAQ rich results on 7 May 2026, and they no longer appear in Search. Google is also removing the FAQ search appearance, rich result report and Rich Results Test support in June 2026, with Search Console API support ending in August. However, FAQPage remains valid Schema.org markup, rankings are unaffected by the change, and Google has said unused structured data causes no problems. So don’t rush to strip existing markup out; just stop treating it as a traffic tactic.
Which schema types still earn rich results?
The reliably active types in 2026 include Article for blog posts and guides, Organization for company identity, Product for e-commerce items, LocalBusiness for physical locations, BreadcrumbList for site hierarchy, Review and AggregateRating for star ratings, plus Event, Video and Recipe. The notable exceptions are FAQPage, retired as a rich result in May 2026, and HowTo, deprecated on desktop back in September 2023. Google also retired seven further types in June 2025, so always check its current structured data documentation before investing effort in a type.
Why does Google recommend JSON-LD over Microdata?
Because JSON-LD sits in a single self-contained script block that doesn’t touch your visible HTML, making it far easier to add, edit and generate automatically. Microdata and RDFa weave attributes through your HTML tags, which tangles your markup with your content and breaks easily during redesigns. JSON-LD can be placed in either the head or the body of your page, is trivial for plugins and templates to output, and is the format Google explicitly recommends – so unless you have a specific reason otherwise, use it.
Does schema markup help with AI search and AI Overviews?
Only indirectly, and less than many claims suggest. Google’s own guidance states there is no special structured data required for AI Overviews or AI Mode – what it asks is that any structured data you use matches your visible page content. Schema does help machines parse entities and relationships clearly, which is useful to any system reading your page, but what actually earns an AI citation is a clear, well-structured answer in your visible content rather than the markup around it. Treat schema as machine-readability hygiene, not an AI shortcut.
Can schema markup get my site penalised?
Yes, if it describes content that isn’t genuinely on the page. Google’s spam policies require structured data to match visible content, and marking up invented ratings, prices you don’t display, or reviews that don’t exist can trigger a manual action that removes rich results across your site. It’s one of the more common causes of suddenly vanishing star ratings. The rule is simple: only mark up what a visitor can actually see on the page, and never use structured data to make claims the content doesn’t support.
How do I add schema markup in WordPress?
The easiest route is your SEO plugin. Rank Math automatically outputs Article, Organization, WebSite and BreadcrumbList schema once you complete its setup wizard, and its Schema tab lets you change the type per post. Yoast SEO builds a connected schema graph for every page automatically, linking Organization, WebSite, WebPage and Article together – you just set whether the site represents an organisation or a person and add your logo and profiles. For specialised types like Product, your e-commerce plugin usually generates the markup, so verify rather than duplicate it.
How do I check if my structured data is working?
Use Google’s Rich Results Test to see which rich results your page qualifies for – run it before and after adding markup. For types Google doesn’t support, or to check pure syntax, use the Schema Markup Validator at validator.schema.org. Then monitor Search Console’s enhancement reports, which surface errors across your whole site over time. Note that Google is removing FAQ support from the Rich Results Test in June 2026, so FAQPage markup will stop returning results there – that reflects the retired feature, not a fault in your code.
Key Takeaways
- Schema markup describes your content to machines using the Schema.org vocabulary, making you eligible for rich results. It is not a direct ranking factor.
- A schema TYPE and a RICH RESULT are different things – Google can retire the visual feature while the markup stays perfectly valid. That distinction explains 2026.
- Google retired FAQ rich results on 7 May 2026. Rankings are unaffected, FAQPage is still valid markup, and there’s no need to rush and remove it.
- HowTo rich results were deprecated back in September 2023, and seven more types were retired in June 2025 – so check Google’s current docs before investing in any type.
- The types that still earn features: Article, Organization, Product, LocalBusiness, BreadcrumbList, Review/AggregateRating, Event and Video.
- Use JSON-LD – Google’s recommended format. It’s a self-contained script block that doesn’t tangle with your HTML and is easy for plugins to generate.
- The golden rule: markup must match visible page content. Invented ratings or hidden claims violate spam policy and can trigger a manual action.
- On AI search, be realistic: Google says no special schema is required for AI Overviews. Clear visible answers earn citations; schema just keeps your facts unambiguous.
