Amazon needs residential traffic
Amazon challenges datacenter IPs and fast, uniform traffic with robot checks. For product pages, offers, search and reviews, residential traffic is the norm on both providers. Provider guides: Webshare for Amazon data and Geonode for Amazon scraping.
| Webshare | Geonode | |
|---|---|---|
| Residential price (list) | $3.50 to $1.40/GB, monthly plans | Under $1/GB at most volumes, no expiry |
| Marketplace countries | 195 residential countries | 150+ residential countries |
| ZIP targeting | Yes | City level |
| Sticky sessions | Session suffix | Up to 24 hours |
| Managed option | None | Scraper API with rendering |
Cost per 10,000 product pages, illustrated
Amazon product pages are large; HTML alone is often 500 KB to 1.5 MB.
| Setup | Data at 1 MB/page, 85% success | Rough cost |
|---|---|---|
| Webshare residential (10 to 25 GB tiers) | About 12 GB | About $30 to $33 |
| Geonode residential (10 to 100 GB tiers) | About 12 GB | About $9 to $11 |
| Geonode Scraper API | 11,800 requests | Depends on plan |
Bandwidth is the main cost driver, so fetch HTML without rendering where possible and block images in browsers.
Delivery location
Prices, availability and delivery dates depend on the delivery ZIP or postcode, usually stored in a session cookie. On either provider:
- Start a sticky session.
- Set the delivery location.
- Collect the products for that location within the session.
Webshare's ZIP targeting lets IP and delivery location agree exactly; Geonode's city targeting gets close, and its longer sticky sessions help when a location's product list is long.
Avoiding robot checks
- Detect robot check pages by content, not status code.
- Keep per-IP rates low and rotate between products.
- Use realistic headers and TLS fingerprints, or a real browser.
- Retry with a fresh IP, with a cap.
See CAPTCHAs and proxies.
Proxy tip: To test the Geonode side of this comparison, a small residential balance from Geonode is enough, and it doesn't expire if you pause. See Geonode for Amazon data for its full product range.
Verdict
- Bandwidth-heavy Amazon collection: Geonode, for lower per-GB cost and no expiry.
- ZIP-exact local data: Webshare.
- Small volumes without running a scraper: Geonode Scraper API.
Monthly budget by catalog size
| ASINs tracked | Frequency | Approx. GB per month | Webshare (list) | Geonode (list) |
|---|---|---|---|---|
| 1,000 | Daily | About 27 | About $65 to $75 | About $20 to $24 |
| 10,000 | Daily | About 270 | About $550 to $600 | About $175 to $195 |
| 10,000 | Weekly | About 38 | About $95 to $105 | About $30 to $34 |
Assumes about 0.8 MB of HTML per page and 90% success.
Testing both on Amazon
Run 300 product pages per marketplace through each provider and record robot check rates. Robot check rates vary with time and targeting, so repeat at different hours before deciding.
When a Scraper API makes sense
For small, irregular Amazon tasks (a few hundred ASINs occasionally), a managed API can be simpler than maintaining parsers and residential plans. For large, daily programs, raw residential proxies with good parsers are usually cheaper.
Budget tip: The cheapest way to settle this comparison is to test both: Webshare has a free datacenter plan, and Geonode offers a low-cost residential trial. Run the same targets through each. See Webshare for Amazon data.
A real-world example
A pricing tool for Amazon sellers tracks 3,000 ASINs daily in two marketplaces. A one-week test shows similar robot check rates on both providers' residential pools at their chosen rate. At about 160 GB a month, Geonode's per-GB pricing makes it the cheaper option; Webshare residential is kept as a fallback for the days when one pool sees more robot checks than usual.
Webshare and Geonode are two options among many. Our best proxies in 2026 guide explains how to match a proxy type to each task, and cheap proxies that work shows where budget providers fit. To understand the IP type behind this, read our residential proxies guide.
Key takeaways
- Amazon needs residential traffic on either provider.
- Geonode is cheaper per GB at list prices; Webshare offers ZIP targeting.
- Bandwidth is the main cost driver, so fetch HTML only.
- Set delivery location in sticky sessions for accurate prices.
- Test robot check rates on both at different times before deciding.
FAQ
Can I scrape Amazon with datacenter proxies from either provider?
You'll hit robot checks quickly. Use residential traffic.
Which provider is cheaper for Amazon?
At list prices, Geonode's residential traffic costs less per GB.
Is Amazon data collection allowed?
Check applicable laws and Amazon's terms. Sellers should prefer Amazon's official APIs for their own data.
How do I handle Amazon's different layouts?
Write parsers per page type and validate fields; store raw HTML samples for fixes.
Should I use the Scraper API for Amazon?
For small or irregular jobs, it can be simpler; for large daily programs, raw residential proxies are usually cheaper.
Can I track Buy Box ownership?
Yes, from product pages; record seller and price with timestamps.
Editorial note: Proxy providers change their pools, features and prices often, so treat any figures here as typical ranges at the time of writing and confirm current terms with the provider before you buy.