Web Development Company in Pune: Which Structured Data (Schema Markup) Your Business Website Actually Needs

Structured Data for Business Websites: What to Ask a Web Development Company in Pune to Build

A good web development company in Pune should add structured data (schema markup) to your website as part of the build: an Organization or LocalBusiness block on the home and contact pages, BreadcrumbList on inner pages, Article on blog posts, Product on product pages and Service on service pages, all written as JSON-LD, all matching what a visitor can actually see, and all tested before launch. Structured data does not push a page up the rankings by itself. What it does is tell search engines, in a format they can read without guessing, who you are, where you are, what you sell and how the pages relate to each other, which makes you eligible for the richer results Google is willing to show.

This guide is for a business owner or marketing manager who has heard the term from an SEO report or an agency proposal and wants to know what is worth paying for. It covers the types that matter, what each one needs, what to ignore (including a few types that no longer produce anything visible), how to test, and the mistakes that cause markup to be ignored or, worse, to trigger a manual action.

What structured data is, in plain terms

Search engines read the words on your page and make educated guesses. A line reading "2nd Floor, Landmark Plaza, 206 Satara Road" is probably an address. "Rs 1,499" is probably a price. "4.6" next to some stars is probably a rating. Structured data removes the guessing by labelling those facts in a standard vocabulary, schema.org, which Google, Bing and other engines all support.

The format Google recommends is JSON-LD: a block of JSON inside a <script type="application/ld+json"> tag, separate from the visible HTML. It is easier to maintain than the older microdata approach because it sits in one place rather than being threaded through your page markup.

A minimal example for a business looks like this:

{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Example Business Name",
  "url": "https://www.example.com/",
  "telephone": "+91-XXXXXXXXXX",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "Your street address",
    "addressLocality": "Pune",
    "addressRegion": "Maharashtra",
    "postalCode": "411009",
    "addressCountry": "IN"
  }
}

The values above are placeholders. Yours must be the real details, identical to what appears on your contact page and your Google Business Profile.

What structured data does and does not do

Be clear on this before you pay for it, because it is where most of the exaggeration in proposals sits.

• It does not directly improve ranking. Google's own guidance describes structured data as helping it understand content and making pages eligible for enhanced appearances in search. It is not a ranking switch.
• It can improve how a result looks, for example breadcrumbs in place of a raw URL, product details, or review stars where the type and the page qualify. A better-looking result can attract more clicks, but nobody can promise a number.
• It helps machines resolve who you are. Consistent Organization details, links to your official profiles and a clean site structure reduce the chance of your business being confused with a similarly named one.
• It has no effect if it is wrong. Markup that contradicts the page is ignored at best. Markup that describes things a visitor cannot see, or that is fabricated, can lead to a manual action against the site.

The rest of this article assumes you want the benefits without the risk.

Which schema types a business website in Pune actually needs

You do not need thirty types. You need the handful that match what your site is and does. Here is the practical shortlist.

Everything else, such as Event, Course, JobPosting or Recipe, applies only if your site really publishes that kind of content.

Organization versus LocalBusiness

Use LocalBusiness (or one of its more specific subtypes, such as a professional service, a store or a medical clinic type) when customers visit or you serve a defined area from a physical address. Use Organization when you are not location-bound, for example an online-only brand. If you have both an office and an online store, one Organization block for the brand and one LocalBusiness block on the page that describes the location is a sensible split. Ask your developer to link them with a shared @id so they are clearly the same entity.

Properties worth filling in properly

For a business, the ones that pay for themselves are:

1. name exactly as you trade, matching your signage, invoices and Business Profile.
2. address as a full PostalAddress, including postal code.
3. telephone in international format.
4. url and logo pointing to real, crawlable files.
5. openingHoursSpecification if customers visit; leave it out if you are appointment-only rather than publishing something inaccurate.
6. sameAs listing your official profiles: LinkedIn, Instagram, YouTube, Facebook, your Google Business Profile URL.
7. geo coordinates if you have a physical location customers navigate to.

Consistency matters more than volume. If the address in your markup, your footer and your Business Profile differ by even a floor number, you have created a small trust problem for automated systems.

The types most sites get wrong, and how

BreadcrumbList

Breadcrumbs are the least glamorous and most reliably useful type. They tell Google how a page sits in your hierarchy (Home, Services, Website Creation) and can replace a long URL under your title in results. The common failure is a breadcrumb in markup that has no equivalent on the page. Keep them identical: if the visible trail says Home / Blog / Post title, so should the markup.

