Geotargeting Settings: What They Are and Why They Matter
Geotargeting settings are the signals you set to tell Google which country a page or site is meant for, so the right version shows up for the right audience. Get them wrong and a searcher in Berlin lands on your Australian pricing page, bounces, and your conversion rate takes the hit while a competitor eats your lunch.
There isn't one master switch. Geotargeting is a stack of overlapping signals that each carry different weight, and Google reads them together. Knowing which signal does what stops you from wasting a week tweaking the one that barely moves the needle.
A Real Scenario: One Signal Fighting Another
Say you run example.com/uk/ and example.com/us/ off a single generic .com. You set the /uk/ subfolder to target the United Kingdom in Search Console. Good. But your entire site is hosted on a US server, your prices are in dollars sitewide, and your hreflang tags list en with no region. Now Google has one strong signal (the Search Console setting) pulling toward the UK and three weak-to-mixed signals pulling elsewhere. The result is usually the UK page ranking inconsistently for British searchers. The fix isn't more effort on the strong signal, it's cleaning up the ones that contradict it, which is exactly why you need to know each signal's strength before you touch anything.
Where Geo Signals Live and How Strong Each One Is
| Signal | Where it's set | Scope | Relative strength | Notes |
|---|---|---|---|---|
| Country-code TLD (ccTLD) | Domain registration (.de, .fr, .co.uk) | Whole site | Strongest | Hard-wired to one country; can't be overridden in Search Console. |
| Search Console international targeting | Legacy country setting (generic TLDs only) | Site, subdomain, or subfolder | Strong, but for one country only | Being deprecated in the classic UI; still a real signal for gTLDs. Does nothing on a ccTLD. |
| hreflang annotations | HTML head, HTTP header, or sitemap | Per URL / language + region | Moderate — it's a hint, not a directive | Handles many countries at once. Must be reciprocal and use valid codes or it's ignored. |
| Server / IP location | Hosting provider | Whole site | Weak — mostly overridden by a CDN anyway | Rarely worth optimizing; a global CDN muddies it regardless. |
| Local signals (currency, address, phone, language) | On-page content | Per page | Weak individually, meaningful in aggregate | Reinforces intent for users and reduces bounce even when Google already knows. |
How to Check Your Geotargeting Setup
- Identify your domain type. ccTLD or generic (
.com,.org,.net)? A ccTLD locks you to one country and ignores Search Console country settings, so stop here if that's you. - Check your Search Console international targeting for each property or folder. Confirm the country set matches the audience you actually want.
- Pull your hreflang and validate it. Run the URLs through a checker, confirm every tag is reciprocal, and confirm the language-region codes are real (
en-GB, noten-UK). - Spot-check with a search from the target region. Use a VPN or the region parameter to see which version Google actually serves for a branded and a non-branded query.
- Confirm on-page signals agree. Currency, contact details, and spelling on the UK page should read British, not American, so users and Google get the same message.
Common Mistakes and How to Fix Them
- Setting a country in Search Console on a ccTLD and expecting it to do something. It can't. The ccTLD wins. Fix: leave it and put your energy into hreflang and content.
- Using hreflang as a country switch when you mean language.
hreflang="en"targets a language globally;hreflang="en-CA"targets English speakers in Canada. Mixing these up sends the wrong page to the wrong market. Fix: decide language-only vs. language-plus-region deliberately. - Contradictory signals. Search Console says UK, content says USD, hreflang says generic
en. Fix: pick the target market per page and make every signal agree. - Geo-IP redirecting or blocking Googlebot. If you auto-redirect visitors by IP, Googlebot (crawling mostly from the US) may only ever see one version. Fix: serve a default and let users choose, never hard-redirect the crawler.
- Chasing the weak signal. Migrating hosts to a local IP for "SEO" while your hreflang is broken. Fix: hreflang and Search Console first, server location basically never.
Frequently Asked Questions
Can I geotarget a subfolder differently from the rest of my site?
Yes, on a generic TLD. Search Console lets you set international targeting at the subfolder or subdomain level, so /uk/ and /de/ can each point at their own country. On a ccTLD the whole domain is fixed to one country and folders can't split it.
Does server location still matter for geotargeting?
Barely. Google leans on your TLD, Search Console settings, and hreflang far more than IP. Most sites run through a CDN that scrambles the server-location signal anyway, so it's the last thing worth optimizing.
What's the difference between geotargeting and language targeting?
Geotargeting is about country; language targeting is about the language a searcher uses. They overlap but aren't the same — you can target one language across many countries, or one country in several languages. See Language Targeting for how the mechanisms differ.
Is the Search Console country setting going away?
The classic international targeting country setting has been getting deprecated in the interface. Even so, for generic TLDs your practical geo signals are hreflang and clear on-page cues, so build on those and don't rely on a setting that may disappear.
How long before a geotargeting change takes effect?
Google has to recrawl and reprocess the pages, so expect days to a few weeks, not hours. hreflang changes in particular need both sides recrawled before they register as reciprocal.
Related Reading
Claude Vincent is a technical SEO consultant focused on crawlability, rendering, and AI-search visibility. He writes the field guides and case studies at SEO ProCheck, with a bias toward the durable, unglamorous work that decides whether search engines and AI answer engines can actually read and cite a site.
About SEO ProCheck
Technical SEO consulting and GEO strategy with 20 years of enterprise experience. Case studies, resources, and tools for search and AI visibility.
Work With Me
Technical SEO audits, GEO strategy, site migrations, and international SEO. Hourly consulting for teams who need hands-on support, not just reports.
Subscribe to our newsletter!
