Measure geo fidelity

Geo accuracy is essential for any operation that depends on seeing content as a user in a specific location would see it. SEO monitoring requires verifying search rankings in the exact market you are targeting. Ad verification demands confirming that advertisements display correctly in the intended geography. Localization QA must validate that language, currency, and regional content adapt properly based on the visitor's apparent location. Price comparison across markets only works when each request genuinely originates from the target region.

When a proxy provider advertises "US targeting," the critical question is how precisely that targeting maps to reality. A request targeted to New York that actually exits through an IP geolocated to Chicago will return different search rankings, different ad placements, and potentially different pricing. This benchmark quantifies that gap between intended and actual geographic placement.

What this benchmark evaluates

The Geo Accuracy Score measures three dimensions. Region accuracy captures whether the exit IP maps to the correct country or state. This is the broadest and most reliable level of geo verification, and it receives the highest weight at 50 percent. City accuracy measures whether the IP resolves to the specific city requested, which is harder to guarantee because geolocation databases are less precise at the city level. Variance captures the consistency of accuracy across repeated tests, penalizing configurations that produce accurate results sometimes but not reliably.

Together, these metrics tell you not just how accurate your geo-targeting is on average, but how much you can depend on it for production workloads that require consistent regional placement.

Methodology: how to test geo accuracy

Geo accuracy testing requires a reliable ground truth. Choose a single IP geolocation service as your reference, such as ipinfo.io, MaxMind GeoLite2, or ip-api.com, and use it consistently across all tests. Different geolocation providers use different databases and may disagree on the location of a given IP. Switching providers between tests introduces noise that makes results incomparable.

For each geographic target you want to test, create a session through the proxy gateway with the desired location parameters. Send the request to your chosen geolocation endpoint and record the returned country, region, and city. Repeat this process at least 50 times per target location, spread across different times of day, to account for pool composition changes. Record both the intended location and the actual returned location for every request.

Calculate region accuracy as the percentage of requests where the returned country and state match the intended target. Calculate city accuracy as the percentage where the returned city matches. For variance, compute the standard deviation of accuracy across multiple test batches and convert it to a 0-to-100 score where lower variance earns a higher score.

Be aware that geolocation databases themselves have error margins, particularly at the city level. An IP that ipinfo.io places in "San Jose" might actually be in a data center in nearby Santa Clara. For this reason, consider a radius-based match for city accuracy: any city within 50 kilometers of the target may be acceptable depending on your use case.

How to interpret the results

A Geo Accuracy Score above 85 indicates reliable geographic targeting suitable for production geo-sensitive operations. Your proxy configuration consistently places sessions in the intended region with minimal variance between test runs.

Scores between 70 and 85 suggest that region-level targeting works well but city-level precision may be inconsistent. This is common with residential pools where IPs are distributed across metropolitan areas rather than pinpointed to specific cities. For use cases that only require country or state-level accuracy, this range is often acceptable.

Scores below 70 indicate a significant gap between intended and actual geographic placement. Investigate whether the issue is provider-side (the proxy pool lacks sufficient IPs in the target region) or database-side (the geolocation provider has inaccurate data for the pool's IPs). Testing with a second geolocation provider can help distinguish these causes.

How Hex Proxies delivers geo accuracy

Hex Proxies maintains geo accuracy above 95 percent at the country level and above 80 percent at the city level across all major markets. Our residential IP pool is sourced from real ISP assignments with verified geolocation data. The gateway validates IP geolocation before assigning sessions, ensuring that a request targeted to Germany exits through an IP that multiple geolocation databases agree is located in Germany. For ISP proxies, our owned hardware in Virginia provides deterministic US geo placement with zero ambiguity.

Practical recommendations

Test geo accuracy before relying on location-specific data for business decisions. Run this benchmark whenever you add a new target geography to your operations. If city-level accuracy is critical for your use case, such as local SEO monitoring, test the specific cities you need rather than assuming that country-level accuracy extends uniformly to all cities within that country. Maintain a log of geo accuracy results over time, as geolocation database updates can shift how your pool's IPs are classified, causing accuracy changes that have nothing to do with the proxy infrastructure itself.