Structured Data & Schema Markup for SEO

Structured data is code added to a webpage that explicitly labels what its content means — a phone number as a phone number, a review as a review, an author as a specific person — instead of leaving a search engine to infer it from surrounding text.

It's written in a shared vocabulary called schema.org, and on most modern sites it's placed on the page as JSON-LD rather than mixed into the visible HTML.

Adding structured data doesn't move your rankings by itself, and Google says so directly. What it does is make specific content eligible for the enhanced result formats — star ratings, breadcrumbs, article cards — that Google's own documentation ties to click-through-rate gains as high as 25–82% in its supporting case studies.

Key Takeaways

Structured data is not a ranking factor — Google states this directly — but it makes content eligible for rich results, which Google’s own documentation links to click-through-rate gains as high as 25–82% in supporting case studies.
JSON-LD is Google’s recommended format because it lives in a single script tag and doesn’t require marking up the visible HTML itself, unlike Microdata or RDFa.
Google significantly narrowed FAQ rich results in 2023 to mostly well-known government and health sites, and has continued pulling the feature back since — adding FAQPage markup no longer gets most sites a rich result.
The schema types worth implementing on a typical business site are Organization, WebSite, BreadcrumbList, and Article/BlogPosting — not exotic or niche types.
Structured data has to describe content that’s actually visible on the page; markup that doesn’t match what a visitor sees violates Google’s spam policies and can trigger a manual action.

What Structured Data Actually Is

Structured data describes page content using a shared vocabulary — schema.org — so that a search engine can identify specific pieces of information rather than parsing free text and guessing. A price is marked explicitly as a price, a rating as a rating, an author as a distinct Person entity.

Webpage elements each marked with a small invisible label icon showing what type of content they represent

Three formats can express this vocabulary: JSON-LD, Microdata, and RDFa. JSON-LD is a self-contained block of code, usually placed in the page’s <head>, that describes the page without touching its visible markup. Microdata and RDFa are embedded directly as attributes on the HTML elements they describe, which means the markup breaks more easily whenever the visible design changes.

Why JSON-LD Is the Format Worth Using

Google explicitly recommends JSON-LD, and it’s what most modern CMS and framework tooling generates by default. Because it lives in one script tag, a template or redesign change can update it once, in one place, without touching the markup scattered through the visible page.

How Search Engines Use It to Understand Your Content

Search engines build an understanding of a page from more than its words — they try to identify the entities on it (a business, a person, a product) and how those entities relate to each other. Structured data makes those relationships explicit instead of inferred: this article was written by this specific author, this page belongs to this specific organization, this breadcrumb trail is this page’s actual position in the site.

Central webpage icon radiating connections outward to separate person, organization, and article entity nodes

That disambiguation matters most when names are ambiguous or shared. A generic "About" page doesn’t tell a search engine much on its own; an Organization entity with a name, logo, and sameAs links to verified profiles does.

Structured Data Has to Match What’s Visible

Markup that describes content a visitor can’t actually see on the page — a rating that isn’t shown, a price that isn’t listed — is treated as misleading. Google’s spam policies cover this directly, and mismatched structured data is one of the more common reasons a site loses rich-result eligibility or receives a manual action.

Common Schema Types Worth Implementing

Most of the practical benefit comes from a small set of schema types, not from covering every option schema.org offers.

Browser search results screen showing one enhanced result with a star rating and thumbnail next to a plain text-only result

Organization and WebSite

Placed sitewide, these identify the business itself — name, logo, social profiles, and site search behavior — and anchor every other entity on the site back to a single, consistent source.

Article or BlogPosting

Used on blog and editorial content, this ties a specific author, publish date, and headline to the entity Google displays in article-style search results and Google Discover.

BreadcrumbList

This maps a page’s actual position in the site hierarchy, which Google can display directly in the search result instead of the raw URL — useful on any site more than one level deep.

FAQPage — With a Real Caveat

FAQPage markup still helps describe the content on the page, but it stopped being a reliable path to a rich result after Google's 2023 update: FAQ rich results are now shown mainly for well-known, authoritative government and health websites, and Google has continued narrowing the feature since. Add it if the content genuinely is FAQ-formatted — don't add it chasing a rich snippet that most sites are no longer eligible for.

What Structured Data Can’t Do

It can't substitute for weak content, and it doesn't guarantee a rich result even when a page is eligible — Google decides at query time whether to display one. It also isn't a ranking signal on its own; its value is entirely in what it makes eligible and how search engines interpret the content around it.

Getting Structured Data Right

Use JSON-LD for anything new — not Microdata or RDFa.
Validate markup with a structured data testing tool before shipping a template change, not after.
Keep structured data in sync with visible content; update both together whenever a page changes.
Don’t add schema types that don’t genuinely apply to the page just because they’re available in the vocabulary.
Re-check structured data after a redesign or CMS migration — template changes are the most common way markup silently breaks or duplicates.

How to Validate Structured Data

Google’s Rich Results Test checks a live URL or a code snippet against the specific schema types Google Search actually uses for rich results. The independent Schema Markup Validator at validator.schema.org checks broader schema.org compliance, which is useful for types the Rich Results Test doesn’t evaluate. For an already-live site, the Enhancements reports in Search Console surface sitewide structured data errors and warnings without checking pages one at a time.

Code validation tool on a monitor showing a large green checkmark confirming valid markup

A Simpler Way to Keep Structured Data Correct

Structured data doesn't have to be maintained by hand on every page. Payload CMS's block-based content model can generate Article, Organization, and BreadcrumbList schema automatically from the same data that already powers the page, so there’s no separate markup to keep in sync. It’s one of the reasons structured data tends to come up alongside page speed when a team is evaluating what actually changes when they move off WordPress.

Frequently Asked Questions

Does adding structured data improve my Google rankings?

Not directly — Google states structured data is not a ranking factor. What it can do is make content eligible for rich results, which tend to improve click-through rate rather than ranking position itself.

Do I still need FAQPage schema?

Rich results from FAQPage markup are now largely limited to well-known government and health sites following Google’s 2023 change, and the feature has been scaled back further since. The markup itself isn’t harmful to keep, but don’t add it expecting a guaranteed rich snippet.

What's the difference between JSON-LD, Microdata, and RDFa?

All three describe the same schema.org vocabulary in different syntaxes. JSON-LD sits in a separate script tag and doesn’t touch the visible HTML; Microdata and RDFa are embedded as attributes directly inside the HTML elements they describe. Google recommends JSON-LD.

Can structured data get my site penalized?

Yes, if it describes content that isn't actually visible on the page or is used to mislead. Google's spam policies cover this directly, and mismatched markup can lead to a manual action.

How do I check if my structured data is working?

Run individual URLs through Google’s Rich Results Test, and check the Enhancements reports in Search Console for sitewide errors and warnings.

Which schema type should a small business site start with?

Organization and WebSite on the homepage, plus Article or BlogPosting on blog content and BreadcrumbList sitewide. Those four cover most of the practical benefit before anything more specialized is worth considering.

Want Your Site's Technical SEO Handled Properly?

From structured data to page speed, see how we approach the technical side of SEO.

Sources and Further Reading

Structured data fundamentals: Google Search Central — Understand how structured data works. Full vocabulary reference: schema.org. Current FAQ rich-result eligibility: Google Search Central — FAQPage structured data.

How Structured Data Helps Search Engines Understand Your Website