Can you really block your site from Google Discover in certain countries?

Why is the question of geographical blocking arising?

Discover is not just a simple list of classic search results. It is a personalized feed that shows up without user query, powered by browsing history, interests, and approximate location.

Some publishers find that their content appears in countries where they do not wish to be visible — sometimes for contractual reasons (broadcast rights), legal reasons (GDPR compliance, taxation) or strategic reasons (business segmentation). Hence the question: can certain geographies be excluded from Discover?

What does “algorithmic and organic functioning” mean?

Google emphasizes that Discover does not have manual settings for geographical distribution. Unlike Google Ads campaigns where you can target or exclude specific areas, Discover is based on algorithmic signals: content relevance, freshness, expected engagement, user profile.

If a user based in Belgium has shown interest in French-speaking content about motorsports and your site covers this topic, Discover can present it to them even if you are primarily targeting France. There is no 'block Belgium' button in Search Console.

What indirect levers are still available?

Even though Google does not offer direct blocking by country within Discover, some indirect strategies do exist. These involve technical or editorial adjustments that indirectly influence the geographical distribution of content.

For example, hreflang helps Google understand which language version to serve in which country for classic Search — but its impact on Discover remains unclear. Similarly, geographical targeting in Search Console applies to the entire domain or subdomain, with no guarantee on Discover. Finally, outright blocking by IP or server-side geolocation can exclude some visitors, but it also cuts off access to Google bots based in those areas.

• No manual settings allow blocking Discover in a given country.
• Discover operates on algorithmic signals: relevance, interests, freshness, engagement.
• Indirect levers (hreflang, Search Console targeting, IP blocking) have limited effectiveness or side effects.
• The only radical method is to disable Discover entirely via the max-image-preview:none tag in meta robots, at the cost of losing all Discover traffic.

Does this statement align with field observations?

Yes, it perfectly matches what is observed. No SEO has ever found a 'exclude country X from Discover' panel in Search Console or in meta tags. Discover performance reports clearly show clicks by country, but no geographic filtering option appears.

However, Google remains vague about the actual influence of hreflang and geographic targeting in Search Console on Discover. [To be verified]: do these signals carry weight in the Discover algorithm, or are they completely ignored? No official data clarifies this. In practice, some multi-country publishers find that Discover generally respects hreflang language versions, while others do not.

What nuances should be added to this rule?

If Discover operates algorithmically, it also means that it adapts in real-time to user signals. A French expatriate in Germany may very well see French-speaking content in their Discover feed, even if the site is targeting France. The algorithm prioritizes linguistic and thematic relevance over strict geolocation.

One more point: geographical targeting in Search Console (available for gTLDs like .com, .org) may potentially influence classic Search, but its effect on Discover remains [To be verified]. No public A/B test clearly demonstrates that activating 'target France' in GSC reduces the site's appearance in Discover Belgium or Switzerland. It's a theoretical lever, not a certainty.

In what scenarios does this limitation pose a real problem?

Broadcast rights and licensed content: some media publishers cannot distribute certain content outside their country of origin (e.g., video clips, TV show excerpts). Discover can bypass this barrier by offering content to users outside the zone. A radical solution: blocking access by IP, but this also prevents Google crawling from foreign data centers.

Legal and tax compliance: an e-commerce site that cannot sell in certain countries but appears in local Discover creates user frustration and legal questions (price display, terms and conditions). Again, there is no clean solution on the Discover side — it needs to be managed at the site level (redirects, messages about geographical unavailability).

What should you do concretely if you want to limit Discover's geographical reach?

Accept the reality: Discover does not offer fine geographical control. If this lack of control poses a critical business problem, consider solutions outside of Discover — server-side IP blocking, geographical unavailability messages on pages, conditional redirection. None of these options are ideal; all have side effects (loss of crawl, poor UX).

If the goal is simply to favor a target country without blocking others, optimize hreflang and geographical targeting in Search Console. Even if their impact on Discover is not guaranteed, they clarify the site's intentions for Google's overall algorithm. This can indirectly influence distribution, without certainty.

What mistakes should be avoided at all costs?

Never block Googlebot by geolocation IP: Google crawls from data centers spread around the globe. Blocking certain countries also blocks some Googlebot instances, which harms overall indexing. If a Google bot based in Germany cannot crawl your site targeting France, you lose visibility even in France.

Another frequent mistake: adding max-image-preview:none thinking it will “limit” Discover. This tag does not limit; it completely deactivates eligibility for Discover. If 30% of your traffic comes from Discover France and you just want to avoid Discover Belgium, this tag cuts you off from both. It's a blunt tool, not a fine filter.

How can I check if my approach is working?

Monitor Discover reports in Search Console by country. If you have implemented hreflang, geographical targeting, or editorial adjustments (language, local themes), observe the evolution of the geographical distribution of clicks in Discover over 3-6 months. A gradual decline in non-targeted countries may indicate that the algorithm has integrated your signals.

Also, test the appearance of your content in Discover from different countries via VPN or geolocalized devices. It's rudimentary, but it gives an empirical idea. If your French-speaking content appears massively in Discover Germany while you have indicated 'target France', it's a signal that the indirect levers have limited effectiveness.

• Use hreflang to clarify language versions and target countries, even if the impact on Discover is not guaranteed.
• Activate geographical targeting in Search Console if you are using a gTLD (.com, .org) to signal your main market.
• Never block Googlebot by IP — it harms overall indexing.
• Avoid max-image-preview:none unless you want to completely disable Discover.
• Monitor Discover reports by country in Search Console to detect geographical distribution changes.
• If geographical blocking is critical for legal or contractual reasons, manage it at the application level (IP, redirection, unavailability message) rather than waiting for a Discover lever that does not exist.