📍 Gandhipuram, Coimbatore – 641012, Tamil Nadu
  1. Home
  2. Blog
  3. Schema markup guide

Part of our Answer Engine Optimization guide

Schema Markup Guide: How to Add Structured Data That Search Engines Actually Use

What schema markup does, what it doesn't, which rich results Google still shows after the 2023–2026 changes, and copy-ready JSON-LD templates for every common page type, explained for beginners.

By Bala Murugan, Fulcrum Creative School, Coimbatore Updated Reading time about 25 minutes
"@type": "Course",
"name": "SEO Course",
"description": "Keyword research,
  technical SEO, Search Console",
"provider": {
  "@type": "Organization",
  "name": "Example Institute"
}
Schema markup turns "some text on a page" into labelled facts: this is a course, this is its name, this is who provides it.

Quick answer: what is schema markup and should you use it?

Schema markup is code you add to a web page, usually as a JSON-LD script, that labels its content using the Schema.org vocabulary: this is an organisation, this is its address, this is the author, this is the event date. It helps search engines understand the page and can make it eligible for rich results. Use it on every template where it honestly describes visible content, but don't expect it to guarantee rich results or AI citations.[1][2][11]

HelpsSearch engines understand facts clearly
EnablesRich results for supported features
Doesn'tGuarantee rankings, rich results or AI citations

How to read this guide: numbered sources mark facts from Google's documentation and other primary sources. Best practice boxes describe accepted practice; Expert tips are our opinion from teaching and site reviews.

What is schema markup?

Definition

Schema markup is structured data written with the Schema.org vocabulary, a shared set of types (like Organization, Course, Event) and properties (like name, address, startDate) used by major search engines.[12]

Humans read a page and instantly understand that "Mon–Sat, 9:30–9" is opening hours and "2nd Floor, Kani Towers" is an address. Search engines are good at guessing, but they're still guessing. Schema markup removes the guesswork by stating facts in a format machines are built to read.

The same fact, two ways

What people see

Free SEO Workshop
Saturday 12 December 2026, 10 am – 1 pm
Example Institute, Coimbatore

What schema adds

"@type": "Event",
"name": "Free SEO Workshop",
"startDate": "2026-12-12T10:00:00+05:30",
"endDate": "2026-12-12T13:00:00+05:30",
"location": { "@type": "Place",
  "name": "Example Institute" }

Notice that the markup doesn't add new information. It labels information that's already visible. That's the most important rule of schema: it must be a true representation of the page content.[2]

Vocabulary vs format: Schema.org and JSON-LD

Quick answer: Schema.org is the vocabulary (the words). JSON-LD, Microdata and RDFa are formats (the grammar for writing them). Google supports all three and recommends JSON-LD.[2]

Beginners often mix these up. Think of Schema.org as a dictionary of agreed terms, and JSON-LD as one way of writing sentences with those terms. You can write the same facts in any of the three formats; JSON-LD is simply the easiest to add and maintain because it sits in its own script block, separate from your design.

JSON-LD
Microdata
RDFa
What it is
A script block of JSON
Attributes added to HTML tags
Attributes added to HTML tags
Where it goes
Anywhere in the page, often the head
Inside the visible HTML
Inside the visible HTML
Ease of maintenance
Easy: separate from design
Harder: mixed into templates
Harder: mixed into templates
Google's view
Recommended[2]
Supported
Supported
Best for
Almost every site
Legacy templates already using it
Legacy or publishing systems

Schema vs no schema

Is it worth the effort? For most business sites, yes, as long as the markup is accurate and you understand what it can and can't do.

With accurate schema
Without schema
Machine understanding
Facts are explicitly labelled: author, address, date, price
Search engines infer facts from text and layout
Rich result eligibility
Eligible for supported features (not guaranteed)[2]
Not eligible for most rich results
Click-through potential
Google's published case studies report higher CTR on rich results[1]
Standard blue link only
AI features in Google
No special schema required[11]
Can still appear if indexed and helpful
Risk
Manual action if markup is spammy or misleading[2]
No markup risk
Effort
Setup per template, then maintenance
None
Best use
Organisations, local businesses, articles, products, events, videos, course lists
Very simple pages with nothing to label

