910 five-star reviews, and not one of them on his own website.
Henry Roth runs Rent A Maui Boy out of Wailuku — private Road to Hana tours, solo operator. He texted me around 21 August 2026, a friend referral, asking whether Digital Reach had moved into AI search.
rentamauiboy.com was not a website. It was a Squarespace-registered domain forwarding to a Linktree, so five years of five-star reviews — the thing that sells a $345 day with a stranger — sat inside Airbnb, on pages Airbnb owns.
Ten written questions went out on 22 August, then a 75-minute Zoom on 24 August. I screen-shared both proposals and he gave me the go-ahead on the call.
Prerendered because a crawler had found nothing.
The engagement existed because a crawler found nothing, so “the crawler finds something” was the build spec. That ruled out a normal single-page app, which serves an empty div and fills it in with JavaScript. This site is React 19, Vite 8, Tailwind 4 and react-router 7, but every route runs through a server-render step at build time and lands on disk as real HTML. On 26 August /road-to-hana-tour carried 2,284 characters of body text inside #root before a line of JavaScript ran.
The four moves behind the result
- 01
Seven pages with their own title, description, canonical and schema
Before: zero pages of his own that Google or an AI model could read. After: seven, plus a 404 that actually returns 404 with
noindex, follow. Every page shipsTouristInformationCenterwith a Wailuku locality and anAggregateRatingof 5.0 across 910 reviews; home and/road-to-hana-touraddTouristTrip, anOfferof $345 and aFAQPage. robots.txt and sitemap.xml are live, listing all seven URLs. - 02
The proof, moved out of Airbnb
Not a widget and not a plugin. On 31 August I parsed 862 of the 887 reviews out of the Airbnb listing’s reviews modal and published 43 verbatim as blockquote text — one per guest city across five years, nothing edited; two were dropped for naming guides Henry hires. That page alone carries 2,453 crawlable words.
His own estimate had been 900-plus. It became a counted number: 887 Airbnb + 14 Yelp + 6 Google + 2 Tripadvisor + 1 second Airbnb listing = 910, verified 31 August 2026 and dated on the page. One variable feeds the hero, the About table, the reviews page and the
AggregateRating, so the figure cannot drift. - 03
The domain went dark four days before launch
On 3 September the domain was returning SERVFAIL from every resolver: the Squarespace/Google zone had been deleted around 31 August, RDAP confirmed, and the delegation was left pointing at it. Nameservers moved to Namecheap that day; the apex resolved that afternoon.
Then the certificate. Namecheap Stellar does not include cPanel AutoSSL, and there was no certificate on the account at all. I issued a Let’s Encrypt certificate with acme.sh over HTTP-01 for the apex and www, installed through cPanel’s API on a renewal cron. rentamauiboy.com was serving 200 on 4 September 2026: valid certificate, seven routes, zero broken assets. Eleven days from the go-ahead.
- 04
Tracking the hand-off that actually exists
Bookings happen on Airbnb, and they should. The four tour cards map one to one to his four live listings, and Book now opens in a new tab. So the measurable conversion is the outbound click:
book_now_clickon five buttons, carrying tour name and tour price, plustext_me_clickon four links. Pageviews are re-fired manually on route change, because gtag fires once in a single-page app — a pass that surfaced two real defects: the tab title never changed between routes, and navigation never scrolled to the top.
He owns everything.
The domain and the hosting are registered and paid for in Henry’s own name, not mine. I set it up that way on purpose: if anything happens to me, he still owns every piece of this.
The same thinking shaped phase one. He asked for no calendar write access of any kind — he had lost bookable days once to a calendar sync that absorbed unrelated personal events — so the site ships a form, not a calendar, labeled in the site’s own words: “This is an enquiry, not a booking.” Airbnb is never framed here as something to escape: it carries his liability coverage, and his reviews live there.
What we didn’t promise — and why.
- The proposal offered a booking calendar and a payment gateway. The site has neither — a documented decision taken on 25 August at the client’s request, not a miss. Both are phase two, and SEO billing did not start before the site was live.
- The Google Business Profile, the piece that gates Maps, has never been handed over — six reviews on the 31 August count, and nothing here claims we touched it.
- There is no ranking, lead, booking or revenue number here, because none exists yet. The pre-launch Search Console baseline is genuinely zero: 0 clicks and 0 impressions, 1 June to 31 August 2026. This is a build story. When the property has 30 days of post-launch data I will add a dated, sourced results section — or none at all.
Your proof is probably sitting on someone else’s platform too.
