JSON-LD Formatter

JSON-LD is JSON that uses keys such as @context and @type to describe an entity. It usually sits in a script element. Indentation does not change the meaning. A syntax error can make a crawler ignore the whole script.

What you get from JSON-LD Formatter is concrete. The snippet is indented without changing the keys. A parse error stops a bad snippet from looking valid. The JSON-LD stays in the browser. Read those results before you paste them into a template, a file, or a ticket. A copied mistake is harder to see later than a mistake still on this page.

A careful pass on JSON-LD Formatter looks like this. Start with real input, not a placeholder you do not understand. Paste the JSON-LD object. Then check the middle of the form, because that is where optional fields change the output. Read the indented JSON. Finish by reading the whole result, not only the first line. Fix the text if a parsing error is shown.

The limit is the part people skip on JSON-LD Formatter. Match the output to the input you actually typed, then decide whether it belongs on the live site. Paste the JSON object itself if the parser complains about the tag. A parse error stops a bad snippet from looking valid.

A second reading of JSON-LD Formatter is worth it because the first pass is easy to rush. Say out loud what the output is claiming. The snippet is indented without changing the keys. A parse error stops a bad snippet from looking valid. The JSON-LD stays in the browser. Then say what it is not claiming. No. It only changes whitespace, unless the JSON could not be parsed. Paste the JSON object itself if the parser complains about the tag. No. Indenting happens in the browser. If those two speeches disagree, change the input or pick a different tool. JSON-LD Formatter will not resolve the disagreement for you.

Read JSON-LD Formatter once more as a single job. Part 1: Paste the JSON-LD object. Part 2: Read the indented JSON. Part 3: Copy it back into a script type application/ld+json. Part 4: Fix the text if a parsing error is shown. You should be able to point at this in the result: The snippet is indented without changing the keys. You should be able to point at this in the result: A parse error stops a bad snippet from looking valid. You should be able to point at this in the result: The JSON-LD stays in the browser. Does formatting change my @type? No. It only changes whitespace, unless the JSON could not be parsed. What if the paste includes a script tag? Paste the JSON object itself if the parser complains about the tag. Is the snippet sent away to be formatted? No. Indenting happens in the browser. Who is JSON-LD Formatter for? JSON-LD Formatter is for someone already doing developer tools work who needs beautify and validate JSON-LD structured data snippets. JSON-LD is JSON that uses keys such as @context and @type to describe an entity. It usually sits in a script element. Indentation does not change the meaning. A syntax error can make a crawler ignore the whole script. The first field was filled with a real value: Paste the JSON-LD object. The result was read: The snippet is indented without changing the keys. Optional fields were either filled or left empty on purpose. The copy went into the place the last step names. The boundary in the guide was respected before anything was published.

Keep JSON-LD Formatter as this step only. When the job moves on, the JSON Formatter is the next page: JSON Formatter pretty-prints JSON you paste, or minifies it, and names a parse error when the JSON is invalid. The SHA256 Generator covers a different piece of the same work: SHA256 Generator hashes text you type into a 64-character hexadecimal SHA-256 digest.