SiteNavigationElement schema
The site's primary navigation links, described so a crawler can distinguish navigation chrome from page content.
Where to use it
Sitewide, usually once.
A complete example
Valid as written, with every required property and the recommended ones that carry real information.
{
"@context": "https://schema.org",
"@type": "SiteNavigationElement",
"name": "Acme Reference",
"url": "https://www.seoforsolos.com/example"
}Properties
| Property | Status |
|---|---|
name | Required |
url | Recommended |
The three mistakes this type attracts
- 01Emitting it on every page with a different @id each time.
- 02Listing every link on the site rather than the primary navigation.
- 03Using it as a substitute for real, crawlable anchor tags.
Related types
Where this appears in the playbook
- Structured data: what each type is for and which ones earned their place.
- The schema graph: composing types into one graph with stable identifiers.
- One JSON-LD script per page, holding one @graph
- Stable @id anchors that cross-reference rather than duplicate
- Optional fields are omitted, never emitted as empty strings
Questions
What is the SiteNavigationElement schema type for?
The site's primary navigation links, described so a crawler can distinguish navigation chrome from page content. Use it on: sitewide, usually once.
Which SiteNavigationElement properties are required?
SiteNavigationElement requires one property: name. It also recommends 1: url.
Does SiteNavigationElement produce a rich result?
SiteNavigationElement does not produce a Google rich result. It is still worth shipping, because its value is entity resolution and answer extraction rather than search result presentation.
What is the most common SiteNavigationElement mistake?
The most common SiteNavigationElement mistake is: Emitting it on every page with a different @id each time.