How to put your pizzeria menu online (and why not as a PDF)
Put your menu on a web page, not in a PDF, with one item per pie and its own price. A PDF reads badly on a phone, gives search engines almost nothing, and turns one price change into a whole new file. The menu is the page customers came for, so it should be the easiest thing on your site to change.
Why not a PDF
| Web page | ||
|---|---|---|
| On a phone | Pinch and zoom | Reads at any width |
| Changing a price | Export and upload again | Seconds |
| Marking an item sold out | Not really possible | One tap |
| Search engines | Very little extracted | Items and prices readable |
| Screen readers | Often unusable | Works |
| Ordering from it | No | Yes |
The PDF exists because someone already had the menu in a design file for the print shop. That’s a reason to keep a PDF as well, for the takeout menus you hand out. It isn’t a reason to make it the thing a hungry customer taps at 7pm.
Structure it once, properly
Most of the work is deciding on the shape, and it’s the same in every pizzeria:
- Categories: specialty pies, build-your-own, white pies, wings and sides, salads, desserts. Five or six. Someone scrolling on a phone can’t hold more.
- Items: one per pie, with a base price and its ingredients. The ingredients aren’t decoration; they drive your allergen information.
- Options: size, crust, extra toppings, half-and-half. Set up once and attached to many items, so raising the price of the 18-inch is one edit instead of twenty.
Write descriptions for someone deciding
A description earns its place when it answers a question the name doesn’t. Nobody needs a paragraph under the cheese pizza. They might need one under your house special, and they definitely need to know whether the hot honey is actually hot.
Skip the adjectives. “Hand-tossed and lovingly crafted with the finest ingredients” tells a customer nothing that “crushed tomato, whole-milk mozzarella, cup-and-char pepperoni” doesn’t say better.
Allergens belong on the item
Not on a separate page, not in a downloadable chart: on the pie, where the person deciding is looking. The FDA’s 2022 model Food Code asks restaurants to give written notice of the nine major allergens in unpackaged food, and a menu notification counts. Your state or county decides whether that edition applies to you.
Recording allergens per ingredient, not per pie, is what makes this manageable. Switch to a pesto made with cashews instead of pine nuts and you update one line, not every pie it goes on.
What the allergen rules actually require
Photos: all or none
A menu where three pies have photos and eleven don’t makes the eleven look unavailable. Either shoot everything on the same day in the same light, or shoot nothing and keep the page clean and fast. Stock photos of someone else’s pizza are the worst of the three, and customers notice.
Let search engines read it
Marking up the menu as structured data lets a search engine connect your pies and prices to your restaurant instead of guessing from a paragraph. It costs nothing to serve, and it is what puts a pie name in front of someone searching for it nearby.
Keep it true
An online menu is a promise about price and availability. Two habits matter: change the price on the site the same day you change it on the board, and mark things sold out during service, not after. Both are only realistic if editing takes seconds from your phone, which is really the whole argument for everything above.