SEOProxiesScraping

City SERP Divergence: A Re-Runnable Protocol (2026)

MT
SEO Strategist
Published
August 30, 2026
Updated
September 18, 2026
Reviewed by
Read Time
9 min read
Same search query from two household exits in different US metros returning different local packs

City SERP divergence is the measurable difference in local results for the same query when the exit metro changes, holding the parser and headers constant.

That sentence is the unit this page exists to make operational. A country-US exit can return a perfectly healthy 200, a parseable organic list, and a local pack that describes a market nobody on your team sells into. The failure is silent: dashboards look green, rank history looks complete, and a franchise owner in Miami says those businesses have never been the ones that show. Country-level targeting explains the mechanism. This page is the measurement protocol — the basket you re-run, the columns you store, and the overlap formula you compute only after both metros assert clean. It is marked as a dataset so you can cite the method. It is not a substitute for a dated retrieval you actually performed.

Note

[!NOTE] How to read this page. The 16-query basket, the column schema, and the Jaccard overlap formula are the citable artifacts. They are free to reuse with attribution to Aethyn and a link back here. This article does not publish first-party overlap percentages. We did not run a live Chicago-versus-Miami (or any other pair) measurement for this ship. Search layouts, local packs, and consent walls drift. Re-run before you cite a number — the same discipline as the HTTP 200 soft-block notes.

The practical job this protocol supports is not “scrape Google.” It is sampling the SERP a household in that metro actually sees, then comparing it to another metro under identical client conditions. Pair it with SERP tracking when the product is rank history, track rankings across countries when you are building the collector, and local business data when the object of interest is the listing card itself rather than the organic URL order. Local offers — merchant, price, pickup — are a different object: use the Google Shopping how-to and why Google Shopping prices differ by city.

Why country is the wrong unit for local intent

Local search is not a national catalog with a flag on top. The map pack, the “near me” ordering, and a large share of organic local results are computed from an approximate location — device GPS when the engine has it, otherwise the network’s idea of where the request came from. Two household exits two thousand miles apart, same query string, same User-Agent, same parser, routinely return different businesses, a different pack size, and a different organic order. That is not noise. That is the product.

Country targeting is the correct lever when the page does not vary sub-nationally: documentation, a global catalog SKU, a filing, most non-local informational queries. It is the wrong lever the moment you can name a location-sensitive mechanism — the pack, a store-picker, a media-market ad, a ZIP-gated hours sheet. If you cannot name the mechanism, stay on Premium country routing and spend the bandwidth on volume. If you can, Elite city suffixes are how you pin the sample. ISP suffixes are a narrower tool (carrier-shaped pages, CDN edges); they are not required for a standard local-pack study and they shrink the pool you draw from.

The silent-failure pattern is always the same. Status 200. Selectors hit. Rows land. The vantage point was never written down, so six weeks later nobody can tell whether last Tuesday’s Miami rank was actually Miami. The protocol below makes the vantage point a first-class column, not a comment in a runbook.

Protocol (run this, then cite your numbers)

Hold these constants across both metros: query string, device class (desktop), language, User-Agent, parser version, and collection window (same UTC day unless you are studying time-of-day). Change only the Elite city suffix and the sticky session id.

  1. Pin the city. Username shape: aethyn-XXXXX-country-us-city-chicago-session-serpchi-lifetime-30. City targeting is Elite. Premium will refuse a city suffix rather than silently ignore it. Full suffix order lives in the targeting docs.
  2. Verify the exit before the first SERP. Fetch https://ipinfo.io/json (or equivalent) through the same session. Record resolved_city, resolved_region, resolved_isp, and exit_ip. If resolved_city does not match what you asked for, rotate the session id and re-check, or keep the row and label it a country fallback. Never label a fallback row as Chicago.
  3. Hold sticky for the flow. Lifetime is minutes, 1–1440, default 30. A SERP fetch plus a couple of start= pages is usually well inside 30 minutes. Sticky is a hold on a rotating-pool residential IP, not a dedicated or static SKU.
  4. Fetch with asserts. Status 200 is not success. Reject consent walls, /sorry/ interstitials, empty #rso, and deny titles before you write organic URLs. Soft 200s poison overlap math the same way they poison scraper datasets.
  5. Parse into the schema below. Organic URLs in order, local-pack business names in order, ads present or not. Do not store reviewer identities.
  6. Repeat the other metro with a new session id and a new verify step. Do not reuse the Chicago sticky id for Miami.
  7. Compute overlap only on paired, assert-ok rows. Formula in the next section. If either side failed asserts, the pair does not exist.

HTTP 5499 (Elite) or SOCKS5 3499 for a browser-backed collector; Premium 2099 / 1099 is the country-level control leg, not the city sample. Same pool, both protocols.

Pin, verify, fetch, parse, record — then compare
Asking for Chicago is not landing there. Verify the exit, then fetch. Sticky default 30 minutes.

The 16-query basket (citable)

Run every query in both metros. Keep the strings exact so someone else can reproduce the basket. Classes are labels for analysis, not a claim about how Google internally buckets them.

IDQueryClass
L01plumber near melocal_pack
L02emergency dentistlocal_pack
L0324 hour pharmacylocal_pack
L04locksmith open nowlocal_pack
L05veterinary cliniclocal_pack
L06storage unitslocal_pack
L07car washlocal_pack
L08yoga studiolocal_pack
C09italian restaurantlocal_category
C10coffee shop wifilocal_category
C11best pizzalocal_category
C12oil changelocal_category
N13gmailnational_control
N14wikipedianational_control
N15federal minimum wagenational_control
N16how to reset a routernational_control

