Validate JSON Before Using It as JSON-LD

Use four checks, not one

A document can be valid JSON and still be wrong for its intended contract. It can match a generic schema and still use the wrong vocabulary for a web page. It can even pass a structured-data test without earning a particular search appearance.

The reliable order is JSON syntax, schema-contract conformance, JSON-LD meaning, and then the requirements of the target platform or search feature.

1. Confirm that the JSON parses.
2. Validate required fields, types, and nested structures against the intended schema.
3. Review context, type, properties, and page accuracy.
4. Test the requirements of the target platform and the rendered production URL.

Start with valid JSON

JSON uses double-quoted names and strings, matching braces and brackets, commas between members, and a small set of value types. Single quotes, trailing commas, comments, and invalid escaping are common reasons a copied example fails.

Fix syntax first. A structured-data checker cannot reliably interpret a document that a JSON parser cannot read.

{
  'name': 'Example Guide',
  'url': 'https://example.com/guides/example',
}

{
  "name": "Example Guide",
  "url": "https://example.com/guides/example"
}

Validate the expected data contract

Parseable JSON can still omit required fields or use the wrong value type. A JSON Schema can describe the contract through required properties, types, patterns, enumerations, and nested rules.

Use the schema draft and contract your workflow actually expects. UtilityDock's validator supports a supplied draft-07 schema; passing that test proves conformance to that schema, not automatic Schema.org or search-feature correctness.

{
  "name": "Example Guide"
}

{
  "name": "Example Guide",
  "url": "https://example.com/guides/example"
}

Review what the JSON-LD means

JSON-LD adds linked-data meaning through terms such as @context and @type. Confirm that the vocabulary, type, properties, nested objects, URLs, and images accurately describe the visible page.

A schema maintained by your team can enforce an expected structure, but it does not automatically establish that every vocabulary choice or page claim is appropriate.

Test the target feature and live URL

Search platforms can impose requirements beyond basic JSON-LD validity. Review the current documentation for the exact feature, test the markup, publish through the normal release process, and then inspect the rendered URL.

Correct markup can make a page eligible for a feature, but it does not guarantee crawling, indexing, rankings, traffic, or a rich result.

1. Format and parse the JSON.
2. Validate the instance against the intended schema.
3. Review JSON-LD context, type, properties, and nesting.
4. Confirm that values match visible page content.
5. Test feature-specific requirements.
6. Test the rendered production URL and monitor after later changes.

Common questions

FAQ