What schema does and does not do
Schema markup is structured data that tells search engines what a page is about in a machine-readable format. It does not directly improve rankings. It makes you eligible for rich results, which improve click-through rate, and it helps AI systems understand your content well enough to cite it.
That second benefit has become more valuable as answer engines have grown.
The types worth implementing
| Type | Use for | Visible result |
|---|---|---|
| Organization | Every site, once | Knowledge panel eligibility |
| LocalBusiness | Physical locations | Local pack support |
| Product | E-commerce pages | Price, availability, rating in results |
| Article / BlogPosting | Editorial content | Top stories, better AI comprehension |
| FAQPage | Genuine question sections | Reduced visibility now, still useful for AI |
| BreadcrumbList | Any nested page | Breadcrumb trail in results |
| Event | Exhibitions, webinars | Event listings |
The rules that get you skipped
Google ignores or penalises structured data that breaks these, so they are worth stating plainly:
- ✓Mark up only what is visible on the page. Schema describing content a user cannot see is a guideline violation, not a shortcut.
- ✓Do not invent reviews. Self-serving review markup on your own organisation is ignored and risks manual action.
- ✓Keep it accurate. Prices and availability that disagree with the page will cost you eligibility.
- ✓Use JSON-LD. It is Google's stated preference and much easier to maintain than inline microdata.
- ✓One primary type per page, with related types nested rather than duplicated.
Why schema matters more for AI search
Answer engines need to establish what an entity is and how confident they can be about it. Explicit structured data removes ambiguity that a language model would otherwise have to infer. Organisation schema with consistent naming, an address and a logo does more for entity clarity than several blog posts.
This connects directly to generative engine optimisation, where being an unambiguous entity is most of the work.
Testing and maintaining it
- 1Validate with Google's Rich Results Test on a live URL, not just a snippet.
- 2Check the Schema.org validator for syntax that is valid but not Google-supported.
- 3Watch the Enhancements reports in Search Console for errors appearing at scale.
- 4Re-test after any template change. Schema is generated by templates and breaks silently when they change.
Implementation and validation are part of the technical work in our SEO, AEO and GEO service, and it is on the list in our technical SEO checklist.
Frequently asked questions
Does schema markup improve rankings?
Not directly. It makes you eligible for rich results, which improve click-through rate, and it helps machines understand your content. The ranking benefit is indirect but real.
Is FAQ schema still worth adding?
Google reduced FAQ rich result visibility significantly, so the direct benefit is smaller than it was. It remains useful for AI comprehension and costs little to add where the questions are genuine.
Can I add schema without a developer?
On WordPress and Shopify, plugins and apps handle common types adequately. Custom implementations, or anything beyond the basics, generally need someone comfortable with JSON-LD.
