Indulge Chefs: Website Rebuild and Guided Inquiry

The problem

Indulge already had its iPhone marketplace app (now live on the App Store), but the website was the front door most clients still used. The old Wix site had steady organic traffic and no working way to capture it. Inquiries went to an inbox with no date, guest count, or budget, nothing was tracked, and hundreds of past contacts had never been emailed. The owners wanted a rebuild with themselves at the center of the brand, without losing the pages that already ranked.

What we built

The plan was written and signed off section by section in August. The build followed in October, and indulgechefs.com moved to it on November 4, 2026.

• A search-safe move off Wix. Every URL on the old site was inventoried, and the permanent redirects are generated from that inventory at build time, so none is hand-edited and none is forgotten. The pages that ranked kept their addresses, titles, and headings. The domain moved with the business email untouched.
• A site that looks like the table. Full-bleed photography from the owners’ own events, a classic serif with a clean sans, quiet motion, a founders’ note, and a season calendar that shows where the kitchen is cooking each month.
• An inquiry that qualifies. One guided screen with seven short cards: occasion, dates, place, host, table, anything else, and a call to book. Each card saves as the visitor goes, and the last one puts the call on the owners’ calendar. Spam is filtered without a visible puzzle.
• Found in Google and AI search. Twelve market pages, a Hamptons page with the villages served, a FAQ written as short standalone answers, structured data for the business, the people, the services, and the FAQ, and an llms.txt generated from the same content as the pages.
• Measured from the first visit. Every inquiry step, every call, text, and booking click, and every key button reports to analytics, and the inquiry counts as a conversion for paid search.
• One ecosystem. The site routes two ways: clients who want the owners cook use the inquiry, and anyone who wants a vetted chef anywhere in the US goes to the app.

How it works

The site is static HTML on Cloudflare Pages, so search engines and AI assistants read the answer text on first load. The only server code is the inquiry endpoint, which writes to its own database, kept apart from the app’s, and alerts the owners. Tags load through one container, so a new event needs no page change.

Claims the owners could not yet document, such as awards and press, stayed off the page until they can.

Stack

Astro, Cloudflare Pages and Pages Functions, Supabase, Cloudflare Turnstile, Google Tag Manager, GA4, Google Ads conversion tracking, Schema.org structured data, llms.txt.

Where it stands

Live on indulgechefs.com since November 4, 2026. It is too early for results, so none are claimed here. Next is measurement: which market pages earn impressions and inquiries, how far visitors get through the inquiry, and which channels bring the clients who book. Together with the App Store app, this is the marketing and booking surface of the Indulge revenue ecosystem. The longer write-up is on ops-pal.com.