Schema Markup: JSON-LD, Validators and the Rich Results Left in 2026

Schema markup is a block of code that describes what a page contains in a vocabulary search engines understand: this is a product with a price, this is an event on a date, this organisation has this logo. Visitors never see it, yet it shapes how the page can appear in Google. The list of rich results it unlocks has also shrunk noticeably since 2023, so it pays to know what still works before writing a line of code.

What is schema markup?

Schema markup is structured data written in the schema.org vocabulary and added to a page's HTML, so that search engines can read facts about the page directly instead of inferring them from text and layout.

Schema.org is an open, community-maintained vocabulary used by the major search engines. It defines types such as Organization, Product, Article and Event, and properties for each one: name, price, datePublished, startDate and so on. Structured data is the general idea; schema markup is the most common way of expressing it on the web.

How schema helps search engines understand content

A crawler can usually work out that a number beside a currency sign is a price. Markup removes the guesswork: it states that 49.00 is the price, GBP is the currency and the item is in stock. The same applies to event dates, cooking times, salary ranges and review ratings, where the details are the whole point of the page.

Markup also ties a page to an entity. Organization data can connect your site to your legal name, logo and official profiles, which helps search engines keep facts about your business consistent.

JSON-LD, Microdata and RDFa

Google reads three formats. JSON-LD is a separate script block; Microdata and RDFa are attributes woven into the visible HTML. Google says all three work if the markup is valid, but recommends JSON-LD because it is the easiest to add and maintain at scale. A minimal schema markup example for a company looks like this:

<script type="application/ld+json"> {"@context": "https://schema.org", "@type": "Organization", "name": "Example Ltd", "url": "https://example.com", "logo": "https://example.com/logo.png"} </script>

Which rich results still exist in 2026?

Google's search gallery currently lists about two dozen structured data features. Since 2023 it has removed HowTo, sitelinks search box, FAQ and several niche types, so check the documentation changelog before investing in a type.

The table summarises the state of Google's structured data gallery as of November 2026. Other search engines and applications may still read types Google no longer displays, so schema.org validity and Google eligibility are separate questions.

Markup for a retired feature does not need to be stripped out in a panic, but it should no longer drive new work. Spend the effort on types that describe your main business entities and still have a visible feature behind them.

Why does schema matter for SEO?

Schema markup is not a ranking boost on its own. Its value for SEO comes from eligibility for rich results, clearer entity information and consistent data that other systems, including AI features, can rely on.

Rich results and click-through

Knowing how to use schema markup for SEO starts with realistic expectations. A result showing price, availability, rating or event date answers part of the query before the click, which can make it more useful than a plain blue link. Google never guarantees that valid markup will be displayed: its systems decide per query. Measure the effect in Search Console by comparing pages with and without a given search appearance, rather than relying on industry averages.

Entities, knowledge panels and AI features

Organization and LocalBusiness data help Google connect your site with your brand details. For AI Overviews and AI Mode, Google states there is no special schema to add; what matters is that existing structured data matches the visible text. The Speakable type exists for news read aloud by Google Assistant, but for most sites voice visibility depends on clear, well-structured content rather than markup.

How to add schema markup to a website

To add schema markup, choose the type that matches the page's main content, write JSON-LD with all required properties, place it in the page's HTML and confirm that every value matches what visitors see.

1. Identify the page's main entity: a product, an article, an event, the business itself.
2. Open Google's documentation for that feature and note the required and recommended properties.
3. Write the JSON-LD and fill it from the same data that renders the page.
4. Place the script in the head or body; Google reads both, and it can also read JSON-LD injected with JavaScript.
5. Test the page before release, then monitor it after release.

Manual code, plugins or templates

Hand-written markup suits a handful of static pages. CMS plugins cover common types on WordPress and similar platforms, but they often add generic markup to every page and may lag behind Google's changes. On catalogues and large sites the most reliable route is template-level generation: the product template outputs price and availability from the same database fields as the visible page, so the two cannot drift apart.

Rules that keep markup eligible

• Mark up only content that is visible on the page.
• Put markup on the page it describes, not site-wide.
• Do not invent ratings or reviews. Pages where a business controls reviews about itself are not eligible for review stars with LocalBusiness or Organization markup.
• Misleading markup can lead to a manual action that removes rich result eligibility.

How to test and validate structured data

Use two validators: Google's Rich Results Test, which checks eligibility for Google features, and the Schema Markup Validator, which checks general schema.org syntax. After launch, Search Console reports show errors at scale.

• Rich Results Test shows which Google features a URL or code snippet qualifies for, with errors and warnings.
• Schema Markup Validator (validator.schema.org) checks any schema.org type, including ones Google does not use.
• URL Inspection in Search Console confirms that Google found the markup on the indexed version.
• Rich result reports in Search Console group valid and invalid items across the site after release.

Errors block a feature; warnings flag missing recommended properties. Fix errors first, then add recommended properties where you hold genuine data.

Using AI tools and generators

Generators and AI assistants are useful for a first draft of JSON-LD, but they cannot know whether a value is true on your page. Treat their output as a draft that still needs validation and a content check.

Where AI and generators help

Form-based generators produce clean code for standard types in minutes. Language models can map an existing page to a schema type, suggest properties and convert Microdata to JSON-LD. Both save time on repetitive work.

Where they go wrong

AI tools can add properties that do not exist, use deprecated types or fill fields with plausible but invented values, such as a rating the page does not show. That last mistake breaks Google's guidelines. Always validate the code and compare every value with the page.

Keeping schema accurate on large sites

On sites with thousands of pages, automate the checking rather than the writing. Generate markup in templates, run a validator against sample URLs after each release, and watch Search Console reports for spikes in invalid items. Schema that silently breaks after a CMS update is a common finding in a technical SEO audit.

Structured data for local SEO and small websites

Small websites need only a few types: Organization or LocalBusiness, Article or BlogPosting for posts, Breadcrumb and Product where relevant. Accurate basics beat a long list of rarely displayed types.

For a local business, LocalBusiness markup should carry the name, address, phone number, opening hours and URL exactly as they appear on the site and in your Google Business Profile. Inconsistent details across these sources create doubt rather than clarity.

Update the markup whenever the underlying facts change: prices, stock, opening hours, event dates. Review it after redesigns and CMS updates, and check Google's changelog a few times a year, because features are retired with only a short notice period.

If you want structured data built into your templates and checked as part of a wider site review, QIO handles it within its technical SEO service.

Sources

• Introduction to structured data markup in Google Search | Google Search Central
• Structured data markup that Google Search supports | Google Search Central
• Latest Google Search documentation updates | Google Search Central
• General structured data guidelines | Google Search Central
• AI features and your website | Google Search Central