> For the complete documentation index, see [llms.txt](https://docs.roadmap.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roadmap.so/reviews/getting-started/getting-started-with-reviews.md).

# Getting started with reviews

Set up review collection, moderation, storefront display, and request flows in the right order.

Use this guide for your first review setup.

It walks through the core decisions in the order most stores need them.

### What to set up first

1. Decide how reviews will be published.
2. Add reviews to your product pages.
3. Choose how you will request reviews.
4. Decide whether reviews should trigger rewards.
5. Add optional sharing or syndication features.

### 1. Choose your moderation approach

Start with [Review auto publishing settings](/reviews/getting-started/review-auto-publishing-settings.md).

Use **Disabled** if you want to approve reviews manually.

Use **Enabled** if you want qualifying reviews to publish automatically once they meet your minimum star threshold.

### 2. Add reviews to your storefront

Use [Add Reviews to Product Pages](/reviews/storefront-and-display/add-reviews-to-product-pages.md) to place the review widget on your product templates.

Then refine the display with [Customise review widget design](/reviews/storefront-and-display/customise-review-widget-design.md).

If you collect photo reviews, also enable [image display in the PDP review widget](/reviews/storefront-and-display/enable-image-display-in-the-pdp-review-widget.md).

### 3. Set up review request emails

If you want automated review capture, start with [How to integrate Roadmap with Klaviyo](/reviews/integrations/klaviyo-review-integration/how-to-integrate-roadmap-with-klaviyo.md).

Then follow [Introduction to Klaviyo review flow setup](/reviews/integrations/klaviyo-review-integration/introduction-to-klaviyo-review-flow-setup.md).

If you use Roadmap's reminder timing controls, review [Review reminder emails](/reviews/integrations/klaviyo-review-integration/review-reminder-emails.md).

### 4. Decide whether reviews should earn rewards

Use [Review rewards & limits](/reviews/managing-reviews/review-rewards-and-limits.md) to control who can submit reviews and what happens after submission.

Start with submission rules, then add points or discount incentives if needed.

### 5. Add optional advanced features

Use [Shared Reviews](/reviews/managing-reviews/shared-reviews.md) if related products or connected stores should share review content.

Use [Integrate reviews with Google Merchant Center](/reviews/integrations/integrate-reviews-with-google-merchant-center.md) if you want product ratings to appear on Google Shopping and Search.

### Recommended setup order

* Set moderation first.
* Add storefront widgets second.
* Launch review-request emails third.
* Add rewards only after the submission flow works.
* Add sharing and Google syndication last.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.roadmap.so/reviews/getting-started/getting-started-with-reviews.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.