Remediation
A cookie-consent modal does not cover or block the primary content on first load.
auth.cookie_consent_blocks_contentreadabilityweight 2heuristic
Why it matters
Cookie banners that overlay the entire page until a user clicks "accept" hide content from agents the same way they hide it from a screen reader. Agents cite the cookie banner instead of your page.
How to fix
- Cookie banners must not block content rendering. Render the page first; show the banner alongside, not on top.
- For full-screen consent UX, ensure agents (User-Agent: GPTBot etc.) bypass the banner; they are not legal consent subjects.
- Audit your cookie-consent vendor for an "exempt bots" setting or use IP / UA detection.
Hand it to your AI assistant
Paste this into Claude Code, Cursor, or any assistant with your repository open. It carries the steps, how to verify them, and the shortcuts to avoid. It is generic, though: run a scan to get one written from what your pages actually do.
Run a scan to check your site
Verify on your site
Run a scan against your domain to see whether auth.cookie_consent_blocks_content currently passes, warns, or fails. Free, no signup; the score page is permanent and citable.