Wedding Celebrant Asia: Person + ProfessionalService as first-class entities
A service-driven site rebuilt around the celebrant as a schema Person and the practice as a ProfessionalService, wired into the network graph.
https://weddingcelebrantasia.com/ · Professional services — celebrancy · Published 22 January 2026
Challenge
Flat internal linking, no Person schema for the celebrant despite the entire business being built on their credentials, no ProfessionalService node, and title/description patterns inherited from a generic WordPress theme.
Audit
Service pillars extracted from GSC query data. Historical URL audit identified genuine service pages worth preserving versus WordPress noise (author archives, tag pages, empty categories).
Implementation
IA rebuilt around service pillars. Person schema added with worksFor pointing at the ProfessionalService. Both entities cross-referenced with Unique Phuket via the network graph. Every service page carries a BreadcrumbList and unique head metadata.
Validation
Rich Results Test clean. sameAs targets verified back-link. Redirect register accounts for every historical URL — kept, 301'd, or 410'd — with zero chains and zero loops.
Outcome
Celebrant now resolvable as a Person entity across the network. Service surface concentrated on pages with genuine SEO history. Aggregator noise retired.
Lessons learned
For service businesses built on a named practitioner, Person is not optional. Skipping it leaves the strongest entity signal on the table.