Enos Restaurant
Enos is an Italian restaurant in Weybridge that needed reservations running on its own infrastructure rather than through a marketplace taking a cut of every cover. We built the site with its own reservation service behind the booking form, and marked that path up with ReserveAction and FoodEstablishmentReservation so search engines can read it as a bookable action.
- Sector
- Restaurant
- Location
- Weybridge
- Year
- 2025
- Built with
- React · Vite · GSAP · Lenis · Custom reservation API
The problem
Restaurant bookings usually arrive through a marketplace that charges per cover and owns the diner relationship. The restaurant wanted the booking to happen on its own site, on its own terms, and still be visible to search engines as something you can act on rather than a form nobody can see inside.
What we built
- A reservation API on the restaurant's own infrastructure, so bookings are not routed through a marketplace
- ReserveAction and FoodEstablishmentReservation markup with a typed EntryPoint, so the booking path is machine-readable
- Full Restaurant and Menu structured data, with opening hours, geo coordinates and postal address
- Service areas marked up as City and AdministrativeArea, matching where the restaurant actually draws from
- GSAP and Lenis for motion, scoped so reduced-motion preferences are respected
Bookings that belong to the restaurant
A reservation taken through a marketplace costs money per cover and, more importantly, puts somebody else between the restaurant and the diner. The booking confirmation, the reminder, the record of who came and when - all of it accrues to the platform.
Enos takes bookings through its own site, backed by a small reservation API of its own. There is no per-cover fee because there is no intermediary to pay.
Making the booking path machine-readable
A booking form is invisible to a search engine unless you tell it what the form does. This build
marks the reservation path up as a ReserveAction with a FoodEstablishmentReservation result and
a typed EntryPoint, which is the vocabulary Google and AI assistants use to understand that a
page offers a bookable action rather than just describing one.
The rest of the graph carries the parts people actually search for: the menu, the opening hours, the address and the coordinates.
Motion without the cost
The site uses GSAP for sequencing and Lenis for scroll, both scoped inside a matchMedia block
with teardown, so a visitor who has asked their operating system for reduced motion gets a static
page rather than a degraded animated one.
Tell us what you need built.
A short call, a straight answer on scope and cost, and a fixed quote. No retainer, no monthly fee, no commission on your orders.