Structured data is information added to a page in a standard format so machines can read it reliably. Schema markup, from the Schema.org vocabulary, is the most common format, usually written as JSON-LD in the page code. It can make pages eligible for rich results such as product, review, breadcrumb and event features, and helps search and AI systems identify who you are and what a page describes. It must match the visible content, and it does not guarantee a rich result or an AI citation.
The distinction between structured data and regular web content is the difference between a human reading your page and understanding it, versus a computer parsing your page and extracting specific data points. Humans understand context intuitively; machines need explicit declarations. Structured data provides those declarations — eliminating the ambiguity that forces search engines and AI tools to make educated guesses about your content's meaning.
What is schema markup?
Schema markup (also called structured data) is code added to web pages that explicitly tells search engines what the content means — not just what it says. It uses a standardised vocabulary from Schema.org to describe entities like organisations, products, events, recipes, people, and FAQs in a machine-readable format. Schema markup enables search features like star ratings, FAQ accordions, and product prices in search results, and is also how AI tools like Google AI Overviews and Perplexity identify and extract specific facts from pages to use in AI-generated responses.
Without schema markup, search engines must infer the meaning of your content from context — reading your page like a human would and making educated guesses about what type of content it is. With schema markup, you explicitly declare: 'this is an FAQ', 'these are the answers', 'this is the price', 'this is the author's name and credentials'. This precision reduces ambiguity and significantly improves how search engines and AI tools represent your content.
Most important schema types for UK businesses
- Organization — company name, logo, contact details, social profiles, and knowsAbout declarations for AI entity recognition
- LocalBusiness — for businesses with physical locations; includes address, hours, phone, and geographic area
- FAQPage — marks up question-and-answer pairs; enables FAQ rich results in Google Search and AI citation
- Product — price, availability, SKU, and reviews for ecommerce product pages
- Article/BlogPosting — marks up editorial content with author, publish date, and speakable sections
- BreadcrumbList — navigation hierarchy for rich result breadcrumbs
- Review/AggregateRating — star rating markup from legitimate review collections
- Event — event name, date, location, and tickets for event pages
Structured data types that generate rich results
- FAQPage — accordion-style FAQ results in Google Search; also used by AI tools for direct answer extraction
- Product — star ratings, price, availability in Google Shopping and organic results
- HowTo — step-by-step process results
- Recipe — cook time, ingredients, nutrition information in recipe search features
- Event — date, location, and ticket information in event search cards
- Review — star ratings from your own review schema
- Article/BlogPosting — article metadata in news and discover features
- LocalBusiness — map and local business information integration
Why does schema matter more in the AI era?
Schema markup (JSON-LD structured data) tells search engines and AI systems precisely what your content is and who stands behind it. For AI visibility the essentials are: one consolidated @graph per page, Organisation and named-Person nodes, FAQPage where real FAQs exist, and Article with real dates — never markup for content that is not visibly on the page.
Classic search used schema mostly for rich results — stars, FAQs, breadcrumbs in the SERP. AI engines use it differently: as ground truth for attribution. When a model assembles an answer, schema tells it which organisation published this, which person wrote it, and what the page's key entities are. Content without schema can still be cited, but content with clean schema is cheaper to verify — and engines, like people, take the cheaper path.
What does correct implementation look like?
- One @graph per page — a single JSON-LD block containing every entity, linked by stable @ids. Scattered plugin-generated blocks contradict each other and dilute the signal.
- Named Person for authorship — a real human with sameAs links, not your brand name stuffed into an author field.
- FAQPage only for visible FAQs — the questions and answers must appear on the page; invisible FAQ markup is a policy violation and a trust risk.
- Real dates — datePublished and dateModified that change only when the content actually changes.
- Validation in the build — schema checked mechanically on every deploy, not once during setup and never again.
Which schema mistakes actively hurt you?
Three patterns draw penalties or distrust. First, aggregate ratings you did not collect — marking up supplier or third-party scores as if they were your reviews is a manual-action risk. Second, markup that does not match the visible page — schema describing a different product, price or author than what a reader sees. Third, schema spam — marking up every block on the page because a plugin can, which tells engines you optimise for the markup, not the reader.
How do you prove your schema works?
Test the rendered page, not the code. View source on the live URL and confirm there is exactly one JSON-LD block, that it parses, that every @id reference resolves inside it, and that nothing in it contradicts the visible content. Then re-check after every deploy — schema decays silently when templates change, and the first symptom is usually a dropped rich result or a missing citation weeks later.
Do you need schema on every page?
You need the right schema on every page, which is mostly the same foundation — Organisation, WebSite, the page node with real dates — plus page-type extras where genuine: Article on posts, FAQPage where visible FAQs exist, Service on service pages. A page with only the foundation is fine. A page with invented extras is not. When in doubt, mark up less.
Which schema types does a typical UK business site need?
| Page | Schema types | Why |
|---|---|---|
| Homepage | Organization (or LocalBusiness subtype), WebSite | States your legal name, logo, contact points and profiles in one place. |
| Service page | Service, BreadcrumbList | Describes what you offer, who provides it and where. |
| Article or guide | Article or BlogPosting, BreadcrumbList | Identifies the author, publisher and dates. |
| Product page | Product with Offer and, where genuine, AggregateRating | Can make price, availability and reviews eligible to show in results. |
| Event or course | Event or Course | Dates, location and booking details in a form engines can read. |
Google's rich results change over time: HowTo results were withdrawn in 2023 and FAQ results in May 2026. Check Google's search gallery before building markup for a particular feature, and test pages with our free schema checker or Google's Rich Results Test.
Frequently asked questions
Google provides the Rich Results Test tool (search.google.com/test/rich-results) for validating structured data and previewing how it may appear in search results. The Schema Markup Validator (validator.schema.org) checks for schema.org compliance. Google Search Console's Rich Results section shows pages with implemented structured data and any errors in the implementation. Always validate new structured data implementations before deploying to production — invalid markup may be ignored or, in rare cases, generate a manual action.
Incorrect structured data can cause problems in two ways. First, if the structured data is misleading — marking up content as an FAQ when it is not, or marking up review stars that do not reflect genuine user reviews — Google may apply a manual action for structured data spam. Second, poorly implemented structured data (schema that references non-existent page elements, or JSON-LD with syntax errors) may be ignored, wasting the implementation effort. The most important rule: structured data must accurately reflect the visible content on the page.
It can help systems identify entities and page facts, but no AI product promises to use it, and Google says no special schema is needed for its AI features. Treat markup as accurate labelling of content that already deserves to be cited, not as a shortcut.
These are three different formats for implementing schema markup. JSON-LD is Google's preferred format — it is placed in a script tag in the page head, is easy to add without modifying the visible HTML, and is the cleanest implementation method. Microdata and RDFa are embedded directly in HTML elements, making them harder to maintain. Google supports all three formats but recommends JSON-LD. For new schema implementations, JSON-LD is the correct choice.
Schema markup does not directly improve search rankings in the traditional sense — Google has stated it is not a direct ranking factor. However, it enables rich results (star ratings, FAQ accordions, product prices) that significantly improve click-through rates, which indirectly benefits rankings. More importantly for 2026, schema markup is a primary signal that AI tools use to identify and extract specific information for AI-generated responses — making it essential for AEO and GEO performance.