Hello, I am trying to build out a Parameterized JSON-LD Template for Elements. Is there a comprehensive list available? @dan @ben
In an ongoing effort to resolve my needs, this is one way I can make this happen. Perhaps if anything is missing we can work together to add it to the list of available parameters.
Are you trying to build something like this?
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Realmac Software",
"url": "https://www.realmacsoftware.com",
"logo": "https://www.realmacsoftware.com/logo.png"
}
</script>
Can you give me an example of what you’re trying to do and hopefully we can point you in the right direction!
Hi Dan, thanks for jumping in.
The goal is to show search engines and AI systems (Google, ChatGPT, Perplexity, etc.) how the website is structured. I plan to build a four-tier architecture:
Tier 1 – Home
Tier 2 – Silo (category page with extensive content; feeds 6–20 Hub pages)
Tier 3 – Hub (sub-category page with extensive content; feeds 6–20 Article pages)
Tier 4 – Article (detailed pages; most visitors arrive here via long-tail searches)
Visitors and crawlers can navigate upward through Hub and Silo pages to explore related content. The goal is to make this navigation as intuitive as possible.
Breadcrumbs: Shown on all pages except Home.
Top Bar: Links to Home (Tier 1) and Silo (Tier 2) pages.
Sidebar: Displays all Tier 2 pages and only the Tier 3 pages related to the current Silo, preserving the site’s hierarchical structure.
Article Pages (Tier 4): Sidebar remains, with an additional navigation container for other related articles under the current Hub, perhaps at the end of the article or floating on the right side.
Structured data (JSON-LD) explicitly communicates the website’s hierarchy to crawlers. This ensures they can interpret relationships between pages without relying solely on links. Adding full JSON-LD support in Elements would give the site a clear, machine-readable map of its structure, showing exactly how pages relate from Home to Silo, Hub, and Article. This makes it easier for search engines and AI tools to understand the hierarchy, generate rich search snippets, and summarize content accurately. It also reduces the risk of broken links or orphaned pages, because any edits or reorganizations are automatically reflected in the structured data.
Hierarchy Implementation
Tier 4 articles link upward to their Tier 3 Hub.
Tier 3 Hubs list related articles in hasPart and mention their parent Silo.
Tier 2 Silos define broader subjects and reference associated Hubs.
Home page defines overall hierarchy, organization, and search capability.
This structure creates a clear, interlinked schema that search engines can interpret as a coherent topic-based hierarchy while maintaining silo integrity.
I plan to use logic from the parameters so that any edits are updated automatically by Elements when published, thereby avoiding broken links or missing pages.
Breadcrumb (Tier 4 Article Page)
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{ "@type": "ListItem", "position": 1, "name": "Home", "item": "https://MyWebsite.org/" },
{ "@type": "ListItem", "position": 2, "name": "Main Silo Page", "item": "https://MyWebsite.org/Silo1/SiloPageTier2.html" },
{ "@type": "ListItem", "position": 3, "name": "Hub Page", "item": "https://MyWebsite.org/Silo1/First-HubPageTier3.html" },
{ "@type": "ListItem", "position": 4, "name": "Article Tier 4 - Page One", "item": "https://MyWebsite.org/Silo1/ArticleTier4-PageOne.html" }
]
}
Home Page
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "Organization",
"@id": "https://MyWebsite.org/#organization",
"name": "MyProjectOrganization",
"url": "https://MyWebsite.org/",
"logo": "https://MyWebsite.org/images/logo.png",
"sameAs": [
"https://www.facebook.com/MyWebsite",
"https://www.instagram.com/MyWebsite",
"https://www.linkedin.com/company/MyWebsite"
]
},
{
"@type": "WebSite",
"@id": "https://MyWebsite.org/#website",
"url": "https://MyWebsite.org/",
"name": "MyWebsite.org",
"description": "An evergreen resource exploring one central topic through six related dimensions.",
"inLanguage": "en",
"publisher": { "@id": "https://MyWebsite.org/#organization" },
"hasPart": [
{ "@id": "https://MyWebsite.org/Silo1/SiloPageTier2.html" },
{ "@id": "https://MyWebsite.org/Silo2/SiloPageTier2.html" },
{ "@id": "https://MyWebsite.org/Silo3/SiloPageTier2.html" },
{ "@id": "https://MyWebsite.org/Silo4/SiloPageTier2.html" },
{ "@id": "https://MyWebsite.org/Silo5/SiloPageTier2.html" },
{ "@id": "https://MyWebsite.org/Silo6/SiloPageTier2.html" }
],
"potentialAction": {
"@type": "SearchAction",
"target": "https://MyWebsite.org/search?q={search_term_string}",
"query-input": "required name=search_term_string"
}
},
{
"@type": "WebPage",
"@id": "https://MyWebsite.org/",
"url": "https://MyWebsite.org/",
"name": "Home",
"isPartOf": { "@id": "https://MyWebsite.org/#website" },
"about": { "@type": "Thing", "name": "Main Topic and Six Related Dimensions" },
"mainEntityOfPage": "https://MyWebsite.org/"
}
]
}
Tier 2 – Silo Page
{
"@context": "https://schema.org",
"@type": "WebPage",
"@id": "https://MyWebsite.org/Silo1/SiloPageTier2.html",
"name": "Tier 2 Silo Page",
"hasPart": [
{ "@id": "https://MyWebsite.org/Silo1/First-HubPageTier3.html" },
{ "@id": "https://MyWebsite.org/Silo1/Second-HubPageTier3.html" },
{ "@id": "https://MyWebsite.org/Silo1/Third-HubPageTier3.html" },
{ "@id": "https://MyWebsite.org/Silo1/Fourth-HubPageTier3.html" },
{ "@id": "https://MyWebsite.org/Silo1/Fifth-HubPageTier3.html" }
],
"about": { "@type": "Thing", "name": "Main Silo Subject" }
}
Tier 3 – Hub Page
{
"@context": "https://schema.org",
"@type": "WebPage",
"@id": "https://MyWebsite.org/Silo1/First-HubPageTier3.html",
"name": "Tier 3 Hub Page",
"isPartOf": { "@id": "https://MyWebsite.org/Silo1/SiloPageTier2.html" },
"hasPart": [
{ "@id": "https://MyWebsite.org/Silo1/ArticleTier4-PageOne.html" },
{ "@id": "https://MyWebsite.org/Silo1/ArticleTier4-PageTwo.html" },
{ "@id": "https://MyWebsite.org/Silo1/ArticleTier4-PageThree.html" },
{ "@id": "https://MyWebsite.org/Silo1/ArticleTier4-PageFour.html" },
{ "@id": "https://MyWebsite.org/Silo1/ArticleTier4-PageFive.html" },
{ "@id": "https://MyWebsite.org/Silo1/ArticleTier4-PageSix.html" }
],
"mentions": [
{ "@id": "https://MyWebsite.org/Silo1/SiloPageTier2.html" }
],
"about": { "@type": "Thing", "name": "Topic Overview" }
}
Tier 4 – Article Page One
{
"@context": "https://schema.org",
"@type": "WebPage",
"@id": "https://MyWebsite.org/Silo1/ArticleTier4-PageOne.html",
"name": "Article Tier 4 - Page One",
"isPartOf": { "@id": "https://MyWebsite.org/Silo1/First-HubPageTier3.html" },
"about": [
{ "@type": "Thing", "name": "Subject A" },
{ "@type": "Thing", "name": "Subtopic A1" },
{ "@type": "Thing", "name": "Category Group A" }
],
"mainEntityOfPage": "https://MyWebsite.org/Silo1/ArticleTier4-PageOne.html"
}
Thanks for all you are doing.
@dan just looking for an update.
@dan just bumping this.
I can see what you’re aiming for, but this is a pretty big setup and it’ll take some time to map everything out properly. I don’t have the bandwidth to sit down and run through all the details right now.
Best approach is to break it into smaller pieces and build it step by step. That way you can adjust things as you go and avoid getting stuck on the whole thing at once.
And just to confirm the above is possible to build in Elements using the built-in components and probably a sprinkling of custom components/code.
Thanks for the response Dan. I have no idea what you are talking about here. The need is now. I’m not sure what “smaller pieces and build it step by step means.” I assume you are talking about manually building it.
My take away. I can do anything if I custom component the app. Which is not a solution I can do. I am a html/css guy. That’s it.
Argh 
this is so frustrating for people who have large websites and real navigation needs.
The frustration seems to be coming from not having a clear handle on how Elements works yet, which is fair. It is a different way of building and it takes a bit of time to get comfortable with it.
Before jumping into something this large, it is worth spending some time getting familiar with the basics and building up from there. Every app has a learning curve and trying to solve the whole thing in one go is only going to make it feel really tough.
I am not suggesting you switch tools, but if you already know another builder well and the project is time-critical, that might be the quicker path for this specific job…