# Changelog of HRS Hotel & Reviews Scraper — Hotels, Ratings & Guest Reviews (`haketa/hrs-scraper`) Actor

- **URL**: https://apify.com/haketa/hrs-scraper/changelog.md
- **Full Actor documentation**: https://apify.com/haketa/hrs-scraper.md

## Changelog

### 1.0.0 — 2026-11-01

- **Verified at scale:** fresh auto-discovery run collected **400 unique HRS hotels** (0 duplicates) from the public sitemaps in **~115s** on datacenter proxy — no residential needed.
- **Core-field coverage 100%:** `hotelId`, `name`, `stars`, `url`, `street`, `city`, `postalCode`, `country`, `latitude`, `longitude`, `rating`, `reviewCount`, `amenities` and `paymentAccepted` all populated on every record; `images` at 99%.
- **Rich reviews confirmed:** 67% of hotels returned embedded guest reviews (623 reviews across the run), with per-review `categoryRatings`, `overallRating`, `date`, `travellerType`, `locale` and `recommends` at 100% coverage.
- **Fixed review-text formatting:** guest comments and hotel responses no longer contain leaked `\n`/`\t` escape artifacts from the page payload — text now reads cleanly (fixed ~14% of review text fields).
- **Documented all per-category scores:** added `restaurantService` and `wellnessRanking` to the documented `categoryRatings` keys (already captured dynamically by the scraper).
- **README refreshed** to the gold standard: output example and field reference now match the live response exactly, with honest coverage notes (e.g. `region` is rarely exposed by HRS).
- No input or output field names were changed — fully backward compatible.
