# Guest reviews from five sources, as one feed

> Tripadvisor, Booking.com, Expedia, Hotels.com and Google Hotels reviews, page by page, with the rating, the text, the stay details and the management reply kept as structured fields.

Canonical page: https://scrapercompany.com/use-cases/hotel-review-monitoring. Built for: Reputation teams, Hotel groups, Hospitality agencies, Guest-experience analysts.

## The problem

Reputation lives in five places, and each one pages, rates and labels reviews differently. Tripadvisor scores out of 5, Expedia out of 10. Booking.com publishes category scores, and Google mixes its own reviews with partner sites.

Analytics needs one shape: who wrote it, when they stayed, what they scored, what they said and whether the hotel answered. That is how you measure review velocity and response coverage across a portfolio.

## How it works

1. **Identify the property on each site.** Use the Tripadvisor location id, the Booking.com page name, the Expedia or Hotels.com id, or the Google property token.
2. **Page through new reviews.** Each source pages its own way, and each answer says how to fetch the next page. Reviews come newest first where the site supports it. Endpoint: [`POST /v1/ota/tripadvisor/reviews`](https://scrapercompany.com/docs/reference/tripadvisor-reviews), 1 credit.
3. **Store the fields you track.** Rating, text, stay summary, the site's own labels (such as Expedia's verified-review flag) and the management reply, when there is one.
4. **Score, summarize and alert.** Run each review through your sentiment model or an LLM to tag topics and tone, summarize the week, and alert on unanswered complaints.

## What you get back

- **Review text**: title and body as the guest wrote them
- **Ratings**: on each site's own scale, plus Booking.com category scores
- **Stay details**: stay summaries such as "Stayed 4 nights in Sep 2026"
- **Management replies**: the hotel's answer, where the site shows one
- **Ready for analysis**: one review per row, so sentiment and topic models need no scraping cleanup

## Worked example (illustrative)

An agency watches 40 hotels for new reviews on four sites, once a day.

- Newest review page, 40 hotels × 4 sources: 160 calls a day × 1 credits = 160 credits a day
- About 4,800 credits a month (30 days)

Pricing: free trial of 50 calls or 14 days, whichever ends first, no card needed; Starter $49/month for 40,000 credits; Growth $149/month for 150,000 credits; Scale $399/month for 500,000 credits; Business $999/month for 1,500,000 credits; credit packs $15 for 7,500, $60 for 35,000, $200 for 125,000 (valid 12 months). Failed requests (4xx or 5xx) and empty results cost 0 credits. https://scrapercompany.com/pricing

## FAQ

### Which review sites are supported?

Tripadvisor, Booking.com, Expedia, Hotels.com and Google Hotels. Google Hotels also returns partner reviews, such as Tripadvisor and Priceline, and names the provider on each row.

### How much does a page of reviews cost?

Two credits per page from any source. A page with no reviews is free, and failed requests are free.

### Does the API do sentiment analysis?

No. It returns the reviews as structured fields, and scoring and summarizing run in your stack with the model you choose. The shape suits that work: one review per row with its text, its rating on the site’s own scale, stay details and the management reply.

### Do reviews include the hotel’s reply?

Yes, where the site publishes one: the management reply is a field on the review.

### Are review dates exact?

Tripadvisor, Booking.com and Expedia publish dates. Google Hotels shows only relative dates such as "a month ago", and the API returns exactly what Google shows.

## Read next

- [Guide: scrape guest reviews](https://scrapercompany.com/docs/guides/hotel-reviews)
- [Hotel reviews API](https://scrapercompany.com/hotel-reviews-api)
- [Hotel price API](https://scrapercompany.com/hotel-price-api)
- [Credits per endpoint](https://scrapercompany.com/docs/credits)
