Discussion starter: an entity SEO question, posted with an answer from Niraj Raut to open the thread. If you have dealt with this on a site, reply with what you saw, especially where it differs.
- Entity SEO
- Structured Data
- WordPress SEO
Yoast, WooCommerce and a schema plugin all output markup on one page. Have duplicate or contradictory entities ever caused visible problems?
Disclosure: Niraj Raut, who posted this answer, runs the SEO consultancy linked at the end of it.
1 reply
-
adminAdmin
Yes, overlapping plugins are one of the most common causes of structured data problems on WordPress and WooCommerce sites, and the problems are visible when you look in the right places. Typical symptoms are two or three Product entities on one page, one with a price and one without; conflicting Organization details such as different names or logos; duplicate aggregate ratings; and errors in Search Console’s merchant listing or product snippet reports caused by the incomplete duplicate. Google may choose one of the entities, merge them imperfectly or treat the page as having invalid items, which can cost rich results. The fix is to decide which tool owns each entity type and switch off the others’ output for that type.
How the conflicts arise
SEO plugins generate a structured data graph describing the site, organisation, page and author. WooCommerce outputs its own Product markup. Dedicated schema plugins add their own entities, often for the same things. Each works correctly in isolation. Together, they describe the same product or organisation several times with slightly different data, and without shared identifiers linking them into one entity.
Common problems and their symptoms
Problem Where you see it Two Product entities, one missing price or availability Merchant listings report errors for missing fields; Rich Results Test shows two items Conflicting Organization name or logo Inconsistent logo or name in search features; validator shows multiple organisations Duplicate or conflicting aggregate ratings Review snippet warnings; ratings that do not match the page Breadcrumbs defined twice with different paths Inconsistent breadcrumbs in results Author or Person entities duplicated with different URLs Ambiguous authorship in the graph Diagnosing it
- Run key templates, such as product, category, article and homepage, through the Rich Results Test and a general schema validator. Count the entities of each type.
- View the page source and identify which plugin produced each JSON-LD block, usually from comments or class names in the output.
- Check Search Console’s merchant listings, product snippets, review snippets and breadcrumb reports for errors that appear on many pages at once.
- Compare the values in each duplicate with what the page shows.
Fixing it
- Assign ownership per entity type: for example, the SEO plugin owns Organization, WebSite, WebPage and BreadcrumbList; WooCommerce or an integration add-on owns Product.
- Disable duplicate output in the other plugins through their settings, or remove the redundant plugin.
- Use integrations designed to merge graphs where available, so product data joins the main graph with shared identifiers rather than sitting beside it.
- Connect entities with
@idreferences so the product’s brand, the page’s publisher and the organisation are one consistent graph. - Validate again on every template and after every plugin update, since updates sometimes re-enable output.
Hypothetical example:
A WooCommerce store uses an SEO plugin, WooCommerce’s default markup and a separate schema plugin added by a previous developer. Search Console’s merchant listings report shows thousands of items with “missing field price”. The Rich Results Test shows two Product entities per page: WooCommerce’s, which is complete, and the schema plugin’s, which has no offer. The store removes the schema plugin, uses the SEO plugin’s WooCommerce integration so product data joins the main graph, and revalidates. The missing-field errors clear as pages are recrawled, and merchant listing eligibility is restored for those items.
Watch for this:
Custom markup added through themes or tag managers can conflict with plugin output in the same way, and it is easy to forget. Include theme files and tag manager containers in the audit, not only plugins.
What the page shows must match the markup
Resolving duplicates is only half the job. Whichever source owns the Product entity, its values must match the visible page: the same price, currency, availability and rating count. Google’s merchant listing documentation says it may verify structured data against the page and feed, and mismatches lead to warnings or disapproved items. Sale prices, variant prices and out-of-stock states are where plugins most often disagree with the page, because they read different fields. Test those cases specifically: a product on sale, a product with variants at different prices and a product out of stock, and compare what each tool outputs with what a shopper sees.
Keep it governed
Document which tool owns which entity type, and add a structured data check to the release process: a validator run on each template after plugin, theme or WooCommerce updates. Plugin updates are frequent, and a single update can reintroduce duplicate output months after you fixed it.
Audit each template for duplicate entities, give each entity type one owner, switch off the rest, connect the graph with shared identifiers, and revalidate after updates. Overlapping plugins cause real, visible problems, and they are among the easiest structured data issues to fix once found.
Need help with this on your own site?
Niraj Raut works with businesses in Nepal, Australia, the UK, Europe and the US on technical SEO, ecommerce SEO, local SEO and AI search.
Add a reply Cancel reply
Replies are open to approved members. Log in or apply to join.