Product and Offer for online stores

For an online store, Product markup is where structured data can influence the look of your results the most, but it is also where errors are most costly. What the markup must contain is a name, images, a description and an Offer with price, currency (INR) and availability. What it must never do is disagree with the visible page. If a price changes with a sale, the markup has to change with it, which means it should be generated from the same data as the page, not typed in by hand.

If you run WooCommerce or Shopify, most themes and plugins output Product markup for you. The job of your developer is to check what is emitted, fix it where it is wrong (for example, variant products showing a single price, or out-of-stock items still marked as available) and make sure two plugins are not both outputting competing blocks. Duplicate, conflicting Product blocks on one page are one of the most common issues we see when auditing WordPress stores.

Review and rating markup deserves particular care. Only mark up reviews that are genuine, visible on the page and about the product on that page. Marking up ratings you wrote yourself, or copying a rating from a third-party site, is against Google's guidelines. Do not let anyone talk you into it.

Article and BlogPosting

For blog posts, Article markup identifies the headline, author, publication date, modification date and lead image. Three details are worth checking. First, datePublished and dateModified must be real and in a standard format. Second, the author should be a genuine named person or your organisation, not a placeholder. Third, the headline in markup should match the visible title.

Service

There is no dedicated "service rich result", so Service markup is about clarity rather than display. It lets you state, in machine-readable form, what the service is, who provides it (your Organization) and the area served. It is useful, cheap to add, and should describe only what the page actually offers. Do not include prices in markup unless the same prices are published on the page.

Types that no longer earn you anything visible

This is the part that most often saves money. Google has narrowed which structured data produces visible results, and some proposals still sell markup that no longer does anything in a normal search result.

• FAQPage. Since 2023, Google shows FAQ rich results only for well-known, authoritative government and health websites. For a business site in Pune, FAQ markup will very likely not produce an expanded result. That does not make the FAQ section pointless. A visible FAQ still answers real questions for your visitors and can help you match the way people phrase searches. Add the markup if it costs nothing extra, but do not pay a premium for it or expect stars and dropdowns.
• HowTo. Google has also stopped showing HowTo rich results. Write good step-by-step content for readers; do not pay for markup on the expectation of a special appearance.
• Site-search boxes and other retired features. If a proposal lists features you cannot find on Google's current structured data gallery, ask why.

The lesson is to check any proposal against Google's current Search Central documentation, not against a blog post from three years ago, including this one. Support for types changes, and your developer should verify before building.

How structured data should be added: template, plugin or hand-coded

There are three realistic ways to do it, and the right one depends on your platform.

On WordPress

An established SEO plugin can output Organization, WebSite, BreadcrumbList and Article markup from settings you fill in once. This is a sound default for most business sites. The risks are misconfiguration (the wrong logo, an outdated address), several plugins outputting overlapping markup, and page builders or themes adding their own blocks on top. A developer should inspect the rendered page source, not just the plugin settings screen.

On Shopify and WooCommerce stores

Themes usually emit Product markup. Audit it against real products, especially variants, sale prices, stock status and multi-currency or GST-inclusive pricing. Your GST display setting decides whether the visible price is inclusive; the markup price should match what the customer sees.

On a custom-built or React site

Here the developer writes JSON-LD in code, ideally generated from the same data that renders the page. A subtle issue is rendering. If the markup is injected only by JavaScript after the page loads, some crawlers may not see it reliably. The safer pattern is to include it in the server-rendered or pre-rendered HTML. If your site is a single-page application, ask specifically how markup reaches the HTML that crawlers receive.

This is also a fair test of a developer's competence. Ask them to show you the page source of a page they built and point to the JSON-LD. If they cannot, that is informative.

A worked example: what a small service business should ship

Consider a fictional services firm in Pune with a home page, five service pages, a contact page and a blog. A sensible structured data plan looks like this, and would be a modest amount of work rather than a large project.

1. Home page: Organization block with name, logo, URL, contact details and sameAs links.
2. Contact page: LocalBusiness block with address, phone and opening hours that match the Business Profile exactly, linked to the Organization by @id.
3. Each service page: Service block naming the service, the provider (by @id) and the area served, plus BreadcrumbList.
4. Blog posts: Article or BlogPosting with real dates and a named author, plus BreadcrumbList.
5. Visible FAQ on key pages: written for readers first, with FAQPage markup optional and expectation set at zero for rich results.

No fabricated ratings, no invented awards, no price ranges the business does not publish. The plan is short precisely because most of the value comes from getting a few types right and consistent.

