Hi all,
Does anyone know how I can fix this duplication? Seems to be across all my products. Thanks in Advance
Hey @Chuckachucka
I had a look at your product page source and found the cause. You’ve got 4 separate product schema blocks on the page, and they all use the same product id, so Google merges them into one and finds conflicting data.
That’s where the duplicate “brand” comes from, three of them set a brand and they don’t even match (“thegoodpaw” in two and “The Good Paw” in the other). The offers are also set up differently in each one, which is what’s causing the “invalid object type” warning, and your return policy says 30 days in one and 14 days in another.
Quick heads up on where they’re coming from, two of them look like your theme’s built in schema being output twice, and the other two look like they were added manually at some point. You’ve also got two Organization schemas with different names, not causing this error but worth cleaning at the same time.
The fix is to keep just one product schema with the correct info merged into it (right brand name, correct return days, shipping and reviews) and remove the rest. Since it’s across all your products, it’s coming from the theme code rather than individual product settings.
If you’d like, I can sort it for you and clean it all up properly.
Cheers,
Moeed
Hey @Chuckachucka
All sorted mate. The duplicate brand error is gone and your product page now shows as a valid item in the Rich Results Test.
Quick summary of what was done:
- Removed the 4 separate product schemas and replaced them with one clean one
- Brand is now consistently “The Good Paw”
- Fixed the invalid return policy value
- Cleaned up the duplicate Organization schema too
Since it’s all in the product template, the fix applies to every product in your store, not just this one.
One thing left on your end, this product doesn’t have a description in admin, which shows up as a small warning. Just add a short description to the product and that’ll clear it.
Last step, go to Search Console, Enhancements, Merchant listings, open the duplicate brand error and hit Validate fix so Google recrawls your pages.
Hope that helps! If it did, a Like and Marking it as Solution goes a long way and helps others find the fix faster too.
Cheers,
Moeed
Thanks Moeed! I will try recrawl to see if the reviews get pulled through.
My name is Francesco Guiducci and I’m the founder of IFG eCommerce.
The duplicate Product data is definitely the area I would investigate, but I would be careful with simply deleting three schema blocks and keeping one.
Having more than one JSON-LD script on a page is not automatically a problem. The real issue is when different scripts describe the same Product or Organization with conflicting values, which seems to be what is happening here with the brand, offers and return policy.
Before removing anything, I would identify exactly who owns each block.
On a Shopify product page, structured data can come from the theme itself, a manually added Liquid snippet, an SEO app, a reviews app or another integration. Search the rendered page source for application/ld+json, then compare the Product blocks and trace each one back to the theme or app producing it.
I would do that work on a duplicated theme rather than editing the live theme directly.
The reason this matters is that one block might contain the basic Product data while another app is supplying something useful such as reviews. Removing the wrong one can make the duplication warning disappear while also removing valid structured data you wanted to keep.
The end goal should be one coherent description of the product, with consistent identifiers, brand, offers, availability, shipping or return information and any review data that is genuinely present on the page.
Once cleaned up, test a representative product URL with Google’s Rich Results Test and inspect the live URL in Search Console. Then check both the Product snippets and Merchant listings reports after Google has recrawled the pages.
Since you said this happens across the whole catalogue, fixing the source at theme or app level is much better than trying to correct individual products.