In-house property-site rebuild
One Astro framework that clones into any property's site with the booking engine wired straight in.
The property sites are where the booking engine actually lives, and they sat on an outside agency's CMS with the same gaps over and over. No rates shown. Decorative review badges instead of live ratings. Oversized hero images. Almost no direct-book perks. Every booking an OTA takes is one the direct channel should have kept, and these sites were not built to win that fight.
How it works
A data-driven Astro framework on Cloudflare Pages. One property data file drives the whole site, so the shared layout and components clone across properties while per-property photography and room data slot in. The booking flow is a direct Mews embed on each property's own config IDs, no agency middle layer. It is built to a 12-section standard with a hard pre-launch gate on Core Web Vitals (LCP under 2.5s, INP under 200ms, CLS under 0.1) and one headline metric: direct-booking share.
- One property data file clones the whole site
- A direct Mews booking embed, per-property config IDs, no middleman
- A pre-launch gate on Core Web Vitals and accessibility
- One test for every element: does it move a booking from OTA to direct, or lose one
It is piloted on one property, with the home and room pages live, and paused on purpose right now. I pivoted to optimizing the existing sites in place, because the agency cost is modest and the edits turned out to be cheap. The framework is on the bench, ready the moment the economics flip.
Agents give you options. The owner still decides which one earns its keep.