Schema Markup & Structured Data for Indian Websites 2026

A Thiruvananthapuram law firm added LocalBusiness and FAQPage schema to their website in January 2026. Within six weeks, their Google Search Console impressions increased by 34% without any content changes, and their average position for "lawyer Thiruvananthapuram" improved from 6.2 to 4.1. The FAQ accordion rich results appearing in SERPs increased their click-through rate from 2.4% to 6.1% on question-format queries. Schema markup did not change their content quality or backlink profile — it changed how Google understood and presented their content to searchers.

Structured data is one of the most underutilised SEO tools for Indian websites. While large e-commerce platforms and national news sites have implemented schema comprehensively, most Indian SME, service business, and local brand websites either have no schema markup or have implemented it incorrectly — missing rich result eligibility and sending confusing signals to Google's entity understanding system.

This guide covers the schema types that matter most for Indian websites in 2026, the implementation errors that undermine their effectiveness, and the post-March 2026 Spam Update rules that govern FAQPage schema use.

What Schema Markup Does (and Doesn't Do) for Indian SEO

Schema markup — implemented as JSON-LD in the page head, or as Microdata/RDFa in HTML markup — communicates structured information about page content directly to search engines. It tells Google not just what text is on the page, but what that text means: that this is a business with a specific address, that these are frequently asked questions, that this is a product with a specific price in INR.

Schema markup does not directly improve rankings. Google has confirmed this clearly, and SEO experiments consistently support it. What schema does: it makes your page eligible for rich results — enhanced SERP presentations that can significantly improve click-through rates. FAQPage schema enables accordion Q&A results. Product schema enables price and rating stars. LocalBusiness schema enriches the Knowledge Panel and local pack presentation. Review schema enables star ratings in organic results.

For Indian websites, the business case for schema is click-through rate improvement. Indian SERPs are competitive, and rich results — especially FAQ accordions that expand the search result to 3–4 lines with answers — occupy significantly more screen real estate than standard blue-link results. A result with a 4-line FAQ expansion below it on mobile (where 70%+ of Indian searches happen) dominates the viewport in a way that a standard result cannot.

LocalBusiness Schema for Indian Businesses

LocalBusiness schema is the highest-priority schema type for any Indian business with a physical location or service area. It communicates business identity, location, hours, and contact information in a machine-readable format that strengthens Google's understanding of your local entity.

A correctly implemented LocalBusiness schema for a Kerala Ayurveda clinic:

{
  "@context": "https://schema.org",
  "@type": "MedicalBusiness",
  "name": "Vaidyaratnam Ayurveda Centre",
  "image": "https://example.com/clinic-image.jpg",
  "url": "https://example.com",
  "telephone": "+914954223344",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "123 Ayurveda Road",
    "addressLocality": "Thrissur",
    "addressRegion": "Kerala",
    "postalCode": "680001",
    "addressCountry": "IN"
  },
  "openingHoursSpecification": [
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Monday","Tuesday","Wednesday","Thursday","Friday","Saturday"],
      "opens": "08:00",
      "closes": "18:00"
    }
  ],
  "priceRange": "₹₹",
  "currenciesAccepted": "INR",
  "paymentAccepted": "Cash, UPI, Credit Card"
}

Critical LocalBusiness schema errors that Indian websites commonly make:

Using generic "@type": "LocalBusiness": Google gives more entity disambiguation weight to specific business type declarations. Use the most specific applicable type: Restaurant, MedicalBusiness, LegalService, HomeAndConstructionBusiness, HealthAndBeautyBusiness, FinancialService, EducationalOrganization, LodgingBusiness. Schema.org has hundreds of specific types — choosing the right one helps Google categorise your business correctly.

addressLocality set to "India" or "Kerala" instead of the city: This is the most common Indian LocalBusiness schema error. addressLocality must be the specific city (Thiruvananthapuram, Kochi, Kozhikode, Thrissur) — not the state or country. Setting it to "Kerala" or "India" undermines local entity recognition entirely.

