Writing a menu that sells, and that Google can read
Updated 2026-07-25
The menu is the most-read page on a restaurant's website. A guest deciding whether to book, order or walk in reads it before almost anything else. Yet most menus are treated as an afterthought: a photo of a printed board, a PDF, a list of names with no prices. A menu is not a list. It is the closest thing your website has to a salesperson, and it is worth writing like one.
Write the dish, not the adjective
"Delicious homemade pasta" tells a guest nothing. What kind of pasta, with what, made how? Name the dish and the two or three things that make it worth ordering: the fresh crab, the twelve-hour broth, the chilli you grow out the back. Specifics sell; adjectives are noise. A guest orders a plate they can picture, not one they have been told is nice.
Let the order and layout guide the choice
A menu is a path, not a wall. Group dishes the way a guest decides: the things to share, the mains, the ones your kitchen is known for. Put your strongest, most profitable dishes where the eye lands first, near the top of a section, not buried in the middle. A menu that helps a guest choose sells more than one that simply lists everything and leaves them to it.
Prices belong on the menu
Leaving prices off does not make a guest spend more. It makes them hesitate, and a hesitating guest often closes the page. Clear prices are a courtesy and a signal of confidence. The only thing hiding them reliably does is lose the guest who would have been happy to pay.
A menu Google can read
If your menu is a photograph or a PDF, a search engine cannot read a word of it. So when someone nearby searches for a dish you serve, "khao soi near me", "wood-fired pizza Ao Nang", there is nothing for Google to match, and the table goes to whoever wrote their menu as real text. Building the menu as an actual web page, not an image, is what makes it findable. This is half of why a restaurant stays invisible on Google, and it is the fix with the highest return.
Real text also means you can change it yourself. Prices move, specials change, a supplier lets you down. On a menu built as text you raise a price in a moment; on a printed image you are calling someone.
Both languages, written properly
In Thailand your menu has two audiences who search differently and want different things, so it needs to work in Thai and in English, written for each rather than machine-translated. A dish name that reads perfectly in Thai can be meaningless in a literal English rendering, and the reverse. Doing both properly is its own small craft, covered in ranking in Thai and English.
A menu that names the dish, guides the order, shows the price, and can be read by both a hungry guest and a search engine does more for a restaurant than almost anything else on the site. If yours is trapped in a photo or an app, tell us what you have now, or see what a restaurant site includes.
Common questions
Should the menu have prices?
Yes. A menu without prices makes a guest hesitate, and a hesitating guest often leaves. Clear prices are a courtesy and a trust signal. Hiding them rarely sells more; it just filters out the people who would have come.
Do photos of every dish help or hurt?
A few strong photos of your signature dishes help; a photo of all forty items overwhelms and slows the page. Show the dishes you most want to sell, and let the rest be well-written text.
My menu changes often. Can I update it myself?
Yes, on a proper site you get an editor for the things that move, so raising a price or swapping a special does not mean calling an agency. That is exactly what a menu as real text, rather than a printed image, makes easy.
Is a PDF menu good enough?
No. A PDF is slow to open on a phone, awkward to read, and mostly invisible to Google. A menu built as a real web page is faster, readable, and findable when someone searches for a dish.