E-commerce14 min read•

Ecommerce Website Development in Pune: Building the Product Page — Structure, Variants, Stock States and Product Markup That Matches What Shoppers See

How to structure an online store product page: images, price, delivery, variants, stock states and Product markup that matches the visible page.

#ecommerce website development Pune#product page#Product schema#merchant listings#online store

A good online store product page does five jobs in one screen: it shows the product clearly, states the price and delivery honestly, answers the questions a buyer would otherwise phone about, makes the buy button impossible to miss on a mobile, and describes itself to search engines in structured data that matches what is visible. If you are commissioning ecommerce website development in Pune, this is the page template worth getting right first, because every product you ever list will use it. This guide walks through the structure of that page, the content it needs, how variants and stock states should behave, and how Product markup relates to Google's merchant listing features.

It is for store owners, merchandisers and developers working on Shopify, WooCommerce or a custom build. It does not cover payments, tax or shipping rate policy, which are separate subjects; it covers the page itself. Everything about Google's markup requirements comes from Google's current documentation, and where we could not confirm a detail we say so rather than guess.

The Job of a Product Page

A visitor arrives on a product page from a search, an ad, a WhatsApp link or a category page. They have one question: is this the right thing, and can I trust this shop to deliver it? The page has to answer both without making them hunt. When it fails, the usual symptom is the buyer leaving to ask a question by phone or WhatsApp, or not asking at all.

It helps to design the page around questions rather than around fields in a database. A buyer of a kurta asks: what is it made of, what size will fit me, what colour is it really, when will it arrive, can I return it. A buyer of a mixer grinder asks: what wattage, how many jars, what warranty, who services it. The template should have a place for each answer, and the data entry process should make it hard to forget them.

The Structure, From the Top of the Screen Down

Product name and a short summary

Use the name a customer would use, not an internal SKU code. Put the name in the single H1 of the page. Directly beneath, a one- or two-line summary of what the product is and who it suits is more useful than a paragraph of adjectives.

Images and video

Images carry most of the decision. Our separate guide to product photography briefs covers shot lists and specifications, so here we cover the page behaviour: show the main image large, allow zoom on mobile with a pinch, keep a thumbnail strip or swipe gallery, and make sure images have real alt text describing the product. Load the first image eagerly and the rest lazily so that the page does not feel slow, which ties into Core Web Vitals concerns.

Price, availability and the buy button

Show the current price in rupees, any sale price alongside the original, and a plain statement of whether tax is included. If you are unsure how to display tax inclusion, ask your accountant. Show stock state in words: In stock, Only a few left (only if true), Out of stock, or Available for pre-order with a date. The buy button should be the most prominent control on the page, and on mobile a sticky bar with price and button is common. Make sure it does not cover the content it is meant to help sell.

Delivery and returns, near the button

A buyer deciding whether to press the button wants to know when it arrives and what happens if it is wrong. A PIN code check that returns an estimated delivery window, and a one-line returns summary with a link to the full policy, belong close to the buy button, not buried in a footer. Be careful to state only what your logistics and policy actually deliver. If a delivery estimate is a range, say so.

Description, specifications and fit information

Split descriptive copy from specifications. Copy tells the story and the use; specifications are a scannable list or table of facts: dimensions, materials, weight, warranty, what is in the box. For clothing, a size chart with measurements matters more than any amount of marketing copy. For electronics, the specification table is what comparison shoppers read first.

Reviews and questions

Show genuine reviews, collected from real buyers, with the date. Do not invent or purchase them; marking up fake reviews is explicitly against Google's structured data guidelines. A short on-page questions and answers area, or a link to your WhatsApp support, helps with the questions the description missed. Our article on building a help centre for an online store shows how to reduce repeat questions across the whole store.

Related products

Related items are useful when they are genuinely related: a case for the phone, the next size up, the matching dupatta. Randomly chosen or bestseller-only widgets add noise. Keep them below the main purchase content.

Variants: Size, Colour and the Rules That Keep Them Honest

Variants cause more product page bugs than anything else. The principles are simple:

  • Show variant state clearly. The selected colour and size should be visible, and unavailable combinations should be shown as unavailable rather than silently failing at the cart.
  • Change what changes. Selecting a colour should swap the main image. Selecting a size should update the price if prices differ, and the stock state.
  • Give each variant its own identifier. A distinct SKU per variant lets stock, orders and feeds stay accurate. This matters for syncing with billing software, as our inventory sync guide explains.
  • Decide on URLs deliberately. Either each variant has its own URL, or one URL covers all variants with a parameter. Both can work. What does not work is an unpredictable mixture that creates duplicate or conflicting pages.
  • Keep the default sensible. Preselect the variant that is in stock and most commonly bought, rather than a blank selector that makes the buy button inert.

