One tap for your guest.A findable page for everyone else.
A QR code opens a PDF that nobody but the person at the table can read. An NFC menu built properly opens instantly at the table and becomes a page Google and AI assistants can read, quote and recommend. Same tap. Completely different asset.
The tap does two jobs at once
Your guest gets the menu in under a second, with no camera, no focusing, no app and no pinching.
At the same moment, that menu exists as a real web page — every dish in readable text, every price marked up as data, the whole thing crawlable. So while the guest is deciding between the short rib and the branzino, Google is indexing both dishes and an AI assistant somewhere is learning that you serve them.
A PDF cannot do the second job. That is the entire argument on this page, and everything below is the detail underneath it.
Illustration of how a properly built tap menu works.
What is an NFC menu?
An NFC menu is a restaurant menu that opens when a guest taps their phone against a small tag built into a table tent, card or sticker. NFC stands for near field communication, the same technology behind tap-to-pay. There is no app to download and no camera to aim. The phone reads the tag from about an inch away and opens a web address instantly. Whether that address leads to a PDF or to a real indexable web page is the difference between a convenience feature and a search asset.
Most restaurants that moved to digital menus during and after 2020 landed on a QR code pointing at a PDF. It worked well enough for the immediate problem, which was handing fewer objects to guests.
But it quietly created a bigger one. The menu — the single richest description of what your restaurant actually sells — became invisible to every search engine and every AI assistant on earth.
NFC menus vs QR code menus
These are two different questions wearing one label. The first is how the guest gets there. The second is what they arrive at. Only the second one affects whether you get found.
| QR code | NFC tap | |
|---|---|---|
| How it opens | Open camera, aim, focus, wait, tap the banner that appears | Hold phone near the tag. Opens in about a second. |
| In low light | Difficult. Dim dining rooms are the common failure case. | Unaffected. No camera involved. |
| Device support | Essentially universal | Nearly all phones sold in the last several years. Older devices need the QR fallback. |
| Guest familiarity | Very high | High and rising, since tap-to-pay taught the gesture. |
| Cost per table | Effectively free to print | Small per-tag cost |
| Searchable by Google | Only if the destination is a real page. A PDF is not. | Only if the destination is a real page. Same rule. |
| Readable by AI | Same. Depends entirely on the destination. | Same. Depends entirely on the destination. |
The part most vendors will not tell you
NFC versus QR is a guest experience decision. It is not a search decision. Swapping a QR code for an NFC tag while still pointing at the same PDF changes nothing about whether you get found. The tap is smoother and guests appreciate it, but the visibility problem is completely untouched.
The decision that actually matters is what sits at the other end of the link. We build both — tap and scan together, on the same card — because the fallback costs nothing and some guests still prefer the camera.
Why a PDF menu makes your restaurant invisible
Your menu is the most detailed, most specific, most commercially useful description of your restaurant that exists. Locking it in a PDF throws all of that away.
Can Google read a PDF menu?
Poorly, and often not at all. Google can sometimes extract raw text from a PDF, but it cannot understand the structure — which line is a dish, which number is a price, which heading is a section. A photographed or designed menu is worse, because the words are pixels rather than text and there is nothing to extract. AI assistants face the same wall. They cannot tell someone you serve gluten-free gnocchi at $22 if that fact exists only as an image.
Count the phrases you are giving up
A restaurant with forty menu items is sitting on forty specific things people search for. Not "Italian restaurant" — that is one crowded phrase. Forty distinct phrases like cacio e pepe near me, wood fired margherita denver, house made burrata, each with a person attached who already knows exactly what they want to eat.
Dish-level searches carry the highest intent in the entire restaurant category. Somebody searching for a specific dish is usually minutes from a decision and frequently already in the car.
With a text menu you have forty chances to be the answer. With a PDF you have zero, and your competitor down the street with a plain HTML menu wins every single one of them.
What a machine sees
— no readable dishes
— no readable prices
— no structure
MenuItem: Cacio e Pepe
price: 24.00
description: pecorino,
black pepper, house
tonnarelli
suitableForDiet:
VegetarianDiet
Same menu. One is a picture. The other is a set of facts a machine can state out loud with confidence.
The compounding part: once your dishes exist as structured data, they feed everything at once. Google can show your menu in your listing. Voice assistants can answer questions about your prices. AI models can recommend you for a specific craving. And it all runs off one page you update when the menu changes — which you were going to do anyway.
Delivery Commission Bleed Calculator
Third-party delivery commissions run 15% to 30% per order, and the effective cost commonly reaches 30% to 40% once promotions, processing and refunds are counted. Against a typical independent net margin of 3% to 5%, that math is worth seeing written down. Runs entirely in your browser.
What are the apps costing you?
And what moving a share of it in-house would be worth.
Estimate only, from the figures you entered. Actual platform costs vary by contract, tier, city and promotion. This is a planning tool, not financial advice or a projection of results.
Read that last box again
The right-hand number is the one that surprises operators. At a 4% net margin, recovering a dollar of commission is worth the same as roughly twenty-five dollars of new dine-in revenue. Commission you stop paying drops straight to the bottom line, while revenue you add has to carry food cost, labor and overhead first.
That is why owning your own ordering channel is not a marketing project. It is a margin project.
What changes in the dining room
The search argument is the big one, but the operational wins are what your managers will actually notice in week one.
86 an item in ten seconds
The salmon is gone at 7:15. You mark it unavailable once and every table in the room sees it immediately. No more servers apologizing forty times, and no more guests deciding on something they cannot have.
Change prices without reprinting
Food costs move constantly. With printed menus a price change means a print run, a delay, and a stack of obsolete paper. With a live menu it means editing one field.
Run specials that actually get seen
A special written on a chalkboard by the host stand reaches whoever glances at it. A special at the top of the menu everyone opens reaches every guest in the building.
Seasonal menus without waste
Swap the whole menu overnight for a holiday service or a seasonal change, then swap it back. No printing cost and no minimum order quantity forcing you into a long run.
Answer dietary questions once
Tag items as vegetarian, vegan, gluten free or containing common allergens, and let guests filter. It reduces a genuinely stressful category of table conversation and it makes you findable for those searches.
No more sticky laminated menus
A small thing that guests notice. Nobody has ever enjoyed being handed a menu with last night's sauce on the corner.
Where the tags actually go
Placement decides adoption. Tags people cannot find do not get tapped, and tags in the wrong spot get knocked around all night.
- Table tents. The standard. Weighted base, tag inside, QR printed on the reverse as fallback.
- Under-table or table-edge stickers. Discreet, cannot be knocked over, and nothing to store between services.
- Host stand and waiting area. People waiting for a table will read a menu given the chance, and it primes the order.
- Window or front door. The highest-value placement almost nobody uses. Passersby deciding whether to come in can read the whole menu without opening the door.
- Bar rail. Cocktail and bar-food menus separate from the dining room menu.
- Takeout counter and delivery bags. This is how you convert an app customer into a direct one over time.
- Business cards for the owner. Hand someone your entire menu at a chamber event.
Two small things that matter
Tell people it is there. Print "tap or scan" on the card. The gesture is familiar from tap-to-pay, but guests will not try it if nothing indicates the option exists.
Always keep some paper. Not every guest wants a phone menu, and some cannot use one. Keeping a small stack of printed menus behind the host stand costs almost nothing and removes the one real objection to going digital.
The goal is never to force the phone. It is to make the fast path available and to make sure the menu behind it does a second job while nobody is looking.
Accessibility is not optional
A real HTML menu is dramatically more accessible than a PDF. Screen readers can read it, text can be enlarged without pinching, and contrast adapts to the guest's own settings. A PDF of a designed menu fails all three. This is a genuine reason to make the switch that rarely gets mentioned.
From table menu to owning your customers
The menu page is the first step of a longer move: getting out from under marketplace commissions and holding onto the guest relationship yourself.
What is first-party ordering, and why does it matter?
First-party ordering means orders that come through your own website or menu page rather than a delivery marketplace. The difference is not only the commission you avoid. It is that you keep the customer's name, email and order history, which the marketplace never gives you. A restaurant with two thousand marketplace orders a month has no customer list. A restaurant with two hundred direct orders has two hundred people it can reach again for free.
What you lose on a marketplace order
- Margin. 15% to 30% published, commonly 30% to 40% effective once promotions, processing and refunds are counted.
- The customer. No name, no email, no order history. You cannot invite them back.
- Price integrity. Many restaurants inflate marketplace prices to offset commission, which trains guests that you are expensive.
- Brand control. Competitor ads appear alongside your listing inside the app.
- The complaint. When a driver is late, the one-star review lands on you.
The markup trap
Most operators try to solve commission by raising marketplace prices. The arithmetic does not work the way people assume, because the commission is charged on the new higher price too.
To actually match your dining-room margin, the required markup is the commission divided by one minus the commission. At 15% commission that is roughly a 17.6% markup. At 25% it is 33.3%. At 30% commission you need a 42.9% price increase, not 30%.
Marking up is damage control. It makes a bad-margin channel less bad. It does not change the fact that you are renting access to your own customers.
The pattern that works
Use the marketplaces for what they are genuinely good at, which is discovery. Then convert repeat customers to your direct channel over time: an insert in the bag with a tap tag, a better price than the app, a loyalty offer, a card at the takeout counter. You are not trying to leave the apps overnight. You are trying to stop paying 30% on the same customer for the fortieth time.
Your menu page is where that conversion happens, which is why it needs to be genuinely good rather than merely functional.
Dietary tags do more than you would expect
Marking items as vegetarian, vegan, gluten free, dairy free or containing common allergens takes an afternoon and pays back in three separate ways.
In the dining room, it removes one of the most stressful exchanges in service. A guest with celiac disease currently has to interrogate a server who may or may not know the answer, in front of a table waiting to order. A filterable menu answers it privately in ten seconds and the guest relaxes.
In search, "gluten free" plus your city is a high-intent phrase with far less competition than your cuisine plus your city. The person searching it has a hard requirement, limited options, and usually brings a table of three or four people with them.
In AI answers, dietary constraints appear constantly in conversational queries. "Somewhere my vegan sister can actually eat" is a real question people ask assistants. If those words are not attached to your dishes as data, you cannot be the answer.
Worth tagging
- Vegetarian and vegan
- Gluten free, and separately, made without gluten in a shared kitchen
- Dairy free
- Nut allergens
- Shellfish
- Spice level
- Kid-friendly items
- Available for takeout or delivery
One honesty note
Distinguish between "gluten free" and "made without gluten ingredients in a kitchen that also handles gluten." These are different claims with genuinely different stakes for someone with celiac disease. Overstating it is a real safety issue and a real liability issue. Say precisely what is true.
What to watch after you launch
A menu page produces data a paper menu never could. Here is what is worth reading and what it tells you.
Menu views per service
Tells you adoption. If views are far below your cover count, the tags are placed badly or the floor is not mentioning them. This is usually a briefing problem, not a technology problem.
Most-viewed items
Which dishes people look at hardest before ordering. Sometimes it matches your sales mix and sometimes it exposes a dish people consider and then talk themselves out of, which is a description or price problem worth fixing.
Time on the menu
Very long dwell times can mean the menu is hard to navigate rather than fascinating. Very short ones can mean guests bounced to paper. Both are worth a look at the layout.
Dietary filter usage
Reveals demand you may be underserving. If a meaningful share of guests filter for gluten free every night, that is a menu development signal and a content signal at the same time.
Dish-level search impressions
Once indexed, your Google Search Console will start showing which dish phrases surface your menu. This is the clearest proof the visibility argument on this page is working.
Menu link clicks from Google
Available in your Google Business Profile insights. It tells you how many people looked at your menu before ever arriving, which is a strong leading indicator of covers.
A fair expectation: the operational benefits show up in week one. The search benefits take longer, because Google needs to crawl and index the page and AI models refresh on their own schedules. Give it two to three months before judging the visibility side, and compare against the same period last year rather than last month, since restaurants are seasonal.
Four things people get wrong about digital menus
"Digital menus are a pandemic leftover"
The contactless argument was the reason they arrived, and it is genuinely no longer the point. The reasons that hold up are operational and commercial: instant price changes, live availability, dietary filtering, accessibility, and a menu that search engines and AI assistants can actually read. Plenty of restaurants went back to paper because they only ever saw the hygiene argument. They gave up the other five without noticing.
"A digital menu means an app"
No app, for you or your guests. A tap opens a web page in the phone's existing browser. Any vendor asking your guests to download something has designed the wrong product, because the download is where you lose most of them and it buys the guest nothing.
"We already have QR codes, so we're covered"
This is the most common and most costly misunderstanding on this page. The code is just a doorway. If it opens a PDF, your menu is still invisible to every search engine and AI assistant, and you have all the downsides of a digital menu with none of the visibility upside. What matters is the destination.
"Guests hate them"
Some do, and that is worth respecting rather than arguing with. The complaints are almost always about bad implementations: slow pages, pinch-to-zoom PDFs, forced account creation, upsell popups, menus that require signal your dining room does not have. A fast text menu that loads in a second and asks nothing of the guest draws very few complaints. Keep paper available for the people who want it and the objection mostly disappears.
The objections we hear, answered honestly
Some of these have good answers. One of them we will simply concede.
"Do all phones support NFC?"
Nearly all phones sold in recent years read NFC tags natively, without an app, from the lock screen. Older devices and a small number of budget models do not. That is exactly why every card we build carries a QR code on the reverse. Nobody gets stuck.
"Will older guests know what to do?"
Some will not, and that is fine. Print "tap or scan" on the card, keep printed menus behind the host stand, and let servers offer one without being asked. Adoption climbs on its own because the gesture is the same one people already use to pay.
"Is it secure? Can a tag be tampered with?"
NFC tags can be locked read-only at programming, which prevents anyone rewriting the destination. We lock every tag we ship. An unlocked tag is a real risk and it is worth asking any vendor directly whether theirs are locked.
"Does this drain the guest's battery?"
No. The tag itself has no battery and draws no power. The phone's NFC reader uses a negligible amount, and the page it opens is a lightweight menu, not an app.
"Won't people just look at their phones all dinner?"
This is the concession. Handing guests a reason to pick up the phone is a real cost, and some rooms should weigh it seriously. Our answer is a menu that loads fast, has no ads, no account, no upsell popups and nothing to scroll past — so the phone goes back down in ninety seconds. But if your concept depends on a phone-free room, that is a legitimate reason to stay on paper, and we will tell you so.
"What if the internet goes down?"
Guests are usually on cellular data rather than your wifi, so a router outage generally does not affect them. For total outages, the printed menus behind the host stand are the answer. This is the same contingency you already need for your POS.
LinkRestaurants.com
Our NFC and QR menu network. Every menu on it is a real, indexable web page — not a PDF, not an image, not a page behind a login.
That structure is the point. Each menu carries proper Menu, MenuSection and MenuItem markup, so every dish is a discrete object with a name, a description, a price and dietary properties. Search engines index them. AI assistants can quote them.
And because the menus sit on a network rather than in isolation, each one benefits from the others. A guest looking at one restaurant's menu is on a site that also carries local restaurant content, which builds the kind of topical authority a single standalone page struggles to earn alone.
Your menu also stays yours. You get the page, the traffic and the customer. There is no marketplace taking a cut of an order placed from it.
See LinkRestaurantsWhat each menu page includes
- Every dish as readable text with its own price.
- Menu, MenuSection and MenuItem structured data.
- Dietary tags and guest-facing filters.
- Your hours, address and phone as structured data.
- One-tap calling and directions.
- Instant availability toggles for 86'd items.
- Mobile-first layout that loads in about a second.
- Locked NFC tags plus printed QR fallback.
Get listed where people are already looking
A menu page works harder when the restaurant around it is also being found. We place clients on LocalFoodNearMe.com, BestRestaurantDenver.com, ColoradoWhatsUp.com and DenverColoradoThingsToDo.com.
How to set up NFC menus in your restaurant
Five steps. Most restaurants are live inside two weeks, and the slow part is almost always waiting on menu copy.
Get the menu into text
Not a scan. Actual typed text with sections, item names, descriptions and prices. If your menu currently exists only as a designed PDF or a photograph, this is the real work of the project and it is worth doing carefully. Write descriptions the way guests describe dishes, not the way a chef writes a spec.
Build the page and mark it up
The menu becomes a mobile-first page with structured data behind every item. Dietary tags get applied. Hours, address and phone are added as structured data so the page can answer questions on its own.
Program and lock the tags
Each tag gets written with your menu address and then locked read-only so nobody can change the destination. QR codes get generated for the same address and printed on the reverse of every card.
Place them and brief the floor
Tables, host stand, bar, window, takeout counter. Then a five-minute staff briefing: where the tags are, how to explain the tap, and that printed menus are available for anyone who wants one. Server buy-in decides adoption more than anything else.
Link it everywhere and let it get indexed
Add the menu link to your Google Business Profile, your website, your Apple listing and your social profiles. This is the step that converts the menu from a table convenience into a search asset, and it is the one most restaurants skip.
NFC menu questions
What is an NFC menu?
An NFC menu opens when a guest taps their phone against a small tag built into a table tent, card or sticker. NFC stands for near field communication, the same technology behind tap-to-pay. There is no app to download and no camera to aim — the phone reads the tag from about an inch away and opens a web page instantly.
Do guests need an app to use an NFC menu?
No. Nearly all phones sold in recent years read NFC tags natively, straight from the lock screen, with no app and often no unlocking. The phone shows a notification with the menu link and one tap opens it. This is the same mechanism as tap-to-pay, which is why most guests recognize the gesture immediately.
Are NFC menus better than QR codes?
For the guest, yes — a tap is faster than aiming a camera, and it works in a dim dining room where QR scanning often struggles. For search visibility, the two are identical, because what matters is the destination rather than how you get there. An NFC tag pointing at a PDF is just as invisible to Google as a QR code pointing at the same PDF. We build both on one card so guests can use whichever they prefer.
Can Google read a PDF menu?
Poorly, and often not at all. Google can sometimes extract raw text from a PDF but cannot reliably understand the structure — which line is a dish, which number is a price, which heading is a section. A photographed or fully designed menu is worse, because the words are pixels rather than text. AI assistants hit the same wall and cannot quote prices or dishes they cannot parse.
How much do NFC menus cost?
The tags themselves are inexpensive per table. The real cost is in getting your menu into properly structured text with markup, which is a one-time build that varies with menu size and how the menu currently exists. A restaurant with a typed menu in a document is a much smaller project than one with only a designed PDF. We scope it per restaurant rather than quoting a package price.
Can NFC tags be tampered with?
An unlocked tag can be rewritten by anyone with a phone, which is a genuine risk. Tags can be locked read-only at the time of programming, which permanently prevents the destination from being changed. We lock every tag we ship, and we would encourage asking any vendor directly whether theirs are locked before buying.
Can I update prices without reprinting anything?
Yes. That is one of the strongest day-to-day arguments for a live menu. Price changes, seasonal swaps and marking an item unavailable all happen by editing the page, and every table sees the change immediately. The tags themselves never need reprogramming because they point at an address, not at content.
Do I still need printed menus?
Keep a small stack. Some guests prefer paper, some cannot comfortably use a phone menu, and it covers you during any outage. Keeping ten printed menus behind the host stand costs almost nothing and removes the only real objection to going digital. The goal is to offer a fast path, not to force one.
Will an NFC menu help my restaurant show up on Google?
Only if the menu is a real indexable page rather than a PDF. When it is, every dish becomes a phrase you can be found for, and dish-level searches carry the highest intent in the category. Adding the menu link to your Google Business Profile is what connects the two, and it is the step most restaurants skip after building the page.
Do NFC menus work without wifi?
Guests are typically on cellular data rather than your restaurant's wifi, so your router going down usually does not affect them. The tag itself requires no power or connection of any kind. For a full connectivity outage in an area with poor cell service, the printed menus behind the host stand cover you — the same contingency you already keep for your POS.
Let's get your menu out of that PDF
Send us your current menu and we will tell you what it would take to convert it, what it would look like as a real page, and roughly how many dish-level searches you are currently invisible for.
- We count the dish phrases your PDF is hiding.
- We check whether your Google listing links a menu at all.
- We test whether AI assistants can describe what you serve.
- You get the findings whether or not you hire us.
If your menu is already text and already marked up, we will say so and you will have spent nothing.
Free menu visibility check
Usually back within one business day.