Let's say we have a website that is offered in English and German. Assume the Services offered -
{
"@context": "http://schema.org/",
"@type": "Service",
"serviceType": "#{t('TRANSLATION.MARKETING')}",
"provider": {
"@type": "LocalBusiness",
"name": "#{Settings.brand.company_name}"
}
-- are available in UK, Ireland, Germany, Austria and beautiful Switzerland (hence, content is available in both EN & DE).
Should we add the structured data both on EN & DE pages in English, or shall we translate it into each respective language?
Example - Translated JSON-LD with LocaleApp (Ruby on Rails):
"areaServed": [
{
"@type": "Country",
"name": "#{t('generals.united-kingdom')}"
},
"@type": "Country",
"name": "#{t('generals.ireland')}"
},
"@type": "Country",
"name": "#{t('generals.austria')}"
},
"@type": "Country",
"name": "#{t('generals.germany')}"
},
"@type": "Country",
"name": "#{t('generals.switzerland')}"
},
]
or just keeping it simple and tag in English (on both EN & DE):
"areaServed": [
{
"@type": "Country",
"name": "United Kingdom"
},
"@type": "Country",
"name": "Ireland"
},
"@type": "Country",
"name": "Germany"
},
"@type": "Country",
"name": "Austria"
},
"@type": "Country",
"name": "Switzerland"
},
]
I am split about this, given the information is for search engines, and to make sense of the content (Semantic Web). Of course anything tagged on a page needs to correspond to its content (according to Google Best Practice). However, JSON-LD remains something we feed to SEs and not the user. So by that logic, offering it in English should be sufficient. I have not been able to find a clear answer to this.
So if anyone has a link that confirms the best practice that would be amazing - or perhaps has experience with multilingual pages.