Landmark Checker
Paste your page HTML and find missing main, duplicate banners and unlabeled navs — landmarks are how assistive tech skips chrome.
What this tool gives you
Check landmarks
Paste your page HTML. Analysis runs locally in your browser — nothing is sent anywhere.
One <main>, unique banner/contentinfo, and named navs when you have more than one.
What this checker looks for
Landmark lists are how screen-reader users skip chrome. Duplicates and unnamed navs make that list useless.
One main
Exactly one <main> or role="main" wrapping the primary content.
Unique banner
A single page-level header maps to role=banner.
Unique contentinfo
A single page-level footer maps to role=contentinfo.
Named navs
Two or more <nav> regions need aria-label ("Primary", "Footer").
Named asides
Multiple complementary regions need names too.
0–100 score
Track landmark hygiene across templates, not just the homepage.
How to fix landmark structure
Three rules cover almost every landmark bug in the wild.
One main
Wrap the primary content in a single <main>. Delete extra role="main" wrappers.
Name extra navs
If you have more than one <nav>, add aria-label so the landmark list is unique.
Keep banner unique
One page-level header and footer. Nested article headers do not need a second banner.
Why answer engines care about landmarks
Named regions are a cheap-to-parse signal of document structure and citation-ready content.
| Signal | What engines infer | Why it helps |
|---|---|---|
| One main | The primary content is marked. | Crawlers can quote the story, not the chrome. |
| Named navs | Menus were designed, not dumped. | Predictable structure lowers bounce on AI-referred visits. |
| Unique banner | The page has a single identity region. | Consistent conventions make parsing cheap. |
| Skip-friendly | Keyboard users can jump past chrome. | Engagement quality feeds crawl and ranking models. |
| WCAG 1.3.1 pass | Info and Relationships is met. | Citable, trustworthy pages get quoted more often. |
Related GEO pages
Landmarks pair with skip links and unique ids so keyboard paths actually resolve.
Landmark FAQs
Why does a page need a main landmark?
Screen-reader users jump between landmarks. Without a single <main>, they have to tab through header, nav and ads to reach the story. WCAG 1.3.1 (Info and Relationships) expects the primary content to be marked as main.
When do navigation landmarks need aria-label?
One <nav> can stay unlabeled. Two or more must be named — "Primary", "Footer", "Breadcrumb" — so the landmark roster is not a list of identical "navigation" entries.
Can a page have more than one header or footer?
Article and section headers are fine. The page-level banner and contentinfo landmarks should stay unique. Nested <header> inside <article> does not become a second banner; a second top-level <header> does.