HolidayCheck Reviews Scraper

Extract HolidayCheck hotel reviews in a flat structured dataset that is ready for research, monitoring, analysis, and enrichment. Collect review headlines, review text, traveler context, travel dates, recommendation status, owner replies, topic summaries, and simplified contribution values from HolidayCheck hotel review pages at scale.

Features

• Review-first extraction — Collect individual HolidayCheck hotel reviews instead of hotel listing records
• Direct hotel-review inputs only — Accept only direct HolidayCheck hotel review-style URLs that resolve to a single hotel
• Filter-aware collection — Respect review-page filters already present in the input URL, including sort and topic slices
• Flat review records — Flatten reviewer, owner reply, topic, and contribution data into analysis-friendly fields
• Clean datasets — Remove null and empty values automatically so exports stay compact and production-friendly

Use Cases

Reputation Monitoring

Track what guests are saying about a hotel over time. Monitor recommendation status, owner responses, and recurring themes across new reviews.

Travel Research

Compare real guest experiences before planning content, making recommendations, or building destination research databases. Use reviewer type and travel dates to segment feedback.

Competitive Analysis

Collect review datasets from multiple hotels and compare guest sentiment, repeated complaints, and service strengths across competing properties.

Data Enrichment

Send structured HolidayCheck review data into BI tools, spreadsheets, CRMs, warehouses, or custom quality-monitoring workflows.

---

Input Parameters

Parameter	Type	Required	Default	Description
urls	Array	Yes	—	One or more direct HolidayCheck hotel review-style URLs. Supported paths are /hr/, /hi/, /ho/, /hm/, /ha/, and /wcf/hotelreview/contribution/ when they include a hotel ID.
results_wanted	Integer	No	20	Maximum number of review items to collect across all provided URLs.
max_pages	Integer	No	2	Safety cap for pagination. Each review API page contains up to 10 reviews.
review_sort	String	No	relevance	Review sort mode. Supported values are relevance, entrydate, positive, and negative. When set, it overrides any sort already present in the URL.
proxyConfiguration	Object	No	{"useApifyProxy": false}	Optional proxy configuration for more reliable production runs.

---

Output Data

Each dataset item can contain the following fields:

Field	Type	Description
review_id	String	HolidayCheck review ID
hotel_id	String	HolidayCheck hotel ID
hotel_name	String	Hotel name returned with the review
review_title	String	Review headline
review_position	Integer	Position of the review in the collected dataset
review_page	Integer	Review page number on HolidayCheck
sort	String	Sort mode derived from the review URL
traveled_with	String	Travel companion category such as couple or family
recommendation	Boolean	Whether the reviewer recommends the hotel
proofed_reservation	Boolean	Whether the review is tied to a verified reservation
ranking	Number	HolidayCheck ranking score for the review
entry_date	String	Review publication date in ISO format
travel_date	String	Travel month represented as an ISO date
original_locale	String	Original review locale
returned_locale	String	Locale returned in the response
review_text	String	Main free-text hotel review body when available
overall_rating	Number	Overall structured rating when available
owner_comment_text	String	Hotel owner reply text
owner_comment_entry_date	String	Hotel owner reply date
user_first_name	String	Reviewer first name
user_age_group	String	Reviewer age group
user_hotel_review_count	Integer	Number of hotel reviews shown for the reviewer
topic_ids	Array	Flattened topic identifiers
topic_names	Array	Flattened topic names
topic_quotes	Array	Flattened topic quotes
service_opinion, room_opinion, restaurant_opinion, etc.	Mixed	Flattened contribution fields, one value per field

---

Usage Examples

Direct Review Page

Use a HolidayCheck review page directly:

{
  "urls": [
    {
      "url": "https://www.holidaycheck.de/hr/bewertungen-pickalbatros-dana-beach-resort-hurghada/1aa4c4ad-f9ea-3367-a163-8a3a6884d450"
    }
  ],
  "results_wanted": 20,
  "max_pages": 2,
  "review_sort": "relevance"
}

Hotel Page Input

Start from a direct hotel page that contains the hotel ID:

{
  "urls": [
    {
      "url": "https://www.holidaycheck.de/hi/pickalbatros-dana-beach-resort-hurghada/1aa4c4ad-f9ea-3367-a163-8a3a6884d450"
    }
  ],
  "results_wanted": 15,
  "max_pages": 2,
  "review_sort": "entrydate"
}

