What this guide will help you do
Help search engines understand a page with valid structured data that accurately reflects what visitors can see.
Key takeaways
- Choose schema because it describes the page, not because you want a larger result.
- JSON-LD is usually easiest to maintain, but the visible page must support every claim.
- Valid markup makes a page eligible for features; it does not guarantee that Google will show them.
What structured data can and cannot do
Structured data gives machines explicit labels for entities and relationships already present on a page. It can identify an article's author and dates, a product's offer, or a breadcrumb trail. It is a translation layer, not hidden content.
Correct markup may make a page eligible for supported search features, but eligibility is not a promise. Search systems still consider page quality, relevance, policies, device, location, and the query itself.
Choose the narrowest accurate type
Start with Google's Search Gallery and confirm the feature is supported. Use Article for a real article, Product for a specific purchasable product, and LocalBusiness for an actual business location. Do not label a general service page as a product merely to add stars or prices.
Connect related entities rather than publishing unrelated blocks. An Article can reference its author and publisher; a WebPage can include BreadcrumbList. Give stable entities consistent URLs and names across pages.
Write and validate JSON-LD
Place JSON-LD in a script element with the application/ld+json type. Generate dynamic values from the same trusted data used in the visible page so titles, dates, prices, availability, and URLs cannot drift apart.
Test the rendered public URL, not only a copied snippet. Use the Rich Results Test for Google-supported features and Schema.org's validator for broader vocabulary. Also parse the JSON during automated tests so a stray comma cannot break every page using a template.
Maintain markup after launch
Watch Search Console enhancement reports and inspect examples, but confirm issues on the live page before changing code. Some warnings describe optional properties; errors generally prevent eligibility.
Revalidate when templates, pricing, review systems, authorship, or URL structures change. Remove markup when visible content is removed. Accurate modest markup is more trustworthy than an elaborate graph that the page cannot support.
A practical next-step checklist
- Identify the page's real primary entity.
- Select a Google-supported type when relevant.
- Generate markup from the same source as visible content.
- Validate the rendered page and monitor Search Console.
When you make a technical change, test a small group of representative URLs first. Then run the free SEO audit to catch broken links, metadata gaps, crawl signals, and page-level regressions before applying the change across the whole site.
Frequently asked questions
Does schema markup directly improve rankings?
There is no guaranteed ranking boost. Accurate markup can improve understanding and eligibility for supported search features.
Is JSON-LD better than microdata?
Google supports multiple formats, but JSON-LD is often easier to generate and maintain because it is separate from presentation markup.
Can I add review stars to any page?
No. Review markup must follow the feature's eligibility and content policies and accurately represent visible, genuine review information.
Primary references
Use these first-party references to confirm details that may change after this guide is published: