Schema Markup
Schema markup is structured data code added to a webpage that helps search engines understand what the page is about and how its content is organized.
Start here
- Start with one page that has clear structured content (product, review, event, FAQ).
- Use JSON-LD format — it's Google's recommendation and easiest to maintain.
- Always test your schema with the Rich Results Test before and after deployment.
- Match schema to visible page content — misleading markup can lead to penalties.
- Schema improves click-through rates, not rankings directly — set expectations accordingly.
I remember the first time I added schema markup to a client's recipe page — it felt like magic when the star ratings appeared in search results. But I also learned the hard way that getting it wrong can do more harm than good.
What I'd do first
- Pick one page — don't try to schema-ify your whole site at once. Start with a page that has clear, structured content: a product page, a review, an event, or an FAQ.
- Choose the right type — go to Schema.org and find the type that matches your content. For a product page, use
Product. For a recipe, useRecipe. Don't guess. - Write JSON-LD — it's the format Google recommends. You can hand-code it or use a generator like Google's Structured Data Markup Helper.
- Test before deploying — paste your code into the Rich Results Test. Fix any errors or warnings.
- Add it to your page — embed the JSON-LD script in the
<head>or<body>of your HTML. Then test again after it's live.
Plain-English take
Think of schema markup as a translator for search engines. Your page might say "This movie is 4.5 stars" in plain text, but a search engine doesn't automatically know that's a rating. Schema markup labels it explicitly: <span itemprop="ratingValue">4.5</span>. That clarity can unlock rich results — those eye-catching snippets with stars, prices, or event dates that make people more likely to click.
It's not a magic ranking boost. Google has said it's not a direct ranking factor. But it can improve your click-through rate, which can indirectly help. And for certain content types (like recipes or events), it's almost table stakes now.
When it actually matters
- Product pages — show price, availability, and reviews in search results.
- Local businesses — use LocalBusiness schema to display hours, address, and phone number.
- Events — let users see dates and locations directly in the SERP.
- FAQs — FAQ schema can create an expandable accordion in search results.
- Recipes — display cook time, calories, and star ratings.
- Articles — Article schema can help Google understand authorship and publication date.
If your content doesn't fit one of these patterns, schema might not move the needle much. Don't force it.
What I got wrong
- I thought schema would boost rankings directly. It doesn't. It can improve click-through rates, which might help over time, but it's not a ranking signal.
- I once used schema that didn't match the visible content. I added Review schema to a page that had no actual reviews. Google eventually flagged it, and I had to clean it up. Always match schema to what's on the page.
- I skipped testing. I deployed schema without running it through the validator. Turns out I had a missing required field. The rich result never showed. Now I test every time.
- I treated schema as a substitute for good content. It's not. Schema helps search engines understand your content, but if the content itself is weak, schema won't save you.
Next step
Sources
Primary documentation is linked directly. Anything commercial is marked nofollow.
- Google Search Central — Most authoritative source for how Google uses structured data and rich results.
- Schema.org — Official vocabulary reference for schema types and properties.
- Google Rich Results Test — Primary testing tool for checking rich result eligibility and implementation.
- Google Structured Data Testing / Schema Markup Validator — Useful validator for checking structured data syntax and schema conformance.
Notes from Callum Bennett.