Review URL With Sort

Use an already filtered review URL and still force the API sort through input:

{
  "urls": [
    {
      "url": "https://www.holidaycheck.de/hr/bewertungen-pickalbatros-dana-beach-resort-hurghada/1aa4c4ad-f9ea-3367-a163-8a3a6884d450?sort=negative"
    }
  ],
  "results_wanted": 20,
  "max_pages": 2,
  "review_sort": "positive"
}

Sample Output

{
  "review_id": "ee20b26c-d6b7-4272-aad5-ff3d3ac61940",
  "hotel_id": "1aa4c4ad-f9ea-3367-a163-8a3a6884d450",
  "hotel_name": "Pickalbatros Dana Beach Resort - Hurghada",
  "review_title": "Service nach wie vor Top, Auswahl und Qualität bei Speisen und Getränken deutlich verschlechtert.",
  "review_position": 1,
  "review_page": 1,
  "sort": "relevance",
  "traveled_with": "COUPLE",
  "recommendation": false,
  "proofed_reservation": true,
  "ranking": 0.7916,
  "entry_date": "2026-02-19T08:45:16.000Z",
  "travel_date": "2026-02-01",
  "user_first_name": "Dirk",
  "user_age_group": "FROM_51_TO_55",
  "user_hotel_review_count": 115,
  "owner_comment_text": "Liebe Sonja, Es freut uns sehr, dass Sie sich die Zeit genommen haben, Ihre Eindrücke mit uns zu teilen.",
  "review_text": "Das Dana Beach lebt von seinem Personal.",
  "overall_rating": 0.8,
  "topic_ids": ["SERVICE", "SUSTAINABILITY", "ENTERTAINMENT"],
  "topic_names": ["Service", "Nachhaltigkeit", "Unterhaltung"],
  "service_opinion": "Das Dana Beach lebt von seinem Personal.",
  "room_opinion": "Wir hatten ein Upgrade auf ein Superiorzimmer erhalten."
}

---

Tips for Best Results

Prefer Direct Review URLs

• Use /hr/ review URLs when possible
• These URLs can already contain the exact sort and filter combination you want

Start Small for Validation

• Use results_wanted: 20 for quick checks
• Increase max_pages only when you need deeper review coverage

Use Multiple URLs Intentionally

• Combine several direct hotel or review URLs in one run when you want one shared dataset
• The actor stops once it reaches the total results_wanted limit

Use Proxies for Larger Jobs

• Add proxy configuration for heavier schedules or wider hotel coverage
• This is useful when processing many direct hotel review URLs

---

Integrations

Connect your data with:

• Google Sheets — Export review datasets for quick analysis
• Airtable — Build searchable guest-feedback databases
• Make — Trigger downstream monitoring workflows
• Zapier — Send review data into business tools
• Webhooks — Push data into custom systems or pipelines

Export Formats

• JSON — For APIs and engineering workflows
• CSV — For spreadsheets and reporting
• Excel — For business users and analysts
• XML — For structured integrations

---

Frequently Asked Questions

Which HolidayCheck URLs are supported?

Direct review pages work best. Hotel pages, offer pages, listing pages, and destination pages are also supported.

Can I use filters that already exist in the review URL?

Yes. If your review URL already contains a sort or topic filter, the actor keeps that behavior.

Does the actor collect empty fields?

No. Empty, null, and undefined values are removed automatically before the dataset is saved.

Can I collect reviews from multiple hotels in one run?

Yes. Add multiple HolidayCheck URLs to urls, and the actor will process them in order until it reaches the requested result limit.

Why do some reviews contain more fields than others?

HolidayCheck does not return the same contribution blocks or owner replies for every review. The actor keeps whatever structured data is available for each item.

What happens when I use a destination or listing URL?

The actor first resolves hotels from that HolidayCheck URL and then collects reviews for those hotels.

---

Support

For issues or feature requests, contact support through the Apify Console.

Resources

• Apify Documentation
• Apify API Reference
• Apify Schedules

---

Legal Notice

This actor is designed for legitimate data collection purposes. Users are responsible for ensuring compliance with HolidayCheck terms and all applicable laws. Use collected data responsibly and at appropriate request volumes.