A restaurant website has one job: turn a hungry person holding a phone into someone sitting at your table. Most restaurant sites fail at that job for reasons that have nothing to do with the food. The menu is a PDF that will not open. The hours are from two summers ago. The phone number is not tappable. This guide walks through what a restaurant website in San Antonio actually needs, roughly in the order a diner needs it.
What a Restaurant Website Is Actually For
A restaurant website is a decision tool, not a brochure. Someone has already heard your name — from a friend, a Google Maps result, an Instagram post — and is now checking whether to commit. That visitor wants four things fast: what you serve, what it costs, when you are open, and how to get a table. Everything else on the page is secondary to those four.
That framing changes what belongs at the top of the page. First the name of the restaurant and what kind of food it is. Then hours and a tappable phone number. Then a direct path to the menu. For example, a taqueria on the West Side does not need a full-screen video of sizzling meat before a visitor can find out whether the kitchen is open at 9pm. The video can stay. It just cannot stand in the doorway.
The Menu Page Does More Work Than the Homepage
The menu is the most visited page on almost every restaurant website, and the menu should be real web text rather than a PDF or a photograph. A PDF menu forces a download, opens in a separate viewer, and renders at desk size on a phone screen. An image of a menu cannot be read by a search engine or a screen reader, and it pixelates the moment someone zooms in.
Build the menu as web page text with a real heading for each course. Then, when prices or dishes change, the owner edits text instead of asking a designer to export a new file. In practice this is the single change that saves a restaurant the most money over a year, because menus change constantly and PDF menus always go stale. If the kitchen runs specials, give specials a short section near the top where they are easy to swap out.
Photos Are What People Judge You On
Food photography sells the table more effectively than any sentence of copy. A diner scrolling your site is running a quick gut check on whether the food looks like something they want tonight. Dim, flash-lit phone photos read as a restaurant that has not been touched since the pictures were taken, even when the kitchen is excellent.
Daylight near a window beats a ring light, and a plate shot from slightly above beats a straight-on angle. Shoot a dozen dishes, the dining room with people in it, and one frame of the exterior so visitors recognize the building from the street. Then compress every image before it goes on the site — a four-megabyte photo straight off a phone is the most common reason a restaurant site crawls on mobile data. Image preparation belongs inside the web design work, not on the owner’s to-do list afterward.
Hours, Address, and Phone Belong on Every Page
Hours, address, and phone number are the three facts a restaurant visitor checks most often, and all three should sit in the footer of every single page. A visitor who has to hunt for your hours assumes you are closed. A visitor who finds hours on the website that contradict Google assumes the website is abandoned and trusts neither.
Put the phone number in a tel: link so one tap dials it. Put the address in a link that opens Maps. Then keep the website and the Google Business Profile in agreement, especially around holidays, because those two listings get compared constantly. First update Google, then the website, then any delivery app — in that order, because Google is what most people see first. Writing hours as plain text rather than baking them into an image also lets search engines read them.
Online Ordering and Reservations
Online ordering is where a restaurant website stops being marketing and starts being revenue. Two paths exist. The first is embedding a third-party service, which is quick to set up and takes a cut of every order. The second is running ordering on your own site through WooCommerce, which costs more up front and keeps the margin in the restaurant.
Which path fits depends on volume. A cafe doing a dozen pickup orders a day is usually better off with the embedded service, because the per-order fee stays smaller than the cost of a build. A restaurant doing steady daily volume will eventually pay more in commission than a custom build would have cost once. Either way, the order button should be visible without scrolling, on every page, because people arrive hungry and impatient. WordPress development covers the self-hosted route.
Speed Matters Most in a Parking Lot
Website speed matters more for a restaurant than for almost any other kind of small business, because the visit often happens outdoors on a weak signal. Someone is parked near Broadway deciding between two places, with one bar of service and a dying battery. A site that takes eight seconds to appear loses to the one that takes two.
Three things cause slow restaurant sites: uncompressed photos, a stack of plugins, and a theme built around a full-screen video header. Fix the photos first, since photos are usually most of the page weight. Then audit the plugins and remove anything not doing visible work. Finally, test on a phone with wifi switched off rather than on office broadband, which hides the problem completely. We covered the broader version of this in the signs a website is losing you customers.
Getting Found by People Searching for Dinner
Local search is how most new diners find a restaurant, and local search starts outside your website. The Google Business Profile — the panel holding your photos, hours, and reviews — drives more restaurant discovery than the website itself does. The website’s job inside that system is to confirm what the profile claims and to rank for the specific searches a profile cannot cover.
Those searches are narrower than most owners expect. Not “restaurants san antonio”, which is a fight a single location will not win, but phrases like “birria tacos near Loop 410”, “gluten free bakery Stone Oak”, or “patio dining Southtown”. Build a short page or section for the handful of those that genuinely describe you. Then add LocalBusiness and Menu structured data so search engines can read hours and dishes directly. Local SEO work usually starts there rather than with the website.
What a Restaurant Website Costs and How Long It Takes
A restaurant website built from scratch sits in the same range as any other custom small business site: Satxly projects run $5,000 to $20,000 and take six to ten weeks. What makes a restaurant different is the photo work and the ordering integration, and those two items are what move a quote within that band.
A simpler build — menu, photos, hours, an embedded reservation widget — lands near the bottom of the range. A build with self-hosted ordering, a bilingual menu, and a catering request flow lands near the top. Projects run on video calls. The slowest part is usually not design but getting menu text and photographs finalized. In practice, a restaurant that has its menu copy written and a photo shoot done before the project starts finishes closer to six weeks than ten.
Where to Start
If the menu on your site is a PDF, start there this week — that one change costs nothing and fixes the page people visit most. If you run a restaurant, cafe, or bakery in San Antonio and the whole site is working against you, tell us what you need. We write back within one business day.
