No walls before the content
Does a cookie banner, age gate, or sign-up box come before the content in the page?
What we look for
On the home page and the sampled pages, your newest posts among them, we look for an overlay that comes before your content in the page’s HTML: a cookie or consent banner, an age check, a newsletter sign-up, a paywall, or any pop-up or dialog. We find these by their usual markup (a dialog element, a modal role), their usual names (cookie, consent, newsletter, paywall, popup, and so on), and their words, whatever they’re called: “we use cookies”, “select your country”, “subscribers only”, “verify your age”.
A page fails if such an overlay comes before the main content and has more text than the content does, if the page’s first 1,000 characters of text are all overlay, or if it is a modal, pop-up, or age or country gate placed ahead of the main content, however short, whether or not the page marks its content with a <main>. A page whose article section holds a paywall notice (“This post is for paying subscribers only”) where the article should be fails too: the notice is all a reader gets. So does a page that says so itself: isAccessibleForFree: false in its structured data over a stub, with no article in the HTML. The same flag over the full text is a metered or syndicated article, which a reader has, and passes. An overlay inside the main content is treated as part of the content, and one marked aria-hidden="true" hides nothing from a bot, so it isn’t a wall. Otherwise, the page passes, and if a short banner (a one-line cookie notice) does sit ahead of the content, we say so. The criterion scores the average across pages, and the report names the pages with a wall.
Why it matters
People see a banner floating over the page. A bot reading the HTML sees text in order, and if the first thing on the page is three paragraphs of cookie policy, that’s what it reads first — and sometimes all it reads. An assistant summarizing your site may describe your consent banner.
How to pass
- Put the content first in the HTML, and the overlay after it. Its position on screen is set by the stylesheet, so moving it in the source doesn’t change how it looks:
<body> <main>…your content…</main> <div class="cookie-banner" role="dialog">…</div> </body> - Or load the overlay with JavaScript after the page has loaded, or when someone scrolls or clicks.
- Keep consent text short and link to the full policy rather than including it.
- If your consent tool injects its banner at the top of the body, look for a setting that loads it at the end instead.
Last changed .