How to include json-ld data in eleventy?

[ironfish1000]

Hi, I am using the 11ty / eleventy-base-blog at:
github.com/11ty/eleventy-base-blog

I am trying to add some basic json-ld to pages.

In an include .njk file that is included in base.njk I have tried:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "name": "{{ metadata.title }}",
  "url": "{{ metadata.url }}"
}
</script>

and

{% raw %}
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "name": "{{ metadata.title }}",
  "url": "{{ metadata.url }}"
}
</script>
{% endraw %}

and

<script type="application/ld+json">
{{ {
  "@context": "https://schema.org",
  "@type": "WebSite",
  "name": metadata.title,
  "url": metadata.url
} | dump | safe }}
</script>

and none of them are outputted.

I also tried this directly in base.njk and it also is not outputted:

    <!-- Schema for site in base.njk -->
    {% raw %}
    <script type="application/ld+json">
    {
      "@context": "https://schema.org",
      "@type": "WebSite",
      "name": "{{ metadata.title }}",
      "url": "{{ metadata.url }}"
    }
    </script>
    {% endraw %}

I have tried searching and asking AI and not getting a solution.

What is the best way to output this?

Thanks ahead of time for any help.

[Ryuno-Ki]

I can see how this was surprising behaviour. I had to poke the base blog myself to figure out what was going on. It is not occuring in other Eleventy projects (that is: you have to configure it to use bundling to observe this).

https://github.com/11ty/eleventy-base-blog/blob/d84d3fb36419581448f0ba69474b897e5b3bedc4/eleventy.config.js#L47-L53

is bundling all <script> elements. You can use the escape hatch by adding eleventy:ignore to make it show up where you placed it:

<script eleventy:ignore type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "name": "{{ metadata.title }}",
  "url": "{{ metadata.url }}"
}
</script>

[ironfish1000]

@Ryuno-Ki Thanks very much for your quick and very helpful reply! - that works like a charm! I appreciate you digging thru the code because I would never have found this. Sorry for my late response, I had trouble logging in to github until now.