Schema Markup for Indian Business Websites: A Practical Guide

Schema markup is structured data, usually a JSON-LD script in the page, that tells search engines exactly what a page is about: a local business, a product with a price, an article, a breadcrumb trail. For most Indian business websites, five types cover almost everything: Organization or LocalBusiness on the home and contact pages, BreadcrumbList sitewide, Article on blog posts, Product on product pages, and FAQPage where you have genuine questions and answers. Add them in JSON-LD, keep them consistent with what is visible on the page, and test every template with Google’s Rich Results Test.

What schema does, and what it doesn’t

• Does: helps Google, Bing and AI answer engines read your pages accurately; makes pages eligible for rich results such as product price and availability, breadcrumbs and review ratings on products.
• Doesn’t: push a weak page to the top. It is a clarity layer on top of good content, not a substitute for it.

The types an Indian business actually needs

Schema type	Where it goes	Key fields
Organization	Home page	name, url, logo, sameAs (social profiles), contactPoint
LocalBusiness (or a subtype like Dentist, Restaurant)	Home or contact page of a business with a physical location	name, address, geo, telephone, openingHours, priceRange
BreadcrumbList	Every inner page	itemListElement with name and URL for each level
Article or BlogPosting	Blog posts	headline, datePublished, dateModified, author, image
Product	Product pages	name, image, offers with price, priceCurrency INR, availability
FAQPage	Pages with visible Q&A	mainEntity with Question and acceptedAnswer
Service	Service pages	serviceType, provider, areaServed

Getting LocalBusiness right

For clinics, restaurants, shops and agencies, LocalBusiness is the most valuable type, and it has to agree with everything else about you online.

• Use the most specific subtype available: Dentist, MedicalClinic, Restaurant, AutoRepair, and so on.
• The name, address and phone must match your Google Business Profile exactly, including abbreviations.
• Add geo coordinates and opening hours in the standard format.
• For several branches, give each branch its own page with its own LocalBusiness block. One block listing five addresses helps nobody. More on this in our guide to Google Business Profile optimisation.

How to add schema, step by step

1. List your page templates: home, service, product, blog post, contact, location.
2. Pick one or two types per template from the table above.
3. Generate the JSON-LD. On WordPress, SEO plugins handle Organization, Article and Breadcrumb automatically; add LocalBusiness and FAQ through the plugin’s settings or a custom block. On Shopify, many themes output Product schema; check it rather than assume. On custom sites, generate it from your database so prices and stock stay current.
4. Avoid duplicates. Two plugins printing two conflicting Organization blocks is common. View source and count.
5. Test each template in Google’s Rich Results Test and the Schema.org validator.
6. Monitor the Enhancements reports in Google Search Console. Our Search Console setup guide shows where they are.

Mistakes we fix most often

• Self-serving review stars on the business’s own LocalBusiness markup. Google does not show them, and fake ratings are a policy problem.
• Markup that doesn’t match the page: prices, hours or FAQs in the schema that visitors can’t see.
• Stale dates: dateModified never changes, or datePublished is newer than the content.
• Broken JSON: a stray quote or trailing comma silently kills the whole block. Validate after every edit.
• Staging URLs left in url and @id fields after launch.

Schema and AI search

AI answer engines read structured data too. Clean Organization, LocalBusiness and FAQ markup makes it easier for them to state your business name, location and services correctly. It is one part of a wider approach we describe in our AI search optimisation guide, alongside clear answer-first writing and an llms.txt file.

A LocalBusiness block you can adapt

Most Indian business sites need one well-formed LocalBusiness block and nothing more exotic. The fields that do the work:

• name — the name customers use, matching your Google Business Profile exactly. A mismatch here is the most common reason the two never connect.
• address — street, locality, city, state, postal code, and addressCountry set to IN. Spell the city the way India Post does, not the way locals abbreviate it.
• telephone — in full international form, +91 followed by the number, no spaces or dashes.
• openingHoursSpecification — real hours. If you close for lunch, say so; if you are open on Sunday, say that too.
• geo — latitude and longitude, which matter more than people expect in a city where two addresses can share a street name.
• sameAs — your Google Business Profile, and your real social profiles. This is the cheapest way to tell Google that these pages are the same business.
• areaServed — the cities or districts you actually serve, which is what makes a service business findable outside its own pin.

