Choose Country & Language in RankTracker — 13-Country Guide

Meta Title: Choose Country & Language in RankTracker — 13-Country Guide Meta Description: Track Google rankings in the right country. Compare 13 country indexes and 6 languages in RankTracker, and learn when to pick US, UK, DE, IN, BR or others. Primary Keyword: rank tracker country language Secondary Keywords: google country index tracking, multi country seo, geo rank tracking, international rank tracker URL Slug: how-to-choose-country-and-language-in-ranktracker Featured Snippet Target: In RankTracker, click the country flag next to the project name to open the country and language picker. Choose from 13 supported countries (US, UK, CA, AU, DE, FR, ES, IT, IN, BR, MX and more) and 6 languages (EN, FR, ES, DE, IT, PT). Your choice determines which Google country index every keyword is checked against.

---

Introduction

Pick the wrong country in RankTracker and every number on your dashboard is wrong. Pick the wrong language and your keywords get checked against a SERP your client's audience never sees. This is the single highest-leverage setting in the entire tool, and it takes about ten seconds to get right — but only if you know what you are doing.

This article walks through RankTracker's country and language picker, the thirteen supported markets, the six interface languages, and the decision framework for matching them to your client's audience. It also covers the multi-market case — what to do when your client serves more than one country — and the common mistakes that cause months of misleading reports.

Where the Country Picker Lives

Open RankTracker. Look at the toolbar above the tab row. You will see the project name (Rankar), and immediately to the right of it, a country flag and a code: Google | US. That is the picker. Click it.

A dropdown appears with two sections. The top section lists the supported countries, each with its flag, ISO code, and Google domain (google.com for the US, google.co.uk for the UK, google.de for Germany, and so on). The bottom section lists the supported interface languages (EN, FR, ES, DE, IT, PT). Pick one from each section.

The change takes effect immediately. The next sync will run against the new country and language combination. Existing historical data is preserved separately for each country/language combo — so if you switch from US to UK and back, your US data is still there.

The Thirteen Supported Countries

Each country corresponds to a real Google country index. Picking US means RankTracker checks each keyword against google.com with location United States. The supported list as of this writing:

US — United States. The default for global SaaS, US-based agencies, and most B2B SEO work. UK — United Kingdom. Use this for any UK-only client. Avoid the temptation to track UK queries against US — Google UK has its own distinct SERP shape for the same query. CA — Canada. English and French Canadian markets behave differently. Combine with the EN or FR language setting based on the client's audience. AU — Australia. Mostly mirrors UK with local results, but local competitors and SERP features differ enough that the dedicated index matters. DE — Germany. Largest non-English market. Use with DE language. Critical for any DACH-region client. FR — France. Pair with FR language. French SERPs are dominated by very different domains than English ones. ES — Spain. Use ES language. Note: Spain and Latin American Spanish-speaking markets have meaningfully different SERPs — track them separately if you care about both. IT — Italy. Use with IT language. IN — India. English-dominant for B2B but a vast and competitive market. Pair with EN language unless your client targets a regional language. BR — Brazil. Pair with PT language. Brazil is one of the most underestimated markets in the suite — competition has been rising rapidly. MX — Mexico. Spanish-speaking Latin America's largest market by search volume. Pair with ES language.

The Six Supported Languages

Language is independent of country in RankTracker. You can track Google US in English, Spanish or French — that is useful for US sites targeting Hispanic or Francophone audiences. The supported languages are EN, FR, ES, DE, IT and PT.

Pairing rules:

• Google US + EN is the most common combo by far.
• Google US + ES for US Hispanic audiences.
• Google CA + FR for Quebec-targeting clients.
• Google IN + EN for B2B SaaS targeting India.
• Google BR + PT is the only sensible combo for Brazil.

Mismatched combos (Google DE + EN, for example) technically work but rarely make sense — Google DE assumes German as the user's preference, and forcing English changes the SERP composition.

Why This Setting Matters So Much

Google personalises SERPs by country, language, and device. The same query returns different result sets in different country indexes, sometimes radically so. Consider seo tools:

