How to Capture Region-Specific Pages from 80+ Countries

Why country matters for screenshots

The same URL can show completely different content depending on where the visitor is located. Pricing may be in local currency, cookie consent banners differ by jurisdiction, language changes, and some content is geo-restricted entirely. If you are testing or monitoring a website, you need to see what local visitors see — not what your US-based server sees.

How country routing works

Add a country parameter to your API request. The screenshot is captured from a real browser physically located in that country:

# Capture from Germany
curl "https://api.screenshotcenter.com/api/screenshot/create?url=https://example.com&country=de&key=YOUR_API_KEY"

# Capture from Japan
curl "https://api.screenshotcenter.com/api/screenshot/create?url=https://example.com&country=jp&key=YOUR_API_KEY"

ScreenshotCenter routes through 80+ countries across Americas, Europe, and APAC.

Region-level targeting

For large countries like the US, you can also pass a region parameter to target a specific state or metro area:

&country=us&region=california

This is useful for testing location-based pricing (e.g., ride-sharing fares, insurance quotes) that varies by state.

Use case: SEO audit across markets

Verify that hreflang tags, OG images, and meta descriptions render correctly for each target market. Combine country routing with data extraction trackers to pull the meta title and description alongside the screenshot:

{
  "url": "https://example.com",
  "country": "fr",
  "trackers": [
    { "name": "meta_title", "selector": "title", "type": "text" },
    { "name": "meta_desc", "selector": "meta[name=description]", "type": "attribute", "attribute": "content" },
    { "name": "lang", "selector": "html", "type": "attribute", "attribute": "lang" }
  ]
}

See SEO audit screenshots for a complete workflow.

Use case: ecommerce price monitoring

Monitor competitor pricing in every market you operate in. Capture the product page from each country, extract the displayed price, and compare trends over time. See ecommerce price monitoring for examples.

Use case: compliance verification

Verify that GDPR consent banners appear in EU countries, that age verification gates show in the right jurisdictions, and that geo-restricted content is correctly blocked. Store timestamped screenshots as compliance evidence.

Combining with locale and timezone

Country routing handles the browser's IP location. For full fidelity, also set locale (Accept-Language header) and timezone to match the target market:

&country=jp&locale=ja-JP&timezone=Asia/Tokyo

This ensures the page sees a Japanese IP, Japanese language preference, and Japanese timezone — exactly what a local visitor would experience.