How to use the classes. Local-pack and local-category queries are where divergence is the object of study. National controls are a sanity check: if Gmail organic overlap between Chicago and Miami collapses, you probably changed a header, hit a consent wall, or parsed a soft block — not “city SEO.” Do not report a headline divergence number that mixes L/C with N.

Recommended first pair for a US study: Chicago and Miami (Elite -city-chicago / -city-miami). They are far enough apart that local inventory is not shared, and both are large enough that city suffixes usually resolve. They are examples, not a claim we measured them on this page. Substitute the metros you actually sell into; a 50-city grid is usually 45 cities of bandwidth you will not use.

Public web only. Respect robots.txt, rate limits, and Terms. This protocol is for sampling publicly rendered SERPs, not for circumventing logins or automating engagement.

Local-pack queries diverge; national controls should not
Sixteen strings, three classes. Mix the classes in one headline percentage and the study is noise.

Column schema (store the vantage point)

Every row is one query × one metro × one retrieval. Without the vantage columns, overlap is not auditable.

ColumnTypeRule
query_idstringL01–N16 from the basket
query_textstringExact string sent
query_classenumlocal_pack / local_category / national_control
requested_citystringWhat you put in the username
requested_countrystringISO-ish, e.g. us
resolved_citystringFrom ipinfo (or equivalent), not the request
resolved_regionstringState/region if present
resolved_ispstringorg / ASN label
exit_ipstringThe address you actually used
collected_atdatetimeUTC ISO-8601
enginestringe.g. google
devicestringdesktop unless you are studying mobile SERP
sticky_session_idstringUnique per metro pass
sticky_ttl_minint1–1440, default 30
http_statusintLogged, not trusted
body_bytesintCalibrate a per-route floor yourself
assert_okboolParser saw real SERP structure, not a wall
organic_urlsstring[]Ordered, normalized (strip tracking params)
local_pack_namesstring[]Ordered business names; empty if no pack
ads_presentboolTop or side ads visible
notesstringCAPTCHA, consent, fallback, parser miss

Overlap (compute after the run, never invent). For a paired query with both assert_ok = true:

  • Organic Jaccard: |set(organic_A) ∩ set(organic_B)| / |set(organic_A) ∪ set(organic_B)|
  • Pack Jaccard: same on local_pack_names (case-fold, strip legal suffixes like LLC if you document that step)
  • Report median Jaccard per class, not a single blended number
  • Drop pairs where either side failed asserts
  • Publish collected_at next to the figure so a reader knows the retrieval date

If resolved city ≠ requested city, either exclude the pair or report it in a “fallback” slice. Mixing fallbacks into the city slice is how country-level data pretends to be metro-level data.

Record the city you resolved, not the city you requested
requested_city is an intent. resolved_city is the fact. Overlap is undefined until both sides assert_ok.

Sticky sessions, cookies, and ZIP alignment

Local results are not only “which IP.” Store pickers, ZIP cookies, and consent cookies persist on the client. If you rotate the exit mid-pagination, page 2 can be a different market than page 1 and the Jaccard is garbage. That is why the protocol uses a sticky session per metro pass, then a new session for the next metro.

Lifetime is in minutes (1–1440, default 30). Size it to the flow rather than the job: a ten-query basket with one page each is a few minutes; an hour of Maps zoom-and-scroll belongs on local business collection, not this SERP protocol. Extending TTL does not make the IP dedicated. When the window ends, the pool may hand you a different household in the same city — verify again if the job continues.

Do not pin ISP unless the hypothesis is carrier-shaped (a broadband offer page, a CDN edge). Extra constraints shrink availability. City is the lever for pack divergence; ISP is the lever for “through whom.”

Sticky holds one rotating-pool IP for the metro pass
Default 30 minutes on a rotating residential pool — not a static dedicated IP. New session id per metro.

What this page is not

It is not a ranked list of proxy vendors. It is not a Python tutorial (the SDK quickstart already covers username assembly). It is not a claim that Aethyn measured 37% pack overlap between two cities last Tuesday. If you need a number for a slide, run the basket, store the schema, and put your collected_at on the slide.

It is also not license to ignore rate limits. Residential exits look like households; they are not a reason to query like a botnet. Scale throughput by widening the city sample and pacing, not by hammering one sticky IP.

FAQ

Common questions about this article

What is city SERP divergence?
City SERP divergence is the measurable difference in local results for the same query when the exit metro changes, holding the parser and headers constant. Organic URLs, the local pack, and ads can all move. Country targeting cannot see that split.
Does this page publish Chicago versus Miami overlap percentages?
No. This page is a protocol dataset: a query basket, a column schema, and the Jaccard formula. We did not run a live two-metro measurement for this article. Re-run the protocol on the date you cite and publish your own overlap — edges and SERPs drift.
Why Elite city targeting instead of Premium country?
Premium routes by country. Local-pack queries resolve against an approximate location, not a country. Elite adds a city username suffix such as -city-chicago. Asking for a city is not the same as landing there — verify via ipinfo (or equivalent) and record the resolved city.
How long should the sticky session last?
Sticky holds a rotating-pool residential IP for 1–1440 minutes (default 30). Size it to the flow: a SERP fetch plus pagination is usually well inside 30 minutes. This is not a dedicated or static IP product.
Is this protocol free to cite?
Yes. Cite the basket, schema, and method with attribution to Aethyn (aethyn.io) and a link to this article. Do not attribute invented overlap percentages to this page. Label your own run with collected_at and resolved_city.
Share this article

Guides, integrations & docs

Continue reading

Sample the metro, not the country average

Elite city suffixes pin the exit. Sticky 1–1440 minutes (default 30) keep ZIP and store cookies aligned. Verify the city you landed in before you trust the rank.

Back to all articles