Web Design

GDPR Cookie Consent: What a Small Business Site Needs, and How to Test Your Banner

Search results for this topic are mostly sellers of consent tools, each with a banner to install. This guide starts from the rules instead: what the GDPR text and EU regulators say a valid cookie banner needs, which design mistakes they named, and a way to test your own banner without buying anything. It is information, not legal advice.

GDPR Cookie Consent: What a Small Business Site Needs, and How to Test Your Banner

Key takeaways

  • Consent comes before the cookie. Cookies that are not strictly necessary should not be set until the visitor has said yes with a clear action. Silence, scrolling and pre-ticked boxes do not count.
  • GDPR can apply outside the EU. Article 3 reaches businesses that offer goods or services to people in the EU or monitor their behaviour there.
  • Refusing must be as easy as accepting. A majority of EU regulators in a 2023 taskforce treated a banner with no reject option as an infringement.
  • A banner can look right and still be wrong. The test is what loads before the visitor answers, not what the banner says.
  • Withdrawal must be as easy as giving consent, and the choice should be kept somewhere visitors can find again.
  • This is not legal advice. Rules differ by country. Read the regulator's own pages for yours.

The short answer

Under the GDPR and the ePrivacy rules behind it, a site that reaches people in the EU needs their consent before it sets cookies or similar trackers that are not strictly necessary, such as marketing pixels and most analytics. Consent has to be an active choice, with a refuse option as easy to use as the accept option, a clear description of each purpose and a simple way to change your mind later. If your site only sets strictly necessary cookies, no banner is needed for them, though you should still say what they do.

Who is writing: we are Amariq, a web design studio, not a law firm. We built this from the legal texts and the EDPB report named below, read on 12 November 2026. Where we give a testing routine, it is our suggestion and we say so.

What the current results cover, and what is missing

On 12 November 2026, Google (US, English) showed an AI Overview, GDPR.eu, Cookiebot, Termly, Osano, Iubenda and a sponsored result from a consent tool, with Reddit threads below. The sellers explain the rules and then offer a product. Missing is a plain way for a small site owner to check a banner they already have, using the regulators' own list of bad designs. That is the section further down.

Does it apply to your site?

Article 3 of the GDPR says the regulation applies to organisations established in the EU. It can also apply to an organisation outside the EU that handles the personal data of people in the EU when it offers them goods or services, whether or not they pay, or monitors their behaviour there. The test is where the people are, not their nationality.

So a US, Australian or UK business that sells to customers in Europe, or runs tracking that follows visitors from Europe, may be covered. Other places have their own rules; for the UK see our UK website redesign guide, which covers the Information Commissioner's analytics exception. If you are unsure, ask a data protection professional.

What the rules say

RuleSource, read 12 Nov 2026
Consent is needed before any cookie except strictly necessary onesGDPR.eu cookies page (run by Proton AG; says it is not an official EU resource and not legal advice)
Silence, pre-ticked boxes or inactivity are not consentGDPR recital 32
Consent can be a ticked box on a site, and requests should not be unnecessarily disruptiveGDPR recital 32
Pre-ticked checkboxes for cookies are not valid consent, and users must be told how long cookies last and whether third parties can access themCourt of Justice, Planet49, case C-673/17, 1 October 2019
Strictly necessary cookies need no consent, but their function should be explainedGDPR.eu
Keep a record of the consent you receiveGDPR.eu
Visitors who refuse some cookies should still be able to use the serviceGDPR.eu
Withdrawing consent must be as easy as giving itGDPR.eu; EDPB taskforce report, point 34

The Court of Justice ruling also said the rules apply whether or not the information stored is personal data.

What regulators called a mistake

In January 2023 the European Data Protection Board published a report from its Cookie Banner Taskforce, adopted on 17 January 2023, after complaints about banner designs. It is a report of positions the national authorities agreed on, not a ruling, and some points are marked as needing a case-by-case check. These are the practices it discussed.

PracticeWhat the taskforce said
No reject button on the first layerA vast majority of authorities said that having no refuse option on any layer that has a consent button does not meet the rules for valid consent and is an infringement. A few said the ePrivacy text does not mention a reject option
Pre-ticked boxesConfirmed that pre-ticked boxes do not give valid consent
Reject offered only as a linkThe examples that fail include a "refuse" or "continue without accepting" link buried in a paragraph of text. Banners should not give the impression that consent is needed to see the content, or push the visitor towards it
Button colours and contrastNo general colour or contrast standard can be imposed. Each banner is judged on its own. A reject button whose text is unreadable to nearly any user is an example that could be manifestly misleading
"Legitimate interest" in the second layerThe taskforce said the legal basis for placing or reading cookies cannot be the controller's legitimate interest, and that a second refusal step can confuse people
Cookies wrongly called "essential"Classing cookies as strictly necessary when they are not was a concern. Cookies that remember a visitor's own choices can count as essential
No way to withdrawOwners should provide an easy way to withdraw at any time, such as a small permanent icon or a link in a standard place. No specific solution can be imposed

