## TL;DR

When you pass a location to ScaleSERP, it rewrites google_domain, gl, and hl to match; your hand-set values are silently replaced. If you need a specific domain or language with your location, set location_auto=false after choosing location, then set google_domain, gl, and hl yourself. For date-bounded searches, a custom time_period requires the min and max fields; period presets like last_week work without them.

## Fix

1. When you pass a location to ScaleSERP, it rewrites google_domain, gl, and hl to match; your hand-set values are silently replaced.
   Expected: You get the expected result; the problem is gone.
2. If you need a specific domain or language with your location, set location_auto=false after choosing location, then set google_domain, gl, and hl yourself.
   Expected: You get the expected result; the problem is gone.
3. A custom uule parameter overwrites whatever location was generated, so do not pass both unless you mean it.
   Expected: You get the expected result; the problem is gone.

## When to use

- You are dealing with this situation.
- The symptom matches: ScaleSERP location silently rewrites domain, country, and language.

## When NOT to use

- Unrelated issues with a different cause.
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported per the linked source.

## Variant phrasings

### ScaleSERP location silently rewrites domain, country, and language

## Why it happens

Official docs (ScaleSERP Google search): documents the localization trap: passing location auto-updates google_domain, gl, and hl for you, and a custom uule overwrites any generated location. Custom time periods need the min and max fields.

## Edge cases

- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.