How to test and monitor

Structured data is easy to break silently: a theme update, a plugin change or a redesign can remove or duplicate it without any visible sign. Build testing into the project.

1. Before launch, run key pages through Google's Rich Results Test to see which rich result types are detected and whether there are errors or warnings. Use the Schema Markup Validator to check syntax against the schema.org vocabulary in general, since it covers types Google does not display.
2. After launch, verify the site in Google Search Console and watch the Enhancements and Products sections, which report valid items, warnings and errors for the types Google supports on your site.
3. After every redesign or major plugin update, re-test a sample page of each template.
4. Compare markup to page. Open the page, open the source, and check that every fact in the JSON-LD is visible on the page.

Errors block eligibility for rich results; warnings usually flag optional properties. Treat errors as bugs and warnings as judgement calls.

Mistakes that get markup ignored, or worse

• Marking up content that is not on the page. Google's guidelines require markup to represent visible content. Hidden text used to hold markup facts is a spam pattern.
• Fake or self-written reviews and ratings. A common route to a manual action.
• Prices or availability that do not match the page. Frequently caused by caching or by hand-typed values.
• Wrong or inconsistent business details. A different phone number in markup than on the page, or an old address left in a theme option.
• Copying another site's markup wholesale. Including their name, logo or ratings, which happens more often than you would expect with template sites.
• Stacking multiple plugins that each emit their own Organization or Product block.
• Setting and forgetting. Markup that was correct in 2024 may describe a service you no longer offer.

What to put in a proposal, and what it might reasonably cost

Ask your web development company to write structured data into the scope explicitly, with a list of types by page template, a testing step and a line saying how errors will be reported. Vague wording such as "schema included" can mean anything from a plugin toggle to a proper implementation.

We do not publish a fixed price for this because it depends on your platform and the number of templates. As a rule of thumb, a small brochure site should treat structured data as part of the normal build rather than a separately priced extra, while an online store with many product variants, multiple currencies or a custom theme will need more careful auditing and testing time. Ask for the hours and the deliverable, not a headline figure. If a quote treats "schema" as a large recurring monthly line item for a small site, ask what changes each month.

Related: another small search-appearance detail is your logo beside the result; see why your favicon does not show in Google.

Related: see our guide to writing LocalBusiness markup with name, address, phone and opening hours.

Structured data works alongside the title and description Google shows; our guide to writing page titles and meta descriptions covers the snippet text itself.

Frequently Asked Questions

Does schema markup improve Google rankings?

Not directly. Google describes structured data as a way to help it understand a page and to make the page eligible for enhanced results such as breadcrumbs or product details. Better-looking results can lift click-through, but markup is not a ranking lever on its own, and no one can promise a position because of it.

Which schema types does a small business website need?

Most need Organization or LocalBusiness on the home and contact pages, BreadcrumbList on inner pages, Article on blog posts and Service on service pages. Online stores add Product with Offer. Add other types only if your site really publishes that content.

Is FAQ schema still worth adding?

Google now shows FAQ rich results mainly for well-known government and health sites, so a typical business site should not expect the expanded result. A visible FAQ section is still useful for readers. Add the markup only if it costs you nothing extra, and only for questions that appear on the page.

How do I check my website's structured data?

Run pages through Google's Rich Results Test for supported types and the Schema Markup Validator for general syntax. After launch, use the Enhancements and Products reports in Google Search Console to catch errors that appear later.

Can wrong structured data hurt my site?

Yes. Markup that describes content visitors cannot see, fabricated ratings, or details that contradict the page can be ignored or can lead to a manual action, which removes rich result eligibility for the site. Accuracy and consistency are the whole job.

Where to Start

Write down your business name, address, phone number and opening hours exactly as they should appear everywhere, then check they match on your website, your Google Business Profile and your social profiles. That single consistency check is worth more than any plugin. Next, list your page templates and ask your developer which schema type each one will carry and how it will be tested.

Govindani Infotech Pvt. Ltd. is a website design and development company at 2nd Floor, Landmark Plaza, 206 Satara Road, Parvati Paytha, Pune 411009. Our website creation service includes technical SEO groundwork such as structured data, and our SEO service covers auditing and monitoring it over time. To go deeper on related topics, see our guides on local SEO for the Google map pack in Pune, accessibility and Core Web Vitals for a website designer in Pune and controlling AI crawlers with robots.txt and llms.txt. If you would like a second opinion on the markup on your current site, talk to our team on WhatsApp or use the contact page.