Hours, the menu, and one way to get the food.

The first screen

What is cooking, when the door is open, and the next step: call, reserve, or order. That is the screen. The story of the family can come after, if you want it. It cannot come instead. A menu that is a PDF with no date is a guess. If the menu changes, the page has to change, or the page should say how to see today's menu. Photos are the plates you serve and the room you have. A photo of a dish you no longer make is an hours problem in picture form.

Phone numbers on the page have to be links. Half the people reading it are deciding whether to tap. If you take reservations through a tool, the button should be that tool, and the listing's website link should land on the same screen. Do not make them hunt from the homepage to a buried reservations tab.

The listing fails in the parking lot

Hours are the failure I would look at first. Holiday weeks, the day you are closed, the hour the kitchen stops even though the door is still unlocked. The listing, the door, and the website have to match. A person who trusted the listing and found you closed does not give the website a second chance to explain.

Category is the cuisine and the format you are, not every food word that has search volume. Photos on the listing should be recent enough that the room still looks like that. Services or menu highlights should be food you can make today. A post is optional. It is not a substitute for correct hours.

No invented crowd

I will not put a review count, a star average, or a ranking on a page, and I will not invent one for yours. If reviews are public on the listing, they are already public. They do not need a slogan next to them. Cost context for a restaurant site is the restaurant cost guide. The notes on where software helps a kitchen or a front door are the restaurant playbook and the cafe playbook. The build is the websites service.

The check before any of that is the free website and Google audit: the page you send, and the public listing for the name and city. One reply within one business day. No password, and no promise of more covers. Filling the profile in is the separate $650 setup. If the restaurant is on Dempster, Milwaukee, or near Old Orchard, the village pages say why those streets behave differently: Morton Grove, Niles, Skokie.

Straight answers

Common questions

What is the first job of a restaurant website?

Say what you serve, when you are open, and how to get a table or an order. That belongs in the first screen. A PDF from a past menu, with no date, is a page the audit would flag because a customer cannot tell if it is still true.

What breaks when the Google hours and the door disagree?

The person who checked the listing in the parking lot finds a locked door or a kitchen that has already stopped. They do not call the number on a website that said something else. Hours on the listing, the door, and the site have to be the same, including the day you close.

Do you write a review count or a ranking claim on these pages?

No. A review count that is not on the public listing, a star average you typed in by hand, or a claim about where Google places you does not belong here or on the restaurant site I would build.

How do I get the free look?

Use the free website and Google audit. Send the site, the restaurant name, and the city. I reply once within one business day about that page and the public listing. Phone and the call-consent box are optional. The audit does not wait on either one.

Ready? Send the page and the business name through the free website and Google audit, or text them to (847) 387-0244.