Cookie Banner Examples and the Designs Regulators Reject

Cookie Banner Examples and the Designs Regulators Reject

For client sites, copy the GOV.UK and Mozilla pattern (accept and reject as buttons on the first layer, a settings link, and analytics that wait for a choice), and build it with ConsentLayer, which holds trackers until consent. If a site has many US visitors, add what GitHub does: a “Do Not Share My Personal Information” footer link and Global Privacy Control honored. When a client wants nothing set before a click, copy the EDPB banner.

What a good cookie banner does on a client site

A good cookie banner controls what the page loads. Analytics, ad pixels, chat widgets and video embeds that set cookies stay off until the visitor picks an option, then start only for the accepted categories. A banner that looks right while Google Analytics fires in the background has failed, because the page has already set the cookies it asks about.

Any visitor who closes the tab or scrolls past the banner without clicking hasn’t agreed to anything. The safe reading of that silence is a refusal, so the optional scripts stay held on every page view until a real choice arrives.

On a site you inherit, test this before you touch the design. In a private window, open the Network tab in your browser’s developer tools and load the homepage without clicking the banner.

Requests to google-analytics.com or connect.facebook.net at that moment mean something bypasses the banner, and the usual cause is a tracking snippet pasted into the theme header, or a Google Tag Manager tag on an “All Pages” trigger with no consent check. A new design on top of those scripts changes nothing, so fix the loading first.

How we chose these cookie banner examples

Every example is a live banner whose text and buttons we read on the site itself on 20 October 2026, so you see what a visitor gets today and not a screenshot from an older version. We picked two regulators, a government site and two large software sites, because those owners have the strongest reason to get their own banner right.

For each one we looked at three things: the choices on the first layer, what runs before the visitor chooses, and how the visitor changes the choice later. If you are still picking the tool that will run these banners, start with choosing a consent management platform for client sites.

Five live cookie banner examples, plus one you configure

GOV.UK: a reject button and a confirmation line

A GOV.UK visitor rejects with one click on “Reject additional cookies”, a button next to “Accept additional cookies”, and a third button, “View cookies”, opens the full list. After the click, the banner swaps its text for “You have rejected additional cookies” (or “accepted”) and adds “You can change your cookie settings at any time”. The new text comes with a “Hide cookie message” button.

Until then, GOV.UK sets only its strictly necessary cookies, which “always need to be on”, and it holds back Google Analytics, the LUX/SpeedCurve performance script, marketing cookies and the cookies that remember settings.

This is the pattern to copy for most client sites. The confirmation line answers the question clients hear from their own customers (“did my choice save?”) without a second page. Its limit is that the first layer treats every optional cookie as one group.

Mozilla: three categories with their own switches

Mozilla collects analytics only with consent, so a visitor who clicks “Reject All Additional Cookies” loses nothing the site needs to work. A “Cookie settings” link next to “Accept All Additional Cookies” leads to a page where they decide per category. The page splits cookies into three groups and gives each optional group its own pair of answers:

  • Necessary cookies can’t be turned off, and the page says so instead of showing a switch that does nothing.
  • Preference and Analytics each get “I Agree” and “I Do Not Agree”, so the visitor answers every category in words.
  • A single “Save Changes” button stores all the answers at once.

Copy this layout for a software product or membership site whose visitors ask for detail, and budget for keeping the settings page in step with the cookie list each time the client adds a tool.

EDPB: no choice means no cookies

The European Data Protection Board site shows two buttons, “Accept cookies for aggregated statistics” and “No thanks, only essential cookies”. A visitor who closes the tab without clicking either gets no cookies on that visit. The EDPB shows the banner “every time you enter our website” until one of the two options is chosen, so that visitor sees it again the next day.

This is the strictest model you can show a client, and it suits a law firm, a health practice or a public body that wants nothing optional before a click. The trade-off is the repeat banner, which a visitor who ignores it sees on every visit.

ICO: analytics on arrival, with an off switch

On the same question, the UK Information Commissioner’s Office does the opposite of the EDPB. Its analytics cookies are labelled “optional”, yet “they will be set when you arrive on the website”, and the visitor’s only route is “You may turn them off” afterwards.

On the first layer the ICO uses “Accept non-essential cookies” and “Reject non-essential cookies”, and its settings panel has an On/Off switch per category and a “Save and close” button. The EU regulators’ own banner waits for consent, so for an EU client, skip the analytics-on-arrival part. Copy the switches and the “C” icon that reopens the settings.

GitHub: a banner by region, and GPC honored

GitHub says some users can manage non-essential cookies through a consent banner.

VisitorWhat GitHub does
A visitor in a region that gets the bannerThey can accept, manage, or reject all non-essential cookies, and GitHub says that in “some jurisdictions” none are used until consent
A visitor whose browser sends Global Privacy ControlGitHub doesn’t share their data, with no click, and a “Do Not Share My Personal Information” footer link gives the same opt-out to everyone else

This model fits a client with a large US audience, because a footer link and the GPC signal meet the US opt-out style without forcing a banner on every visitor. With this model, you have to decide the regions yourself. For the US side in detail, read CCPA cookie banner on a client site.

ConsentLayer: three templates you set per client

ConsentLayer gives each client one of three templates (a floating card, a wide bar, or a modal), and you switch each button on or off, so you can put reject next to accept on the first layer.

  • Each banner takes one of 7 positions and 5 colors, a client logo, and text you edit to match the client’s own words.
  • The Solo plan adds the modal template, branding removal, weekly automatic scans, region rules for GDPR, CCPA, LGPD and custom groups, Do Not Sell request handling, and unlimited banner languages.

