Reviews and ratings: search stars without the risk of sanctions
Reviews and ratings in an online store are three separate jobs: to collect ratings from customers, display them on the page and describe them with structured data so that the search engine has a reason for stars. The procedure is exactly this, and it cannot be changed: marking without real feedback does not give stars, but a reason for manual sanctions. In our own project, we found exactly that - the code declared a rating of 4.8 with 50 ratings, and there was no feedback on the page. Therefore, the work begins with the analysis of what is already standing.
collection of feedback after purchase, moderation with store responses, marking of the rating for visible content
after a free audit
Price
30
Guarantee
days after project sign-off
collection of feedback after purchase, moderation with store responses, marking of the rating for visible content
Three jobs in one service
8–25
Term
working days: the lower limit is when there are already reviews, the upper limit is when the collection needs to be built from scratch
free feedback check and markup, 2-3 business days
Before the estimate
rating 4.8 with 50 ratings in structured data with zero mentions of the word "feedback" on the page - our own project, measurement 07/31/2026
Measured find
garden tool store: 1,300 unique addresses in the directory and JSON-LD on the main - only Organization and ContactPoint
The second measured finding
the appearance of stars in the output: the markup gives the reason, the decision is made by the search engine
What we do not promise
Who it's for
Situations where this service delivers results
Scenario 1 of 4
Sales are going on, but the product card is empty
The order is there, there are few returns, but the person who came in for the first time does not see any confirmation from other buyers. She either goes to read about your product on the site, or does not buy at all. What is needed is not a rating for the sake of stars, but a mechanism that brings feedback from the buyer to the page: a request after receipt, a direct link to the desired product, a one-touch rating.
We'll review your situation in a free audit
Scenario 2 of 4
The marking was put by the contractor, and you do not know what is in it
The most common case and the most expensive. A topic or module could kill the rating in structured data "for beauty": there is a number, but there are no ratings for it. The owner will learn about it from a letter in the webmaster panel when the stars have already disappeared. It gets tested in half a day, and manual sanctions are removed in months - so we start with code analysis, not new features.
Scenario 3 of 4
Reviews are collected externally, but they are not visible on the website
In the garden tool store we measured, there is a Google feedback module: the source is alive, the ratings are there, but the catalog page knows nothing about them. The task here is the opposite of collecting — not to drag other people's numbers into your markup, because this is again a self-assigned rating, but to get your own reviews and show them.
Scenario 4 of 4
The product is chosen for a long time and compared
Tools, machinery, equipment, expensive equipment. The decision is made not by a photo, but by someone else's experience: how it behaves after the season, what is in the kit, whether it is suitable for a specific task. A catalog like this needs extensive reviews with photos and store responses below them, not an average rating with two decimal places.
Cases
Tasks and results in numbers — all metrics measured by us
Ukrainian platform for automatic rewriting of product descriptions
Task
Check the technical health of the web application: speed, structured data, sitemap and markup risks.
Solution
Speed and weight measurement, list of public pages, analysis of all blocks of structured data with verification of compliance with visible content, verification of sitemap and robots.txt.
Result
TTFB of 220.6 ms at 140.8 KB of HTML, the fastest response of the 16 sites measured. 8 public pages, connected application manifest. Risk found: the structured data declared a rating of 4.8 with 50 ratings, while the page does not contain any mention of the words "review", "review" or "rating" - the markup declares 50 ratings, which do not exist on the page; this is a direct reason for manual sanctions for self-imposed feedback marking. Optional: robots.txt links to a sitemap that returns a 404.
online store of the official seller of garden tools
Task
Assess the technical condition of the store, in particular the set of connected external services and the state of structured data.
Solution
Speed and weight measurement, analysis of the site map for the uniqueness of addresses, checking of structured data and the list of integrations.
Result
The site map has 1,300 unique addresses — about 1,213 product cards and 70 categories. TTFB 625ms, full load 752.5ms at 350.4KB HTML. External Google feedback module, sales platform, messengers are connected. Found: structured data on the main page is limited to organization and contacts — there is no markup of goods and breadcrumbs, that is, the site did not provide grounds for an extended snippet with a rating.
What's included
Complete list of work and what you get as a result
A product review and a store review are two separate entities: each has its own markup, so the delivery rating is not mixed with the product rating.
Evaluation by criteria, if the niche requires it - correspondence to the description, quality, delivery: you can see why they gave four stars.
Feedback request after receiving the order: a letter or message in the messenger with a direct link to the purchased product and a one-touch rating.
The "bought here" mark for reviews after a confirmed order - the reader distinguishes a buyer from a random commenter.
Moderation turn with a notification of a new review and response templates so that the review does not lie unpublished for a week.
The public response of the store under the review, both positive and critical: you can see a live seller, not silence.
Photos and videos in the reviews with a check of format and weight on download - otherwise the first file from the phone will put the page.
Review and AggregateRating markup bound to content visible on the same page, with a run through the validator.
Removing the self-imposed and false marking, if it already stands, is a separate first step before the rest of the work.
Category list rating and rating filter: the buyer weeds out the junk without opening twenty cards.
Protection against cheating: binding to the order, restrictions on the device and the speed of sending the form.
Terms: payment by stages, guarantee of 30 calendar days after acceptance.
When this service isn't right
What's not included — so there are no surprises at delivery
Writing reviews and any imitation thereof
Removal of negative reviews on external sites
The guarantee of the appearance of stars in the output — the markup gives the reason, the decision is made by the search engine
Moderation as a permanent service is a separate support
Hosting, domain, acquiring
Process steps
Transparent stages with approval at every step
Total duration:8–25 days
1
Analysis of the current markup
1-3 working days
Let's see what is declared in the structured data and whether there is confirmation of this on the page. We remove the risky marking immediately, before all other work, and fix the date - from it the wait until the warnings disappear is calculated.
2
Feedback Policy
1-3 working days
Who moderates, how many days after receiving the request, what do we do with criticism, in what form does the store respond. It is the owner's decision - we show the consequences of each option and record the choice in writing.
3
Form, storage, moderation
2-6 working days
Feedback fields, rating, confirmed purchase mark, publication queue, notification to the person in charge, response templates and roles in the admin.
4
Collection after purchase
2-5 working days
Queue of deferred tasks: the order moves to the desired status, after an agreed number of days, a request with a reference to a specific product is sent. The accuracy here is a day, not a minute, and that's normal.
5
Display and markup
1-5 working days
Feedback block on the card, rating in the category list, filter by rating, JSON-LD Review and AggregateRating under visible content, validator run.
6
Check and transfer
1-3 working days
End-to-end run from the order to the published feedback and response to it, markup reconciliation, webmaster panel without warnings, written instructions to the moderator.
Free review of reviews and markup
We look at two things: whether you have real reviews and whether your markup is declaring something that isn't on the page. The second occurs more often than one would like and costs more.
What we measure
What is now declared in the markupIs the ranking in the structured data and is it supported by visible content. In the app we measured, the markup had a rating of 4.8 out of 50 ratings, despite the fact that there was no mention of the word "feedback" or "rating" on the page - a direct reason for manual sanctions for self-imposed marking.
How many real reviews are thereQuantity, distribution by products and seniority. The rating, compiled from three reviews of the entire catalog, does not give anything in the issue.
How are they going nowIs there even a request mechanism after the purchase, or do the reviews appear by themselves. Unsolicited, they are mostly written by dissatisfied people.
Moderation and answersWho reads the reviews, how much they post for, and whether the store is responsible. Feedback with an answer works better than feedback without an answer, even if it's bad.
External sourcesIs collection through third-party services connected? In a measured garden tool store, Google's feedback module is a source that should be considered and not duplicated.
Risks and rulesThe requirements of search engines are not violated: the rating must describe what is visible on this very page, and not be self-assigned.
What you get
Report on the current marking with a list of risky places.
Evaluation of the existing array of reviews: how many there are and how evenly they are distributed across the catalog.
Collection plan: when and how to ask for feedback to be answered.
A conversation for 30–40 minutes on the document, where you can argue with the conclusions.
Timeline: 2-3 working days
Why is it free
Because checking the markup takes a few days, and manual sanctions for a self-assigned rating take months to remove. It is cheaper to learn about the risk before it than after.
What's next
After verification - amount and term, contract, account, deed. If we find a risky marking, we will offer to remove it as the first step, separately from the rest of the work.
Short form: your contact and site URL
Contract, act and 30-day warranty
Every project gets a written contract: scope, deadlines, amount, acceptance procedure. After delivery — act and invoice, then 30 calendar days of warranty.
Sole proprietor & bank transfer
The contractor is a registered sole proprietor. Payment by invoice with closing documents.
Rights & access — yours
Code, design and materials transfer to you after full payment. Domain, hosting, repository and analytics are registered to you.
Client portal instead of email chains
During the project you get access to a portal: contracts, invoices, acts and project status in one place.
European clients
Among our work — projects for Norway, Bulgaria, Moldova and Spain.
Verifiable numbers
Every case in the portfolio comes with a link to a live site and a technical measurement.
Audit first, then pricing
There is no price list on the site intentionally: the scope of the same work differs multiples between clients.
We say "no" when unsure
If the task isn't ours or the deadline is unrealistic — we tell you upfront.
Did not find your case?
Describe how it works on your side — we will tell you whether “Reviews and ratings in the online store” fits and what it means in your situation. No brief and no call: one question, one answer.
What affects the price
Why two seemingly identical tasks are priced differently
How many reviews are there already?If the array is assembled and it is only necessary to mark it correctly and display it, this is the lower limit of the term. If there are three reviews for the entire catalog, the main work is not in the code, but in starting the collection and waiting for the first hundreds.
Status of existing markupAn empty markup is cheaper than an incorrect one. Removing the self-assigned rating, checking the ad with the visible content and waiting for the warnings to disappear from the webmaster panel is a separate line of work that we usually put first.
Request channelMail via SMTP is sent quickly. Messenger requires a connected channel and agreed text, SMS requires a gateway and balance. The number of channels drives both the deadline and the number of approvals from your side.
Photos and videos in reviewsText feedback is a form and a table. Media is downloads, format checks, reduced copies, and storage that needs to be kept somewhere. At the start, it is often wise to refuse media and add them in a second step.
How many entities do we markOnly the product is one scheme. The product, the store and the evaluation criteria are three, and each should be compared with what is actually visible on the page, and not with what is convenient to announce.
ModerationQueue, roles, response templates, notifications. If one person is moderating from the phone, different solutions are needed than when the night shift department does it.
Technologies & integrations
What we build on and what it connects to
Stack
OpenCart 3.x and 4.x — in the core there is a review only about the product: oc_review is tied to product_id, we start the "store review" separately
PHP and MySQL are the language and base of the engine; the average rating is considered a request, so we cache it in a large catalog
JSON-LD Review, AggregateRating, Product - the ad must be visible on the same page, otherwise it is a self-assigned rating
a queue of deferred tasks on cron - the request goes a few days after receipt, and not at the time of payment
SMTP is the cheapest channel and the worst deliverability: part of the letters settles in promotions
Telegram and Viber are more open, but you can write only to those who have given their consent
structured data validator and webmaster panel — checking markup at a glance
image processing at the reception - a photo from the phone weighs more than the entire page
Integrations
Google Business Profile
Google feedback module
eSputnik
SMTP
SMS gateway
Telegram
Viber
Google Search Console
Google Tag Manager
GA4
Your own feedback section against an external service
How this option differs from the alternative
External feedback serviceOur approach
Who owns the reviews?service: when the tariff is turned off, they remain thereto you: lie in your database and move with the site
Marking of the ratingis often loaded with a script and does not enter the page markup; you cannot transfer other people's numbers to your JSON-LDon your domain and describes what is visible on that same page
Inquiry after purchaseaccording to the service script; the binding to the product is approximatefrom your order status, with a link to a specific product
The store's responsedepends on the tariff and what the interface allowsfield under the feedback, published immediately
Reader's trustthe logo of a well-known service itself reads as independenceyou can see the confirmed purchase mark from your order
Cost of ownershipsubscription fee, which grows with the number of reviews and sent lettersone-time development and your hosting
What we need from you
We can't start without this — best to prepare in advance
1Access to the site, database and webmaster panel.
2The decision of how many days after receipt to ask for feedback depends on the product, so it's up to you.
3Who will moderate and respond to feedback from you.
4The text of the feedback request agreed with you: the signature, the tone, and what you are willing to promise in return for the feedback.
5List of external feedback sources already in use.
6One person with the right to make decisions on publication policy.
If something is missing — let us know, we'll help you gather it or do it as a separate task.
FAQ
Most frequently asked questions — with concrete answers
Why are there sanctions for marking reviews at all?
Because the rating in structured data should describe what a person sees on this very page, and not be self-assigned. In our own project — a platform for automatically rewriting product descriptions — we found a declared rating of 4.8 out of 50 ratings in the code, with zero mentions of the words "feedback," "review," or "rating" on the page. This is a direct reason for manual sanctions. The most unpleasant thing is that the owner usually does not know about this: he did not put the markings, but the module or the contractor.
How to collect the first reviews, if there are none at all?
Ask, not wait. A few days after receiving the order, a letter or message is sent with a direct link to the purchased product and with a one-touch assessment - without registration and without a ten-field questionnaire. Shops without such a request almost always have a worse average rating than they deserve. You decide how many days to wait: for consumables it is a few days, for a tool it is more reasonable to let a person work with it.
Do I need to respond to reviews?
Yes, and primarily on critical ones. A review with an answer reads differently than a review without it: a live seller is visible. A calm public response to a complaint is often more persuasive than ten positive reviews in a row. Technically, this is an answer field under the feedback, a notification to the responsible person about a new publication and an agreement on the response period — otherwise, the answers are written once a quarter and all at once.
Is it possible to delete negative ones?
No, and we don't. The catalog with the highest fives reads like a cheat - buyers have long learned to feel it and first look for what they scolded for. Moderation is needed for other things: spam, insults, other people's advertising, off-topic reviews. If a specific product has systematically low ratings, this is a signal about the product or its description, and the reason should be removed, not the page.
Will the stars in the output appear immediately after launch?
Not immediately and not necessarily. Correct markup makes a page suitable for an advanced view in search results, but whether to show it or not is up to the search engine, and the decision depends on the number of real reviews and the trustworthiness of the site. The markup does not raise items or force a snippet to be shown: we are responsible for the fact that it is correct and describes the real content, and that the reviews are genuine.
We have already connected feedback collection through an external service
Then the main rule is not to duplicate the rating. The garden tool store we measured has a Google feedback module: this is a separate source with its own display rules. The markup on the site should describe your own reviews, which are in your database and visible on the page. Transferring someone else's numbers to your JSON-LD is once again a self-imposed rating, only this time with someone else's data.
How many reviews do you need for this to make sense?
The question is not in the total number, but in the distribution. Two hundred reviews for five hits and zero for the rest of the catalog is two hundred reviews and an empty catalog. Therefore, we measure two things: the share of products with at least one review, and the share of completed orders for which a review was left. Both figures are visible from the first month of collection, and it is by them that it is clear whether the request is working or it is flying into the void. Analytics is needed here — but it shows a trend, not an accounting truth, and it must be consciously reconciled with real orders.
And if a competitor starts writing us bad reviews?
That's why restrictions are needed: the feedback is tied to the confirmed order, there is a limit by device and by the speed of sending the form, everything new goes through the moderation queue. It doesn't make cheating impossible, but it makes it boring and obvious. We do not post completely open forms without an order link - they will be flooded with spam in a week, and this is not a hypothesis.
How long will it run?
8-25 working days. The lower limit is when the reviews have already been collected and you need the correct markup, display in a category and a filter by rating. Top — when you need to build a collection after purchase, a queue of moderation, answers, photos in reviews and evaluation criteria. We take the removal of risky markings as the first step and close it in a few days, without waiting for the rest of the work.
Submit your store address - let's see what's currently advertised in your structured data.
In response: a list of risky places in the markup, an assessment of the existing body of feedback and a collection plan - when and how to ask for feedback to respond to it.
From measured casesTTFB of 220.6 ms at 140.8 KB of HTML, the fastest response of the 16 sites measured
There is no price list on the site on purpose: the same work differs several times over between two clients, and a “from” figure explains nothing in that case. First a free audit — we count your pages, duplicates and speed — then we name the sum and the deadline and fix both in the contract.