# Missing

landmark > Without a

landmark, assistants and screen readers can’t find your primary content. Wrap the main content in a single semantic

. _Category: AI readiness · Detector `aeo` · Check `no-main-landmark` · Severity: info_ Landmarks like `

`, `

`, and `

` tell assistive tech and content extractors where the primary content is, instead of forcing them to guess from a sea of `

`s. Screen-reader users jump straight to `

`; answer engines use it to separate content from chrome. AI scaffolds output `

`-only trees, so this signal is simply absent. ## Symptoms - Screen readers offer no "skip to main content" landmark - The page is a tree of `

`s with no semantic regions - Content extractors include nav/footer boilerplate as if it were content - Accessibility audits flag "no main landmark" ## How VibeCheck detects it The `aeo` detector flags this live in the browser and reports it to the widget's Problems list — and to your coding agent over MCP. - **Issue string:** `No

landmark` - **Threshold:** document.querySelector("main") returns null ## Root causes - The layout uses `

` everywhere instead of semantic elements - A component library wraps content without a `

` region - Multiple content areas but no single primary landmark ## The fix Wrap the primary content of each page in exactly one `

` element, and use `

`, `

`, `