WordPress GEO plugin stack without schema soup

WordPress powers millions of cross-border stores; it also excels at duplicate meta and conflicting JSON-LD. GEO needs discipline more than another "AI optimization" plugin.

• One SEO/schema owner — Yoast, Rank Math, or SEOPress—not all three.
• WooCommerce product schema from same plugin; disable redundant outputs from theme.
• FAQ block (native or ACF) mirrored into FAQPage via hook or plugin field.
• Caching that does not strip JSON-LD scripts.
• Hreflang via multilingual plugin (WPML, Polylang) with reciprocal validation.

Variable products: ensure default variation or explicit variation URLs in schema. Stock status sync between wc_product_meta and Offer.availability.

View-source one PDP. Count application/ld+json blocks. More than two Product graphs? Disable offenders.

GEO is not an excuse for 40-plugin stacks. Slow TTFB reduces crawl depth on large catalogs.

Do AI plugins that "rewrite for ChatGPT" help? Rarely—fix facts and schema first.

Is classic editor vs block editor relevant? Blocks ease FAQ structure; either works with discipline.

Headless WordPress? Schema generated at SSR from WPGraphQL fields—same parity rules apply.

Run Visora /audit on WooCommerce URLs after plugin changes—conflicts appear immediately in HTML–JSON reports.