Midtown Atlanta Website Design Services

PDF, photo or real text? How each menu format holds up on a phone

A menu typed into the page as real text beats a PDF or a photo on almost every count. It reads on a small screen, updates in minutes and can be found by search.

We see the PDF menu more than any other kind, and we get why it sticks around. It's easy. The designer already made one for the printer, so it gets uploaded as is. The trouble shows up on a phone, where a guest has to open a file, wait, then pinch and drag around a page built for paper. Plenty of people give up and pick the place next door.

A text menu takes a bit more work once, then saves time every week after. We'd build it as a normal page with sections for each part of the meal, prices beside each dish and a short line under anything whose name doesn't explain itself. You can still keep a printable PDF for catering or large parties. It just shouldn't be the main event.

There's a quieter benefit too. Once your dishes are words on a page, search engines can match them to what people type. Someone searching for shrimp and grits in Midtown has a chance of finding your page, because the dish name is right there in text. Nobody finds you through a picture of a menu.

A menu page rewritten so a hungry stranger can order in a minute

Dish names get people curious, and a short plain line tells them what they'll actually eat. Put prices beside every item and group the menu the way guests order.

Look at what didn't change. The dish names stayed fun, because that's part of the place's personality. We only added the plain line underneath, so a stranger isn't left guessing. Guests who know you skim past it, and first-timers finally know what they're ordering.

Grouping matters more than people think. A guest looking at 10:40 p.m. only cares what the kitchen is still making. If late-night dishes sit in their own section, with the hours right at the top, they can decide in seconds. Mixed together, the menu turns into homework.

We'd write the plain lines with your chef, since they know what matters on each plate. Keep them short, around eight to twelve words. Our only rule is that a guest should be able to picture the dish without asking the server.

• Every dish has a name, a short plain description and a price
• Sections match the way people order, like starters, mains and late night
• Dietary marks are explained once, near the top of the page
• Nothing important lives only inside a photo
• The date the menu was last updated sits quietly at the bottom
• A printable version exists for groups, linked below the real menu
• Prices written as plain numbers that scan fast, like 14 instead of 14.00

Keep one menu address all year while the dishes change

Your menu page should live at the same web address through every season. New dishes go onto that page, so saved links, Google and your profile never point at an old menu.

1. Pick one plain address and keep it Something like yoursite.com/menu works. Avoid names with a season or year in them, because they go stale the day the menu changes.
2. Update the page itself each season Swap dishes on the same page. The address stays put, so every link anyone has saved still lands on today's food.
3. Give special menus their own lasting pages Brunch, happy hour or a private dining menu can each have a page. Keep those addresses steady too.
4. Point your Google profile at the menu page Use the same address in your profile's menu link, so a guest on Maps sees the same menu as a guest on your site.
5. Redirect anything you retire If an old seasonal page has to go, send it to the current menu with a permanent redirect instead of letting it break.

We've seen menu links multiply on plenty of sites: menu-2023, menu-fall, new-menu, menu-final. Each one gets shared, bookmarked and linked from somewhere, then quietly forgotten. A year later, a guest clicks an old link and sees prices from two springs ago. They either show up expecting the old price or skip you entirely.

One steady address fixes that for good. It's also easier on search engines, which learn that one page is your menu and keep coming back to it. We'd set this up at launch, then leave it alone for the life of the site.

If you already have a pile of old menu pages, we don't delete them in a hurry. We'd list every one, check which ones still get visits or links, and point each at the current menu. It's an hour of tidy work that stops a lot of wrong-price arguments.

When the kitchen closes before the bar does

Late Midtown nights need two sets of hours. Show when the kitchen stops and when the bar closes, on your site and your Google profile, so nobody walks in hungry at 11.

Picture a bar that pours until 1 but stops cooking at 10. It has two honest answers to the question of whether it's open. If the website only shows 1 a.m., a group coming out of a late show walks in expecting dinner. They get a bowl of nuts and a shrug. That's the kind of night that ends up in a one-star post, and it wasn't really anyone's fault.

We'd put both times side by side on the site, in plain words like kitchen until 10 and bar until 1. Then we'd make sure the Google profile says the same thing, using its separate kitchen hours. When those two places agree, most of the confusion disappears before it starts.

We'd also think about the guest reading at 9:45. A small line such as 'last food orders at 9:45' does more than the closing time alone. It tells a hungry group to hurry, and it spares your kitchen the awkward talk at the pass when the tickets stop.

• Main hours and kitchen hours shown together, near the top of the home page
• The same two times on the contact page and the menu page
• A late-night menu section that says when it starts and stops
• Kitchen hours added to your Google profile under More hours
• Holiday changes posted on the site and the profile on the same day

Check the city's rules before a drink special goes on the site

Atlanta has specific rules on alcohol discounts, and they've been changing. Confirm what's allowed today before any happy hour line goes on your website, menu or Google profile.

We're a marketing agency, so we won't tell you what your license allows. What we can tell you is that a website makes a promise in public, all day, to anyone who reads it. If a special on your site doesn't match the rules, that line is sitting there as a record. It's worth a quick check with the city or your attorney before it goes live.

Once you know what's allowed, write it plainly. Say which drinks, which days and which hours, and keep the wording on your site, menu and profile identical. When the special ends, take it down everywhere on the same day. A happy hour that lives on in an old post is how a guest ends up arguing with your bartender.

If you do run a special, we'd give it its own small section on the menu page instead of a banner that covers the screen. Guests who want it will find it. Guests who came for dinner won't have to close a pop-up to see the food.

Allergen and dietary notes that don't overpromise

Mark what's in each dish in plain words, and be careful with the word free. A kitchen that shares fryers can say what it avoids without guaranteeing what it can't.

