Structured data is a standardized code format (usually JSON-LD) added to a webpage that explicitly labels what different pieces of content mean — this is a review, this is a price, this is a recipe’s cook time — rather than leaving search engines to infer it from surrounding text.
Schema.org is the shared vocabulary most structured data follows, giving search engines a consistent way to interpret content across the entire web.
Why it matters: Structured data is what enables rich results in search — star ratings under a review, a recipe card with cook time and calories, or a job posting with salary and location visible before a click. These enhanced listings typically stand out more and can improve click-through rates.
High-value schema types to start with: - Article schema for blog posts and news content - Product schema for e-commerce, including price and availability - FAQPage schema for FAQ sections (note: Google now shows FAQ rich results only for a limited set of authoritative sites) - Organization and LocalBusiness schema for brand and location information - BreadcrumbList schema to show a page’s site hierarchy in search results
Implementation: Add JSON-LD markup inside the page’s <head> or body, then validate it using Google’s Rich Results Test before publishing. Many CMS plugins (Yoast, RankMath) generate common schema types automatically.
Structured data doesn’t directly boost rankings, but it significantly improves how a listing looks and performs in search results.
A simple JSON-LD example
JSON-LD is Google's recommended format because it sits in one script block and doesn't mix with your visible HTML. Here is a basic Article example:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Structured Data & Schema Markup for SEO Explained",
"image": "https://example.com/images/schema-guide.webp",
"datePublished": "2026-07-31",
"dateModified": "2026-10-01",
"author": { "@type": "Person", "name": "Monika Gupta" },
"publisher": { "@type": "Organization", "name": "ClicZeo" }
}
</script>An update on FAQ and HowTo rich results
In 2023 Google reduced FAQ rich results so they show only for a limited set of well-known, authoritative government and health websites, and it stopped showing HowTo rich results. For most businesses, FAQPage markup will no longer create a dropdown in search results. It is still valid schema, and clear question-and-answer content remains useful for readers and for AI systems that summarise pages, but don't add it expecting a visual change in Google.
Rules that keep your markup eligible
- Mark up only what users can see. Prices, ratings and reviews in the schema must match the visible page.
- Don't mark up content you didn't earn. Self-written reviews of your own business are not eligible for review stars.
- Use the most specific type. Use
Productrather thanThing, andLocalBusinesssubtypes such asDentistwhere they fit. - Fill in required properties. Google's documentation lists required and recommended properties for each feature.
Breaking these rules can lead to a structured data manual action, which removes rich results for the whole site.
Structured data and AI search
Schema markup helps search engines connect your content to entities: your organisation, your authors, your products. That clarity supports how your brand is understood in both classic search and AI answers. Organization markup with sameAs links to your official social profiles, and Person markup for authors, are low-effort additions that strengthen this. Read more in our guide to schema markup for AI search.
How to test and monitor
- Validate new markup in Google's Rich Results Test before publishing.
- Use the Schema Markup Validator (validator.schema.org) to check general schema.org syntax.
- After launch, check the Enhancements section in Search Console. It reports errors and warnings for each rich result type across the whole site.
Templates are where structured data usually breaks, for example when a theme update removes a field. Re-test a sample of pages after every major site change.