postalCode using state or country codes instead of PIN: Indian PIN codes are 6-digit numbers (e.g., 680001 for Thrissur city centre). Never use state abbreviations or country codes in the postalCode field.

Telephone format inconsistency: Use +91XXXXXXXXXX format consistently. Google maps this to your Google Business Profile phone number — inconsistency between schema, website, and GBP creates NAP (Name, Address, Phone) inconsistency signals that hurt local pack rankings.

FAQPage Schema: Post-March 2026 Spam Update Rules

FAQPage schema was heavily abused in 2024–2025 by Indian and global websites adding 10–20 generic questions to every page purely to generate accordion rich results. Google's March 2026 Core and Spam Updates specifically targeted FAQPage schema abuse, and Google has reduced FAQPage rich result display frequency for pages where the FAQ content is deemed thin, generic, or manipulative.

FAQPage schema rules in 2026 for Indian websites:

Only add FAQPage schema when the page genuinely contains FAQ content. A blog post that covers a topic thoroughly but doesn't have explicitly formatted Q&A sections should not use FAQPage schema. The schema should match what the user actually sees on the page.

2–4 questions per page is optimal. Google's documentation recommends including only the most important FAQs. Pages with 8–15 questions are more likely to be flagged as schema spam than pages with 3 genuinely useful questions.

Answers must be specific and informative. Generic answers like "Yes, we offer this service. Contact us to learn more" do not meet the quality threshold for rich result eligibility. Each answer should provide 2–5 sentences of genuinely useful information that a user would value seeing directly in the SERP.

Never duplicate FAQPage schema across multiple pages. Using the same 3 questions and answers on your homepage, service page, and blog post signals schema manipulation. Each page's FAQPage schema must be unique to that page's specific content.

FAQ answers must not be keyword-stuffed. Including the page's target keyword phrase 3–4 times in a FAQ answer is a signal that the schema is written for bots rather than users. Write answers that a human expert would give to a genuine question.

Product Schema for Indian E-Commerce Websites

Product schema enables price, availability, and review stars in Google Shopping and organic search results. For Indian e-commerce businesses, correctly implemented Product schema is essential for rich result eligibility.

The minimum viable Product schema for an Indian e-commerce product page:

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Kerala Kasavu Saree — Gold Zari Border",
  "image": "https://example.com/kasavu-saree.jpg",
  "description": "Handwoven Kerala kasavu saree with traditional gold zari border.",
  "brand": {"@type": "Brand", "name": "KeralaWeaves"},
  "offers": {
    "@type": "Offer",
    "url": "https://example.com/kasavu-saree",
    "priceCurrency": "INR",
    "price": "3500",
    "priceValidUntil": "2026-12-31",
    "itemCondition": "https://schema.org/NewCondition",
    "availability": "https://schema.org/InStock"
  }
}

Key requirements for Google to display Product rich results for Indian websites:

The price must match what is displayed on the page. Google crawls product pages and cross-checks schema price against visible page price. Discrepancies — such as showing a sale price in schema while the page displays the original price (or vice versa) — can result in rich result suppression or manual action.

priceCurrency must be "INR" for Indian Rupee pricing. Do not use "₹" as the currency code — the ISO 4217 currency code "INR" is required.

For products with reviews, AggregateRating can be added to display star ratings in SERPs. The ratingValue and reviewCount must reflect actual reviews — fabricated review counts are a policy violation that Google's product review systems increasingly detect.

Article Schema for Indian Blog Posts

Article schema on blog posts and news articles helps Google understand the authorship, publication date, and content category — which feeds into E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) signals.

For Indian blogs covering business, technology, finance, health, or legal topics — all considered "Your Money Your Life" (YMYL) categories — Article schema with accurate author Person schema provides additional E-E-A-T signals. The author's @type should be "Person" with a name, url (linking to an About page or LinkedIn), and jobTitle that matches the content expertise.