What Google's own case studies report

Google's introduction to structured data cites several published case studies:[1]

  • 25%higher click-through rate reported by Rotten Tomatoes on pages with structured data
  • 82%higher click-through rate for rich result pages reported by Nestlé
  • 35%increase in visits reported by Food Network after enabling search features
  • 1.5×more time spent on pages with structured data reported by Rakuten

These are results reported by large publishers and brands, not predictions for your site. Results vary by industry, feature and query.

What schema does, and what it doesn't

What schema does

  • Labels facts so search engines understand them precisely[1]
  • Makes pages eligible for supported rich results[3]
  • Helps Google disambiguate your organisation and choose your logo and site name[4][7]
  • Connects entities (organisation, authors, content) through @id

What schema doesn't do

  • Guarantee rich results, even when valid[2]
  • Act as a shortcut to higher rankings
  • Get you into AI Overviews: Google says no special schema is needed[11]
  • Make up for thin or unhelpful content

The anatomy of JSON-LD

Quick answer: every JSON-LD block has a @context (which vocabulary), a @type (what kind of thing) and properties (facts about it). Advanced blocks use @id to name entities and @graph to hold several connected entities.

  1. 1

    <script type="application/ld+json">

    The wrapper. It tells the browser this is data, not code to run, so it never affects how the page looks.

  2. 2

    "@context": "https://schema.org"

    Declares the vocabulary. Every term after this is a Schema.org term.

  3. 3

    "@type": "Course"

    What the thing is. Use the most specific type that's accurate.

  4. 4

    Properties

    "name", "description", "startDate"… Each is a fact. Values are text, numbers, URLs, dates or nested objects.

  5. 5

    Nested objects

    A property can hold another typed object, like an address of type PostalAddress inside a LocalBusiness.

  6. 6

    "@id"

    A unique identifier, usually a URL plus a fragment (…/#organization), so other blocks can point to the same entity.

  7. 7

    "@graph"

    An array holding several entities in one block, all connected by their @id references.

Formatting rules that prevent most errors

  • Put every key and text value in straight double quotes: "name", not “name”
  • Separate properties with commas, but don't put a comma after the last one
  • Write dates in ISO 8601: 2026-11-19T09:00:00+05:30
  • Use full URLs including https://
  • Use Schema.org enum URLs for fixed values: https://schema.org/InStock

Rich results status board (2026)

Quick answer: Google still supports many rich results, including Article, Breadcrumb, Course list, Event, Local business, Organization, Product, Review snippet and Video. It no longer shows FAQ, HowTo or Course info rich results.[3][8][9][10]

Google has simplified its results pages several times since 2023. Many older guides still recommend markup for features that no longer appear. Here's where things stand.

  • Supported

    Article

    News, blog and sports articles: better title, image and date display.

  • Supported

    Breadcrumb

    Shows the page's position in the site hierarchy.

  • Supported

    Course list

    A carousel of courses from one provider (English, all regions).[5]

  • Supported

    Event

    Dates, venues and ticket details for events.

  • Supported

    Local business

    Business details such as hours and location.

  • Supported

    Organization

    Logo, contact details and identity information.[4]

  • Supported

    Product

    Price, availability and reviews for products.

  • Supported

    Profile page

    Information about a person or organisation on creator-focused sites.

  • Supported with limits

    Review snippet

    Star ratings, with strict rules on self-serving reviews.[6]

  • Supported

    Video

    Video thumbnails, key moments and live badges.

  • Supported

    Job posting

    Job listings in Google's job search experience.

  • Supported

    Recipe, Movie, Dataset and more

    Specialist features for specific content types.[3]

  • No longer shown

    FAQ

    FAQ rich results stopped showing in Google Search in May 2026.[9]

  • No longer shown

    HowTo

    HowTo rich results were deprecated in 2023.[8]

  • No longer shown

    Course info

    Retired in 2025 (Course list remains).[10]

  • No longer shown

    Claim review, Estimated salary, Learning video, Special announcement, Vehicle listing, Book actions

    Phased out in 2025 to simplify results.[10]

Google updates its search gallery regularly. Check the official gallery before planning new markup.[3] "No longer shown" means no rich result in Google; the markup itself remains valid Schema.org vocabulary.

Copy-ready templates by page type

Choose a page type to see a JSON-LD template, then replace every example value with your real, visible information. Test the result before publishing.

Home page: Organization + WebSite
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://www.example.com/#organization",
      "name": "Example Institute",
      "url": "https://www.example.com/",
      "logo": "https://www.example.com/logo.png",
      "telephone": "+91-00000-00000",
      "sameAs": ["https://www.instagram.com/example/"]
    },
    {
      "@type": "WebSite",
      "@id": "https://www.example.com/#website",
      "url": "https://www.example.com/",
      "name": "Example Institute",
      "publisher": { "@id": "https://www.example.com/#organization" }
    }
  ]
}

