This article explains why the “Link every page to a privacy policy” check can flag, even when your website does have a privacy policy page.
In most cases, this behaviour is expected and relates to how the check works, rather than an issue with your site.
What this check looks for
The “Link every page to a privacy policy” check ensures that visitors can easily access your privacy policy from any page on your website.
For the check to pass, each page must contain a clear link to the privacy policy.
Why having a privacy policy page is not enough
Simply having a privacy policy page on your site does not automatically satisfy the check.
If a page does not include a visible link to the privacy policy, the check will flag because:
Visitors cannot easily find the policy from that page.
Access to the policy relies on users navigating elsewhere first.
The check is focused on consistent access, not just the existence of the policy itself.
Why a footer link can still result in a flag
Even when a privacy policy link is present in the footer, the check may still flag.
This usually happens when the link text does not match what the check is configured to recognise.
How the check works
The “Link every page to a privacy policy” check is implemented as a configurable policy.
It works using the following logic:
Find all HTML pages.
Exclude any page that contains a link with specific link text, taken from a configurable list.
If a page contains a matching link, it is excluded.
If it does not, that page is flagged.
Why the default configuration cannot cover every site
There are several common reasons why pages may flag even though a privacy policy link exists.
Link text does not match the default list
By default, the policy checks for common link text such as “Privacy policy”.
If your site uses different wording, for example “Privacy notice” or “Your privacy”, the link will not be recognised unless that wording is added to the policy.
Language differences
The default configuration uses English link text.
If your website is in another language, the check will not recognise translated link text unless it is added to the configuration.
Non-standard implementations
If the privacy policy is linked using icons, images, or JavaScript-driven elements without clear link text in the page HTML, the check may not detect it.
Why this is a configurable policy
There is no single, reliable way to automatically detect every possible way a website may link to a privacy policy.
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 keeps the check flexible while still enforcing consistent access.
What to do if this check is flagging
If your site already links to a privacy policy:
Confirm that every page includes a visible link to the privacy policy.
Review the policy configuration for the check.
Add any additional link text or translations used on your site.
Re-run the check to confirm the issue is resolved.
Summary
The “Link every page to a privacy policy” check usually flags because:
Pages do not contain a direct link to the policy.
The link text does not match the configured list.
The default configuration does not include all wording or languages used on the site.
Customising the policy ensures the check accurately reflects how your site provides access to its privacy policy.