Skip to content

Unique Phuket: Flagship wedding planner and network anchor

The flagship Phuket wedding planning business — established in 2012 by Paul Cunliffe and Supparin — rebuilt from WordPress as the canonical Organization entity referenced by every sibling site in the network.

https://uniquephuket.com/ · Parent brand — flagship wedding planner · Published 15 January 2026

Challenge

Unique Phuket — the flagship destination-wedding planner operating in Phuket since 2012 — carried the network's oldest WordPress instance with heavy plugin surface, mixed image ownership across a third-party CDN and the WP media library, and only a partial Organization schema block with no cross-network relationships modelled.

Audit

Full URL inventory via live crawl, Wayback and GSC. Structured-data audit confirmed the site had no Person, no ProfessionalService, and no @id that could anchor the wider network graph. Image inventory revealed dual ownership — some assets on third-party CDNs the business could not control.

Implementation

Migrated the site to TanStack Start on Cloudflare Workers while preserving the wedding-planning service surface — destination weddings, beach and villa weddings, elopements, vow renewals, celebrant coordination and in-house floral design. Every image moved into Lovable Assets with immutable CDN URLs. A single canonical Organization entity was defined with a stable @id at /#organization, and this became the reference point for every sibling brand's owns/parentOrganization relationship.

Validation

Post-launch production crawl confirmed every canonical URL present, no broken internal links, and schema validated clean in the Rich Results Test. The network graph resolves — each sibling brand's @id reference to Unique Phuket now returns a matching Organization node.

Outcome

Flagship wedding-planning site modernised and network anchor established in a single migration. Nine sibling brands can now reference a single stable @id for the parent entity. Image ownership consolidated. Site weight reduced substantially versus the WordPress baseline.

Lessons learned

The parent brand of a network is the leverage point. Getting the anchor entity right removes ambiguity for every sibling site downstream. Doing this last would have forced rework across the entire graph.