Geotargeting is how you tell Google which country a page is meant to serve, so an Indian shopper sees your India pricing and a German shopper sees your German store. It is a country signal, not a language signal — for language you use hreflang. Google no longer has a simple "target this country" button, so you signal country through your domain, your links, and your on-page content instead.
This guide walks through every signal Google actually reads, why the old Search Console setting disappeared, when a country-code domain locks you in, and how to stop your signals from fighting each other.
What geotargeting means for search engines
Geotargeting answers one narrow question: for which country is this URL intended? That is different from language targeting, which asks in which language is this URL written?
The distinction trips people up constantly. A page can be:
- Language only — Spanish content for every Spanish speaker worldwide (
es), with no country attached. - Country only — an English page aimed specifically at users in India.
- Both — Portuguese content aimed at Brazil (
pt-BR) versus Portuguese aimed at Portugal (pt-PT).
Geotargeting handles the country half. When you get it right, Google is more likely to surface your India page to a search from Mumbai and your UK page to a search from Manchester, even when the content is nearly identical. When you get it wrong, Google picks one version and shows it everywhere — often the wrong one.
If you are just mapping out your first multi-country setup, start with the broader international SEO overview and the ccTLD vs subdomain decision before you touch any targeting settings.
Signals Google uses to determine target country
Google does not rely on a single flag. It reads several signals and weighs them together. Here is how much each one actually carries:
| Signal | Strength | Notes |
|---|---|---|
| ccTLD (.in, .de, .co.uk) | Very strong | Auto-targets its country; cannot be overridden |
hreflang with region (en-IN) |
Strong | Best tool for generic domains and subfolders |
| Local backlinks & citations | Moderate | Links from in-country sites reinforce the market |
| On-page cues (currency, address, phone) | Moderate | Prices in ₹, a local address, +91 numbers |
| Server / hosting location | Weak | Minor now; matters more for speed than targeting |
| Search Console country setting | Retired | Removed in 2022 — no longer available |
The practical takeaway: on a generic domain (.com, .org, .net), your two real levers are hreflang and content signals. On a ccTLD, the domain does most of the work automatically. Everything else is supporting evidence.
Setting country targeting in Search Console
If you have read older SEO guides, you may be hunting for the International Targeting report and its country dropdown. Stop looking — Google retired the country-targeting setting in 2022. There is no longer a place to assign, say, "India" to a generic .com property.
Why did it go? Google decided the setting was redundant. hreflang, ccTLDs, and content signals already told it what it needed, and the manual override often created conflicts when site owners forgot they had set it.
So what does Search Console still do for international work?
- hreflang error reporting. Search Console flags return-tag errors and unknown language codes so you can catch broken annotations. This is the report you actually want to watch.
- Performance filtering by country. Under Performance → Search results, filter by country to see where each page earns impressions and clicks. This is your reality check on whether targeting is working.
- URL Inspection. Confirm Google has indexed the specific regional URL you expect.
The replacement workflow
Since the button is gone, targeting a country now looks like this:
- Choose your URL structure — ccTLD, subfolder (
/in/), or subdomain (in.example.com). - Add hreflang annotations mapping each regional version, including a
x-defaultfallback. See the full hreflang tags walkthrough for the exact syntax. - Align on-page signals — local currency, address, phone format, and language.
- Earn local backlinks from in-country domains.
- Monitor the Performance report by country and fix hreflang errors as they surface.
When ccTLDs auto-target and when they don't
A country-code top-level domain (ccTLD) — .in, .de, .fr, .co.uk, .com.au — is the strongest geotargeting signal you can send. Google automatically ties it to its country, and you cannot override it. Register shop.in and Google will treat it as an India site whether you like it or not.
That power cuts both ways:
- It auto-targets when your business genuinely serves one dominant market. An India-only brand on
.ingets instant local trust with zero configuration. - It locks you in when you want flexibility. If
shop.inlater expands to serve Bangladesh and Nepal, you cannot re-point the domain; Google still sees India first. You would need separate ccTLDs or a generic domain.
The generic-domain exceptions
Some TLDs look like ccTLDs but Google treats them as generic (gTLD) because they are used globally — .co, .io, .me, .tv, and .ai are common examples. These do not auto-target. If you run a .io startup, you get no automatic country signal, so hreflang and content cues become essential.
For a full comparison of when a ccTLD earns its keep versus a subfolder, read ccTLD vs subdomain. If you are juggling several markets on one domain, the SEO for multiple countries guide covers the structural trade-offs.
Server location, local backlinks and other signals
Once your domain and hreflang are set, the remaining signals are supporting evidence. They rarely decide rankings alone, but they tip close calls and reinforce a market.
Server and hosting location
Google's own documentation says server location matters less than it used to. CDNs and global cloud hosting mean a physical server address no longer reliably indicates audience. Do not obsess over it.
Where hosting does help is speed. A server or CDN edge near your users delivers faster load times, and Core Web Vitals feed into rankings. So hosting near your primary market is worth doing — for performance, not as a geotargeting trick.
Local backlinks and citations
Links from in-country domains are a genuine, moderate-strength signal. Ten links from .in news sites and directories tell Google your page belongs in India far more convincingly than any on-page tweak. Build these deliberately — our international link building guide covers earning links per market without duplicating outreach.
On-page and business signals
Small cues add up and remove ambiguity:
- Currency shown in the local unit (₹, €, £) and language.
- Physical address and a local phone format (+91, +49).
- Local business schema with the correct
addressCountry. - Language and spelling conventions matching the region (colour vs color).
If you run a currency or language switcher, make sure it does not accidentally cloak or block crawlers — see currency and language selector SEO.
Avoiding conflicting geotargeting signals
The fastest way to sabotage geotargeting is to send Google contradictory signals. When your domain says one country, your hosting says another, and your currency says a third, Google stops trusting any of them and guesses — usually wrong.
Here is a do / don't checklist that catches the common conflicts:
| Do | Don't |
|---|---|
| Assign one clear target country per URL | Mix targets on a single page (US prices + UK phone) |
| Keep hreflang and on-page currency consistent | Ship a .in page priced only in USD |
Use x-default for a generic fallback |
Leave users with no fallback version |
| Let ccTLDs target their own country | Fight a ccTLD with hreflang pointing elsewhere |
| Make return tags reciprocal | Point A→B without B→A (breaks hreflang) |
A few conflicts show up again and again:
- The mismatched .com. A generic
.comhosted in India, priced in USD, with a UK contact address. Every signal points somewhere different. Pick one country per URL and make currency, address, and hreflang agree. - ccTLD versus hreflang. Putting
hreflang="en-US"on a.inpage. The ccTLD wins and the annotation is wasted — worse, it looks like a mistake to Google. - Broken return tags. hreflang requires reciprocal links. If your India page points to the US page but the US page doesn't point back, Google may ignore the whole cluster.
Before you ship, run one sanity pass: for each URL, ask which single country is this for? Then confirm the domain, hreflang, currency, address, and links all answer the same way. If they don't, fix the outlier.
Verify what Google actually does
Setting signals is half the job; confirming Google honors them is the other half. Rankings look different from Delhi than from Berlin, so checking from your own desk tells you little.
Use a rank tracker that lets you set the search location per keyword. With DeployFlare's rank tracker you can watch a keyword in India, Germany, and the UK side by side and see exactly which page Google serves in each market. If your /in/ folder is ranking in the US, or your German page is invisible in Germany, you have found a geotargeting conflict before it costs you traffic. Pair this with the country filter in Search Console's Performance report for a full picture.
Geotargeting is not a one-time setting — it is a set of signals you keep aligned as your site grows. Get the domain and hreflang right, keep every on-page cue consistent, earn local links, and monitor by country. Do that, and Google will route the right page to the right market on its own.
For the next step, pair this with multiregional website SEO to structure content across markets and international keyword research to make sure you are targeting terms people in each country actually search.