Reviews.io Scraper FAST | Exact Dates | Votes | Intel avatar

Reviews.io Scraper FAST | Exact Dates | Votes | Intel

Pricing

from $4.00 / 1,000 results

Go to Apify Store
Reviews.io Scraper FAST | Exact Dates | Votes | Intel

Reviews.io Scraper FAST | Exact Dates | Votes | Intel

The cheapest way to scrape Reviews.io reviews: extract company reviews, verified buyer ratings, merchant replies, helpful votes and exact dates from JSON-LD — no browser needed. Build reputation datasets, monitor competitors and track review sentiment for $0.005 per review.

Pricing

from $4.00 / 1,000 results

Rating

0.0

(0)

Developer

Ahmed Jasarevic

Ahmed Jasarevic

Maintained by Community

Actor stats

0

Bookmarked

3

Total users

2

Monthly active users

5 days ago

Last modified

Categories

Share

Reviews.io Scraper — Customer Reviews, Verified Ratings & Merchant Replies

Scrape Reviews.io company reviews at $0.005 per result — with no headless browser, no login and no CAPTCHA solving. This actor pulls exact review dates from the page's JSON-LD (data the UI hides behind "Posted 2 days ago"), helpful-vote counts from Reviews.io's own internal JSON API, verified-buyer flags, photo galleries and merchant replies — a cheap, structured window into the reputation data of the 100k+ European businesses that use Reviews.io.

Main Use Cases

  • Competitor reputation tracking — monitor rival brands' Reviews.io profiles weekly and catch rating drops, complaint spikes and negative review trends early.
  • Merchant service audits — measure how fast merchants reply to reviews, what they reply, and which negative reviews go unanswered.
  • Ecommerce review monitoring — track ratings, recommend percentages and review velocity across UK and European online stores.
  • Review sentiment analysis — build text datasets of verified customer feedback for sentiment models, topic clustering and CX analytics.
  • Lead generation for review-management agencies — identify merchants with weak ratings or slow reply times and target them with reputation services.
  • Reviews.io vs Trustpilot comparison — combine Reviews.io data with Trustpilot datasets to benchmark the same brands across both platforms.

How the Reviews.io Scraper Works

This actor is a pure HTTP + Cheerio crawler — it requests the server-rendered HTML of Reviews.io company review pages, so no browser, no rendering engine and no extra memory are needed. For each company it:

  1. Reads the company profile — average rating, review count, recommend percentage, store ID and about text.
  2. Parses every review card on the page — author, stars, verified-buyer badge, text, date text and merchant reply.
  3. Matches each review to its exact datePublished timestamp from the JSON-LD block server-rendered into the page.
  4. Hydrates each review with helpful-vote counts and sub-ratings from the same internal JSON API the Reviews.io frontend uses (/company-reviews/data/{storeId}?ids=...).
  5. Collects review photo URLs from the gallery sidebar.
  6. Follows pagination until maxReviewsPerCompany is reached (or 10 per company on free runs).
  7. Optionally visits the product-reviews list page when includeProductReviews is enabled, saving product-level ratings and per-product review rows.

Get Exact Review Dates the UI Hides

Reviews.io renders review dates as relative text ("Posted 57 minutes ago", "Posted 1 week ago"). The real timestamps exist only in the page's JSON-LD structured data. This actor reads datePublished from JSON-LD and returns an exact ISO date (e.g. 2026-09-18) on every review and product review — essential for chronological datasets, measuring review velocity, and deduplicating incremental runs.

Track Competitor Reviews and Merchant Replies

Every review row includes the merchant reply and its date when one exists. That makes it possible to audit response times, spot unanswered negative reviews, and benchmark customer-service quality across a whole competitor set — the classic groundwork for competitive intelligence and agency outreach.

Build Ecommerce Review Databases Without the Official API

Reviews.io does not offer free public read access to company review pages: its developer API (developer.reviews.io) is a merchant-facing collection/sync API gated to paid plans, used to send invitations and retrieve a merchant's own reviews. There is no public endpoint to dump another company's review history. This scraper is the practical route to a structured, queryable database of Reviews.io reviews — company profiles, verified buyer ratings, product ratings and replies.

Input — Configure the Reviews.io Scraper

