Can the regionsAllowed attribute limit the visibility of your videos in certain countries?

How does the regionsAllowed attribute actually work?

The regionsAllowed attribute fits directly into the VideoObject structured data that you deploy on your pages containing videos. Its syntax expects an array of country codes in ISO 3166 format (FR, DE, US, etc.). Google crawls this information, indexes it, and then uses it as a geographic broadcasting filter when building the SERPs.

When a user searches from a given country, Google checks if that country is on the allowed list. If so, the video can appear in rich results (video rich snippets, carousels, Google Discover). If not, it is purely and simply excluded from the results for that user, even if the rest of your page is perfectly optimized.

Why does Google offer this feature?

The answer can be boiled down to two words: broadcast rights. Media outlets, streaming platforms, and video content publishers often sign territorial agreements that prohibit them from showing certain videos outside specific geographic zones. Without a technical restriction mechanism, they risk contractual disputes or copyright violations.

Google addresses this need by providing a granular control lever. Instead of blocking video access server-side (which generates 403 errors or complex redirects), you signal the broadcast constraints directly to Google. The engine then takes care of not displaying the video in unauthorized countries, simplifying the technical stack.

What is the difference with server-side geo-blocking?

Traditional geo-blocking (IP detection + access denial) operates on the server level: the user attempts to access the video, your CDN or backend detects their location, and sends back an error or an alternative page. This is effective, but it creates contradictory SEO signals: Google can crawl from U.S. IPs, discover the video, index it, and then find that French users have no problem accessing it.

With regionsAllowed, you explicitly describe the broadcasting policy in your metadata. Google understands the rule before attempting to display the video in the SERPs. The result: no false hopes for users, no artificially inflated bounce rates, and a consistency between indexing and user experience.

• regionsAllowed accepts an array of ISO 3166 country codes (e.g., ["FR", "BE", "CH"])
• Videos not authorized for a country do not appear at all in local results
• This restriction applies to video rich snippets, carousels, and Google Discover
• The rest of the page can still rank; only the video is filtered
• No SEO penalty: it's a declarative filter, not a quality signal

Is this statement consistent with field observations?

Yes, and this is one of the rare cases where Google precisely documents a geographic filtering mechanism without ambiguity. Tests conducted on media sites (especially in sports and entertainment) show that the attribute is indeed respected: a video marked "FR" only disappears from UK or US SERPs, even if the host page ranks well.

However, be cautious: this filtering only applies to video rich results. If your page ranks in traditional organic position (blue link), the user will see the link, click, and potentially encounter an error message on the player side. The regionsAllowed attribute does not block the indexing of the page, only the display of the video in Google features.

What are the limits and gray areas of this attribute?

First limit: Google does not manage VPNs. A user in France with a VPN set to the USA will see American results, hence not your video restricted to France. There’s nothing you can do about it from an SEO perspective; it's an inherent constraint of geographic detection via IP.

Second point: if you combine regionsAllowed with server-side geo-blocking, ensure that the two mechanisms are aligned. A discrepancy (e.g., regionsAllowed allows DE, but your CDN blocks German IPs) creates an inconsistent experience. Google often crawls from US IPs, so check that Googlebot can access the video for proper indexing. [To verify]: exact behavior if Googlebot is blocked but regionsAllowed lists allowed countries—logically, Google should not index the video at all.

When does this feature become counterproductive?

If you run an international site without territorial broadcasting constraints, using regionsAllowed is like shooting yourself in the foot. You artificially reduce your potential audience when Google could have distributed your videos globally. That's organic traffic you leave on the table.

Another trap: configuration errors. A webmaster who mistakenly lists just one country (e.g., "US") instead of a complete list is cutting access to 95% of global traffic. Unlike other Schema.org attributes that generate warnings in the Search Console, regionsAllowed operates in silent mode: no alert if you mess up, you just notice an unexplained drop in video traffic.

How to properly implement the regionsAllowed attribute?

Integrate the attribute into your existing VideoObject markup. The property expects an array of strings in ISO 3166-1 alpha-2 format (two-letter country codes). A concrete example: if your video can be broadcast in France, Belgium, and Switzerland, you write "regionsAllowed": ["FR", "BE", "CH"]. Google interprets this list as a whitelist: only these countries will see the video in the results.

Test the implementation with Google’s Rich Results Test. The tool validates the Schema.org syntax and confirms that the attribute is recognized. Then, use a VPN or proxy to check that the video does indeed disappear from the SERPs of non-listed countries. Don't forget to monitor the Search Console: video impressions should logically decrease in excluded countries and focus on the allowed areas.

What mistakes must be absolutely avoided?

Mistake #1: listing invalid or outdated country codes. Strictly adhere to the ISO 3166-1 alpha-2 standard. "UK" does not exist; it's "GB" for the United Kingdom. "EN" doesn't exist either; "EN" is a language code, not a country code. A typo ("FRA" instead of "FR") is enough to invalidate the attribute and potentially block the video everywhere.

Mistake #2: confusing regionsAllowed with contentLocation. The former filters display by country, the latter specifies where the video was filmed (a descriptive metadata). Using contentLocation thinking it restricts broadcasting is pointless. Mistake #3: forgetting to synchronize the markup with your video player. If regionsAllowed says "FR" but your YouTube or Vimeo embed blocks France, the user clicks on the rich snippet, arrives on your page, and sees an error message. Guaranteed bounce rate.

How to check that the configuration produces the expected effects?

Three complementary methods. First: analyze the video performance reports in the Search Console ("Enhancements" section > "Videos"). Filter by country and verify that impressions are indeed concentrated in the allowed areas. Second: use a multi-country rank tracking tool (SEMrush, Ahrefs, SE Ranking) to monitor the positions of your video rich snippets in different markets.

Third: deploy server log monitoring. If you find video traffic coming from theoretically excluded countries, either your regionsAllowed isn't being taken into account (incorrect syntax, outdated crawl), or users are accessing through VPNs. Cross-reference this data with Google Analytics to identify traffic anomalies and adjust your configuration if necessary.

• Integrate regionsAllowed in the VideoObject with valid ISO 3166-1 alpha-2 codes
• Validate the syntax using Google's Rich Results Test
• Synchronize the list of allowed countries with your video player and CDN rules
• Test the display from multiple countries via VPN or geolocated proxies
• Monitor video impressions by country in the Search Console
• Document the legal or contractual reasons justifying each restriction