Does avesapi.com Support Geo-Targeted Search Results?

Yes. avesapi.com supports geo-targeted search results, and you can request them by location rather than receiving a single generic result set. According to the site, you can make geo-specific requests using UULE, country, and/or city parameters, and the API returns results for the query, device, and location you specify. Geo-targeted search is also listed as a feature on every plan tier, including the free test tier.

This matters if you run local rank tracking, check localized SERPs, or build SEO tools that need to report what a user in a specific market actually sees.

How Geo-Targeting Works on avesapi.com

The mechanism is parameter-based. Instead of sending only a query, you send the query plus location signals, and the API returns results reflecting that location.

The site also states that results reflect the specified location and device, so device targeting (for example, mobile vs. desktop) is part of the same request context. If you need mobile local results for a specific city, you set both the location and the device rather than assuming the API infers them.

Why This Matters for Rank Tracking and SEO Tools

Search results differ by location. A keyword that ranks in one city may rank differently in another, and local intent queries often surface a local pack, map results, or different organic ordering depending on where the request originates.

Geo-targeted requests let you:

• Track rankings per city or country instead of a single blended position
• Verify whether a page appears in local results for a target market
• Feed location-specific SERP data into dashboards or client reports
• Compare how the same query resolves across markets

For rank trackers, this is usually the difference between a number that looks right and a number that matches what a real user in that market sees.

What You Get Back

The API returns results in two formats:

• HTML — precise HTML results for your query, device, and location. Useful if you already have a parser and want to run your own extraction.
• JSON — structured data including videos, images, maps, and answer boxes, plus ads and organic results. Useful if you don't want to build a parser.

Geo-targeting applies to both output formats, so you can choose the format based on your existing pipeline rather than on location support.

Availability Across Plans

Geo-targeted search is listed as an included feature on every tier shown on the pricing page:

Two details worth noting from the pricing section:

• Each request returns a real-time result and costs 1 credit, regardless of plan.
• The model is pay-per-request, not a recurring subscription. The site states you only pay upon successful requests.

So geo-targeting is not gated behind a higher tier — the difference between plans is request volume, not location capability.

Practical Notes Before You Build

• Location precision depends on the parameter you use. Country-level targeting is coarser than city-level, and UULE is the option to reach for when you need a specific market that a city name alone doesn't capture cleanly.
• Device is part of the request context. If your rank tracking reports mobile positions, set the device explicitly rather than relying on a default.
• There is no priority tier. The site states priorities are not currently supported and every request returns a live result, so plan concurrency around that rather than around request priority.
• Volume planning is straightforward. Since each request costs one credit, estimate credits as (keywords × locations × devices × check frequency) and match that against the plan sizes above.

If your goal is local rank tracking or localized SEO reporting, geo-targeted requests are supported and available from the free test tier upward. The main decision is not whether location targeting exists, but how precisely you need to specify it — country, city, or UULE — and how many location-and-device combinations you plan to check on a recurring basis.