A NexBuilt guide · 5 September 2026
What is schema markup and does a small business need it?
Schema is extra labelling on a page so Google can understand it. What Google actually says, and when a Delhi shop should care.
Schema markup is extra labelling in the page code that names what the page is, in a form machines can read. A restaurant in Khan Market or a dental clinic in Green Park needs it only after the page already opens and tells the truth. Markup on a theme that takes a wait longer than they will sit is jewellery on a closed door.
Google’s introduction to structured data says you can help Search understand a page by giving explicit clues, in a standardised format, about the content on that page. Most of that markup uses schema.org words. Google says to treat its own documentation as the rule for how Search behaves.
What it is not
It is not a Google Business Profile. The profile is a listing you claim. What a Google Business Profile is is that job. Whether the listing is enough is the split.
It is not a paid rank. Local ranking notes say relevance, distance and prominence decide the pack. Schema will not buy the pack either.
It is not AEO. AEO and GEO are labels. Google’s structured data page is about understanding the page and richer results, not about a new product named AEO.
Does a small shop need it
Need is the wrong first word. Need a page a stranger can use. Then, if the page has a real type Google documents, a FAQ, a restaurant menu, a local business, markup can make that type clearer.
I will not tell you every gym in Dwarka must ship JSON-LD tomorrow. I will not tell you markup alone brought anyone a chair. I have not run that study. I will say this site’s own pages carry a graph so the questions on the page and the questions in the data cannot drift. That is a build choice, not a promise about your traffic.
A website starts at Rs 30,000 on pricing. I will not add a second “schema fee” on this page. If the page needs those clues, they go in the page.
How to think about it without a developer lecture
Imagine a menu photo versus a list of dishes as text. The photo is for people. The list is for people and for a machine. Schema is closer to the list. If your only menu is a blurry image, markup cannot invent the dal.
A Khan Market kitchen that posts a phone photo of last season’s card has given Search nothing it can name. Schema cannot read the dal off that JPEG. Type the dishes, the hours and the Jain note as text first. Label them after the text is true. A Green Park clinic that only uploads a waiting-room selfie has the same hole. Markup cannot invent the fee list from a smile.
Text first, then the label
I will walk a Khan Market owner through this in that order. Open the page on a phone. Can a stranger read tonight’s hours and three dishes without pinching a photo. If no, type those lines. Then, if Google documents a restaurant type for that page, add the clues. Do not buy a “schema package” while the only menu is a JPEG from last winter.
A Defence Colony clinic that already has a readable services list can add LocalBusiness clues in the same build. That is not a second invoice. It is part of making the page say the same thing in code that it says in words. I still will not promise a richer result. Eligibility is what Google’s intro claims.
If the page takes a wait longer than they will sit, stop talking about markup. People leave after three seconds. Jewellery on a closed door is still a closed door.
Keep the markup true. Google’s introduction says the structured data describes the content of that page. Labelling a closed clinic as open is a lie in code. That is a downside I will not skip.
What I will not tell you
I will not tell you a plugin “does schema” and therefore the site is fine. Open the phone test. People leave after three seconds.
I will not tell you rich results are guaranteed if the markup validates. Google’s own intro is about eligibility, not a promise that the richer look will show.
Write or from hours, if the URL already opens.
What to do before you buy markup
Open the page. If the hours are wrong, fix the hours. If the page never arrives, fix the wait. Markup is a later sentence.
Then get in touch if the page is real and you want the labelling said in plain words. Bring the URL. I will say the page needs clues, the page needs speed first, or the listing is the hole and schema can wait.