A service aimed at restaurants that need their menu to be accessible online, bookings to be channelled automatically, and the venue to appear on Google when a user searches for where to eat. A bespoke website is developed, with optimised load times, in-house editing by the team, and an SEO and GEO configuration tailored to the realities of the sector.
The most frequent situation: the manager updates the menu, the wine list or the prices in the internal system, but the website remains in the background. The customer sees an outdated menu, calls to confirm, and ends up choosing another venue with up-to-date information.
Without properly implemented local SEO, without Schema.org Restaurant, and without consistent data on the Google Business Profile, the restaurant does not appear in searches such as "restaurant near the Plaza Mayor" or paella in the city. Customers who have already decided to eat out are lost.
If TheFork, CoverManager or a proprietary system is used, the website must be integrated. Otherwise, each booking is managed manually via email, call or message, with the resulting saturation at weekends and the associated loss of bookings.
The majority of users searching for a restaurant do so from a mobile phone. If the site takes more than 2 seconds to load, does not display correctly, or the menu is illegible on a small screen, the customer abandons it within seconds in favour of the competition.
Any change to a photograph, a schedule or a dish requires a request to a third party, with the associated cost and waiting time. A well-designed restaurant site allows in-house editing by the team, without intermediaries.
Each element is designed with a specific orientation to the hospitality sector. This is not a generic site with an attached menu module: it is a website conceived to increase sales and optimise the management of the restaurant, with in-house editing by the team and no need for external assistance.
Dishes organised by sections (starters, paellas, mains, desserts, tasting menu). Each dish includes description, price, allergens, suggested pairing and a "signature" flag to highlight the chef favourites.
Wines classified by type (red, white, rose, cava…). Each reference includes grape, vintage, tasting notes, pairing and availability. When a wine sells out, the team marks it as such from the CMS and it disappears on the next build.
The site is integrated with TheFork, CoverManager, Resy, OpenTable or the management system in use. The booking enters the venue panel directly, without intermediate emails. If a bespoke system is required (in-house panel, table management by time slot), it is developed specifically.
Images that convey the experience of the venue: the dining room, the bar, the kitchen, the freshly served dishes, the team. Resources optimised (WebP, srcset, lazy loading) to ensure optimum performance even with limited wifi in the dining area.
Schema.org LocalBusiness and Restaurant, correctly configured Google Business Profile, meta tags by city, consistent business data (NAP), optimised sitemap and robots.txt, content oriented to real queries from users with the intent to eat out.
Parallel structure: when a dish is added in Spanish, it is added in the English JSON file and appears automatically in both languages. It covers the needs of international tourism without requiring two separate websites or manual duplication of contents.
JSON, visual panel or the solution best suited to the team workflow. In the Los Pinochos case, the team edits the menu, the wine cellar, the featured dishes, the opening hours and the venue data from JSON files directly, with no visual panel and no WordPress. Zero external maintenance, zero forgotten passwords.
Astro and TypeScript, 0 JavaScript by default on most pages, optimised images, preconnect to Google Fonts. The site is perceived as fast on the customer mobile device, the main access channel.
Project developed by the studio and live since 2026. It is the most complete example of the practice in this sector. The figures shown below correspond to the real project, not to a demo.
See the live siteThe same workflow is applied as with any client, with a pace adapted to the reality of hospitality, which operates between services and in which 30-minute calls must be planned with margin.
The relevant aspects of the restaurant are discussed: cuisine type, audience, service areas, booking system in use, current situation and main friction points. Duration of 30-45 minutes, by video call or phone, with no commitment.
Scope, timeline and price are presented in writing. What is agreed at the start is what is invoiced. Without last-minute additional items or undisclosed "complexities". If the project does not fit the practice, the client is referred to a trusted collaborator.
A visual proposal is prepared so that the client can assess the direction of the site (structure, style, colour palette) without making any payment. If the proposal is satisfactory, 20 % is paid to start.
As the development progresses, advances are shared with the client. Any modification is incorporated on the fly. Within 2-4 weeks, the site is ready for full review, on a provisional URL, before proceeding to its publication on the final domain.
The publication of the site on the client domain is carried out once the result has been validated. The remaining 80 % is then settled. The first 15 days, any minor adjustment is included.
Optional maintenance from EUR 25/month (2.5 hours for minor adjustments) or EUR 50/month (5 hours, valid for modifications of greater scope). Without contract commitment: the month it is not required, the service is cancelled at no cost.
The cost depends on the scope. As a reference, a restaurant website with menu, wine cellar, online bookings, gallery and local SEO starts at EUR 450. The budget is fixed in writing after the first conversation, without additional items appearing afterwards. The full breakdown of tiers and fees is available on the services page.
Yes. A bespoke CMS is implemented in JSON or in the backend agreed with the client: the team adds dishes, modifies prices, updates the wine cellar, marks a wine as out of stock, and all changes are reflected on the site without the need to touch the HTML. In the Los Pinochos case, the team edits the menu, the wine cellar and the featured dishes from JSON files directly, with no dependence on the studio or on third parties.
It depends on the system in use. If it is TheFork, CoverManager, Resy, OpenTable or another similar platform, the website is integrated with the corresponding system. If a proprietary system is available or a bespoke solution is required (in-house panel, table management by time slot), it is developed specifically. The objective is that the booking is incorporated directly into the venue panel, without intermediate emails or additional manual tasks for the front-of-house team.
With correctly implemented local SEO, yes: optimised Google Business Profile, Schema.org LocalBusiness and Restaurant, consistent business data (NAP), meta tags by city, and content oriented to real queries such as "Valencian cuisine restaurant in Valladolid", "paella near the Plaza Mayor" or "where to eat in Simancas". Transparency is in order, however: whether the site appears on Google depends ultimately on Google, and sometimes the results are quick, while in other cases they require more time. What is guaranteed is the delivery of the site in the best possible technical conditions to maximise its visibility opportunities. No empty guarantees are offered.
Multi-location websites are developed: a single site with dedicated pages per venue, each with its own address, hours, phone, menu, photographs and independent booking system. LocalBusiness schema per venue, structured sitemap and Google Business Profile for each location.
A typical restaurant website (menu, wine cellar, bookings, gallery, local SEO) is delivered within 2 to 4 weeks from the first conversation. The specific timeline depends on the speed with which the photographs, texts and menu are provided. In case an urgent delivery is required, an express sprint can be considered.
The wine cellar is included as a separate section. Each wine includes type (red, white, rose, cava…), grape, vintage, tasting notes, pairing and availability. The team can mark each wine as available or out of stock from the CMS, without the need for programming.
The bilingual Spanish/English version is included at no additional cost, with a parallel structure: when a dish is added in Spanish, it is incorporated in the English JSON file and appears automatically in both languages. It is the most efficient formula to cover the needs of international tourism without requiring two separate websites or manual duplication of contents.
Yes. The same approach works for private chefs, event catering and home cooking: presentation of menus and services, guideline pricing, bookings or contact in one click, event gallery and local SEO to show up when someone searches for a private chef or catering nearby. As a reference, such a website sits between EUR 280 and 600 depending on scope, with a fixed budget in writing after the first conversation.
If your business is a restaurant, you can submit your enquiry directly: a response is provided within 24 hours with a written quote. No commitment, no automated forms.
