# Tripadvisor Proxies: 713 Words Over Plain HTTP

> Tripadvisor measured through residential proxies: a plain HTTP fetch returns 713 words and 19 LocalBusiness JSON-LD objects in 3.6 s, from the US and Italy.

[Home](https://quanticdata.io/)/[Blog](https://quanticdata.io/blog/)/Tripadvisor Proxies: 713 Words Over Plain HTTP

# Tripadvisor Proxies: 713 Words Over Plain HTTP

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

Tripadvisor measured on 28 September 2026 through residential proxies: 388,397 bytes and 713 words over plain HTTP from the United States with 19 LocalBusiness JSON-LD objects, 757 words from an Italian exit on the same English page, 5,915 bytes from a 46-second browser render, and 30 Chicago restaurants in 8.1 seconds from the tripadvisor_search collector

On this page [The SERP already knows the API is not the answer](/blog/tripadvisor-proxies/#the-serp-already-knows-the-api-is-not-the-answer) [713 words, 21 JSON-LD objects, no browser](/blog/tripadvisor-proxies/#713-words-21-json-ld-objects-no-browser) [The exit country does not change the page](/blog/tripadvisor-proxies/#the-exit-country-does-not-change-the-page) [robots.txt names sixteen crawlers and shuts every one out](/blog/tripadvisor-proxies/#robots-txt-names-sixteen-crawlers-and-shuts-every-one-out) [The collector returns 30 restaurants in 8.1 seconds](/blog/tripadvisor-proxies/#the-collector-returns-30-restaurants-in-8-1-seconds) [What a gigabyte buys on Tripadvisor](/blog/tripadvisor-proxies/#what-a-gigabyte-buys-on-tripadvisor) [The setting that works on Tripadvisor](/blog/tripadvisor-proxies/#the-setting-that-works-on-tripadvisor)

Tripadvisor hands a plain HTTP client more than any browser will get from it. On 28 September 2026 we fetched the home page through a United States residential exit as a pure HTTP client and received 713 words, the h1 "Where to?", a self-referencing canonical, seven h2 headings and 21 JSON-LD objects, 19 of them LocalBusiness entries with a name, a URL and a country, for 388,397 bytes in 3.6 seconds. From an Italian exit the same URL returned the same English page with 757 words and the same canonical. The rendered fetch spent 46.2 seconds and returned 5,915 bytes with nothing to parse. The setting for Tripadvisor proxies is residential, `engine: tls`, any exit country, no browser, and the [Tripadvisor collector](https://quanticdata.io/collectors/tripadvisor-scraper-api/) when you want a whole destination's listings: 30 Chicago restaurants in 8.1 seconds.

## The SERP already knows the API is not the answer

Autocomplete has nothing for "tripadvisor proxies" or "proxies for tripadvisor" and thirteen completions for "tripadvisor scraper": github, api, python, extension, free, reddit, apify, review scraper. The review phrasing adds a revealing pair, "can tripadvisor reviews be traced" and "scraping reviews from tripadvisor python". People want the reviews and they want to know what it costs them.

The first page for "tripadvisor scraper api" holds a GitHub project, a hosted actor, two vendor tutorials, two scraping-API vendors and, at position four, a thread on Tripadvisor's own support forum from 2015 titled "API access or scraping?", where the answer from another user is that without written authorisation, no, and the content is copyrighted. The best tutorial on the page is 4,670 words and technically right: it replicates the site's GraphQL search endpoint and parses the JSON hidden in script variables, and its FAQ notes that the official API returned only 3 reviews per location. What none of them do is fetch the page plain and count.

## 713 words, 21 JSON-LD objects, no browser

We audited `tripadvisor.com/` from a United States residential exit as a pure HTTP client and then fully rendered, then pulled every `script type="application/ld+json"` block out of the plain HTML with a CSS extraction.

| Fetch | Exit | Bytes | Seconds | Words | h1 | Canonical | JSON-LD |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Plain HTTP | United States | 388,397 | 3.6 | 713 | Where to? | tripadvisor.com/ | Organization, WebSite, 19 LocalBusiness |
| Rendered | United States | 5,915 | 46.2 | n/a | n/a | n/a | none |
| Plain HTTP | Italy | n/a | n/a | 757 | Where to? | tripadvisor.com/ | Organization, WebSite, LocalBusiness |

The plain response is a complete server-rendered page: title, a 214-character description, canonical, Open Graph tags, a `content-language: en` header, seven h2 sections from "Find things to do by interest" to "Tripadvisor: join the largest travel community", and 713 words of copy around them. The first JSON-LD block is an `@graph` with the Organization, seven sameAs links and a WebSite with a SearchAction pointing at `/Search?q=`. The next two blocks are arrays of LocalBusiness objects, ten and nine, one per promoted tour: a Florence storyteller tour, a Ninh Binh day trip, a Blue Cave boat tour from Dubrovnik, a London pub tour, nineteen in all, each with a name, the AttractionProductReview URL, an image and a PostalAddress whose country is filled in.

That is a structured feed of what Tripadvisor is promoting today, delivered in the source of the home page to a client that runs no JavaScript. It changes as the promotions change, which makes it a cheap daily signal for anyone tracking the experiences market, and it costs 388,397 bytes.

The rendered fetch is the other row. The browser ran for 46.2 seconds and came back with 5,915 bytes and no page to parse. On Tripadvisor the plain fetch returns 713 words and the browser returns none; that is the whole render decision, and it is the same finding the 4,670-word tutorial reached by a longer road when it chose httpx over a browser.

## The exit country does not change the page

We repeated the plain audit from an Italian residential exit with no Accept-Language header. The response was the same English page: h1 "Where to?", canonical `tripadvisor.com/`, `content-language: en`, the same three JSON-LD types, 757 words. The 44-word difference is the promoted-tour carousel, which rotates between requests, not a localisation.

This is the opposite of what [Kayak](https://quanticdata.io/blog/kayak-proxies/) and [Airbnb](https://quanticdata.io/blog/airbnb-proxies/) do, which is redirect a European exit to a country domain. Tripadvisor keeps `tripadvisor.com` as the en_US storefront regardless of where the request comes from, and serves its other markets on their own domains, which is why the sitemap lines in robots.txt are all suffixed `en_US`. For the English site, any residential exit will do and the country is a cost decision, not a correctness one. Pin the country only when you fetch a localised domain on purpose.

## robots.txt names sixteen crawlers and shuts every one out

`tripadvisor.com/robots.txt` is 24,267 bytes and 790 lines, and it begins with a recruiting note for its SEO team before listing eight Sitemap indexes. The rules are eight blocks. The first names sixteen agents in one block and gives them a bare `Disallow: /`: Amazonbot, Applebot-Extended, Bytespider, CCBot, ClaudeBot, Cohere-ai, GPTBot, Google-CloudVertexBot and the rest of the training crawlers. Google-Extended gets its own `Disallow: /` further down. The wildcard block is shared with ChatGPT-User, ChatGPT-User/2.0, Gemini-Deep-Research and OAI-SearchBot and carries 668 disallow lines and 8 allow lines, a path-by-path list of account, forum, edit and internal endpoints. PerplexityBot, bingbot and Baiduspider each get a short block of their own. The training crawlers are out entirely; the AI search crawlers get the same long list as everyone else; the review and listing pages are not on it. We have written about that split in [should I block AI crawlers](https://quanticdata.io/blog/should-i-block-ai-crawlers/).

The Terms of Use are the line that gets cited. The prohibited activities list says you may not access, monitor, reproduce or otherwise exploit any content using any robot, spider, scraper or other automated means or any manual process without express written permission, may not violate robot exclusion headers, may not deep link, and, in clause (x), may not use or enable any robot, spider, artificial intelligence system or other automated device to access, retrieve, copy, scrape, aggregate or index any portion of the services except as expressly permitted in writing. That is one sentence and we will not argue with it: reading Tripadvisor with a script is something its terms prohibit. The licensed route used to be the Content API; its reference page now carries a deprecation notice pointing to a successor platform called Terra, so a business that wants licensed reviews applies there.

## The collector returns 30 restaurants in 8.1 seconds

For destination-level public data, we ran the [tripadvisor_search collector](https://quanticdata.io/collectors/tripadvisor-scraper-api/) once on 28 September 2026 with the input Chicago, Illinois, type restaurants, exit country United States, up to 30 results. It resolved the destination to Tripadvisor's own geo id 35805, finished in 8.1 seconds and delivered 30 rows, none partial, read from the schema.org ItemList the listing page publishes for search engines.

| Field | What the 30 rows contained |
| --- | --- |
| Rating | 4.1 to 4.7 on all 30 |
| Review count | 209 to 9,907 |
| Phone | present on all 30 |
| Address and coordinates | present on all 30 |
| Price level | $ on 3, $$ - $$$ on 21, $$$$ on 6 |
| Cuisines | one or two per row, from Italian and Pizza to French and Steakhouse |
| Detail URL | the Restaurant_Review page for every row |

Two details matter for a pipeline. Three names appear twice in the 30 rows, because a chain has two locations in the city; they have different ids, different addresses and different phone numbers, so de-duplicate on id, never on name. And the collector's note says the rank reflects Tripadvisor's order in that response and is re-ranked between requests, so do not store rank as a fact. It paginates 30 per page up to 300 per run, hotels or restaurants, and the rows carry the detail URL, which is the page you fetch plain when you want the full listing.

## What a gigabyte buys on Tripadvisor

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 | 388,397 | 2,574 | $0.00031 | 713 |
| Home page, rendered | 5,915 | 169,061 | $0.0000047 | none to parse |
| tripadvisor_search, one place | billed per row | n/a | $0.001 | name, rating, reviews, phone, coordinates |

The render row is nearly free per request and worth nothing, and it costs 46 seconds each; a thousand renders is more than twelve hours of browser time for no words. A thousand plain fetches is $0.31 and about an hour. The collector is billed per delivered place and failed rows are never charged, so the 30-row Chicago run cost $0.03. Mobile exits at $2.30/GB would raise the plain row to $0.00089 for a page that returned the same 713 words to every exit we tried; keep the Basic line. 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/).

## The setting that works on Tripadvisor

**Network**: residential, Basic line at $0.80/GB; nothing in the plain fetches from two countries scored the address. **Fetch mode**: `engine: tls`, plain HTTP, which returned 713 words, the h1, the canonical and 21 JSON-LD objects in 3.6 seconds; the browser returned 5,915 bytes in 46.2 seconds with nothing to parse, so it is off. **Country to pin**: none required for tripadvisor.com, which served the same English page with the same canonical from the United States and from Italy, 713 and 757 words; pin a country only when you fetch a localised domain on purpose. **When the proxy is not enough**: for a whole destination, the [tripadvisor_search collector](https://quanticdata.io/collectors/tripadvisor-scraper-api/) returned 30 Chicago restaurants with phone, rating, review count and coordinates in 8.1 seconds at $0.001 per place, and for any single listing page the [web scraping API](https://quanticdata.io/web-scraping-api/) over plain HTTP returns it as Markdown with the JSON-LD intact, and every account gets $2 of free API usage per month, which is 2,000 places.

Of the three lodging and review sites we measured, Tripadvisor is the open one on the fetch. [Booking.com](https://quanticdata.io/blog/booking-proxies/) hands a plain client 26 words and a browser none; [Expedia](https://quanticdata.io/blog/expedia-proxies/) hands it 72 from the right country and 14 from the wrong one. Tripadvisor hands it 713 words and nineteen businesses in JSON-LD from anywhere, and its terms, not its servers, are where the limit is.

### Sources & further reading

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

- [Tripadvisor Terms, Conditions and Notices: prohibited activities](https://tripadvisor.mediaroom.com/us-terms-of-use)

- [Tripadvisor Content API reference overview (deprecation notice)](https://tripadvisor-content-api.readme.io/reference/overview)

- [API access or scraping? Tripadvisor Support Forum, 2015](https://www.tripadvisor.com/ShowTopic-g1-i12105-k8995100-API_access_or_scraping-Tripadvisor_Support.html)

## FAQ

Quick answers on tripadvisor proxies.

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

### Do I need a browser to scrape Tripadvisor?

No, and the browser gets less. On 28 September 2026 a plain HTTP client through a United States residential exit received 713 words, the h1, a canonical and 21 JSON-LD objects from the home page for 388,397 bytes in 3.6 seconds. The rendered fetch took 46.2 seconds and returned 5,915 bytes with nothing to parse. Fetch it with engine tls.

### What structured data is in Tripadvisor's plain HTML?

Three JSON-LD blocks: an @graph with the Organization and a WebSite SearchAction, then two arrays holding 19 LocalBusiness objects, one per promoted tour, each with name, AttractionProductReview URL, image and a PostalAddress with the country filled in. We extracted them with a CSS selector on script type application/ld+json over plain HTTP, no rendering.

### Does the proxy country matter for Tripadvisor?

Not for tripadvisor.com. From an Italian residential exit the same URL returned the same English page: h1 "Where to?", canonical tripadvisor.com/, content-language en, 757 words against 713 from the United States, the difference being a rotating carousel. Other markets live on their own domains, so pin a country only when you fetch a localised domain on purpose.

### Is scraping Tripadvisor against its terms?

Yes. The prohibited activities in the Terms of Use forbid accessing, monitoring or reproducing content with any robot, spider, scraper or other automated means without written permission, and clause (x) extends that to AI systems. robots.txt (24,267 bytes) fully blocks 16 named training crawlers and gives the wildcard 668 disallow lines. The legacy Content API is deprecated in favour of a successor platform for licensed partners.

### How do I get all restaurants in a city from Tripadvisor?

Run the tripadvisor_search collector with the destination and type restaurants. Our Chicago run resolved geo id 35805 and returned 30 rows in 8.1 seconds with rating 4.1 to 4.7, 209 to 9,907 reviews, phone, address, coordinates, price level and the detail URL on every row, at $0.001 per place. It paginates 30 per page up to 300 per run; de-duplicate on id, since chains appear more than once by name.

### How much does a Tripadvisor page cost through a residential proxy?

$0.00031 over plain HTTP on the Basic line at $0.80/GB, counting 1 GB as 10^9 bytes, so a gigabyte buys 2,574 home pages with their JSON-LD. The rendered fetch costs almost nothing in bytes and 46 seconds in time for no parseable page, and every account gets $2 of free API usage per month, which is 2,000 collector places or about 6,450 plain fetches.

## Fetch it plain and keep the JSON-LD

Tripadvisor returned 713 words and 19 LocalBusiness objects to a plain fetch and nothing to a 46-second render; audit any URL both ways in one call and see which one your target needs. 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 Expedia Proxies: 72 Words Without a Browser Expedia measured on 28 September 2026 through residential exits in the United States and the United Kingdom. From the United States a plain HTTP client gets the home page: 72 words, the h1 "The one place you go to go places", a canonical and a description for 507,949 bytes in 4.1 seconds. The browser gets 14 words. From the United Kingdom the plain fetch gets 14 words too. Structure over plain HTTP from a US exit; prices from the hotels and google_flights collectors. Read →](https://quanticdata.io/blog/expedia-proxies/) [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/)

## 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/tripadvisor-proxies/ · Site index for AI: https://quanticdata.io/llms.txt · Full dump: https://quanticdata.io/llms-full.txt