How Hand-Poured Candle Brands Can Get More Reviews And UGC
For candle sellers updating an existing product page, this guide lays out a neutral review request and a permission-led process for publishing customer comments and photos.
Improve the review block on an existing candle product page, then check the post-purchase route that directs customers to it. Send the same optional, neutral invitation to eligible buyers after delivery is confirmed. Let customers comment on scent, burn experience, or packaging if they choose, then verify the product match and record permission for each planned use before publishing.
- Start with the existing candle product page and its current review route.
- Invite all eligible buyers to share honest feedback, without screening by sentiment.
- Match every submission to the correct candle and confirm its intended use.
- Approve the page, wording, permissions, and final publication before launch.
Open the candle product page shoppers already use, then follow the message or insert that asks for feedback. Can a buyer find comments about the right candle? Does the route make clear where to respond? Check whether each displayed quote or photo has permission for that specific placement. This is a focused review of the existing page and request process, not a promise of more reviews or sales. Fix product matching and publication approval first; add automation only if its role and scope are confirmed.
Inspect The Existing Product Page And Request Route
Open the candle listing on a phone and desktop. Find the review summary, the full review area, and the route a buyer follows after receiving an order. Record whether comments identify the candle they refer to and whether customer opinions are distinct from the product details you have verified.
Then check the existing email, package insert, or other request message. Note whether it leads to the intended response route or sends buyers to a general page where they must guess what to do. If it points to a different candle, document the mismatch before editing. Similar scents or packaging are not enough to establish that a review belongs to a particular product.
Write down observable gaps: no visible review area, unclear response instructions, missing product matches, or a photo with no permission record. Treat an unknown detail as a question for the owner. Do not fill it in based on what seems likely.
Set Up A Neutral Post-Purchase Request
Use an owner-approved trigger, such as confirmed delivery, and send the same optional invitation to all eligible buyers. If delivery status is unknown, pause until the owner confirms another appropriate trigger. Do not choose recipients based on satisfaction, send unhappy customers to a private route instead, or make a benefit conditional on leaving feedback.
Keep the request short and let the customer decide what to say. A candle-specific prompt can be optional: “If you’d like, what stood out about the scent, burn experience, or packaging?” Identify the response route, who checks replies, and whether one follow-up is permitted. No follow-up limit or owner should be left implicit.
For Google reviews, Google says reviews should reflect genuine experiences and prohibits incentives in exchange for reviews. Its guidance also recommends valuing honest, balanced feedback. Those are Google-specific requirements, not a statement that every review platform has identical rules. See Google’s guidance for requesting reviews.
| Situation | Trigger and invitation | Response route and follow-up | Owner check | Decision |
|---|---|---|---|---|
| Delivery status is confirmed. | Use the owner-approved trigger; send the same optional, neutral request to every eligible buyer. | Name the response route and set a follow-up limit, including whether one follow-up is allowed. | Record the status source, approved wording, route, follow-up limit, and responsible owner. | Ready only when all required details are clear. Do not screen by sentiment. |
| The owner approves a different trigger. | Document the alternative trigger and use the same neutral invitation for eligible buyers. | Use the approved response route and stated follow-up limit. | Confirm who approves the trigger and who handles responses. | Ready only after the owner confirms the trigger and required route details. |
| Delivery status or trigger is unclear. | Do not assume the order arrived or send based on a guess. | Hold the request until the owner confirms the trigger and destination. | Ask the owner to verify the status source, wording, response route, follow-up limit, and responsible person. | Clarification needed. Do not treat an incomplete route as ready. |
| A customer has an order concern. | Do not imply a review is required to resolve the concern. | Direct the customer to the owner-approved customer-service route. | Confirm who handles the issue and how it is separate from the optional request. | Handle the concern through customer service; do not use it to filter review invitations. |
- Inspect
Review the current product page, request route, product matches, and available permission records.
- Prepare
The owner confirms the request trigger, wording, response route, follow-up limit, and responsible person.
- Approve
The owner approves the page change, display rules, product matches, and permission for each item.
- Test
Check the request and published page on mobile and desktop, then verify the correction route.
Keep Customer Opinions Separate From Product Facts
Optional prompts can invite observations about scent, burn experience, or packaging, but they should not lead a customer toward praise or a preferred phrase. “What would you like other shoppers to know about your experience?” leaves room for a balanced answer. A review about one person's experience should remain attributed to that customer, not rewritten as a promise about every candle.
Use owner-verified information for the product description: the candle name, scent, size, wax, vessel, and care details. If the product match is unclear, including when a customer names a different scent than the listing, hold the content while the owner checks the match. Apply the same product check to positive and critical comments. Do not alter a comment to make it sound more certain or more favorable.
A review request should not suppress criticism or ask customers to include a particular rating. Google’s Maps policy also prohibits selectively soliciting positive reviews and offering incentives for reviews; apply that rule to Google Maps requests specifically. For other destinations, check the relevant platform’s current requirements rather than assuming Google’s policy governs them.
Check Permission Before Publishing Reviews Or Photos
A customer’s submission does not automatically establish permission for every placement. Ask whether a quote or photo may appear on the relevant candle product page, and record the approved scope. If you want to reuse it in email or social content, confirm that separately. Hold an item when the product match or permission is unclear.
Clearly hypothetical example: A seller sends every eligible buyer the same optional, neutral request. One customer submits a balanced comment and photo. The seller verifies which candle the comment concerns, asks separately about using the photo on that product page, records the answer, and publishes only the approved material. There is no reward or preferential request.
Keep the customer’s approved wording, attribution, image edits, and placement with the permission record. Provide a way to request a correction or removal, and make sure someone is responsible for responding. If an item is held, do not publish it while waiting for clarification.
| Item and product match | Permission scope | Edits, attribution, and placement | Decision | Correction or removal route |
|---|---|---|---|---|
| Text review clearly matches the candle listing. | Record permission for the intended product-page use. | Confirm any edit and the attribution approved by the customer. | Publish only after the owner approves the item and placement. | Provide the owner-approved correction contact. |
| Photo shows a candle, but product identity needs checking. | Confirm permission for the specific page before use. | Confirm approved crop, attribution, and placement. | Hold until both product match and permission are clear. | Identify who handles a correction or removal request. |
| Product-page use is approved; social or email reuse is not. | Record that permission is limited to the product page. | Do not treat page approval as approval for another channel. | Use only on the approved page; hold from email and social. | Ask again before changing the placement. |
| Product match, permission, or approved edits are unclear. | Request clarification and record the answer. | Do not assign the item to a similar scent or edit around uncertainty. | Hold until the owner confirms the facts and permission. | Use the owner-approved customer-service contact. |
Test The Page And Measure Approved Proof
Before publication, check the request for three things: it is optional, it goes to eligible buyers without sentiment screening, and it offers no benefit conditioned on a review. On mobile and desktop, check that each displayed item matches the candle, stays within its approved placement, and is readable beside the product information. Test the correction or removal route, too.
The owner gives final approval for the wording, product matches, display rules, and each item’s use. A send, click, submission, or raw review count is not the same as approved proof. A verified qualified action is a customer review or photo that is approved for publication and clearly tied to the candle product page, plus a recorded permission note for reuse where needed.
If you already have a relevant baseline, preserve it before making the change. Otherwise, begin recording when the updated page or request route goes live. Note changes to the request, trigger, or page when reviewing later activity. Do not treat a page edit as proof of a sales increase or a search or AI citation.
Choose An Owner Edit Or Managed Page Update
A manual process may be enough if you can maintain the neutral invitation, confirm its trigger, keep a permission record, and update the existing product page yourself. Managed help makes sense when the review block is hard to edit, approved copy needs implementation, or you want ongoing website updates. Our small-business website management can be scoped for the owned-site page work. A review platform, email automation, customer-data connection, or external posting integration is a separate scope question, not an assumed part of a page edit.
For a proposal, share the actual product-page URL, your goal, the current review and request route, and the specific page or copy change you want. Include the owner-approved trigger and status source, customer-service and correction contacts, existing reviews or photos, product matches, and permission records. We can then confirm what page work is in scope. You approve the wording and final publication; only the proposal is free.
Frequently Asked Questions
Can I offer a discount or gift in exchange for a candle review?
Do not make a discount, gift, or other benefit conditional on leaving, changing, or removing a review. Google specifically prohibits incentives for Google reviews. Keep the request optional and neutral, and do not tell customers which rating or wording to use.
What should I do if a review names the wrong candle?
Hold it while you verify which product the customer means. Do not attach the comment to a similar scent or rewrite it to make the match seem certain. Use the owner-approved customer-service route to ask for clarification, then publish only when the product association and required permissions are clear.
Does permission for a product page also cover social or email use?
No. Confirm and record each intended placement. Approval for a photo on one candle’s product page does not automatically cover an email or social post. If the scope is unclear, hold the content until the customer confirms the additional use.
Can Storebox connect a review platform or automate request emails?
A specific platform, email automation, customer-data connection, or external posting route needs confirmation in the project scope. None is assumed as part of a page edit. You can begin by defining the owner-approved trigger, neutral wording, response route, and follow-up limit.
What information should I send to request a review-block update?
Send the actual product-page URL, your goal, the current request route, the approved trigger, and the specific copy or page change you want. Include existing reviews or photos, product matches, permission records, and correction contact. Before publication, the owner should approve the wording and test product matches, placements, and the correction route.