Count Structured Data Blocks and Catch Invalid JSON

How to Use This Tool

Parse each application/ld+json block without executing page scripts. Audit JSON-LD blocks in pasted HTML locally, reporting block types and invalid structured-data JSON. Processing stays in the browser.

The failure HTML JSON-LD Audit is designed to catch

A script tag with the right MIME type can still contain malformed JSON that no structured-data consumer can parse. The boundary is the job stated in Count Structured Data Blocks and Catch Invalid JSON; HTML JSON-LD Audit is not intended to score or transform a different workflow.

The HTML JSON-LD Audit input contract

The fields used for this specific operation are Input text, Unused option. Keep the source values beside the HTML JSON-LD Audit result, because replacing the original would remove the evidence needed to reproduce or reverse the operation.

• For HTML JSON-LD Audit, Input text starts at <script type="application/ld+json">{"@type":"Article"}</script> in the worked case; replace that example with the matching source value.
• For HTML JSON-LD Audit, Unused option starts at in the worked case; replace that example with the matching source value.

Worked result for HTML JSON-LD Audit

The executable case called Default browser-only example expects out: Blocks: 1 Article. Verify that observation before entering real material, and then change one HTML JSON-LD Audit field at a time so an unexpected direction or formatting change can be traced to a specific input.

Reading the HTML JSON-LD Audit output

No. The transform runs in browser JavaScript and the page does not call a processing API. Network extensions or a compromised device remain outside this page's control. Apply that answer only when Input text, Unused option describe the same scope and format as the worked operation. If the source uses different units, quoting, nesting, timing or account rules, a plausible-looking HTML JSON-LD Audit output is not sufficient validation.

Assumptions attached to HTML JSON-LD Audit

• HTML JSON-LD Audit assumes that the pasted input uses the syntax described by the selected standard or page guidance.
• HTML JSON-LD Audit assumes that the operation is intentionally narrow and does not infer private downstream schema rules.

If one of these HTML JSON-LD Audit assumptions is false, keep the result as a diagnostic rather than production or decision data, and choose an implementation that explicitly supports the missing rule.

Evidence maintained for HTML JSON-LD Audit

The recorded reference is WHATWG HTML Living Standard. Reopen that source when the definition, format, fee or policy behind HTML JSON-LD Audit changes; private configuration and downstream acceptance still have to be checked in the user's own system.

Where HTML JSON-LD Audit runs

The named operation executes in browser JavaScript without an ecech calculation API. For HTML JSON-LD Audit, local execution reduces transmission but does not control browser extensions, device security or the destination where the result is pasted, so sensitive inputs still require the user's normal handling rules.