en
/login
Koval SEO

Structured data absent on a captured duplicate variant

In the reportDuplicate page variants missing the canonical's structured data

structured_data_missing_on_duplicate_variants · Review item

Short answer

Put the relevant structured data on each duplicate page that describes the same content.

Severity: Notice. Review item: a conservative static comparison, not an indexing, penalty or rich-result eligibility judgment.

Why it matters

Google recommends placing the same structured data on duplicate pages, including variants that point to a canonical page.

What to do

  1. Compare the two captured pages and their structured data before copying markup.
  2. Add the relevant structured data to the same variant URL.
  3. Run another full audit. Exact captured JSON-LD copies with equal expanded values can demonstrate a fix in the supported subset.

When to leave it as it is: Keep valid distinct content and markup. A canonical link alone does not establish duplicate content.

What we read

Original retained current-200 HTML from the same audit and registered origin, with server-rendered source coverage.

The existing extractor’s normalized, casefolded extracted-text hash, recomputed from source-bound bytes; qualified HTML-head canonicals.

Complete supported typed and original JSON-LD inventories on both pages; original declaration excerpts and byte ranges on the canonical target.

Example & evidence

Illustrative same-content variant receiving the target’s markup.

Canonical page: Product JSON-LD.
Duplicate variant: same extracted text and rel=canonical, no structured data.
Both pages: the same relevant Product JSON-LD.

Confirm & check again

Check for yourself: Read the captured canonical target, original markup samples and the missing variant URL in the finding.

Check again: Full audit — Use the next full audit and shared lifecycle. Incomplete coverage never proves a fix.

Limits & sources

This compares normalized extracted text, not browser-rendered visibility, layout or full semantic equivalence.

Only total markup absence on a qualified canonical variant fires. Missing canonical targets, foreign origins, partial/render-shell source and untyped or unsupported markup remain unknown.

Other nonempty markup is not an automatic fix. The supported positive fix requires exact original JSON-LD declaration copies and equal expanded values. Microdata/RDFa correspondence is not established.

Losing the duplicate relationship or changing text does not prove the former markup problem fixed. The missing URL keeps its identity even when the peer changes.

Findings from known pairs may remain beside incomplete scope, but insufficient coverage cannot reconcile them.

Confidence: Medium Medium for the conservative captured canonical pair and original markup absence; no rich-result or penalty conclusion.

Sources

  • Google Search Central, General structured data guidelines — Location guidance recommends the same structured data on duplicate pages, including noncanonical variants. Checked 5 October 2026.

Editorial review: 2 November 2026