Schema is one of those SEO terms thrown around as if everyone already knows what it means. Most people don’t, and the explanations online tend to make it sound either magical or terrifying. It’s neither.
In plain terms, schema is a way of labelling your content so that machines can read it without guessing. Your page might say “Open Monday to Friday, 9 until 5”. A person understands that instantly. A search engine has to work it out. Schema removes the guesswork.
It’s also a topic where the advice changed quite a lot this year, so some of what you’ll read elsewhere is already out of date. I’ll flag where that matters.
Where the Word Comes From
Schema.org is a shared vocabulary, started in 2011 by Google, Microsoft and Yahoo, with Yandex joining soon after, that gives everyone the same names for things. A business is a LocalBusiness. A blog post is an Article. A person has a name, a job title and a web address. Because everyone agrees on the terms, a search engine in any country can read the same label and understand it the same way.
You’ll often see people say “schema markup” or “structured data”. They mean the same thing in practice. Schema.org supplies the vocabulary, and structured data is the code that uses it.
What It Looks Like
Schema can be written in a few formats, but Google recommends one called JSON-LD, and that’s what almost everyone uses now. It sits in a block of code on the page and is invisible to visitors. Here’s a stripped-back example for a made-up business.
{ “@context”: “https://schema.org”, “@type”: “LocalBusiness”, “name”: “Example Plumbing Ltd”, “telephone”: “+44 1234 567890”, “address”: { “@type”: “PostalAddress”, “streetAddress”: “1 High Street”, “addressLocality”: “Anytown”, “postalCode”: “AB1 2CD”, “addressCountry”: “GB” }, “openingHours”: “Mo-Fr 09:00-17:00”}
Even if you’ve never written a line of code, you can read that. It names the business, gives a phone number and address, and states the opening hours. Nothing there is shown to a visitor. It’s just a tidy, labelled summary for anyone who wants to read it.
What Schema Does and Doesn’t Do
Here’s where expectations tend to go wrong. Schema doesn’t push you up the rankings. Google has said structured data isn’t a ranking factor in itself, and I’d treat anybody selling it as an SEO shortcut with suspicion.
What it can do is help Google understand a page more accurately, and for certain content types, make you eligible for extra features in the results. Star ratings on a product, price and availability, event dates, breadcrumb trails showing where a page sits on a site. Those richer listings, usually called rich results, can improve how a result looks and sometimes how many people click it.
The key word there is eligible. Marking something up doesn’t guarantee Google will show anything extra. It decides that for itself, page by page.
What Changed in 2026
This is the part many guides haven’t caught up with. Google’s own documentation says FAQ rich results stopped appearing in Search from 7 May 2026. Until then, a page with FAQ markup could show expandable questions under its listing. That feature has gone for every site. A practice problem feature for education content was removed earlier in the year, in January.
The FAQPage markup itself isn’t banned or broken. It’s still valid schema, and leaving it on a page won’t harm you. It just no longer produces that visible result in Google. If you added FAQ schema purely to get those dropdowns, there’s no benefit left to chase.
The second change is about AI search. Google’s guidance on its generative AI features, published in May, says no special schema is needed to appear in AI Overviews or AI Mode. You’ll find plenty of claims online that the right markup is the key to AI visibility. Google says otherwise, and I’d go with the people who run the system. Other AI tools may behave differently, but nobody has shown that schema is a dependable lever for them either.
None of this makes schema pointless. It just means the honest case for it is smaller and quieter than the hype suggests. It’s good housekeeping that helps machines read your content, and it’s still the route to a handful of useful rich results.
The Types Most Small Sites Actually Need
- Organization or LocalBusiness, so your name, address, phone number and logo are stated clearly
- Article or BlogPosting, for the posts you publish, with author and date
- BreadcrumbList, if your site has a clear page hierarchy
- Product and Offer, for shops, where price and stock details can show in results
- Event, VideoObject or Review snippets, only where they truly apply to the page
Google keeps a list of the types that can trigger visible features, and it changes, as the FAQ news shows. Check the current list in its documentation before building a plan around any one of them.
Mistakes I See Most Often
Marking Up What Isn’t on the Page
Schema must describe content visitors can actually see. Claiming five-star reviews in the code when the page shows none is a quick route to a manual action, which is a penalty applied by a person at Google.
Reviewing Your Own Business
Google doesn’t allow self-serving reviews, meaning ratings you collect and mark up about your own organisation, to produce review stars on your own pages. It also added a guideline this year about fake and undisclosed incentivised reviews. Keep review markup for genuine third-party reviews and the content types it’s meant for.
Leaving Template Text Behind
Copied examples often still contain placeholder phone numbers, other companies’ names or the wrong address. Search engines read it all as fact.
Stacking Plugins
Two plugins both outputting schema can produce duplicates and conflicting details. One source of truth is better than three.
Adding Schema to a WordPress Site
You rarely need to write it by hand. Most SEO plugins, including Yoast, Rank Math and others, generate a sensible set of schema automatically, covering your organisation, your pages, your posts and breadcrumbs. Many block themes and e-commerce plugins add product markup too.
That means the practical job is checking, not creating. Look at what your plugin is producing, make sure your business details are filled in properly in its settings, and test a few key pages.
- Google’s Rich Results Test shows whether a page is eligible for specific features
- The Schema Markup Validator at validator.schema.org checks that your code is valid, whether or not Google uses it
- Search Console reports problems with the structured data it finds across your site, though some reports have been withdrawn as features were retired
A Quick Schema Checklist
☐ Fill in your business name, address, phone number and logo in your SEO plugin
☐ Check that one schema source is active, not several competing ones
☐ Make sure everything marked up is also visible on the page
☐ Test your homepage and one post in the Rich Results Test and the Schema Markup Validator
☐ Remove placeholder text and anything out of date
☐ Don’t add review markup about your own business
☐ Re-check Google’s documentation once or twice a year, because supported features change
Frequently Asked Questions
Is schema a ranking factor?
No. Google has said structured data isn’t a ranking factor on its own. It helps Google understand a page and can make it eligible for rich results, but it won’t lift a weak page above a strong one.
Do I need schema to appear in AI Overviews?
No. Google’s May 2026 guidance on its AI features says no special schema is required. Clear, useful, original content that is indexed and eligible to show in Search is what counts.
Should I remove the FAQ schema I already have?
There’s no need. FAQPage markup is still valid and doesn’t cause problems; it just no longer produces the dropdown listing in Google. If you want to tidy it away, you can, but there’s no urgency.
Does WordPress add schema automatically?
Not on its own, but most SEO plugins do, and many themes add some basic markup. Check what your site is outputting before adding anything, so you don’t end up with duplicates.
How do I check my schema is working?
Run key pages through Google’s Rich Results Test and the Schema Markup Validator, and keep an eye on Search Console for structured data warnings. Remember that valid code doesn’t guarantee Google will show a rich result.
Not Sure What Your Site Is Telling Google?
If you’d like a second opinion on your structured data, or simply want to know what your plugins are outputting, get in touch for a plain conversation with no obligation and no sales pitch.