# Zalando Proxies: 266 Words, One False 200

> Zalando.it through residential proxies, 28 September 2026: 266 words over plain HTTP, 268 rendered at 2.8x the bytes, and one 200 that is not the catalogue.

[Home](https://quanticdata.io/)/[Blog](https://quanticdata.io/blog/)/Zalando Proxies: 266 Words, One False 200

# Zalando Proxies: 266 Words, One False 200

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

Bytes and words returned by zalando.it on 28 September 2026: 570,402 bytes of no-JavaScript HTML with 266 words, 1,607,265 bytes of rendered page with 268 words, and one collector run delivering 10 products with Omnibus reference prices in 3.6 seconds after one 200 interstitial was retried from a fresh exit

On this page [The home gives a plain client 266 words, and the browser adds two](/blog/zalando-proxies/#the-home-gives-a-plain-client-266-words-and-the-browser-adds) [A 200 from Zalando is a claim, not a page](/blog/zalando-proxies/#a-200-from-zalando-is-a-claim-not-a-page) [The collector reads the catalogue with the prices the law requires](/blog/zalando-proxies/#the-collector-reads-the-catalogue-with-the-prices-the-law-re) [What robots.txt closes, and what the country changes](/blog/zalando-proxies/#what-robots-txt-closes-and-what-the-country-changes) [Cost math with real numbers](/blog/zalando-proxies/#cost-math-with-real-numbers) [The setting that works on Zalando](/blog/zalando-proxies/#the-setting-that-works-on-zalando)

Zalando is Europe's largest online fashion retailer, and the thing to know before pointing a proxy at it is that its status codes do not tell you what you got. On 28 September 2026 zalando.it answered a plain HTTP client through an Italian residential exit with 200 OK, 570,402 bytes and 266 words; rendered, the same URL cost 1,607,265 bytes and returned 268 words. During the same hour our catalogue collector received a 200 that carried an Akamai interstitial instead of products, retried it from a fresh residential exit, and delivered 10 products with EU Omnibus reference prices in 3.6 seconds. The setting that works on Zalando is residential, plain HTTP, country matched to the domain, and a content check on every response instead of a status check.

## The home gives a plain client 266 words, and the browser adds two

Zalando's home is server-rendered by what its own header calls rendering-engine/gender-split-stackset, behind Akamai. The seo_audit tool in our [MCP server](https://quanticdata.io/mcp-server/) fetched it twice, as a pure HTTP bot and fully rendered, and the diff between the two views is two words. The no-JS page carries the title, the meta description and a self-referencing canonical; it carries no h1, no JSON-LD and no Open Graph tags, and neither does the rendered page. Zalando's home is a navigation surface, not a data surface, on both passes.

| Fetch (28 September 2026) | Status | Bytes returned | Time | Words | Notes |
| --- | --- | --- | --- | --- | --- |
| zalando.it, plain HTTP, Italian exit | 200 | 570,402 | 8.4 s | 266 | Title, description, canonical; no h1, no JSON-LD |
| zalando.it, rendered, Italian exit | 200 | 1,607,265 | 39.1 s | 268 | Same title, description and canonical; still no h1 |
| zalando.it, plain HTTP, German exit | 200 | n/a | 11.3 s (audit) | 266 | Identical Italian page; no redirect to zalando.de |
| zalando.it/robots.txt | 200 | 573 | 0.4 s | n/a | Last modified 8 September 2026 |

On 26 September the same audit counted 266 and 275; the render count moves with which teaser tiles have loaded at capture, the no-JS count does not move at all. Nothing in the diff justifies 2.8 times the bytes and 4.7 times the wall-clock. Read Zalando's HTML over plain HTTP and keep the browser for the one job where the page is actually built in the client, which on this site is not the home.

## A 200 from Zalando is a claim, not a page

The build guide that ranks for "zalando scraper" says a plain fetch of a product page returns a 200 with the fields blank, or a challenge. We saw the sharper version of that in our own collector log. On one of the requests behind the run below, Zalando answered HTTP 200 with an Akamai bot interstitial in place of the catalogue. Nothing about the status distinguished it from a real page. The collector classified the body, discarded it, retried from a fresh [residential](https://quanticdata.io/residential-proxies/) exit, and got the catalogue on the second try. The whole run, including that retry, took 3.62 seconds.

This is the practical rule for anyone reading Zalando through a proxy of any brand: never accept a response on its status code. Check for the thing you came for, a product grid, an article SKU in the URL pattern, a price, and treat its absence as a miss to retry from a different exit. A status-only pipeline will log a 100 percent success rate and deliver a folder of interstitials. Our [WAF detector](https://quanticdata.io/tools/waf-detector/) will tell you Akamai sits in front; only a content check tells you whether this response got past it.

## The collector reads the catalogue with the prices the law requires

We ran the [Zalando collector](https://quanticdata.io/collectors/zalando-scraper-api/) once on 28 September 2026 with the query "nike air max" and max_results 10. It delivered 10 rows in 3.62 seconds, one retry included. Each row carries the brand, the product name with its colourway, the article SKU read from the product URL, the packshot image, the current price in euro and two fields most scrapers skip: Zalando's EU Omnibus reference prices, the 30-day median and the 30-day low, each with its own discount percentage.

| Field in the run | What came back for 10 rows |
| --- | --- |
| Current price | 10 of 10, from 71.99 € to 159.99 €; 4 flagged price_from, meaning the card shows a "da" price for the cheapest variant |
| 30-day median reference | 8 of 10 carried one, from 89.99 € to 159.99 €, with stated discounts of 20, 25 and 30 percent |
| 30-day low reference | 1 of 10 carried one, 119.99 € against a current 111.99 €, a 7 percent discount |
| SKU | 10 of 10, config id plus colour code, for example NI112O0BT-Q12 |
| Brand | 9 Nike Sportswear, 1 Nike Performance |

The Omnibus fields are the reason to prefer a collector over a card parser on this site. The EU price-indication rules require a retailer to show the prior price when it advertises a discount, and Zalando shows it as a median or a low with its own percentage; the two are not interchangeable, and a card may state either, both or neither. The collector labels which one it read. It also notes that rank is this response's order, because Zalando re-ranks between requests, so a monitor should key on SKU, not position. At $0.001 per delivered product, the run cost one cent.

## What robots.txt closes, and what the country changes

Zalando's robots.txt is 573 bytes and was last modified on 8 September 2026. It disallows the whole site to ClaudeBot, AI2Bot, Bytespider, GPTBot, Google-Extended and Applebot-Extended. For everyone else it disallows any URL with three or more ampersands, the cart, wardrobe and account areas, /opinions, /reco-catalog/, /assistant and, with two named exceptions, everything under /api/: /api/navigation and /api/graphql/ are explicitly allowed, /api/navigation/* and /api/* are not. A crawler that stays on catalogue and product URLs with at most two filters is inside the file; one that hits the JSON endpoints behind the grid is not. The CGV page, fetched over plain HTTP at 620,167 bytes, governs purchases and returns; the automated-access rules live in robots.txt.

The country question on Zalando is answered by the domain, not the exit. Zalando runs one shop per market, 30 of them, and zalando.it fetched through a German residential exit returned the same Italian title, description and canonical and the same 266 words, with no redirect to zalando.de. The number that changes when you pick the wrong exit is, on the home, zero. Pin the exit to the market of the domain anyway, country=it for zalando.it, because prices, sizes and stock are per shop and a session that arrives from a different country than the shop it browses is the one pattern no real customer produces.

What we do not do on Zalando is the other intent in the autocomplete, "zalando order grabbing": bots that reserve limited drops. Automated checkout on a retailer is the retailer's decision, not a proxy setting, and we build nothing for it.

## Cost math with real numbers

Prices from our [pricing page](https://quanticdata.io/pricing/): residential Basic $0.80/GB, Premium $2.20/GB, the [web scraping API](https://quanticdata.io/web-scraping-api/) from $0.0002 per page ($0.001 rendered) and the Zalando collector at $0.001 per delivered product. One gigabyte is counted as 10^9 bytes.

| Approach | Bytes per page | Pages per GB | Cost per 1,000 |
| --- | --- | --- | --- |
| Plain HTTP over residential Basic ($0.80/GB) | 570,402 | about 1,753 | about $0.46 per 1,000 pages |
| Plain HTTP over residential Premium ($2.20/GB) | 570,402 | about 1,753 | about $1.25 per 1,000 pages |
| Rendered over residential Basic | 1,607,265 | about 622 | about $1.29 per 1,000 pages |
| Web scraping API, plain HTTP | n/a | n/a | $0.20 per 1,000 pages |
| zalando_search collector | n/a | n/a | $1.00 per 1,000 products, 24 per catalogue page, Omnibus prices parsed |

Byte figures are decoded HTML; wire transfer is lower and headers add a little back. The row that changes a decision is the collector: a thousand products is about 42 catalogue pages, so raw bandwidth for them is under two cents, and what the dollar buys is the retry on the false 200, the SKU, and the reference prices read correctly. For a marketplace where the raw page is cheap and stable, see [Subito through residential proxies](https://quanticdata.io/blog/subito-proxies/); for one where the render is not wasteful but shut out entirely, [Idealista](https://quanticdata.io/blog/idealista-proxies/).

## The setting that works on Zalando

- **Network**: residential, Basic at $0.80/GB. The interstitial we saw was resolved by a fresh residential exit, not by a more expensive tier; Premium at $2.20/GB is for jobs where the exit must stay fixed for a session.

- **Fetch mode**: engine: tls, plain HTTP. 266 words in 8.4 seconds; the rendered page returns 268 words for 1,607,265 bytes and 39.1 seconds. Validate every response on content, never on the status code.

- **Country**: the country of the shop, country=it for zalando.it. The exit does not change the page (266 words from Germany, no redirect); pin it so prices, sizes and stock belong to one market.

- **When the proxy is not enough**: the [zalando_search collector](https://quanticdata.io/collectors/zalando-scraper-api/), 10 products in 3.6 seconds with SKU, current price, the 30-day median and 30-day low Omnibus references and their discount percentages, $0.001 per delivered product, retries on interstitials included.

- Every account gets $2 of free API usage per month, and failed requests are never billed.

### Sources & further reading

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

- [Condizioni Generali di Vendita (CGV), Zalando.it](https://www.zalando.it/zalando-terms/)

- [Zalando, Wikipedia](https://en.wikipedia.org/wiki/Zalando)

## FAQ

Quick answers on zalando proxies.

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

### Do you need a proxy to scrape Zalando?

For the home page a residential exit and a plain HTTP client returned 200 OK, 570,402 bytes and 266 words on 28 September 2026. For the catalogue you need a pool and a content check: one of the collector requests received a 200 carrying an Akamai interstitial, and a retry from a fresh residential exit returned the products. The proxy is the retry path, not a key.

### Does Zalando need JavaScript rendering?

Not the home: our seo_audit run counted 266 words without JavaScript and 268 with it, at 1,607,265 bytes and 39.1 seconds against 570,402 bytes and 8.4 seconds. The audit found no title, description or canonical that existed only in the browser, and no h1 on either pass.

### Why does Zalando return 200 with no products?

Because Akamai can serve a bot interstitial with a 200 status. In our 28 September 2026 collector run, 1 request out of the batch came back as a 200 interstitial instead of the catalogue, was discarded, and was retried from a fresh exit; the run still finished in 3.62 seconds. Classify responses on content, not status.

### What are the Omnibus prices in Zalando data?

Zalando shows an EU Omnibus reference price next to a discount: either the 30-day median or the 30-day low, each with its own percentage. In our 10-row run, 8 products carried a median reference with discounts of 20 to 30 percent and 1 carried a 30-day low, 119.99 € against a current 111.99 €. The collector returns both fields separately.

### Which country should the proxy exit be in for Zalando?

The country of the shop you request. zalando.it fetched through a German exit returned the same Italian page with 266 words and no redirect, so the exit does not change access; pin country=it for zalando.it so prices, sizes and stock belong to one of the 30 markets Zalando runs.

### Does Zalando robots.txt allow scraping?

The 573-byte file, last modified 8 September 2026, closes the whole site to ClaudeBot, GPTBot, Bytespider, AI2Bot, Google-Extended and Applebot-Extended, and closes /api/* to everyone except /api/navigation and /api/graphql/. Catalogue and product URLs with at most two filters are open; URLs with three or more ampersands are not.

## Check the body, not the status

Every number here came from one platform: a plain fetch and a render of zalando.it, and one collector run that caught a 200 interstitial, retried it from a fresh exit and delivered ten products with Omnibus prices in 3.6 seconds. Every account gets $2 of free API usage per 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 Kleinanzeigen Proxies: 506 Words, No Geo Gate Kleinanzeigen.de measured through residential exits on 28 September 2026. The home answers a plain HTTP client with 200 OK, 288,478 bytes and 506 words from Germany, 503 from the United Kingdom; rendered, 1,305,776 bytes and 530 words. Its robots.txt closes pages 6 onward of every listing to crawlers, and the kleinanzeigen_search collector returns 10 ads with price, VB flag and ZIP in 3.5 seconds. Read →](https://quanticdata.io/blog/kleinanzeigen-proxies/) [Use cases Subito Proxies: 600 Words for 183 KB Subito.it measured through residential exits on 28 September 2026. The home answers a plain HTTP client with 200 OK, 182,983 bytes and 600 words; rendering it costs 1,263,991 bytes and returns the same 600. The subito_search collector returns 10 ads in 2.7 seconds with price, comune, seller type and shipping cost, out of the 9,268 Subito reports for the query. Read →](https://quanticdata.io/blog/subito-proxies/) [Use cases Vinted Proxies: 227 Words in 2 MB of HTML Vinted measured through residential exits on 28 September 2026. The Italian home answers a plain HTTP client with 200 OK, 1,997,674 bytes and 227 words; the rendered page takes 36 seconds and returns 204 words. The country lives in the domain, not in the exit: from Germany, vinted.it is still Italian. And robots.txt says, in its own words, what bots may not do. Read →](https://quanticdata.io/blog/vinted-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/zalando-proxies/ · Site index for AI: https://quanticdata.io/llms.txt · Full dump: https://quanticdata.io/llms-full.txt