# AliExpress Proxies: 519 Words, 2 Domains

> AliExpress through residential proxies: a US exit lands on aliexpress.us, a German one on de.aliexpress.com. 519 vs 2,502 words, 20 collector items in 4.5 s.

[Home](https://quanticdata.io/)/[Blog](https://quanticdata.io/blog/)/AliExpress Proxies: 519 Words, 2 Domains

# AliExpress Proxies: 519 Words, 2 Domains

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

AliExpress fetched through residential proxies on 28 September 2026: the same aliexpress.com URL is redirected to aliexpress.us from a United States exit, returning 519 words plain and 2,502 rendered, and to de.aliexpress.com from a German exit, returning 427 words plain and 2,085 rendered

On this page [The keyword belongs to playing cards, and the data question is one word away](/blog/aliexpress-proxies/#the-keyword-belongs-to-playing-cards-and-the-data-question-i) [The exit rewrites the domain, the currency and the language](/blog/aliexpress-proxies/#the-exit-rewrites-the-domain-the-currency-and-the-language) [Plain HTTP is a fifth of the page, and it carries a trap](/blog/aliexpress-proxies/#plain-http-is-a-fifth-of-the-page-and-it-carries-a-trap) [What the render costs, and where the collector is cheaper than both](/blog/aliexpress-proxies/#what-the-render-costs-and-where-the-collector-is-cheaper-tha) [What robots.txt closes, what it opens, and the eight sitemaps](/blog/aliexpress-proxies/#what-robots-txt-closes-what-it-opens-and-the-eight-sitemaps) [The setting that works on AliExpress](/blog/aliexpress-proxies/#the-setting-that-works-on-aliexpress)

AliExpress does not localise the page for your exit; it changes the domain. On 28 September 2026 we sent the same aliexpress.com URL through residential proxies in two countries. A US exit was redirected to aliexpress.us and received 519 words over plain HTTP, 2,502 rendered. A German exit was redirected to de.aliexpress.com and received 427 words in German, 2,085 rendered. AliExpress proxies are therefore a country-per-job decision before they are anything else, and for listings the collector returned 20 items with price, original price and discount in 4.47 seconds.

## The keyword belongs to playing cards, and the data question is one word away

Google's AI Overview for "aliexpress proxies" opens by explaining that the term usually means either proxy network configurations or unofficial replica game cards sold on the marketplace, and the ten organic results are all the second thing: an r/magicproxies thread, four AliExpress wholesale pages for MTG proxy cards, a Facebook group, MTG Salvation and three YouTube hauls. Autocomplete agrees: mtg, pokemon, riftbound, yugioh. Nobody typing that phrase wants an IP.

The people who do type "aliexpress scraper api", "aliexpress scraper python", "aliexpress product scraper" and "scrape aliexpress products", and that SERP is vendor scraper pages, a GitHub topic and one technical guide. We read the guide. It says, correctly, that AliExpress relies on JavaScript rendering and dynamic class names and that the useful data sits in an embedded JSON payload. It does not fetch the page from two countries, and that is the measurement that decides how you build.

## The exit rewrites the domain, the currency and the language

We audited https://www.aliexpress.com/ from a US residential exit and from a German one, each in a single call that fetches twice, without JavaScript and in a headless browser.

| Exit | Final URL | Canonical | Plain words | Rendered words | Title language |
| --- | --- | --- | --- | --- | --- |
| United States | aliexpress.us/?gatewayAdapt=glo2usa&_randl_shipto=US | https://www.aliexpress.us/ | 519 | 2,502 | English |
| Germany | de.aliexpress.com/?gatewayAdapt=glo2deu | https://de.aliexpress.com/ | 427 | 2,085 | German |

The redirect is the whole story. The query string names it: `gatewayAdapt=glo2usa` from the United States, `glo2deu` from Germany, the global gateway adapting the request to a country site. Everything downstream follows the domain: the canonical, the title ("AliExpress - Affordable Chinese Stores & Free Shipping" against "AliExpress German - Kaufen Sie günstig qualitativ hochwertige Produkte"), the meta description, the language, and from the United States a ship-to default written into the URL. Only the Open Graph URL still says //www.aliexpress.com on both, which is a leftover, not a fact.

For a job this means one thing: a mixed pool produces a mixed dataset. Rotate through US and German exits and you will be writing dollar prices from one catalogue and euro prices from another into the same table under the same product ids, and nothing in the response status will tell you. Pin one country per job, and record `finalUrl` and the canonical on every row so the domain is in the data. We saw the same shape on [bet365](https://quanticdata.io/blog/bet365-proxies/), where the exit picks the licence, and the opposite on [Lazada](https://quanticdata.io/blog/lazada-proxies/), where the domain is fixed and the exit changes nothing.

## Plain HTTP is a fifth of the page, and it carries a trap

The plain fetch of the US home is 405,156 bytes and 519 words, and the first thing in its body is a banner: "Your browser does not support JavaScript!". The document is still useful. It has the h1, the canonical, a WebSite JSON-LD block, a description claiming over 111 million products, and a server-rendered deals module with titles and prices. The rendered page is 1,171,957 bytes, 2,502 words and arrives in 16.8 seconds; the extra 1,983 words are the product feed, the category grid and the promotional modules that hydrate from JSON.

The trap is in the prices the plain view does show. They arrive doubled with no separator, `$1.33$11.05`, `$0.33$4.04`, current price followed by struck-through original, and each is labelled "New shoppers only". A regex that takes the first currency match is right; one that takes the text node is off by an order of magnitude; and either way what you have captured is the new-shopper price, which a fresh residential exit with no cookies always qualifies for. A price monitor that wants the standing price must read the original alongside it. The same doubled-price pattern is on Facebook Marketplace, and [our Facebook measurement](https://quanticdata.io/blog/facebook-proxies/) shows the parser that survives it.

## What the render costs, and where the collector is cheaper than both

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

| Fetch | Bytes | Fetches per GB | Cost per fetch | Words |
| --- | --- | --- | --- | --- |
| Home, US exit, plain HTTP | 405,156 | 2,468 | $0.00032 | 519 |
| Home, US exit, rendered | 1,171,957 | 853 | $0.00094 | 2,502 |
| Collector aliexpress_search, 20 items | n/a | n/a | $0.02 per run ($0.001 per item) | 20 rows |

Unlike [Shopee](https://quanticdata.io/blog/shopee-proxies/), where the render returns the same words, on AliExpress it returns 4.8 times the words for 2.9 times the bytes: the render pays on category and home pages, where the feed is what you came for. On [mobile proxies](https://quanticdata.io/mobile-proxies/) at $2.30/GB the same render is $0.0027, and nothing in four audits and three fetches scored the network, so the Basic line is the right one.

For search listings neither fetch is the cheapest route. We ran the [AliExpress search collector](https://quanticdata.io/collectors/aliexpress-scraper-api/) with the query "usb c cable", country `us`, currency USD and a cap of 20. It started at 17:02:50 UTC and finished at 17:02:54, 4.47 seconds for 20 rows, each with product id, title, price, original price, discount percent, orders sold, rating, delivery window, selling points and item URL, parsed from the page's own hydration payload with no browser. Eighteen of the twenty rows carried a price; eight of them were US $0.33 with discounts of 86 to 95 percent, which is the new-shopper price the plain fetch also shows, and the collector returns the original price beside it so you can keep both. Two rows had no price and the store field was empty on all twenty, because the search grid does not expose it; the item page does.

At $0.001 per delivered item, twenty priced rows cost two cents and 4.47 seconds. The rendered home costs $0.00094 and 16.8 seconds and returns a feed you still have to parse. For listings the collector wins on both columns, and [how to price monitor](https://quanticdata.io/blog/how-to-price-monitor/) covers turning those rows into a history.

## What robots.txt closes, what it opens, and the eight sitemaps

`aliexpress.com/robots.txt` is 2,731 bytes. Googlebot gets one line. The wildcard block is long and specific:

```
User-agent: *
Disallow: /items/*
Disallow: /search/*
Allow: /wholesale.html$
Allow: /wholesale-page-*.html
Disallow: /productdetail/*
Allow: /api/data_homepage.do
Disallow: /api/*
Disallow: /wishlist/*
Disallow: /shopcart/*
Disallow: /brands/*
Disallow: /product/*
Allow: /i/api/reviews
Disallow: /i/api/*
```

Search, item, product-detail, brand, wishlist and cart paths are disallowed for an unnamed client; the wholesale listing pages, one homepage data endpoint and the reviews API path are allowed by name. Then eight `Sitemap:` lines point at item sitemaps for 2026, wholesale sitemaps split into commercial, informational, brand and transactional, and two more. We fetched the first item sitemap index: 54,161 bytes of gzipped sitemap references, with a lastmod of 15 September 2026 on the entries. AliExpress publishes a map of its items while telling a generic client to stay off the item paths, which is the same posture we found on [Facebook](https://quanticdata.io/blog/facebook-proxies/) and on [Taobao](https://quanticdata.io/blog/taobao-proxies/).

The official routes are narrow and clear. The AliExpress Open Platform at open.aliexpress.com serves developers behind credentials, and it is a JavaScript application end to end: without a browser its API reference renders as the single word "loading". The Alibaba Group introduction page describes the parent company. Accounts, buyer or seller, are governed by the AliExpress terms, and running several through proxies is not something we help with. Everything measured here was logged out and public.

## The setting that works on AliExpress

- **Network**: residential, Basic line at $0.80/GB through [residential proxies](https://quanticdata.io/residential-proxies/). Nothing in seven requests from two countries scored the IP; the cost is bytes, and for listings it is rows.

- **Fetch mode**: rendered for home and category pages, 2,502 words against 519 for 1,171,957 bytes; `engine: tls` only when the h1, canonical and JSON-LD are all you need. Read prices as current plus original, never as one number.

- **Country**: pin one per job. A US exit lands on aliexpress.us, a German exit on de.aliexpress.com, with different words, titles and currencies from the same starting URL. Record `finalUrl` on every row.

- **When the proxy is not enough**: run [aliexpress_search](https://quanticdata.io/collectors/aliexpress-scraper-api/): 20 items in 4.47 seconds on 28 September 2026 with price, original price, discount, orders and rating, at $0.001 per delivered item, no browser. For item detail beyond the grid, the [web scraping API](https://quanticdata.io/web-scraping-api/) with rendering on the item URL.

- Failed requests are never billed, and every account gets $2 of free API usage per month, which is 2,000 collector rows or about 2,100 rendered pages.

### Sources & further reading

- [aliexpress.com/robots.txt (fetched 28 September 2026, 2,731 bytes)](https://www.aliexpress.com/robots.txt)

- [AliExpress item sitemap index, 2026 P0 (lastmod 15 September 2026)](https://www.aliexpress.com/sitemap/en-https-item-item-2026-P0-sitemap-index.xml)

- [AliExpress Open Platform](https://open.aliexpress.com/)

- [Introduction to Alibaba Group](https://www.alibabagroup.com/en-US/about-alibaba)

## FAQ

Quick answers on aliexpress proxies.

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

### Which country should an AliExpress proxy use?

One country per job, chosen for the catalogue you want. On 28 September 2026 the same aliexpress.com URL sent a US exit to aliexpress.us with 519 plain words and a German exit to de.aliexpress.com with 427 words in German. The exit picks the domain, the currency and the language, so a mixed pool writes two catalogues into one table.

### Do I need to render JavaScript to scrape AliExpress?

For home and category pages, yes: the render returned 2,502 words against 519 for 2.9 times the bytes, and the extra content is the product feed. For search listings, no: the aliexpress_search collector parses the hydration payload without a browser and returned 20 rows in 4.47 seconds.

### Why do AliExpress prices appear doubled in the HTML?

Because the current price and the struck-through original are adjacent with no separator, as in $1.33$11.05, and both are labelled New shoppers only. Take the first currency match for the current price and keep the second as the original. A fresh residential exit with no cookies always sees the new-shopper price, so a monitor needs both.

### How fast is the AliExpress collector and what does it return?

Twenty items in 4.47 seconds on 28 September 2026, for the query usb c cable in the US catalogue: product id, title, price, original price, discount percent from 52 to 95, orders sold, rating from 4.5 to 4.9, delivery window and item URL. Eighteen of twenty rows carried a price; the store field is empty on the search grid.

### How much does an AliExpress page cost through residential proxies?

At $0.80/GB on the residential Basic line, counting a gigabyte as 10^9 bytes, a 405,156-byte plain home fetch is $0.00032 and a 1,171,957-byte rendered one is $0.00094. The collector costs $0.001 per delivered item, so 20 listings are two cents, and undelivered rows are never charged.

### Does AliExpress robots.txt allow scraping?

Not on item, search, product-detail, brand, wishlist or cart paths for an unnamed client; the 2,731-byte file allows the wholesale listing pages, one homepage data endpoint and the reviews API path by name, and lists eight sitemaps whose item index we fetched with a lastmod of 15 September 2026. Accounts are governed by the AliExpress terms, and we do not help automate them.

## Pin the country before you fetch AliExpress

One call fetches any AliExpress URL from the country you choose, plain and rendered, and shows you which domain it landed on and what each view returned. For listings, the collector delivers priced rows in seconds at $0.001 each. 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 Rakuten Proxies: 882 Words From Any Country Rakuten Ichiba serves a plain HTTP client 882 words, a canonical and Corporation plus WebSite JSON-LD in 381,287 bytes, and it serves exactly the same 882 words to a US exit. Rendering adds 268 words of rotating modules for 4.2 times the bytes. The catalogue itself has an official API. Here is what to fetch, from where, and what it costs. Read →](https://quanticdata.io/blog/rakuten-proxies/) [Use cases Shopee Proxies: 1,427 Words, Pin Singapore Shopee.sg answers a plain HTTP client from Singapore with 1,427 words and answers a headless browser with the same 1,427 words, for 1.74 times the bytes and 55 seconds of waiting. From an Indonesian exit the same URL returns a 163,632-byte shell with no title and no words. The whole setting is one line: residential, plain HTTP, Singapore. Read →](https://quanticdata.io/blog/shopee-proxies/) [Use cases Taobao Proxies: 36 Words at Home, 410 Deeper world.taobao.com hands a plain HTTP client 36 words and a headless browser 56, from Singapore and from the United States alike; a full render downloads 1,032,793 bytes of category menu with no listing and no price. One level down, a /lang/en-us/ page returns 410 words and four prices for 49,272 bytes without JavaScript. The home is not the page. Here is which pages are, and what they cost. Read →](https://quanticdata.io/blog/taobao-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/aliexpress-proxies/ · Site index for AI: https://quanticdata.io/llms.txt · Full dump: https://quanticdata.io/llms-full.txt