Schema Markup for Beginners

Schema Markup for Beginners

Schema markup (also called structured data) is code you add to a webpage to help search engines understand what the page is about.

For example, instead of Google seeing:

“Samsung Galaxy S25 — ₹74,999 — In stock”

schema markup tells Google explicitly:

• Product name → Samsung Galaxy S25
• Price → ₹74,999
• Currency → INR
• Availability → In stock
• Brand → Samsung
• Rating → 4.5

1. Why use Schema Markup?

Schema can help search engines understand your content and may make your search result eligible for rich results, such as:

• ⭐ Product ratings
• 💰 Product prices
• 📦 Availability
• 🍳 Recipe information
• 📅 Events
• ❓ FAQ information
• 📰 Article information
• 🏢 Organization details
• 🗺️ Breadcrumbs

Important: Schema does not guarantee that Google will display a rich result.

2. The most common format: JSON-LD

For beginners, JSON-LD is usually the easiest format.

Example for a simple article:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Schema Markup for Beginners",
  "author": {
    "@type": "Person",
    "name": "John Smith"
  },
  "datePublished": "2026-09-07"
}
</script>

You normally put this inside the <head> of the HTML page, although JSON-LD can also be placed in the body.

3. Understanding the basic structure

The important properties are:

{
  "@context": "https://schema.org",
  "@type": "Product"
}

@context tells search engines that you’re using Schema.org vocabulary.

@type tells search engines what the entity is.

Examples:

Product
Article
Organization
Person
Recipe
Event
LocalBusiness
BreadcrumbList
Review

4. Example: Product Schema

For an ecommerce website:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Example Smartphone",
  "image": [
    "https://example.com/images/phone.jpg"
  ],
  "description": "Example smartphone with 256GB storage.",
  "brand": {
    "@type": "Brand",
    "name": "Example Brand"
  },
  "offers": {
    "@type": "Offer",
    "price": "49999",
    "priceCurrency": "INR",
    "availability": "https://schema.org/InStock"
  }
}
</script>

This is particularly useful for PrestaShop, WooCommerce, Shopify, etc.

5. Product + Review + Offer

A more complete ecommerce schema might contain:

Product
 ├── name
 ├── image
 ├── description
 ├── brand
 ├── sku
 ├── aggregateRating
 ├── review
 └── offers
      ├── price
      ├── priceCurrency
      └── availability

For example:

"aggregateRating": {
  "@type": "AggregateRating",
  "ratingValue": "4.5",
  "reviewCount": "128"
}

Only use ratings/reviews that actually exist on the page. Don’t add fake ratings just to obtain stars in Google.

6. Schema.org vs Google

This is an important beginner concept.

Schema.org defines the vocabulary:

Schema.org

Google decides which structured-data types and properties it uses for its search features.

So:

Schema.org = vocabulary
Google Search = implementation/use of that vocabulary

7. How to validate your Schema

After adding schema, test it rather than assuming it’s correct.

Useful tools include Google’s Rich Results Test and Schema.org’s validator.

For an ecommerce website, I recommend checking at least:

1. Product schema
2. BreadcrumbList
3. Organization
4. WebSite
5. Article/BlogPosting where applicable
6. Review/AggregateRating where genuinely available

8. Beginner SEO rule

The most important rule is:

Your structured data should accurately describe the visible content on the page.

Don’t add schema just because a property exists.

For example, if a product page doesn’t display a review, don’t invent:

"ratingValue": "5"