Give it an Expedia hotel URL - or just the numeric hotel id - and get that property's guest reviews back as rows: the reviewer, the rating, the date, the headline and the full review text. Four sort orders and an oldest-first toggle are set before the run, so the slice you pay for is the one you meant to read.
The input is the property, not the review - you name the hotels you want feedback on, pick the order and the direction, and the job collects what their guests wrote.
One row per review, each tagged with the query it came from - so a run across fifty properties still reconciles back to your input list.
The hotel id is the number sitting inside the Expedia address - .h41313. - and this form takes it on its own. A column of ids in a spreadsheet is therefore a valid input list, with no URL to reconstruct first, and a full hotel URL works exactly as well when that is what you have.
Most relevant, most recent, highest guest rating or lowest - plus a From (oldest first) toggle that flips the direction independently. Pair a sort with a small limit and you buy the complaints or the launch-period reviews rather than a whole history you then have to sift.
Worth knowing before your first run: this form ships with the per-query limit pre-filled at 100. The hint says to leave it empty to fetch all, which means clearing the box rather than leaving it as delivered. A first run left untouched is capped, and that is a cost decision made for you unless you change it.
Each row carries the review as Expedia displays it: who wrote it, the rating, the date, the headline and the full text.
Review text comes back verbatim, with no preprocessing applied. The column list below is the platform's own, and both download paths - JSON and Excel - project through it in the same order, so the file you get carries these six names whichever button you press. Read the note under the table before you write a parser: the names are verified and the value formats are not.
The platform's own column list, in export order, confirmed identical across the JSON and Excel download paths. Descriptions say what each field is for; they claim nothing about its format - see the note underneath.
Read this dictionary as a list of names, not a promise about contents. The six names and their order are solid: they come from the platform's published column list, and the JSON and Excel downloads both project through that same list in that same order. What is not settled is the shape of the values, because we hold no archived Expedia Reviews export at all - not an empty one, not a full one. So this page states no date pattern, no rating scale or range, and no fill rate for any column. query is the exception the mechanism guarantees: the scraper writes it rather than reading it off the page, so it is on every row. One more thing worth knowing: this schema is byte-identical to the one on the Hotels.com reviews scraper - same six names, same order - but they are separate services, and neither one's values tell you anything about the other's. Pull a free run and read the first rows before you assume anything else.
A per-query limit decides what a run costs and how much lands in the file. The sort order and the direction decide which reviews that limit spends itself on - all three are chosen before the job starts.
A few examples of how teams use guest review data to answer a question they actually have.
Pull your own property sorted by lowest guest rating with a modest limit. You get the complaints at the top of the file rather than at the bottom of a full history, which means the read is short and the credits went where the problem is.
Turn on From (oldest first) and the file begins where the property did. Launch-period complaints are the ones that tell a fixed problem from a buried one, and they are exactly the reviews a default run never reaches.
If your portfolio or your competitive set already lives in a spreadsheet as Expedia ids, that column is the input - paste it or upload the file, no URLs to build. The query column echoes whatever you sent, so the export joins straight back to the sheet it came from.
No subscription, no minimum, no recurring bill. Your first 500 rows are on us - after that, pay-as-you-go at the same flat rate as every other scraper here.
Every new account, one-time. No credit card required. Per-query limits, every sort order, file upload and every export format included.
Roughly $2 per 1,000 reviews. The pre-flight estimator shows the row count and credit cost before a run starts - no surprise bills, no compute units to translate.
Volume pricing, dedicated workers and an SLA for continuous monitoring or very large historical pulls. Tell us your numbers and we will quote.
LIVESCRAPER10 at checkout.The same six columns in the same order, pointed at Hotels.com. Two differences worth knowing: it takes a URL only, and its limit arrives empty rather than pre-filled.
The same properties as travellers rate them elsewhere, with two columns this one does not have: the kind of trip the reviewer was on, and the language they wrote in.
Short answer: yes for the public review content - and this export carries nothing about the booking behind it.
Guest reviews on Expedia are published to be read. The rating, the headline, the review text and the date are shown to anyone who opens the property page, signed in or not. Collecting publicly visible feedback for research is long-established practice, and nothing here touches a login, a booking or a paywall.
The reviewer field carries what the site itself publishes, which is a display name rather than a full identity - there is no email and no address in this output. Nothing about the stay behind a review is collected either: not what was paid, not the dates, not the room. If you are processing the review text in the EU, the usual rules still apply to what you do with it downstream.
Expedia's own terms restrict automated access, so this is a terms question as well as a legal one - if you have a contractual relationship with the platform, check it. We run no third-party trackers on the data layer, and your exports auto-delete after 30 days.
The questions we hear most. Anything else? Talk to us - humans, not bots, write the answers.
500 one-time free rows on every new account - no expiry. After that it is $0.002 per row, pay-as-you-go - no card on file until you say so.
Livescraper's Expedia Reviews Scraper turns a list of properties into review data. You submit Expedia hotel URLs or bare hotel ids - typed one per line, or uploaded as a CSV, XLSX, TXT or Parquet file - set a limit per query or clear it to fetch all, choose the sort order and the direction, and download what guests wrote as a clean CSV, Excel or JSON file.
Accepting the id on its own is the practical difference. The hotel id is the number sitting inside the Expedia address, so a column of ids in a spreadsheet is already a valid input list with no URLs to reconstruct - and because the query column echoes back exactly what you sent, the export joins straight to the sheet it came from.
Each row carries the review as Expedia displays it: the reviewer, the rating, the date, the headline and the full review text. The headline and the body stay separate columns, so the short verdict a guest writes above the explanation is available on its own, and the body arrives verbatim with no preprocessing. Four sort orders and an oldest-first toggle decide which reviews a limit spends itself on: lowest first for the complaints, oldest first for the launch period that a default run never reaches.
One practical note up front. This page describes the six columns and their order, which the platform's published list and both of its download paths agree on exactly, but it claims no date pattern, no rating scale and no fill rates, because no archived Expedia Reviews export exists to base them on. The same schema also appears on the Hotels.com reviews scraper - identical names, identical order, separate services - so neither one's values tell you anything about the other's. Pull a free run and read the first rows before you build against it. Your first 500 rows cost nothing and need no credit card, and after that it is $0.002 per row, flat.