{"id":139,"date":"2026-10-22T14:47:30","date_gmt":"2026-10-22T12:47:30","guid":{"rendered":"https:\/\/www.imwaa.com\/blog\/?page_id=139"},"modified":"2026-10-26T09:39:22","modified_gmt":"2026-10-26T08:39:22","slug":"plugin","status":"publish","type":"page","link":"https:\/\/www.imwaa.com\/blog\/plugin\/","title":{"rendered":"WordPress SEO Plugin &#8211; Semantic Seo Graph"},"content":{"rendered":"<style>\/* FIX LAYOUT SEO SEMANTIC *\/.entry-content:has(.seo-semantic-hero){padding:0!important;margin:0!important;max-width:100%!important;width:100%!important}article:has(.seo-semantic-hero)>h1,article:has(.seo-semantic-hero) .entry-title,article:has(.seo-semantic-hero) .post-title,main:has(.seo-semantic-hero)>h1{display:none!important;margin:0!important;padding:0!important;height:0!important;line-height:0!important;overflow:hidden!important}main:has(.seo-semantic-hero){padding-top:0!important}.seo-semantic-hero{width:100vw!important;max-width:100vw!important;position:relative;left:50%;margin-left:-50vw!important;background-color:#020617!important;box-sizing:border-box}.seo-semantic-hero .section-hero{width:100%!important;max-width:100%!important;padding:60px 20px!important;min-height:auto!important;display:flex;align-items:center;box-sizing:border-box;background-color:#020617!important}.seo-semantic-hero .hero-content{width:100%;max-width:900px;margin:0 auto;padding:0 15px;text-align:center;box-sizing:border-box}.seo-semantic-hero .section-hero h1{margin-top:0!important;margin-bottom:20px!important;font-size:2.5rem!important;line-height:1.2!important}.seo-semantic-hero~section .container{width:100%!important;max-width:var(--container-width, 1200px)!important;padding-left:20px!important;padding-right:20px!important;margin:0 auto!important;box-sizing:border-box}@media(max-width:768px){.seo-semantic-hero~section .container{padding-left:15px!important;padding-right:15px!important;max-width:100%!important}.seo-semantic-hero~section .card{padding:22px!important;margin:0!important}.seo-semantic-hero~section .card h3{font-size:1.2rem!important;margin-bottom:10px!important}.seo-semantic-hero~section .card p{font-size:0.95rem!important;line-height:1.5!important}.seo-semantic-hero~section .card ul{padding-left:1rem!important;margin-bottom:0!important}.seo-semantic-hero~section .card li{font-size:0.9rem!important;line-height:1.6!important}.seo-semantic-hero~section.section{padding:40px 0!important}.seo-semantic-hero .section-hero{padding:50px 15px!important}.seo-semantic-hero .section-hero h1{font-size:1.8rem!important;margin-bottom:15px!important}.seo-semantic-hero .section-hero p{font-size:1rem!important}.seo-semantic-hero~section .terminal-box{padding:12px!important;font-size:0.8rem!important}.seo-semantic-hero~section details.waa-accordion{padding:0!important}.seo-semantic-hero~section summary.waa-summary{padding:15px!important;font-size:0.95rem!important}.seo-semantic-hero~section .accordion-content{padding:0 15px 15px 15px!important;font-size:0.9rem!important}}@media(min-width:992px){.seo-semantic-hero .section-hero{padding-top:80px!important;padding-bottom:60px!important}}<\/style>\n<div class=\"seo-semantic-hero\">\n<section class=\"section-hero\" aria-labelledby=\"hero-plugin-title\">\n<div class=\"hero-bg\"><\/div>\n<div class=\"hero-content\">\n      <span class=\"badge text-primary\">WordPress Plugin \u00b7 Enterprise SEO<\/span><\/p>\n<h1 id=\"hero-plugin-title\">SEO Semantic Graph: The Ontological Engineering Engine for WordPress<\/h1>\n<p style=\"font-size: 1.1rem; max-width: 800px; margin: 0 auto 20px auto;\">\n        SEO Semantic Graph builds a <strong>unified Knowledge Graph<\/strong> that tells Google and AI models exactly how your content is structured: what is a container, what is content, what belongs to what, and what is connected to what. No scattered code fragments, no &#8220;Ontological Chimeras&#8221;.\n      <\/p>\n<p style=\"font-size: 1.05rem; max-width: 800px; margin: 0 auto 20px auto;\">\n        Above all, it <strong>solves the main content cannibalization problems<\/strong>: every URL gets one clear role in the graph, with no overlapping signals. <a href=\"#cannibalization\" title=\"Jump to the section on how SEO Semantic prevents content cannibalization\">See how it prevents cannibalization \u2192<\/a>\n      <\/p>\n<p style=\"margin-bottom: 30px; color: var(--text-sub);\">\n        Traditional plugins focus on <em>syntax<\/em> (the green light). We focus on <em>ontology<\/em>: the actual structure and meaning of your site.\n      <\/p>\n<div style=\"display: flex; gap: 15px; justify-content: center; flex-wrap: wrap;\">\n        <a href=\"#getting-started\" class=\"btn btn-primary\" title=\"Learn how to download and install the SEO Semantic plugin\">Download &amp; Install<\/a><br \/>\n        <a href=\"#why-different\" class=\"btn btn-secondary\" title=\"Discover why a green validator light is not enough\">Why it&#8217;s different<\/a>\n      <\/div>\n<\/p><\/div>\n<\/section>\n<\/div>\n<section id=\"why-different\" class=\"section\" aria-labelledby=\"title-problem\">\n<div class=\"container\">\n<div class=\"centered-header\">\n<h2 id=\"title-problem\">The Problem: Validators check grammar, not logic<\/h2>\n<p>A JSON-LD document can pass every automated test and still be ontologically wrong. The Schema.org Validator and Google&#8217;s Rich Results Test verify that the markup is well formed. They do not verify that the graph makes logical sense.<\/p>\n<\/p><\/div>\n<div class=\"grid-2\">\n<div class=\"card\" style=\"border-left: 4px solid var(--accent-red);\">\n<h3>What validators accept (without flinching)<\/h3>\n<ul style=\"margin-bottom: 0; padding-left: 1.5rem; color: var(--text-sub); line-height: 1.8;\">\n<li>A <code>WebPage<\/code> declaring itself as an <code>Article<\/code> (container confused with content).<\/li>\n<li>A <code>hasPart<\/code> used to list pages that are not physically part of the document.<\/li>\n<li>A <code>Review<\/code> attached to a type Google does not accept (for example an <code>Article<\/code>).<\/li>\n<li>An <code>@id<\/code> pointing to a node that exists nowhere else (an orphan node).<\/li>\n<li>An <code>about<\/code> property that is free text instead of a resolvable reference.<\/li>\n<li>A legacy microformat (<code>hentry<\/code>) that validators read as an extra <code>CreativeWork<\/code>, unconnected to your graph and filled with whatever comes first in the page.<\/li>\n<\/ul><\/div>\n<div class=\"card\" style=\"border-left: 4px solid var(--accent-green);\">\n<h3>The Solution: No Ontological Chimeras<\/h3>\n<p>An <strong>Ontological Chimera<\/strong> is structured data that is syntactically valid but logically incoherent: a page that declares two incompatible things at the same time.<\/p>\n<p><strong>SEO Semantic was built to prevent exactly this.<\/strong><\/p>\n<p style=\"margin-bottom: 0;\">The plugin decides <em>where<\/em> each property lives, which node owns it, and how nodes reference each other through exact <code>@id<\/code>s. It works at the ontological level, not just the semantic one.<\/p>\n<\/p><\/div>\n<\/p><\/div>\n<div class=\"card\" style=\"margin-top: 30px; border-left: 4px solid var(--accent-blue, #2563eb);\">\n<h3>Note on <code>hentry<\/code>: what it is and why it appears<\/h3>\n<p>You may see an <code>hentry<\/code> node in your graph that does not come from our plugin. <code>hentry<\/code> is a microformat from the blog era (hAtom) that WordPress and many themes add to every post through <code>post_class()<\/code>. Google documents JSON-LD, Microdata and RDFa \u2014 not hAtom. The validator reads it as an extra <code>CreativeWork<\/code>, disconnected from the graph, and fills it with whatever comes first on the page. It is, in effect, an ontological chimera.<\/p>\n<p>SEO Semantic removes it by default. There is a <strong>&#8220;Replacement CSS class&#8221;<\/strong> field: if your theme styles <code>.hentry<\/code>, enter for example <code>ssg-entry<\/code> and it will be added in its place.<\/p>\n<p style=\"margin-bottom: 0;\"><strong>Limitation:<\/strong> if the theme hard-codes <code>hentry<\/code> in its templates, or prints its own Microdata (<code>itemscope<\/code>, <code>itemtype<\/code>), the plugin cannot remove it \u2014 it does not clean the HTML after the fact. If a <code>hentry<\/code> CreativeWork still appears after the test, search <code>itemtype<\/code> in the page source: it comes from the theme and must be fixed in a child theme.<\/p>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n<section id=\"cannibalization\" class=\"section section-alt\" aria-labelledby=\"title-cannibalization\">\n<div class=\"container\">\n<div class=\"centered-header\">\n<h2 id=\"title-cannibalization\">How SEO Semantic Prevents Content Cannibalization<\/h2>\n<p>Traditional WordPress sites suffer from cannibalization because categories, tags, and poorly structured archives create overlapping signals. Search engines and AI models get confused about which page is the actual authority.<\/p>\n<\/p><\/div>\n<div class=\"grid-2\">\n<div class=\"card\" style=\"border-left: 4px solid var(--accent-red);\">\n<h3>The Old Way: The Ambiguous Tree<\/h3>\n<p>In standard setups, multiple pages fight for the same keywords because categories and overlapping archives group them loosely. Google&#8217;s crawler has to guess the hierarchy, often leading to internal cannibalization and diluted ranking power.<\/p>\n<\/p><\/div>\n<div class=\"card\" style=\"border-left: 4px solid var(--accent-green);\">\n<h3>The Semantic Way: Zero Guesswork<\/h3>\n<p><strong>SEO Semantic completely prevents cannibalization by design.<\/strong> By enforcing strict ontological rules\u2014such as explicit <code>isPartOf<\/code> vertical parent links and targeted <code>significantLink<\/code> bridges\u2014every URL has a unique, non-overlapping role in the Knowledge Graph.<\/p>\n<p style=\"margin-bottom: 0;\">When AI models and search engines crawl your site, they don&#8217;t have to &#8220;guess&#8221; relationships. They mathematically read who the master Hub (Pillar) is and who the child nodes are. Total clarity, zero cannibalization.<\/p>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n<section class=\"section\" aria-labelledby=\"title-features\">\n<div class=\"container\">\n<div class=\"centered-header\">\n<h2 id=\"title-features\">The Entity SEO Rules, Applied by Default<\/h2>\n<p>The plugin applies the Semantic Audit Guide so that the correct configuration is the default one.<\/p>\n<\/p><\/div>\n<div class=\"grid-4\">\n<div class=\"card\">\n<div class=\"card-icon\" aria-hidden=\"true\">\ud83d\udce6<\/div>\n<h3 style=\"font-size: 1.2rem;\">Container \u2260 Content<\/h3>\n<p style=\"font-size: 0.9rem;\">A URL is never declared an &#8220;Article&#8221;. It is a <code>WebPage<\/code> that hosts a <code>mainEntity<\/code> (the logical content).<\/p>\n<\/p><\/div>\n<div class=\"card\">\n<div class=\"card-icon\" aria-hidden=\"true\">\ud83d\udd17<\/div>\n<h3 style=\"font-size: 1.2rem;\">Linking vs Containment<\/h3>\n<p style=\"font-size: 0.9rem;\">On Pillar Pages the plugin never uses a fake <code>hasPart<\/code>. It uses <code>significantLink<\/code> (as strings) combined with a structured <code>ItemList<\/code>.<\/p>\n<\/p><\/div>\n<div class=\"card\">\n<div class=\"card-icon\" aria-hidden=\"true\">\ud83c\udfaf<\/div>\n<h3 style=\"font-size: 1.2rem;\">Pure Reference Nodes<\/h3>\n<p style=\"font-size: 0.9rem;\">Nodes are stitched together with exact <code>@id<\/code>s (<code>#webpage<\/code>, <code>#article<\/code>, <code>#organization<\/code>). Every reference inside a page resolves inside the same graph; references to other pages point only to their containers (<code>#webpage<\/code>).<\/p>\n<\/p><\/div>\n<div class=\"card\">\n<div class=\"card-icon\" aria-hidden=\"true\">\ud83e\udde9<\/div>\n<h3 style=\"font-size: 1.2rem;\">Entity Disambiguation<\/h3>\n<p style=\"font-size: 0.9rem;\">One strong <code>about<\/code> (for example a Wikipedia URL) and an array of secondary <code>mentions<\/code>.<\/p>\n<\/p><\/div>\n<div class=\"card\">\n<div class=\"card-icon\" aria-hidden=\"true\">\ud83e\udded<\/div>\n<h3 style=\"font-size: 1.2rem;\">Breadcrumb on the WebPage<\/h3>\n<p style=\"font-size: 0.9rem;\">The <code>BreadcrumbList<\/code> belongs to the page, not to the content, and follows the parent chain you declare.<\/p>\n<\/p><\/div>\n<div class=\"card\">\n<div class=\"card-icon\" aria-hidden=\"true\">\u2696\ufe0f<\/div>\n<h3 style=\"font-size: 1.2rem;\">Data Parity by Design<\/h3>\n<p style=\"font-size: 0.9rem;\">FAQs, reviews, aggregate ratings, prices and availability are generated from the same data as the visible HTML, so what the JSON-LD declares is what the visitor sees.<\/p>\n<\/p><\/div>\n<div class=\"card\">\n<div class=\"card-icon\" aria-hidden=\"true\">\ud83e\uddf1<\/div>\n<h3 style=\"font-size: 1.2rem;\">Single Source of Truth<\/h3>\n<p style=\"font-size: 0.9rem;\">By default SEO Semantic silences the JSON-LD of Yoast SEO, Rank Math and All in One SEO (you can switch this off in the settings). Schema printed by other plugins or by your theme, for example WooCommerce product data, is not touched.<\/p>\n<\/p><\/div>\n<div class=\"card\">\n<div class=\"card-icon\" aria-hidden=\"true\">\ud83d\udd24<\/div>\n<h3 style=\"font-size: 1.2rem;\">Legacy hentry Removed<\/h3>\n<p style=\"font-size: 0.9rem;\">The <code>hentry<\/code> microformat added by WordPress and many themes is removed by default, because validators read it as an extra, unconnected <code>CreativeWork<\/code>. If your theme styles <code>.hentry<\/code>, choose a neutral replacement class in the settings.<\/p>\n<\/p><\/div>\n<\/p><\/div>\n<div class=\"text-center\" style=\"margin-top: 40px;\">\n<p>To see how these rules are applied in practice, read the <a href=\"https:\/\/www.imwaa.com\/en\/audit\/schema\/\" title=\"Guide to the Schema.org Audit and the Entity SEO rules\">full Schema.org Audit guide<\/a>.<\/p>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n<section class=\"section\" aria-labelledby=\"title-relations\">\n<div class=\"container\">\n<div class=\"centered-header\">\n<h2 id=\"title-relations\">Relations, not categories<\/h2>\n<p>Categories and tags belong to the old, tree-shaped web: they give a machine a label, not a meaning. To understand what a category contains, a search engine or an LLM has to read the titles inside it and guess.<\/p>\n<\/p><\/div>\n<div class=\"grid-2\">\n<div class=\"card\">\n<h3>SEO Semantic replaces labels with declared relations<\/h3>\n<ul style=\"margin-bottom: 0; padding-left: 1.5rem; color: var(--text-sub); line-height: 1.8;\">\n<li><strong>Vertical:<\/strong> this page belongs to that pillar (<code>isPartOf<\/code>). Pages with the same parent are siblings.<\/li>\n<li><strong>Horizontal:<\/strong> this page connects to a page of another collection (<code>significantLink<\/code>). Pages linked across different parents are cousins.<\/li>\n<li><strong>Topical:<\/strong> this article is part of collection X but has points of contact with an article of collection Y \u2014 you declare it with <code>about<\/code> or <code>mentions<\/code>.<\/li>\n<\/ul><\/div>\n<div class=\"card\">\n<h3>Declared, never inferred<\/h3>\n<p>The plugin declares these relations. It never infers them, and it does not use WordPress categories or tags. For this reason archive, category, tag, author and search pages receive only the <code>Organization<\/code> and <code>WebSite<\/code> nodes: they are listing pages, not entities.<\/p>\n<p style=\"margin-bottom: 0;\">If your site already earns traffic from category archives, turn them into pillar pages or keep them out of the index.<\/p>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n<section class=\"section\" aria-labelledby=\"title-who-is-it-for\">\n<div class=\"container\">\n<div class=\"centered-header\">\n<h2 id=\"title-who-is-it-for\">Who it&#8217;s for (and who it&#8217;s not for)<\/h2>\n<p>This plugin is a surgical tool for those who need ontological control.<\/p>\n<\/p><\/div>\n<div class=\"grid-2\">\n<div class=\"card\" style=\"border-top: 4px solid var(--accent-green);\">\n<h3>\u2705 It&#8217;s for you if:<\/h3>\n<ul style=\"margin-bottom: 0; padding-left: 1.5rem; color: var(--text-sub); line-height: 1.8;\">\n<li>You are an SEO consultant or webmaster working on Entity SEO.<\/li>\n<li>You need a coherent Knowledge Graph for pillar pages, silos, service or product catalogs.<\/li>\n<li>You have used a validator, seen the green light, and suspected the graph made no logical sense.<\/li>\n<li>You want a single source of truth for JSON-LD, with no conflicts from other plugins.<\/li>\n<\/ul><\/div>\n<div class=\"card\" style=\"border-top: 4px solid var(--accent-red);\">\n<h3>\u274c It&#8217;s NOT for you if:<\/h3>\n<ul style=\"margin-bottom: 0; padding-left: 1.5rem; color: var(--text-sub); line-height: 1.8;\">\n<li>You are looking for an all-in-one SEO suite (meta tags, sitemaps, redirects, analytics). This plugin does not do that.<\/li>\n<li>You only need basic meta tags and do not care about structured data.<\/li>\n<li>You expect the plugin to fix SEO automatically without configuring the ontology.<\/li>\n<li>You want several plugins printing JSON-LD at the same time. By default SEO Semantic silences the JSON-LD of Yoast SEO, Rank Math and All in One SEO (you can switch this off in the settings). Schema printed by other plugins or by your theme, for example WooCommerce product data, is not touched.<\/li>\n<\/ul><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n<section class=\"section section-alt\" aria-labelledby=\"title-manuals\">\n<div class=\"container\">\n<div class=\"centered-header\">\n<h2 id=\"title-manuals\">Use Cases &amp; Practical Guides<\/h2>\n<p>Two specific guides show you exactly how the plugin behaves on different types of WordPress content.<\/p>\n<\/p><\/div>\n<div class=\"grid-2\">\n<div class=\"card\">\n<div class=\"card-icon\" aria-hidden=\"true\">\ud83d\udcc4<\/div>\n<h3>Configuring Articles (Content)<\/h3>\n<p>How the plugin handles the <code>Article<\/code> entity: why reviews are blocked on posts, how author and date are extracted, and how type errors are prevented.<\/p>\n<p style=\"margin-top: 20px;\"><a href=\"https:\/\/www.imwaa.com\/blog\/json-ld-seo-on-wordpress\/\" class=\"btn btn-primary\" title=\"Read the guide on configuring JSON-LD SEO in a WordPress article\">Go to Articles Guide<\/a><\/p>\n<\/p><\/div>\n<div class=\"card\">\n<div class=\"card-icon\" aria-hidden=\"true\">\ud83d\uddc2\ufe0f<\/div>\n<h3>Configuring Pages (Container)<\/h3>\n<p>How to declare a <code>Service<\/code>, a <code>Product<\/code>, an <code>App<\/code>, a <code>CollectionPage<\/code>, an <code>About<\/code> or <code>Contact<\/code> page. How siloing works and how to prevent cannibalization.<\/p>\n<p style=\"margin-top: 20px;\"><a href=\"https:\/\/www.imwaa.com\/blog\/json-ld-seo-wordpress-page\/\" class=\"btn btn-primary\" title=\"Read the guide on configuring JSON-LD SEO in a WordPress page\">Go to Pages Guide<\/a><\/p>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n<section id=\"getting-started\" class=\"section\" aria-labelledby=\"title-getting-started\">\n<div class=\"container\">\n<div class=\"centered-header\">\n<h2 id=\"title-getting-started\">How to Get Started<\/h2>\n<p>The plugin will be available on WordPress.org. In the meantime you can install it manually.<\/p>\n<\/p><\/div>\n<div class=\"grid-2\">\n<div>\n<details class=\"waa-accordion\" open>\n<summary class=\"waa-summary\">1. Global E-E-A-T configuration<\/summary>\n<div class=\"accordion-content\">\n<p>Go to <strong>SEO Semantic<\/strong> in the sidebar. Enter your company details (name, VAT number, founder), your <code>sameAs<\/code> links (for example LinkedIn or Wikipedia) and choose your About Us page, which is typed <code>AboutPage<\/code> automatically. The <code>Organization<\/code> is printed on every page, so every reference to it resolves inside the page&#8217;s own graph.<\/p>\n<\/div>\n<\/details>\n<details class=\"waa-accordion\">\n<summary class=\"waa-summary\">2. Single page or article<\/summary>\n<div class=\"accordion-content\">\n<p>Open any post or page. In the <strong>SEO Semantic Graph<\/strong> box choose what the page hosts (<code>Service<\/code>, <code>Product<\/code>, <code>App<\/code>, <code>Collection<\/code>, <code>About<\/code>, <code>Contact<\/code>). Posts are <code>Article<\/code>s automatically. For Products and Apps enter price, currency and availability: they are declared in the JSON-LD and shown in a small visible details box.<\/p>\n<\/div>\n<\/details>\n<details class=\"waa-accordion\">\n<summary class=\"waa-summary\">3. The Relationship Builder (siloing)<\/summary>\n<div class=\"accordion-content\">\n<p>Use <strong>Belongs to<\/strong> for the vertical relation (parent). Use <strong>Links to<\/strong> for horizontal relations between collections. Tick the <strong>Pillar<\/strong> option on a hub page to generate its <code>ItemList<\/code>; every child page declares the hub as its parent by default.<\/p>\n<\/div>\n<\/details><\/div>\n<div>\n<details class=\"waa-accordion\">\n<summary class=\"waa-summary\">4. Ontology and disambiguation<\/summary>\n<div class=\"accordion-content\">\n<p>Use <strong>About<\/strong> for the main topic (a Wikipedia URL or an internal pillar) and <strong>Mentions<\/strong> for secondary concepts or pages of other collections.<\/p>\n<\/div>\n<\/details>\n<details class=\"waa-accordion\">\n<summary class=\"waa-summary\">5. Styling FAQs and reviews<\/summary>\n<div class=\"accordion-content\">\n<p>The blocks inherit your theme&#8217;s fonts and colours and use three CSS variables (<code>--ssg-accent<\/code>, <code>--ssg-radius<\/code>, <code>--ssg-border<\/code>) that you can set in Additional CSS. Stable class names and HTML filters are documented in the readme. You can also switch the default stylesheet off. Never hide the blocks with <code>display:none<\/code>: the structured data would describe content visitors cannot see.<\/p>\n<\/div>\n<\/details>\n<details class=\"waa-accordion\">\n<summary class=\"waa-summary\">6. Languages<\/summary>\n<div class=\"accordion-content\">\n<p>The interface is in English and is translated through WordPress language packs. The Italian translation is included as a downloadable file: copy <code>seo-semantic-graph-it_IT.mo<\/code> into <code>wp-content\/languages\/plugins\/<\/code> and set the site language to Italiano. Once the plugin is on WordPress.org, translations are managed on translate.wordpress.org and delivered automatically.<\/p>\n<\/div>\n<\/details>\n<details class=\"waa-accordion\">\n<summary class=\"waa-summary\">7. Legacy hentry<\/summary>\n<div class=\"accordion-content\">\n<p>The <code>hentry<\/code> microformat that WordPress and many themes add to posts is removed by default, because validators read it as an extra, unconnected <code>CreativeWork<\/code>. If your theme styles <code>.hentry<\/code> you can choose a neutral replacement class in the settings. <strong>Limitation:<\/strong> if the theme hard-codes <code>hentry<\/code> in its templates or prints its own Microdata (<code>itemscope<\/code>, <code>itemtype<\/code>), the plugin cannot remove it. Search <code>itemtype<\/code> in the page source: it comes from the theme and must be fixed in a child theme.<\/p>\n<\/div>\n<\/details><\/div>\n<\/p><\/div>\n<div class=\"text-center\" style=\"margin-top: 40px;\">\n<p style=\"margin-bottom: 20px;\">Download the .zip file, go to <strong>WordPress &gt; Plugins &gt; Add New &gt; Upload Plugin<\/strong>, upload the file and click <strong>Activate<\/strong>.<\/p>\n<p>      <a href=\"#\" class=\"btn btn-primary\" title=\"Download the SEO Semantic plugin (zip file)\">Download Plugin (.zip)<\/a>\n    <\/div>\n<\/p><\/div>\n<\/section>\n<section class=\"section\" aria-labelledby=\"title-good-to-know\">\n<div class=\"container\">\n<div class=\"centered-header\">\n<h2 id=\"title-good-to-know\">Good to know<\/h2>\n<p>A few practical notes before you configure your graph.<\/p>\n<\/p><\/div>\n<div class=\"grid-2\">\n<div class=\"card\">\n<h3>FAQ rich results are over<\/h3>\n<p style=\"margin-bottom: 0;\">Since May 2026 Google no longer shows FAQ rich results. <code>FAQPage<\/code> is still valid Schema.org markup and describes your content to other consumers, but do not expect a visual snippet in Google.<\/p>\n<\/p><\/div>\n<div class=\"card\">\n<h3>Empty results are normal<\/h3>\n<p style=\"margin-bottom: 0;\">A <code>Service<\/code> or <code>CollectionPage<\/code> returns <em>No items detected<\/em> in the Rich Results Test. The Schema.org Validator is where you check the graph.<\/p>\n<\/p><\/div>\n<div class=\"card\">\n<h3>Theme limits<\/h3>\n<p style=\"margin-bottom: 0;\">If a theme hard-codes <code>hentry<\/code> or prints its own Microdata, the plugin cannot remove it: use a child theme.<\/p>\n<\/p><\/div>\n<div class=\"card\">\n<h3>Reviews<\/h3>\n<p style=\"margin-bottom: 0;\">Use only genuine ratings. Google does not accept self-serving reviews on organizations.<\/p>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n<section class=\"section section-alt\" aria-labelledby=\"title-audit\">\n<div class=\"container text-center\">\n<h2 id=\"title-audit\">Do you have a WordPress site and want to know if your graph is coherent?<\/h2>\n<p>Don&#8217;t stop at the green light. Find out if your site has Ontological Chimeras or orphan nodes.<\/p>\n<p style=\"margin-top: 30px;\"><a href=\"https:\/\/www.imwaa.com\/en\/audit\/\" class=\"btn btn-primary\" title=\"Run the complete audit: Schema.org, rich snippets and performance\">Run the Complete Audit on your site<\/a><\/p>\n<\/p><\/div>\n<\/section>\n<\/section>\n","protected":false},"excerpt":{"rendered":"<p>WordPress Plugin \u00b7 Enterprise SEO SEO Semantic Graph: The Ontological Engineering Engine for WordPress SEO Semantic Graph builds a unified Knowledge Graph that tells Google and AI models exactly how your content is structured: what is a container, what is content, what belongs to what, and what is connected to what. No scattered code fragments, [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-139","page","type-page","status-publish"],"_links":{"self":[{"href":"https:\/\/www.imwaa.com\/blog\/wp-json\/wp\/v2\/pages\/139","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.imwaa.com\/blog\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.imwaa.com\/blog\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.imwaa.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.imwaa.com\/blog\/wp-json\/wp\/v2\/comments?post=139"}],"version-history":[{"count":7,"href":"https:\/\/www.imwaa.com\/blog\/wp-json\/wp\/v2\/pages\/139\/revisions"}],"predecessor-version":[{"id":190,"href":"https:\/\/www.imwaa.com\/blog\/wp-json\/wp\/v2\/pages\/139\/revisions\/190"}],"wp:attachment":[{"href":"https:\/\/www.imwaa.com\/blog\/wp-json\/wp\/v2\/media?parent=139"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}