How to fix landmark banner is top level on Webflow
Ensure your site's banner landmark (<header> or role="banner") sits at the top level of the page, not nested inside another landmark region.
Steps for Webflow
- Open your project in the Webflow Designer. In the Navigator panel (left sidebar), locate the Navbar or Header element at the top of your page structure.
- Ensure the Navbar/Header element is a direct child of the Body node in the Navigator — it should not be nested inside a Section, Div Block, or any element that has a landmark role assigned.
- If it is nested, drag it in the Navigator panel to be directly under Body, above all other landmark-carrying elements.
- To check/change ARIA roles: select the element, open the Element Settings panel (D key), scroll to Custom Attributes, and ensure no conflicting `role` attribute is set on a wrapper around your header.
- Publish the site and verify with the axe DevTools browser extension.
<header role="banner">
<!-- Site logo, main navigation, etc. -->
</header>
<main id="main-content">
<!-- Page content -->
</main>
<footer>
<!-- Footer content -->
</footer>
<!-- ✅ All three are direct children of <body> — correct structure -->
<!-- ❌ WRONG — banner nested inside <main>: -->
<!--
<main>
<header role="banner">...</header>
...
</main>
-->What is landmark banner is top level?
Every webpage has structural "landmarks" — named regions that screen readers and assistive technologies use to let users jump around the page quickly, similar to chapters in a book. The "banner" landmark is the one that identifies your site-wide header (logo, navigation, etc.). It must live directly inside the `<body>` of your HTML page, not wrapped inside another landmark like `<main>`, `<section>`, `<article>`, or `<aside>`. When it is accidentally nested inside another landmark, it breaks the expected page structure that screen readers rely on.
Screen reader users — including many people with visual impairments — rely on landmarks to navigate pages efficiently. When the banner landmark is nested incorrectly, assistive technologies may not recognize it as the site-wide header, making it impossible for those users to quickly find the top of your page or skip to main content. This is a WCAG 2.1 failure (Success Criterion 1.3.1 and 4.1.2), meaning it creates real legal accessibility risk in regions with accessibility laws (ADA, EN 301 549, UK Equality Act). Beyond compliance, fixing it improves the experience for the growing segment of shoppers using assistive technology — directly protecting your store from exclusion complaints and broadening your customer reach.
See the complete Landmark banner is top level guide for every platform and the full background.
Not sure if your Webflow store has this?
Run a free SEOLZ audit — we’ll find landmark banner is top level and every other issue across your whole site.
Scan my site free