PILLAR 4, AUTHORITY NETWORK · 4.1 Structured data validityHighVerified

Unparseable / bad escaping

What it is

Unescaped quotes or special characters inside JSON-LD values break the whole block. Proper escaping keeps the markup parseable. Encoding/escaping breaks the JSON. Same as invalid syntax. Escape correctly; validate. Medium-high. Direct.

Why does unparseable / bad escaping matter for AI search?

Same as invalid syntax.

How do you fix it?

Escape correctly; validate.

How do you find it on your site?

  1. Validate the structured data and look for parse errors.
  2. Find values with unescaped quotes, line breaks or special characters.
  3. Escape them correctly or generate the JSON programmatically.
  4. Re-validate.

Which ranking and citation factors does it touch?

A single bad character can void the entire block. Clean escaping keeps the markup usable.

What is the impact?

Medium-high. Direct.

What is the evidence?

Valid, parseable structured data required. Google Search Central, Structured data general guidelines

Frequently asked questions about unparseable / bad escaping

What does "Unparseable / bad escaping" mean?

Encoding/escaping breaks the JSON.

How do you fix unparseable / bad escaping?

Escape correctly; validate.