.svg)
spatialCoverage
spatialCoverage · Recommended by Google
Appears in
What is it?
The spatialCoverage property describes the geographic area that a dataset covers. It tells data consumers whether the data applies to a specific country, region, coordinate range, or global scope.
Values can be a simple text description ("Sweden"), a Place object with a name, or a Place with precise GeoCoordinates or GeoShape boundaries.
Why this matters for AEO
When a user asks "is there rainfall data for the Pacific Northwest," AI answer engines check spatialCoverage to match datasets to geographic queries. A Place object with coordinates lets the AI determine geographic overlap precisely, rather than relying on text matching.
What the specs say
Schema.org:Place. The spatialCoverage of a CreativeWork indicates the place(s) which are the focus of the content. It is a subproperty of contentLocation intended primarily for more technical and detailed materials.
Google: Recommended. "You can provide a single point that describes the spatial aspect of the dataset. Include only if dataset has spatial dimension." Source
How to find your value
- Weather station data — Station coordinates (lat/long)
- Country-level statistics — Country name or ISO code
- Regional surveys — State, province, or region name
- Global datasets — "Earth" or world bounding box
- City-level data — City name with coordinates
Format and code
Simple text:
{
"@context": "https://schema.org",
"@type": "Dataset",
"name": "Indo-Pacific Biodiversity Survey",
"spatialCoverage": "Primarily focused on the tropical Indo-Pacific region, with an emphasis on Oceania"
}
Place with coordinates:
{
"@context": "https://schema.org",
"@type": "Dataset",
"name": "Svartberget Climate Data",
"spatialCoverage": {
"@type": "Place",
"containedInPlace": {
"@type": "Country",
"identifier": "SE",
"name": "Sweden"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": 64.226154,
"longitude": 19.770768
}
}
}
Bounding box for a region:
{
"spatialCoverage": {
"@type": "Place",
"geo": {
"@type": "GeoShape",
"box": "39.3 -120.5 41.2 -118.1"
}
}
}
Webflow implementation
Static pages
Add the spatialCoverage object inside your Dataset JSON-LD block in Page Settings > Custom Code > Footer Code. Use GeoCoordinates for point data or GeoShape for regional boundaries.
CMS template pages
Store latitude, longitude, and location name in CMS number and text fields. Reference them in a custom code embed to build the Place object dynamically.
In Schema HQ
The spatialCoverage field does not currently generate Dataset markup. Add spatial coverage data manually through Webflow custom code.
Real examples
From Swedish Research Data Service:
{
"@context": "https://schema.org",
"@type": "Dataset",
"spatialCoverage": [
{
"@type": "Place",
"containedInPlace": {
"@type": "Country",
"identifier": "SE",
"name": "Sweden"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": 64.226154,
"longitude": 19.770768
}
}
]
}
Related fields
FAQ
Should I use text or a Place object?
Use a Place object with GeoCoordinates or GeoShape for precision. Text descriptions like "Pacific Northwest" are valid but less useful for geographic matching. Google's documentation recommends providing at least a single point coordinate when possible.
Can a dataset cover multiple locations?
Yes. Pass an array of Place objects in spatialCoverage. Each can have its own coordinates and name. This works well for multi-site studies or distributed sensor networks.
