JSON-LD invalid

What this means

At least one <script type="application/ld+json"> block on the page contains a JSON syntax error. Search engines and AI crawlers silently skip any block they cannot parse. Every piece of structured data on that page is effectively invisible until the syntax is fixed.

How to fix it

The CLI output includes the parse error message, which typically names the line or character position of the problem. The most common causes are listed below.

Missing comma between properties:

{
  "@context": "https://schema.org"
  "@type": "Organization"
}

Fix: add the missing comma after each property except the last.

{
  "@context": "https://schema.org",
  "@type": "Organization"
}

Trailing comma after the last property:

{
  "@context": "https://schema.org",
  "@type": "Organization",
}

Fix: remove the comma after the last property.

Single quotes instead of double quotes:

{
  '@context': 'https://schema.org',
  '@type': 'Organization'
}

Fix: JSON requires double quotes for all strings and property names.

{
  "@context": "https://schema.org",
  "@type": "Organization"
}

Unescaped special characters in strings:

If a property value contains a double quote, backslash, or control character, it must be escaped with a backslash. The most common case is a description that contains a quotation mark.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "description": "Learn what "schema" means and why it matters."
}

Fix:

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "description": "Learn what \"schema\" means and why it matters."
}

Verify the fix

Re-run orino audit. The schema-invalid-json check should pass. You can also run JSON.parse() on the block content in your browser console to confirm it parses without error.