Each layout is in ConsentLayer banner templates and blocking.

Cookie banner examples compared

SitePer-category choice on the first layerHow the visitor changes the choice later
GOV.UKNo, accept or reject covers all additional cookies, and “View cookies” opens the list“You can change your cookie settings at any time”, shown after the choice
MozillaNo, categories sit behind the “Cookie settings” linkCookie settings page with “I Agree”, “I Do Not Agree” and “Save Changes”
EDPBOne optional category only, aggregated statistics, so the two buttons are the category choiceBanner returns on every visit until the visitor picks an option
ICONo, On/Off switches sit in the settings panel“C” icon on every page
GitHubAccept, manage, or reject all non-essential cookies“Do Not Share My Personal Information” link in the footer, or a GPC signal from the browser

Banner designs EU regulators reject

The EDPB cookie banner taskforce adopted its report on 18 January 2023, and it records where the EU’s data protection authorities agree on banner design. When a client asks you to “just check the banner”, its findings are the standard to check against.

No reject button on the first layer

In the report, “a vast majority of authorities” count a banner with no reject option on any layer with a consent button as an infringement. Run this check on each client site:

  1. Load the homepage in a private window so no earlier choice is stored.
  2. Find the accept button on the first layer.
  3. Look on that same layer for a reject, refuse or “No thanks” button. If the only way to refuse is through “Settings” or “Manage”, the banner fails.

Pre-ticked category boxes

Pre-ticked boxes on the settings layer “do not lead to valid consent”, the report says. Open the settings layer and confirm that every non-essential box starts unticked. This one hides well on inherited sites, where a banner plugin may ship with Analytics switched on and the client never opened the panel. A visitor who clicks “Save” without changing anything has then agreed to analytics they never chose.

A reject link or a faded reject button

Reject must be a control a visitor can see and read. The report says a reject option that is only a link inside a paragraph, or a link outside the banner, without enough visual support doesn’t give valid consent, and a reject button whose text is “unreadable to virtually any user” is manifestly misleading.

GOV.UK shows what passes, with “Reject additional cookies” as a real button in the banner, while a gray “continue without accepting” text link under a bright accept button is the version the report describes as failing.

“Essential” cookies that are not essential

The report puts the site owner in charge of the cookie list and of showing why each cookie is essential. Go through each cookie in the Essential category and match it to a purpose. A scan can list the cookies a page sets, but the report says scan tools can’t check what a cookie is for, so the judgment stays with you. Three items to question on client sites:

  • An analytics or heatmap cookie filed as Essential because the client “needs the data”.
  • A chat widget cookie that loads on every page, when the chat could start only on click.
  • Cookies with no known owner, left from a plugin the client removed.

No easy way to change the choice later

A visitor accepted all cookies on a client’s shop last week, and today they want to undo it. They find no link, no icon and no way to reopen the banner short of clearing their browser data. The report says withdrawing consent must be as easy as giving it, so that banner fails. The report suggests “a small hovering and permanently visible icon” or a link in a visible and standard place, but it imposes no single solution, so a footer link and a floating icon both pass.

Cookie banner FAQ

Should a cookie banner respond to browser privacy signals?

The EDPB site does: it reads Do Not Track and shows “We’ve detected your browser’s Do Not Track request, so no tracking cookies will be deployed”, with a “Dismiss” button that hides it for 6 months. ConsentLayer honors Global Privacy Control by default on all plans, as how Global Privacy Control works explains.

What should a YouTube embed show before the visitor consents?

Show a placeholder, not the player. With video cookies off, the ICO shows its videos as standard links to YouTube or Vimeo. ConsentLayer swaps YouTube, Vimeo, DailyMotion, Google Maps, reCAPTCHA, X and Instagram embeds for a click-to-load placeholder until consent.

Do you need to show the cookie banner to every visitor?

No, a banner can depend on location. GitHub sets a show_cookie_banner cookie from the client’s region to decide whether the banner appears. On Solo and up, ConsentLayer region rules can target the EU/EEA and UK block, 65 countries, and 51 US states including DC.

Can a site use legitimate interest instead of consent for cookies?

It can’t, because the EDPB taskforce report says the legal basis for placing or reading cookies under Article 5(3) of the ePrivacy Directive “cannot be the legitimate interests of the controller”. A banner that offers a “legitimate interest” toggle for analytics or ads still needs consent for those cookies.

Build one of these banners on a client site

With the AI you already use connected to ConsentLayer over MCP, one prompt sets up the next site on your roster:

Set up a cookie banner for clientsite.com with a wide bar,
accept and reject on the first layer, and a settings link.

Your agent calls setup_site, which creates the site and scans it. It also sets up the consent categories and returns the install tag with a real project key. Paste that tag into the <head> of every page, before other scripts, and deploy. Then ask your agent to check the install. It runs check_installation, which fetches the live homepage and confirms the tag is in <head> without defer or async. The guide to set up cookie consent from your agent covers the connection, where you sign in through your browser.

Without an agent, sign in at app.consentlayer.com and add the client’s domain. Run the scan, then pick the template and buttons. Then copy the same tag into the <head> of every page.

The banner renders in Shadow DOM, with ARIA labels, a focus trap, and a 640px mobile breakpoint, so the client theme’s CSS cannot break it. Visitors get a floating reopen button, with 4 icon choices, to change their decision at any time, and the consent log records every decision on every plan, including Free. Repeat the private-window Network check once the tag is live. The site is protected when the tag sits in <head> on the real domain, blocking is on, and the log shows decisions arriving.

Set up the banner on your first client site, free, and check that trackers wait for the visitor’s choice.