Configuring Geotargeting Correctly in Search Console

1. What geotargeting means and why it matters

Geotargeting refers to the process of associating a website or individual URLs with a target country so that Google shows the result preferentially to users in that specific country. For internationally oriented Magento stores with multiple store views, this is not a side issue, it's a core requirement for making sure a German user sees the German product page and a French user sees the French variant, without both pages competing against each other for the same search results. Without working geotargeting, Google can show the wrong language version in a country, or multiple country variants can end up cannibalizing each other.

Important for framing this correctly: geotargeting is not a single switch, but the result of several signals working together that Google evaluates to associate a URL with a country. These include the choice of domain structure, hreflang markup, server location, the language and currency of the visible content, and to a lesser degree the origin of backlinks and user behavior. Anyone who equates "configuring geotargeting" with a single setting in Google Search Console is working from an outdated model that no longer reflects the actual complexity involved.

2. The former International Targeting setting: what still applies today

Until May 2022, Google Search Console offered an International Targeting report under "Legacy tools and reports," with a Country tab. There, property owners could manually assign a target country to domains, subdomains, or directories, provided the property sat on a generic top-level domain. This setting acted as an additional, but comparatively weak signal, and never overrode stronger signals like ccTLDs or a clear hreflang structure.

Google removed the setting, stating it was rarely used in practice and offered little value relative to its complexity. At the same time, the hreflang error report in the same tool was also discontinued. Anyone who still reads about a country dropdown in Search Console today is referring to a feature that has not existed since 2022. In practice, this means "configuring geotargeting in Search Console" today is about correctly setting the relevant signals outside of a single switch, not ticking a checkbox.

3. gTLD vs. ccTLD: when geographic signals apply automatically

The distinction between generic top-level domains (gTLDs) like .com or .shop and country-code top-level domains (ccTLDs) like .de, .fr, or .ch remains the most important type of geographic signal Google evaluates, regardless of whether the old Search Console setting still exists. Google automatically associates a ccTLD with its corresponding country, a strong, implicit signal that requires no additional configuration. The former manual country setting in Search Console historically only ever applied to gTLD properties anyway, since ccTLDs already carried a clearer, stronger signal.

For gTLD stores with no automatic country signal, directory structure, hreflang, and content language now fill the role that the manual setting partially served before. A store at mironsoft.de needs no additional configuration for this, since the ccTLD itself is a sufficient signal. However, ccTLD stores with multiple language variants, for example German and English on a .de domain, still benefit from correct hreflang, since the ccTLD only clarifies the country, not the language variant within that country.

4. Geotargeting vs. hreflang: two different problems

Geotargeting and hreflang are often used interchangeably, but they solve different problems. Geotargeting answers the question of which country a URL is associated with for the user, independent of language. hreflang, on the other hand, answers the question of which language and region variant of a page should be served in search results for which language-country combination, for example de-DE versus de-CH versus fr-CH. A store can have technically perfect hreflang implemented and still have unclear geotargeting, for example if a gTLD is run with no geographic structure at all.

Conversely, a clear geographic structure like country subdirectories alone does not solve the language problem: without hreflang, Google might show the German directory variant to an Austrian user even though a dedicated variant exists. Both mechanisms complement each other: hreflang ensures correct content matching between language variants of the same page, while geographic structure and domain signals ensure the basic country association. Anyone relying on only one of these two tools typically covers only half the problem in international Magento stores.

5. The myth of a direct ranking boost

The most persistent misconception around geotargeting is that correct country association directly improves search ranking position. That's false: geotargeting does not affect ranking position, it only affects which users a result is shown to preferentially. A page with excellent geotargeting but weak content relevance does not automatically rank better for a German user than an international competitor page with stronger content, just because its geotargeting is technically correctly configured.

The practical effect of geotargeting lies in visibility distribution, not ranking strength: with correct configuration, the German page variant competes primarily with other German-language or Germany-related results for visibility among German users, instead of competing against its own English variant or appearing in countries it was never meant for. This can indirectly increase effective visibility in the target market by reducing cannibalization between a site's own URL variants, but it changes nothing about a single page's fundamental ability to rank against the global competition.

6. Practical examples: domain, directory, and subdomain strategies

