HolidayCheck Hotel Reviews & Ratings Scraper
Pricing
from $4.00 / 1,000 hotel scrapeds
HolidayCheck Hotel Reviews & Ratings Scraper
Extract German-language hotel reviews, ratings and profiles from HolidayCheck. 900,000+ hotels worldwide with guest reviews, 1-10 ratings, review counts and addresses.
Pricing
from $4.00 / 1,000 hotel scrapeds
Rating
0.0
(0)
Developer
GTForge Data
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
Extract German-language hotel reviews and ratings from HolidayCheck — the DACH region's largest hotel review platform, covering 900,000+ hotels worldwide.
Built for hotel reputation management, hospitality benchmarking, travel analytics and market research teams who need structured German-market review data.
What you get
Per hotel:
| Field | Detail |
|---|---|
| Profile | name, HolidayCheck id, full postal address, region, country, telephone |
| Aggregate rating | native 1–10 score and a 0–5 normalisation for cross-source comparison |
| Review count | the hotel's total review count, so you know what a sample represents |
| Reviews | headline, full review text, author, ISO-8601 publish date, per-review 1–10 rating |
| Amenities | amenity features as published |
Why the German market
HolidayCheck is where German, Austrian and Swiss travellers actually write hotel reviews. If you are benchmarking a DACH property, or tracking a portfolio's reputation in German, this is the source that matters — and it is not covered by the English-language review platforms.
Use cases
- Hotel reputation monitoring — track score and new German-language reviews over time
- Competitive benchmarking — compare a property against its local set
- Portfolio tracking — sweep every hotel in a region or chain
- Market research — 900,000+ hotels with ratings, review volume and location
- Text analytics — clean German review text for sentiment and topic work
Input
| Field | Meaning |
|---|---|
venueUrls | Hotel or review page URLs; a bare hotel UUID also works |
discoverAll | Ignore the list and enumerate hotels from the sitemaps |
maxVenues | Bound the run (default 100) |
includeReviews | Off = profiles + aggregate ratings only, at lower cost |
outputMode | venue (nested), review (flat rows), or both |
{"venueUrls": ["https://www.holidaycheck.de/hi/entdeckerhotel-panorama/4b53f727-a5c5-36bb-8fc1-63c039565112"],"includeReviews": true,"outputMode": "venue"}
Output
{"source": "holidaycheck","venueId": "4b53f727-a5c5-36bb-8fc1-63c039565112","name": "Entdeckerhotel Panorama","address": {"street": "Sonnenstr. 11","city": "Chienes / Kiens","region": "Südtirol","country": "Italien"},"aggregate": {"rating": { "native": 10, "nativeScale": 10, "normalised": 5 },"count": 58},"reviews": [{"title": "Ein gelungener Familienurlaub mit viel Komfort und Genuss.","text": "Das Hotel ist einfach wundervoll für einen Urlaub in dem die Eltern...","rating": { "native": 10, "nativeScale": 10, "normalised": 5 },"author": { "name": "Martina" },"publishedAt": "2025-12-25T21:29:22.000Z","language": "de"}],"reviewsTruncated": true,"totalReviewCount": 58}
Pricing
Pay per event — you pay for what you extract, no monthly rental:
| Event | When |
|---|---|
actor-start | Once per run, per GB of memory |
venue-scraped | Per hotel profile returned |
review-scraped | Per individual review returned |
Turning includeReviews off charges only venue-scraped.
An honest note on review coverage
HolidayCheck publishes each hotel's most recent reviews on the page, typically around ten,
alongside the hotel's total review count. This actor returns those, and sets
reviewsTruncated: true with the real totalReviewCount whenever a hotel has more than were
served.
For reputation monitoring — where recent reviews are the signal — that is the whole job. If you need complete historical archives of every review ever written, this actor is not that tool, and says so here rather than quietly handing you a partial set.
Requests are rate-limited to one per 700 ms per host. Discovery uses HolidayCheck's own published sitemaps rather than guessed URLs, and the actor reads only paths the site's robots.txt permits.
Support
Open an issue on the actor page. Bug reports with the hotel URL attached get fixed fastest.