Understand structured data, product, and video checks

TechDash extracts JSON-LD from rendered monitored pages, stores a fingerprint and payload, and derives focused Product and video signals. These checks identify parse failures and regressions. A pass can mean valid, unchanged, absent, or baseline stored. It does not prove schema quality, Google eligibility, or rich-result appearance.

Structured data changes

Structured data changed is Advisory change intelligence. It matters because a template release can alter or remove markup used by search features. The first eligible evaluation passes and stores a baseline. It fails when a previously non-empty JSON-LD fingerprint differs from the current fingerprint. A pass means the fingerprint is unchanged or no prior non-empty fingerprint exists, not that the payload follows Google's requirements.

Evidence combines each hash with pretty-printed JSON-LD, but the comparison preview is clipped to 500 characters. The hash establishes that the complete stored payload changed; the preview may omit the changed node or property and is not a full semantic diff. Dynamic prices, availability, ratings, dates, identifiers, ordering, personalization, and consent-dependent output can cause benign changes.

Review the complete current page markup and relevant template data, then confirm whether the change was authorized. Restore accidental removals or malformed generation. Run Check & Verify after deployment. Recovery means the current fingerprint no longer differs from the accepted baseline; Mark Resolved can accept an intentional current payload, but neither outcome validates its SEO quality.

Structured data validity

JSON-LD parse error is Warning because invalid JSON cannot be reliably consumed. It is an absolute-state check: it fails whenever the stored combined JSON-LD payload exists but JSON.parse rejects it. It passes when that payload parses or no JSON-LD was extracted. Absence therefore passes and does not mean structured data is present.

The check returns the parse result but does not identify the exact script block, exact place in the markup, required property, or Google eligibility issue. Required schema properties missing and Gallery schema type removed appear in product documentation but do not currently open in the app. Their absence is not evidence that required properties or gallery types are healthy.

Benign-looking causes such as a truncated render or consent variant still represent what TechDash received and should be reproduced before changing production. Validate every application/ld+json block, fix serialization rather than hand-editing output, and retest with Google's current tooling. Recovery is a parsing pass on Check & Verify, followed by separate Rich Results Test or Search Console validation.

Product attribute regression

This family extracts the first Product node it finds, then the first object in offers or the Product itself. It tracks Product entity presence, price or priceSpecification.price, availability's final token, GTIN variants or MPN, and brand text or brand.name. Losses matter because incomplete commercial markup can reduce product-result eligibility.

The first eligible evaluation stores a baseline. A pass means no previously present tracked value disappeared. A fail occurs when one or more tracked attributes move from present to absent; only the first loss in check order is named:

• Product schema removed, Product price missing, and Product availability missing are Warning.
• Product GTIN or MPN removed and Product brand removed are Advisory.

Evidence summarizes the previous and current extracted values. It does not show which JSON-LD node supplied them, validate types, compare visible content, inspect every Product or Offer, or prove that a changed value is correct. A price changing between two populated values does not trigger this family, although Structured data changed may report it. Benign losses include intentional removal from a non-product page or an out-of-scope variant, but never retain stale values just to pass.

Inspect the full payload and visible product, restore accurate Product and Offer fields, and validate the template. Check & Verify recovers when the lost tracked values are present again or the new state is intentionally accepted.

Video regression

Video or VideoObject disappeared is Warning. Video presence is true when TechDash detects either a recognized embedded player or any VideoObject node. After a baseline, it fails only when prior presence becomes current absence. A pass means video presence is stable or was absent at baseline, not that VideoObject is complete or playable.

Evidence says that video was present and is now missing; it does not identify the prior embed, validate playback, or list required VideoObject properties. Removing VideoObject while leaving a recognized embed passes, as does retaining VideoObject after the player breaks. Consent, geolocation, lazy loading, or an intentional editorial removal can be benign.

Confirm both the rendered player and complete JSON-LD. Restore accurate embed and VideoObject markup when accidental, test playback, and validate required properties. Run Check & Verify; recovery requires either signal to be detected again.

Related articles

• Read before-and-after content, HTML, and JSON differences