Google changes how it parses double-escaped JSON-LD entities

Google has modified the way it extracts JSON-LD information, bringing it extra according to JSON and different net requirements. As Google Search Central introduced on LinkedIn, Google will solely do a single move of HTML unescaping.

What builders ought to know

If builders are utilizing JSON-LD for structured information, it’s time to replace your code. As an alternative of counting on double-escaped entities, change to plain JSON escapes or Unicode hexadecimal escapes.

Since Google’s parser now solely unescapes as soon as, any code that relied on double-unescaping gained’t work the way in which it used to.

Google Search Central posted about this on LinkedIn:

“To deliver our parser as much as JSON and different requirements, we modified our JSON-LD extraction and are actually solely making use of a single move of HTML unescaping. Virtually talking, because of this double-escaped entities (like & or ✔) will not be unrolled. Should you’re utilizing JSON-LD for structured information, you’ll want to replace your code to plain JSON escapes or Unicode hexadecimal escapes (like u0026).”