How to fix landmark main is top level on Wix
Move the `<main>` element (or `role="main"`) so it is a direct child of `<body>` and not nested inside any other landmark element such as `<header>`, `<nav>`, `<aside>`, or `<footer>`.
Steps for Wix
- Wix generates its own HTML structure and does not expose direct `<main>` tag editing in the standard Editor or Editor X/Studio.
- In Wix Editor or Wix Studio, open the Page Settings for each page and check whether you have custom `<header>` or section elements wrapping the main content area; restructure sections so the primary content section is not inside a Header/Footer widget.
- If you have added custom HTML via the Wix HTML iframe widget (`Embed Code` → `Embed HTML`), review that code and ensure any `<main>` or `role="main"` you've added is not wrapped in another landmark.
- For deeper structural control, consider migrating to Wix Studio, which offers more semantic layout control, or raise a support ticket with Wix asking them to ensure their generated markup places `<main>` at the top level of `<body>`.
- Test each page with the WAVE browser extension to confirm the landmark structure.
<!-- ✅ CORRECT: <main> is a top-level sibling of other landmarks -->
<body>
<header>…site logo and branding…</header>
<nav>…navigation links…</nav>
<main>
…unique page content…
</main>
<footer>…footer links…</footer>
</body>
<!-- ❌ INCORRECT: <main> is nested inside <header> -->
<body>
<header>
…site logo and branding…
<main> <!-- wrong! <main> must not live inside <header> -->
…page content…
</main>
</header>
<footer>…</footer>
</body>What is landmark main is top level?
Every webpage should have one clearly defined "main content" region that screen readers and other assistive technologies can jump to directly. In HTML this is the `<main>` element (or any element marked with `role="main"`). The WCAG rule "landmark-main-is-top-level" means that this main region must sit at the top level of the page structure — as a direct child of `<body>` — and must not be wrapped inside another landmark region like `<header>`, `<nav>`, `<aside>`, or `<footer>`. Nesting `<main>` inside another landmark confuses the accessibility tree and breaks the expected page hierarchy that assistive technologies rely on.
Screen reader users — including many people with visual impairments — use keyboard shortcuts to skip straight to the main content of a page, bypassing repetitive navigation menus. When `<main>` is incorrectly nested inside another landmark, that shortcut either fails silently or lands the user in the wrong place, forcing them to tab through every menu item on every page visit. This is a WCAG 2.1 / 2.2 failure (Best Practice, closely tied to Success Criterion 1.3.6 and the bypass-blocks requirement at 2.4.1), which creates legal accessibility risk under ADA Title III in the US, the European Accessibility Act, and similar laws globally. Beyond legal exposure, poor accessibility reduces your potential customer base and signals poor technical quality to search engines that increasingly factor accessibility into crawl quality.
See the complete Landmark main is top level guide for every platform and the full background.
Not sure if your Wix store has this?
Run a free SEOLZ audit — we’ll find landmark main is top level and every other issue across your whole site.
Scan my site free