# Expedia Proxies: 72 Words Without a Browser

> Expedia measured through residential proxies: a US exit over plain HTTP returns 72 words, h1 and canonical for 507,949 bytes; the browser returns 14 words.

[Home](https://quanticdata.io/)/[Blog](https://quanticdata.io/blog/)/Expedia Proxies: 72 Words Without a Browser

# Expedia Proxies: 72 Words Without a Browser

Use casesSep 28, 2026·9 min read·By [Aldo Morese](https://quanticdata.io/about/), founder of QuanticData

Expedia measured on 28 September 2026 through residential proxies: 507,949 bytes and 72 words over plain HTTP from the United States, 383,086 bytes and 14 words rendered, 14 words over plain HTTP from the United Kingdom, and 20 priced properties in 160 seconds from the hotels collector

On this page [What the SERP teaches, and the one thing it misses](/blog/expedia-proxies/#what-the-serp-teaches-and-the-one-thing-it-misses) [72 words over plain HTTP, 14 words rendered](/blog/expedia-proxies/#72-words-over-plain-http-14-words-rendered) [Pin the exit to the United States: the same URL returns 14 words from the UK](/blog/expedia-proxies/#pin-the-exit-to-the-united-states-the-same-url-returns-14-wo) [robots.txt fences off exactly the pages with prices](/blog/expedia-proxies/#robots-txt-fences-off-exactly-the-pages-with-prices) [Rates come from the collectors, not from the search page](/blog/expedia-proxies/#rates-come-from-the-collectors-not-from-the-search-page) [What a gigabyte buys on Expedia](/blog/expedia-proxies/#what-a-gigabyte-buys-on-expedia) [The setting that works on Expedia](/blog/expedia-proxies/#the-setting-that-works-on-expedia)

Expedia is the site where the browser returns less than the plain fetch. On 28 September 2026 we fetched the home page through a United States residential exit as a pure HTTP client and received 72 words, the h1 "The one place you go to go places", a self-referencing canonical, a description and a robots meta of index,follow, for 507,949 bytes in 4.1 seconds. The fully rendered fetch of the same URL returned 14 words. From a United Kingdom exit, the plain fetch returned 14 words as well, with no canonical and no h1. The setting for Expedia proxies is residential, `engine: tls`, country pinned to the United States for page structure, and the hotels and flights collectors for rates, because the search URLs where prices live are the ones robots.txt fences off.

## What the SERP teaches, and the one thing it misses

Nobody types "expedia proxies" into Google; autocomplete returns nothing for it and nothing for "proxies for expedia". The demand is under "expedia data scraping" and, from buyers, "expedia hotel price tracking", "price tracker", "price alert" and "price history". The first page for the scraping term is vendor pages, two tutorials, a GitHub scraper published by a vendor and a Reddit thread reporting that listing items do not render in headless mode.

The top tutorial is instructive in a way its author did not intend. It opens Selenium, loads a hotel page, finds that the prices are missing, and fixes that by adding request headers: User-Agent, Accept, Accept-Encoding, Referer. It never tries the obvious control, which is to send those headers without the browser. We did, and it is the whole post.

## 72 words over plain HTTP, 14 words rendered

We audited `expedia.com/` from a United States residential exit as a pure HTTP client and then fully rendered, and weighed each response.

| Fetch | Exit | Bytes | Seconds | Words | h1 | Canonical |
| --- | --- | --- | --- | --- | --- | --- |
| Plain HTTP | United States | 507,949 | 4.1 | 72 | The one place you go to go places | expedia.com/ |
| Rendered | United States | 383,086 | 50.9 | 14 | none | none |
| Plain HTTP | United Kingdom | n/a | n/a | 14 | none | none |
| Rendered | United Kingdom | n/a | n/a | 14 | none | none |

The first row is the working configuration and it is complete: title, description, canonical, h1, the navigation and the promotional copy of the day, which on our fetch was a members' sale banner. Seventy-two words is thin because the home page is a search box, not because anything was withheld; the words that exist are all there, in 4.1 seconds, and the response carries a `content-language: en-US` header that tells you which storefront you got.

The second row is the one to stop paying for. Rendering the same URL took 50.9 seconds and returned a 14-word page with no h1, no canonical and no description. On Expedia the headless browser is not a slower path to the same data; it is a path to less data. Every tutorial on the SERP starts there. Do not.

There is no JSON-LD on the home page in either view, which matters for the pipeline: unlike [Kayak](https://quanticdata.io/blog/kayak-proxies/), which ships three structured blocks in the source, Expedia gives you markup and headers only. Parse the h1 and the canonical, and treat the presence of the h1 as your health check, because the 14-word responses have none.

## Pin the exit to the United States: the same URL returns 14 words from the UK

We repeated the audit from a United Kingdom residential exit, sending no Accept-Language header. Over plain HTTP the same URL returned 14 words, no canonical and no h1; rendered, the same 14 words. The United States exit received the page; the United Kingdom exit received a stub, in both modes.

This is the number that changes when you do not pin the country, and it is not a localisation story like Kayak's redirect to kayak.co.uk. It is a whole page versus almost none. `expedia.com` is the United States storefront and it serves United States visitors; the other markets have their own domains, and the robots file even disallows `/en-au/` and `/en-nz/` paths on this one. A pool that rotates through mixed countries will return a working page from some exits and a 14-word stub from others, and a retry loop keyed on status alone will not distinguish them. Key it on the h1. With `country: us` on every request, the h1 was present on every plain fetch we made.

## robots.txt fences off exactly the pages with prices

`expedia.com/robots.txt` is small, 2,210 bytes and 109 lines, with four user-agent blocks and no Sitemap line at all. The wildcard block is 52 disallow lines and reads like an inventory of where the money is: `/Hotel-Search`, `/hotel-search`, `/search?`, `/*/search?`, `/*chkin=*`, `/*chkout=*`, `/Flights-Search`, `/Flight-SearchResults`, `/carsearch`, `/things-to-do/search?`, plus every checkout and confirmation path. Any URL with check-in and check-out dates in the query string is disallowed for a generic client. The hotel and destination pages that carry no dates are not listed.

The other three blocks are short. Google's hotel-ads and ads verifiers get 6 disallow lines and an allow. SemrushBot gets `Disallow: /`. And a block naming OAI-SearchBot, ChatGPT-User, PerplexityBot, Perplexity-User, Claude-User and Claude-SearchBot gets 6 disallow lines of its own, which is Expedia deciding, by name, how far the AI search crawlers may go. We have written about that pattern in [the AI crawler user-agent list](https://quanticdata.io/blog/ai-crawler-user-agent-list/).

The terms say the rest in one list. Section 2 of the Terms of Service asks you not to access, monitor or copy any content on the service using any robot, spider, scraper or other automated means or any manual process, not to violate the restrictions in any robot exclusion headers, not to impose an unreasonable load, and not to deep link. That is the line, and it is why the rest of this post routes rates through collectors that do not touch a disallowed Expedia URL. For a licensed integration, the Expedia Group Developer Hub documents the Rapid API for lodging, a White Label Travel Platform, a Travel Redirect API and an analytics product, all for approved partners.

## Rates come from the collectors, not from the search page

Price monitoring on Expedia means dated searches, and dated searches are the disallowed URLs. So for the prices we ran two collectors on the same afternoon, both through United States exits, neither of which fetches Expedia at all.

The [hotels collector](https://quanticdata.io/collectors/google-hotels-api/), input New York, NY, check-in 20 October, check-out 22 October, two adults, currency USD, up to 20 results, returned 20 properties in 160 seconds: nightly rates from $82 to $263, two-night totals from $195 to $611, rating and review count on every row, and a link to the stay. That is the metasearch view of the same market Expedia sells into, with the same dates, and every property row costs $0.02.

The [google_flights collector](https://quanticdata.io/collectors/google-flights-api/), input JFK to LAX on 20 October, currency USD, returned 15 itineraries in 19.4 seconds: prices from $204 to $294, 14 nonstop, four airlines, with departure and arrival times, duration and a CO2 estimate per row, at $0.003 per itinerary. For fare tracking that is the whole job, and it does not depend on any one seller's markup.

## What a gigabyte buys on Expedia

Every number above came through [residential proxies](https://quanticdata.io/residential-proxies/) on the Basic line at $0.80/GB. Counting a gigabyte as 10^9 bytes:

| Request | Bytes | Requests per GB | Cost per request | Words |
| --- | --- | --- | --- | --- |
| Home page, plain HTTP, US exit | 507,949 | 1,968 | $0.00041 | 72 |
| Home page, rendered, US exit | 383,086 | 2,610 | $0.00031 | 14 |
| hotels collector, one property | billed per row | n/a | $0.02 | price, total, rating, reviews |
| google_flights, one itinerary | billed per row | n/a | $0.003 | price, times, stops, airline |

The render row is cheaper per request and worthless, which is the trap: a budget that counts bytes will prefer it. Count words. The plain fetch is $0.00041 for a whole page; the collectors are priced per delivered row and failed rows are never billed, so the 20-property New York run cost $0.40 and the 15-itinerary run cost $0.045. Mobile exits at $2.30/GB change nothing here: the difference between a page and a stub was the country, not the network. Sizing a monthly plan from bytes per request is covered in [how much proxy data you need](https://quanticdata.io/blog/how-much-proxy-data-do-i-need/), and the cadence in [how to price monitor](https://quanticdata.io/blog/how-to-price-monitor/).

## The setting that works on Expedia

**Network**: residential, Basic line at $0.80/GB. **Fetch mode**: `engine: tls`, plain HTTP, which returned 72 words with h1, canonical and description in 4.1 seconds; the browser returned 14 words in 50.9 seconds, so it is off. **Country to pin**: `country: us`, because the same URL over plain HTTP returned 72 words from a United States exit and 14 from a United Kingdom one. **When the proxy is not enough**: for every dated price, which robots.txt disallows on Expedia itself; the [hotels collector](https://quanticdata.io/collectors/google-hotels-api/) returned 20 priced New York properties in 160 seconds and the [google_flights collector](https://quanticdata.io/collectors/google-flights-api/) 15 JFK to LAX itineraries in 19.4 seconds, and for undated hotel or destination pages the [web scraping API](https://quanticdata.io/web-scraping-api/) over plain HTTP returns the page as Markdown, and every account gets $2 of free API usage per month.

Read the two lodging measurements next to this one: [Booking.com](https://quanticdata.io/blog/booking-proxies/) gives a plain client 26 words and a browser none, so it is collector-only, while [Tripadvisor](https://quanticdata.io/blog/tripadvisor-proxies/) gives a plain client 713 words and 19 LocalBusiness objects. Expedia sits with Tripadvisor on the fetch and with Booking.com on the prices.

### Sources & further reading

- [expedia.com/robots.txt (fetched 28 September 2026)](https://www.expedia.com/robots.txt)

- [Expedia Terms of Service, section 2, Using our Service](https://www.expedia.com/lp/b/terms-of-service)

- [Expedia Group Developer Hub: Rapid API, White Label, Travel Redirect API](https://developers.expediagroup.com/docs)

## FAQ

Quick answers on expedia proxies.

[Something else? Ask us →](mailto:hello@quanticdata.io)

### Do I need a headless browser to read Expedia?

No, and it hurts. On 28 September 2026 a plain HTTP client through a United States residential exit received the home page with 72 words, the h1, a canonical and a description for 507,949 bytes in 4.1 seconds. A full browser render of the same URL returned 14 words in 50.9 seconds with no h1 and no canonical. Fetch it plain.

### Which country should the proxy exit be for Expedia?

The United States, for expedia.com. Over plain HTTP the same URL returned 72 words with h1 and canonical from a United States exit and 14 words with neither from a United Kingdom exit. Pin country us on every request and use the presence of the h1 as the health check, since the 14-word responses have none.

### Does Expedia robots.txt allow scraping search results?

No. The file is 2,210 bytes with 52 disallow lines for the wildcard, and they cover /Hotel-Search, /search?, /*chkin=*, /*chkout=*, /Flights-Search, /carsearch and every checkout path: any URL with dates in it. Hotel and destination pages without dates are not listed. There is no Sitemap line, and a separate block names six AI search crawlers with 6 rules of their own.

### Is scraping Expedia against its terms?

Yes. Section 2 of the Terms of Service prohibits accessing, monitoring or copying content with any robot, spider, scraper or other automated means or any manual process, violating robot exclusion headers, imposing an unreasonable load and deep linking. The licensed route is the Expedia Group Developer Hub, which documents the Rapid API, a white label platform and a Travel Redirect API for approved partners.

### How do I track Expedia hotel prices without fetching disallowed URLs?

Run the hotels collector for the destination and dates. Our run for New York on 20 to 22 October 2026, two adults, USD, returned 20 properties in 160 seconds with nightly rates from $82 to $263, two-night totals from $195 to $611, rating and review count on every row, at $0.02 per property. Failed rows are never billed.

### What does one Expedia page cost through a residential proxy?

$0.00041 over plain HTTP on the Basic line at $0.80/GB, counting 1 GB as 10^9 bytes, so a gigabyte buys 1,968 home pages. The rendered fetch is $0.00031 and returns 14 words instead of 72, which is why a budget must count words rather than bytes, and every account gets $2 of free API usage per month.

## Count words, not bytes

One call fetches any URL twice, plain and rendered, and shows you the diff: on Expedia that is 72 words against 14. Run the audit on your own targets, then route dated prices through the hotels and flights collectors. Every account gets $2 of free API usage each month, and failed requests are never billed.

[Start free — $2/month included](https://quanticdata.io/signup/)[Explore Residential Proxies from $0.80/GB](https://quanticdata.io/residential-proxies/)

## Related reading

[Use cases Kayak Proxies: 2,451 Words With No Browser Kayak measured on 28 September 2026 through residential exits in the United States and the United Kingdom. The home page hands a plain HTTP client 2,451 words, an h1, a canonical and three JSON-LD blocks including a four-question FAQPage, for 1,656,272 bytes. A full browser render returns 2,455 words for 2,415,047 bytes and 40.7 seconds. Every tutorial on the SERP opens Selenium first; the measurement says close it. Read →](https://quanticdata.io/blog/kayak-proxies/) [Use cases Skyscanner Proxies: 0 Words, 15 Fares in 34 s Skyscanner measured on 28 September 2026 through residential exits in the United Kingdom and the United States. The home page returns a title, a description, a canonical and a WebSite JSON-LD block, and zero words of body text, to a plain HTTP client and to a full browser alike, in both countries. No fetch mode changes that. The google_flights collector, asked for London Heathrow to New York JFK on 20 October in pounds, returned 15 itineraries in 33.7 seconds. Read →](https://quanticdata.io/blog/skyscanner-proxies/) [Use cases Tripadvisor Proxies: 713 Words Over Plain HTTP Tripadvisor measured on 28 September 2026 through residential exits in the United States and Italy. The home page hands a plain HTTP client 713 words, the h1 "Where to?", a canonical and three kinds of JSON-LD, including 19 LocalBusiness objects with URLs and countries, for 388,397 bytes in 3.6 seconds. From Italy the same URL returns the same English page with 757 words. The browser spends 46 seconds and returns 5,915 bytes. The setting is plain HTTP; the tripadvisor_search collector returned 30 Chicago restaurants in 8.1 seconds. Read →](https://quanticdata.io/blog/tripadvisor-proxies/)

## Also on this site

Quantic**Data**

Residential proxies & web data APIs for AI.

#### Proxies

- [Residential Basic](https://quanticdata.io/residential-proxies/#basic)

- [Residential Premium](https://quanticdata.io/residential-proxies/#plans)

- [Cheap Residential](https://quanticdata.io/cheap-residential-proxies/)

- [Mobile Proxies](https://quanticdata.io/mobile-proxies/)

- [Datacenter Proxies](https://quanticdata.io/datacenter-proxies/)

- [ISP Proxies](https://quanticdata.io/isp-proxies/)

- [Rotating Proxies](https://quanticdata.io/rotating-proxies/)

- [Sneaker Proxies](https://quanticdata.io/sneaker-proxies/)

- [SOCKS5 Proxies](https://quanticdata.io/socks5-proxies/)

- [IPv6 Proxies](https://quanticdata.io/ipv6-proxies/)

- [Proxy locations](https://quanticdata.io/proxies/)

#### Data APIs

- [MCP Server](https://quanticdata.io/mcp-server/)

- [Web Scraper API](https://quanticdata.io/web-scraping-api/)

- [SERP API](https://quanticdata.io/serp-api/)

- [Collectors](https://quanticdata.io/collectors/)

- [Web Data for AI](https://quanticdata.io/web-data-api-for-ai/)

- [Quantic AI](https://quanticdata.io/ai-web-scraping-service/)

- [Crawl & Map](https://quanticdata.io/crawl-map/)

- [SEO Audit](https://quanticdata.io/seo-audit/)

#### Use cases

- [Company data](https://quanticdata.io/scrape-company-data/)

- [Price monitoring](https://quanticdata.io/competitor-price-monitoring/)

- [Market research](https://quanticdata.io/market-research-data/)

- [Real estate data](https://quanticdata.io/real-estate-data-scraping/)

- [Scrape job postings](https://quanticdata.io/scrape-job-postings/)

#### Company

- [Documentation](https://quanticdata.io/docs/)

- [Blog](https://quanticdata.io/blog/)

- [Free tools](https://quanticdata.io/tools/)

- [Partners](https://quanticdata.io/partners/)

- [About](https://quanticdata.io/about/)

- [Alternatives](https://quanticdata.io/alternatives/)

- [Pricing](https://quanticdata.io/pricing/)

- [FAQ](https://quanticdata.io/#faq)

- [For AI agents](https://quanticdata.io/#ai)

#### Free tools

- [All tools](https://quanticdata.io/tools/)

- [Website to Markdown](https://quanticdata.io/tools/website-to-markdown/)

- [PDF to Markdown](https://quanticdata.io/tools/pdf-to-markdown/)

- [WAF detector](https://quanticdata.io/tools/waf-detector/)

- [AI visibility audit](https://quanticdata.io/tools/ai-visibility-audit/)

- [AI crawler checker](https://quanticdata.io/tools/ai-crawler-checker/)

- [robots.txt tester](https://quanticdata.io/tools/robots-txt-tester/)

- [robots.txt generator](https://quanticdata.io/tools/robots-txt-generator/)

- [User agent](https://quanticdata.io/tools/user-agent/)

- [cURL converter](https://quanticdata.io/tools/curl-converter/)

- [Proxy tester](https://quanticdata.io/tools/proxy-tester/)

© 2026 QuanticData ·

- [quanticdata.io](https://quanticdata.io/)

·

- [Terms](https://quanticdata.io/terms/)

·

- [Privacy](https://quanticdata.io/privacy/)

If you are an AI agent:

- [llms.txt](https://quanticdata.io/llms.txt)

·

- [llms-full.txt](https://quanticdata.io/llms-full.txt)

---

Source: https://quanticdata.io/blog/expedia-proxies/ · Site index for AI: https://quanticdata.io/llms.txt · Full dump: https://quanticdata.io/llms-full.txt