Shares the service area in the structured data

The business's areaServed now comes from a serviceArea list in the site
content: Huizen and Gooi en Vechtstreek, as the pages describe it,
instead of a fixed Place Huizen. Services on other pages can use the
same list through areaServed().

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-10-24 23:40:24 +02:00
co-authored by Claude Opus 5.5
parent eb235368bf
commit befe97af1e
5 changed files with 87 additions and 2 deletions
+6
View File
@@ -18,6 +18,12 @@ const siteContent: SiteContent = {
email: { user: 'info', domain: 'andreaslop.nl' },
// Switched on once the API can receive the form
contactForm: { enabled: false },
// Huizen and the region around it (Bussum, Hilversum, …), as the pages
// say; not the whole country, which would weaken the local signal
serviceArea: [
{ type: 'City', name: 'Huizen' },
{ type: 'AdministrativeArea', name: 'Gooi en Vechtstreek' },
],
};
export default siteContent;
+10
View File
@@ -22,6 +22,16 @@ export interface SiteContent {
email: EmailAddress;
// Off: the form is shown dimmed under a "coming soon" notice (FR-HP-07)
contactForm: { enabled: boolean };
// Where Andrea mainly works, for the structured data of the business
// and its services. Matches what the pages say, not every place she
// would travel to.
serviceArea: ServiceArea[];
}
// A place in schema.org terms: a town, or a region such as Gooi en Vechtstreek
export interface ServiceArea {
type: 'City' | 'AdministrativeArea';
name: string;
}
// An image as the API will deliver it. width and height are the intrinsic