Cookie Banner Text You Can Copy for Client Sites

Cookie Banner Text You Can Copy for Client Sites

Paste these templates into ConsentLayer’s banner, which holds known trackers until the visitor consents, so EU wording such as “[Client name] uses cookies” with “Accept all | Reject all | Choose cookies” is true on the live site. California visitors get a notice at collection with a “Do Not Sell or Share My Personal Information” link.

What compliant cookie banner text has to say

Cookie banner text has to name what the site’s cookies do, such as measure visits or show ads, before the visitor picks a button. For visitors in the EU and UK, the GDPR and the ePrivacy rules require opt-in, so the first layer needs a reject button as easy to reach as the accept button, and nothing optional may load before the click.

The text also needs a link to the cookie policy, which lists each cookie, its provider, and how long it lasts. Visitors must be told how to change their choice later, because consent that can’t be withdrawn as easily as it was given doesn’t hold up.

California works the other way round. Under the CCPA and CPRA, the site gives a notice at collection that says what personal information it collects and why, and it shows a “Do Not Sell or Share My Personal Information” link so the visitor can opt out. Browsers that send Global Privacy Control make that opt-out request automatically, and California treats the signal as a valid request.

On a client site, the risk sits in the gap between the wording and the scripts: a Meta Pixel that a marketing plugin adds to the header fires on page load, so the banner says “nothing runs until you choose” while the site sends data to Meta before the visitor reads a word.

How we picked these cookie banner texts

We left out one-line “we use cookies, OK” notices, because a banner with a single button gives an EU visitor no way to refuse, and every template here gives Accept all and Reject all the same weight. Each one is plain text, so you can paste it into the text fields of any banner, ConsentLayer’s or another, and swap the square-bracket placeholders for the client’s details.

A lawyer, not a template, decides whether the wording is enough for a particular client, so send the final text to whoever handles that client’s legal review before launch. For finished designs you can compare against, look at these cookie banner examples from GOV.UK, the ICO and GitHub.

Cookie banner text templates you can copy

EU and UK opt-in banner text

The line “Nothing optional runs until you make a choice” is true only when the banner blocks trackers before the click and runs them after it. Check it on the live site before the client signs off.

> [Client name] uses cookies > We use cookies to measure how visitors use this site and, with your permission, to show you relevant ads on other sites. Nothing optional runs until you make a choice. You can change your choice at any time from Cookie settings at the bottom of every page. Read our cookie policy: [cookie policy URL] > [Accept all] [Reject all] [Choose cookies]

Use it as the first layer on any client site with visitors in the EU, EEA, or UK. Keep “Reject all” on that first layer even when the client asks you to move it into the panel, because a reject that takes more clicks than accept breaks the opt-in and opt-out consent rule the text claims to follow.

The “Cookie settings” line is the one that goes wrong after launch, since it promises a footer link that someone has to add to the theme, and a client who edits the footer later can delete it without knowing. Its limit is scope: the text names analytics and ads only, so a site with a chat widget or embedded videos that set cookies needs one more clause for them.

Preferences panel text for each category

Every category description has to match the Google signal it controls. A visitor who allows Statistics allows analytics_storage, a visitor who allows Marketing allows ad_storage, ad_user_data, and ad_personalization, and Essential maps to functionality and security storage.

> Choose which cookies we use > Essential (always on): The site needs these for logins, the cart, and security checks. > Statistics: We count visits and pages viewed with Google Analytics to see what works. > Marketing: Google and other ad partners use your visits to show you ads and check whether they work. > [Save choices]

The panel opens when the visitor clicks “Choose cookies”, and it suits any site that sends data to Google through Google Consent Mode v2 on client sites. Make three edits before launch:

  • Name the vendor that really receives the Statistics data, such as Matomo in place of Google Analytics.
  • Keep the Marketing line about ads. The ad_user_data and ad_personalization signals decide whether Google may use the visitor’s data for advertising, and a vague “better experience” line misdescribes that switch.
  • Hold each description to one sentence of under 20 words, about five seconds of reading.

California notice at collection with a Do Not Sell or Share link

A California visitor needs a notice and an opt-out link, and the opt-out requests need somewhere to go. ConsentLayer handles Do Not Sell requests on Solo and up, and its region rules cover GDPR, CCPA, LGPD, and custom groups.

> Your privacy choices > [Client name] collects your device information, the pages you visit, and how you use this site through cookies and similar tools. We use this information to run and measure the site and to show ads, and we share it with advertising partners, which California law may treat as a sale or sharing; we keep it for [retention period]. Read our privacy policy: [privacy policy URL] > [Do Not Sell or Share My Personal Information] [OK]

Unlike the EU and UK opt-in text, this notice lets tracking start on page load and leaves the visitor to opt out. Don’t carry the line “nothing optional runs until you make a choice” over to it, since a California visitor would read a false claim. Keep the link label word for word: “Do Not Sell or Share My Personal Information” is the wording the regulations name, and a client who shortens it to “Privacy” has removed the link the law asks for.

Repeat the link in the site footer for visitors who dismissed the notice and still want to opt out. The CCPA cookie banner setup covers the region rule that shows this text only to California visitors.

Notice text for visitors who send Global Privacy Control

A visitor whose browser sends GPC never sees the prompt, so the only text they read is the short notice that tells them a reject was recorded. Take a client’s shop with a Meta Pixel, opened in Brave or in Firefox with GPC switched on: the banner skips the prompt and records a reject. It also sets the Do Not Sell flag and shows this notice in its place.