Stock States and Edge Cases

How the page behaves when something goes wrong decides whether a shopper stays.

  • Out of stock: keep the page live if it has traffic and history, show a clear message, and offer a back-in-stock notification or alternatives. Deleting the page throws away its search visibility.
  • Discontinued permanently: if there is a close replacement, redirect to it; if not, keep the page with a clear note or redirect to the category. Do not return a confusing error.
  • Price changes: make sure the displayed price, the cart price and any structured data price all come from the same source, so a sale ending does not leave an old price in one place.
  • Pre-orders: state the expected date and what happens if it slips.
  • Made-to-order: state the lead time up front, since a buyer who expects next-day delivery will be upset.

Product Structured Data: What Google Documents

Product markup describes a product page to search engines in a standard vocabulary. Google's documentation distinguishes two related features. Product snippets are for pages where people cannot buy directly, such as review pages. Merchant listings are for pages where customers can buy from you, and they allow more detailed product information such as size specifications, shipping details and return policy. Meeting the merchant listing requirements can also make a page eligible for product snippets.

According to Google's merchant listing documentation, the required properties are:

  • name: the product name.
  • image: product photo URLs; Google recommends several high-resolution images in different aspect ratios.
  • offers: a nested Offer, not an AggregateOffer, because for merchant listings the seller must be the merchant.
  • Within the Offer, price (the current active price, which must be above zero) and priceCurrency (a three-letter ISO 4217 code such as INR).

Availability is listed as recommended rather than required, along with properties such as brand, sku, GTIN where you have one, description, aggregate rating and review where genuine, and on the offer: item condition, shipping details, merchant return policy, and the validity dates of the price.

A minimal illustrative block for a made-up product follows. The values are placeholders.

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Example Cotton Kurta, Indigo, Size M",
  "image": ["https://www.example.com/images/kurta-indigo-1.jpg"],
  "description": "Straight-cut cotton kurta with a mandarin collar.",
  "sku": "KURTA-IND-M",
  "brand": { "@type": "Brand", "name": "Example Label" },
  "offers": {
    "@type": "Offer",
    "price": "1499.00",
    "priceCurrency": "INR",
    "availability": "https://schema.org/InStock",
    "url": "https://www.example.com/products/kurta-indigo/"
  }
}

Rules that keep markup safe

  1. Mark up only what is visible. Google's general guidelines say markup must describe content users can see on the page. The price in the markup should be the price a visitor sees. We could not confirm from the merchant listing page alone an explicit price-matching sentence, but the general visible-content rule covers it and a mismatch is simply poor practice.
  2. Use real reviews only. If the page shows multiple reviews, Google's guidelines say to mark up all of them, and never to mark up fake or misleading ones.
  3. Do not block the page. Pages carrying structured data must be crawlable. Do not disallow them in robots.txt or noindex them.
  4. One source of truth. Generate markup from the same product record that renders the page, so changing the price changes both.
  5. Valid markup is not a promise. Google says it does not guarantee that a rich result will display.

Shopify and WooCommerce specifics

Many Shopify themes and WooCommerce setups output Product markup by default. The common faults are duplicates (theme plus SEO app plus plugin), missing currency, stale prices when sale pricing is scheduled, and variant markup that describes only the default variant. Check a few real product pages in the page source, and in testing tools, before buying another app. Our Shopify vs WooCommerce comparison explains which platform suits which kind of shop, and the guide to local business markup covers the rest of the site's schema.

Merchant Listings and the Free Listing Route

Product markup is one way to give Google product information. Google also has a separate product-feed route through its merchant tools, where you upload a catalogue. Details of those programmes, eligibility and country availability change, and we did not verify current India-specific terms for this article. Check Google's Merchant Center help pages for the current position before you plan around them. What we can say is that clean product data, with consistent names, prices, images and identifiers, helps whichever route you take.

Mobile First, Because Most Shoppers Are

