Schema That Changes Your Listing, and Schema That Doesn't

Structured data — often called schema markup — is a block of code you add to a page that describes what the page is about in a format search engines read directly. Not headings and paragraphs, which they have to interpret, but a labelled list: this is a product, this is its price, this is whether it is in stock.

It gets sold badly. Plenty of agencies and plugins will add forty types of markup to every page of your site and call it an SEO deliverable. Most of that code does nothing you can see. A small number of schema types genuinely change how your listing appears in Google, and those are worth the effort. This piece is about telling the two apart.

What structured data actually does

Structured data makes you eligible for a different kind of search result. It does not move you up the page.

That distinction matters because it is where most of the sales pitch goes wrong. Google's own documentation describes structured data as a way to help it understand a page and to qualify for rich results — star ratings, prices, breadcrumb trails, event dates in the listing. Google has never documented schema markup as a general ranking signal, and its representatives have said publicly that adding it does not by itself lift you in the results.

So the honest business case is not "we will rank higher". It is: if you already appear on page one for a search, a listing with a price and a stock status and a breadcrumb takes up more space and gives more reason to click than three lines of grey text. On a phone screen, where four or five results fill the whole view, that is not a small thing.

The second thing worth knowing: markup must match what a visitor can see on the page. Google's guidelines are explicit about this. Marking up a ₹8,000 price when the page says ₹12,000, or marking up reviews that do not appear anywhere, is a policy breach. Search Console issues a manual action called "Spammy structured markup" and the rich result disappears — sometimes the page goes with it. This is the main risk of letting a plugin generate markup automatically from fields nobody fills in properly.

The types worth adding

For most Indian small businesses, the useful list is short.

Product, if you sell things online

This is the one with the clearest payoff. Product markup carries price, currency, availability and condition. Done properly, your result can show "₹2,499" and "In stock" before anyone clicks. For a shopper comparing four tabs, that decides which tab they open first. It also feeds Google's shopping surfaces, which matters if you are listing in Merchant Center.

The trap is out-of-stock and stale prices. If your markup says in stock and your page says sold out, you get a bad click and eventually an error in Search Console. Product markup has to be generated from live data, not typed in once. Shopify and WooCommerce both handle this reasonably out of the box, which is one of the quiet reasons to use them rather than a hand-built catalogue — something we get into when planning a build.

Breadcrumb

Unglamorous and almost free. Breadcrumb markup replaces the raw URL line in your listing with a readable path — Home › Kitchen Fittings › Sink Taps — so the searcher sees where the page sits in your site. It works, Google supports it, and it takes no maintenance because the structure comes from your navigation. If your site has categories at all, add it.

Organization, once, on your homepage

One block that states your legal name, logo, address, phone number and your official social profiles. This does not produce a rich result you can point to. What it does is remove ambiguity about which entity your site belongs to, which helps when Google is assembling a knowledge panel or reconciling your site with your Google Business Profile listing. Keep the phone number and address identical to the ones on your profile.

LocalBusiness, with a caveat

Worth adding if you have a premises customers visit. Opening hours, area served, geo coordinates. But be clear about what it will not do: LocalBusiness markup does not get you into the map pack. That is driven by your Google Business Profile, your reviews and proximity. If someone sells you schema as a way to appear in local map results, they are selling you the wrong thing — the work you actually need is on the profile itself, and on the fields most owners leave blank.

Event, JobPosting, Video, Recipe — only if they describe you

These are narrow but strong when they fit. A training institute running batches, a company hiring regularly, a business whose pages are genuinely built around video. Event markup can put dates and venues in the listing. JobPosting can get a role into Google's jobs experience. If none of these describe your business, skip them entirely rather than force a fit.

What to skip, including things we could sell you

This is the more useful half of the article.

FAQ markup

For years the standard advice was to add FAQ schema to every service page so your listing showed expandable questions and took up double the space. In August 2023 Google announced it was limiting FAQ rich results to well-known, authoritative government and health sites. If you run a manufacturing unit in Patparganj or a clinic in Preet Vihar, you will not get those expandable questions. The markup is not harmful and costs nothing to leave in place, but paying for it as a deliverable in 2025 is paying for something that stopped working two years ago.

Answering real customer questions on the page is still very much worth doing — for the reader, and possibly for AI answers. Just not for the rich result.

HowTo markup

Same story, more final. Google dropped HowTo rich results. The step-by-step display it used to produce no longer appears in normal search results. Writing good instructional content is fine; wrapping it in HowTo schema achieves nothing visible.

Sitelinks search box

Google retired this one in late 2024. The little search field that occasionally appeared under a brand's result is gone. Any proposal that still lists it is a copy-paste from an old checklist.

Review and rating markup you generate yourself

This is the one to be firm about. Star ratings in search results are the most requested rich result and the most abused. Google's guidance does not support self-serving review content — reviews of a local business or an organisation collected and published by that business itself, on its own site, are not eligible for review snippets. So a plugin that lets you type in five testimonials and a 4.9 rating is generating markup that either gets ignored or gets you a manual action.

The route to visible stars is third-party: reviews on platforms Google trusts, or product reviews collected through a legitimate reviews provider with verification. Which brings you back to actually asking customers for reviews, patiently, on Google.

Everything-everywhere markup

Some plugins will add Article, WebPage, WebSite, Person, ImageObject and half a dozen other types to every URL. It rarely breaks anything. It also rarely does anything, and it makes real errors harder to spot in Search Console because the noise floor is high. Fewer types, correctly maintained, is a better position than forty types nobody checks.

How to add it, and how to check it is working

Use JSON-LD — a block of code in the page's head section. Google prefers it and it does not tangle with your page layout, so a theme change will not silently destroy it. Most content management systems have a way to insert it per page type.

Then check two things, and check them again a month later:

1. The Rich Results Test. Paste in a URL. It tells you which rich result types the page qualifies for and lists errors and warnings. Errors are blocking; warnings are usually optional fields.
2. The Enhancements reports in Search Console. This is the one people skip. It shows valid and invalid items across your whole site over time, which is how you catch the case where a template change broke price markup on 400 product pages. A single-URL test will never tell you that.

One practical note: eligibility is not a guarantee. A page can be technically perfect and still show a plain listing, because Google decides per query whether a rich result is useful. Do not let anyone promise you stars.

Does schema help with AI answers?

Honest answer: nobody outside the companies building these systems knows, and they have not published much.

The plausible case is that clean, explicit, machine-readable facts — your name, your address, your prices, your hours — make it less likely an AI assistant states something wrong about you. The argument against is that large language models are trained on text and appear to read pages much as a person would, so well-written visible content may matter more than the code behind it.

Our position is unexciting: keep the four or five schema types that already earn their place, because the search-result benefit is real and documented, and treat any AI benefit as a possible bonus rather than the reason. Be suspicious of anyone selling schema as the key to visibility in AI answers with confidence they cannot justify. The genuinely useful work there is making sure the facts about your business are consistent everywhere they appear.

What to do next

Pick your three most commercially important pages — a category page, a product or service page, and your homepage. Run each through the Rich Results Test and write down what comes back. Then open Search Console and look at the Enhancements section for errors you did not know about.

If what you find is Product markup with wrong prices, FAQ markup from 2021, and self-made review stars, you now know exactly which one to fix and which two to stop paying for. If you would rather someone audited it properly alongside the rest of your search work, or you need the markup wired into live product data rather than typed in by hand, tell us what you sell and where and we will tell you which of these types actually apply to you.

Questions we get asked