Seeing The Result Page A Market Actually Sees

Results differ by country, by city, by device and by the language of the query, and the machine you are sitting at matches none of those. Adding a country parameter or switching on a VPN gets you closer but still misses city-level variation and account personalisation, and a rank tracker configured once at setup usually reports a country nobody intended. When the local team says the page looks different, they are normally right, and the argument is unresolvable until everyone fixes the same four variables.

O ficheiro da competência

---
name: in-country-serp-verification
description: Use when a local team reports rankings or results that contradict your tracker, or before making a call about a country you cannot search from.
---

# Seeing The Result Page A Market Actually Sees

Results differ by country, by city, by device and by the language of the query, and the machine you are sitting at matches none of those. Adding a country parameter or switching on a VPN gets you closer but still misses city-level variation and account personalisation, and a rank tracker configured once at setup usually reports a country nobody intended. When the local team says the page looks different, they are normally right, and the argument is unresolvable until everyone fixes the same four variables.

## O que precisa primeiro

- The disputed queries, with the market and the query language each is claimed for
- Your rank tracker configuration per project: country, city, device, query language and interface language
- Access to someone physically in the market, or a proxy or ads preview tool that resolves to it
- A clean browser profile with no signed-in account and no search history

## Método

1. Write down the four variables before searching anything: country, language of the query, interface language and device. Two people comparing results that differ on any one of these are not looking at the same page and will argue indefinitely.
2. Search first from a clean signed-out profile so personalisation and history are excluded, then repeat signed in. The difference between the two tells you how much of the disagreement was yours rather than the market.
3. Set the country explicitly rather than relying on where you happen to be. Country-coded Google domains no longer serve a different country result by themselves, so requesting a national domain from elsewhere does not reproduce that market.
4. Check city-level variation for anything with local intent. Country granularity is not enough where a local pack appears, and a national average hides results differing between the two cities that carry the revenue.
5. Capture the whole result page rather than the organic list. Feature blocks, shopping units and generated answers vary between markets far more than the organic order does, so an unchanged position can sit much lower down the page in one country than another.
6. Compare with the local colleague on the same query at the same time on the same device type. Time of day and staged rollouts explain a large share of contradictory screenshots.
7. Once reproduced, correct the tracker configuration and label every number in the report with its country, city, language and device, so the next dispute takes minutes rather than a week.

## O que isto produz

A reproduced result page per disputed query, annotated with country, city, language and device, plus a corrected tracker configuration.

## Onde isto corre mal

- Relying on a consumer VPN and assuming the exit node decides the market, when account settings and query language still override it
- Comparing a local colleague mobile screenshot with your desktop result and reading the difference as a ranking change
- Reporting a tracker number without stating its country, city and device, leaving a market that sees something else with no way to reconcile it
- Checking only the query in your own language in a market that searches in two, so half the demand stays invisible

---

Da biblioteca de competências da QuQi - https://www.quqi.io/pt/skills/in-country-serp-verification

O que precisa primeiro

• The disputed queries, with the market and the query language each is claimed for
• Your rank tracker configuration per project: country, city, device, query language and interface language
• Access to someone physically in the market, or a proxy or ads preview tool that resolves to it
• A clean browser profile with no signed-in account and no search history

Método

1. 01 Write down the four variables before searching anything: country, language of the query, interface language and device. Two people comparing results that differ on any one of these are not looking at the same page and will argue indefinitely.
2. 02 Search first from a clean signed-out profile so personalisation and history are excluded, then repeat signed in. The difference between the two tells you how much of the disagreement was yours rather than the market.
3. 03 Set the country explicitly rather than relying on where you happen to be. Country-coded Google domains no longer serve a different country result by themselves, so requesting a national domain from elsewhere does not reproduce that market.
4. 04 Check city-level variation for anything with local intent. Country granularity is not enough where a local pack appears, and a national average hides results differing between the two cities that carry the revenue.
5. 05 Capture the whole result page rather than the organic list. Feature blocks, shopping units and generated answers vary between markets far more than the organic order does, so an unchanged position can sit much lower down the page in one country than another.
6. 06 Compare with the local colleague on the same query at the same time on the same device type. Time of day and staged rollouts explain a large share of contradictory screenshots.
7. 07 Once reproduced, correct the tracker configuration and label every number in the report with its country, city, language and device, so the next dispute takes minutes rather than a week.

O que isto produz

A reproduced result page per disputed query, annotated with country, city, language and device, plus a corrected tracker configuration.

Onde isto corre mal

• Relying on a consumer VPN and assuming the exit node decides the market, when account settings and query language still override it
• Comparing a local colleague mobile screenshot with your desktop result and reading the difference as a ranking change
• Reporting a tracker number without stating its country, city and device, leaving a market that sees something else with no way to reconcile it
• Checking only the query in your own language in a market that searches in two, so half the demand stays invisible

Use esta skill na sua própria IA

O ficheiro é markdown simples, com o nome e o gatilho no frontmatter. Quando um assistente consegue carregar skills sozinho, é esse frontmatter que lê para decidir que esta se aplica.

Mais em SEO internacional