Geotargeting Settings

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 up the /uk/ subfolder as the locale URL for the United Kingdom. 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 clear signal (the UK locale folder) 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 that one 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

How to Check Your Geotargeting Setup

1. Identify your domain type. ccTLD or generic (.com, .org, .net)? A ccTLD locks you to one country, so stop here if that's you.
2. Check your locale URLs for each subdomain or folder. Google retired the Search Console international targeting setting in 2022, so the URL structure and hreflang now carry the country; confirm each one matches the audience you actually want.
3. 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, not en-UK).
4. 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.
5. 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

• Expecting the old Search Console country setting to do something. It can't. Google retired it in 2022, and on a ccTLD the ccTLD always won anyway. Fix: 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. The UK folder 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 locale URLs 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. Give each subfolder or subdomain its own locale URL and hreflang (Google retired the Search Console country setting in 2022), 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, hreflang, and local signals 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?

It is already gone. Google deprecated the International Targeting report and its country setting in 2022, so for generic TLDs your practical geo signals are locale-specific URLs, hreflang, and clear on-page cues. Build on those.

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

• Hreflang and International SEO: The Complete Implementation Guide
• ccTLD vs Subdirectory vs Subdomain: Choosing an International Site Structure
• Language Targeting
• Hreflang Validator