Schema
Schema is a standardized vocabulary for adding structured data to web pages so search engines can better understand page content and qualify it for rich results.
Start here
- - Start with the most relevant schema type for your page (e.g. - Article for blog posts, Product for e-commerce).
- Use JSON-LD format — it's Google's preferred method and easiest to maintain.
- Validate your markup with Google's Rich Results Test before deploying.
- Only mark up visible content — don't hide things in schema that aren't on the page.
- Keep it accurate and up-to-date; stale schema can hurt more than help.
I used to think schema was optional fluff until I saw a client's click-through rate jump 20% after adding it to their product pages.
What I'd do first
- Pick the schema type that matches your page's main purpose. For a blog post, use Article. For a product, use Product. Don't overcomplicate it.
- Write your schema in JSON-LD. It's a separate script block, so you won't mess up your HTML. Google prefers it, and it's easier to update.
- Run every new schema through Google's Rich Results Test before you push it live. It'll catch typos and missing required fields.
- Only mark up what's visible on the page. If you don't show a price, don't include it in schema. Google checks for consistency.
- Keep a log of your schema versions. When you update a page, update the schema too. Stale data can trigger manual actions.
Plain-English take
Schema is like adding labels to your website's content so search engines don't have to guess. Instead of reading a page and trying to figure out if it's a recipe or a review, you tell them explicitly using a standard vocabulary called Schema.org. Think of it as a cheat sheet for bots. You write a small block of code (usually JSON-LD) that says "This page is a recipe, it has these ingredients, this cooking time, and these ratings." Then Google can show that info directly in search results. It's not magic — it's just making your content machine-readable.
How it shows up
When you add schema correctly, your page can appear with extra features in search results: star ratings, prices, event dates, FAQ dropdowns, breadcrumbs, and more. For example, a recipe page with Recipe schema can show cooking time and calorie count right in the snippet. A local business with LocalBusiness schema can display hours and reviews. These rich results stand out and get more clicks. But not every schema type guarantees a rich result — Google decides based on quality and relevance. I've seen perfectly valid schema fail to trigger anything because the page content was thin.
Tradeoffs
Schema isn't a ranking factor, but it can improve click-through rates. However, implementing it wrong can lead to penalties. I've had to clean up schema that was marking up hidden content — Google can see that and may issue a manual action. Also, maintaining schema for dynamic content can be a pain. If your product prices change frequently, you need to update the schema every time. I've seen teams spend hours on schema that never triggers rich results because Google's algorithms are picky. Is it worth it? For most sites, yes — the potential CTR boost outweighs the effort. But don't expect miracles overnight.
What I got wrong
Early on, I marked up content that wasn't visible on the page, like adding Product schema for a page that only had a description but no price or availability. Google's guidelines say you should only mark up what users can see. Also, I used Microdata instead of JSON-LD at first, which made updates harder — I had to dig through HTML to change values. Another mistake: I assumed more schema was better. I once added multiple schema types to a single page (Article, BlogPosting, and WebPage) and confused Google. Stick to one primary type per page.
Next step
Quick answers
Does schema improve rankings?
Not directly. Schema isn't a ranking factor, but it can boost click-through rates by making your listing more attractive. Higher CTR can indirectly influence rankings over time.
What's the best format for schema?
JSON-LD. Google recommends it, and it's easier to maintain than Microdata or RDFa. You can add it to the <head> or body without touching your HTML structure.
Sources
Primary documentation is linked directly. Anything commercial is marked nofollow.
- Google Search Central — Primary source for Google's definition, supported formats, and structured data guidance.
- Schema.org — Official vocabulary reference for schema types and properties.
- Google Search Central - Rich results test — Official validation tool for checking structured data eligibility and errors.
Notes from Callum Bennett.