SEO Schema
SEO schema is structured data you add to your page's code to help search engines understand what's actually there—not just guess from keywords.
Start here
- Start with one page type that matters most.
- Use JSON-LD and test with Google's Rich Results Test.
- Only mark up visible content.
- Schema helps understanding, not rankings.
- Measure results before scaling.
I used to think schema was a ranking hack. It's not. But it's still worth doing right.
What I'd do first
- Pick one page type that matters most. For an e-commerce site, that's probably a product page. For a blog, it's an article. Start there, not everywhere.
- Write the JSON-LD manually or use a plugin. I prefer manual for control, but plugins like Yoast or Rank Math work fine for beginners.
- Test with Google's Rich Results Test before you publish. It'll catch missing properties or wrong types.
- Only mark up content that's actually visible on the page. Don't add a review schema if there are no reviews.
- Check Search Console after a few weeks to see if any rich results are showing up.
Plain-English take
Schema is like giving search engines a cheat sheet for your page. Instead of them guessing what's a headline, what's a price, or who wrote the article, you tell them explicitly. It's a small bit of code—usually JSON-LD in a script tag—that sits in your page's HTML. It doesn't change how your page looks to visitors, but it can change how it appears in search results. Think star ratings, recipe timers, or FAQ dropdowns. That's schema at work.
How it shows up
When schema works, your page might get a rich result in Google. For example, a recipe page with correct schema can show a photo, cook time, and star rating right in the SERP. A product page might show price and availability. An FAQ page might show expandable questions. But here's the thing: Google doesn't guarantee rich results just because you added schema. It's a signal, not a promise. I've had pages with perfect schema that never got a rich result, and pages with sloppy markup that did. It's frustrating, but that's the reality.
Tradeoffs
The biggest tradeoff is time vs. payoff. Adding schema takes effort—especially if you're doing it manually for hundreds of pages. And the payoff isn't guaranteed. You might spend an afternoon marking up a product catalog and see zero change in traffic. On the other hand, when it works, it can boost click-through rates noticeably. I've seen a 10-20% lift on some pages after getting a rich result. But I've also wasted hours on schema that never triggered anything. My advice: start small, measure, and scale only if you see results.
What I got wrong
Early on, I added the same schema to every page on a site—like a blanket Article markup. Google didn't like that. It's called 'over-markup' and it can get you ignored or even penalized. Another mistake: I marked up content that wasn't on the page. For example, adding review schema to a product page that had no reviews. Google's guidelines are clear: only mark up what's visible. I also assumed schema would boost rankings. It doesn't. It can improve click-through rates, but not rankings directly. That was a hard lesson.
Next step
Quick answers
Does schema guarantee rich results?
No. It only qualifies your page for them. Google decides if and when to show them based on quality and relevance.
Can I use schema on every page?
You can, but you shouldn't. Only add schema that matches the actual content of that page. Site-wide schema for a specific type is a common mistake.
Sources
Primary documentation is linked directly. Anything commercial is marked nofollow.
- Google Search Central: Intro to Structured Data — Google's official documentation on how structured data works and when rich results appear.
- Schema.org — The canonical vocabulary reference for all schema types and properties.
- Google Rich Results Test — The official tool to validate your markup before and after launch.
Notes from Callum Bennett.