This is a small-restaurant content-planning framework, not a recipe for a platform algorithm or a guarantee of sales. Start with questions real customers ask the shop. Choose a post format that staff can keep accurate when a dish, price or opening time changes. A good photograph can invite attention, but it cannot replace basic information the customer needs before visiting or contacting the restaurant.
Let each post answer one main question
Do not squeeze every dish, map, opening hour and restaurant story into a single graphic. Pick a focus: What is available today? Is a dish for one person or sharing? Where can someone read the full menu? Give only the supporting details needed for that question. A dish post can show its current name, real photograph, price and selling unit. A shop-information post can show verified hours and contact details. A response post can answer a repeated question about an option the kitchen actually provides.
Make the image readable on a phone
Use a food photograph the restaurant owns or has permission to use; do not publish a customer's image without appropriate permission. Leave room around the dish name and price. Check type size and cropping on the actual channel before posting, since a square design may lose text in another feed. If the picture is illustrative rather than the normal portion, label it. Do not enlarge a plate or add ingredients until it looks unlike the version customers will receive. Put key information in the post text as well, so a reader need not decipher tiny lettering inside an image.
Link to a menu that matches the post
If a post advertises a dish but opens an out-of-date menu, the customer must ask staff all over again. Compare the name, photo, options and current price on the destination page before sharing its link. A QR or direct menu link should lead to a viewing page, not imply that the customer can check out online. The online menu page explains the display format, and material examples help a shop pick a layout appropriate to its information.
Observe questions instead of claiming a sales effect
Keep a simple record of post date, topic, destination link and the questions received afterward. Did customers find the menu? Did fewer people need to ask whether the displayed price was per plate or per set? Separate what staff observed from what they hoped would happen. View counts and likes alone do not establish that a particular post increased restaurant sales. The team can use this record to improve clarity without inventing a return-on-investment statistic.
Keep a schedule the shop can maintain
One row per post can name the reviewer, last check date and source menu link. Start with a frequency the small team can sustain; there is no need to post every day. When a price, menu item or opening hour changes, correct the destination page and check still-active posts before producing more artwork. For the source information, use the menu-planning guide; for shop listing details, see the Google Business Profile checklist.