Schema Markup Guide 2026: Every Type, When to Use It, and How to Implement

Schema markup has had three phases in its 15-year life. Phase one, 2011 to 2016, was the “maybe Google will show you a rich snippet” phase when only heavy-handed implementers bothered. Phase two, 2017 to 2023, was the “rich results are a real ranking advantage” phase when schema went mainstream. Phase three, starting in 2024 and dominating 2026, is the “schema is how AI engines understand your website” phase. Most Indian agencies are still running phase-two playbooks against a phase-three reality.

This guide covers every schema type that matters in 2026, when to use each, how to implement them in JSON-LD, and the specific schema choices that drive AEO and GEO citations. It is the reference our technical team at Kerkar Media uses on every new engagement, and it is deliberately practical rather than exhaustive. You will not find 200 schema types here, only the ones that actually drive results.

1. What Is Schema Markup?

Schema markup is a vocabulary of tags that you add to your web pages to give search engines and AI engines machine-readable descriptions of the content. Instead of a crawler having to guess whether a paragraph is a product description, a review, or a company bio, schema explicitly labels it. That label is what allows rich snippets, knowledge panels, and AI citations to work.

The vocabulary is maintained at Schema.org, a collaborative project backed by Google, Microsoft, Yahoo, and Yandex. The format most commonly used, and the one Google recommends, is JSON-LD. It lives inside a script tag in your page’s HTML and has zero visual impact.

2. How Schema Works in 2026

Three things changed between 2023 and 2026 that shifted the strategic weight of schema.

Change 1: AI answer engines became first-class citizens

ChatGPT with browsing, Perplexity, and Google AI Overviews all parse structured data when deciding what to cite. Pages with clean schema get parsed faster, more reliably, and with better author attribution. This is the single biggest reason schema matters more in 2026 than it did two years ago. See our SEO strategy guide for how this fits into the wider picture.

Change 2: Google reduced some visible rich results

Counterintuitively, Google removed some rich snippets (FAQ rich results for most domains, HowTo for non-experts) while still using the underlying schema internally. The signal is not less valuable; it just became less visible. Schema now pays dividends you cannot always see, through knowledge graph strength and AI citations.

Change 3: The entity graph matured

Google’s Knowledge Graph and AI engines’ internal entity graphs both now depend heavily on sameAs links between profiles. Schema is the layer that makes those connections explicit.

3. The Complete Schema Type Map

Schema.org defines 800+ types, but the vast majority of SEO value comes from about 25 of them. Here is the map, grouped by purpose.

4. The Five Core Schema Types You Need

Eighty percent of schema value comes from five types. Implement these first on every site.

1. Organization schema

Deploy on the homepage (and optionally in the footer sitewide). Tells search engines what your brand is, its logo, its social profiles, and its key contact information. The sameAs property is the highest-leverage part.

Example JSON-LD structure includes these fields:

• @type: Organization (or LocalBusiness if you have a physical location)
• name: your brand name
• url: your canonical homepage URL
• logo: URL to your logo image
• sameAs: array of links to your LinkedIn, Twitter, Facebook, Instagram, Wikipedia, Wikidata
• contactPoint: customer service phone and email
• address: PostalAddress object

2. Article or BlogPosting schema

Deploy on every content page. Tells engines who wrote the article, when it was published, when it was last updated, and what the main entity is. Modern SEO plugins like Rank Math and Yoast handle this automatically, but the defaults are often thin. Customise for full benefit.

3. FAQPage schema

Deploy on any page with genuine question-and-answer content. Each Q and A pair becomes an extractable unit for AI engines. Note that most sites have lost visible FAQ rich results, but the underlying signal is still used for Perplexity, ChatGPT, and internal Google signals.

4. BreadcrumbList schema

Deploy on any page with hierarchical navigation (product categories, blog category trees, service taxonomies). Drives the breadcrumb-trail rich result in Google and gives AI engines a clean site structure map.

5. Product or Service schema

