Step 5 —Settings=> Schema => Third Party Conflict #
Prevent duplicate schema output by disabling the default schema generated by WooCommerce, Yoast SEO, and Rank Math — allowing SchemaEngine AI to take full control of your structured data.
Navigation Path
| WordPress Admin → SchemaEngine AI → Settings → Schema → Third Party Conflict |
| ⚠️ The Duplicate Schema Problem When multiple plugins each output their own JSON-LD schema markup on the same page, search engines receive conflicting structured data. This is called duplicate schema and it is one of the most common causes of schema validation errors and warnings in Google Search Console. SchemaEngine AI is designed to be your single source of truth for schema markup. Use the toggles on this page to silence the default schema output of any other plugin that may be producing conflicting or redundant structured data. |
Sections on This Page #
5.1. What Duplicate Schema Does to Your Site
5.2. Disable WooCommerce Default Schema
5.3. Disable Rank Math Default Schema
5.4. Disable Yoast SEO Sitelinks Searchbox
5.5. Disable Yoast SEO Default Schema JSON-LD
5.6. Best Practices — One Plugin, Error-Free Schema
What Duplicate Schema Does to Your Site #
Running two or more plugins that each generate schema markup causes a chain of issues that can actively harm your search performance and structured data health. The table below outlines the key problems:
| Issue | Impact | Severity |
|---|---|---|
| Conflicting schema types | Two plugins may output different schema.org types for the same page (e.g. one outputs Product, another outputs Article). Search engines cannot determine which is correct and may ignore both. | High |
| Duplicate JSON-LD blocks | Multiple <script type=”application/ld+json”> blocks with overlapping properties appear in the page source. Google Search Console flags these as errors or warnings in the Rich Results report. | High |
| Invalid property values | Plugin A may set a property (e.g. price) that contradicts what Plugin B sets. This creates invalid structured data that fails Google’s Rich Results Test. | High |
| Rich result ineligibility | Duplicate or conflicting schema can disqualify a page from rich results entirely — meaning no star ratings, no FAQ dropdowns, no product price in search results — even if the data itself is correct. | High |
| Wasted crawl budget | Search engines must parse and evaluate multiple schema blocks per page. On large sites this can slow down structured data processing. | Medium |
| Hard to debug errors | When schema errors appear in Google Search Console, it becomes difficult to identify which plugin caused the issue when multiple plugins are outputting schema simultaneously. | Medium |
| Inconsistent Knowledge Panel | Google may pick up conflicting organization information from two different plugins and show incorrect or outdated details in the Knowledge Panel. | Medium |
| 🔬 How to check for duplicate schema on your site Open any page on your site, view the page source (Ctrl+U or Cmd+U), and search for application/ld+json. If you see more than one <script type=”application/ld+json”> block, you have multiple plugins generating schema. Use the toggles on this page to eliminate the ones you do not need. |
5.1 Disable WooCommerce Default Schema #
WooCommerce ships with its own built-in schema markup for product pages, including Product, Offer, AggregateRating, and BreadcrumbList types. When SchemaEngine AI is also generating Product schema, both sets of markup appear on the same page — causing duplicate schema conflicts.
| Disable WooCommerce default schema Affects: WooCommerce This will disable WooCommerce plugin default schema. When to enable: Enable this toggle if WooCommerce is active on your site and SchemaEngine AI is configured to generate schema for the product post type (via Post Type Mapping). Disabling WooCommerce’s default schema gives SchemaEngine AI full control over product structured data, ensuring a single clean schema output with no conflicts. Default: ONN — third-party schema is active by default until you explicitly disable it. |
💡 Also applies to Easy Digital Downloads (EDD) WooCommerce is the most common e-commerce plugin, but EDD also outputs its own schema markup for download post types. If you use EDD instead of or alongside WooCommerce, disabling WooCommerce schema here covers both platforms’ default output. Verify by checking your page source after enabling this toggle.
5.2 Disable Rank Math Default Schema #
Rank Math SEO plugin includes its own schema generation system — it can output Article, Product, FAQ, BreadcrumbList, and other schema types automatically. If both Rank Math and SchemaEngine AI are generating schema simultaneously, every page on your site will have duplicate JSON-LD blocks.
Disable Rank Math default schema
Affects: Rank Math SEO This will disable Rank Math SEO plugin default schema.
When to enable: Enable this toggle if Rank Math SEO is installed and active on your site. You can continue using Rank Math for all its other SEO features (meta titles, descriptions, sitemaps, redirects, analytics) — this toggle only disables its schema output. SchemaEngine AI then becomes the sole source of schema markup on your site.
Default: ONN — third-party schema is active by default until you explicitly disable it.
✔ You can use SchemaEngine AI alongside Rank Math
Disabling Rank Math’s schema output does not affect any other Rank Math feature. Your Rank Math meta tags, sitemaps, redirects, and analytics integrations remain fully functional. Only the JSON-LD schema blocks that Rank Math injects into page source are disabled. This is the recommended configuration when using SchemaEngine AI as your primary schema plugin.
5.3 Disable Yoast SEO Sitelinks Searchbox #
Yoast SEO includes a Sitelinks Searchbox schema feature that adds a WebSite schema type with a SearchAction property. This was originally used to enable a search box directly within Google search results when your brand name was queried.
| Disable Yoast SEO sitelinks searchbox ⚠ DEPRECATED Affects: Yoast SEO This will disable sitelinks searchbox default by Yoast SEO plugin. When to enable: Enable this toggle on any site running Yoast SEO. The Sitelinks Searchbox feature is deprecated — Google no longer supports or displays this feature in search results as of 2023. The schema markup it generates serves no practical purpose and adds unnecessary JSON-LD output to every page. Disabling it removes dead markup from your site. Default: ONN — third-party schema is active by default until you explicitly disable it. |
| ⚠️ Deprecated Feature — No Longer Supported by Google Google officially deprecated the Sitelinks Searchbox feature in 2023. It no longer appears in search results and the associated schema markup (SearchAction on WebSite type) is ignored by Google’s structured data parser. Recommendation: Enable this toggle to remove the deprecated Sitelinks Searchbox schema output from Yoast SEO. It has no SEO value and contributes unnecessary markup to your page source. |
5.4 Disable Yoast SEO Default Schema JSON-LD #
Yoast SEO outputs a comprehensive set of schema markup by default — including WebSite, WebPage, Organization, BreadcrumbList, Article, and Person types — as JSON-LD blocks injected into every page. When SchemaEngine AI is also generating the same types, every page receives two full sets of schema markup.
| Disable Yoast SEO Default Schema JSON-LD Affects: Yoast SEO This will disable all default schema default by Yoast SEO plugin. When to enable: Enable this toggle if Yoast SEO is installed and you want SchemaEngine AI to be the sole schema generator. This disables all of Yoast’s JSON-LD output site-wide — including its WebSite, WebPage, Organization, BreadcrumbList, and Article schema blocks. All other Yoast SEO features (meta tags, XML sitemaps, redirects, readability analysis, social previews) remain completely unaffected. Default: ONN — third-party schema is active by default until you explicitly disable it. |
✔ You can use SchemaEngine AI alongside Yoast SEO
Just like with Rank Math, disabling Yoast’s JSON-LD schema output does not remove any of its other SEO capabilities. Your Yoast meta titles, meta descriptions, OpenGraph tags, Twitter Card tags, XML sitemap, robots.txt configuration, and readability scores all continue to work normally. Only the structured data (JSON-LD) blocks that Yoast injects are disabled. This is the recommended setup when SchemaEngine AI is your primary schema plugin.
5.5 Best Practices —Generate Schema Markup from One Plugin #
The golden rule of schema markup: one plugin should be responsible for generating all structured data on your site. Mixing schema output from multiple plugins is the single biggest cause of rich result errors and warnings in Google Search Console.
✔ Recommended Setup #
| Best Practice | |
|---|---|
| ✔ | Use SchemaEngine AI as your single schema plugin — configure all schema types through its settings. |
| ✔ | Disable WooCommerce default schema if WooCommerce is active on your site. |
| ✔ | Disable Rank Math schema output if Rank Math SEO is installed — keep using Rank Math for all its other SEO features. |
| ✔ | Disable both Yoast SEO toggles (Sitelinks Searchbox AND Default Schema JSON-LD) if Yoast SEO is installed — keep using Yoast for meta tags, sitemaps, and analytics. |
| ✔ | After disabling third-party schema, validate your pages using Google’s Rich Results Test (search.google.com/test/rich-results) to confirm only one clean schema block is present. |
| ✔ | Monitor Google Search Console › Enhancements for any outstanding schema errors or warnings after making changes. |
✖ What to Avoid #
| Best Practice | |
|---|---|
| ✖ | Do not run SchemaEngine AI and Yoast SEO both generating schema at the same time — this produces duplicate JSON-LD on every page. |
| ✖ | Do not run SchemaEngine AI and Rank Math both generating schema simultaneously — the same conflict applies. |
| ✖ | Do not leave WooCommerce schema enabled if SchemaEngine AI is mapping the product post type — product pages will have two Product schema blocks. |
| ✖ | Do not ignore schema warnings in Google Search Console — even warnings (not just errors) can affect rich result eligibility. |
| ✖ | Do not assume that because a toggle is OFF by default it is not causing a conflict — check your page source for multiple JSON-LD blocks. |
💾 Save Changes
After updating the Third Party Conflict settings, click the Save Change button in the bottom-right corner of the screen. A success notice will appear at the top of the page confirming the settings have been saved.