datePublished and dateModified must be accurate. Post-2025 Google has become better at detecting artificially manipulated dates — setting datePublished to a date before the content was actually created to claim first-mover advantage is increasingly detectable and counterproductive.

For Indian financial, medical, or legal content, include a sameAs property linking the author's Person schema to their LinkedIn profile, professional registration pages, or authoritative third-party profiles. This provides Google with additional verification signals for E-E-A-T assessment.

BreadcrumbList Schema for Indian Website Navigation

BreadcrumbList schema enables breadcrumb navigation display in Google SERPs — the "Home > Services > SEO Services" path that appears below some organic results. For Indian websites with deep navigation structures, breadcrumbs improve both user experience and Google's understanding of site hierarchy.

BreadcrumbList is particularly valuable for Indian e-commerce sites and content-heavy websites where Google may not fully understand the site's category structure from internal links alone. A kasavu saree product page with breadcrumbs declaring Home > Sarees > Kasavu Sarees > Product Name tells Google the product category relationship explicitly.

Implementation note: the BreadcrumbList must match the actual navigation breadcrumbs visible on the page. Declaring a breadcrumb path in schema that does not appear in the page's visible navigation is a policy violation.

Review and AggregateRating Schema

Review schema and AggregateRating schema enable star ratings in organic search results — one of the highest click-through rate improvements available through structured data. However, these schema types come with strict policies that Indian websites must understand.

Google's review policies prohibit self-serving reviews — reviews written by the business itself or solicited specifically for schema display. For Indian service businesses adding AggregateRating schema, the ratings must come from a verifiable review platform (Google Reviews, Justdial, Sulekha) or from genuine on-page testimonials with individual Review markup for each testimonial.

The reviewCount in AggregateRating must match actual verified reviews. A business with 12 genuine Google reviews cannot display a reviewCount of 87 in their schema. Google's structured data quality algorithms detect implausible review counts and suppress rich results accordingly.

For Indian medical, legal, and financial businesses, Note that these categories face heightened scrutiny for review schema under YMYL policies. Review manipulation in these categories is treated more severely than in general retail verticals.

Schema Implementation: JSON-LD vs Microdata for Indian Websites

JSON-LD (JavaScript Object Notation for Linked Data) is the recommended schema implementation method for all Indian websites. Google explicitly recommends JSON-LD over Microdata and RDFa because it is easier to implement, easier to debug, and does not require embedding schema attributes within HTML element markup — it can be placed entirely in the <head> as a <script type="application/ld+json"> block.

For Indian CMS-based websites: WordPress users should use Rank Math SEO or Yoast SEO (both have free tiers) which generate correct JSON-LD schema automatically for posts and pages. Rank Math has better support for Indian-specific schema requirements and is actively maintained with Google guideline updates.

For static HTML Indian websites: place JSON-LD blocks directly in the <head> section. Multiple schema types on the same page should be implemented as separate <script type="application/ld+json"> blocks rather than combined into a single block — this is valid per spec and easier to maintain.

Testing and Validating Schema for Indian Websites

Before deploying schema on any Indian website, validate it using Google's Rich Results Test (search.google.com/test/rich-results) and Schema.org's validator (validator.schema.org). Both tools identify errors and warnings that prevent rich result eligibility.

Common validation errors on Indian websites: missing required fields for specific @type (Product schema missing priceCurrency; LocalBusiness missing telephone); invalid telephone format (Indian numbers must start with +91); incorrect addressCountry (using "India" instead of "IN"); and FAQPage answers that are too short (under 50 characters) to qualify for rich results.

After deployment, monitor rich result performance in Google Search Console under Enhancements > structured data report. This shows which pages have valid schema, which have errors, and whether rich results are being generated. For Indian business websites, the local pack and FAQ enhancement reports provide the most actionable optimisation data.