Why location changes the answer
Websites often change prices, search results, ads, availability and even content by the visitor's country, city or network. A request from a datacenter address in one place does not show what a household in another place sees. Residential proxies route your request through a real home connection in 227 countries and territories, with city and ISP targeting, so the page you collect is the page a local would get.
Every guide below explains what that job collects, why the location matters for it and how to set up the proxy line your tool dials.
The use cases at a glance
- Web data collection: collect public pages at volume, with each request from a different home connection. See web data collection.
- Price monitoring: compare prices as shoppers in different places see them. See price monitoring.
- E-commerce: check listings and storefronts by market. See e-commerce.
- Ad verification: confirm how ads appear in a given country or city. See ad verification.
- SEO monitoring: check search results from the locations you target. See SEO monitoring.
- Market research and market intelligence: study markets as local users see them. See market research and market intelligence.
- Review monitoring and social media analytics: follow public reviews and posts. See review monitoring and social media analytics.
- Brand protection, affiliate verification and cybersecurity research: check how your brand, links and exposure appear from outside. See brand protection, affiliate verification and cybersecurity research.
- Travel fare aggregation: compare fares as shown in different markets. See travel fare aggregation.
How to choose a proxy for your job
Match the session type to the work. Independent lookups such as crawling public pages suit rotating sessions that change IP on every request. Multi-step flows such as a login, a cart or a long check suit sticky sessions that hold one IP from 1 minute up to 24 hours. The rotating vs sticky comparison goes deeper.
If speed and cost matter more than blending in, datacenter proxies from $0.29/GB work on sites that accept them. For mobile-first platforms, see mobile proxies. Platform-specific pages are under proxies for.
The line your tool dials
Every use case ends in the same four parts: host, port, username and password. Targeting is added to the username. For a crawler that rotates on every request and exits in the United States:
gw.nefo.net:9000:yourlogin-country-us:your passwordHTTP, HTTPS and SOCKS5 are supported. The API docs list every targeting token, and the integration guides show the same line in Python, Node.js, Go and more.
Keep it lawful
Nefo is for lawful work: public data collection, price and ad verification, SEO monitoring and QA. The acceptable use policy lists what is not allowed, and accounts that break it can be suspended. The post on safe and acceptable proxy use cases explains the line in plain language.
Frequently asked questions
Lawful jobs where results depend on the visitor's location: collecting public web data, price and review monitoring, ad verification, SEO monitoring and market research. A home IP shows what a local visitor sees.
Rotating residential proxies are the usual choice for public pages that block server IPs, because each request can use a different home connection. Sites that accept it can also be crawled with datacenter proxies.
Yes. Target the country, state or city in the username and your request returns the page a local shopper sees. See price monitoring.
Anything illegal or abusive, such as spam, credential stuffing, payment fraud, phishing or unauthorized access. Read the acceptable use policy.
Rotating residential proxies start at $4.50 for 5 GB, and the bandwidth never expires. See pricing.