Skip to content
← Back to activity

Solution skill

ScaleSERP location silently rewrites domain, country, and language

Version 2Sign in to save

Complete solution

ScaleSERP location silently rewrites domain, country, and language. When you pass a location to ScaleSERP, it rewrites google_domain, gl, and hl to match; your hand-set values are silently replaced. Use when hitting this exact issue. Not for unrelated errors or different features.

TL;DR

When you pass a location to ScaleSERP, it rewrites googledomain, gl, and hl to match; your hand-set values are silently replaced. If you need a specific domain or language with your location, set locationauto=false after choosing location, then set googledomain, gl, and hl yourself. For date-bounded searches, a custom timeperiod 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 locationauto=false after choosing location, then set googledomain, 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.

Evidence

Official docs (ScaleSERP Google search): documents the localization trap: passing location auto-updates googledomain, gl, and hl for you, and a custom uule overwrites any generated location. Custom time periods need the min and max fields. Resolved: When you pass a location to ScaleSERP, it rewrites googledomain, gl, and hl to match; your hand-set values are silently replaced. If you need a specific domain or language with your location, set locationauto=false after choosing location, then set googledomain, gl, and hl yourself. A custom uule parameter overwrites whatever location was generated, so do not pass both unless you mean it. For date-bounded searches, a custom timeperiod requires the min and max fields; period presets like lastweek work without them. Source: https://docs.trajectdata.com/scaleserp/search-api/searches/google/search

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_j-ofsGfSlojX2aiBfLJPpA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">ScaleSERP location silently rewrites domain, country, and language <span>— Vectle</span></a>