Test the page on a real mid-range Android phone, on mobile data, not only in a desktop browser narrowed to phone width. Check:

  • The first image appears quickly and does not jump when the page finishes loading.
  • Tap targets for variants are big enough for a thumb.
  • The sticky buy bar does not hide the delivery information.
  • The keyboard type for the PIN code field is numeric. Our guide to the checkout address form covers that.
  • Text can be read without zooming.

Writing Product Copy That Does Not Repeat the Supplier

A frequent weakness on Indian online stores is copy pasted from a supplier's catalogue or a marketplace listing. Search engines see the same paragraph on dozens of sites, and buyers see nothing that tells them why to buy from you. You do not need long copy. You need accurate copy in your own words, written from the product in front of you.

A simple pattern works for most products. Start with one sentence on what it is and who it suits. Follow with three to five facts a buyer can verify, such as fabric, dimensions, capacity or what is in the box. Add one line on care or use. If you have handled the product yourself, say something you noticed: how the fabric feels after a wash, how heavy the unit is, whether the colour in the photo matches daylight. That kind of observation cannot be copied from a catalogue and tends to reduce returns.

Avoid claims you cannot support. Words like "best", "premium" and "100% genuine" tell a buyer nothing, and statements about certifications, materials or warranty should match your paperwork. If a claim is regulated or could be disputed, check it before it goes live.

Measuring Whether the Page Works

Without measurement, you are guessing. Useful signals, in order of ease:

  1. Add-to-cart rate per product page view, by product type and device.
  2. Questions asked by phone or WhatsApp, logged by topic. Repeated questions show a content gap on the page.
  3. Returns reasons. If many returns say "colour different from the photo", fix the images, not the policy.
  4. Search Console, to see which product queries bring impressions and clicks, and whether the page appears for the terms you intended.
  5. Session recordings or heatmaps, if you use them, with attention to privacy and consent.

Change one thing at a time where you can, and give a change enough traffic before judging it. With a small store, a week may show nothing; do not declare victory or failure from ten visits.

A Product Page Template Checklist

Use this before launching a new store or reworking an old template.

  1. One H1 with the natural product name.
  2. Large, zoomable main image with descriptive alt text, and extra angles.
  3. Price in rupees, sale price handled clearly, tax inclusion stated.
  4. Stock state in words, accurate in real time.
  5. Prominent buy button, sticky on mobile.
  6. PIN code delivery estimate and one-line returns summary near the button.
  7. Specifications separate from descriptive copy; size chart where relevant.
  8. Genuine reviews with dates; no invented ones.
  9. Variants with their own SKUs and clear unavailable states.
  10. Product markup generated from the same data, with name, image, offer price and currency present.
  11. Crawlable and indexable, with a sensible canonical URL.
  12. Tested on a real phone.

What a Quotation Should Say

When you get a quotation for store development, look for a line on product page templates. Ask what is included: number of templates, variant handling, delivery estimate by PIN code, structured data, review display, and mobile testing. A vague "product page design" with no detail is where scope disputes later start. Our ecommerce website development guide for Pune lists other items worth asking about.

Frequently Asked Questions

What should a product page include?

At minimum: a clear name, good images, price in rupees, stock state, a visible buy button, delivery and returns information near the button, specifications, and genuine reviews if you have them.

Do I need Product schema on every product page?

Product markup is optional but useful where it is accurate. Google's merchant listing documentation lists name, image, and an Offer with price and currency as required properties. Generate it from the same data as the visible page.

Can I mark up reviews on my product pages?

Only genuine reviews that are visible on the page. Google's guidelines warn against marking up fake or misleading reviews, and say that if a page shows multiple reviews you should mark up all of them.

Should I delete the page for an out-of-stock product?

Usually not. Keep it live with a clear message and alternatives or a back-in-stock option, so the page keeps its history. Redirect to a close replacement if the product is discontinued.

Does valid Product markup guarantee rich results in Google?

No. Google says valid markup does not guarantee that a rich result will be shown. The markup makes the page eligible; the algorithm decides.

Planning an Online Store Template?

Govindani Infotech, a website design and development company at 2nd Floor, Landmark Plaza, 206 Satara Road, Parvati Paytha, Pune 411009, builds online stores on WooCommerce, Shopify and custom stacks. See our ecommerce services and website creation services, then contact us or call 092019 58274.

Sources:

About the author: written by the Govindani Infotech ecommerce development team in Pune.

Need Help With Your Digital Strategy?

Govindani Infotech helps Indian businesses and NGOs build websites, run ads, and grow online. Contact us for a free consultation.