Collecting and Showing Reviews for Coffee Bags
A roaster with a product page and no reviews under it is leaving a real decision aid off the page. A shopper deciding between two bags of coffee they have never tasted leans hard on what other people said, and an empty review section is a quiet vote of no confidence a roaster never meant to cast, even when every bag on the shelf is genuinely good.
Short answer: ask for a review at the right moment after delivery, in plain words that do not pressure anyone toward a positive answer, display what comes back honestly including the occasional bad one, and only add structured markup to reviews that actually live on your own page and meet the eligibility rules Google's documentation describes for products. Nothing here is invented. If a review, a rating, or a count is not real, it does not belong on the page or in the markup.
This post covers three things in order: collecting reviews with the right timing and wording, showing them where they actually help a buying decision, and adding schema markup correctly across the platforms most roasters use. It also draws a plain line between a product review on a coffee bag page and a Google Business Profile review of the cafe or roastery itself, since the two get confused more often than they should.
Collecting Reviews at the Right Moment
Timing matters more than most roasters assume. A request sent the same day an order ships asks a customer to review coffee they have not tasted yet. A request sent too late arrives after the moment has passed and the customer has moved on to their next bag from somewhere else. The useful window sits a handful of days after the coffee is likely to have arrived and been brewed at least once, long enough for a real impression to form, short enough that the experience is still fresh.
The wording of the ask matters as much as the timing. A plain, low pressure message works better than an enthusiastic one. Something like, we would love to hear what you thought of this coffee, good or not so good, a short review helps other people trying to decide between bags, does the job without steering anyone toward a five star answer. Avoid any language that rewards only positive reviews or implies a discount is tied to a good rating, since that kind of incentive runs against the review policies platforms and Google both maintain, and it produces a review section that no longer means anything to a reader trying to make an honest comparison.
A bad review, when it comes, is not a failure of the request, it is the system working. Respond to it plainly and specifically if the platform allows a public reply, acknowledge what the customer said, and avoid being defensive. A product page with one honest three star review sitting next to several five star ones reads as more credible to a shopper than a page with nothing but perfect scores, because real buying decisions rarely come with perfect agreement.
Never delete or hide a negative review to improve the page's appearance. Beyond being dishonest to future shoppers, most platforms and Google's own policies treat review gating, selectively asking only happy customers or suppressing unhappy ones, as a violation worth avoiding entirely, not a gray area worth risking.
If a customer's negative review points to something genuinely fixable, a roast that shipped stale, a grind that did not match the brew method they described wanting, treat that as useful information rather than a nuisance to manage away. The review itself stays exactly as written. What changes, if anything needs to, is the process on your end, not the record a future shopper reads.
Showing Reviews Where They Actually Help
Reviews belong near the decision a shopper is trying to make, which on a coffee bag product page usually means close to the tasting notes and the add to cart button, not buried at the very bottom of a long page a shopper may never scroll to. A star rating visible near the top of the page, with the full written reviews available just below the product description, respects both the shopper who wants a quick signal and the shopper who wants to read the detail.
Be specific about what is being reviewed. A coffee bag review and a Google Business Profile review of the cafe or roastery itself are two different things, collected in two different places, and a page should never blend the two together or imply that a strong Maps rating for the shop is the same thing as strong reviews for a specific bag of coffee. Keeping these separate is both more honest and clearer for the shopper trying to evaluate the actual product in front of them.
If a bag has very few reviews so far, say so plainly rather than hiding the section entirely. A line like, this coffee is new to our shop and does not have reviews yet, be the first to try it, reads as honest and even slightly inviting, compared to a blank space that just looks like an oversight or an empty shell of a feature that was never finished.
Adding Schema Markup Correctly
Structured data for a product review, the Review and AggregateRating types described in schema.org and in Google's own documentation for product structured data, is meant to describe reviews that exist on the page, in the words of real customers, not a summary invented to make the page look more credible in search results. Markup should mirror what a shopper sees when they land on the page, nothing added, nothing summarized differently.
Google's documentation on review snippets and product structured data lays out eligibility rules and explicitly prohibited practices, including markup for reviews that do not appear on the page, self authored reviews from the business itself, and incentivized reviews collected in exchange for compensation. A roaster adding markup should read that documentation directly rather than copying a pattern from another site, since the specifics of what counts as eligible can change and a page that follows an outdated pattern risks losing the rich result entirely rather than gaining one.
The platform a roaster builds on shapes how this markup gets added. Shopify, Squarespace and Wix each have their own product review tools or supported apps, and each differs in whether reviews are collected natively or through a third party app, and in whether that tool outputs the structured data automatically or requires manual setup. Whatever the platform, the practical step is the same: after reviews are live on a product page, run that page through Google's Rich Results Test and confirm the Review and AggregateRating properties are being detected as intended, rather than assuming the platform handled it correctly by default.
None of this guarantees a rich result will display in search. Eligibility and display are Google's decision, not something a roaster or a platform can promise, and this post is not going to claim otherwise. What a roaster can control is whether the underlying markup is honest, accurate, and matches what a real shopper sees on the page, which is the whole foundation the eligibility rules are built on in the first place.
What the Census Shows About Who This Applies To
Among the more than 1,000 shops across six regions in Hillcane's national census, snapshot dated September 15, 2026, a meaningful share are roasters selling bags online rather than cafe only operations, and among that group the platform split leans toward ecommerce focused builders. That context matters here because it means the review and schema question in this post applies to a real, sizable slice of the businesses this research covers, not a narrow edge case.
It also means the platform advice above is not theoretical. A roaster reading this on Shopify, Squarespace, or Wix is reading about the actual tools available on the platform they are already using, not a generic recommendation aimed at nobody in particular.
It is worth separating two different things the census can and cannot tell a roaster here. It can describe how many shops in the research sell bags online and roughly which platforms they use, since those are actual recorded fields. It cannot say how many of those bag pages currently have reviews, ratings, or working schema markup, because that detail was not a column in the underlying data. Treat this post as a how to guide built for the platforms roasters are using, not as a report on how common reviews or markup already are across the industry.
Building the Request, the Display Plan and the Checklist
A working request email needs only a few pieces: a short, warm opening that references the specific coffee the customer bought, a plain ask for an honest review, a direct link to where they can leave it, and a closing line that thanks them regardless of what they say. Keep it to a few sentences. A long request reads as a chore, and a short one reads as a genuine, quick favor.
A display plan is just as short. Decide where the star rating shows on the page, decide where the full written reviews sit, and decide how a bag with few or no reviews yet will be handled honestly rather than left blank and unexplained. Write these three decisions down once and apply them consistently across every product page, so a shopper moving between bags sees a familiar, trustworthy pattern rather than a different layout every time.
The markup checklist closes the loop: confirm every review in the markup appears as visible text on the page, confirm no review was written by the business itself or collected through an incentive that violates platform or Google policy, and run the finished page through the Rich Results Test to confirm the properties are detected. If the test does not detect what was intended, fix the markup before publishing rather than leaving it live and hoping it resolves itself.
Being Honest When a Request Program Grows
As a roaster sends more review requests, it becomes tempting to build the process around whichever emails get the best response, which usually means the most enthusiastic customers. Resist tuning the request process toward that bias. A review program aimed only at happy repeat customers who are easy to reach will drift toward an inflated picture of how a coffee is received, even without anyone intending to mislead a shopper.
The Federal Trade Commission publishes guidance on consumer reviews generally, including the principle that reviews shown to the public should represent honest opinions rather than a curated, one sided selection. A roaster does not need to be a legal expert to follow the spirit of that guidance: send the same request to every customer who bought the coffee, not a hand picked subset, and let whatever comes back stand as written.
This also means resisting the urge to only send requests after a smooth, uneventful order. If a shipment ran late or arrived with a minor issue that was resolved, that customer still had a real experience with the coffee itself and deserves the same invitation to review it as anyone else. Selectively skipping customers who had a rough start is a quieter version of the same problem as deleting a bad review after the fact.
Related Reading
More from Hillcane on this topic, plus the pages on the site that sit next to the work.
Frequently Asked Questions
When is the best time to ask a customer for a coffee bag review?
A handful of days after the coffee has likely arrived and been brewed at least once, giving a real impression time to form while the experience is still fresh. Too early and the customer has not tasted it yet. Too late and the moment has passed and they have already moved on to another bag.
Can I offer a discount in exchange for a positive review?
No. Rewarding only positive reviews, or implying a discount depends on a good rating, runs against the review policies that platforms and Google maintain, and Google's product structured data documentation treats incentivized reviews as ineligible for markup. The Federal Trade Commission's consumer review guidance points the same way: shown reviews should be honest opinions. Send one plain, low pressure ask to every buyer that welcomes a good or not so good answer, and let whatever comes back stand.
Should I hide or delete a negative review?
No. A negative review is the system working, not a failure to fix by hiding it. Respond publicly and plainly if the platform allows it, and let it stand. Most platforms and Google's own policies treat selectively suppressing unhappy reviews as a violation, not a gray area, and a page with only perfect scores tends to read as less credible to a shopper anyway.
Where on the product page should reviews appear?
Place reviews near the decision a shopper is making, close to the tasting notes and the add to cart button, not buried at the bottom of a long page. A star rating visible near the top, with full written reviews just below the product description, serves the quick skimmer and the detailed reader. Keep bag reviews clearly separate from Google Business Profile reviews of the cafe or roastery, since a strong Maps rating says nothing about one specific coffee.
Are coffee bag reviews the same thing as Google Business Profile reviews of my cafe?
No, and a page should never blend the two together. A coffee bag review describes one specific product, collected on your own site. A Google Business Profile review describes the cafe or roastery as a whole, collected on Google Maps. Keeping them clearly separate is more honest and clearer for a shopper evaluating the product in front of them.
What does Review and AggregateRating schema markup require?
It requires that the markup mirror reviews that genuinely exist and are visible on the page, in the words of real customers. Google's documentation on review snippets and product structured data describes eligibility rules and prohibits markup for reviews not shown on the page, self authored reviews, and incentivized reviews collected in exchange for compensation.
Does adding review schema guarantee a rich result in search?
No. Whether a rich result displays is Google's decision, not something a roaster, Shopify, Squarespace, or Wix can promise. What a roaster controls is whether the Review and AggregateRating markup is honest and matches the reviews a shopper sees on the page. Google's documentation excludes markup for reviews not on the page, reviews written by the business, and incentivized reviews, so read it directly rather than copying another site's pattern, which may be outdated.
How do I check whether my review markup is working correctly?
Once reviews are live, run the finished product page through Google's Rich Results Test and confirm the Review and AggregateRating properties are detected as intended. Do not assume a Shopify, Squarespace, or Wix review tool or app output the markup correctly by default, since some generate it automatically and others need manual setup. Also confirm every marked up review appears as visible text on the page. If the test misses something, fix it before publishing.
What should I do if a product has no reviews yet?
Say so plainly rather than leaving the section blank. A short line such as, this coffee is new to our shop and does not have reviews yet, be the first to try it, reads as honest and slightly inviting, while an empty space looks unfinished. Never add placeholder Review or AggregateRating markup to fill the gap. Then send the review request a handful of days after the coffee has likely arrived and been brewed once.
Do review tools work the same way on Shopify, Squarespace and Wix?
No. Each platform has its own native tools or supported apps for product reviews, and they differ in whether reviews are collected natively or through a third party app, and in whether structured data is output automatically or needs manual setup. Whatever the platform, always confirm the actual markup with the Rich Results Test rather than assuming it is correct by default.
Work with Hillcane
An empty review section under a coffee bag is not neutral. It is a quiet vote of no confidence a roaster never meant to cast.
If you want help setting up an honest review request and correct markup for your product pages, reach out at hillcane.co/contact or call (256) 384-2449.
Comments