Geolocation & GeoIP

Geolocation controls the position a website sees when it asks “where are you?” through the browser. Santiago lets you set exact coordinates per profile, or let it auto-match the location to your proxy so the GPS position, timezone, and language all line up with the IP you’re browsing from.

What geolocation controls

When a site calls the browser’s Geolocation API (the prompt you’ve seen as “This site wants to know your location”), it gets back a latitude, longitude, and an accuracy radius. Santiago decides what that answer is, per profile, instead of leaking your real device location.

There are two ways to set it:

Mode	When to use	What you configure
Auto-match (GeoIP)	You use a proxy and want everything to line up automatically	Just turn on auto-match — coordinates, timezone, and language come from the proxy
Manual	You want a specific city/spot, or you don’t use a proxy	Latitude, longitude, and accuracy by hand

Tip

If you use a proxy, leave auto-match on. It’s the simplest way to stay consistent, and it updates itself if your proxy’s exit IP changes. See Proxies: test & GeoIP.

Auto-match to your proxy (recommended)

When GeoIP auto-match is enabled and the profile has a proxy, Santiago looks up the proxy’s exit IP and derives the location for you when the profile launches:

• Latitude / longitude — coordinates for the proxy’s region
• Timezone — set to match the IP’s region (so Date and the clock match the location)
• Language — a region-appropriate locale, unless you’ve set a language manually

You don’t enter any coordinates yourself. Each time the profile launches, the lookup runs again, so if your proxy rotates to a new exit IP, the location follows it.

How to enable it

1. Open the profile in Create / Edit (see Create & edit profiles).
2. Add a proxy under the proxy section (Configure proxies).
3. In the Geolocation section, turn on Auto-match (GeoIP).
4. Save and launch. The location is applied at launch.

Note

The location lookup happens on Santiago’s servers, not on your machine — the geo database isn’t shipped with the app. You don’t need to download or update anything.

Why auto-match prevents IP / timezone mismatches

This is the main reason to use it. A common way profiles get flagged is an inconsistency between signals: your IP says one country, but your browser’s timezone, GPS coordinates, or language say another. A real person in São Paulo doesn’t browse with a New York clock.

Auto-match removes that gap by deriving the coordinates, timezone, and language from the same proxy IP you’re actually browsing through, so all the signals agree:

• IP region, GPS coordinates, and timezone all point to the same place.
• The browser’s locale matches the region too.
• It re-runs on every launch, so it stays correct even if the proxy’s exit IP moves.

Caution

Auto-match needs a proxy. If a profile has no proxy, the GeoIP lookup is skipped entirely and the browser launches without a location override — there’s no IP to derive a location from. Either add a proxy, or set coordinates manually.

If the lookup can’t be completed (for example, a temporary network issue), the profile still launches — it just starts without the geo override for that run rather than failing.

Set coordinates manually

Use manual mode when you want a specific place, or when the profile has no proxy. In the Geolocation section, fill in:

Field	Meaning
Latitude	North–south coordinate, e.g. 40.7128 for New York
Longitude	East–west coordinate, e.g. -74.0060 for New York
Accuracy	The radius (in meters) the site sees as the margin of error

A few tips:

• Pick coordinates that match your proxy’s region if you use one, so the location and IP stay consistent.
• Accuracy is what a phone’s GPS would report as its precision. A small number (a few meters) looks like a precise mobile GPS fix; a larger number looks like a rough estimate. Keep it realistic for the kind of device your profile pretends to be.
• You can get coordinates for any place by right-clicking a point on most map apps.

Tip

Manual coordinates don’t auto-update. If you later switch the profile to a proxy in a different country, remember to update them or turn on auto-match instead.

Enable or disable the Geolocation API

Whether the browser answers location requests at all is part of the profile’s fingerprint. When geolocation is configured (auto or manual), sites that request location get the spoofed position. If you’d rather a profile never expose a location, you can leave it without geolocation so requests behave as if the feature isn’t available.

Match this to the device you’re imitating: a typical desktop browser may have geolocation available but unanswered until the user allows it, while leaving it off entirely is fine for profiles where location simply isn’t relevant.

Geolocation vs. WebRTC and timezone

Location is only one of several signals that need to agree. Two related ones:

• Timezone — handled together with geolocation. With auto-match, the timezone is set from the proxy IP automatically. With manual coordinates, make sure the profile’s timezone matches the place you chose.
• WebRTC — can leak your real IP through a separate channel even when your proxy is set. Santiago offers three WebRTC modes — real, fake, and disabled — where fake reports the proxy’s public IP instead of your real one. Keep this consistent with your proxy too. See Fingerprint parameters.

The goal is consistency

IP, geolocation, timezone, language, and WebRTC should all describe one believable person in one place. Auto-match lines up the location signals for you; just make sure WebRTC is set to match your proxy as well.

Related pages

• Configure proxies — add a proxy so auto-match has an IP to work from.
• Test proxies & GeoIP — check a proxy’s exit IP and the location it resolves to.
• Fingerprint parameters — the full list of signals, including timezone and WebRTC.
• How fingerprinting works — why consistency across signals matters.
• Create & edit profiles — where the geolocation settings live.