Geotargeting
Last updated
Geotargeting is how you tell a search engine which country or region a page is for, so it shows to the audience you intend rather than the wrong market. It is distinct from language: a page can be in English and still need to signal whether it is for the UK, the US, or Australia. Getting the signals right is what keeps your Australian store out of British results and your GBP prices away from US shoppers.
Google’s documentation is unusually direct about the mechanics here, including about which popular tactics do nothing. It names two ways to geotarget: locale-specific URLs at page or site level, and hreflang or sitemaps at page level.1 Everything else on this page is either a signal that supports those two, or a shortcut worth avoiding.
One framing to fix before anything else. Geotargeting and hreflang are often described as separate jobs, with hreflang cast as a swap mechanism that has nothing to do with country targeting. That is not how Google documents it: hreflang is listed both as a geotargeting method and as one of the signals Google uses to determine a page’s target locale.1 Country targeting and version-swapping are two things the same annotation does.
What signals does Google use for geotargeting?
Google lists four signal groups it uses to determine the target audience for a page.1
Country-code top-level domain (ccTLD). A .co.uk, .de, or .fr domain is a strong signal that a site is explicitly intended for that country, and Google treats it as such without configuration. Two trade-offs. A ccTLD binds the whole site to one country, so it suits single-market businesses rather than a brand serving many markets from one domain. And some countries restrict who may register one.
The exception catches people out constantly: Google treats around twenty vanity ccTLDs as generic, not country-targeted, because owners and users read them as generic. The list includes .ai, .co, .io, .me, .tv, .fm, .cc and .ws, and the regional domains .eu and .asia are treated the same way.1 A startup on a .io or a Colombian-registered .co has no automatic country association at all and must geotarget by the other methods.
Check the list before you buy the domain
Both halves of this decision are effectively permanent, and both are made at purchase. A genuine ccTLD binds the whole site to one country, which is a handicap the moment you want a second market. A vanity ccTLD gives you no country association at all, so a .io bought for branding cannot later be made to signal Britain. Neither is fixable afterwards without a migration, so check the domain against Google's published list before committing rather than after.
Note also that the list is not fixed. Google publishes it with the caveat that "this list may change", so a domain's status is a current fact rather than a guarantee. If a purchase decision rests on it, check Google's live documentation rather than a secondary source repeating an older version of the list.
hreflang annotations. hreflang tags map each page to its language and, optionally, its region, whether expressed in tags, HTTP headers, or sitemaps. They tell Google which pages apply to which locations, and which version to serve a given searcher. Note the limit: hreflang does not tell Google what language a page is in. Google determines language from the visible content and ignores the HTML lang attribute for that purpose.
Server location. Google says the server’s IP address “is often physically near your users and can be a signal about your site’s intended audience”, but qualifies it immediately: CDNs and offshore hosting mean “it is not a definitive signal”.1 In practice this is the weakest of the four and not worth engineering around.
Local market signals. Local addresses and phone numbers, local currency and pricing, the local language and spelling, country-relevant local citations and links, and signals from a Business Profile where one exists. This group is cheap to get right and easy to overlook.
Sitting underneath all four is URL structure. Subdirectories (example.com/de/) and subdomains (de.example.com) organise a site so the signals above attach cleanly to each market. Google explicitly does not recommend expressing country in a URL parameter, such as example.com?loc=de, because that segmentation is hard for both users and crawlers to read.1
Which geotargeting shortcuts does Google ignore?
Two tactics circulate widely and are ruled out in Google’s own documentation. Both are worth knowing before someone bills you for implementing them.
Locational meta tags do nothing. Google “ignores locational meta tags (like geo.position or distribution) or geotargeting HTML attributes”.1 There is no markup you can add to a page that sets its country.
Do not adapt content by IP address, or auto-redirect on a guess. Google flags IP analysis as a caution rather than a preference: it is “difficult and generally not reliable”, and it can stop Google crawling your variants properly, because most Google crawls originate from the US and Google does not vary the crawler’s location to find regional versions.1 A site that serves different content by IP is likely to have only its US-facing version indexed. The mechanism, the Accept-Language variant of the same mistake, and how to test for it are covered under common international SEO mistakes.
Is there still a country setting in Search Console?
No. Search Console’s International Targeting report carried a manual country-targeting control, and Google removed it in September 2022 on the basis that it “was determined to have little value for the ecosystem”.2 The same report also validated hreflang annotations, and that function was not replaced either. What the removal means in practice, and how to monitor hreflang errors without it, is covered in geotargeting in Search Console.
The consequence for this page is short: there is no switch to set, and geographic targeting rests entirely on the signals above.
What are the common geotargeting mistakes?
Confusing language with country. Targeting “English” is not targeting a country. Users in the UK, US, Canada, and Australia all search in English and need distinct regional targeting, which is what hreflang’s region codes are for.
Assuming a ccTLD is always a country signal. Covered above, and worth restating because it is the most expensive version of this mistake: a business that bought a .io or .co for branding reasons has no country targeting from its domain, however much it looks like a ccTLD.
Expecting a ccTLD to rank everywhere. The inverse problem. A .co.uk domain is a strong UK signal and a handicap in other markets. Businesses serving several countries should not scatter ccTLDs unless each market genuinely warrants a separate site.
Inconsistent signals. A /uk/ URL with US pricing, a dollar currency selector, and only US backlinks sends mixed messages. Geotargeting works when the URL, content, currency, and links all point at the same market. These and related pitfalls are covered further in common international SEO mistakes.
Treating geotargeting as exact. Google’s own caveat is that geotargeting “isn’t an exact science”, and it advises planning for users who land on the wrong version anyway.1 A region selector on every page is the practical answer.