Place on the home page only. Logo must be at least 112×112 px and crawlable. WebSite name helps Google choose your site name.[4][7]

Contact page: LocalBusiness
{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "@id": "https://www.example.com/#organization",
  "name": "Example Institute",
  "url": "https://www.example.com/",
  "telephone": "+91-00000-00000",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "2nd Floor, Example Towers, Main Road",
    "addressLocality": "Coimbatore",
    "postalCode": "641000",
    "addressRegion": "TN",
    "addressCountry": "IN"
  },
  "geo": { "@type": "GeoCoordinates", "latitude": 11.0, "longitude": 76.9 },
  "openingHoursSpecification": [{
    "@type": "OpeningHoursSpecification",
    "dayOfWeek": ["Monday","Tuesday","Wednesday","Thursday","Friday","Saturday"],
    "opens": "09:30", "closes": "21:00"
  }]
}

Match your Google Business Profile exactly. Use a specific subtype (for example EducationalOrganization or Store) when one fits. Don't add star ratings for reviews you collect about yourself.[6]

Blog post: BlogPosting + author
{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "How to Learn SEO in 60 Days",
  "image": ["https://www.example.com/images/seo-60-days-16x9.jpg"],
  "datePublished": "2026-11-19T09:00:00+05:30",
  "dateModified": "2026-11-19T09:00:00+05:30",
  "author": {
    "@type": "Person",
    "name": "Priya Kumar",
    "url": "https://www.example.com/team/priya-kumar"
  },
  "publisher": { "@id": "https://www.example.com/#organization" }
}

Article markup has no required properties in Google's documentation, but headline, image, dates and author improve understanding. Change dateModified only for meaningful updates.

Course list page: ItemList + Course
{
  "@context": "https://schema.org",
  "@type": "ItemList",
  "itemListElement": [
    { "@type": "ListItem", "position": 1,
      "url": "https://www.example.com/courses/seo" },
    { "@type": "ListItem", "position": 2,
      "url": "https://www.example.com/courses/google-ads" },
    { "@type": "ListItem", "position": 3,
      "url": "https://www.example.com/courses/content-marketing" }
  ]
}

/* On each course page: */
{
  "@context": "https://schema.org",
  "@type": "Course",
  "name": "SEO Course",
  "description": "Learn keyword research, technical SEO and Search Console.",
  "provider": {
    "@type": "Organization",
    "name": "Example Institute",
    "sameAs": "https://www.example.com/"
  }
}

Course list needs at least three courses, ItemList on a summary or all-in-one page, and a unique URL per item. Course descriptions display up to 60 characters.[5]

Product page: Product + Offer
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Handmade Cotton Tote Bag",
  "image": ["https://www.example.com/images/tote.jpg"],
  "description": "Hand-printed cotton tote, 38 x 42 cm.",
  "sku": "TOTE-001",
  "offers": {
    "@type": "Offer",
    "url": "https://www.example.com/tote",
    "priceCurrency": "INR",
    "price": "499",
    "availability": "https://schema.org/InStock"
  }
}

