# Feedaty Reviews Scraper (`memo23/feedaty-reviews-scraper`) Actor

Scrape merchant reviews from Feedaty.com, the Italian e-commerce review platform — full review text, star rating, date and language, plus each shop's average rating and total review count. Paste any Feedaty merchant URL or a bare domain. Pay per result; JSON, CSV or Excel.

- **URL**: https://apify.com/memo23/feedaty-reviews-scraper.md
- **Developed by:** [Muhamed Didovic](https://apify.com/memo23) (community)
- **Categories:** E-commerce, AI, Agents
- **Stats:** 3 total users, 1 monthly users, 100.0% runs succeeded, 1 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 review scrapeds

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Feedaty Reviews Scraper 🟠

Extract merchant reviews from **Feedaty.com** — the Italian e-commerce review platform (by Zoorate) used by thousands of online shops. Get every review's text, star rating, date and language, plus the shop's aggregate rating and review count. Paste a Feedaty merchant URL (or just a domain) and export to JSON, CSV or Excel.

![How Feedaty Reviews Scraper works](https://raw.githubusercontent.com/muhamed-didovic/muhamed-didovic.github.io/main/assets/how-it-works-feedaty.png)

### Why use this scraper?

- 🇮🇹 **Italy-first coverage.** Feedaty is a leading review platform for Italian e-commerce — data you won't get from the global review sites.
- ⚡ **Full history, not just page one.** Paginates every review for a merchant and de-duplicates across pages by review id.
- 🧾 **One clean row per review** with the merchant's name, website and aggregate rating attached.
- 📊 **A merchant "header" row, once per shop** — lifetime totals, the full star breakdown, 12/3/1-month rating windows, other rating channels, subscription status and a 12-month monthly trend, all in a single `recordType: "merchant_summary"` row (not repeated on every review).
- 🟢 **No anti-bot, no proxy headaches.** Reads Feedaty's public, SEO-indexed certificate pages — runs fast on the default Apify proxy (or direct).
- 💸 **Pay per result.** Transparent per-review pricing; the merchant summary row doesn't eat into your review budget (`maxItems` only caps reviews).

### Overview

Feedaty (operated by Zoorate) is an Italian review-collection platform. Each merchant gets a public "certificate" page listing customer reviews, an average score and a total count — pages built to rank in Google for "{shop} recensioni / opinioni".

This actor turns any Feedaty merchant page into structured data. Point it at one or many merchants and it returns each review's text, rating, date and language, with the shop's name, website and aggregate rating on every row.

> **Note on reviewer names:** Feedaty anonymises reviewers — `authorName` is always **"Utente Feedaty"** (Italian for "Feedaty user"). Individual reviewer identities, company replies and verified-purchase flags are not exposed in Feedaty's public data.

### Supported inputs

| You paste… | Example | What you get |
|---|---|---|
| A merchant review URL | `https://www.feedaty.com/recensioni/caffevergnano` | All reviews for that merchant |
| The legacy certificate URL | `https://www.feedaty.com/feedaty/reviews/caffevergnano` | Same merchant, same data |
| A bare domain or slug | `caffevergnano.com` or `diadora.com` | Auto-resolved to its review feed |

Mix as many merchants as you like in a single run.

### Use cases

- **Reputation monitoring** — track new reviews and the average score for your own shop on Feedaty.
- **Competitor analysis** — pull a rival Italian merchant's full review history and rating trend.
- **Voice-of-customer & CX** — mine Italian-language review text for recurring praise and complaints.
- **Market research** — compare merchants by review volume and average rating across a category.
- **Data enrichment** — append Feedaty review counts and ratings to a list of Italian e-commerce domains.

### How it works

1. **Input** — paste Feedaty merchant URLs (`/recensioni/{slug}`) or bare domains/slugs.
2. **Fetch** — each merchant's certificate page is fetched and its embedded JSON-LD block is parsed.
3. **Paginate** — pages are walked via `?pag=N`, de-duplicating reviews across pages by review id until the full history is collected (or `maxItems` is reached).
4. **Map** — each review is flattened with its merchant context (name, website, average rating, review count).
5. **Summarize** — once per merchant, the page's star breakdown, other rating channels, subscription status and monthly trend chart data are read from the page, plus a call to Feedaty's own ratings endpoint for lifetime totals and the 12/3/1-month windows — together pushed as a single merchant-summary row.
6. **Output** — review rows and one merchant-summary row per merchant to the Apify dataset, exportable as JSON, CSV or Excel.

Feedaty has no anti-bot protection, so the actor runs fast and reliably on the default Apify proxy (residential proxies are not required).

### Input configuration

| Field | Type | Default | Description |
|---|---|---|---|
| `startUrls` | array | `["https://www.feedaty.com/recensioni/caffevergnano"]` | Merchant review URLs or bare domains/slugs. |
| `companySlugs` | array | – | Optional convenience list of bare slugs/domains. |
| `maxItems` | integer | `1000` | Hard cap on total reviews collected across all merchants. |
| `maxConcurrency` | integer | `4` | How many merchants to fetch in parallel. |
| `proxy` | object | Apify Proxy | Proxy settings. Default is fine — set Use Apify Proxy off to run direct. |

#### Example input

```json
{
  "startUrls": [
    "https://www.feedaty.com/recensioni/caffevergnano",
    "diadora.com"
  ],
  "maxItems": 500,
  "maxConcurrency": 4
}
```

### Output

Two kinds of rows, distinguished by `recordType`: one `"review"` row per review, and a single `"merchant_summary"` row per merchant.

#### Review row

```json
{
  "recordType": "review",
  "platform": "feedaty",
  "reviewId": "12502830",
  "rating": 5,
  "bestRating": 5,
  "reviewBody": "Ottima. Tutto molto semplice e chiaro. Ottimi tempi di consegna",
  "authorName": "Utente Feedaty",
  "reviewDate": "2026-06-23T23:17:47.54",
  "language": "IT",
  "merchantSlug": "caffevergnano",
  "companyName": "Caffè Vergnano Official Store",
  "companyUrl": "https://www.caffevergnano.com/shop",
  "companyRatingAvg": 4.8,
  "companyReviewCount": 261,
  "sourceUrl": "https://www.feedaty.com/recensioni/caffevergnano?gui=it-IT&l=&s=&t=1&pag=1",
  "scrapedAt": "2026-06-26T09:52:55.354Z"
}
```

#### Merchant-summary row (one per merchant, like a header)

```json
{
  "recordType": "merchant_summary",
  "platform": "feedaty",
  "merchantSlug": "caffevergnano",
  "merchantCode": "10215614",
  "companyName": "Caffè Vergnano Official Store",
  "companyUrl": "https://www.caffevergnano.com/shop",
  "totalReviewCount": 5374,
  "totalReviewAvg": 4.8,
  "starBreakdown": { "star5": 4632, "star4": 654, "star3": 54, "star2": 14, "star1": 20 },
  "last12Months": { "avg": 4.8, "count": 261 },
  "last3Months": { "avg": 4.9, "count": 67 },
  "lastMonth": { "avg": 4.9, "count": 15 },
  "otherChannels": [
    { "channel": "Prodotti/Servizi", "avg": 4.8, "count": null },
    { "channel": "Consegna", "avg": 4.8, "count": null }
  ],
  "subscriptionStatus": "ATTIVO",
  "lastReviewDate": "30 giugno 2026",
  "reviewsInMediationCount": 0,
  "monthlyTrend": [
    { "period": "2026-06", "totalCount": 350, "star5": 175, "star4": 50, "star3": 44, "star2": 31, "star1": 50 }
  ],
  "sourceUrl": "https://www.feedaty.com/recensioni/caffevergnano?gui=it-IT&l=&s=&t=1&pag=1",
  "scrapedAt": "2026-06-30T21:02:00.901Z"
}
```

#### Key output fields

**Review rows**

| Field | Description |
|---|---|
| `rating` | Star rating, 1–5 (`bestRating` is the max, 5). |
| `reviewBody` | Full review text (Italian). |
| `reviewDate` | Publication date (ISO 8601). |
| `authorName` | Always `"Utente Feedaty"` — Feedaty anonymises reviewers. |
| `language` | Review language (e.g. `IT`). |
| `companyRatingAvg` / `companyReviewCount` | The merchant's **rolling last-12-months** rating/count (Feedaty's own published headline figure). For lifetime totals see `totalReviewAvg`/`totalReviewCount` on the merchant-summary row. |

**Merchant-summary row** (filter on `recordType === "merchant_summary"`)

| Field | Description |
|---|---|
| `totalReviewCount` / `totalReviewAvg` | Lifetime review count and average rating across the merchant's full history. |
| `starBreakdown` | Absolute review count per star (1–5), full history. |
| `last12Months` / `last3Months` / `lastMonth` | `{avg, count}` for each rolling time window. |
| `otherChannels` | Extra rating channels/criteria Feedaty shows for this merchant (e.g. "Prodotti/Servizi", "eBay", or per-criterion scores like "Consegna", "Servizio clienti") — varies by merchant, `count` is `null` when Feedaty doesn't publish one for that channel. |
| `subscriptionStatus` | The merchant's Feedaty subscription badge text (e.g. `"ATTIVO"`). |
| `lastReviewDate` | Date of the merchant's most recent review, as published by Feedaty (e.g. `"30 giugno 2026"`). |
| `reviewsInMediationCount` | Reviews currently in Feedaty's mediation process (not yet public). |
| `monthlyTrend` | Array of `{period, totalCount, star5..star1}` for the last ~12-13 months — the same data behind the page's "Andamento delle recensioni" chart. |

### FAQ

**Does it scrape all reviews or just the first page?**
All of them. The actor paginates the merchant's full review history and de-duplicates across pages, not just the reviews on the first page.

**Why is every `authorName` "Utente Feedaty"?**
Feedaty anonymises reviewers in its public data — individual names aren't available to scrape. Each review still includes the full text, rating, date and language.

**Does it include company replies or verified-purchase flags?**
Feedaty's public review data doesn't expose those, so they aren't in the output. (If you need a richer Italian/EU review source with replies, see our TrustMate scraper.)

**Can I scrape product-level reviews?**
This actor returns the merchant's company-level reviews (the certificate page). Product-review pages are a separate feed — tell us if you'd like them added.

**What's the merchant-summary row, and why is it separate from the reviews?**
One extra row per merchant (`recordType: "merchant_summary"`) carrying lifetime totals, the star breakdown, 12/3/1-month windows, other rating channels, subscription status and a monthly trend — so this data isn't repeated on every single review row. It's pushed once regardless of `maxItems`, so it never displaces a review you're paying for.

**Some merchants don't show all the same fields in `otherChannels` — why?**
Feedaty shows a different set of extra rating channels per merchant (a couple of named channels like "eBay" for some, six per-criterion scores like "Consegna"/"Servizio clienti" for others, or none at all). The actor reads whatever Feedaty publishes for that merchant rather than assuming a fixed set.

**Do I need a residential proxy?**
No. Feedaty has no anti-bot protection — the default Apify Proxy is plenty, and you can even run direct.

**How is it billed?**
Pay-per-result: you're charged per review row returned. Use `maxItems` to cap any run.

### Support

Found a bug or need an extra field (e.g. product reviews)? Open an issue on the actor's **Issues** tab and we'll take a look.

### Additional services

Need a custom scraper, a recurring schedule, or the data pushed to your database/webhook? We build and maintain review, directory and e-commerce scrapers across many platforms — get in touch via the Issues tab.

### Explore more scrapers

Collecting reviews across platforms? Pair this with our **TrustMate.io Reviews Scraper** (Poland/EU) and scrapers for the larger global review sites. Check the publisher's other actors on the Apify Store.

### 🤖 For AI Agents & LLM Apps

Compact reference for AI agents calling this actor via the [Apify MCP server](https://mcp.apify.com) or the Apify API (actor: `memo23/feedaty-reviews-scraper`).

**Purpose:** Extract merchant reviews from Feedaty.com (the Italian e-commerce review platform by Zoorate) — every review's text, rating, date and language, plus one merchant-summary row per shop with lifetime totals and rating windows.

**Minimal input:**

```json
{
  "startUrls": ["https://www.feedaty.com/recensioni/caffevergnano"],
  "companySlugs": [],
  "maxItems": 20,
  "maxConcurrency": 4
}
```

A bare domain or slug (e.g. `"diadora.com"`) also works inline in `startUrls` or in `companySlugs`.

**Output:** two row kinds keyed by `recordType`. Review rows — recordType "review", platform, reviewId, rating, bestRating, reviewBody, authorName (always "Utente Feedaty"), reviewDate, language, merchantSlug, companyName, companyUrl, companyRatingAvg, companyReviewCount, sourceUrl, scrapedAt. Merchant-summary rows (one per merchant) — recordType "merchant\_summary", merchantCode, totalReviewCount, totalReviewAvg, starBreakdown {star5..star1}, last12Months / last3Months / lastMonth {avg, count}, otherChannels\[], subscriptionStatus, lastReviewDate, reviewsInMediationCount, monthlyTrend\[].

**Behaviors an agent should know:**

- Full review history is paginated and de-duplicated by reviewId; `maxItems` caps review rows only.
- Exactly one merchant\_summary row is pushed per merchant regardless of `maxItems` — it never displaces a paid review row.
- Reviewers are anonymised by Feedaty (`authorName` is always "Utente Feedaty"); company replies and verified-purchase flags are not exposed.
- Leave `proxy` empty — Feedaty has no anti-bot protection and the default proxy is sufficient.
- Public certificate pages only; no login-gated fields. Pay-per-result billing — charged per review row; the merchant-summary row is not counted.

### ⚠️ Disclaimer

This actor collects only **publicly available** information from Feedaty.com — the same data any visitor can see without logging in. It does not bypass authentication, access private data, or collect personal reviewer identities (Feedaty anonymises these). Use the data in compliance with Feedaty's Terms of Service, applicable laws (including GDPR and other data-protection regulations), and the rights of data subjects. You are responsible for how you use the scraped data; review text is the intellectual property of its authors and platform. This actor is not affiliated with, endorsed by, or sponsored by Feedaty or Zoorate.

### SEO keywords

Feedaty scraper, Feedaty.com reviews scraper, scrape Feedaty reviews, Feedaty recensioni scraper, Italian reviews scraper, Italian e-commerce reviews, Zoorate reviews, merchant reviews scraper, e-commerce reviews scraper, online review data Italy, reputation monitoring Italy, competitor review analysis, voice of customer Italy, review export CSV JSON, EU reviews scraper.

# Actor input Schema

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

Feedaty merchant review URLs (e.g. https://www.feedaty.com/recensioni/caffevergnano) or bare domains/slugs (e.g. caffevergnano.com). Each is resolved to the merchant's review feed.

## `companySlugs` (type: `array`):

Convenience list of bare merchant slugs or domains (e.g. caffevergnano, diadora.com). Resolved to review URLs the same way as Start URLs.

## `maxItems` (type: `integer`):

Hard cap on the total number of review rows collected across all merchants. Use it to control billing.

## `maxConcurrency` (type: `integer`):

How many merchants to fetch in parallel. Review pages within one merchant are fetched sequentially.

## `proxy` (type: `object`):

Leave empty — the actor already routes all traffic through its own built-in residential proxy at no extra cost to you. Only set this if you want to use your own proxies.

## Actor input object example

```json
{
  "startUrls": [
    "https://www.feedaty.com/recensioni/caffevergnano"
  ],
  "maxItems": 1000,
  "maxConcurrency": 4
}
```

# 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.feedaty.com/recensioni/caffevergnano"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("memo23/feedaty-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.feedaty.com/recensioni/caffevergnano"] }

# Run the Actor and wait for it to finish
run = client.actor("memo23/feedaty-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.feedaty.com/recensioni/caffevergnano"
  ]
}' |
apify call memo23/feedaty-reviews-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,memo23/feedaty-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/SBTQqx5CkQmFZI0Wp/builds/aMOpf55oocQMj8YXM/openapi.json