Premip
← All solutions

Search intelligence

SERP data from the locations that matter

Check rankings, features, and snippets from the locations your audience actually searches in, then feed those observations into your SEO process.

Who this is for

SEO, content, and competitive-intelligence teams who need local search views. Premip is not an SEO rank-tracking SaaS.

Make search research represent the market

Run the same query from each dashboard location so packed features, local packs, and organic lists match that market.

What you can compare

Country and city SERPs

Results and features change with location.

Repeatable checks

Same queries, tagged locations, scheduled reruns.

Your SEO stack stays

Export captures into sheets, warehouses, or rank tools that accept fetches.

SERP-oriented setup

Regional SERPs

Set location before you load the search URL.

Repeatable checks

Sticky for a short query session; rotate between independent batches.

Tool compatibility

Any client that can use an HTTP proxy can fetch the public results page.

Search intelligence tasks

  • Local rankings

    See which URLs appear for a query in a market.

  • Feature presence

    Note ads, local packs, and other public features.

  • Competitor visibility

    Compare who appears in each region.

Mobile or residential

Search results are often localized for consumer networks. Use mobile or residential for the audience market.

Sessions

Sticky while you run a small query batch in one market. Rotate between markets or large batches.

Location

Match the country or city you rank in. Never mix markets in one unlabeled export.

Before you start

  • A frozen query set and the markets to cover.
  • A Premip plan with those locations.
  • A fetch client and a schema for ranking, URL, and features.
  • A schedule if you track change over time.

How to collect location-aware SERP data

Pilot one query in one market, lock parsing, then scale the keyword list.

  1. Step 1

    Choose the search view

    Define engine, language, device assumption, and query list. Write the exact public search URL pattern you will request.

  2. Step 2

    Provision the proxy

    Sign up and copy credentials from the dashboard.

  3. Step 3

    Set the market location

    Select the country or city before the first request. Record it in the output filename or table.

  4. Step 4

    Fetch through the proxy

    Configure http://USERNAME:PASSWORD@HOST:PORT. Use headers consistent with a normal browser if you render JS.

  5. Step 5

    Validate one SERP

    Confirm the page is a results list for that market, not a block or a home-country view. Save a golden HTML sample.

  6. Step 6

    Batch the query set

    Keep the session sticky for a short run in one market. Space requests. Tag every row with location and timestamp.

  7. Step 7

    Rotate between markets

    Finish the market, then change location or rotate IP before the next country batch.

  8. Step 8

    Hand off to SEO

    Load rankings into your reporting process. Fix parsers when layouts change, using the saved samples.

Fetch a public page through the search-market proxy
Replace USERNAME, PASSWORD, HOST, and PORT with values from your dashboard.
curl -x http://USERNAME:PASSWORD@HOST:PORT https://example.com

SERP data questions

Can I check different countries?
Yes. Set location targeting and run the same query set per supported region.
Is this an SEO platform?
No. Premip is the location-aware proxy layer for your existing SEO and search intelligence tools.
Do you return parsed rank JSON?
No. You fetch public pages or use your own parser. We provide access, not a SERP API product.
Should I mix many countries on one session?
No. Finish a market, then change location so results stay interpretable.

Capture the first local SERP

Set the market, fetch one query through the proxy, and lock your parser before you schedule the keyword list.