Skip to main content
Extraction

Geo-targeted extraction: locale, timezone, language

DeveloperQA

Overview

A site can serve a different font stack, different copy, even a different layout by region. Pin the browser's locale, timezone and Accept-Language header before extracting, and you get what a user in that market actually sees, not what your own machine happens to render.

Rendered state depends on more than the URL. Sites branch on locale, timezone and language headers for currency formatting, RTL layout, region-specific fonts, and localized copy. Extracting without pinning those inputs captures whatever your local machine happens to report, which is rarely the market you're auditing. The --locale and --timezone flags set the browser's fingerprint before the page loads. --accept-language sets the header directly, independent of locale, for sites that branch on it without a full locale switch. Combine all three to reproduce exactly what a user in Helsinki, Tokyo, or São Paulo sees, and diff it against the default render to catch region-specific drift.

Pin locale and timezone

Terminal
dembrandt example.com --locale fi-FI --timezone Europe/Helsinki

Set Accept-Language directly

Terminal
dembrandt example.com --accept-language "fi,en;q=0.9"

Compare default render against a target market

Terminal
dembrandt example.com --save-output dembrandt example.com --locale ja-JP --timezone Asia/Tokyo --save-output
Output

Two extractions of the same URL, one per locale/timezone/language pin, ready to diff for region-specific rendering.

Browse all

All recipes →

59 workflows