Use a temporary website announcement banner when a short-term service change could affect a guest’s next visit or order, and the guest needs to know before acting. Examples include an unexpected dining room closure, a temporary pickup entrance, or a change to ordering hours. Skip the banner for routine information that already belongs on your hours, menu, or ordering page.
A banner should answer three questions quickly: What changed? Who is affected? What should the guest do next? It also needs an owner and an end time. An outdated announcement can create nearly as much confusion as no announcement at all.
Choose service changes that need a banner
A banner earns its space when the change is temporary, matters to a current guest decision, and needs attention across more than one page. A guest may land directly on the menu or ordering page rather than the homepage, so a notice limited to the homepage may be easy to miss.
Start with the facts from the person responsible for the affected service. The shift manager can confirm dining room access and hours. The kitchen lead can confirm whether a menu change affects all orders or just a few items. The person managing online orders can check what guests will see and whether ordering has actually been adjusted.
Ask these questions before publishing:
- What is different? Name the service, location, entrance, or hours affected.
- When does it apply? Get a start time, an expected end time, and the local time zone if guests may be elsewhere.
- Who is affected? Separate dine-in guests from pickup or delivery customers when the change does not apply to everyone.
- What can guests do? Identify a useful page, ordering option, phone number, or other next step that staff can support.
- Who can confirm it is over? Assign a person, not just a department.
A temporary shortage of one side dish usually belongs on the menu or ordering screen, not in a notice on every page. A short-term closure of the pickup entrance may deserve a banner because it changes where guests need to go. For a permanent closure, update the restaurant’s core website information rather than relying on a temporary cross-site notice.
In a hypothetical example, a restaurant expects its front entrance to be unavailable from Tuesday through Thursday while the entryway is repaired. Dine-in and pickup remain open through a side door. A banner is appropriate because guests need the new entrance before arriving. The manager confirms the dates and door location; the website owner publishes the message and sets a reminder to check it Thursday.
Write a short message with a clear action
Lead with the change, not the reason behind it. Guests deciding where to go do not need a history of the repair. They need enough information to avoid the closed entrance and find the open one.
For the entrance example, the message could read: “Tuesday–Thursday: Please use the Oak Street side entrance for dine-in and pickup. See directions.” Link “See directions” to a page that actually identifies that entrance. If no such page exists, give the usable direction in the message rather than sending guests to a generic homepage.
The trade-off is space. A single sentence is easier to scan, especially on a phone, but it must not leave out a detail that changes the guest’s decision. If the side entrance has limited access, for example, include a practical way to get assistance rather than assuming every guest can use it. Ask staff what questions they expect and revise the message before it goes live.
Make the action specific. “View pickup hours” is more useful than “Learn more” when pickup hours have changed. A link to online ordering is useful only if ordering is available and the destination reflects the temporary service. A banner does not itself change the hours, menu, or fulfillment options in an ordering system. Update those separately where needed.
Use a full date when a weekday could become ambiguous, and include an end time when the change ends partway through the day. Avoid promises such as “back to normal tomorrow” until the responsible person has confirmed them. If the end is uncertain, say when guests can expect the next update instead.
Set a removal time and accountable owner
Plan the banner’s removal before publishing it. Record the person who can edit the site, the person who can confirm the service has resumed, and the time they will check. They may be the same person, but both jobs need to be covered if someone is off shift.
For the entrance example, the website owner could schedule a Thursday afternoon check with the shift manager. If the entrance is open, remove the banner and check that the regular directions are accurate. If the repair continues, replace the dates with confirmed information or a clear next-update time. Do not leave an expired date visible while waiting for certainty.
The table below is a publication and expiry worksheet using that hypothetical entrance change. It shows what to decide and who should act; adapt the names and timing to your own shift schedule.
| Step | Example decision | Owner | Check |
|---|---|---|---|
| Confirm | Side entrance serves dine-in and pickup Tuesday–Thursday | Shift manager | Confirm access and expected repair timing |
| Publish | Show the short notice with a directions link | Website owner | Open the link and check affected pages |
| Review | Check repair status Thursday afternoon | Shift manager | Tell the website owner whether access has changed |
| Remove or revise | Remove if the front entrance is open; otherwise update the notice | Website owner | Reload pages and confirm the current message |
A scheduled expiry can help if your website tool offers it, but a reminder still matters. An automatic removal may happen before a repair is complete; a notice left in place may direct guests away from an entrance that has reopened. Ask your provider how scheduling, editing, and removal work, including who has permission to make changes outside normal office hours.
Keep a fallback ready. If the usual editor is unavailable, identify another authorized person and the steps needed to reach the site controls. For an urgent change, also make sure front-of-house staff know the message so they can give callers the same directions.
Check the banner on mobile before and after publishing
A notice is useful only if guests can read it without losing access to the rest of the site. Preview it on a phone-sized screen, then check the published version on a real phone if possible. Use a second screen size when available; a line that fits on one device can wrap into several lines on another.
Before publishing, use a preview or other safe test environment where available. This is a simulated check, not a live service pilot. Do not place a real order, send a guest message, take a payment, or dispatch a courier just to test the banner.
- Read the whole message. Check that the change, affected guests, dates, and action are understandable without opening another page.
- Check contrast and size. Make sure text is readable against its background and is not cramped at normal phone settings.
- Inspect the page underneath. The banner should not cover navigation, menu details, an ordering button, or other controls guests need.
- Open the action link. Confirm it goes to the relevant information. Stop short of any real transaction or message.
- Check affected pages. Look at the homepage and other pages where guests may enter, including the menu and ordering entry point. Do not assume a notice appears everywhere.
- Practice removal. In a preview or safe test environment, check how an authorized editor can hide or revise the notice.
After publication, reopen the live site and verify the actual message and link. If the site uses separate tools for ordering and the main website, inspect both guest paths; a notice on one may not appear on the other. Fix any mismatch in the relevant tool rather than relying on the banner to explain an incorrect ordering screen.
When comparing a new setup, ask for a demonstration of banner placement, mobile preview, permissions, and expiry controls. The restaurant website builder comparison can help frame the wider buying decision. Also check who controls the domain and who can make urgent edits; the domain ownership guide covers questions worth asking before a change of provider.
Use the checklist on your current site first. If you need a different setup, ask Fleksa about its restaurant website, the banner controls available for your situation, and current US availability.
Frequently asked questions
Should a restaurant banner appear on every page?
Use broad placement when the change affects guests across the site. For a narrow change, a notice on the relevant menu or ordering page may be clearer. Check the pages guests actually use rather than assuming placement.
What if there is no confirmed end date?
State what is known and when the restaurant expects to provide an update. Assign someone to review the notice at that time, even if the underlying issue is not yet resolved.
Can a banner replace an update to ordering hours?
No. A banner informs guests, but the ordering setup must also reflect the service you can fulfill. Check the ordering path separately and correct its hours or options where needed.