> We received your browser’s Global Privacy Control signal, so we’ve opted you out of the sale and sharing of your personal information and turned off optional cookies. To change this, open Cookie settings at the bottom of the page.

See how Global Privacy Control works on client sites.

Banner text in German, French, and Spanish

ConsentLayer has written default copy in 10 languages (en, de, fr, es, it, nl, pt, pl, sv, da), so for a client site with German or French visitors you edit a translation instead of writing one. The banner also accepts 186 locale codes and supports 8 right-to-left languages. Each version below keeps the EU and UK opt-in text and its three buttons.

German, in the formal “Sie” that most German business sites use:

> [Client name] verwendet Cookies > Wir verwenden Cookies, um zu messen, wie Besucher diese Website nutzen, und mit Ihrer Erlaubnis, um Ihnen auf anderen Websites passende Werbung zu zeigen. Optionale Cookies werden erst gesetzt, wenn Sie eine Auswahl treffen. Sie können Ihre Auswahl jederzeit über „Cookie-Einstellungen” unten auf jeder Seite ändern. Unsere Cookie-Richtlinie: [cookie policy URL] > [Alle akzeptieren] [Alle ablehnen] [Cookies auswählen]

French, with “vous”:

> [Client name] utilise des cookies > Nous utilisons des cookies pour mesurer l’utilisation de ce site et, avec votre accord, pour vous montrer des publicités pertinentes sur d’autres sites. Aucun cookie optionnel n’est déposé avant votre choix. Vous pouvez modifier votre choix à tout moment via « Paramètres des cookies » en bas de chaque page. Notre politique de cookies : [cookie policy URL] > [Tout accepter] [Tout refuser] [Choisir les cookies]

Spanish, with “usted”:

> [Client name] usa cookies > Usamos cookies para medir cómo se usa este sitio y, con su permiso, para mostrarle anuncios relevantes en otros sitios. No se activa ninguna cookie opcional hasta que usted elija. Puede cambiar su elección en cualquier momento desde «Configuración de cookies», al pie de cada página. Nuestra política de cookies: [cookie policy URL] > [Aceptar todas] [Rechazar todas] [Elegir cookies]

Have a native speaker on the client’s side read the final copy, because the footer link label in the banner text has to match the label in the theme footer, and translators often pick a different word for each.

Cookie banner text templates side by side

TemplateWhere it showsButtons and links on the first layerEnglish word count
EU and UK opt-inFirst layer for visitors in the EU, EEA, and UKAccept all, Reject all, Choose cookies, cookie policy link64
Preferences panelSecond layer, after the visitor clicks Choose cookiesSave choices, plus one switch each for Statistics and Marketing53
California notice at collectionFirst layer for California visitors, with the link repeated in the footerDo Not Sell or Share My Personal Information, OK, privacy policy link77
GPC noticeIn place of the prompt when the browser sends Global Privacy ControlCookie settings link in the footer39
German, French, SpanishFirst layer, matched to the visitor’s languageThree translated buttons and a cookie policy link64 (English source)

Cookie banner text questions

Does “by continuing to browse” count as consent?

No. The GDPR asks for a clear affirmative act, and its Recital 32 says silence or inactivity can’t count, which rules out scrolling. Each ConsentLayer site can run opt-in, the default, or opt-out, so leave opt-in set for European audiences and switch a site to opt-out only where its visitors’ law permits that model.

Does the banner text need a link to a cookie policy?

Yes, since the visitor has to be able to see what each cookie does before choosing. ConsentLayer generates a hosted cookie policy from the site’s categories, services, and cookies, and rebuilds it when they change, so the URL you paste into the template stays current after the next scan.

How often should the banner ask visitors again?

Consent lasts 365 days by default, after which the banner asks again. Ask sooner when the client adds a new ad or analytics vendor, because an earlier yes didn’t cover a tool the visitor never heard of. Shorten the period if the client’s lawyer asks for it.

What should the button that reopens the banner say?

ConsentLayer adds a floating reopen button with 4 icon choices, so visitors can change their decision at any time without hunting for a link. An icon carries no words, so pair it with a footer link labelled “Cookie settings”, which matches the wording in every template.

Putting the text on a client site’s banner

Once the client approves the wording, it goes into the banner’s editable text. There you can also add the client’s logo and pick one of 7 positions and 5 colors, with each button switched on or off. Give your agent one prompt like this, after you replace the placeholder with the domain of the site you are setting up (your own or a client’s):

On <your-domain>, replace the ConsentLayer banner text with the
EU and UK opt-in text I paste here. Show only the buttons
Accept all, Reject all, and Choose cookies. Turn every other
button off. Then tell me the text and buttons the banner now has.

[paste the template with the client's details filled in]

Your agent updates that site’s banner settings and replies with the text and the buttons it set, so you can compare them with the approved copy in the same chat. Without an agent, open the site in the ConsentLayer dashboard and go to the banner settings. Paste the text into the text fields and switch each button on or off by hand. Both paths reach the same result, since every dashboard screen has a matching agent tool, and a colleague can review your change from the dashboard later.

To check that it worked, open the client site on its real domain in a private browser window and read the banner against the approved text. Then click “Choose cookies” to confirm the panel shows your category descriptions and the “Save choices” button.

Put the opt-in text on your next client site’s banner and check that trackers wait for the click: create a ConsentLayer account.