Website monitoring · No. 12
Schema.org markup check
In short
Schema.org markup is structured data in your page code that tells search engines what a page contains: a product with a price, a business with an address, an article, breadcrumbs. Google uses it to understand content and show rich results with prices, ratings, and availability. Broken markup, or markup that contradicts the visible text, loses those benefits.
Contents
What is Schema.org markup?
Schema.org markup (also called schema markup or structured data) describes a page in a language machines understand. A person can see at a glance that a page shows a product at a certain price. A search engine has to be told explicitly: “This is a Product; here’s its name, price, currency, and availability.”
“Structured data is a standardized format for providing information about a page and classifying the page content.”
The vocabulary of types and properties is maintained by the Schema.org project, founded by Google, Microsoft, Yahoo, and Yandex (schema.org). You can write markup in JSON-LD, Microdata, or RDFa. Google recommends JSON-LD: it’s a separate <script type="application/ld+json"> block that doesn’t mix with your HTML layout, so it’s easier to maintain.
| Type | For which pages | What it can get you in Google |
|---|---|---|
Organization | Home page, About page | Logo, name, address, contact details — in the knowledge panel and other features |
LocalBusiness | Website of a venue or store with a physical address | Opening hours, ratings, directions in the knowledge panel |
Product | Product page | Price, availability, and review ratings right in search results |
BreadcrumbList | Inner pages | The page’s position in your website structure instead of a long URL |
WebSite | Home page | Your preferred site name in search results (Google may choose a different one) |
Article | Articles, news, blog posts | The article headline, date, and image |
For the full list of what Google supports, see the search gallery of structured data features.
Why monitor your Schema.org markup?
Markup works on two levels at once. First, it helps Google understand the page:
“Google uses structured data that it finds on the web 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.”
Second, it unlocks rich results — more eye-catching snippets in search. For products, according to Google’s documentation, that means “price, availability, review ratings, shipping information, and more right in search results” (Google documentation on product structured data).
Here’s what happens when something goes wrong with your markup:
- The markup disappears or breaks. The page stays in search but loses prices, stars, and breadcrumbs in its snippet — and becomes less noticeable next to competitors.
- The markup doesn’t match the page. Google requires structured data to be “a true representation of the page content” and says, “Don’t mark up content that is not visible to readers of the page” (Google’s general guidelines).
- Manual actions. Breaking the rules can lead to a manual action: the page loses eligibility for rich results, although this doesn’t affect how it ranks in regular web search.
Keep the reverse in mind too: even flawless markup doesn’t guarantee rich results. Google says plainly that it doesn’t guarantee your structured data will show up in search results, even if your page is marked up correctly.
Visibility in AI answers
How does Schema.org markup affect your visibility in AI answers?
Schema.org markup helps AI systems confirm facts about a page and connect entities correctly, but it isn’t a requirement for AI answers. Google’s AI Overviews and AI Mode don’t need any special markup — Google says so directly:
“You don’t need to create new machine readable files, AI text files, or markup to appear in these features. There’s also no special schema.org structured data that you need to add.”
At the same time, in the same document, among the SEO fundamentals that still help with AI answers, Google lists “Making sure your structured data matches the visible text on the page.” In other words, what matters to Google for AI answers isn’t some special markup type — it’s markup that’s consistent with the page.
In GEO (generative engine optimization), structured data is valuable because it confirms facts and connects entities. How this works in practice is our explanation, not Google’s position:
- No ambiguity. Language models work with entities and the relationships between them: a company, a product, an author, a city. Markup spells out the page’s context — that Jaguar here is a car brand, not an animal, and that the person mentioned is the article’s author, not its subject — so the model doesn’t have to guess.
- Compact facts. Instead of parsing all the HTML with its menus, banners, and scripts, a system can take a few lines of JSON-LD with the name, price, and date. That saves token budget — the amount of text a model processes at once.
- Fewer made-up answers. When prices, authors, dates, or how-to steps are structured, there’s less risk that a model mixes them up or “hallucinates” — gives a plausible but wrong answer.
- Data for product comparisons.
Productmarkup fields — price (price), availability (availability), rating (aggregateRating), GTIN — provide ready-made material for product lists and comparisons in AI answers.
There are still few independent measurements of this effect. The marketing agency Stackmatix estimates that content with proper markup is 2.5 times more likely to appear in AI answers, but it doesn’t share the methodology behind that number (Stackmatix). So it’s the agency’s estimate, not a proven fact.
The practical takeaway: Schema.org markup is a way to improve visibility, not a button that gets you into AI answers or a guarantee of rankings. Accurate markup that matches the text helps systems understand what the page is about, while markup with an outdated price or a nonexistent rating goes against Google’s guidelines — for both regular search and AI features.
Why does Schema.org markup break?
Markup rarely breaks on its own — it usually gets caught up in other changes to the website:
- A theme or SEO plugin update. The new template stops outputting product markup or outputs it with a different set of properties.
- Two sources of markup. The theme and a plugin both add their own
OrganizationorProductblocks with different data. - Broken JSON. Quotation marks in a product name, an extra comma, or a truncated block make the entire JSON-LD block unreadable: the search engine can’t parse a single property from it.
- A mismatch with the visible text. The price or availability on the page was updated, but the markup still has the old values because they come from a different field.
- A move to a new CMS. The templates were rewritten, and the markup was forgotten.
- Manual template edits. Someone removed an “unnecessary” script from the
<head>without realizing it was JSON-LD.
How do you spot a Schema.org markup problem?
Markup isn’t visible on the page, so you usually find out about problems from search results or Search Console:
| What you see | Possible cause | What to do |
|---|---|---|
| Product prices and stars disappeared from search results | A template update removed the Product markup | Check the page in the Rich Results Test and restore the markup |
| The Rich Results Test reports a syntax error | Broken JSON-LD | Find and fix the error in the template that generates the block |
| Search results show a different price than your website | The markup pulls the price from a different field | Tie the markup to the same value visitors see |
The page has two different Organization blocks | Both the theme and a plugin output markup | Turn off one of the sources |
| A manual action notice in Search Console | The markup doesn’t match the content or is misleading | Bring the markup in line with the page and request a review |
How to check Schema.org markup yourself
There are two public tools for this, with different purposes. Google describes the Rich Results Test as “The official Google tool for testing your structured data to see which Google rich results can be generated.” The Schema Markup Validator checks your markup against the Schema.org vocabulary “without Google feature specific warnings” (Google documentation).
- Open the Rich Results Test, paste in the page URL, and see which markup types were found, whether there are errors, and which rich results the page is eligible for.
- Check the same URL in the Schema Markup Validator — it shows all Schema.org types, including the ones Google doesn’t use for rich results.
- Compare the values in the markup with what visitors see: name, price, currency, availability, rating, address.
- View the page source (
Ctrl+U) and search forapplication/ld+jsonto make sure there’s one markup block, not several conflicting ones. - In Search Console, review the rich result reports: Google recommends monitoring them after deployment to keep an eye on the validity of the markup on your pages.
- Or use the FullCheckApp “Schema.org markup check” and get the results in a clear visual format.
If you chose the last option, you’ve already made the right call: the check runs automatically, and you’ll be the first to know about any warning or critical issue.
What FullCheckApp checks
Every day, FullCheckApp checks your Schema.org markup: which types are on the page and whether the markup is valid. FullCheckApp looks at your website from the outside, the way a regular visitor does, so there’s nothing to install.
- When. Once a day, at the time you choose, in your time zone.
- Where. Your home page and up to 10 inner pages per website; the report shows exactly which page has the problem.
- How it’s flagged. Green means OK, yellow means a warning, and red means critical. You can set the severity level separately for each website.
- How you’ll know. After each check, you get an email report, and critical issues are also sent to Telegram.
Valid markup: WebSite, Store, LocalBusiness
The first check records a baseline, and after that FullCheckApp compares your pages every day. This check looks at the markup the way any visitor receives it. How Google sees and indexes these pages is shown by the Google page indexing check, and the technical page tags are covered in the page SEO tags check article.
FAQ
Which is better: JSON-LD, Microdata, or RDFa?
Google supports all three formats but recommends JSON-LD if your website setup allows it. JSON-LD is written as a separate script block and doesn’t mix with your HTML layout, so it’s easier to add, test, and maintain. For search, it matters more that the markup is valid and matches the page than which format you choose.
Does schema markup guarantee stars and prices in Google results?
No. Google says plainly that it doesn’t guarantee structured data will show up in search results, even if the Rich Results Test says the markup is valid. Markup only makes a page eligible for rich results; Google’s algorithms decide whether to show them based on the query and other factors.
Do I need special markup to appear in AI Overviews?
No. According to Google, AI Overviews and AI Mode don’t require any new markup or special schema.org structured data, although Google recommends that your structured data match the visible text on the page. Accurate, up-to-date Schema.org markup helps AI systems understand the facts about a page without ambiguity. It’s a way to improve visibility, not a guarantee of appearing in AI answers or ranking high.
What’s the difference between the Rich Results Test and the Schema Markup Validator?
The Rich Results Test is a Google tool: it shows which rich results Google can generate for a page and checks Google’s own requirements. The Schema Markup Validator checks your markup against the Schema.org vocabulary in general, without Google-specific warnings. It’s worth checking your page in both.
Can I mark up data that isn’t on the page?
No. Under Google’s guidelines, structured data must be a true representation of the page content, and you can’t mark up content that visitors can’t see. A violation can lead to a manual action that makes the page ineligible for rich results. According to Google, it doesn’t affect rankings in regular web search.
Sources
- Google Search Central — Introduction to structured data markup in Google Searchdevelopers.google.com/search/docs/appearance/structured-data/intro-structured-data
- Google Search Central — General structured data guidelinesdevelopers.google.com/search/docs/appearance/structured-data/sd-policies
- Google Search Central — Schema Markup Testing Tooldevelopers.google.com/search/docs/appearance/structured-data
- Google Search Central — Structured data markup that Google Search supportsdevelopers.google.com/search/docs/appearance/structured-data/search-gallery
- Google Search Central — Product structured datadevelopers.google.com/search/docs/appearance/structured-data/product
- Google Search Central — AI features and your websitedevelopers.google.com/search/docs/appearance/ai-features
- Schema.org — Aboutschema.org/docs/about.html
- Stackmatix — Structured Data AI Search: Schema Markup Guide (2026), agency estimatewww.stackmatix.com/blog/structured-data-ai-search
Check your website
Add your website address — the first check runs right away, and you’ll see the status of every item in this article.
Check for free