Table of contents

This guide sits inside our wider guide to technical SEO. It covers what Google says markup does, the formats, a real example from our own site, the types worth adding and how to check a page.
What is schema markup and structured data?
Structured data is information about a page written in a fixed format that software can read without guessing. Schema markup is structured data that uses the schema.org vocabulary. The two terms are used interchangeably in practice.
Two pieces make it work. The first is the vocabulary: schema.org defines types of thing (an Organization, a Service, a Person) and the properties each can have (a name, a url, a telephone). The second is the format: the syntax you use to write those types and properties into the page.
Google describes structured data as "a standardized format for providing information about a page and classifying the page content". Its example is a recipe page, where markup labels the ingredients, the cooking time and the calories, so a machine does not have to work out which number is which.
What does Google say schema markup does?
Google says structured data helps it understand a page and can make the page eligible for rich results. It does not say structured data improves rankings, and it does not promise anything.
The wording in Google's introduction to structured data is that it uses structured data "to understand the content of the page, as well as to gather information about the web and the world in general, such as information about the people, books, or companies that are included in the markup". It adds that markup "can enable search results that are more engaging to users", which it calls rich results. A rich result is a search listing with extra detail, such as star ratings on a recipe.
Google's general structured data guidelines are blunt about the limits: "Google does not guarantee that your structured data will show up in search results, even if your page is marked up correctly according to the Rich Results Test." Using it "enables a feature to be present, it does not guarantee that it will be present."
That answers the question people ask most: does schema markup help SEO? It helps Google read the page accurately, and it can make the page eligible for a richer listing. Nothing in Google's documentation calls it a ranking factor, so we do not sell it as one. Treat it as groundwork that removes ambiguity about what your page says.
What are the three schema formats: JSON-LD, Microdata and RDFa?
Google supports three formats: JSON-LD, Microdata and RDFa. It recommends JSON-LD.
| Format | How it works | Where it lives |
|---|---|---|
| JSON-LD | A block of script in the page, written separately from the visible text | In a <script type="application/ld+json"> tag in the <head> or <body> |
| Microdata | Attributes added to the HTML tags that already hold your content | Mixed into the body of the page |
| RDFa | A similar set of attributes, from an HTML5 extension for linked data | Mixed into the head or body |
Google's documentation says that "all 3 formats are equally fine for Google, as long as the markup is valid and properly implemented", and that it recommends JSON-LD "as it's the easiest solution for website owners to implement and maintain at scale (in other words, less prone to user errors)".
The reason is practical. JSON-LD (JavaScript Object Notation for Linked Data) keeps the markup out of the visible text, so a designer can change a heading without breaking your data. Google can also read JSON-LD that scripts or a CMS add after the page loads. With Microdata and RDFa, the labels are woven into the page HTML, so a design edit can quietly damage them.
On WordPress, Wix or Shopify you may not edit the HTML directly. Google's guide notes that your CMS may have a settings page or plugin for it.
For the rest of this guide, "schema markup" means JSON-LD.
What does JSON-LD schema look like? A real example
A JSON-LD block is a list of named values inside curly brackets. Here is a trimmed version of the markup on our own homepage, which describes SEO Pages as an organisation. We have cut it down to the lines that matter.
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://www.seopages.co.uk/#organization",
"name": "SEO Pages",
"legalName": "SEO Pages Ltd",
"url": "https://www.seopages.co.uk",
"sameAs": [
"https://www.linkedin.com/company/seo-pages",
"https://clutch.co/profile/seo-pages",
"https://www.google.com/search?kgmid=/g/11zggns48z"
]
}
Here is what each line does:
@contexttells a reader which vocabulary the words belong to. Here it points at schema.org, sonamemeans the schema.orgnameproperty.@typesays what kind of thing this is.Organizationis the schema.org type for a company or group.@idgives the thing a permanent identifier, written as a URL with a#organizationfragment. Other markup on the site can point at this identifier to say "that same organisation". One thing gets one@id, so a reader never sees two nodes and wonders whether they are the same company.nameis the name we trade under.legalNameholds the registered name, SEO Pages Ltd.urlis the official website of the thing being described.sameAslists other pages on the web that describe the same organisation: a LinkedIn company page, a directory profile, and a link that identifies us in Google's own records. It lets a reader of the markup join the dots between those pages and this site.
The full block on our site also carries a Companies House number, the founder as a Person with their own @id, and each service with an @id of its own. The principle is the same at any size: say what the thing is, give it one identity, and point to where else it appears. Google says it "can make general use of the sameAs property", so we keep those facts correct.
Which schema types does a small business site need?
A small business site needs a handful of types: one for the business itself, one for each service, one for the people behind it, and a few for the pages. You do not need dozens.
| Type | What it describes | Where it goes |
|---|---|---|
Organization or LocalBusiness | The business: name, address, phone, website, profiles elsewhere | Homepage, plus contact and about pages |
Service | One thing you sell, with a name and a description | Each service page |
Person | The owner, founder or author | About page, and as the author on articles |
BreadcrumbList | The path from the homepage to the current page | Every page below the homepage |
Article or BlogPosting | A blog post: headline, author, dates | Each blog post |
FAQPage | Questions and answers shown on the page | Pages with a visible FAQ section |
Use LocalBusiness (or a more specific subtype such as Plumber or Electrician) when you serve customers at a place or in an area. Use Organization for a business with no local footprint. Our guide to local business schema walks through the properties a local firm should fill in and how to match them to a Google Business Profile.
Google's guidance on specificity applies here: "Try to use the most specific applicable type and property names defined by schema.org". A Plumber says more than a LocalBusiness, and a LocalBusiness says more than a Thing.
Start with the business and the services. Our schema generator produces LocalBusiness, Organization, Service and Person markup, and our FAQ schema generator covers the last row.
Does AI use schema markup?
Google says AI Overviews and AI Mode need no special structured data. Whether other AI tools read your markup is not something their makers have documented, so treat any claim that schema "gets you into ChatGPT" with caution.
Here is what Google's AI features guidance says: "There are no additional requirements to appear in AI Overviews or AI Mode, nor other special optimizations necessary." On markup it adds: "There's also no special schema.org structured data that you need to add." To be shown as a supporting link, a page "must be indexed and eligible to be shown in Google Search with a snippet", and one of the listed basics is "making sure your structured data matches the visible text on the page".
So schema is not a switch that turns AI visibility on. That is Google's position, and we agree with it.
Our own view, and it is a view rather than a claim from Google, is that markup is still worth having. It states your legal name, address, services and profiles in a form software cannot misread, so any system that reads the page starts from the right facts. An AI answer that gives a customer your old phone number costs you the call, and clean markup is a cheap way to reduce that risk.
Markup repeats what the visible text says and cannot make up for a thin page. For the wider picture, see AEO vs SEO for local businesses and how to get recommended by AI search.
What is the visible-content rule?
The rule is that your markup must describe what a visitor can see on the page. If the markup says something the page does not, Google treats it as a problem.
The guidelines say it in several places. Google tells site owners: "Don't mark up content that is not visible to readers of the page. For example, if the JSON-LD markup describes a performer, the HTML body must describe that same performer." In the introduction it goes further: "don't add structured data about information that is not visible to the user, even if the information is accurate."
Two related rules: markup "must be a true representation of the page content", and you must not mark up "irrelevant or misleading content, such as fake reviews". Before you publish, check:
- Does every name, address, phone number and price in the markup appear on the page?
- Is the markup on the page it describes, not parked on an unrelated page?
- Are the reviews and ratings real, and shown to visitors?
- Is each statement true today? Old opening hours in markup are still wrong.
- Can Googlebot reach the page? Google says not to block structured data pages with robots.txt, noindex or other access controls.
The simplest safeguard is to build the markup from the same source as the page, so the two cannot drift apart.
How can you check the schema code on a page?
You check schema by running the page through a validator, which reads the markup and reports errors. Three free tools cover it.
- Our schema validator. It finds the JSON-LD on a page and flags markup that is invalid.
- Google's Rich Results Test. It shows whether the page is eligible for Google's rich result features, and previews them where it can. Google calls it "an easy and useful tool for validating your structured data".
- The Schema.org validator. It checks your markup against the full schema.org vocabulary, including types and properties that Google does not use for rich results.
The Rich Results Test asks whether Google can use the markup for a rich result. The Schema.org validator asks whether it is valid schema.org at all. Passing one does not guarantee the other.
A clean test result is not the end. Google's guidelines warn that markup can be "incorrect in a way that the Rich Results Test was not able to catch", and that pages can break after launch "due to templating or serving issues". Re-test after a redesign, after a plugin update and after you change a template.
How do schema statements connect to entities?
Every line of schema markup is a small statement made of three parts: a subject, a property and a value. That structure is what entity SEO builds on.
Read the example above that way. The subject is the organisation with the @id ending #organization. One statement says its name is "SEO Pages". Another says its legalName is "SEO Pages Ltd". Another says it is sameAs a LinkedIn page. Each is a plain fact about one identified thing, in subject, predicate, object order.
A search engine or AI system that collects many such facts from many sources can build a picture of the business as a distinct entity, a thing with an identity, rather than a string of words that happens to appear on a page. Our guide to entity SEO explains how those facts add up and how to keep them consistent across your site and the wider web.
We found out how much this matters when we audited our own markup in October 2026. The audit turned up a shared fallback that had labelled 25 local area pages with a service name we do not sell, and one @id that carried two different names for the same service. The markup was valid. It was also wrong, and a validator would not have caught either mistake. We fixed every finding the same day and re-checked all 199 pages in the sitemap.
FAQ
Does schema markup help SEO?
It helps Google understand your page, and it can make the page eligible for rich results. Google's documentation does not describe structured data as a ranking factor, and it guarantees nothing about what appears in search. Add it because it states your facts clearly, and judge it on rich results and accuracy.
Does AI use schema markup?
Google says AI Overviews and AI Mode need no special schema, and that its normal SEO basics still apply. Other AI tools have not published how they treat markup. Our view is that accurate markup helps any system reading the page to get your facts right.
How can I check the schema code?
Paste the page address into our schema validator, Google's Rich Results Test or the Schema.org validator. Each reads the JSON-LD and reports errors. Check again after any redesign or template change.
Can you provide an example of schema markup?
The Organization block earlier in this guide is a real one, taken from our homepage. For a local firm, the shape is the same with a LocalBusiness type, an address and opening hours. Our local business schema guide has the full template.
Next step
Schema markup is a few lines of JSON-LD that say who you are and what you sell, in a form every reader of the page can use. Build the identity first, keep it true to the visible page, and test it after every change. When you are ready to write yours, generate your schema markup free.


