# Local-check glossary

> Local-check glossary: 24 terms covering city IPs, ZIP areas, Maps, sessions and billing. Learn no KYC and crypto terminology for US tests.

- URL: https://localserpproxy.com/glossary/
- Last updated: 2026-10-15
- Publisher: LocalSERP Proxy (https://localserpproxy.com)

## Which terms matter for a local proxy test?

**Quick answer**

As of 15 October 2026, this **LocalSERP Proxy** glossary defines 24 terms used in manual local checks. Residential traffic starts from $0.53/GB, with no KYC and crypto payment. Distinguish a city-selected exit, an observation point and a shipping destination before interpreting what a search page or application shows.

## Locations and test scope

**Local check** — A deliberately scoped observation of a page from a selected market. Record the question first: a result order, a delivery message and a landing-page variation are different measurements. Include the place, time, browser context and what actually appeared.

**Exit IP** — The address the destination sees for a proxied connection. Its city label depends on the database consulted. The requested city, an independent IP lookup and the destination’s displayed location can disagree.

**City targeting** — Requesting an exit associated with a named city. Country and city targeting on every plan; in the United States also state and ZIP code; ASN targeting at no extra cost. City availability varies. Check the actual exit before recording evidence. This does not define an exact business address or a Google Maps measurement pin.

**State targeting** — A broader US location choice for a statewide question. It suits a test where the state is the unit being compared. Do not interpret a state-only request as a verified observation from a particular city.

**ZIP targeting** — A postal-area request for an eligible US exit. A five-digit ZIP is not a coordinate. A retailer’s entered shipping destination can determine delivery independently of the exit IP.

**ASN** — Autonomous System Number: a routing-network identifier. It helps describe the network announcing an address range. It does not establish stock, the household’s exact location or permission to collect a target’s pages.

**IP geolocation** — A database estimate associating an IP address with a place. Retain the database name and lookup time. Do not substitute an IP estimate for browser coordinates or an exact measurement point.

**Observation point** — The place and context defined by a test. A coordinate grid needs coordinates and a clear rule for each observation. A city-selected proxy supplies a network exit, rather than a certified street-level position.

## Search, ads and browser context

**SERP** — Search engine results page. Organic links, map-associated results and paid placements can appear together. Separate them in a report and preserve the query rather than calling the whole page one local ranking.

**Local pack** — A map-associated group of business results in Search. Its composition can differ from a full Maps view or an ordinary organic ranking. Label the observed surface so later comparisons use the same method.

**Browser profile** — A context with separate saved settings and site data. Record its signed-in state and earlier cookies. A clean profile limits one source of variation without proving all other localisation signals are identical.

**Location permission** — Permission for a website to use browser-provided device location. It is separate from the proxy exit. Record whether permission was granted, denied or unavailable when comparing a map or an application flow.

**Ad preview** — A platform tool for inspecting your own campaign. Google recommends Ad Preview and Diagnosis to avoid accumulating impressions. Inspect the final destination directly when testing your own landing page.

**Landing URL** — The final destination configured for an advertisement. Open that page directly for localisation QA. An ad server’s click link can count an interaction and should not be used as a connection test.

**Shipping destination** — The address or postal code entered for delivery. It can control stock and fulfilment messages separately from IP location. Retain both inputs when inspecting your own store or a public page you may access.

## Connections and sessions

**Sticky session** — Temporary access intended to keep an exit stable during one task. Sticky sessions keep the same IP for the time you set (ttl, in minutes), up to 30 minutes. The IP can change earlier, for example if the residential device goes offline. Record an interruption if the exit changes while checking a multi-step application flow.

**Rotation** — Allocation of an exit when a connection changes. Rotating mode: each new connection gets an IP from the pool, usually a different one. To get a new IP on every request, send one request per connection (turn off keep-alive). Sticky mode keeps one IP for the session time you set. Several HTTPS requests can share a tunnel, so a request count and connection count are different things.

**HTTP CONNECT** — The tunnel method used to carry HTTPS through an HTTP proxy. A successful tunnel response confirms that stage of a connection. It does not mean the destination accepted the later page request.

**SOCKS5** — A proxy protocol available in compatible clients. Remote hostname handling sends the name to the proxy rather than resolving it locally. This identifies who resolves it, not the resolver’s physical location.

**Proxy authentication** — The credentials or allowed connecting IP used for gateway access. Username and password on every plan, or an IP allowlist (up to 10 IPs). Sub-users with their own credentials and traffic cap. API keys you can revoke at any time. These credentials are separate from the account number and should be redacted in screenshots and support samples.

## Traffic, balance and evidence

**Gigabyte** — The per-GB traffic unit. Usage counts all data sent and received through the proxy (upload and download, headers included). 1 GB = 1,000,000,000 bytes. Connection attempts that fail before reaching the target are not counted. An allowance is transferred data rather than a promised number of screenshots, result pages or completed tasks.

**Prepaid balance** — Account value funded with a crypto top-up and spent on plans. The minimum top-up and a plan’s price are different amounts. Unused balance stays on your account and never expires, but it is not paid back, except where the law requires it.

**Balance credit** — Value returned to an account under the refund policy. This differs from cryptocurrency sent to a wallet. Product windows and usage thresholds apply, with mandatory legal rights preserved.

**Evidence log** — Your record of what appeared and under which conditions. Keep the query, requested place, exit lookup, target location label, device and screenshot. Exclude secrets and unrelated personal information.

## Use the same vocabulary in your report

A report should name the selected scope and observed outcome separately. Write “requested Chicago; lookup returned Chicago; destination indicated a broader region” when that is what happened. Preserve a disagreement rather than replacing it with a stronger city claim. The [city-check hub](https://localserpproxy.com/check-from/), [workflow](https://localserpproxy.com/how-it-works/) and [price grid](https://localserpproxy.com/pricing/) help a colleague reconstruct the context.

## Sources

1. [How Google determines local results](https://support.google.com/business/answer/7091?hl=en) — Google Business Profile (2026-10-15)
2. [Ad Preview and Diagnosis](https://support.google.com/google-ads/answer/148778?hl=en) — Google Ads (2026-10-15)

---

LocalSERP Proxy: LocalSERP Proxy is a US residential proxy service for checking local search results, ads and prices city by city, paid in crypto with no ID upload.