Price and availability must match what shoppers see. Only include reviews and ratings that are genuinely shown on the page.[2]

Event page: Event
{
  "@context": "https://schema.org",
  "@type": "Event",
  "name": "Free SEO Workshop",
  "startDate": "2026-12-12T10:00:00+05:30",
  "endDate": "2026-12-12T13:00:00+05:30",
  "eventAttendanceMode": "https://schema.org/OfflineEventAttendanceMode",
  "eventStatus": "https://schema.org/EventScheduled",
  "location": {
    "@type": "Place",
    "name": "Example Institute",
    "address": { "@type": "PostalAddress", "addressLocality": "Coimbatore", "addressCountry": "IN" }
  },
  "organizer": { "@id": "https://www.example.com/#organization" }
}

Use for real, dated events. Update eventStatus if an event is postponed or cancelled.

Video page: VideoObject
{
  "@context": "https://schema.org",
  "@type": "VideoObject",
  "name": "How to Use Google Search Console",
  "description": "A 10-minute walkthrough of the Performance report.",
  "thumbnailUrl": ["https://www.example.com/thumbs/gsc.jpg"],
  "uploadDate": "2026-11-19T09:00:00+05:30",
  "duration": "PT10M",
  "contentUrl": "https://www.example.com/videos/gsc.mp4"
}

The video must be visible on the page. Use one main video per page for the clearest signal.

Any deep page: BreadcrumbList
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com/" },
    { "@type": "ListItem", "position": 2, "name": "Courses", "item": "https://www.example.com/courses/" },
    { "@type": "ListItem", "position": 3, "name": "SEO Course" }
  ]
}

Mirror the visible breadcrumb trail. The last item can omit the URL.

Schema for educational institutes and training centres

Quick answer: use Organization or EducationalOrganization on your home page, LocalBusiness details on your contact page, BlogPosting on guides, and Course markup with a Course list on your courses page. Don't add star ratings for reviews you collect about yourself.[4][5][6]

Course list: the rules

  • Mark up at least three courses, on separate detail pages or one all-in-one page[5]
  • Add ItemList markup to a summary page or all-in-one page, with a unique URL for each course[5]
  • Each course needs a name and description; descriptions display up to 60 characters[5]
  • Include the provider (your organisation) for every course[5]
  • The feature is available in English in all regions where Google Search is available[5]

Reviews and star ratings

Many institutes want gold stars in search results. Google's review snippet rules say that if an organisation controls the reviews about itself, its pages using LocalBusiness or Organization markup aren't eligible for star review snippets.[6] Showing genuine Google reviews on your site is fine for visitors; just don't mark them up as self-serving ratings. Point people to your Google Business Profile reviews instead.

Real example

A training institute lists eight courses on its "Courses" page with a short description and link for each. It adds ItemList markup there and Course markup (name, description, provider) on each course page. Its home page carries Organization markup with logo and sameAs; its contact page carries the address and hours. No AggregateRating markup is used for its own reviews.

How to add schema markup: 7 steps

  1. Map your templates

    List every page type on your site (home, course, blog, contact, product) and the schema type that honestly describes each.

  2. Check current documentation

    Open Google's documentation for each feature you want. Note required and recommended properties; Google says required properties are needed for eligibility, and fewer complete, accurate properties beat many incomplete ones.[1]

  3. Write the JSON-LD

    Start from a template, use real visible values and give each entity an @id.

  4. Test before publishing

    Paste the code or a staging URL into the Rich Results Test and fix every error.[1]

  5. Add it to the page

    Place the script in your template (head or body), or use your CMS or SEO plugin's custom schema field.

  6. Confirm Google sees it

    After publishing, use URL Inspection to confirm Google found the structured data.[1]

  7. Monitor

    Check Search Console's rich result reports for errors and warnings, and compare performance over time.[1]

Testing and monitoring tools

Use more than one tool: each answers a different question.

