When Yoast SEO or Rank Math is active alongside AEO God Mode, both plugins may try to output the same schema types. The Conflicts page detects these overlaps and gives you control over which plugin handles each schema type.
How Conflict Detection Works
The conflict detector runs 7 checks when you open the Conflicts page:
| Check | Severity | Triggers When |
|---|---|---|
| `meta_title` | Error | AEO’s basic_meta module is ON and Yoast/RM is active |
| `meta_description` | Error | AEO’s basic_meta module is ON and Yoast/RM is active |
| `schema_output` | Warning | AEO’s schema module is ON and Yoast/RM is active |
| `robots_txt` | Warning | AEO’s robots module is ON and Yoast/RM is active |
| `sitemap` | Warning | AEO’s sitemap features overlap with Yoast/RM |
| `canonical` | None | AEO God Mode does not output canonical tags, so no conflict |
| `og_tags` | None | AEO God Mode does not output Open Graph tags, so no conflict |
Results are cached so the page loads quickly on repeat visits.
Resolving General Conflicts
For each detected conflict, you have three resolution options:
- Defer: Let the other plugin handle it (AEO God Mode steps back)
- Override: AEO God Mode takes control (the other plugin’s output is suppressed)
- Merge: Both plugins output together (AEO God Mode only adds what the other plugin doesn’t cover)
To set a resolution:
- Go to AEO God Mode > Conflicts (
admin.php?page=aeo-god-mode#/conflicts) - Review each detected conflict card
- Select your preferred resolution
- Your choice is saved instantly
Per-Type Schema Resolution
The most useful feature is per-type schema control. The Schema Comparison tool shows a side-by-side breakdown for 7 schema types:
| Schema Type | What AEO God Mode Outputs | What Yoast/RM Outputs |
|---|---|---|
| **Article** | headline, dates, author, publisher, wordCount, articleSection, image, description, inLanguage, mainEntityOfPage, isPartOf, speakable | headline, dates, author, publisher, image (Yoast adds wordCount) |
| **Person** | name, url, image, jobTitle, description, knowsAbout, hasCredential, alumniOf, worksFor, sameAs, memberOf | name, url, image (Yoast also adds description, sameAs) |
| **BreadcrumbList** | Home > Category > Post | Home > Category > Post |
| **WebSite** | name, url, inLanguage, SearchAction | name, url, inLanguage, SearchAction |
| **Organization** | name, url, inLanguage, logo, sameAs | name, url, logo |
| **HowTo** | Auto-detected from content | Only if using their blocks (rare) |
| **FAQPage** | Auto-detected from content | Only if using their blocks (rare) |
For each type, you can choose:
- Ours: AEO God Mode handles this schema type
- Theirs: Let Yoast/Rank Math handle it
- Both: Both plugins output this type (not recommended for identical types)
To set per-type resolutions:
- Go to AEO God Mode > Conflicts
- Scroll to the Schema Comparison section
- Click on each schema type to see the field comparison
- Select Ours, Theirs, or Both
- Resolutions are saved instantly
Recommendations
The plugin auto-generates recommendations based on which side has more unique fields:
- Person: Always recommends “Ours” because AEO God Mode includes E-E-A-T fields (jobTitle, knowsAbout, hasCredential, alumniOf, worksFor) that Yoast/RM doesn’t output
- HowTo / FAQPage: Always recommends “Ours” because only AEO God Mode auto-detects these from content
- Article: Recommends whichever side has more unique fields (AEO God Mode typically wins with speakable, description, and isPartOf)
- BreadcrumbList / WebSite / Organization: Recommends “Theirs” as the safe default, since Yoast/RM coverage is similar
How Your Choices Are Applied
When you set a type to “Theirs,” AEO God Mode stops printing its own version of that schema and leaves the type to the other plugin. Every schema type honours your choice the same way, and the plugin also checks that the other plugin is actually active, so nothing goes missing if you later remove it.
Troubleshooting
No conflicts detected but you have Yoast/RM installed:
- The scan only detects conflicts for AEO modules that are enabled. If Schema module is off, no schema conflict appears
- Run a fresh scan by refreshing the Conflicts page
Duplicate schema appearing in page source:
- Check your per-type resolutions. If set to “Both,” you’ll get duplicates
- Set the overlapping type to either “Ours” or “Theirs”