• Name the big allergens in the dish description, like nuts, shellfish or dairy
• Use simple marks for vegetarian or vegan dishes, with a key at the top
• Say 'made without gluten' only if that's true, and add a line about shared equipment
• Tell guests to mention allergies to their server, every time
• Keep the notes updated when a recipe changes, since an old note is worse than none

Dietary notes do two jobs. They help the guest with a real allergy decide whether to come in at all, and they save your servers from answering the same question fifty times a night. A clear note on the website means the conversation at the table starts from facts.

We'd sit with your chef for fifteen minutes and go dish by dish. It's quicker than it sounds, and it usually turns up a couple of surprises, like a sauce with anchovy in it that nobody thought to mention. Those are exactly the details a careful guest is hunting for.

We'd also put a short note at the top of the menu that invites questions. Something like 'Tell us about any allergy and we'll walk you through the menu' sets a friendly tone. It tells guests you'd rather hear about it than have them guess.

A moody bar site that's still readable at 11 p.m.

Dark backgrounds and thin gray fonts look great on a big design screen and fade out on a phone on the sidewalk. Check contrast before you fall for a mockup.

1. Test the colors with a free checker Put your text color and background color into any contrast checker. If body text falls under 4.5 to 1, it needs to change.
2. Turn your phone brightness down Read the menu and hours at low brightness, the way many people keep their phones at night. Anything you squint at, a guest will skip.
3. Step outside Read the site again under a streetlight and again in bright sun. Glare hurts thin fonts most.
4. Check the buttons too A dark button on a dark page can vanish. The booking button should be the easiest thing on the screen to spot.
5. Keep the mood in the photos Let your photos carry the candlelit feel, and keep the words crisp and easy to read.

We love a dark, moody bar site as much as anyone. Plenty of Midtown spots have a look worth showing off. But the words still have to work for the guest standing outside the theater with a dim phone. Good contrast doesn't have to mean bright white pages. Warm cream text on a deep charcoal background can pass the test and still feel like your room.

There's a second reason to care. Guests with low vision rely on strong contrast to read at all. A site that meets the guideline is easier for everyone, and it avoids shutting out people who'd happily spend an evening with you.

We'd check contrast on every page before launch, and again whenever someone adds a new color. It's a two-minute habit, and it catches the pretty gray footer text that tired eyes can't read at night.

House rules, written down so your host can stop repeating them

Late arrivals, cancellations, dress code and kids all come up on show nights. Put your real answers on one short page, and link it from the booking button.

• How long you'll hold a table if the guests are running late
• Whether there's a cancellation window or a fee for no-shows
• Dress code, even if the honest answer is 'come as you are'
• Whether kids are welcome, and until what time
• How to reach you if a train or a show runs long
• Which MARTA stop is closest and where people usually park

These answers already exist in your host's head. Putting them on the site means the host stops repeating them, and guests stop worrying on the way over. A calm, friendly page also sets expectations, so a late party knows what to expect before they sprint up Peachtree.

We'd write it in your voice and keep it short, a screen or so on a phone. Rules sound harsh in a list, so we'd give each one a reason. 'We hold tables for fifteen minutes because we're usually full on show nights' reads a lot kinder than 'Tables released after 15 minutes.'

We'd link this page from the booking button, the confirmation email and the footer. Guests who read it before they come tend to arrive on time and a little calmer. Your host will notice the difference on the first busy Friday.

A private dining form your manager can answer in one reply

Office parties and pre-show groups ask the same things every time. A short form that collects the right details up front saves three rounds of email.

• Date and the time the group needs to leave, if they're heading to a show
• Number of guests, with a note if it might change
• Seated dinner, standing reception or just a block of tables
• Rough budget per person, as a range with a 'not sure' option
• Any allergies or dietary needs in the group
• Name, phone and email for the person organizing

Should the form show prices for private dining?

We'd show a starting range or a sample menu with prices if you're comfortable. Organizers are often spending a company card and need a number for their boss. A range saves them an email and saves you a tour for a group that was never going to fit the budget.

What should happen after someone hits send?

The confirmation screen should say who will reply and roughly when, in your real words. Then the details should land in one inbox that a manager actually checks every day.

Is a form better than just listing a phone number?

Offer both. Some organizers want to talk it through, and others are filling this out at 11 p.m. after the kids are asleep. The form catches the second group without anyone playing phone tag.

How many questions is too many?

If it takes more than a minute on a phone, it's too long. We'd keep the six fields above and let the manager ask the rest on the reply. Every extra box costs you a few organizers who give up halfway.

The 'time you need to leave' field is our favorite. Groups heading to a performance at the Woodruff campus or anywhere nearby have a hard stop. If your manager knows that on day one, they can suggest a set menu that fits the window. That one field turns a vague inquiry into a plan, and it shows the organizer you've done this before.

We'd test the form ourselves before launch by sending a fake party of twelve through it. Then we'd check that the email arrives, that it's readable on the manager's phone and that hitting reply goes straight back to the organizer's own email.

Who changes the site when the fish runs out at 4 p.m.?

Decide now who can make each kind of change and how fast. A site that only one busy person can edit goes stale within a month.

On a restaurant site we build, a manager should be able to change a dish or an hour from a phone in a couple of minutes. Nobody should need to email a designer to take the salmon off for the night. Bigger changes, like a new menu section or a redesigned home page, are where we'd still step in.

We'd also mark the booking button, the call button and the private dining form as key events in your analytics. After the first month, you'll see which pages send people to those actions and which ones just collect visits. That tells us where the next round of changes should go.

None of this needs a big team. Most of the small places we'd work with have an owner, a chef and a manager who already juggle a dozen jobs. The plan just makes sure each change has a name next to it, so the site never waits on whoever happens to be on vacation.