What you need to know
Use areaServed on Service or Organization when geographic coverage matters. Choose a real Country, AdministrativeArea, City or Place and make sure the visible page supports that scope.
areaServed specifies the geographic area where an Organization or Service operates. It can use Country, AdministrativeArea, City or Place. It is different from address, which describes where the entity is located.
Key properties
The table below summarizes the fields that most often determine whether the entity is clear and internally consistent. Only provide values supported by the page.
| Property | Importance | How to use it |
|---|---|---|
areaServed | Main property | Real service coverage. |
Country | Broad scope | For genuine nationwide service. |
AdministrativeArea | Regional scope | State/province/region. |
City | Local scope | City-level service. |
Place | Generic | When a more specific geographic type is unsuitable. |
What areaServed means
It answers where the service is available, not where a visitor is located or where a testimonial mentions a city.
Choose the right type
Use Country, AdministrativeArea or City according to real coverage. More precise claims need stronger support.
Service versus Organization
An organization can serve broadly while one specific Service has narrower coverage. Model the real relationship.
areaServed versus address
Address says where an entity is based; areaServed says where it delivers service.
Multiple areas
Multiple values are valid, but a broad Country is often clearer than hundreds of city names when coverage is truly nationwide.
Local SEO
areaServed does not create local rankings by itself. Use it as factual structured data, not a location-keyword generator.
Validation
Compare geographic claims with visible service copy and remove stale coverage after business changes.
JSON-LD examples
Nationwide service area
Use Country for real nationwide coverage.
{
"@context": "https://schema.org",
"@type": "Service",
"name": "Technical SEO Audit",
"provider": {
"@type": "Organization",
"name": "Example Agency"
},
"areaServed": {
"@type": "Country",
"name": "United States"
}
}Regional service areas
Multiple areas are valid when each region is truly served.
{
"@context": "https://schema.org",
"@type": "Service",
"name": "On-site AV Installation",
"areaServed": [
{
"@type": "AdministrativeArea",
"name": "New York"
},
{
"@type": "AdministrativeArea",
"name": "New Jersey"
}
]
}Google, Bing and Yandex
areaServed is valid Schema.org data but not a standalone rich-result trigger.
Bing can use geographic entity relationships from Schema.org JSON-LD to understand content.
Yandex supports Schema.org selectively; accurate area data still helps machine understanding.
Important: valid structured data does not guarantee a rich result. Each search engine decides whether to use the data and how to present it.
Common mistakes
- warningUsing areaServed as an SEO city list.
- warningConfusing address with service coverage.
- warningClaiming nationwide coverage without evidence.
- warningCopying one area to every Service.
- warningKeeping obsolete areas.
Frequently asked questions
Is areaServed the same as address?
No. address is where an entity is located; areaServed is where it delivers service.
Can areaServed list several cities?
Yes, when all are genuinely served.
Does areaServed improve local rankings?
Not directly. It is semantic data, not a ranking shortcut.