Keep a catalogue navigation trail in its published order
Admin ·
A page can sit behind more than one navigation path. Start with one trail that a reader uses to reach the winter collection.
Resolve the trail against the current page
Load the example and generate the schema. The list begins with Home, followed by Studio & archive and Prints. Winter collection is fourth.
The relative Prints href becomes https://catalog.example.com/studio/prints/. The final item uses the Page URL because its input line has only a name.
Schema.org BreadcrumbList and ListItem orderGoogle Search Central, breadcrumb structured data
Check a repeated section before publishing
Copy the Prints row and add it after the existing Prints entry. The strict setting reports a duplicate at the added line.
Remove the extra row, or clear the duplicate setting if both occurrences are intentional. Check that the ordered list still matches the visible trail.
Choose the file your template expects
Choose JSON-LD for a CMS field that adds its own script container. Choose HTML script for a template that expects a complete application/ld+json block.
Check itemListElement in the exported file. The last position is 4 in the example, and the hrefs are absolute strings.
Common questions
Can I omit the link for the current page?
Yes. Leave the final item’s URL blank and leave Page URL blank too. Any earlier item needs its own valid URL.
What if Home URL is blank?
When you add Home and supply a Page URL, Home uses that URL’s origin root. Enter another absolute or relative URL to use a different destination.