A Cookie Banner in the Footer Reads as Hiding. Regulators Agree.

A banner that lives in the footer, or as a small link at the bottom of the page, is not a real choice. Regulators read placement as intent, and a consent mechanism the user has to hunt for is a mechanism designed not to be found.

Prominence is the test

Consent has to be as easy to refuse as it is to give, and it has to be visible enough to be a real choice. A banner that appears as a full-width bar at the bottom of the screen, with accept and reject buttons of equal size, passes that test. A banner that lives in the footer, or as a small cookie settings link in tiny text at the bottom of the page, does not, because the user has to scroll to the bottom, find the link, and open a panel, all to exercise a choice the site is supposed to offer upfront. The placement is the message, and the message is that the site would prefer the user not to choose.

Regulators read placement the same way. The CNIL has fined sites for banners that hide the reject option, for banners that require extra clicks to refuse, and for banners that present consent as the default. The EDPB guidelines on consent require it to be freely given, specific, informed, and unambiguous, and a choice the user cannot find is none of those. The fine is not for the footer link. It is for the design decision the footer link represents.

The placements that fail it

The footer link is the most common failure, because it is the easiest to implement: add a cookie settings link to the footer and declare the site compliant. It is not compliant, because the choice is not presented, it is archived. The second failure is the banner that appears once and never returns, so a user who dismisses it without choosing has no way back to the choice. The third is the banner that appears only on the homepage, so a user who lands on a product page from search never sees it. The fourth is the banner that appears in a language the user does not read, which is a choice the user cannot understand. Each of these is a placement failure, and each of them is visible to an auditor in seconds.

The test is simple: land on any page of the store, as a new visitor, and see whether the consent choice is visible without scrolling, without searching, and without clicking anything first. If it is not, the placement fails, whatever the consent platform dashboard claims. The dashboard measures the choice. The placement decides whether the choice exists.

What a compliant banner looks like from the shopper side

The shopper lands, the banner appears immediately, and it offers two buttons of equal prominence: accept and reject. The reject button is not smaller, not paler, not hidden behind a settings link, and not labeled with language that discourages it, like continue without the full experience. The banner says what data is collected and why, in plain language, and it offers a settings link for the shopper who wants granularity, without requiring granularity to refuse. The shopper chooses, the choice is recorded, and the banner disappears. That is the whole interaction, and it takes five seconds.

The equal prominence rule is the one most sites break, because the business wants the accept rate high and the design team obliges by making accept the obvious button and reject the hidden one. The regulator sees that as a dark pattern, and the fines that follow are for the pattern, not for the banner. Equal buttons, plain language, immediate presentation: those three are the test, and they are also the design, because a banner that meets them is a banner that respects the shopper.

The fix that costs nothing

Move the banner to the top of the load order, make the buttons equal, and write the copy in plain language. The fix is a configuration change, not a rebuild, and it costs nothing but the accept rate, which will fall, because some users who would have clicked accept by default will now click reject. That fall is the honest number, and it is the number the site should have been reporting all along. A high accept rate built on a hidden reject button is not a metric. It is a liability with a good-looking chart.

Frequently asked questions

Is a cookie settings link in the footer enough?

No. The consent choice has to be presented upfront, visible without scrolling or searching. A footer link archives the choice instead of offering it, and regulators treat that as a failure of prominence.

Do the accept and reject buttons have to look the same?

Yes, in prominence. The reject button cannot be smaller, paler, or hidden behind extra clicks. Regulators have fined sites for making refusal harder than consent, and that is a dark pattern.

Does the banner have to appear on every page?

It has to appear to every new visitor, wherever they land. A banner that only appears on the homepage misses every visitor who arrives from search on a product page.

Will fixing the banner hurt my accept rate?

Probably, and that is the honest number. An accept rate built on a hidden reject button is not a real metric. The users who click reject when given a real choice were never consenting in the first place.