Websites for restaurants and cafés.

You can, and it will look right to you. But an image of a menu is unreadable to Google, to AI assistants, to screen readers, and to anyone on a slow connection who gives up before it loads. You will never appear in a search for the dish you are best at, because nothing can tell that you make it. Built as text it is searchable, readable aloud, and about a hundredth of the size.

Between $1,000 and $2,000 for most custom builds, and from $500 for a single focused page with a menu and an ordering path. You get a fixed price in US dollars after one short call, and that number does not move. A large multi-branch build with live availability is quoted individually.

Yes, and how the order finishes depends on what you can take payment with. Options are a real card checkout, cash on delivery, or composing the whole order into a single WhatsApp message to the number you already answer. The last one is the right answer for more Lebanese food businesses than people expect, and it is what our live client build does.

No. They bring orders you would not otherwise get, and cutting them off to make a point costs you money. The goal is narrower: make your own site the obvious place for a repeat customer, so you stop paying commission on people who already know you. Winning the first order and winning the fifth are different problems.

Yes, and this is not an optional extra — it is the difference between a site that stays true and one that quietly starts lying. If changing a price needs a developer, the price will be wrong within a month. Menu, prices, hours and sold-out items are all editable by you.

By having hours you can change yourself from a phone, in one place, that feed both the website and your structured data at once. Ramadan rearranges opening times for a month and no plugin predicts it. Temporary closures work the same way — a two-minute change, not an email to an agency.

You need photographs of your own food. They do not have to be expensive, but they cannot be licensed stock, because a generic image of a burger is recognisable as one and it undermines everything else on the page. If you have nothing usable we will say so before design starts rather than build around a gap.

That is the normal path, and the site is built assuming it. Instagram is good at atmosphere and bad at answering a question at the moment it is asked — open now, do you deliver here, is there a vegetarian option. The site handles those, and gives your ads somewhere to land that you control.

Each branch needs its own hours, its own area, and often its own menu variations, and it needs to be findable by people searching near that branch rather than near your head office. That is more work than one page listing three addresses, and it is quoted as such — but a single page for three locations ranks for none of them well.

Yes, and for a restaurant it matters more than most, because the page is often opened outdoors on mobile data by someone deciding quickly. Replacing an image-based menu with text does most of the work. There is a longer piece on building for slow connections linked below.

We build the request path — the form, the confirmation, the handoff to however you actually keep the book. Integrating with a full reservations platform is possible and quoted separately. If you currently take bookings on WhatsApp, that is not a problem to solve; it is a system that already works and the site should feed it.

Three to six weeks from kickoff for most builds, under two weeks for a single page. Menus are the usual reason a project slips, so getting yours into text early — even messily — is the most useful thing you can do to protect the launch date.