Deploy on commercial pages. Product for physical or digital goods; Service for intangible offerings. Includes AggregateRating and Review subtypes for social proof. This is where ecommerce and ecommerce SEO live or die.

5. Industry-Specific Schema

Healthcare (MedicalWebPage, Physician, MedicalClinic)

YMYL-critical. Use MedicalWebPage schema on medical content, Physician schema on doctor profiles, and MedicalClinic or LocalBusiness for the clinic entity. Include credentials, specialties, accepted insurance, and affiliations. Our SEO for doctors and dental SEO guides cover healthcare-specific schema in depth.

Legal (LegalService, Attorney)

Use LegalService schema for the firm entity, Attorney (Person subtype) for each lawyer, and include Bar Council registration as a credential. See law firm SEO.

Real estate (RealEstateAgent, Residence, House, Apartment)

Used for listings. RealEstateAgent for brokers, specific property-type schemas for listings. Includes price, size, amenities, and location. See real estate SEO.

Restaurants (Restaurant, Menu, MenuItem, FoodEstablishment)

Rich result eligibility is highest here. Menu schema with prices and descriptions drives local visibility. See restaurant SEO.

Automotive (AutoDealer, Vehicle, Car)

Dealership and inventory schemas for automotive sites. Structured vehicle specs drive shopping-related AI citations. See automotive SEO.

Manufacturing (Product, ProductGroup, Manufacturer)

B2B manufacturer catalogues benefit enormously from detailed Product schema with technical specifications. See SEO for manufacturers.

6. Schema for AEO and GEO

If you only read one section of this guide, read this one. Schema is the single highest-leverage investment for answer-engine visibility in 2026. Here is why.

Why AI engines love schema

Language models excel at interpreting unstructured text but stumble on extraction precision. A clean FAQPage schema block pre-packages a question and answer as a citation-ready unit. Organization schema with sameAs pre-connects your brand entity to its external identity. Article schema with proper author attribution pre-attributes the quote.

The AEO schema stack

For maximum AI citation rate, every site should have:

1. Organization schema with complete sameAs (Wikipedia if possible, Wikidata, LinkedIn, Crunchbase, major socials).
2. Person schema on every author page, with the same sameAs treatment.
3. Article schema on every content page, with explicit author attribution linking to the Person entity.
4. FAQPage schema on content pages with real Q-and-A.
5. BreadcrumbList on hierarchical pages.
6. Service or Product schema on commercial pages.

The sameAs property, specifically

This is the schema power move almost no Indian agency uses correctly. The sameAs array on Organization schema says “this brand is the same entity as the one on Wikipedia, Wikidata, Crunchbase, LinkedIn, and our Twitter profile.” Answer engines use this to resolve your brand as a single, high-confidence entity rather than fragmented references across the web.

A minimal high-value sameAs array for a typical Indian B2B brand:

• LinkedIn company page
• X or Twitter profile
• Facebook page
• Instagram (for consumer-facing brands)
• Wikipedia page (if you have one; worth pursuing for brands over a certain size)
• Wikidata entity (easier to get than Wikipedia; highly leveraged)
• Crunchbase profile
• Glassdoor or AmbitionBox (for employer-brand entity linking)

7. Specialty Schema: Events, Recipes, Jobs, Videos

Event schema

Drives the Event rich result in Google and is essential for conference organisers, venue owners, and training providers. Required properties: name, startDate, endDate, location, offers. Eligible for Google’s event pack in SERPs.

Recipe schema

Still one of Google’s most reliable rich results. Required: name, image, recipeIngredient, recipeInstructions. Optional but valuable: prepTime, cookTime, nutrition, aggregateRating.

JobPosting schema

Drives Google for Jobs integration. Required: title, description, hiringOrganization, jobLocation, datePosted, validThrough. Important for any company doing regular hiring.

VideoObject schema

For any video content hosted on your site. Drives video rich results and helps Google identify key moments. Required: name, description, thumbnailUrl, uploadDate. Increasingly relevant as digital marketing trends lean toward video.

