Product schema for Indian e-commerce — INR, GST, rating rules

Quick frame: Indian e-commerce Product schema needs INR as priceCurrency, GST-inclusive pricing matching the page, valid schema.org availability URLs, and aggregateRating only when reviews are real and verifiable. Get these right and product listings earn star ratings in the SERP.

The four fields that unlock rich results

Google requires these for product rich result eligibility:

1. name — clear, matches the page H1.
2. image — absolute URL, 1200×675 or larger, accessible without auth.
3. offers.price — numeric, no currency symbol.
4. offers.priceCurrency — "INR" for Indian e-commerce.
5. offers.availability — one of the schema.org URLs (InStock, OutOfStock, PreOrder, Discontinued).

Use the product schema generator — defaults are tuned for INR.

GST and price honesty

Google's policy is strict: the schema price must equal the price the user sees on the landing page. For Indian e-commerce that usually means GST-inclusive prices, even if your back-office systems track ex-GST. Mismatches between displayed and schema price trigger manual actions and rich-result removal.

aggregateRating — only with real reviews

Star ratings in the SERP can lift CTR by 30–60%. But aggregateRating is the field most-abused by spammy sellers, and Google actively detects fake patterns:

• Reviews all clustered in one week.
• Identical wording across reviews.
• Reviews submitted from the same IPs.
• Average ratings that don't match user expectations for the product.

If you fake ratings, expect rich-result removal plus an enforcement action that can take months to clear.

The full Indian e-commerce schema bundle

For a product page to dominate SERP real estate, layer these together:

• Product schema (this page).
• Breadcrumb schema for the category path.
• Organization schema site-wide for entity recognition.
• LocalBusiness schema on the contact / store pages.

For the validation workflow, see validating schema with Google rich results.

FAQ

Q. Do I need GTIN, MPN or brand? A. Strongly recommended for retail products. Google uses them to consolidate product knowledge graphs across sellers. Without them, your listing competes alone instead of joining a unified product cluster.

Q. What about offers with multiple prices (sale + regular)? A. Use the lowPrice / highPrice pattern inside an AggregateOffer wrapper. The price field shows the current selling price; the wrapper preserves the range.

Q. Should I include shipping costs in schema? A. Yes — use shippingDetails. Google now requires shipping data for Free Listings eligibility in many markets, India included.