For Magento stores with multiple store views, there are three common structural patterns: separate ccTLDs per country (mironsoft.de, mironsoft.fr), subdirectories on a gTLD (mironsoft.com/de/, mironsoft.com/fr/), or subdomains (de.mironsoft.com). ccTLDs offer the strongest implicit geotargeting signal but come with the highest maintenance overhead, from separate domains and SSL certificates to sometimes separate link-building strategies. Subdirectories are the technically simplest to implement in Magento via store views with their own base URL path per store view, and they consolidate domain authority for all country variants under one domain.

Pure parameter URLs like mironsoft.com/?country=de should be avoided, since Google treats parameter URLs unreliably as standalone, geotargetable entities, and they don't pair well with hreflang. In practice, most international Magento stores combine several patterns: a ccTLD for the home market with the strongest customer base, plus subdirectories on a gTLD for smaller or new target markets where a dedicated domain doesn't yet make economic sense. Every store view URL needs consistent hreflang references to every other language variant, including a self-reference.

<!-- Hyvä phtml: reciprocal hreflang tags for a gTLD multi-region setup -->
<?php
/** @var \Mironsoft\Core\ViewModel\HreflangViewModel $hreflangViewModel */
$hreflangViewModel = $viewModels->require(\Mironsoft\Core\ViewModel\HreflangViewModel::class);
?>
<?php foreach ($hreflangViewModel->getAlternateUrls() as $localeCode => $alternateUrl): ?>
    <link rel="alternate" hreflang="<?= $escaper->escapeHtmlAttr($localeCode) ?>" href="<?= $escaper->escapeUrl($alternateUrl) ?>">
<?php endforeach; ?>
<!-- x-default catches users outside all explicitly targeted locales -->
<link rel="alternate" hreflang="x-default" href="https://mironsoft.com/en/product-a">

<?xml version="1.0" encoding="UTF-8"?>
<!-- sitemap.xml: hreflang alternates via the xhtml:link extension -->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
        xmlns:xhtml="http://www.w3.org/1999/xhtml">
  <url>
    <loc>https://mironsoft.com/de/produkt-a</loc>
    <xhtml:link rel="alternate" hreflang="de-de" href="https://mironsoft.com/de/produkt-a"/>
    <xhtml:link rel="alternate" hreflang="fr-fr" href="https://mironsoft.com/fr/produit-a"/>
    <xhtml:link rel="alternate" hreflang="en-us" href="https://mironsoft.com/en/product-a"/>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://mironsoft.com/en/product-a"/>
  </url>
  <url>
    <loc>https://mironsoft.com/fr/produit-a</loc>
    <xhtml:link rel="alternate" hreflang="de-de" href="https://mironsoft.com/de/produkt-a"/>
    <xhtml:link rel="alternate" hreflang="fr-fr" href="https://mironsoft.com/fr/produit-a"/>
    <xhtml:link rel="alternate" hreflang="en-us" href="https://mironsoft.com/en/product-a"/>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://mironsoft.com/en/product-a"/>
  </url>
</urlset>

7. Other geographic signals Google evaluates today

Beyond domain structure and hreflang, Google evaluates a range of other signals to assess a page's geographic orientation. These include the server location or the origin of the CDN response, the language and currency used in the visible content, contact and address details in the footer or in structured data, and the origin of inbound backlinks. None of these signals is strong in isolation, but together they form a far more reliable picture than a single manual setting ever could.

Particularly relevant for Magento stores: pricing in local currency, localized payment and shipping options, and an Organization or LocalBusiness schema with areaServed support the geographic classification in addition to technical structure. Server location plays a minor role today, since most stores are delivered via globally distributed CDNs anyway, though it used to be a frequently overestimated signal. It's important that all signals point in the same direction: a .fr domain with exclusively English content and US dollar pricing dilutes the association instead of reinforcing it.

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Mironsoft",
  "url": "https://mironsoft.com/de/",
  "areaServed": [
    { "@type": "Country", "name": "Germany" },
    { "@type": "Country", "name": "Austria" },
    { "@type": "Country", "name": "Switzerland" }
  ],
  "address": {
    "@type": "PostalAddress",
    "addressCountry": "DE"
  },
  "sameAs": [
    "https://www.linkedin.com/company/mironsoft"
  ]
}