Tool
What it does
When to use it
Rich Results Test
Checks whether a page or code snippet is eligible for Google rich results and previews some features[1]
While building and before publishing
Schema Markup Validator
Validates any Schema.org markup, including types Google doesn't use for rich results
To check general syntax and vocabulary
Search Console rich result reports
Shows valid items, warnings and errors across your whole site[1]
After launch, weekly or monthly
URL Inspection
Confirms Google has found the structured data on a specific page[1]
After publishing or fixing a page
Performance report
Compares clicks and CTR for pages, including search appearance filters where available[1]
To measure impact over time

Common schema errors and how to fix them

Error or warning
What it usually means
How to fix it
Missing field "X"
A required or recommended property is absent
Add it, using a value that's visible on the page
Invalid value in field
Wrong format: a date, URL, number or enum value
Use ISO dates (2026-11-19), full URLs, plain numbers and schema.org enum URLs
Unparsable structured data
Broken JSON: a missing comma, quote or bracket
Paste the code into a JSON validator; check commas between properties
Item not eligible
The type isn't supported for rich results, or rules aren't met
Check the feature's Google documentation and requirements
Duplicate or conflicting entities
Two blocks describe the same thing differently
Use one @id per entity and reference it everywhere
Manual action: spammy structured data
Markup misleads users or describes hidden content
Remove or correct it, then request reconsideration[2]

Google notes that a manual action for structured data removes the page's eligibility for rich results, but doesn't affect how the page ranks in web search.[2] That's still a loss worth avoiding.

The rules: do's and don'ts

Google's general structured data guidelines apply to every type.[2] In short:

Do

  • Mark up content visible to users
  • Make markup a true representation of the page
  • Use the most specific accurate type
  • Include all required properties
  • Keep markup up to date

Don't

  • Mark up hidden or irrelevant content
  • Use fake reviews or ratings
  • Misrepresent who you are or what you offer
  • Mark up content that misleads users
  • Add self-serving review stars to your own business

Schema implementation checklist (16 items)

Tick items as you go; ticks are saved on this device. Print it for your developer or team.

Plan

Build

Accuracy

Validate

Maintain

Frequently asked questions (30)

Basics

Schema markup is code added to a web page that labels its content using the Schema.org vocabulary, so search engines can understand facts like who wrote it, where a business is or when an event happens.

Nearly. Structured data is the general idea of organising information in a machine-readable format; schema markup usually means structured data written with the Schema.org vocabulary.

JSON-LD. Google supports JSON-LD, Microdata and RDFa, and recommends JSON-LD because it's easiest to add and maintain.

Google doesn't describe structured data as a ranking boost. It helps Google understand content and can make pages eligible for rich results, which may improve click-through.

No. Google says it doesn't guarantee that structured data will show up in search results, even when the markup is valid.

JSON-LD can go in the head or body of the page. Many sites place it in the head through their template or CMS.

Rich results

Google's search gallery lists features including Article, Breadcrumb, Course list, Event, Local business, Organization, Product, Profile page, Review snippet, Video, Job posting and Recipe.

No. Google stopped showing FAQ rich results in Google Search in May 2026. FAQPage markup is still valid Schema.org vocabulary.

No. Google deprecated HowTo rich results in 2023.

Not from reviews you control about yourself. Google says LocalBusiness or Organization pages are ineligible for star review snippets when the entity controls the reviews about itself.

A carousel of courses from one provider. It needs at least three courses with name and description, and ItemList markup on a summary or all-in-one page.

Google retired the Course info rich result in 2025 as part of simplifying results. The Course list feature remains.

Implementation

Choose the right types for each template, write JSON-LD with accurate visible facts, test it in the Rich Results Test, publish it, confirm with URL Inspection and monitor Search Console reports.

Yes. Many SEO plugins add common schema automatically. Check their output in the Rich Results Test and add or correct types the plugin doesn't handle well.

@id gives an entity a unique identifier so other blocks and pages can refer to it, connecting your organisation, authors and content into one graph.

No. Google recommends placing Organization markup on the home page or a single page describing the organisation. Other pages can reference it with @id.

Content in tabs or accordions that users can open is visible content. What you must not do is mark up information users can't see at all.

