ScrapeLLM routes each request through infrastructure in the country you target via theDocumentation Index
Fetch the complete documentation index at: https://docs.scrapellm.com/llms.txt
Use this file to discover all available pages before exploring further.
country parameter. This page explains how to verify routing worked, how language interacts with country, and per-scraper region support.
How country routing works
Pass any ISO 3166-1 alpha-2 country code to thecountry parameter. ScrapeLLM routes your request through infrastructure in that region so the AI provider sees it as a local user.
Language behaviour
country controls geo-routing. It does not force a response language. AI providers infer language primarily from the prompt itself.
- Write the prompt in the target language for the most consistent localised response
- Mixed-language prompts (English prompt + non-English country) often work but may produce inconsistent localisation
Per-scraper region support
Most scrapers support a broad set of countries. Exceptions:| Scraper | Unsupported countries |
|---|---|
| ChatGPT | None known |
| Perplexity | None known |
| Grok | JP, TW |
| Copilot | JP, TW |
| Gemini | JP, TW |
| Google AI Mode | JP, TW |
| Amazon Rufus | Only supports: US, GB, DE, ES, FR, IT, JP, AU, IN, MX, BR |
country parameter maps directly to Amazon marketplace:
| Country code | Marketplace |
|---|---|
US | amazon.com |
GB | amazon.co.uk |
DE | amazon.de |
ES | amazon.es |
FR | amazon.fr |
IT | amazon.it |
JP | amazon.co.jp |
AU | amazon.com.au |
IN | amazon.in |
MX | amazon.com.mx |
BR | amazon.com.br |
amazon.com.
Verifying the proxy was applied
A common question is: “I targeted country X but the response references country Y — is the routing broken?” The proxy almost always applied correctly. What you’re seeing is AI model behaviour, not a routing failure:- Pre-trained bias: If a model was trained heavily on US English content, it may default to US-centric references even when served from a different region. The proxy was applied; the model just didn’t fully incorporate the regional context.
- Prompt overrides geography: A prompt like “best pizza in Cincinnati” returns Cincinnati results from any proxy — the geography parameter affects the infrastructure routing, not what the user asked for.
- Check the cited sources: The strongest signal that routing worked is
links[],sources[], orcitations[]— if these contain.de,.fr, or other country-specific domains, the proxy was applied correctly. Response language being US-centric while sources are regional is a model bias, not a routing bug.
job_id.
Common questions
Why did my US-targeted request return UK prices?
This is typically model bias from training data, not a routing failure. The AI provider processed your request from US infrastructure but generated an answer that references UK content. Check thelinks[] or sources[] field — if URLs are .com (not .co.uk), routing was correct.