I’m trying to add JSON-LD Structured Data to my site, and in 0.54 was using this template without issue: <script type="application/ld+json"> { "@context": "http://schema.org", "@type": "WebSite", "name": "{{ $.Site.Title }}", {{- with site.Params.alternatePageName }}"alternateName":…

Found my own fix, though it’s a rather painful workaround. I now have two partial templates: the first provides the actual structured data: { "@context": "http://schema.org", "@type": "WebSite", "name": "{{ $.Site.Title }}", {{- with site.Params.alternatePageName }}"alternateName":…

That works for the specific case of an inline URL, but doesn’t seem to work at all for nested structured data, while piping the top level partial through safeJS does seem to work.

[image] yawpitch: doesn’t seem to work at all for nested structured data That’s pretty much the use case of the topic I linked to as well.

I don’t see any nesting within that topic, at least not like I’m doing where there’s an embedded partial call that brings in another bit of structured data that itself might have URLS. If I use the above trick to fix the URL the resulting partial still comes back all in a single line with newlines …

Thank you for this solution/workaround! I was quite stuck. I hope this is not necessary in future versions of Hugo.

Brillant !!! Thanks a lot I was running crazy. Still efficient in 0.61.0

Hugo 0.55.* breaks structured data rendering

support

pointyfar April 25, 2019, 3:25pm 3

As an alternative: Formatting URL's in JSON string

Topic		Replies	Views
Backslash added to my JSON Structured Data support	5	2170	August 12, 2023
\x26rsquo; bad escape sequence in string for JSON-LD support	13	4066	June 5, 2025
Formatting URL's in JSON string support	11	9524	July 7, 2019
Upgraded from v0.53 to v0.55.6 - breaks schema.org support	3	663	May 26, 2019
Problems with encoding special characters in json+ld ("invalid escape sequence") support	16	14138	July 17, 2019

Hugo 0.55.* breaks structured data rendering

Related topics