Lorixen.
EN

Announcement bars: when a site-wide notice actually helps

Short answer: An announcement bar earns its place when it carries one time-sensitive message that changes what a visitor does today, such as a closure, a delivery cut-off or a booking change. It stops working when it becomes permanent wallpaper. Reserve space for it so the page doesn't jump, keep it short enough for a phone, and give it an end date before you switch it on.

That thin strip across the top of a site is one of the cheapest pieces of real estate you have, and one of the most abused. Below is a working checklist for deciding whether you need one, what to put in it and how to build it so it doesn't hurt the rest of the page.

Before you switch it on: the decision checks

Run through these first. If you can't tick at least the first two, the message probably belongs somewhere else, such as the contact page, the checkout or an email.

  • Does the message change behaviour this week? "Last orders for pre-Christmas delivery: Thursday 2pm" changes behaviour. "We value our customers" doesn't.
  • Does it apply to most visitors? A notice that only matters to trade accounts belongs in the trade area, not on every page.
  • Is there a clear end date? Write it down. A bar with no end date becomes invisible within weeks because returning visitors learn to skip it.
  • Is it the only bar? Two stacked strips, plus a cookie notice, plus a sticky header, can eat a third of a phone screen before any content appears.
  • Would a page element do the job better? Opening-hours changes, for example, also need updating on your Google Business Profile and contact page; the bar is a pointer, not the record.

What belongs in the bar (and what doesn't)

Good candidates share one trait: they are short-lived and specific.

  • Temporary closures, reduced hours or a move to a new address
  • Delivery or collection deadlines around holidays
  • A changed phone number or booking system, with a link to the new route
  • A genuine sale with a stated end date
  • Disruption notices, for example "Card machine down today, cash or bank transfer only"

Weak candidates usually fail on the "changes behaviour" test:

  • Generic welcome lines or slogans
  • Newsletter sign-up prompts that run all year
  • Awards or press mentions (these belong in the page body where they can be read properly)
  • Several messages rotating every few seconds, which few people read and which can be hard for some visitors to follow

Writing the message: a quick checklist

  • One sentence, one link. If you need two sentences, the detail goes on a page the link points to.
  • Lead with the fact. "Closed 24–27 December" beats "Please note that over the festive period we will be…"
  • Use a real date, not "this weekend". Visitors arriving from a search result or an old social post don't share your sense of "this weekend".
  • Make the link text say where it goes. "See holiday delivery dates" rather than "Click here".
  • Check it at 360 pixels wide. If it wraps onto three lines on a small phone, cut words.

Building it without breaking the page

This is where many bars quietly cause harm. The common mistake is a script that inserts the bar after the page has started to render, which pushes everything down just as the visitor is about to tap something.

Reserve the space

Google's web.dev guidance on Cumulative Layout Shift (CLS) says sites should aim for a score of 0.1 or less, measured at the 75th percentile of page loads, and that values above 0.25 are poor. It also explains that layout shifts in response to a user's own action, such as tapping a button, are generally fine, but shifts the user didn't trigger are the problem. A bar injected late by a marketing script is exactly that kind of unexpected shift.

The fix is simple in principle: render the bar in the page's HTML from the start, or reserve its height in the layout so nothing moves when it appears. If your theme or site builder offers a native announcement bar setting, that is usually safer than a third-party pop-up tool bolted on afterwards.

Dismissal that sticks

If visitors can close the bar, remember that choice, typically with a small cookie or local storage flag, so it doesn't reappear on every page. Decide what "remember" means: for the session, or until the message changes. When you publish a new message, it should show again even to people who dismissed the old one. Check your rules where you operate on storing such preferences.

Accessibility basics

  • Make sure the close button is a real button with an accessible name such as "Dismiss announcement", reachable by keyboard.
  • Keep text contrast readable against the bar's background colour; brand colours on a coloured strip often fail.
  • Avoid auto-rotating or scrolling text. If you must change the message dynamically, MDN's documentation on aria-live explains that a "polite" live region lets assistive technology announce updates without interrupting the user, while "assertive" interrupts immediately; for a site notice, interrupting is rarely justified, and a static bar needs no live region at all.

Placement and stacking

Put the bar above the header rather than inside a sticky header that follows the user down the page. A sticky bar plus sticky header permanently shrinks the reading area on mobile. If you have a cookie banner, check that the two don't overlap on small screens.

Housekeeping: keeping it honest

  • Give it an owner. One person decides what goes live and when it comes down.
  • Diary the end date. A calendar reminder on the day the closure ends saves you a week of "closed until Monday" showing on Wednesday.
  • Track the link. If the bar links to a page, look at whether that page's visits rise while the bar is live. If nobody clicks, the message may be wrong or unnecessary.
  • Keep a plain-text log. Note each message, its dates and its link. It helps when someone asks why customers thought you were closed.

FAQ

Should an announcement bar appear on every page?

Usually, if the message affects most visitors, such as a closure or delivery deadline. If it only matters at one stage, for example a shipping cut-off, showing it on product, basket and checkout pages can be enough and keeps the rest of the site clean.

Does an announcement bar hurt SEO?

Not in itself. The risk is layout shift if the bar loads late and pushes content down, which affects user experience measures such as CLS. Rendering it with the page or reserving its space avoids that.

Can I rotate several messages in one bar?

You can, but rotating text is easy to miss and can be difficult for some users to read before it changes. One message at a time, with a link to a page listing the rest, is clearer.

How long should a bar stay up?

As long as the message is true and useful, and no longer. Most good announcements have a natural end date; set a reminder to remove the bar on that day.

Planning a holiday closure notice or a cleaner way to flag delivery deadlines across your site? Tell us what needs announcing and we'll suggest where it should live.

Sources

WhatsAppLet’s talk