In short. Use regionsAllowed or ineligibleRegion with ISO 3166-1 country codes to describe video availability by country.
Definition:
regionsAllowednames the countries where aVideoObjectvideo is allowed.ineligibleRegionnames the countries where it is unavailable, using the two or three letter ISO 3166-1 country code format documented by Google.
Key facts
- Google's Video structured data documentation defines
regionsAllowedas the regions where the video is allowed. ineligibleRegiondescribes the region where the video is not allowed. When the property is absent, Google assumes that the video is allowed everywhere.- Google's documentation accepts multiple country codes and gives a JSON-LD array or multiple Microdata
metatags as the formats for multiple values. - Schema.org's
VideoObjectdefinition describesregionsAllowedas the regions where media is allowed and specifies ISO 3166 format for countries. - Google documents either
ineligibleRegionorregionsAllowed, whichever fits the site's availability rule.
How do the two properties express availability?
Google's Video structured data documentation treats regionsAllowed as a positive list. A country in that property is an allowed region for the video. ineligibleRegion expresses the opposite rule by naming a region where the video is unavailable. If neither property is specified, Google's documented assumption is that the video is allowed everywhere.
The documentation presents the two properties as alternatives. A minimal JSON-LD excerpt matching its example is:
{
"@context": "https://schema.org",
"@type": "VideoObject",
"regionsAllowed": ["US", "NL"]
}
The same page also shows ineligibleRegion with the value US in a VideoObject example. The property describes availability of the video itself, so it belongs on the VideoObject that represents that video.
Which region codes are supported?
Google specifies countries in the two or three letter ISO 3166-1 format. The examples use US and NL, and Schema.org describes the corresponding VideoObject property with ISO 3166 format. These are country codes, so a region value should identify a country rather than repeat a country name in free text.
The Google page gives the format and examples rather than a complete country-code table. The code set therefore comes from ISO 3166-1, while the structured data guidance determines how the codes are placed in the markup.
How should multiple values be encoded?
For JSON-LD, Google documents an array when several country codes apply. For Microdata, the same documentation specifies multiple meta tags. The matching JSON-LD shape is:
"regionsAllowed": ["US", "NL"]
The Schema.org page lists regionsAllowed with the value type Place and describes the property as media regions. Google's search documentation supplies the country-code syntax and the serialization options used in the examples.
Related terms
- What thumbnail data does Google require for VideoObject markup?
- How do I add key moments to a video with structured data?
- How do contentUrl and embedUrl differ in VideoObject?
- How can a video identify its creator and profile URL?
FAQ
Can you use both regionsAllowed and ineligibleRegion?
Google documents the properties as alternatives and says to add either one, whichever fits the site's rule. Choose the property that expresses the availability condition directly.
What happens when no region property is present?
Google and Schema.org both document an everywhere-allowed assumption when the relevant property is unspecified.
Can a region value be a country name?
Use the documented two or three letter ISO 3166-1 country-code format. Google's examples use US and NL.
Sources
- Google Search Central, "Video (VideoObject, Clip, BroadcastEvent) structured data", 24 September 2026
- Schema.org, "VideoObject - Schema.org Type", 16 September 2026
Check how a page reads to answer engines. Open the GEO score analyzer