How to add json-ld property to page metadata for pages in EDS with Universal Editor

It sounds like you’re running into the common confusion between how AEM (Adobe Experience Manager) handles metadata via page.json and how JSON-LD needs to be rendered for SEO.

When you define a property in page.json, AEM by default maps that into

. That’s why you’re seeing your schema data show up as a meta tag instead of a 

block.

To get JSON-LD working correctly for SEO, you don’t want to store the raw schema directly as a page property. Instead, you should:

1. Store the schema content (as text or JSON) in a property of the page/component.

2. Create a component (or use a custom HTL script) that outputs this property wrapped in:

    

    

This way, AEM renders it exactly as required by search engines.

If you’re using AEM’s Core Components, you could extend the Page component to include a JSON-LD rendering hook. Otherwise, add a simple custom component to your page template that reads the schema property and outputs it with the correct 

wrapper.

So in short:

• Adding schema to page.json directly will always render as

 → not suitable.

• Instead, store schema as a property and output it with a dedicated 

block in your page.

That should align with Adobe’s documentation and ensure the schema is picked up properly by crawlers.

Strony internetowe Nowy Tomyśl

@seshasai are you using Document based authoring or AEM EDS Sites?

If you are using document based authoring, you can use metadata section to author JSON-LD schema as below screenshot..