As many as genuinely describe the page: for example WebPage, BreadcrumbList, BlogPosting and Person on an article.

Google can apply a manual action. The page loses eligibility for rich results, though Google says its web search ranking isn't affected by that action.

Schema and AI

No. Google says no special schema is required for its AI features. Pages must be indexed and eligible to show with a snippet.

Structured data makes facts explicit and helps search engines disambiguate organisations. Accurate facts on your site and profiles are what matter most for AI answers.

It's harmless if it matches visible questions exactly, but it no longer produces FAQ rich results in Google. Don't add it expecting visual results.

Testing and learning

The Rich Results Test checks eligibility for Google's rich results. The Schema Markup Validator checks any Schema.org markup, including types Google doesn't use for rich results.

Use URL Inspection to confirm Google found it, check Search Console rich result reports for errors, and compare performance over time.

BlogPosting or Article, with headline, image, datePublished, dateModified and an author (Person). Reference your organisation as publisher with @id, and add BreadcrumbList if the page shows breadcrumbs.

Accurate markup won't. Spammy or misleading markup can lead to a manual action that removes rich result eligibility. Broken markup simply gets ignored, so fix errors you find.

Use LocalBusiness (or a more specific subtype) when customers visit you or you serve a local area. Use Organization for organisations without a public location. LocalBusiness is itself a type of Organization.

Bala Murugan of Fulcrum Creative School, Coimbatore, using Google's documentation and the sources listed at the end.

Fulcrum Creative School in Gandhipuram covers structured data, technical SEO and AI search in its SEO and digital marketing courses, in classroom and live online batches.

Yes. Copy and adapt them freely, replacing example values with your real, visible information. A link back to this guide is appreciated.

Schema markup glossary (30 terms)

BreadcrumbList
A schema type describing a page's position in the site hierarchy.
Carousel
A rich result showing several items in a scrollable row, such as courses.
@context
The JSON-LD line that declares which vocabulary is used, usually https://schema.org.
Course list
A Google rich result showing courses from one provider; needs at least three courses.
Deprecated
No longer supported or shown, though the markup may still be valid vocabulary.
Entity
A distinct, identifiable thing described by structured data.
Enum
A fixed set of allowed values, such as https://schema.org/InStock.
@graph
A JSON-LD array that holds several connected entities in one block.
@id
A unique identifier that lets different blocks and pages refer to the same entity.
ISO 8601
The international date and time format used in structured data (2026-11-19T09:00:00+05:30).
ItemList
A schema type for an ordered list of items, used for carousels such as Course list.
JSON-LD
JavaScript Object Notation for Linked Data: the structured data format Google recommends.
Manual action
A penalty applied by a Google reviewer; for structured data it removes rich result eligibility.
Microdata
A format that adds structured data attributes directly to HTML elements.
Nested object
An object inside another, such as an address inside a LocalBusiness.
Property
An attribute of a type, such as name, address or datePublished.
RDFa
Resource Description Framework in Attributes: another attribute-based structured data format.
Recommended property
An optional property that can improve the chance of enhanced display.
Required property
A property a feature needs for an item to be eligible for that rich result.
Review snippet
A rich result showing star ratings, subject to strict eligibility rules.
Rich result
A search result with extra visual features enabled by structured data.
Rich Results Test
Google's tool for testing whether a page is eligible for rich results.
sameAs
A property listing URLs of other profiles representing the same entity.
Schema markup
Code added to a page that labels its content using the Schema.org vocabulary.
Schema Markup Validator
A general validator for Schema.org markup.
Schema.org
A shared vocabulary of types and properties used by major search engines.
Search gallery
Google's list of structured data features it currently supports in Search.
Self-serving review
A review about a business that the business itself controls or displays; not eligible for stars on LocalBusiness or Organization markup.
Structured data
Information organised in a standard, machine-readable format, such as Schema.org markup.
@type
The JSON-LD key naming the kind of thing described, such as Organization or Course.
Questions about the course? Chat with us on WhatsApp
Call Now WhatsApp