A website built for restaurants

The single most damaging decision a restaurant makes on its website is publishing the menu as a PDF. The PDF menu does not load fast on a phone (the device where most restaurant search happens), it cannot be searched or indexed by Google, it does not adapt to the screen, and it forces the hungry customer at 6pm to wait for a download and pinch-to-zoom a document that should be a scrollable page. The customer who is comparing three restaurants for tonight's dinner abandons the PDF-menu site for the one with a text menu, every time. The text menu is the most important restaurant-site decision, and it is the one most restaurants get wrong.

The Supper Club template structures the menu as text by default — sections (apps, mains, desserts, drinks), dish names, descriptions, and prices, all as searchable HTML. When you describe your restaurant and its menu to Black Nile, the AI structures the menu into sections that load instantly and that Google can index. A customer searching "best pasta in [city]" or "restaurant with vegetarian options near me" finds your menu items in the search results because they are text, not a locked PDF. The SEO benefit alone justifies the text menu; the conversion benefit is even larger.

The honest maintenance angle: a text menu is easier to update than a PDF. The restaurant that changes a dish or a price can update the text through the dashboard in plain English ("change the carbonara price to $19, add a new special: grilled branzino"). The PDF menu requires redesigning the document, re-exporting, re-uploading — friction that means the online menu drifts out of sync with the actual menu, and the customer who orders the dish that is no longer available is disappointed. The text menu stays current because it is easy to keep current.

Restaurant search has a distinctive pattern that most restaurant sites are built wrong for. The customer is not researching a week in advance — they are deciding where to eat tonight, or right now, on a phone, often while hungry and often comparing two or three options in adjacent browser tabs. The site that loads fast, shows the menu in one scroll, surfaces the hours and the location, and offers a reservation or order path wins the decision. The site that loads slowly, buries the menu behind a click, hides the hours in the footer, or forces a third-party reservation system that opens a new tab loses.

The Supper Club template is structured for this test. The hero leads with the cuisine and the neighborhood (so the customer confirms they are in the right place), the menu follows immediately (so the hungry customer can browse), the hours and location are prominent (so the customer knows you are open and where), and the reservation or takeout-request form is one scroll away. Every element answers a question the 6pm customer is asking, in the order they ask it. A site that requires the customer to hunt for any of these answers loses to the site that surfaces them.

The hours matter more than restaurants expect. A surprising number of restaurant sites display outdated hours (the Sunday brunch they stopped serving, the holiday hours from last year), and the customer who arrives to find the restaurant closed leaves a bad review. The dashboard makes it easy to keep hours current — and the Supper Club template surfaces them prominently so the customer can confirm you are open before they drive. Accuracy on hours is the most basic and the most overlooked restaurant-site trust signal.

Restaurant reservations are dominated by third-party systems (OpenTable, Resy, Tock) that take a per-cover fee and, more importantly, own the customer relationship — the reservation data, the contact info, the marketing permissions. A restaurant that routes every reservation through a third party pays an ongoing tax on its own customers and hands the relationship to a platform that markets competing restaurants to the same customer. The alternative is a reservation-request form on your own site that captures the party size, time, and contact info as a lead in your dashboard, and the restaurant confirms by phone or text.

The reservation-request model is lead-capture, not real-time booking — there is no live availability calendar that auto-confirms a table. For most independent restaurants, this is the better model, because the host can manage the floor (hold the large party for the back room, stretch the 7pm book, accommodate the regular who always asks for table 4) in a way that a real-time system cannot. The form captures the request; the host confirms and optimizes. The restaurant that runs its own reservation capture avoids the per-cover fee and keeps the customer data, and the customer who interacts with the restaurant's own brand (rather than a third-party interface) is more loyal.

The honest exception: very high-volume restaurants that genuinely need real-time availability (a 200-seat restaurant where the floor turns multiple times a night) may benefit from a real-time system. But the independent 40-seat bistro is better served by the request-and-confirm model, and the site should present the reservation-request form as the primary booking path. The customer who fills out the form gets a personal confirmation from the restaurant, which feels like hospitality rather than a transaction — and that feeling is what brings them back.

Restaurants are researched on the phone at 6pm on a Friday — the site has to load fast, show the menu without a PDF download, and make requesting a table one tap. A slow, menu-less restaurant site loses the party to the next result.

A restaurant site has a specific job: turn the person searching into a reservation request before they hit the next result. The Supper Club template family is built around that job, with the sections restaurants need on the page:

• Dinner service
• Lunch & brunch
• Takeout & delivery
• Private dining
• Catering
• Bar & drinks

These are the services restaurants customers actually search for. The AI names them explicitly on the generated site because vague copy — “comprehensive solutions” — does not rank and does not convert. A restaurant site that lists the real services, in the language customers use, captures the intent the search brought.

The lead-capture story for restaurants is reservation requests. A visitor to your site fills out a short form — the service they want, their preferred time or scope, their contact details — and the request lands in your dashboard Messages inbox with an in-app notification. You confirm by call or text.

This is lead-capture, not real-time scheduling. There is no live calendar that double-books you, no payment processing on the form. The reason it is designed this way: for restaurants, confirming every reservation request yourself keeps you in control of your schedule and your work. You prioritize, you sequence, you close the job on your terms. The form captures the intent; you convert it.

Restaurants rarely list prices on the site — the menu carries that. Price-range signaling ($, $$, $$$) on the page sets expectations without item pricing. That honesty about pricing — what you will quote up front versus what needs a look — is part of how restaurants build trust before the first conversation.

Restaurants are destination businesses — name your neighborhood and what's nearby (parking, landmarks). Delivery zones belong on the page if you deliver.

The Supper Club template structures your service area as a clear section on the page, in the language customers search. That clarity is what ranks a restaurant site for the near me query — generic geography like “serving the metro” does not. When you build your site on Black Nile, describe the towns or neighborhoods you cover in plain English and the AI puts it on the page as customers expect to find it.

Your Google Business Profile carries the menu link, hours, and reviews — keep all three current. Most restaurant searches start and end on the GBP; your site closes the reservation.

For restaurants, the Google Business Profile carries the reviews and the map pin; the website carries the full service list, the service area in detail, the proof, and the lead-capture form. The profile drives discovery; the website closes the reservation request. Both are necessary, and they reinforce each other when the name, address, phone, hours, and service area are consistent across them.

For the vast majority of restaurants, the Supper Club template and the lead-capture flow are exactly right. Try it free and judge the output for your specific business.