Inventory items before blaming duplication
Save the public page output and list each structured-data item by type, identifier when present and important properties. Include nested items rather than counting only script tags. Two scripts can describe different things, while one script can contain several conflicting descriptions.
Google permits multiple relevant items on a page, including nested or separate items. Therefore the number of blocks alone is not a defect. First establish which items describe the same real thing and which describe distinct things, such as the article, its publisher and its navigation trail.
Build a producer map
For each suspected item, record the plugin, theme setting or custom component believed to generate it. Label uncertain attribution as unconfirmed. A familiar class name or position in the HTML is a clue, not enough evidence to remove a component from production.
Use a staging copy and preserve the starting configuration. Change one relevant output setting at a time, compare the generated page and restore it before the next diagnostic change when needed. Prefer a specific schema-output control over disabling an entire plugin whose other functions the site relies on.
Compare facts and relationships
Group descriptions that refer to the same item and compare their names, URLs, dates and relationships against approved page content. Identify the exact contradiction: for example, one publisher description may use an obsolete website while another uses the current one. A repeated correct value is different from a contradictory value.
Where identifiers are used to connect related items, check that they consistently refer to the intended entity. Do not assign one shared identifier to unrelated businesses simply to reduce the count. Google’s guidance describes using identifiers to link related items; the relationship still needs to make sense in the page context.
Illustrative example: two publisher sources
Imagine a fictional article template and an SEO plugin both supplying publisher information. The template retains an old brand URL, while the plugin contains the owner-approved current URL. A staging comparison confirms which setting produces each description before the developer chooses a single maintained source for that publisher information.
The developer keeps the article and breadcrumb information that still serve distinct purposes. The test records the old and new output, configuration change and rollback method. This hypothetical example does not claim that every duplicate block is harmful or that removing one improves rankings.
Verify the correction across templates
After the targeted change, test a small representative set: an article, an organization page and any template affected by the same setting. Compare public content and markup, validate the relevant feature and check that unrelated navigation or page functions still work. Retain any valid items that disappeared accidentally.
Record which component now owns each maintained item and where its facts are edited. Recheck after plugin or theme changes that could restore another producer. An audit can reveal conflicting values, but a source map and a controlled comparison establish how to correct them without stripping useful structured information from the site.