Chrome extension for sitemap-based scraping with cloud execution support. Use KnoxProxy via SwitchyOmega for local scraping or configure it as a custom proxy in WebScraper.io Cloud for server-side runs.
For local browser scraping, install SwitchyOmega from the Chrome Web Store to manage proxy routing.
Create a new proxy profile with KnoxProxy settings.
Protocol: HTTP
Server: gw.knoxproxy.com
Port: 7000
Username: your_username-country-us
Password: your_passwordClick SwitchyOmega in the Chrome toolbar and select the KnoxProxy profile before starting your scrape.
In WebScraper.io Cloud dashboard, go to Settings > Proxy and add KnoxProxy as a custom proxy.
Proxy: http://your_username-country-us:your_password@gw.knoxproxy.com:7000Build your sitemap in the WebScraper.io panel using DevTools (F12). Start the scrape with the proxy active.
Check extracted data for completeness and correct geo-targeting. Export as CSV or push to cloud storage.
{
"sitemap": {
"startUrl": ["https://example.com/products"],
"selectors": [
{
"id": "product",
"type": "SelectorElement",
"parentSelectors": ["_root"],
"selector": ".product-card",
"multiple": true
}
]
},
"proxy": {
"url": "http://gw.knoxproxy.com:7000",
"username": "your_username-country-us",
"password": "your_password"
}
}KnoxProxy rotates IPs automatically per connection. For sitemaps with pagination, use sticky sessions (your_username-session-{id}) to maintain IP consistency across paginated requests.
| Problem | Fix |
|---|---|
| Scrape returns 403 errors | Use -country-{cc} to switch to residential IPs in the target region. Add delays between requests in sitemap settings. |
| Cloud run ignores proxy | Add the proxy URL in WebScraper.io Cloud dashboard under Settings > Proxy. SwitchyOmega only affects local runs. |
USER-country-de-city-berlin-session-profile07Order matters -- geo flags before the session flag. The session name is free text; use the profile ID so the mapping is self-documenting. Password stays as issued; no flags belong there. HTTP on :7000, SOCKS5 on :7001, same credentials.
Yes. Use SwitchyOmega to route KnoxProxy through your local browser for sitemap scraping in Chrome, and separately add KnoxProxy as a custom proxy under WebScraper.io Cloud's Settings > Proxy for server-side runs. The two configurations are independent, so cloud jobs ignore SwitchyOmega and need their own proxy entry.
Use sticky sessions by setting your KnoxProxy username to your_username-session-{id} in either the SwitchyOmega profile or the WebScraper.io Cloud proxy field. This keeps the same residential IP across every paginated request in a sitemap, which avoids the session-based blocks that random IP rotation can trigger mid-scrape.
Yes. Set a different -country-{cc} suffix in the proxy configuration for each sitemap, whether it runs locally through SwitchyOmega or as a WebScraper.io Cloud job. Each sitemap then pulls its DevTools-built selectors against the localized version of the page from that country's residential IP.
KnoxProxy itself has no connection limit and rotates IPs automatically per connection, so it will not throttle your sitemap runs. WebScraper.io may still apply its own rate limits or page-count caps depending on your subscription tier, separate from anything KnoxProxy enforces on the proxy side.
Rotating residential proxies -- 2 minutes setup, instant activation, 14-day money-back guarantee.