# Shopify Reviews Scraper (Judge.me, Yotpo, Okendo, Loox) (`bozomalabs/shopify-reviews-scraper`) Actor

Scrape product and store reviews from Shopify stores using Judge.me, Yotpo, Okendo or Loox. Paste a store domain or product URL; the review app is detected automatically. Get rating, title, text, date, verified buyer, helpful votes and replies, plus optional insights. Export CSV, Excel or JSON.

- **URL**: https://apify.com/bozomalabs/shopify-reviews-scraper.md
- **Developed by:** [Bozoma Labs](https://apify.com/bozomalabs) (community)
- **Categories:** E-commerce, AI, Developer tools
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 reviews

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Shopify Reviews Scraper (Judge.me, Yotpo, Okendo, Loox)

Scrape product and store reviews from any Shopify store that uses **Judge.me, Yotpo, Okendo or Loox**. Paste a store domain or product link. The Actor detects the review app from the page and pulls every public review into clean rows: rating, title, text, date, verified buyer, helpful votes, product and store reply. Turn on **Insights** for a ready summary of complaints, praise, feature requests and lowest-rated products.

Built by **Bozoma Labs**. Public review widget data only: the same reviews any shopper sees on the store. No login, no browser, fast and cheap.

### What you get

| Field | Description |
|---|---|
| store | Store domain |
| provider | `judgeme`, `yotpo`, `okendo` or `loox` |
| scope | `store` (all reviews) or `product` |
| productId, productHandle, productName, productUrl | Product the review is about |
| reviewId | Review app's ID (used to dedupe) |
| rating | 1 to 5 stars |
| title | Review title (if the app has one) |
| text | Review text |
| reviewerName | Public display name (empty with "Omit reviewer names") |
| publishedDate | ISO date |
| verified | Verified buyer flag from the review app |
| helpfulVotes | Helpful or thumbs-up votes |
| variant | Product variant (Okendo) |
| replyText, replyDate | Public store reply (with "Include store replies") |
| sourceUrl | The URL you entered |

The **Review Analyzer** view exports exactly: Rating, Review text, Title, Published date, Reviewer name, Verified.

No emails, phone numbers or private customer data are collected.

### Insights add-on

With `insights: true`, each URL gets one entry in the `INSIGHTS` record of the run's key-value store: average rating, star distribution, share of 1 to 2 star reviews, top complaint and praise phrases, feature requests, lowest-rated products and a monthly trend. Computed from the collected reviews with no external AI service.

### Input example

```json
{
  "startUrls": ["https://www.pupford.com/", "https://www.ridgewallet.com/products/sakura"],
  "maxReviewsPerTarget": 1000,
  "stars": ["1", "2"],
  "dateFrom": "2026-06-01",
  "insights": true
}
```

### Pricing

Pay per result:

- **$1.00 per 1,000 reviews** ($0.001 per review)
- **$0.05 per URL** for the Insights add-on (only if turned on and reviews were found)
- **$0.005** per run start

Set a maximum cost per run in Apify and the Actor stops cleanly when it is reached.

### Supported apps and limits

| App | Store-wide | Single product | Dates | Notes |
|---|---|---|---|---|
| Judge.me | Yes | Yes | Yes | Includes store and product reviews. Judge.me serves about 1,000 per query, so larger pulls are split by star rating (up to about 5,000 per URL) |
| Okendo | Yes | Yes | Yes | Includes variant; if the store groups related products, product reviews include the whole group |
| Yotpo | Yes | Yes | Yes | Some stores only publish part of their reviews to the widget |
| Loox | Yes | Filtered from store pool | No | Loox's public feed has no review dates and no product filter; product URLs are matched by product name |

- If a storefront blocks Apify datacenter IPs, the Actor retries only the storefront page through a residential IP (a few requests per URL). Review data itself comes from the review app APIs without a proxy.
- If a store blocks automated visits entirely, enter its public widget ID directly instead of a URL: `okendo:<store id>`, `yotpo:<app key>`, `judgeme:<shop>.myshopify.com` or `loox:<widget id>`. These IDs are public and visible in the store's page source.
- If no supported app is found you get a clear note in the run's `SUMMARY` record and are not charged for reviews.
- If a store has several apps, the Actor picks Judge.me, then Yotpo, Okendo, Loox. Use **Review app** to force one.
- Stores on other apps (Stamped, Junip, Reviews.io, Klaviyo Reviews) are not supported yet.

### Use cases

- Competitor research: what buyers love and hate about rival products
- Product development: mine feature requests and complaints
- Market research across many DTC brands
- Feed reviews into a spreadsheet, BI tool or your own analysis

### FAQ

**Is this legal?** It collects reviews that stores publish for anyone to read, without logging in. You are responsible for how you use the data, including GDPR. Turn on "Omit reviewer names" if you do not need names.

**Support**: open an issue on the Actor's Issues tab.

# Actor input Schema

## `startUrls` (type: `array`):

A store homepage (e.g. pupford.com) for all store reviews, or a product URL (https://store.com/products/handle) for that product's reviews. A Loox widget URL (https://loox.io/widget/ID/reviews) also works, as do direct public widget IDs: okendo:<store id>, yotpo:<app key>, judgeme:<shop>.myshopify.com, loox:<widget id>.

## `maxReviewsPerTarget` (type: `integer`):

Stop after this many reviews per store or product (after filters). 0 means no limit.

## `provider` (type: `string`):

Leave on Auto to detect from the page. Force one if a store has several apps installed.

## `stars` (type: `array`):

Keep only these star ratings. Leave empty for all.

## `dateFrom` (type: `string`):

Keep reviews published on or after this date (YYYY-MM-DD). Loox does not publish review dates, so this is ignored there.

## `dateTo` (type: `string`):

Keep reviews published on or before this date (YYYY-MM-DD).

## `verifiedOnly` (type: `boolean`):

Keep only reviews the review app marks as verified purchases.

## `includeReplies` (type: `boolean`):

Add replyText and replyDate columns when the store replied publicly.

## `omitReviewerNames` (type: `boolean`):

Leave reviewerName empty, for privacy-friendly exports.

## `insights` (type: `boolean`):

Per URL: rating breakdown, monthly trend, top complaint and praise phrases, feature requests and lowest-rated products, saved to the INSIGHTS record in the run's key-value store. Charged once per URL.

## `proxyConfiguration` (type: `object`):

Usually not needed.

## Actor input object example

```json
{
  "startUrls": [
    "https://www.pupford.com/",
    "https://www.ridgewallet.com/products/sakura"
  ],
  "maxReviewsPerTarget": 500,
  "provider": "auto",
  "stars": [],
  "verifiedOnly": false,
  "includeReplies": true,
  "omitReviewerNames": false,
  "insights": false,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `reviews` (type: `string`):

One dataset item per review, including rating, text, title, date, reviewer, verification and store replies.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "startUrls": [
        "https://www.pupford.com/",
        "https://www.ridgewallet.com/products/sakura"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("bozomalabs/shopify-reviews-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "startUrls": [
        "https://www.pupford.com/",
        "https://www.ridgewallet.com/products/sakura",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("bozomalabs/shopify-reviews-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "startUrls": [
    "https://www.pupford.com/",
    "https://www.ridgewallet.com/products/sakura"
  ]
}' |
apify call bozomalabs/shopify-reviews-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,bozomalabs/shopify-reviews-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/zNCe061QVGdzR1PBg/builds/nG7JH9byQdBnayWGw/openapi.json