Ecommerce Website Development in Pune: How to Build a Product Review System That Is Honest, Trusted by Google and Safe From Fake Reviews
A trustworthy product review system does four things: it collects reviews only from people who actually bought, it publishes them under written rules (including the negative ones), it marks them up so Google can read them without breaking its guidelines, and it does all this without slowing the page. In ecommerce website development in Pune, that usually means choosing between a reviews app or plugin and a custom build, switching on verified-purchase flags, asking for reviews after delivery with permission, and never writing, buying or selectively deleting reviews. Google's own guidelines forbid fake or undisclosed incentivised reviews, and India's regulators and standards bodies are moving in the same direction.
This article is for owners and marketing leads of Indian online stores on Shopify or WooCommerce, and for the developers they brief. It covers platform options, verification, moderation, collecting reviews by email and WhatsApp, Google's structured data rules, the Indian regulatory picture, handling negative reviews, speed cost, a decision table and a launch checklist. It does not cover payments, shipping or tax. Facts come from Google Search Central, WooCommerce and Shopify documentation, WhatsApp's business policy and published summaries of Indian rules, read in October 2026. Policies change, so verify before you build. The Indian legal section is general information, not legal advice.
Why the system matters more than the widget
Our product page checklist covers where reviews sit on the page. This article covers the system behind them: where reviews are stored, who may post, who decides what is published and how they reach Google. We will not quote conversion lifts, as we have no trustworthy universal figure. The case is simpler: a system that can be gamed will eventually be gamed, and the damage lands on shopper trust, search appearance and legal exposure.
Ecommerce website development in Pune: app or plugin first
For most small and mid-size stores, an off-the-shelf tool is the right start. What differs by platform is how much comes built in.
Shopify. Shopify's own Product Reviews app was sunset and delisted in 2023 and removed from the store in May 2024, according to Shopify community and partner notices, with third-party apps such as Judge.me, Stamped.io, Yotpo, Loox and Okendo named as alternatives. In practice a Shopify store chooses a reviews app from the App Store, so the evaluation is about that app: where it stores reviews, how it verifies buyers, what it loads on the page and what happens to your reviews if you cancel.
WooCommerce. WooCommerce ships with native reviews. According to its documentation, under WooCommerce > Settings > Products you can enable star ratings, make ratings required, show a "verified owner" label and restrict reviews to verified owners. Reviews appear under Products > Reviews, where you can approve, unapprove, reply, edit, mark as spam or delete, and the system respects WordPress's comment moderation settings. Plugins add photo reviews, review requests and import tools on top.
When comparing any app or plugin, ask these questions before you install:
- Data ownership. Can you export every review, with dates, ratings and verified status, as a file? If you leave, do the reviews leave with you?
- Verification method. Is "verified" tied to an order in your own store, or can anyone type an email address?
- Moderation controls. Can you hold reviews for approval, and publish by rule rather than by rating?
- Structured data. Does it output Review and AggregateRating markup, and does that match what is visible on the page?
- Weight. What does it load on the product page, and when? (More on this below.)
Option 2: a custom review system
Custom means reviews live in your own database, tied to orders, with your own moderation screen and markup. It makes sense for unusual catalogues needing special attributes, headless storefronts, review data inside your own CRM, or when you want a third-party script off the product page. The cost is owning what an app provides: spam protection, email delivery, accessible forms, export and markup upkeep. For a few hundred products that is rarely worth it. Start with an app that exports cleanly; you own the data and can migrate later.
Decision table: which route suits which store
| Situation | Suggested route | Why | Watch out for |
|---|---|---|---|
| New WooCommerce store, modest catalogue | Native WooCommerce reviews with verified-owner settings, plus a small request plugin if needed | Built in, no extra script, order-linked verification | Basic features; design may need theme work |
| New Shopify store | A well-reviewed reviews app | Shopify's own reviews app is gone, so this is the standard route | Script weight, monthly fees, export terms |
| Growing store with many products and photo reviews | Mature app or plugin with photo and video support | Feature depth without build cost | Page-speed cost of widgets; check export |
| Headless or highly custom storefront | Custom reviews service, or an app with an API | Control over markup and loading | Ongoing maintenance and moderation tooling |
| Store already full of apps and slow | Replace a heavy widget with a lighter one or native reviews | Speed gain without losing reviews | Migration must preserve dates and verified flags |
Verified-purchase flags: what they should mean
A "verified buyer" badge is useful only if it means something specific: the review was submitted through a link or login tied to a real, delivered order for that product.
- Tie verification to the order, not the email. Use a unique order-linked token in the request.
- Show the flag only when true. Label imported or off-flow reviews differently.
- Mark incentivised reviews. Google requires clear and prominent disclosure, and the BIS standard (below) says incentivised reviews should be marked separately and not influence the overall rating.
- Decide on unverified reviews. On WooCommerce one setting restricts reviews to verified owners. Some stores keep questions in a separate Q&A area so the rating stays clean.
- Keep the record. Store order reference and dates internally in case a review is disputed.
A moderation workflow that does not turn into censorship
Moderation removes content that should not be public, not content you dislike. Write the rules down and apply them to every review regardless of rating.
Publish promptly. The BIS standard recommends publishing without undue delay, mentioning 72 hours where possible. A manual queue is fine if it is staffed that fast.
Remove or hold only for stated reasons: personal data; abusive or threatening language; content about delivery or a support call rather than the product (route it to support, do not just delete it); spam and links; reviews you have reason to think are not from a genuine customer, such as a burst of five-star reviews from new accounts in an hour; and allegations of crime or about named individuals.
Never remove a review because it is negative. Suppressing criticism is the quickest way to make a review section dishonest.
Log decisions (who, when, which rule) and publish a short "How our reviews work" page: who can review, how verification works, that you do not pay for positive reviews, what you remove and how to report a review. Transparency is a named principle in the BIS standard.
Watch for fakes: near-identical wording, many reviews from one device or IP range, reviews on products not yet shipped. Flag them for a human to check.
Collecting reviews after delivery: email and WhatsApp, with permission
Most customers will not review unprompted. A request sent a few days after delivery, when the product has been used, works better than one sent at dispatch. Your order system should trigger the request from the delivered status, not from the order date.
Email. Include the product name and image, a one-click star rating that opens the full form, and a plain line that you want honest feedback, good or bad. Do not route happy customers to a public page and unhappy ones to a private inbox. That is review gating; it skews your rating and sits uncomfortably close to selective publication. Offer help to everyone, alongside the public review link.
WhatsApp. WhatsApp works for review requests only within its rules. WhatsApp's Business Messaging Policy says you may only contact people on WhatsApp if they have given you their number and you have received opt-in permission from the recipient. It also says you must respect requests to opt out and give clear instructions on how to do so. So:
- Ask for opt-in at checkout with a clear, separate consent, not a pre-ticked box buried in terms. Say what messages they will get, such as order updates and a review request.
- Record the consent: time, wording and phone number.
- Send the request through the WhatsApp Business Platform, not a personal number.
- Make opting out easy and honour it immediately.
- Send one request and at most one reminder.
If you want this wired into your order flow, our WhatsApp Flow service covers order-triggered messaging. Take advice on data protection duties for stored phone numbers.
Incentives. If you reward reviews, keep the offer identical for positive and negative reviews, disclose it beside the review and never tie it to a rating. Where in doubt, offer none.
Google's rules for review markup
Google can show star ratings for your products in search if your pages carry valid structured data. The documentation sits in two places: Review snippet and Product snippet guidelines in Search Central. Here is what they say.
What is eligible. Google lists Product among the types that support review markup, alongside Book, Course, Event, LocalBusiness, Movie, Recipe and Software App. For a Product, the page must have a name and at least one of review, aggregateRating or offers. The page should focus on a single product or its variants, not a category or listing page.
What AggregateRating needs. The Product snippet documentation names ratingValue and reviewCount as required for aggregateRating. For individual reviews, the reviewer's name must be a valid name for a Person or Team; Google specifically warns against using promotional text, such as a Black Friday offer, as the author name.
The content must be visible. Google says the review content you mark up must be readily available to users on the marked-up page, and it must be immediately obvious that the page has review content. Do not mark up reviews that users cannot see.
Self-serving reviews. This is the rule that catches many sites. Google's guidelines say that if the entity being reviewed controls the reviews about itself, pages that use LocalBusiness or other Organization structured data are ineligible for the star review feature. The documentation's example includes a review placed on the reviewed entity's own site through an embedded third-party widget, such as Google Business or Facebook reviews. In plain terms: do not put review stars on your homepage or "About" page for your own business using Organization markup. The rule concerns LocalBusiness and Organization markup; customer reviews of a product, on that product's page, are the normal use of Product markup. Read the current page before you build, as guidance changes.
Fake and incentivised reviews. The guidelines say not to include fake or undisclosed incentivised reviews, giving as examples reviews not based on a genuine experience and reviews written in exchange for money, discounts, vouchers or free products without clear and prominent disclosure. Ratings must be sourced directly from users.
Implementation notes.
- Use JSON-LD, generated on the server, so markup is present when the page is crawled. Google's Product documentation warns that dynamically generated markup can make Shopping crawls less frequent and less reliable.
- If your reviews app injects the markup with JavaScript, test the rendered page, not just the source.
- Do not output two sets of markup, for example one from the theme and one from the app.
- Validate with the Rich Results Test and watch the Product snippets and Merchant listings reports in Search Console.
Markup makes a page eligible, not guaranteed. For wider structured data work, see our SEO services.
The Indian regulatory picture: general information, not legal advice
Several Indian instruments touch the subject. Treat this as a briefing for a conversation with a lawyer, not a substitute for one.
Consumer Protection Act, 2019. The Act defines an unfair trade practice to include adopting an unfair or deceptive method to promote the sale or supply of goods or services through false or misleading representations. It also created the Central Consumer Protection Authority (CCPA), which can act on matters affecting consumers as a class and can penalise false or misleading advertisements. Fake reviews used to promote a product can fall within the idea of a misleading representation.
Consumer Protection (E-Commerce) Rules, 2020. Legal summaries of the Rules state that sellers, and inventory-based e-commerce entities, must not falsely represent themselves as consumers and post reviews or ratings about their own goods or services. Read the current rule text with your adviser, and see our article on the 2026 consumer protection e-commerce rules.
CCPA's misleading advertisement guidelines. The CCPA's 2022 Guidelines for Prevention of Misleading Advertisements and Endorsements state that endorsements must reflect the genuine, reasonably current opinion of the endorser and be based on adequate information about the product. Penalties under Section 21 of the Act for false or misleading advertisement, as described in government material and commentary, go up to Rs 10 lakh, and up to Rs 50 lakh for repeated violations. A review you wrote yourself but presented as a customer's opinion is the kind of thing such provisions target.
BIS IS 19000:2022. In November 2022 the Bureau of Indian Standards published IS 19000:2022, "Online Consumer Reviews: Principles and Requirements for their Collection, Moderation and Publication". Commentary says it applies to any organisation that publishes consumer reviews online, including sellers collecting reviews from their own customers, and rests on seven principles: integrity, accuracy, privacy, security, transparency, accessibility and responsiveness. Notable requirements reported include screening for fraudulent content by automated or manual processes, publishing without undue delay (within 72 hours where possible), and marking incentivised reviews separately so they do not influence the overall rating. It also envisages a review administrator who is responsible for the process. Compliance has been described as voluntary, with a conformity assessment scheme planned. Check the BIS site for current status, and never display a conformity claim you cannot back.
What this means for your build. Whether or not you seek certification, the standard works as a design checklist: a named owner, a written policy, fraud screening, timely publication and disclosed incentives. For checkout and interface practices that regulators treat as manipulative, see our article on dark patterns and CCPA, since fake urgency and fake social proof are neighbours.
Handling negative reviews and takedown requests
A page of only five-star reviews looks curated. A few critical reviews, answered well, tend to read as more believable.
- Reply publicly, briefly and once. Acknowledge the specific issue, say what you will do and move details to a private channel. Do not argue or reveal order details.
- Remove only for rule-breaking (personal data, abuse, spam), not for disagreement. If a claim is false, reply with the facts.
- Takedown demands from third parties. Do not delete on the first email. Check the review against your policy and order record, keep a copy and take advice if there is a legal threat. Never offer a refund or discount in return for removal; that is buying a rating.
- Google or marketplace reviews follow those platforms' policies. Use their reporting tools, and do not copy those ratings into your own Organization markup.
- Suspected attack. Pause publishing for the product, preserve evidence (order IDs, timestamps, accounts), review by hand, then publish what is genuine.
The page-speed cost of review widgets
Reviews are heavy in a particular way: they are third-party-style code, often injected after load, on the page that matters most for sales. Our guide to store speed and Core Web Vitals explains the metrics. Google's thresholds are 2.5 seconds or less for Largest Contentful Paint, 200 milliseconds or less for Interaction to Next Paint and 0.1 or less for Cumulative Layout Shift, at the 75th percentile of real visits.
Typical harm: a late-appearing rating block causes layout shift (CLS); long review lists with filters and photo galleries make taps sticky (INP); widget scripts compete with the main product image (LCP); and many apps load on every page, including pages with no reviews.
What to do:
- Render the star summary and first few reviews on the server where possible; load the rest on demand, and reserve space for the block.
- Load the full widget after the page is interactive, only on pages that need it, and never lazy-load the main product image.
- Paginate reviews and load photos on request.
- Measure the product page with and without the widget on staging, on a mid-range Android phone, and decide with numbers.
A lighter widget with fewer features usually beats a feature-rich one that fails Core Web Vitals on the page where people decide to buy.
Launch checklist
- Reviews linked to delivered orders by unique tokens; verified label only where true
- Same request wording for every customer, no gating; one reminder at most
- WhatsApp requests only with recorded opt-in and simple opt-out
- Incentives disclosed beside the review and not tied to rating
- Written moderation rules, a named owner, a decision log and a public "How our reviews work" page
- Reviews published within a defined time, with a report-a-review option
- Product markup on single-product pages only, with ratingValue, reviewCount and valid reviewer names
- Marked-up reviews visible on the page; no stars via Organization markup for your own business; no duplicate markup from theme and app
- For the wider product markup that review ratings sit inside, see our guide to product schema for Shopify and WooCommerce
- Tested in the Rich Results Test; Search Console reports watched
- Space reserved for the rating block; widget cost measured on a mid-range phone
- Nobody on your team or agency posts reviews as a customer
- Consent wording and policy checked by a lawyer; data export tested
- Monthly check of spikes, complaints and removals
Working with Govindani Infotech
Govindani Infotech Pvt. Ltd. is a web design and development company in Pune. If you are choosing a reviews app, moving off one, or want a review system that is order-linked, moderated by written rules and light on the page, we can scope it with you. Our ecommerce services and website creation services pages describe how we approach store builds, and the contact page is the quickest route to start a conversation.
To discuss your store, message us on WhatsApp. Please send your store URL, platform and the review tool you use today.
Frequently Asked Questions
Can I write or buy reviews to get my new store started?
No. Google's guidelines say not to include fake reviews, meaning reviews that are not based on a genuine experience, and Indian rules and standards treat posing as a consumer to review your own products as deceptive. Start by asking real buyers after delivery, and be honest that the product is new.
Will my product pages show star ratings in Google search?
They can be eligible if the page has valid Product markup with review or aggregateRating data, visible reviews and a single product focus. Google does not guarantee that stars will appear, so validate your markup and check Search Console rather than expecting a result.
Is it legal to offer a discount in exchange for a review?
General information, not legal advice: Google requires clear and prominent disclosure of any benefit given for a review, and the BIS standard says incentivised reviews should be marked separately and kept out of the overall rating. Ask a lawyer about your specific scheme, and avoid rewards linked to a positive rating.
Is the BIS IS 19000:2022 standard mandatory for my store?
Published commentary describes the standard as voluntary, with a conformity assessment scheme planned. Check the Bureau of Indian Standards site for current status, and use it as a design guide even if you do not seek certification.
Do review apps slow down my store?
They can, mainly through late-loading scripts that cause layout shift and sluggish taps. Measure your product page with and without the widget, reserve space for the rating block, load the full review list after the page is interactive and compare the result against Google's Core Web Vitals thresholds.