AcaciaConciergeStart a conversation
Back to home

Case study · Hospitality & lodging

A direct booking presence for an independent boutique hotel.

An independent oceanfront hotel and villas came to us with a site that looked finished at a glance — and a page-builder underneath it that couldn’t hold their rooms, their languages, or their reputation. This is what the audit found and what the rebuild puts in its place.

The property is kept anonymous here by agreement. Every figure comes from a direct manual review of their live site and public listings.

618

Verified reviews found

0

Shown on their own site

7

Critical fixes identified

The diagnostic

What the audit caught.

A 27-page report covering 10+ diagnostic categories from our scorecard — written before a single line of the rebuild was scoped.

Finding 01

A second, undated checkout

Testing the live site surfaced a shopping-cart-style checkout running alongside the real reservation system: one click, no check-in or check-out dates, and a different price for the same room. A payment nearly went through during testing — a chargeback and dispute risk that shouldn't wait on a rebuild.

Finding 02

A strong reputation, invisible

618 verified reviews averaging 4.1★ on the largest travel platform — a genuinely strong number — appeared nowhere on the property's own website. Guests deciding on the homepage saw none of it.

Finding 03

Two languages, no signal

English and Spanish were mixed across pages with nothing telling a guest, or a search engine, which language they were reading. International visitors landed in the wrong one and search engines couldn't separate them.

Finding 04

No data layer behind the pages

Rooms, capacities, amenities, and rates lived as static page-builder text, hand-edited every time something changed. Search titles led with the raw domain rather than the property name, and a leftover platform test login sat exposed on the public site.

The rebuild

Four weeks, one system.

A fixed-price foundation scope, with every growth piece priced the same way and added only when the property is ready.

Week 1

Data model & content plan

Rooms and units move into a real data table — capacity, amenities, photography, indicative pricing — so the site stops being a stack of hand-edited pages.

Week 2

Core build, bilingual on purpose

Every page in both languages behind one clear toggle, with proper language tagging so guests and search engines always know which version they're on.

Week 3

Search & answer-engine pass

Real per-page titles and descriptions, lodging structured data, and a cleaned sitemap — the groundwork search engines and AI answer engines both read. The verified rating and review count finally sit on the homepage.

Week 4

One booking path, then launch

The real reservation system becomes the only way to book and the rogue storefront checkout is retired entirely. Cross-device testing, launch, and domain cutover close the build.

When you’re ready

Growth, added later.

None of these are required to launch. Each is priced on its own and can follow months after the foundation is live.

Bilingual AI concierge

Answers the recurring questions — breakfast, airport distance, children, pets — in either language, at any hour, and points to the right page when it's relevant.

Bookable day passes

Day passes sold as real products with card or PayPal checkout, without a separate storefront platform or an extra monthly bill.

Wedding & event lead capture

An events page that actually collects inquiries instead of describing the venue and stopping there.

Ongoing content hub

Real, ongoing pages for the searches guests actually type — the acquisition channel a static builder page can't support.

Hospitality enquiries

Running a hotel, lodge, or villas?

Tell us what guests struggle with today — booking, languages, or simply finding you. We read every message and reply within 24 hours.

hello@acaciaconcierge.xyz