Unique Phuket Weddings: Distinct entity scope across sibling wedding brands
Three wedding-adjacent brands in the network required schema-distinct positioning to avoid duplicate entity signals that would confuse crawlers.
https://uniquephuketweddings.com/ · Weddings — planning and venues · Published 26 February 2026
Challenge
Unique Phuket, Wedding Celebrant Asia and Unique Phuket Weddings all address related audiences. Without clear scope boundaries, the graph would appear to define the same entity three times.
Audit
IA workshop drew clear boundaries: wedding planning and venues here; celebrant services on the sibling; flagship destination wedding planning on the Unique Phuket parent. Each brand's Organization schema updated to reflect the boundary via description and service catalogue.
Implementation
Distinct @id per brand. Cross-references via network graph express relationship, not identity. Every wedding-planning page here links to the celebrant sibling and the parent brand where relevant.
Validation
Rich Results Test on each brand shows distinct Organization nodes. No duplicate structured-data warnings.
Outcome
Three sibling brands, schema-distinct, mutually reinforcing rather than mutually diluting.
Lessons learned
Sibling brands need explicit scope boundaries in schema. Implicit boundaries via visual design don't reach crawlers.