This article explains why the “Add a cookie disclaimer to every page” check can flag, even when your website has a cookie banner or a visible link to cookie information.
In most cases, this behaviour is expected and relates to how the check is designed and configured, rather than an issue with your site.
What this check looks for
The “Add a cookie disclaimer to every page” check is designed to make sure visitors can always access cookie information.
This includes situations where:
A visitor has already accepted or dismissed a cookie banner.
The cookie banner no longer appears on subsequent page views.
For the check to pass, visitors must still be able to reach cookie information after the banner has been closed.
Why having a cookie banner is not always enough
Most cookie banners are shown only once per visitor. After they are accepted or dismissed, they typically do not reappear.
If the cookie banner is the only way visitors can access cookie information, the check will flag because:
The information is no longer available once the banner disappears.
Visitors may want to review cookie details later during their visit.
For this reason, the check expects cookie information to be accessible somewhere persistent, such as a footer link, settings link, or dedicated cookie page.
Why a footer link can still result in a flag
Even when a footer link exists, the check may still flag. This is usually related to how the check is configured.
The “Add a cookie disclaimer to every page” check is implemented as a configurable policy so it can work across different site structures and wording.
How the check works
The check uses multiple AND rules:
Find all HTML pages.
Exclude any page that contains a link with specific link text, taken from a configurable list.
Exclude any page that contains specific words or phrases, also taken from a configurable list.
If a page matches any exclusion rule, the entire page is excluded.
If none of the exclusions match, that page is flagged.
Why the default configuration cannot cover every site
There are several common reasons why pages that do include cookie information may still flag.
Link text does not match the default list
The default configuration includes a limited set of common link text and phrases, such as “Cookie policy” or “Cookie information”.
If your site uses different wording, for example, “Tracking preferences” or “Data settings”, the check will not recognise it unless you add that wording to the policy.
Language differences
The default configuration uses English words and phrases.
If your website is in another language, such as Swedish, the check will not match those links or phrases unless translations are added.
Non-standard implementations
If cookie information is accessed via icons, buttons, or JavaScript-driven controls without clear link text or visible phrases in the page HTML, the check may not detect it.
Why this is a configurable policy
There is no reliable way to automatically detect every possible way a website may link to cookie information.
Using a configurable policy allows the check to be tailored to:
Your site’s wording
Your site’s language
Your site’s design patterns
This ensures the check remains accurate without enforcing a single fixed structure.
What to do if this check is flagging
If your site already provides access to cookie information:
Confirm that cookie information is accessible after the banner has been closed.
Review the policy configuration for the check.
Add any additional link text, phrases, or translations used on your site.
Re-run the check to confirm the issue is resolved.
Summary
The “Add a cookie disclaimer to every page” check usually flags because:
Cookie banners alone are not sufficient once dismissed.
The check relies on configurable link text and phrases.
The default configuration cannot cover every wording or language.
Customising the policy ensures the check accurately reflects how your site provides access to cookie information.