• In Google US + EN, the top ten is dominated by Semrush, Ahrefs, Moz, and a few US-based content sites.
• In Google UK + EN, you will see Brafton, Mangools, and other UK-leaning brands push higher up the page.
• In Google IN + EN, Indian SEO blogs and price-conscious tools rank above the US giants.
• In Google DE + DE, the entire SERP changes — you get German keyword research tools, German-language guides, and a different competitor set entirely.

If your client serves the German market and you track against US, you will report rankings that do not exist for their actual users. You will optimise pages for the wrong SERP shape. You will misread the competitive landscape. And the client will eventually figure out that your dashboard numbers do not match what they see when they Google themselves from Munich.

Picking the Right Setting

The decision framework is straightforward:

Single-market client. Use the market they actually serve. UK e-commerce → Google UK + EN. German SaaS → Google DE + DE. Mexican publisher → Google MX + ES. Do not overthink it. Multi-market client, one primary market. Pick the primary. Track the secondary markets in separate projects, each with their own country/language combo. Multi-market client, equal weight on each market. Create one RankTracker project per market. They will share the same domain but track different SERPs. Use Project Management to create the parallel projects, give them names like ClientName — US, ClientName — UK, ClientName — DE, and switch between them via the project switcher. Bilingual market. Canada in particular. Most agencies handle Canada by creating two projects: Client — CA (EN) and Client — CA (FR). Track the English keywords in the first, French in the second. The reporting in RankReport will pull from whichever project you select at report time.

When to Use RankLocal Instead

RankTracker's country picker is for national SERPs. If your client is location-specific — a dentist with three offices, a SaaS targeting cities in California — RankLocal (the dedicated local SEO module in Rankar.ai) gives you city- and ZIP-level tracking with a totally different data model. Use RankLocal for that and keep RankTracker for the national-SERP work.

A simple rule: if the keyword would behave differently from Manchester vs Birmingham searcher locations, you need RankLocal. If the keyword behaves the same from any UK city but differently in the US, you need RankTracker + the right country setting.

The Multi-Country Cost Tradeoff

Each tracked country costs SERP API calls. If you have a 200-keyword project and want to track it across US, UK, CA and AU, that is four separate syncs per cadence — 800 SERP calls per day on the default daily cadence. Most agency plans handle that fine, but it does eat into your tracking quota.

If your quota is tight, two options:

Reduce cadence on the secondary markets. Daily on primary, weekly on the rest. Often good enough. Reduce keyword count on the secondary markets. Track only the top 30 keywords in UK/CA/AU and the full 200 in US. Often the right tradeoff.

Both are easy to set per-project. Make the call based on how much each market matters to the client's revenue.

Common Mistakes That Cost Months

Tracking the wrong country because the agency is US-based. A US agency working with a UK client may default to Google US out of habit. Always confirm with the client where their audience is. Tracking English in a non-English market. A SaaS targeting Germany sometimes assumes the German market searches in English because the product is in English. They do not. They search in German, and your tracker needs to match. Mixing markets in one project. Tempting because it feels like fewer projects to manage, but it produces incomprehensible reports. Always separate. Forgetting to re-check after a project relaunch. Country and language settings persist across keyword changes, so if you redesigned a client's site to expand from US to global, the project may still be tracking against US only. Audit your country setting any time the client's market changes.

After You Pick: One More Sanity Check

Save the country/language change, then trigger a manual Sync. When the sync finishes, open a single keyword's detail view and look at the SERP snapshot. If the result domains, the SERP language, and the SERP features match what you would see from a typical user in that country, you are set. If they look wrong, double-check the country flag in the toolbar — it is easy to accidentally pick Google UK when you wanted Google US because the flags are next to each other in the dropdown.

What's Next

Country, language, and project are now correctly configured. In the next article we cover daily vs weekly tracking cadence — because once your SERP settings are right, the next decision is how often to recheck them, and that decision has more downstream effects than people realise.

Apply This With the Rankar Toolkit

RankTracker works best when paired with the rest of the Rankar suite. Spin up the relevant tools directly: RankTalk • RankOps • RankAudit • RankWriter • RankTracker • RankAIO • RankBridge • RankLinks • RankLocal • RankLaunch • RankSpy • RankUX • RankLead. Each tool pushes data into RankTracker automatically — RankWriter publishes new pages that get tracked, RankLinks contributes backlink ROI data, and RankOps turns declining keywords into actionable tasks.