Updates / Documentation
What you need
JSON-LD Schema Manager (JLSM) runs inside SitecoreAI. You need a SitecoreAI site, a few hours of developer time, and content that is set up so each kind of page can carry its own schema.
In short
- A SitecoreAI subscription, and someone who can install apps from the SitecoreAI Marketplace ↗.
- A developer or Sitecore partner for a few hours, to install and configure the app in your Sitecore tenant.
- A site that uses page designs and partial designs.
- The more your content is organised by type, the more JLSM can do for you.
Is your site ready?
Tick each one that is true for your site today.
- Your site runs on SitecoreAI.
- Someone in your team can install apps from the SitecoreAI Marketplace.
- You have a developer or Sitecore partner who can give a few hours.
- Your site uses page designs and partial designs.
- Your key content types, such as articles, products or events, each have their own page template.
- Key facts, such as titles, images and dates, sit in their own fields.
Most sites tick four or five. Page designs and separate templates for key content types are the ones that matter, and your developer closes the rest during set-up.
Want to know what your site publishes today, what is missing, and what JLSM would add? Request a free schema gap analysis and we send you the findings.
Request a free schema gap analysis
How do I use it
JLSM includes an onboarding guide, inside the app, with step-by-step instructions for your marketing team and your technical team. Each team sees what it needs to do, and in what order.
- Map your content model. Which page templates carry which kinds of content, and where the key facts sit. Half a day with your content team, before anyone opens the app.
- Get ready. What your team does while your developer installs the app and connects it: gather your organisation facts, clear out any old schema, and decide which content types come first. The Getting ready guide is inside the app.
- Set up in a day. The first day, start to finish. By the end, your organisation, website and page facts are on every page, and your first content graphs are in place. The Set up in a day guide is inside the app.
Technical requirements
For your developer or Sitecore partner.
| Requirement | Why | Status |
|---|---|---|
| SitecoreAI | JLSM is a SitecoreAI Marketplace app | REQUIRED |
| Rights to install Marketplace apps | Someone installs JLSM and connects it to your project and site collection | REQUIRED |
| A head application JLSM can render into | Your developer adds the jlsm-jsonld placeholder to each layout (one to three on most sites, about 15 minutes) and a rendering component from our reference examples for React, Next.js or Blazor |
REQUIRED |
| Page designs and partial designs | Every graph reaches your pages as a partial design, added to a page design | REQUIRED |
| Publishing through Experience Edge | JLSM reads its configuration at publish time | REQUIRED |
| A page template for each key content type | Each graph maps to the fields of one kind of page | RECOMMENDED |
| Facts in their own fields | A property maps to one field. A fact inside a rich text field cannot be mapped | RECOMMENDED |
How it reaches your pages
You build graphs in JLSM. Each graph becomes a partial design in Sitecore, and Sitecore does the rest through the page designs and page templates your site already uses.
Works best with content organised by type
JLSM works on any SitecoreAI site that uses page designs. The value grows with the number of content types you can tell apart. A graph maps to the fields of one kind of page, so a site with separate templates for articles, products and advisers gets a Article Graph, a Product Graph and an Adviser Graph, each with the schema that fits.
If most of your content sits on one or two general templates, every page gets similar schema. You can still publish your organisation, website and page facts on every page. Adding templates for your main content types later lets you go further.
Good to know
- Version 1 covers one site collection.
- Multilingual sites are handled automatically. Each page publishes in its own language.
- JLSM is built for desktop use.
Beyond the basics
Some schema belongs on components, such as breadcrumbs, FAQs and locations lists. Your development team or Sitecore partner can add this on top of SitecoreAI. See For Sitecore partners.
Questions
Yes, for a few hours. Your developer adds a placeholder called jlsm-jsonld to each of your layouts, then a rendering component from our reference examples. After that, your marketing team does the work in the app.
No. JLSM is built for SitecoreAI only at this time. We have ideas on how to extend it to Sitecore XP, and we welcome expressions of interest. Please get in touch to discuss your requirements.
You can still publish your organisation, website and page facts on every page. Add templates for your key content types later to go further.
Yes. Each page publishes in its own language.
Version 1 covers one site collection. See Pricing for the Project and Organisation plans.