8. Spotting common mistakes and validating continuously

The most common technical mistake is non-reciprocal hreflang: page A links to page B, but page B doesn't link back to page A. In that case, Google ignores the entire hreflang group for both pages. Another common mistake is missing self-reference, since every page must also link to itself via hreflang, not just to the other variants. Equally problematic are IP-based automatic redirects that push users to a supposedly matching country version without asking, which can also send Googlebot, which mostly crawls from the US, to the wrong version or no version at all.

Another misconception rooted in the deprecated Search Console setting: many teams still believe today that ccTLD stores with multiple languages don't need hreflang, because the domain is already "geotargeted." That's only true for country association, not for the language association within that country, for example German and Turkish on a .de domain. Inconsistent x-default declarations, duplicated hreflang codes, and canonical tags that point to a different language variant than the current page are also among the most common causes of ignored hreflang markup in Google Search.

Since Search Console no longer offers a manual geotargeting switch, control shifts to validation and monitoring. URL Inspection in Search Console shows, for individual pages, which version Google has actually indexed and whether a canonical conflict exists. A full, site-wide hreflang check requires third-party crawlers like Screaming Frog or Sitebulb, since Google removed the former site-wide hreflang error overview from Search Console. It's also worth reviewing the performance report filtered by country: if a German page variant shows notable impressions from the wrong countries, that points to unclear geographic signals.

// Alpine.js component: suggest a region instead of forcing a redirect
// Automatic IP based redirects can hide content from Googlebot entirely
document.addEventListener('alpine:init', () => {
  Alpine.data('regionSuggestion', () => ({
    show: false,
    suggestedLocale: null,

    init() {
      const browserLocale = navigator.language || navigator.userLanguage;
      const currentLocale = document.documentElement.lang;

      // Only suggest, never redirect automatically
      if (browserLocale && !browserLocale.startsWith(currentLocale)) {
        this.suggestedLocale = browserLocale;
        this.show = true;
      }
    },

    dismiss() {
      this.show = false;
      localStorage.setItem('region-suggestion-dismissed', 'true');
    }
  }));
});

#!/usr/bin/env bash
# Quick reciprocity check: does every hreflang target also link back?
URLS=(
  "https://mironsoft.com/de/produkt-a"
  "https://mironsoft.com/fr/produit-a"
  "https://mironsoft.com/en/product-a"
)

for url in "${URLS[@]}"; do
  echo "Checking: $url"
  curl -s "$url" | grep -o '<link rel="alternate" hreflang="[a-z-]*" href="[^"]*"'
  echo "---"
done

# Compare the extracted hreflang sets manually or pipe into a diff script
# to confirm every URL references every other URL, including itself.

9. Geotargeting, hreflang, and ccTLD compared side by side

Geotargeting, ccTLD signals, and hreflang differ significantly in mechanism and effect, yet they are frequently confused or pitted against each other in practice. The table below breaks down the key mechanisms, their actual effect, and the most common misconceptions around each.

In practice, all signals need to point in the same direction: ccTLD, hreflang, domain structure, language, and currency should all communicate the same target country instead of contradicting each other. Correctly configured geotargeting reduces cannibalization between a site's own URL variants and improves effective visibility in the target market, but it doesn't replace any of the classic ranking factors like content quality or backlink profile.

10. Summary

Geotargeting in Search Console hasn't existed as a manual switch since 2022, but that changes nothing about the need to correctly orient international Magento stores geographically. ccTLDs provide a strong, automatic country signal and require no additional configuration. gTLDs without their own country signal, on the other hand, rely on a consistent combination of domain structure, hreflang, language, and currency to give Google a clear geographic association. hreflang and geotargeting solve different problems here and don't replace each other, they complement one another: one clarifies the language variant, the other the country association.

The most important takeaway for practice: geotargeting does not improve a page's ranking position, it controls which user group sees it preferentially. Anyone who internalizes this distinction stops treating geotargeting as a ranking lever and starts using it instead as a tool against cannibalization and for a clean international structure. Regular validation via URL Inspection, third-party crawlers, and country-specific performance data reliably replaces the manual setting that's gone.

11. FAQ: Geotargeting in Search Console