FieldTypeRequiredDefaultNotes
companyUrlsarray of stringsYes—Reviews.io company review page URLs (https://www.reviews.io/company-reviews/store/notino) or bare store slugs (notino). One entry per company.
maxReviewsPerCompanyintegerNo100Maximum number of individual reviews saved per company. 0 = all available (schema limit 100,000).
includeProductReviewsbooleanNofalseAlso scrape the company's product-reviews list page (product name, rating, review count) plus per-product review rows.
proxyobjectNodisabledApify proxy configuration (useApifyProxy, groups, countryCode). Only needed for large multi-company runs.

Output — Dataset Fields

One dataset row is saved per entity. Every row carries a type field: company, review, product or product_review.

FieldTypeApplies toDescription
typestringallRow type: company, review, product, product_review
companyNamestringallCompany or store name
slugstringallStore slug from the URL
urlstringcompany, reviewPage URL of the company profile or the individual review
ratingnumber | nullcompany, productCompany or product average rating
reviewCountnumbercompany, productCompany or product review count
recommendPercentnumber | nullcompany% of reviewers who recommend the company
storeIdstringcompanyInternal Reviews.io store ID used for the JSON API call
aboutstring | nullcompanyCompany about text
productNamestringproduct, product_reviewProduct name
productUrlstringproductProduct review page URL
skustringproduct_reviewProduct SKU
reviewIdstringreview, product_reviewReview ID
authorstringreview, product_reviewReviewer display name
starsnumberreview, product_reviewStar rating (1–5)
verifiedBuyerbooleanreview, product_reviewVerified Buyer/Buyer badge present on the review
datestring | nullreview, product_reviewExact review date from JSON-LD (datePublished)
dateTextstringreview, product_reviewDate string as displayed on the page
textstringreview, product_reviewReview body text
photosarrayreviewPhoto URLs attached to the review
helpfulVotesnumberreview, product_reviewHelpful-vote count from the internal JSON API
subRatingsobject | nullreviewSub-ratings per category returned by the JSON API
replystring | nullreview, product_reviewMerchant reply text
replyDatestring | nullreview, product_reviewMerchant reply date string
scrapedAtstringallISO timestamp of the run

Example Input

{
"companyUrls": [
"notino",
"https://www.reviews.io/company-reviews/store/loveholidays-com"
],
"maxReviewsPerCompany": 100,
"includeProductReviews": false
}

Example Output

[
{
"type": "company",
"companyName": "Notino",
"slug": "notino",
"url": "https://www.reviews.io/company-reviews/store/notino",
"rating": 4.6,
"reviewCount": 3832,
"recommendPercent": 90,
"storeId": "notino",
"about": null,
"scrapedAt": "2026-09-19T08:00:00.000Z"
},
{
"type": "review",
"companyName": "Notino",
"slug": "notino",
"reviewId": "123456789",
"author": "Anonymous",
"stars": 5,
"verifiedBuyer": true,
"date": "2026-09-18",
"dateText": "Posted 1 day ago",
"text": "Great prices and fast delivery service. Thank you.",
"photos": [],
"helpfulVotes": 3,
"subRatings": null,
"reply": null,
"replyDate": null,
"url": "https://www.reviews.io/company-review/store/notino/123456789",
"scrapedAt": "2026-09-19T08:00:00.000Z"
}
]

Integrations & Automation

  • Apify API — run this actor programmatically via POST /v2/acts/~username~reviews-scraper/runs (or the actor ID endpoint) with your Apify token.
  • Scheduled runs — Reviews.io data changes constantly. For competitor monitoring, schedule a monthly (or weekly) run in the Apify console; recurring runs also improve Apify Store recommendation signals for this actor.
  • Webhooks — attach a webhook to the run to push each finished dataset straight into your pipeline.
  • Zapier / Make — Apify's official integrations connect the actor's dataset to thousands of apps (Google Sheets, Slack, Airtable, BI tools).
  • Export — results are downloadable as JSON, CSV or Excel from the dataset, or queryable via the Apify Dataset API.

FAQ

Is there a Reviews.io API?

Yes — Reviews.io has a developer API (developer.reviews.io), but it is a merchant-facing API for syncing orders, sending review invitations and retrieving a merchant's own reviews, and it is gated to paid plans (the API is available on the Plus package). There is no free public API to read other companies' review pages, which is why scraping is the standard route to third-party Reviews.io data.

How do I scrape Reviews.io reviews?

Paste Reviews.io company review URLs or bare store slugs (e.g. notino) into companyUrls, set maxReviewsPerCompany, and run. This actor needs no browser, no login and no CAPTCHA solving — results land in an Apify dataset as JSON, CSV or Excel.

Reviews.io vs Trustpilot — which should I use?

They solve different problems. Reviews.io is an ecommerce-first, verification-first platform (reviews tied to confirmed purchases, on-site widgets, Google Seller Ratings, cheaper tiers) popular with UK and European online stores. Trustpilot is a public open review network with stronger consumer brand recognition and Google visibility, at a higher price. For reputation research, scraping both and comparing the same brands across platforms gives the fullest picture.

Are Reviews.io reviews verified?

Reviews.io is verification-first: reviews tied to a confirmed purchase, email and moderation carry a Verified Buyer / Verified Reviewer badge, and reviews without it display as Unverified Reviewer. The actor returns the verifiedBuyer flag per review so you can filter and analyse verified vs unverified feedback.

How do I get exact review dates?

The Reviews.io UI shows relative dates ("Posted 2 days ago"). This actor reads the ISO datePublished values from the page's JSON-LD and returns them in the date field — exact per-review timestamps the UI does not display.

Where do helpful votes come from?

Reviews.io's own frontend loads helpful-vote counts and sub-ratings from an internal JSON endpoint (/company-reviews/data/{storeId}?ids=...). This actor calls the same endpoint the site uses and attaches those numbers to each review.

Does this actor need proxies?

No. It requests plain server-rendered HTML, so it works out of the box without proxies. The proxy input exists for large multi-company runs where you want to distribute requests.

This actor only reads publicly available pages — no login, no CAPTCHA bypass, no private data access. Users are responsible for complying with Reviews.io's Terms of Service and applicable data-protection law when using scraped data.

SEO Keywords

reviews.io scraper, scrape reviews.io reviews, reviews.io api alternative, reviews.io vs trustpilot, trustpilot vs reviews.io, scrape customer reviews, competitor reputation monitoring, merchant reply tracking, review monitoring tool, review analytics, review sentiment analysis, verified buyer reviews, product review data, ecommerce review monitoring, uk review platform, reviews.io dataset, how to scrape reviews.io, merchant review tracking, review management agencies, reputation intelligence, helpful vote counts, exact review dates, google seller ratings, product rating extraction

For AI Agents & LLM Apps

  • Purpose — Returns structured Reviews.io data (company profiles, company reviews, product-level ratings, product reviews) as dataset rows distinguished by the type field.
  • Minimal working input — {"companyUrls": ["notino"]} produces one company row plus up to 100 review rows (10 on free plan).
  • Variant inputs — {"companyUrls": ["mobile-outfitters"], "includeProductReviews": true} also scrapes the product-reviews list and per-product review rows. {"companyUrls": ["notino"], "maxReviewsPerCompany": 0} requests all available reviews (unlimited for paying users; crawler safety-cap 500 requests per crawl).
  • Output fields — type, companyName, slug, url, rating, reviewCount, recommendPercent, storeId, about, productName, productUrl, sku, reviewId, author, stars, verifiedBuyer, date, dateText, text, photos, helpfulVotes, subRatings, reply, replyDate, scrapedAt.
  • Behaviors an agent should know —
    • companyUrls accepts full URLs or bare slugs; at least one entry is required.
    • Free users are capped at 10 reviews per company regardless of maxReviewsPerCompany; paying users are not.
    • maxReviewsPerCompany: 0 means "all available" (schema upper bound 100,000), not "zero reviews".
    • includeProductReviews: true adds product and product_review rows and one extra request per company (the product-reviews list page).
    • The date field (ISO, from JSON-LD) is more precise than dateText and is the right field for deduplication and time-series analysis.
    • helpfulVotes/subRatings come from an internal JSON endpoint and may be 0/null when that call fails.
  • Billing — pay-per-event: $0.005 per dataset row (result), $0.00005 per actor start. Budget a run as roughly $0.005 × expected rows plus the start fee.
  • This actor is an independent tool and is not affiliated with, endorsed by, or sponsored by Reviews.io (REVIEWS.io).
  • It accesses only publicly available Reviews.io company review pages — no login, no authentication bypass, no CAPTCHA solving.
  • Review text can contain personal data (names, opinions). Users are responsible for complying with Reviews.io's Terms of Service and applicable data-protection law — including the GDPR when processing reviews of EU individuals — and should minimise or pseudonymise personal data where possible.
  • Scraped review data should not be used for unsolicited contact with reviewers in violation of applicable law (e.g. CAN-SPAM, GDPR, UK PECR). This disclaimer is not legal advice.