Course and LearningResource schema

For education and online-learning providers. Useful for course-catalog visibility and increasingly for AI recommendations in learning-adjacent queries.

8. How to Implement Schema

Option 1: SEO plugin (easiest)

Rank Math, Yoast SEO, and SEO Framework all generate schema automatically based on your page type. This covers 60 to 70 percent of typical needs out of the box. The limitation is that default schema is often thin; you will want to customise.

Option 2: Dedicated schema plugin

Schema Pro, Schema and Structured Data for WP, and WP SEO Structured Data Schema all offer richer control than generic SEO plugins. Good for sites that need non-standard types like Event, Recipe, or Product schema.

Option 3: Manual JSON-LD in theme or header

For full control, inject JSON-LD script tags directly via theme files, Google Tag Manager, or a code-injection plugin. This is how we implement schema for clients with complex taxonomies because it decouples schema from plugin updates.

Option 4: Google Tag Manager

GTM can inject schema script tags as Custom HTML tags, triggered by URL or page type. Useful when you cannot modify theme files directly or want version-controlled schema deployment.

Testing your schema

Every schema deployment should pass these four tests:

1. Google Rich Results Test: validates rich-result eligibility.
2. Schema.org Validator: validates structural correctness even for types Google does not render as rich results.
3. Google Search Console Enhancements report: confirms Google is parsing your schema correctly over time.
4. Manual page source inspection: make sure the JSON-LD is actually present on the page (some caching plugins strip it).

9. Best Practices and Common Mistakes

Best practices

• Use JSON-LD, not microdata or RDFa. It is what Google recommends and is easier to maintain.
• Match schema to visible page content. Schema that describes content not actually on the page is a Google policy violation.
• Keep schema DRY. Define Organization schema once sitewide; do not duplicate it on every page.
• Use specific subtypes. LocalBusiness is better than Organization for a physical business; MedicalClinic is better than LocalBusiness for a clinic.
• Include the @id property for cross-referencing between schema blocks on the same page.
• Keep schema in sync with page updates. When you change content, update schema too.
• Validate after every deployment. Small errors cascade.

Common mistakes

• FAQ schema stuffing: adding FAQPage schema with questions not actually visible on the page. Google flags this.
• Review schema on irrelevant pages: self-serving review or rating schema on pages that do not host real reviews. Policy violation.
• Duplicate Organization schema: plugin-generated Organization schema alongside a manual version. Creates conflicts.
• Missing sameAs: Organization schema without sameAs is a missed opportunity. It is the single highest-leverage property.
• Wrong schema type for the page: BlogPosting on a service page; Product on an article. Mismatched types confuse engines.
• Thin schema: implementing schema with only the required properties when the optional ones would help. More properties usually mean richer interpretation.
• Not updating dateModified: stale dates signal stale content.
• Caching issues: some caching plugins strip JSON-LD. Always test the live page, not a preview.

10. Who Needs Schema Markup?

Key Takeaways

• Schema markup is structured data you add to web pages in JSON-LD format to tell search engines and AI engines what your content actually represents.
• Five core types cover 80 percent of needs: Organization, Article or BlogPosting, FAQPage, BreadcrumbList, and Product or Service.
• The sameAs property on Organization schema is the single highest-leverage schema element for entity building in 2026.
• Schema is now as much about AEO and GEO citation as it is about rich results. AI engines use structured data to extract entities and facts cleanly.
• Use JSON-LD. Match schema to visible content. Validate after every deployment. Include as many optional properties as are accurate.
• Industry-specific schema (MedicalWebPage, LegalService, RealEstateAgent) unlocks richer interpretation for regulated verticals.

11. Related Reading

Primary sources for schema reference: Schema.org is the canonical vocabulary. Google’s structured data documentation specifies which types Google renders as rich results. The Google Rich Results Test and the Schema.org Validator should be bookmarked. For ongoing industry updates, Search Engine Land tracks every schema-related announcement.

12. Frequently Asked Questions