Wedding Flowers Phuket: Retiring commerce surface without losing authority

WooCommerce artefacts and product URLs no longer relevant to the business were retired via 410, preserving portfolio and inquiry flow.

https://weddingflowersphuket.com/ · Retail — wedding floristry · Published 29 January 2026

Challenge

The WordPress instance carried a full WooCommerce install even though commerce had been decommissioned years earlier. Hundreds of /product/ and /product-category/ URLs continued to be crawled and indexed, diluting the portfolio's entity signals.

Audit

URL inventory quantified the commerce debt: product URLs represented the majority of the historical index. GSC confirmed none carried meaningful search authority — they were technical residue, not business assets.

Implementation

Rebuilt as a portfolio + inquiry site on TanStack Start. Commerce URLs returned 410 Gone. ImageObject schema added per portfolio piece. Images migrated to Lovable Assets.

Validation

Crawled post-launch — no orphaned /product/ URLs. Portfolio image schema validated. Inquiry form tested end-to-end.

Outcome

Lightweight portfolio site with fully owned imagery and a clean entity footprint. Commerce debt fully retired.

Lessons learned

410 is the correct answer for technical residue. 301'ing a decommissioned product catalogue to a portfolio homepage would have diluted the portfolio's own signals — the opposite of the goal.