Site Navigation Schema

Generate SiteNavigationElement JSON-LD for your main nav. Helps search engines understand site structure. Free tool, no sign-up.

About the tool

What is the SBMM Site Navigation Schema Generator?

The SBMM Site Navigation Schema Generator is a free online tool that builds SiteNavigationElement JSON-LD for your main site navigation. List each top-level menu item with its name and URL; get back a clean schema.org-compliant SiteNavigationElement block ready to paste into the head of every page on your site. Google reads it to understand your site's information architecture without crawling every page to map the nav.

SiteNavigationElement schema tells Google explicitly which URLs make up your primary navigation. The signal helps Google identify your top-level pages, understand their relative importance, and build the sitelinks that appear under your homepage in branded SERP listings. Pages declared as navigation elements typically get crawled more frequently and indexed faster than pages discovered only through breadcrumbs or in-content links.

AI search assistants (ChatGPT, Claude, Gemini, Perplexity) also use site-navigation signals when matching user queries to the right page on a site. A clean SiteNavigationElement declaration helps AI search route users to the right URL the first time, which lifts citation accuracy and click-through to your site from AI Overviews and chat answers.

Step by step

How to use this tool in 3 steps

  1. Step 01

    List your top-level nav items

    Type each top-level navigation item with its display name (what users see in the menu) and the URL it links to. Most sites have five to nine items: Home, Products, Pricing, Resources, About, Contact, plus any vertical-specific items.

  2. Step 02

    We build SiteNavigationElement JSON-LD

    The generator wraps your items in a SiteNavigationElement JSON-LD block with the correct @type, an itemListElement array of SiteNavigationElement child nodes per item, and proper name and url fields per node so Google can parse the nav correctly.

  3. Step 03

    Install on every page head tag

    Copy the generated JSON-LD and paste it inside a script type application ld json tag in the head template that loads on every page. The same nav block should appear on every URL because the schema describes the site navigation, not the current page.

Why this tool

Why use this tool

  • SiteNavigationElement JSON-LD

    Output uses the schema.org SiteNavigationElement type with itemListElement array of named, URL-linked navigation nodes. Spec-compliant and validates clean in the schema.org validator and the Google Rich Results Test.

  • Helps Google build sitelinks

    Google's sitelinks (the indented links under your homepage in branded SERP listings) are built partly from SiteNavigationElement signals. A clean nav schema makes it easier for Google to pick the right links and shape the sitelinks the way you want.

  • Faster crawl + indexing of nav pages

    Pages declared as SiteNavigationElement items get crawled more frequently and indexed faster than pages only discovered through breadcrumbs or in-content links. Critical for new top-level pages that need to enter the index quickly.

  • AI search routing accuracy

    ChatGPT, Claude, Gemini, and Perplexity use navigation signals to route users to the right page on your site when they cite you. A clean nav declaration lifts citation-to-correct-URL accuracy noticeably in AI search answers.

  • Same schema across every page

    SiteNavigationElement describes the site's nav, not the current page's contents, so the same schema block ships on every URL. Most CMS platforms have a global head section that makes this trivial; the schema does not need per-page customisation.

  • Free, no sign-up, no cap

    Generate site-navigation schema for every site you maintain. SBMM Pro adds automated nav extraction from your live HTML, mega-menu support with nested subcategories, and direct WordPress / Webflow / Shopify plugin injection.

FAQ

Frequently asked questions

What is SiteNavigationElement schema?

SiteNavigationElement is a schema.org type that declares the items in a website's main navigation menu. Each item has a name (what users see) and a URL (where it links). Together the nodes describe the top-level information architecture of the site in a machine-readable form Google can parse without crawling every page.

Does Google still use SiteNavigationElement schema in 2026?

Yes. While Google does not document it as widely as Article or Product schema, SiteNavigationElement remains an active signal that feeds sitelinks rendering, crawl prioritisation, and AI search routing. Major news, e-commerce, and SaaS sites use it consistently for these signals.

Where do I install the navigation schema?

In the head section that ships on every page of the site. The same SiteNavigationElement block appears on every URL because it describes the site's navigation, not the current page. Most CMS platforms have a global head template that makes the install a single edit.

How is this different from breadcrumb schema?

BreadcrumbList declares the navigational path from the homepage to the current page (Home > Category > Sub > Current). SiteNavigationElement declares the items in the main navigation menu of the site. Most sites use both: SiteNavigationElement on every page in the head, BreadcrumbList on each individual page describing its specific path. Validate both blocks through our Schema Intelligence Analyzer.

Should I include sub-menu items?

For mega-menus and multi-level navs, include the top-level items first and add sub-menu items as nested children inside each parent SiteNavigationElement. Most rich-result rendering only consumes the top level, so keep the nesting clean and avoid declaring every sub-link if the menu is more than two levels deep.

Will this schema appear visually in SERPs?

Not as a dedicated SERP rich result of its own, but it influences how Google renders sitelinks under your homepage in branded queries and how the nav-aware crawl-frontier prioritises your top-level pages. The lift shows up in crawl frequency, indexing speed, and sitelinks shape rather than as a direct SERP visual change.

Does the visible nav need to match the schema?

Yes. Google's structured-data spam policy treats schema that does not match visible content as cloaking. The SiteNavigationElement schema must declare items that genuinely appear in the visible site navigation; do not pad with hidden links or pages that are not in the menu.

How often should I update the navigation schema?

Every time the live site navigation changes (a new top-level section launches, a section is renamed or removed). Keep the schema in sync with the visible nav so the structured-data layer stays accurate and the cloaking risk stays zero.