Three JSON-LD blocks on a page are not automatically a problem. They may describe three different visible things, such as the main content and its breadcrumbs. The issue is when blocks repeat or conflict about the same entity—or describe content that readers cannot see. Inspect what each block represents before removing anything.
When multiple JSON-LD blocks are—and are not—a problem
JSON-LD is one way to add structured data to a page; the number of script tags alone does not determine whether the markup is correct. Google documents both related items nested together and individual items specified separately. Its example includes a Recipe and a BreadcrumbList on the same page. Google’s structured data overview recommends JSON-LD when a site’s setup permits it, but also supports Microdata and RDFa when correctly implemented. Changing formats does not, by itself, identify or remove duplicate output.
As an Amazon Associate I earn from qualifying purchases.
| What you find | What to do |
|---|---|
| Blocks describe different things visible on the page | They may both be appropriate. Keep accurate items and make their relationship clear where useful. |
| Blocks repeat or conflict about the same entity | Trace each copy to the component generating it, then correct redundant or conflicting output. |
| Markup describes information readers cannot see, or does not match the page | Correct or remove it so the structured data accurately represents visible content. |
Google’s general structured data guidelines say markup should represent the page’s visible content and be placed on the page it describes. They also recommend consistent structured data across duplicate pages for the same content. That is different from repeating an entity in multiple blocks on one page.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →How to find what is generating the repeated markup
- Inspect the rendered page. Open the affected URL’s rendered HTML, not just the content editor. Find every
application/ld+jsonscript and note its@typeand the entity it describes. Record identifiers such as@id,url, andname. Also check whether Microdata or RDFa is present; duplicate structured data can appear in another format too. - Classify each item by subject. Ask whether each block describes a distinct thing a reader can see, or whether two blocks describe the same thing. For distinct related items, Google’s guidance allows nesting or separate items; an
@idcan express a relationship between separate items. Do not merge blocks merely to reduce the script-tag count. - Trace repeated items to their generators. Check the theme or template, CMS plugins, apps, widgets, and custom code that could emit structured data. Identify which component outputs each copy before changing settings or code. The right fix depends on the site’s actual setup; there is no universal setting that removes duplicates across all CMSs.
- Correct the source of the extra or conflicting output. Adjust the responsible component so each item is emitted appropriately. Preserve distinct, accurate items; remove or correct only redundant or misleading output.
- Review the result against the page. Confirm that the remaining markup describes information readers can actually find on the page and follows the requirements for its specific structured-data feature.
Special case: repeated WebSite markup for a site name
If the blocks include multiple WebSite items on a home page and the issue is the site name shown in Google Search, use Google’s feature-specific guidance. It advises adding the name properties to the existing WebSite node where possible rather than adding another WebSite block. Site-name markup belongs on the home page of the domain or subdomain, and Google supports one site name per domain or subdomain. See Google’s site-name documentation.
#1 Best Overall
Do not confuse repeated markup on one page with duplicate home pages for the same content. For duplicate versions such as HTTP and HTTPS or www and non-www, Google recommends using the same structured data across the duplicate pages. That guidance does not mean you should repeat the same entity in several blocks on a single page.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Validate the deployed page, not just the markup you intended to publish
- Use Google’s Rich Results Test during development to check supported rich-result markup.
- After deployment, review the relevant Search Console status reports and use URL Inspection to see how Google reads the page.
- For site-name markup, Google’s documentation points to the Schema Markup Validator because site names are not supported in the Rich Results Test.
- After making a change, allow time for Google to recrawl. Its site-name guidance says discovery can take days to weeks and identifies URL Inspection as a way to request a recrawl.
A tool’s valid result only confirms what that tool checks. Google says structured data may make a page eligible for a search feature, but does not guarantee that the feature will appear; its systems may choose another feature or a text result. Validation does not promise a ranking change or more traffic.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Free tools Windows power users keep installed
One-click scans. No signup required.
