For Sitecore partners and development teams

Run your services on our engine

Every brand needs structured data, and until now every one of them needed a developer to hand-code it, template by template. JSON-LD Schema Manager takes that grunt work off your bench, so your team can spend its hours where the margin is.

Where you add value

One engine, every site, and a customer who is getting fast results

The app handles the mapping, the vocabulary, the validation and the publishing. You advise clients on what to mark up, shape content types and taxonomies to carry it, and build the custom pieces a product cannot.

Strategy and configuration

Your clients will look to you for guidance on what to mark up and in what order, how to set it up properly, and how to keep it valid as the site changes. That is recurring advisory work, and the app lets you deliver it in days rather than sprints.

Build custom components

Every customer is different. They will need your knowledge to map specialised components, complex nested structures and unique content models. One-off build work, scoped and priced by you.

A reference design, not a requirement

The app emits JSON into a data source field, and we supply a component design that renders it. Implement it your way to fit the client’s architecture.

Component-level JSON-LD

Some schema belongs to a component, not a page

JLSM maps schema to page templates, so it covers what is true of the whole page. Some structured data belongs to one component on the page instead, such as a breadcrumb trail or a list of FAQs. Your team builds these.

  • Breadcrumbs, as BreadcrumbList
  • FAQs, as FAQPage
  • Lists, as ItemList
  • Step-by-step instructions, as HowTo
  • Locations lists, as LocalBusiness for offices, branches, dealers and stockists

Your team can build these quickly on top of SitecoreAI, within the client’s own architecture. The client then maintains them in Sitecore as normal.

JLSM plans some component-level options over time. Sitecore builds and components vary too much for one solution to fit every site, so this is work that suits a partner who knows the build.

The reference rendering

Built to be customised

A developer adds a rendering component from our reference examples for React, Next.js or Blazor, and registers it in Sitecore. The JSON-LD is then part of the page HTML.

  • You are free to implement the rendering your way, to fit the client’s architecture.
  • Customising the rendering does not stop your client taking product updates.
  • The configuration stays as content items in the client’s own content tree.

FAQs from partners

Can I customise the rendering component?

Yes. The reference rendering is a starting point. Customising it does not stop your client taking product updates.

Does each client need their own licence?

Yes. Each client needs their own licence.

Can we manage several client sites on one tenant?

Richard and Tim to answer.

Where do I get the reference examples?

Richard to answer.

Working with a client who needs something the product does not do?

Get in touch and we will walk you through the customisation points for their specific implementation, and talk about how we work with partners.

Rejoining the server...

Rejoin failed... trying again in seconds.

Failed to rejoin.
Please retry or reload the page.

The session has been paused by the server.

Failed to resume the session.
Please retry or reload the page.