Pick the most specific type that fits. Dentist, Restaurant and HomeAndConstructionBusiness all say more than LocalBusiness, and all of them inherit its fields.

What India-specific fields are worth adding

A few details are worth more here than in the generic guides written for other markets:

• GST number — use vatID or taxID. It is a strong signal that a real registered entity is behind the site, and almost nobody adds it.
• Payment methods accepted — if you take UPI, say so with paymentAccepted. It answers a question most Indian buyers actually have.
• Languages — availableLanguage for Hindi, English or a regional language tells both Google and the visitor that they can be served in their own language.
• Prices in INR — wherever you use an Offer, set priceCurrency to INR. A price with no currency is routinely read as dollars.
• Multiple branches — one page and one block per branch, each with its own address and geo, all referring to the same parent organisation. Never one page listing six addresses.

Testing it properly, and what the errors mean

Two tools, in this order, and they answer different questions.

1. Schema Markup Validator — is the syntax valid at all? Use it while writing.
2. Google’s Rich Results Test — will Google actually use it? This is the one that matters, because valid markup Google ignores earns you nothing.

Then read the output carefully, because the three message types mean very different things:

• Errors — the rich result will not show. Fix these now.
• Warnings — a recommended field is missing. The result can still show, usually smaller. Fix when convenient.
• “Valid with no eligible rich result” — the markup is fine but this type does not produce a visual result. Not a bug; schema is also structured information, not only stars and boxes.

Finally, test the live URL rather than pasted code. Markup that is injected by JavaScript, or sits behind a cache, can validate in the editor and be absent from the page Google fetches. After any schema change, re-test the live URL and then check the Enhancements section of Search Console a week later to see what Google itself picked up.

The rule that keeps you out of trouble

Schema must describe what is visibly on the page. That one rule prevents every penalty risk in this area:

• No review stars for reviews that are not on the page. Self-serving review markup on a homepage is both against the guidelines and the most common reason a site loses its stars overnight.
• No FAQ markup for questions a visitor cannot read. If the questions are not in the page content, the markup should not exist.
• No prices in markup that differ from the prices shown. Rounding “from ₹24,999” up to a cleaner number in the schema is exactly the kind of mismatch that gets flagged.
• One canonical block per page. Two LocalBusiness blocks with slightly different phone numbers is worse than having none, because now Google has to pick.

Frequently Asked Questions

Does schema markup improve Google rankings?

Schema is not a direct ranking boost. It helps Google understand your pages and makes them eligible for rich results, such as product prices, ratings and breadcrumbs, which can improve how often people click. Content and links still decide where you rank.

Which format should I use: JSON-LD, Microdata or RDFa?

Google recommends JSON-LD where possible. It sits in a single script block, separate from the visible HTML, which makes it easier to add, update and debug without touching the page design.

Can I add review stars to my own business pages?

Google does not show review stars for self-serving reviews of your own business marked up on your own LocalBusiness or Organization pages. Review markup is meant for reviews of products or other items, and the reviews must be genuine and visible on the page.

Do FAQ rich results still show in Google?

Google has limited FAQ rich results to a small set of authoritative sites. FAQ markup is still valid and helps machines, including AI search tools, understand question-and-answer content, but most business sites should not expect the expandable FAQ display in results.

What happens if my schema has errors?

Invalid or misleading markup simply loses eligibility for rich results. Markup that misrepresents the page can lead to a manual action. Test with Google’s Rich Results Test, and make sure everything in the markup is also visible to users on the page.

Which schema types does a small Indian business website actually need?

For most businesses: one Organization or LocalBusiness block on the homepage with address, phone in +91 form, opening hours, geo coordinates and sameAs links to your Google Business Profile; WebSite with SearchAction; BreadcrumbList on inner pages; and Article plus FAQPage on blog posts where the questions are genuinely on the page. Service or Product markup only where you show real prices. Everything beyond that is rarely worth the maintenance.

Can schema markup get my site penalised?

Only if it describes something that is not on the page. The two that cause real trouble are review stars for reviews that do not appear anywhere on the site, and FAQ markup for questions a visitor cannot read. Prices in the markup that differ from the prices shown are also flagged. Keep the markup a description of the visible page and there is no risk.