Create simple cookie notice
Create a clear cookie notice for your website. Customize the message, policy link, and appearance of a ready-made template.
A cookie message tells visitors how your website uses cookies and where they can find the details. Its wording should explain the purpose in plain language and match the controls beside it. A button that simply closes a notification should not suggest that it changes someone’s tracking preferences.
Below, you’ll find editable cookie notice templates, sample text for different cookie uses, and advice on choosing labels and display settings. Getsitecontrol templates provide an informational notice; they do not automatically block optional scripts or manage cookie preferences. If your site needs prior consent, use a consent management system connected to those technologies. For setup instructions, see how to add a cookie banner to your website.
This text-first template keeps the explanation, policy link, and dismissal control together. Replace the sample policy URL and change “Accept” to “Got it” if the button only closes the notice. The design is a starting point, so check the wording and actions before publishing it on your own website.
A slide-in cookie message usually appears in the corner of the screen and may include a supporting visual to match your brand style. This gives a storefront room for a short explanation without making the message look unrelated to its other notifications. Keep the illustration secondary, replace the policy destination, and check that the text and dismissal control remain visible on mobile.
A compact slide-in suits a short message on a blog or service website with limited room around the content. Keep the wording specific and add a policy link for the details. This template’s default text refers to agreeing by continuing to browse; replace it with an informational message rather than treating browsing as a consent choice.
This long floating bar pairs a brief cookie message with a close control. It is a useful format when you can explain the notice in one sentence and want to preserve the reading area above it. Add a policy link before publishing, and check its position against any sticky navigation or chat launcher on a phone.
Most cookie notices communicate two things: that the website uses cookies and why. Visitors don’t need to interpret legal terminology on the banner — detailed explanations belong on a dedicated Cookie Policy or Privacy Policy page, linked directly from the notice.
The examples below are starting points for wording, not complete consent interfaces. Use only statements that describe your actual setup. The analytics, personalization, and marketing examples assume the corresponding choice exists and is connected to those technologies; pasting the sentence into a notification does not create that choice.
| Cookie purpose | Example cookie banner text |
|---|---|
| Analytics | With your permission, we use analytics cookies to understand how visitors use this website. You can accept or reject them in Cookie settings. |
| Personalization | Optional personalization cookies help us tailor content to your interests. Choose whether to allow them in Cookie settings. |
| Marketing | With your permission, we use advertising cookies to measure campaigns and personalize ads. Manage your choice in Cookie settings. |
| Essential | We use necessary cookies to keep this website working. Read our Cookie Policy for details. |
| Mixed use | We use necessary cookies to run this website. With your permission, we also use optional cookies for analytics and advertising. Choose your preferences in Cookie settings. |
Simple cookie policy notifications work best when they’re clearly visible without blocking access to the page content. Bottom bars and slide-ins allow visitors to continue browsing while the notice remains on screen — that’s why these are a common choice for informational notices where a simple acknowledgment is sufficient. A notice that is too subtle risks being overlooked; one that blocks content entirely may frustrate visitors before they’ve had a chance to engage with the site.
For an informational notice, review Stop displaying widget in Targeting and configure After closure for the intended suppression period. That condition covers the X and buttons with a Close action. Upon action is different and does not count a Close action, so choosing the wrong condition can make the notice reappear unexpectedly.
Test dismissal, a second page view, and a return visit. A different device or cleared site data can cause the notice to appear again. These settings control widget visibility; they do not store a visitor’s cookie preferences. The cookie banner setup guide walks through the configuration.
An informational notice and a consent request should use different labels. “Close notice” describes dismissal; “Accept optional cookies” promises a change in what the website is allowed to do. Adding a second button called “Reject” is not enough if both buttons merely close the widget and leave the scripts unchanged.
Where consent is required, make sure the choices control the relevant technologies and can be changed later. The EDPB’s cookie banner taskforce report covers issues including rejection options and withdrawal. The templates here provide a customizable visual notice, not an automatic connection to a consent manager.
Use Got it or Close notice for dismissal, Cookie policy for a link to the policy, and Cookie settings only when the destination actually lets visitors manage their choices. Check each action after customizing the template.
Vague language is one of the most frequent issues — a banner that only says “We use cookies” without explaining why feels incomplete. Adding one short reason, such as analytics or personalization, and linking to your policy page makes the notice clearer and more transparent.
Banners that blend too closely into the page background or use low-contrast colors often go unnoticed. The acknowledgment button in particular should be visually distinct from the surrounding text so visitors can find and click it without effort.
Displaying the cookie notice on every page view after a visitor has already acknowledged it is a configuration issue rather than a design one. Choose an After closure suppression period that matches the notice’s purpose, then test it. For a consent interface, preference retention belongs in the consent system rather than in a widget frequency rule.
Requirements depend on the applicable rules and the technologies your website uses. Don’t assume that targeting a notice to a country also controls scripts for visitors in that country. Review the consent setup separately from the widget’s audience settings.
Once you have established that an informational notice is appropriate, choose a format that fits your page and write the message around your actual cookie use. Use a clear policy link and a dismissal label that describes what the button does. Preview both desktop and mobile layouts before publishing.
With Getsitecontrol, you can choose a ready-made cookie notice template, adjust the text to match your policy, change the colors to align with your website branding, set up proper audience targeting, and publish it on your website. The same builder can be used to create other website notifications, including pop-up messages and announcement bars. Follow the installation and testing guide to connect the widget and check its behavior on your website.
If you’d like to design an informational cookie notice without creating an account, consider Free Popup Builder by Getsitecontrol. It lets you create pop-up banners and slide-in notifications that appear on your website as soon as visitors arrive.
Choose the popup position on the screen, add your cookie notice copy, adjust the acknowledgment button, then publish it on your website using a simple code snippet. This creates a visual notification, not a system for blocking optional cookies or saving category preferences. Check the published behavior before relying on it for a persistent notice.
I really appreciate how intuitive and user-friendly Getsitecontrol is. The widgets are beautifully designed, easy to customize, and integrate seamlessly with my website. It saves me a lot of time and helps me engage with visitors in a professional and effective way.
Explain the actual purpose of the cookies, link to the relevant policy, and describe the choices available. Keep detailed cookie information in the policy. Do not promise settings or rejection controls that the website does not provide.
Use them as drafting starting points and adapt them to your website. Statements about optional cookies assume that the corresponding consent controls exist and work. The wording alone does not provide consent management.
A notice explains cookie use. A consent banner is the interface for a choice that needs to be connected to the relevant technologies. Closing a notice is not the same as allowing or rejecting optional cookies.
Yes. Edit the message, appearance, policy link, and button actions in Getsitecontrol. For a simple dismissal button, use a label such as Got it and check that it performs the Close action.
Check After closure in the widget’s targeting settings and the selected suppression period. Clearing site data or using a different browser can also cause it to reappear. See the cookie banner troubleshooting guide.
Jack Hayes covers onsite marketing, email campaigns, and ecommerce growth at Getsitecontrol. His guides connect popups, personalization, and automated emails into practical strategies for turning visitors into subscribers and customers into repeat buyers.
Create popups for free
Email forms, promos, coupons, surveys, bounce-stoppers.
Get started, it’s free →Subscribe to get updates
Get beginner-friendly tips for growing your online business.