A fair banner, in practice

From those rules, a small site's banner is on safe ground when it:

  1. Says in one or two lines what cookies it wants and why.
  2. Shows "Accept" and "Reject" together, as buttons of equal weight, readable and the same size.
  3. Offers a "Settings" choice for categories, with every optional box off by default.
  4. Loads nothing optional until the visitor accepts.
  5. Lets the visitor read the page without answering, or at least does not hide the content behind the banner.
  6. Keeps a link or icon in the footer, or in a corner, to reopen the choices and change them.
  7. Remembers the choice, and records it.

A footer link is a common place for the reopen control; our website footer guide covers what else belongs there.

Test your own banner

This routine is our suggestion, not something regulators prescribe. It takes ten minutes and needs only a browser.

  1. Open your site in a private window, so no earlier choice is stored.
  2. Open the browser's developer tools and look at the cookie list and the network requests before you touch the banner. Analytics, ad and social scripts should not appear yet. If analytics is the only thing that needs consent, our guide to Google Analytics alternatives compares tools whose makers say they work without cookies.
  3. Click Reject. Reload and check again. Nothing optional should load.
  4. Clear the site data and repeat with Accept. The optional scripts should now load.
  5. Reopen the choices from your footer link or icon and withdraw. Reload. The optional scripts should stop.
  6. Look at the banner itself. Are Accept and Reject the same size and equally readable?
  7. Write down every cookie and script you found, with what it does. If you cannot say why one is there, find out or remove it.

The EDPB report notes that tools exist to list the cookies a site places, but that they cannot judge the nature of each cookie. You still need to know what each one does.

What it can cost to get it wrong

The GDPR sets two fine tiers. For breaches of the basic principles and the conditions for consent, which include Articles 5, 6 and 7, Article 83(5) allows fines of up to 20 million euros or 4% of worldwide annual turnover, whichever is higher, for a company. Fines are decided case by case by national regulators, and these are ceilings, not a forecast of what any one business would pay.

CheckDone?
I know whether people in the EU use my site
Every cookie and script is listed, with its purpose
Strictly necessary cookies are separated from analytics and marketing
No optional cookie loads before consent
Accept and Reject are equally easy to find, equal in size and readable
No pre-ticked boxes
Visitors can read the page without agreeing
A footer link or icon reopens the choices
Consent choices are recorded
The privacy policy matches what the site really does

Your privacy policy has to match what your site does; our privacy policy guide starts from what your site collects, and our terms and conditions guide covers the other page people ask about.

How Amariq can help

We set up the banner, the footer link and the loading rules so that nothing optional runs before consent, and we test it as above before launch. Quotes come from the scope, never the clock, and the work is yours on final payment. See our web design service.

Frequently asked questions

If your site sets cookies or similar trackers that are not strictly necessary, and it reaches people in the EU, you need their consent first, which usually means a banner. If you set only strictly necessary cookies, you do not need consent for those, though you should explain them.

A vast majority of the authorities in the EDPB's taskforce said a banner with no refuse option on any layer that has a consent button does not meet the rules. A few disagreed, so check your own country's regulator, but offering Accept and Reject together is the safest design.

No. Recital 32 says silence, pre-ticked boxes or inactivity should not constitute consent, and the EDPB taskforce said consent must be expressed by a positive action.

Not by default: the rules ask for consent to any cookie that is not strictly necessary, and a national exemption is needed to skip it. The UK has a narrow one for statistics, with conditions, covered in our UK guide. Check your own regulator's page.

GDPR.eu lists documenting and storing the consent you receive as a requirement. A consent tool normally keeps the log for you.

GDPR.eu says users should be able to access a service even if they refuse certain cookies, and the EDPB taskforce said banners should not give the impression that consent is needed to see the content.

Does GDPR apply to a small business outside the EU?

It can. Article 3 applies to organisations outside the EU that offer goods or services to people in the EU or monitor their behaviour there. Where you serve no one in the EU, other laws may apply instead.

Rahat Khondokar, founder of Amariq

Rahat Khondokar

Founder & CEO, Amariq

Rahat designs and builds websites for marketing teams and ecommerce brands, and writes here about the structure, copy and conversion work behind them. More about Amariq. Find him on YouTube, Dribbble and LinkedIn.

Keep reading

Related articles.

All articles