diff --git a/webengine/views/adobe-experience-manager-vs-content-one.html b/webengine/views/adobe-experience-manager-vs-content-one.html
index 1f6afe0..fb8a8dc 100644
--- a/webengine/views/adobe-experience-manager-vs-content-one.html
+++ b/webengine/views/adobe-experience-manager-vs-content-one.html
@@ -44,6 +44,120 @@
     .versus-faq > summary::marker { content: ""; }
   </style>
 
+  <script type="application/ld+json">
+{
+  "@context": "https://schema.org",
+  "@graph": [
+    {
+      "@type": "WebPage",
+      "@id": "https://www.content.one/adobe-experience-manager-vs-content-one.html#webpage",
+      "url": "https://www.content.one/adobe-experience-manager-vs-content-one.html",
+      "name": "Adobe Experience Manager vs Content.One, DXP comparison, AEM 6.5 EOL, pricing",
+      "description": "Comparing Adobe Experience Manager (AEM) and Content.One for multi-location content operations? See pricing, implementation timelines, and the AEM 6.5 deadline forcing the conversation.",
+      "inLanguage": "en-US",
+      "datePublished": "2026-07-23",
+      "dateModified": "2026-09-11",
+      "isPartOf": {
+        "@type": "WebSite",
+        "@id": "https://www.content.one/#website",
+        "url": "https://www.content.one/",
+        "name": "Content.One"
+      },
+      "publisher": {
+        "@type": "Organization",
+        "@id": "https://www.content.one/#organization",
+        "name": "Content.One",
+        "url": "https://www.content.one/",
+        "logo": {
+          "@type": "ImageObject",
+          "url": "https://hj5v68xn.media.zestyio.com/content-one-brand-2025.png"
+        }
+      },
+      "breadcrumb": {
+        "@id": "https://www.content.one/adobe-experience-manager-vs-content-one.html#breadcrumb"
+      }
+    },
+    {
+      "@type": "BreadcrumbList",
+      "@id": "https://www.content.one/adobe-experience-manager-vs-content-one.html#breadcrumb",
+      "itemListElement": [
+        {
+          "@type": "ListItem",
+          "position": 1,
+          "name": "Home",
+          "item": "https://www.content.one/"
+        },
+        {
+          "@type": "ListItem",
+          "position": 2,
+          "name": "Compare",
+          "item": "https://www.content.one/compare.html"
+        },
+        {
+          "@type": "ListItem",
+          "position": 3,
+          "name": "Adobe Experience Manager vs Content.One",
+          "item": "https://www.content.one/adobe-experience-manager-vs-content-one.html"
+        }
+      ]
+    },
+    {
+      "@type": "FAQPage",
+      "@id": "https://www.content.one/adobe-experience-manager-vs-content-one.html#faq",
+      "mainEntity": [
+        {
+          "@type": "Question",
+          "name": "What happens if we're still on AEM 6.5 after August 2026?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Adobe ends support for AEM 6.5 LTS on August 31, 2026. After that date, you're running an unsupported on-prem system, which means no security patches and no official help if something breaks. Organizations still on 6.5 need a migration plan now, whether that's to AEM as a Cloud Service or an alternative platform."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Why doesn't Adobe publish AEM pricing?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "AEM pricing is modular and negotiated per organization based on which components you need (Sites, Assets, Forms, Screens) and your usage volume. Adobe sends every prospect to a sales conversation rather than a pricing page, which is standard for enterprise DXP but makes it hard to budget without already talking to them."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Do we need Java developers to run Content.One the way we'd need them for AEM?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "No. Content.One's agentic page builder lets marketers build and edit pages without touching code. Engineer on Demand covers anything that genuinely needs custom development, on an as-needed basis rather than a permanent headcount requirement."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Can Content.One migrate an existing AEM instance?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Yes. The migration.content.one tool assesses your current AEM setup and gives you a timeline and cost estimate, and Engineer on Demand handles the actual migration work."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Is AEM overkill for a franchise or multi-location network?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Often, yes. AEM's Multi-Site Manager can technically support a multi-location structure, but it's built for organizations with the development resources to configure and maintain that complexity. Most franchise and multi-location teams are marketing-led, not engineering-led, which is the gap Content.One is built to close."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Does Content.One handle digital asset management the way AEM Assets does?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Content.One includes asset management built into the same platform, though AEM Assets remains the more mature option for organizations with very large, complex digital asset libraries as their primary need rather than website publishing."
+          }
+        }
+      ]
+    }
+  ]
+}
+  </script>
   {{include /-/isolated-page-marketing-snippet.html}}
 </head>
 <body class="font-sans">
@@ -87,6 +201,7 @@
     <div class="max-w-5xl mx-auto px-4 sm:px-6 lg:px-8 text-center">
       <span class="inline-flex items-center px-3 py-1 rounded-full bg-white text-royal text-xs font-semibold uppercase tracking-wider mb-5">Side-by-side comparison</span>
       <h1 class="font-display text-4xl md:text-5xl lg:text-6xl font-bold mb-6">Adobe Experience Manager vs Content.One</h1>
+      <p class="text-sm text-white/60 mb-6"><time datetime="2026-09-11">Last updated: September 2026</time></p>
       <p class="text-lg md:text-xl text-white/80 max-w-3xl mx-auto mb-8">Adobe Experience Manager is a deep enterprise DXP built for teams already inside Adobe Experience Cloud with dedicated Java developers. Content.One is built for marketing-led, multi-location networks that need governed publishing across dozens or thousands of properties without a permanent implementation team.</p>
       <div class="flex flex-wrap gap-3 justify-center">
         <a href="https://launch.content.one" target="_blank" rel="noopener" class="inline-flex items-center rounded-lg bg-white text-royal hover:bg-gray-100 font-semibold px-6 py-3 transition shadow">Start a build</a>
@@ -268,6 +383,7 @@ <h2 class="font-display text-3xl md:text-4xl font-bold mb-3">The comparison</h2>
           </tbody>
         </table>
       </div>
+        <p class="text-xs text-gray-500 mt-3 italic">Accurate as of September 2026.</p>
     </div>
   </section>
 
diff --git a/webengine/views/components/footer.html b/webengine/views/components/footer.html
index 42d3d6e..19c0249 100644
--- a/webengine/views/components/footer.html
+++ b/webengine/views/components/footer.html
@@ -113,6 +113,24 @@
             <li><a href="/about/" class="text-sm font-medium text-gray-600 hover:text-royal transition no-underline">About Us</a></li>
           </ul>
         </div>
+        <!-- Compare sub-stack — internal links to all 10 vs pages, anchor text
+             "[Competitor] vs Content.One" per kaya's SEO brief (2026-09-10 #1c). -->
+        <div>
+          <p class="text-sm font-semibold text-royal mb-4">Compare</p>
+          <ul class="list-none p-0 m-0 space-y-3">
+            <li><a href="/compare.html" class="text-sm font-medium text-gray-600 hover:text-royal transition no-underline">All comparisons</a></li>
+            <li><a href="/contentful-vs-content-one.html" class="text-sm font-medium text-gray-600 hover:text-royal transition no-underline">Contentful vs Content.One</a></li>
+            <li><a href="/drupal-vs-content-one.html" class="text-sm font-medium text-gray-600 hover:text-royal transition no-underline">Drupal vs Content.One</a></li>
+            <li><a href="/sanity-vs-content-one.html" class="text-sm font-medium text-gray-600 hover:text-royal transition no-underline">Sanity vs Content.One</a></li>
+            <li><a href="/sitecore-vs-content-one.html" class="text-sm font-medium text-gray-600 hover:text-royal transition no-underline">Sitecore vs Content.One</a></li>
+            <li><a href="/storyblok-vs-content-one.html" class="text-sm font-medium text-gray-600 hover:text-royal transition no-underline">Storyblok vs Content.One</a></li>
+            <li><a href="/contentstack-vs-content-one.html" class="text-sm font-medium text-gray-600 hover:text-royal transition no-underline">Contentstack vs Content.One</a></li>
+            <li><a href="/adobe-experience-manager-vs-content-one.html" class="text-sm font-medium text-gray-600 hover:text-royal transition no-underline">Adobe Experience Manager vs Content.One</a></li>
+            <li><a href="/optimizely-vs-content-one.html" class="text-sm font-medium text-gray-600 hover:text-royal transition no-underline">Optimizely vs Content.One</a></li>
+            <li><a href="/webflow-vs-content-one.html" class="text-sm font-medium text-gray-600 hover:text-royal transition no-underline">Webflow vs Content.One</a></li>
+            <li><a href="/duda-vs-content-one.html" class="text-sm font-medium text-gray-600 hover:text-royal transition no-underline">Duda vs Content.One</a></li>
+          </ul>
+        </div>
       </div>
 
       <!-- Group: Tools (standalone; swapped with Resources per bobby) -->
diff --git a/webengine/views/components/nav.html b/webengine/views/components/nav.html
index 77bc4c6..07743d9 100644
--- a/webengine/views/components/nav.html
+++ b/webengine/views/components/nav.html
@@ -331,6 +331,15 @@
             <span class="mobile-nav-item__tag">The latest from our team</span>
           </span>
         </a>
+        <a class="mobile-nav-item block px-3 py-2 text-sm text-gray-600 rounded-md hover:bg-royal/5 hover:text-royal" href="/compare.html">
+          <span class="mobile-nav-item__icon inline-flex">
+            <svg viewBox="0 0 24 24" class="w-5 h-5" fill="none" stroke="currentColor" stroke-width="1.6" aria-hidden="true"><rect x="3" y="4" width="18" height="16" rx="2"/><line x1="12" y1="4" x2="12" y2="20"/><line x1="3" y1="12" x2="21" y2="12"/></svg>
+          </span>
+          <span>
+            <span class="mobile-nav-item__title">Compare</span>
+            <span class="mobile-nav-item__tag">Content.One vs 10+ CMS platforms</span>
+          </span>
+        </a>
         <a class="mobile-nav-item block px-3 py-2 text-sm text-gray-600 rounded-md hover:bg-royal/5 hover:text-royal" target="_blank" rel="noopener" href="https://docs.zesty.io/">
           <span class="mobile-nav-item__icon inline-flex">
             <svg viewBox="0 0 24 24" class="w-5 h-5" fill="none" stroke="currentColor" stroke-width="1.6" aria-hidden="true"><path d="M4 19.5A2.5 2.5 0 0 1 6.5 17H20"/><path d="M6.5 2H20v20H6.5A2.5 2.5 0 0 1 4 19.5v-15A2.5 2.5 0 0 1 6.5 2z"/></svg>
@@ -546,6 +555,15 @@
                         <span class="c1-mega-item__tag">The latest from our team</span>
                       </span>
                     </a>
+                    <a class="c1-mega-item" href="/compare.html">
+                      <span class="c1-mega-item__icon">
+                        <svg viewBox="0 0 24 24" class="w-5 h-5" fill="none" stroke="currentColor" stroke-width="1.6" aria-hidden="true"><rect x="3" y="4" width="18" height="16" rx="2"/><line x1="12" y1="4" x2="12" y2="20"/><line x1="3" y1="12" x2="21" y2="12"/></svg>
+                      </span>
+                      <span>
+                        <span class="c1-mega-item__title">Compare</span>
+                        <span class="c1-mega-item__tag">Content.One vs 10+ CMS platforms</span>
+                      </span>
+                    </a>
                     <a class="c1-mega-item" target="_blank" rel="noopener" href="https://docs.zesty.io/">
                       <span class="c1-mega-item__icon">
                         <svg viewBox="0 0 24 24" class="w-5 h-5" fill="none" stroke="currentColor" stroke-width="1.6" aria-hidden="true"><path d="M4 19.5A2.5 2.5 0 0 1 6.5 17H20"/><path d="M6.5 2H20v20H6.5A2.5 2.5 0 0 1 4 19.5v-15A2.5 2.5 0 0 1 6.5 2z"/></svg>
diff --git a/webengine/views/contentful-vs-content-one.html b/webengine/views/contentful-vs-content-one.html
index c018818..064cedf 100644
--- a/webengine/views/contentful-vs-content-one.html
+++ b/webengine/views/contentful-vs-content-one.html
@@ -44,6 +44,128 @@
     .versus-faq > summary::marker { content: ""; }
   </style>
 
+  <script type="application/ld+json">
+{
+  "@context": "https://schema.org",
+  "@graph": [
+    {
+      "@type": "WebPage",
+      "@id": "https://www.content.one/contentful-vs-content-one.html#webpage",
+      "url": "https://www.content.one/contentful-vs-content-one.html",
+      "name": "Contentful vs Content.One, Headless CMS comparison, pricing, G2 reviews",
+      "description": "Contentful vs Content.One: side-by-side comparison of pricing, content limits, AI, federated multisite, SSO, and G2 reviews. See where each headless CMS fits best.",
+      "inLanguage": "en-US",
+      "datePublished": "2026-06-25",
+      "dateModified": "2026-09-11",
+      "isPartOf": {
+        "@type": "WebSite",
+        "@id": "https://www.content.one/#website",
+        "url": "https://www.content.one/",
+        "name": "Content.One"
+      },
+      "publisher": {
+        "@type": "Organization",
+        "@id": "https://www.content.one/#organization",
+        "name": "Content.One",
+        "url": "https://www.content.one/",
+        "logo": {
+          "@type": "ImageObject",
+          "url": "https://hj5v68xn.media.zestyio.com/content-one-brand-2025.png"
+        }
+      },
+      "breadcrumb": {
+        "@id": "https://www.content.one/contentful-vs-content-one.html#breadcrumb"
+      }
+    },
+    {
+      "@type": "BreadcrumbList",
+      "@id": "https://www.content.one/contentful-vs-content-one.html#breadcrumb",
+      "itemListElement": [
+        {
+          "@type": "ListItem",
+          "position": 1,
+          "name": "Home",
+          "item": "https://www.content.one/"
+        },
+        {
+          "@type": "ListItem",
+          "position": 2,
+          "name": "Compare",
+          "item": "https://www.content.one/compare.html"
+        },
+        {
+          "@type": "ListItem",
+          "position": 3,
+          "name": "Contentful vs Content.One",
+          "item": "https://www.content.one/contentful-vs-content-one.html"
+        }
+      ]
+    },
+    {
+      "@type": "FAQPage",
+      "@id": "https://www.content.one/contentful-vs-content-one.html#faq",
+      "mainEntity": [
+        {
+          "@type": "Question",
+          "name": "Is Content.One a good Contentful alternative?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "For teams running multiple sites or publishing without heavy developer involvement, yes. Contentful still wins on integration breadth and marketplace depth."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "How much does Content.One cost compared to Contentful?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Contentful publishes a free tier, Lite at $300 a month, and custom Premium pricing. Content.One is quote-based with no public tiers. Factor in that Content.One includes hosting, which is a separate cost with Contentful."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Does Contentful include hosting?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "No. Contentful is the content backend, so you provide the frontend and hosting. Content.One includes hosting and CDN delivery."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Why are Content.One reviews listed under Zesty.io?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Content.One was rebranded from Zesty.io, and the review profiles on G2 and Capterra haven't fully migrated yet."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Does Content.One support SSO and custom roles?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Yes, both are in the standard product, with permissions you can set per content type. On Contentful, SSO and custom roles require a Premium or custom plan."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Is migrating from Contentful to Content.One hard?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Effort depends on how many content types and locales you're moving. You can get an estimate from the migration tool at migration.content.one."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Which is better for franchise or multi-location brands?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Content.One is built around federated multisite, so one team manages many sites from a single platform. Contentful handles this through multiple Spaces, which adds management overhead at scale."
+          }
+        }
+      ]
+    }
+  ]
+}
+  </script>
   {{include /-/isolated-page-marketing-snippet.html}}
 </head>
 <body class="font-sans">
@@ -72,6 +194,7 @@
     <div class="max-w-5xl mx-auto px-4 sm:px-6 lg:px-8 text-center">
       <span class="inline-flex items-center px-3 py-1 rounded-full bg-white text-royal text-xs font-semibold uppercase tracking-wider mb-5">Side-by-side comparison</span>
       <h1 class="font-display text-4xl md:text-5xl lg:text-6xl font-bold mb-6">Contentful vs Content.One</h1>
+      <p class="text-sm text-white/60 mb-6"><time datetime="2026-09-11">Last updated: September 2026</time></p>
       <p class="text-lg md:text-xl text-white/80 max-w-3xl mx-auto mb-8">Contentful is a developer-first headless CMS with mature APIs and a large integration marketplace. Content.One is built for teams publishing across many sites without leaning on developers for every change.</p>
       <div class="flex flex-wrap gap-3 justify-center">
         <a href="https://launch.content.one" target="_blank" rel="noopener" class="inline-flex items-center rounded-lg bg-white text-royal hover:bg-gray-100 font-semibold px-6 py-3 transition shadow">Start a build</a>
@@ -253,6 +376,7 @@ <h2 class="font-display text-3xl md:text-4xl font-bold mb-3">The comparison</h2>
           </tbody>
         </table>
       </div>
+        <p class="text-xs text-gray-500 mt-3 italic">Accurate as of September 2026.</p>
     </div>
   </section>
 
diff --git a/webengine/views/contentstack-vs-content-one.html b/webengine/views/contentstack-vs-content-one.html
index 5d1da4c..ad3e54f 100644
--- a/webengine/views/contentstack-vs-content-one.html
+++ b/webengine/views/contentstack-vs-content-one.html
@@ -44,6 +44,136 @@
     .versus-faq > summary::marker { content: ""; }
   </style>
 
+  <script type="application/ld+json">
+{
+  "@context": "https://schema.org",
+  "@graph": [
+    {
+      "@type": "WebPage",
+      "@id": "https://www.content.one/contentstack-vs-content-one.html#webpage",
+      "url": "https://www.content.one/contentstack-vs-content-one.html",
+      "name": "Contentstack vs Content.One, Headless CMS comparison, pricing, governance",
+      "description": "Contentstack vs Content.One: side-by-side comparison of pricing, governance, multi-site delivery, SSO, and how each handles multi-location content operations.",
+      "inLanguage": "en-US",
+      "datePublished": "2026-07-23",
+      "dateModified": "2026-09-11",
+      "isPartOf": {
+        "@type": "WebSite",
+        "@id": "https://www.content.one/#website",
+        "url": "https://www.content.one/",
+        "name": "Content.One"
+      },
+      "publisher": {
+        "@type": "Organization",
+        "@id": "https://www.content.one/#organization",
+        "name": "Content.One",
+        "url": "https://www.content.one/",
+        "logo": {
+          "@type": "ImageObject",
+          "url": "https://hj5v68xn.media.zestyio.com/content-one-brand-2025.png"
+        }
+      },
+      "breadcrumb": {
+        "@id": "https://www.content.one/contentstack-vs-content-one.html#breadcrumb"
+      }
+    },
+    {
+      "@type": "BreadcrumbList",
+      "@id": "https://www.content.one/contentstack-vs-content-one.html#breadcrumb",
+      "itemListElement": [
+        {
+          "@type": "ListItem",
+          "position": 1,
+          "name": "Home",
+          "item": "https://www.content.one/"
+        },
+        {
+          "@type": "ListItem",
+          "position": 2,
+          "name": "Compare",
+          "item": "https://www.content.one/compare.html"
+        },
+        {
+          "@type": "ListItem",
+          "position": 3,
+          "name": "Contentstack vs Content.One",
+          "item": "https://www.content.one/contentstack-vs-content-one.html"
+        }
+      ]
+    },
+    {
+      "@type": "FAQPage",
+      "@id": "https://www.content.one/contentstack-vs-content-one.html#faq",
+      "mainEntity": [
+        {
+          "@type": "Question",
+          "name": "Is Contentstack a full DXP or just a headless CMS?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "It's primarily a headless CMS with some DXP-style add-ons (personalization, A/B testing) available depending on plan. The core product is content management via API, not an all-in-one experience builder."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Does Content.One require a developer to launch a site?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "No. Content.One's agentic page builder lets marketers generate and edit pages directly. Developers still have full API access if you want custom-built sections, but it's not required to launch."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "How does Contentstack's pricing compare to Content.One's?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Contentstack starts free (Explorer) and scales into custom enterprise contracts, with Scale-tier deals commonly landing in the $100,000 to $200,000+/year range according to Vendr's benchmark data. Content.One also has a free entry tier, with paid plans priced around instance count and support level rather than a separate enterprise SKU."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Does Content.One include SSO and audit logs by default?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Yes, both ship as standard platform features rather than an add-on tier."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Can I migrate an existing Contentstack instance to Content.One?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Yes. Content.One's migration.content.one tool assesses your current content model and gives you a timeline and cost estimate before you commit, and Engineer on Demand can handle the technical migration work directly."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Which platform fits a franchise or multi-location network better?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Content.One, mainly because of the built-in multi-site governance model. Contentstack can support a multi-location setup, but you're building the local-unit permissions and approval structure yourself rather than starting from one."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Does Content.One support headless delivery too, or only visual page building?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Both. Content.One serves HTML, JSON, or both from the same content model, so you can run it fully headless for a mobile app or other channel while still using the visual builder for the website."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Why are Content.One reviews listed under Zesty.io?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Content.One was rebranded from Zesty.io, and the review profiles on G2 and Capterra haven't fully migrated yet."
+          }
+        }
+      ]
+    }
+  ]
+}
+  </script>
   {{include /-/isolated-page-marketing-snippet.html}}
 </head>
 <body class="font-sans">
@@ -72,6 +202,7 @@
     <div class="max-w-5xl mx-auto px-4 sm:px-6 lg:px-8 text-center">
       <span class="inline-flex items-center px-3 py-1 rounded-full bg-white text-royal text-xs font-semibold uppercase tracking-wider mb-5">Side-by-side comparison</span>
       <h1 class="font-display text-4xl md:text-5xl lg:text-6xl font-bold mb-6">Contentstack vs Content.One</h1>
+      <p class="text-sm text-white/60 mb-6"><time datetime="2026-09-11">Last updated: September 2026</time></p>
       <p class="text-lg md:text-xl text-white/80 max-w-3xl mx-auto mb-8">Contentstack is a pure headless CMS built for developer-led teams. Content.One pairs the same headless API with an agentic page builder, so marketing-led, multi-location networks can ship pages without waiting on a dev queue.</p>
       <div class="flex flex-wrap gap-3 justify-center">
         <a href="https://launch.content.one" target="_blank" rel="noopener" class="inline-flex items-center rounded-lg bg-white text-royal hover:bg-gray-100 font-semibold px-6 py-3 transition shadow">Start a build</a>
@@ -258,6 +389,7 @@ <h2 class="font-display text-3xl md:text-4xl font-bold mb-3">The comparison</h2>
           </tbody>
         </table>
       </div>
+        <p class="text-xs text-gray-500 mt-3 italic">Accurate as of September 2026.</p>
     </div>
   </section>
 
diff --git a/webengine/views/drupal-vs-content-one.html b/webengine/views/drupal-vs-content-one.html
index ccae3f4..edbe89b 100644
--- a/webengine/views/drupal-vs-content-one.html
+++ b/webengine/views/drupal-vs-content-one.html
@@ -44,6 +44,136 @@
     .versus-faq > summary::marker { content: ""; }
   </style>
 
+  <script type="application/ld+json">
+{
+  "@context": "https://schema.org",
+  "@graph": [
+    {
+      "@type": "WebPage",
+      "@id": "https://www.content.one/drupal-vs-content-one.html#webpage",
+      "url": "https://www.content.one/drupal-vs-content-one.html",
+      "name": "Drupal vs Content.One, CMS comparison, cost of ownership, G2 reviews",
+      "description": "Drupal vs Content.One: side-by-side comparison of cost of ownership, hosting, multisite, developer dependency, SSO, AI agents, and G2 reviews. See where each CMS fits.",
+      "inLanguage": "en-US",
+      "datePublished": "2026-07-10",
+      "dateModified": "2026-09-11",
+      "isPartOf": {
+        "@type": "WebSite",
+        "@id": "https://www.content.one/#website",
+        "url": "https://www.content.one/",
+        "name": "Content.One"
+      },
+      "publisher": {
+        "@type": "Organization",
+        "@id": "https://www.content.one/#organization",
+        "name": "Content.One",
+        "url": "https://www.content.one/",
+        "logo": {
+          "@type": "ImageObject",
+          "url": "https://hj5v68xn.media.zestyio.com/content-one-brand-2025.png"
+        }
+      },
+      "breadcrumb": {
+        "@id": "https://www.content.one/drupal-vs-content-one.html#breadcrumb"
+      }
+    },
+    {
+      "@type": "BreadcrumbList",
+      "@id": "https://www.content.one/drupal-vs-content-one.html#breadcrumb",
+      "itemListElement": [
+        {
+          "@type": "ListItem",
+          "position": 1,
+          "name": "Home",
+          "item": "https://www.content.one/"
+        },
+        {
+          "@type": "ListItem",
+          "position": 2,
+          "name": "Compare",
+          "item": "https://www.content.one/compare.html"
+        },
+        {
+          "@type": "ListItem",
+          "position": 3,
+          "name": "Drupal vs Content.One",
+          "item": "https://www.content.one/drupal-vs-content-one.html"
+        }
+      ]
+    },
+    {
+      "@type": "FAQPage",
+      "@id": "https://www.content.one/drupal-vs-content-one.html#faq",
+      "mainEntity": [
+        {
+          "@type": "Question",
+          "name": "Is Content.One a good Drupal alternative?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "For multi-site teams that want federated reach without hosting and maintaining the platform themselves, yes. Drupal is the stronger pick if you want open-source control and have the developers to run it."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Is Drupal free?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "The software is free and open-source, so there's no license fee. The real cost is Drupal hosting, developers or an agency to build and maintain the site, and the time spent on updates. Content.One is quote-based with hosting and maintenance included."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Does Drupal include hosting?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "No. You self-host Drupal or pay a specialist host such as Acquia, Pantheon, or Platform.sh. Content.One includes hosting and global CDN delivery."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Do I need a developer to use Drupal?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "For setup and anything beyond a starter template, usually yes. Drupal CMS 2.0 added Canvas for on-page editing and site templates, which helps marketers, but modules, theming, and maintenance still lean on developers. Content.One is built so a non-developer can publish from the start."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "How does Drupal multisite compare to Content.One?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Drupal multisite is native but runs on a shared codebase you host and maintain, so updates and patches apply across every site. Content.One offers managed federated multisite, where one team runs many sites from a single platform without the codebase upkeep."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Does Drupal support AI agents and MCP?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Yes. Drupal CMS 2.0 ships AI tools, and Drupal can act as an MCP server through contributed modules like mcp_server and MCP Tools. Those are community-maintained and still pre-stable, and you install and configure them. Content.One ships a native MCP server."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Is migrating from Drupal to Content.One hard?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Effort depends on how many sites, content types, and languages you're moving. You can get an estimate from the migration tool at migration.content.one."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Why are Content.One reviews listed under Zesty.io?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Content.One was rebranded from Zesty.io, and the review profiles on G2 and Capterra haven't fully migrated yet."
+          }
+        }
+      ]
+    }
+  ]
+}
+  </script>
   {{include /-/isolated-page-marketing-snippet.html}}
 </head>
 <body class="font-sans">
@@ -72,6 +202,7 @@
     <div class="max-w-5xl mx-auto px-4 sm:px-6 lg:px-8 text-center">
       <span class="inline-flex items-center px-3 py-1 rounded-full bg-white text-royal text-xs font-semibold uppercase tracking-wider mb-5">Side-by-side comparison</span>
       <h1 class="font-display text-4xl md:text-5xl lg:text-6xl font-bold mb-6">Drupal vs Content.One</h1>
+      <p class="text-sm text-white/60 mb-6"><time datetime="2026-09-11">Last updated: September 2026</time></p>
       <p class="text-lg md:text-xl text-white/80 max-w-3xl mx-auto mb-8">Drupal is a free, open-source CMS with deep flexibility and a huge module library, run and maintained by you or an agency. Content.One gives multi-site teams the same federated reach as a managed platform, with hosting and upkeep handled.</p>
       <div class="flex flex-wrap gap-3 justify-center">
         <a href="https://launch.content.one" target="_blank" rel="noopener" class="inline-flex items-center rounded-lg bg-white text-royal hover:bg-gray-100 font-semibold px-6 py-3 transition shadow">Start a build</a>
@@ -255,6 +386,7 @@ <h2 class="font-display text-3xl md:text-4xl font-bold mb-3">The comparison</h2>
           </tbody>
         </table>
       </div>
+        <p class="text-xs text-gray-500 mt-3 italic">Accurate as of September 2026.</p>
     </div>
   </section>
 
diff --git a/webengine/views/duda-vs-content-one.html b/webengine/views/duda-vs-content-one.html
index fd4b179..79d7284 100644
--- a/webengine/views/duda-vs-content-one.html
+++ b/webengine/views/duda-vs-content-one.html
@@ -45,6 +45,128 @@
     .versus-faq > summary::marker { content: ""; }
   </style>
 
+  <script type="application/ld+json">
+{
+  "@context": "https://schema.org",
+  "@graph": [
+    {
+      "@type": "WebPage",
+      "@id": "https://www.content.one/duda-vs-content-one.html#webpage",
+      "url": "https://www.content.one/duda-vs-content-one.html",
+      "name": "Duda vs Content.One, pricing, multi-site governance, migration",
+      "description": "Comparing Duda and Content.One for a multi-site network? See published pricing, real cost at 80 sites, shared content models, MCP access, and where each fits.",
+      "inLanguage": "en-US",
+      "datePublished": "2026-08-30",
+      "dateModified": "2026-09-11",
+      "isPartOf": {
+        "@type": "WebSite",
+        "@id": "https://www.content.one/#website",
+        "url": "https://www.content.one/",
+        "name": "Content.One"
+      },
+      "publisher": {
+        "@type": "Organization",
+        "@id": "https://www.content.one/#organization",
+        "name": "Content.One",
+        "url": "https://www.content.one/",
+        "logo": {
+          "@type": "ImageObject",
+          "url": "https://hj5v68xn.media.zestyio.com/content-one-brand-2025.png"
+        }
+      },
+      "breadcrumb": {
+        "@id": "https://www.content.one/duda-vs-content-one.html#breadcrumb"
+      }
+    },
+    {
+      "@type": "BreadcrumbList",
+      "@id": "https://www.content.one/duda-vs-content-one.html#breadcrumb",
+      "itemListElement": [
+        {
+          "@type": "ListItem",
+          "position": 1,
+          "name": "Home",
+          "item": "https://www.content.one/"
+        },
+        {
+          "@type": "ListItem",
+          "position": 2,
+          "name": "Compare",
+          "item": "https://www.content.one/compare.html"
+        },
+        {
+          "@type": "ListItem",
+          "position": 3,
+          "name": "Duda vs Content.One",
+          "item": "https://www.content.one/duda-vs-content-one.html"
+        }
+      ]
+    },
+    {
+      "@type": "FAQPage",
+      "@id": "https://www.content.one/duda-vs-content-one.html#faq",
+      "mainEntity": [
+        {
+          "@type": "Question",
+          "name": "How much does Duda cost for a network of 50 or 100 sites?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Take the plan price, then add $17 a month for every site past the ones included. On the Agency plan at $69 a month with four sites included, 50 sites is about $851 a month and 100 sites is about $1,701 a month on monthly billing. Annual billing brings both down by roughly a quarter."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Is Duda a CMS?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "It manages website content, so in the broad sense yes, and G2 lists it under web content management. In practice it works as a site-scoped builder rather than a structured content platform, so content lives inside each site instead of in a shared model several sites can draw from."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Can Duda publish a change across all my locations at once?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Not through the editor. Templates and sections carry design between sites, but content changes happen per site unless you script them through the partner API or arrange it on a Custom plan."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Does Duda work with AI agents and MCP?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Yes. Duda ships an MCP server, with access starting on the Agency plan, and its AI features draw on a pool of 150 monthly credits with paid top-ups. Content.One also ships a native MCP server, included in the platform, so both support agent-driven content work."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Why are Content.One reviews listed under Zesty.io?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Content.One was rebranded from Zesty.io, and the review profiles on G2 and Capterra have not fully migrated yet."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "What does moving from Duda to Content.One involve?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Content.One runs the migration in parallel with your live sites, and Engineer on Demand covers the implementation work directly. You can get a scoped estimate at migration.content.one."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Should a franchise network use Duda or Content.One?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "If franchisees buy and run their own sites independently, Duda handles that well. If corporate owns the brand standards and needs to push updates across every location while letting each one manage what is local, that is what federated multisite is for."
+          }
+        }
+      ]
+    }
+  ]
+}
+  </script>
   {{include /-/isolated-page-marketing-snippet.html}}
 </head>
 <body class="font-sans">
@@ -73,6 +195,7 @@
     <div class="max-w-5xl mx-auto px-4 sm:px-6 lg:px-8 text-center">
       <span class="inline-flex items-center px-3 py-1 rounded-full bg-white text-royal text-xs font-semibold uppercase tracking-wider mb-5">Side-by-side comparison</span>
       <h1 class="font-display text-4xl md:text-5xl lg:text-6xl font-bold mb-6">Duda vs Content.One</h1>
+      <p class="text-sm text-white/60 mb-6"><time datetime="2026-09-11">Last updated: September 2026</time></p>
       <p class="text-lg md:text-xl text-white/80 max-w-3xl mx-auto mb-8">Duda is a website builder made for agencies, SaaS platforms, and hosts that sell websites to other businesses. Content.One is built for franchise, multi-location, and federated networks that own their properties and need to govern content across all of them from one place.</p>
       <div class="flex flex-wrap gap-3 justify-center">
         <a href="https://launch.content.one" target="_blank" rel="noopener" class="inline-flex items-center rounded-lg bg-white text-royal hover:bg-gray-100 font-semibold px-6 py-3 transition shadow">Start a build</a>
@@ -210,7 +333,7 @@ <h3 class="font-display text-lg font-semibold m-0">Both ship MCP, on different t
     <div class="max-w-7xl mx-auto px-4 sm:px-6 lg:px-8">
       <div class="text-center max-w-3xl mx-auto mb-10">
         <h2 class="font-display text-3xl md:text-4xl font-bold mb-3">The comparison</h2>
-        <p class="text-gray-600">Capability by capability. Why each one matters in the right-hand column. Accurate as of August 2026.</p>
+        <p class="text-gray-600">Capability by capability. Why each one matters in the right-hand column. Accurate as of September 2026.</p>
       </div>
       <div class="overflow-x-auto rounded-2xl border border-gray-200 bg-white shadow-sm">
         <table class="w-full text-sm border-collapse min-w-[760px]">
@@ -256,6 +379,7 @@ <h2 class="font-display text-3xl md:text-4xl font-bold mb-3">The comparison</h2>
           </tbody>
         </table>
       </div>
+        <p class="text-xs text-gray-500 mt-3 italic">Accurate as of September 2026.</p>
     </div>
   </section>
 
diff --git a/webengine/views/optimizely-vs-content-one.html b/webengine/views/optimizely-vs-content-one.html
index 91401b1..6deac91 100644
--- a/webengine/views/optimizely-vs-content-one.html
+++ b/webengine/views/optimizely-vs-content-one.html
@@ -44,6 +44,120 @@
     .versus-faq > summary::marker { content: ""; }
   </style>
 
+  <script type="application/ld+json">
+{
+  "@context": "https://schema.org",
+  "@graph": [
+    {
+      "@type": "WebPage",
+      "@id": "https://www.content.one/optimizely-vs-content-one.html#webpage",
+      "url": "https://www.content.one/optimizely-vs-content-one.html",
+      "name": "Optimizely vs Content.One, CMS 13 migration, pricing, governance",
+      "description": "Comparing Optimizely and Content.One for content operations? See real pricing, the CMS 13 migration wave, and where each platform actually fits.",
+      "inLanguage": "en-US",
+      "datePublished": "2026-07-25",
+      "dateModified": "2026-09-11",
+      "isPartOf": {
+        "@type": "WebSite",
+        "@id": "https://www.content.one/#website",
+        "url": "https://www.content.one/",
+        "name": "Content.One"
+      },
+      "publisher": {
+        "@type": "Organization",
+        "@id": "https://www.content.one/#organization",
+        "name": "Content.One",
+        "url": "https://www.content.one/",
+        "logo": {
+          "@type": "ImageObject",
+          "url": "https://hj5v68xn.media.zestyio.com/content-one-brand-2025.png"
+        }
+      },
+      "breadcrumb": {
+        "@id": "https://www.content.one/optimizely-vs-content-one.html#breadcrumb"
+      }
+    },
+    {
+      "@type": "BreadcrumbList",
+      "@id": "https://www.content.one/optimizely-vs-content-one.html#breadcrumb",
+      "itemListElement": [
+        {
+          "@type": "ListItem",
+          "position": 1,
+          "name": "Home",
+          "item": "https://www.content.one/"
+        },
+        {
+          "@type": "ListItem",
+          "position": 2,
+          "name": "Compare",
+          "item": "https://www.content.one/compare.html"
+        },
+        {
+          "@type": "ListItem",
+          "position": 3,
+          "name": "Optimizely vs Content.One",
+          "item": "https://www.content.one/optimizely-vs-content-one.html"
+        }
+      ]
+    },
+    {
+      "@type": "FAQPage",
+      "@id": "https://www.content.one/optimizely-vs-content-one.html#faq",
+      "mainEntity": [
+        {
+          "@type": "Question",
+          "name": "How much does Optimizely actually cost compared to Content.One?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Optimizely doesn't publish pricing. Real contracts start around $36,000 a year and commonly reach $150,000 to $300,000+ for enterprise deployments, often landing 100% to 200% above the initial quote once professional services are included. Content.One's pricing scales with instance count, with governance and security features included rather than priced separately."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "What does Optimizely's CMS 13 migration actually require?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "It made Optimizely Graph mandatory, introduced Visual Builder as the default editing experience, and moved the platform to .NET 10. Organizations on earlier CMS versions face real migration work, including API and integration changes."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Does Content.One have an equivalent AI feature to Opal AI?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Yes. Content.One's agentic content and page generation is included in the platform rather than priced through a separate credit-based consumption model like Opal AI."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Do we need .NET developers to run Content.One the way we'd need them for Optimizely?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "No. Content.One's agentic page builder lets marketers build and edit pages without touching code. Engineer on Demand covers any genuinely custom development work on an as-needed basis."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Is Optimizely a bad platform?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "No. It's a mature, capable enterprise DXP, particularly strong on localization, experimentation, and regulatory compliance. It's built for large organizations with dedicated development teams, which is a different buyer than the franchise, multi-location, and federated organizations Content.One is built for."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Can Content.One migrate an existing Optimizely site?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Yes. Content.One's migration model runs in parallel to the existing site, and Engineer on Demand covers the implementation work directly rather than requiring a separate systems integrator engagement."
+          }
+        }
+      ]
+    }
+  ]
+}
+  </script>
   {{include /-/isolated-page-marketing-snippet.html}}
 </head>
 <body class="font-sans">
@@ -72,6 +186,7 @@
     <div class="max-w-5xl mx-auto px-4 sm:px-6 lg:px-8 text-center">
       <span class="inline-flex items-center px-3 py-1 rounded-full bg-white text-royal text-xs font-semibold uppercase tracking-wider mb-5">Side-by-side comparison</span>
       <h1 class="font-display text-4xl md:text-5xl lg:text-6xl font-bold mb-6">Optimizely vs Content.One</h1>
+      <p class="text-sm text-white/60 mb-6"><time datetime="2026-09-11">Last updated: September 2026</time></p>
       <p class="text-lg md:text-xl text-white/80 max-w-3xl mx-auto mb-8">Optimizely is a mature, .NET-based enterprise DXP built for organizations with dedicated development teams. Content.One is built for franchise, multi-location, and federated networks that need marketer-led publishing without a standing .NET bench or a multi-year implementation budget.</p>
       <div class="flex flex-wrap gap-3 justify-center">
         <a href="https://launch.content.one" target="_blank" rel="noopener" class="inline-flex items-center rounded-lg bg-white text-royal hover:bg-gray-100 font-semibold px-6 py-3 transition shadow">Start a build</a>
@@ -252,6 +367,7 @@ <h2 class="font-display text-3xl md:text-4xl font-bold mb-3">The comparison</h2>
           </tbody>
         </table>
       </div>
+        <p class="text-xs text-gray-500 mt-3 italic">Accurate as of September 2026.</p>
     </div>
   </section>
 
diff --git a/webengine/views/sanity-vs-content-one.html b/webengine/views/sanity-vs-content-one.html
index c8371c8..ae4457c 100644
--- a/webengine/views/sanity-vs-content-one.html
+++ b/webengine/views/sanity-vs-content-one.html
@@ -44,6 +44,136 @@
     .versus-faq > summary::marker { content: ""; }
   </style>
 
+  <script type="application/ld+json">
+{
+  "@context": "https://schema.org",
+  "@graph": [
+    {
+      "@type": "WebPage",
+      "@id": "https://www.content.one/sanity-vs-content-one.html#webpage",
+      "url": "https://www.content.one/sanity-vs-content-one.html",
+      "name": "Sanity vs Content.One, Headless CMS comparison, pricing, G2 reviews",
+      "description": "Sanity vs Content.One: side-by-side comparison of pricing, hosting, developer dependency, federated multisite, SSO, AI agents, and G2 reviews. See where each headless CMS fits.",
+      "inLanguage": "en-US",
+      "datePublished": "2026-07-10",
+      "dateModified": "2026-09-11",
+      "isPartOf": {
+        "@type": "WebSite",
+        "@id": "https://www.content.one/#website",
+        "url": "https://www.content.one/",
+        "name": "Content.One"
+      },
+      "publisher": {
+        "@type": "Organization",
+        "@id": "https://www.content.one/#organization",
+        "name": "Content.One",
+        "url": "https://www.content.one/",
+        "logo": {
+          "@type": "ImageObject",
+          "url": "https://hj5v68xn.media.zestyio.com/content-one-brand-2025.png"
+        }
+      },
+      "breadcrumb": {
+        "@id": "https://www.content.one/sanity-vs-content-one.html#breadcrumb"
+      }
+    },
+    {
+      "@type": "BreadcrumbList",
+      "@id": "https://www.content.one/sanity-vs-content-one.html#breadcrumb",
+      "itemListElement": [
+        {
+          "@type": "ListItem",
+          "position": 1,
+          "name": "Home",
+          "item": "https://www.content.one/"
+        },
+        {
+          "@type": "ListItem",
+          "position": 2,
+          "name": "Compare",
+          "item": "https://www.content.one/compare.html"
+        },
+        {
+          "@type": "ListItem",
+          "position": 3,
+          "name": "Sanity vs Content.One",
+          "item": "https://www.content.one/sanity-vs-content-one.html"
+        }
+      ]
+    },
+    {
+      "@type": "FAQPage",
+      "@id": "https://www.content.one/sanity-vs-content-one.html#faq",
+      "mainEntity": [
+        {
+          "@type": "Question",
+          "name": "Is Content.One a good Sanity alternative?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "For teams running multiple sites or publishing without heavy developer involvement, yes. Sanity is the stronger pick if you're developer-led and want maximum control of the content model in code."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "How much does Sanity cost compared to Content.One?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Sanity CMS pricing is Free, then Growth at $15 per seat a month, with usage-based charges on API requests, documents, and bandwidth, and Enterprise quoted custom. Content.One is quote-based with no public tiers. Factor in that Content.One includes hosting, which you pay for separately with Sanity."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Does Sanity include hosting?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "No. Sanity hosts your content in the Content Lake and hosts Sanity Studio, but you build and host the actual website frontend yourself. Content.One includes hosting and CDN delivery."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Do I need a developer to use Sanity?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "To set it up, yes. Schemas and the Studio are configured in code, and querying uses GROQ. Once a developer has built it, editors can publish without code. Content.One is built so a non-developer can model and publish from the start."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Does Sanity work with AI agents?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Yes. Sanity has a native MCP server at mcp.sanity.io plus Agent Context, so AI agents can query and update content. Content.One also ships a native MCP server, so both platforms support agent-driven content operations."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Does Content.One support SSO and custom roles?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Yes, both are in the standard product, with permissions you can set per content type. On Sanity, SSO/SAML and custom roles require the Enterprise tier or a paid Growth add-on."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Why are Content.One reviews listed under Zesty.io?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Content.One was rebranded from Zesty.io, and the review profiles on G2 and Capterra haven't fully migrated yet."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Which is better for franchise or multi-location brands?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Content.One is built around federated multisite, so one team manages many sites from a single platform. Sanity handles multiple sites through separate datasets and projects, which adds setup and management overhead at scale."
+          }
+        }
+      ]
+    }
+  ]
+}
+  </script>
   {{include /-/isolated-page-marketing-snippet.html}}
 </head>
 <body class="font-sans">
@@ -72,6 +202,7 @@
     <div class="max-w-5xl mx-auto px-4 sm:px-6 lg:px-8 text-center">
       <span class="inline-flex items-center px-3 py-1 rounded-full bg-white text-royal text-xs font-semibold uppercase tracking-wider mb-5">Side-by-side comparison</span>
       <h1 class="font-display text-4xl md:text-5xl lg:text-6xl font-bold mb-6">Sanity vs Content.One</h1>
+      <p class="text-sm text-white/60 mb-6"><time datetime="2026-09-11">Last updated: September 2026</time></p>
       <p class="text-lg md:text-xl text-white/80 max-w-3xl mx-auto mb-8">Sanity is the most developer-first headless CMS in the category, with schema defined in code and GROQ for querying. Content.One is built for teams publishing across many sites who'd rather not staff a frontend build to do it.</p>
       <div class="flex flex-wrap gap-3 justify-center">
         <a href="https://launch.content.one" target="_blank" rel="noopener" class="inline-flex items-center rounded-lg bg-white text-royal hover:bg-gray-100 font-semibold px-6 py-3 transition shadow">Start a build</a>
@@ -254,6 +385,7 @@ <h2 class="font-display text-3xl md:text-4xl font-bold mb-3">The comparison</h2>
           </tbody>
         </table>
       </div>
+        <p class="text-xs text-gray-500 mt-3 italic">Accurate as of September 2026.</p>
     </div>
   </section>
 
diff --git a/webengine/views/sitecore-vs-content-one.html b/webengine/views/sitecore-vs-content-one.html
index 57389b8..866d09b 100644
--- a/webengine/views/sitecore-vs-content-one.html
+++ b/webengine/views/sitecore-vs-content-one.html
@@ -44,6 +44,136 @@
     .versus-faq > summary::marker { content: ""; }
   </style>
 
+  <script type="application/ld+json">
+{
+  "@context": "https://schema.org",
+  "@graph": [
+    {
+      "@type": "WebPage",
+      "@id": "https://www.content.one/sitecore-vs-content-one.html#webpage",
+      "url": "https://www.content.one/sitecore-vs-content-one.html",
+      "name": "Sitecore vs Content.One, DXP comparison, pricing, G2 reviews",
+      "description": "Sitecore vs Content.One: side-by-side comparison of pricing, implementation, personalization, federated multisite, SSO, and G2 reviews. See where each platform fits best.",
+      "inLanguage": "en-US",
+      "datePublished": "2026-06-30",
+      "dateModified": "2026-09-11",
+      "isPartOf": {
+        "@type": "WebSite",
+        "@id": "https://www.content.one/#website",
+        "url": "https://www.content.one/",
+        "name": "Content.One"
+      },
+      "publisher": {
+        "@type": "Organization",
+        "@id": "https://www.content.one/#organization",
+        "name": "Content.One",
+        "url": "https://www.content.one/",
+        "logo": {
+          "@type": "ImageObject",
+          "url": "https://hj5v68xn.media.zestyio.com/content-one-brand-2025.png"
+        }
+      },
+      "breadcrumb": {
+        "@id": "https://www.content.one/sitecore-vs-content-one.html#breadcrumb"
+      }
+    },
+    {
+      "@type": "BreadcrumbList",
+      "@id": "https://www.content.one/sitecore-vs-content-one.html#breadcrumb",
+      "itemListElement": [
+        {
+          "@type": "ListItem",
+          "position": 1,
+          "name": "Home",
+          "item": "https://www.content.one/"
+        },
+        {
+          "@type": "ListItem",
+          "position": 2,
+          "name": "Compare",
+          "item": "https://www.content.one/compare.html"
+        },
+        {
+          "@type": "ListItem",
+          "position": 3,
+          "name": "Sitecore vs Content.One",
+          "item": "https://www.content.one/sitecore-vs-content-one.html"
+        }
+      ]
+    },
+    {
+      "@type": "FAQPage",
+      "@id": "https://www.content.one/sitecore-vs-content-one.html#faq",
+      "mainEntity": [
+        {
+          "@type": "Question",
+          "name": "Is Content.One a good Sitecore alternative?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "For teams that want fast, marketer-led publishing without enterprise cost and complexity, yes. Sitecore still wins for deep personalization and a CDP at large scale."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Sitecore vs Content.One: which costs more?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Sitecore is custom-priced and usually the larger spend. XM Cloud starts roughly $60K to $100K a year for limited scope, plus implementation that often runs $150K to $350K or more. Content.One is quote-based and includes hosting."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Do I need developers to run Sitecore?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Usually yes. Sitecore builds typically need .NET or Sitecore-certified specialists, often through a partner. Content.One's visual builder lets non-developers publish."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "How long does a Sitecore implementation take?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Commonly six to eighteen months depending on scope and modules. Content.One onboarding is much shorter."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Does Content.One handle personalization like Sitecore?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Content.One has built-in personalization and analytics. Sitecore's personalization and CDP go deeper for large enterprises."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Why are Content.One reviews listed under Zesty.io?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Content.One was rebranded from Zesty.io, and the review profiles on G2 and Capterra haven't fully migrated yet."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Is migrating from Sitecore to Content.One hard?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "It depends on content volume, your multisite setup, and custom integrations. You can get an estimate from the migration tool at migration.content.one."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Which is better for large multi-brand enterprises?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Sitecore is proven at very large scale with deep personalization. Content.One fits multi-site and multi-brand teams that prioritize speed and lower total cost."
+          }
+        }
+      ]
+    }
+  ]
+}
+  </script>
   {{include /-/isolated-page-marketing-snippet.html}}
 </head>
 <body class="font-sans">
@@ -72,6 +202,7 @@
     <div class="max-w-5xl mx-auto px-4 sm:px-6 lg:px-8 text-center">
       <span class="inline-flex items-center px-3 py-1 rounded-full bg-white text-royal text-xs font-semibold uppercase tracking-wider mb-5">Side-by-side comparison</span>
       <h1 class="font-display text-4xl md:text-5xl lg:text-6xl font-bold mb-6">Sitecore vs Content.One</h1>
+      <p class="text-sm text-white/60 mb-6"><time datetime="2026-09-11">Last updated: September 2026</time></p>
       <p class="text-lg md:text-xl text-white/80 max-w-3xl mx-auto mb-8">Sitecore vs Content.One usually comes down to weight. Sitecore is a full enterprise DXP with deep personalization and marketing automation. Content.One is a leaner platform for publishing across many sites without a long implementation.</p>
       <div class="flex flex-wrap gap-3 justify-center">
         <a href="https://launch.content.one" target="_blank" rel="noopener" class="inline-flex items-center rounded-lg bg-white text-royal hover:bg-gray-100 font-semibold px-6 py-3 transition shadow">Start a build</a>
@@ -258,6 +389,7 @@ <h2 class="font-display text-3xl md:text-4xl font-bold mb-3">The comparison</h2>
           </tbody>
         </table>
       </div>
+        <p class="text-xs text-gray-500 mt-3 italic">Accurate as of September 2026.</p>
     </div>
   </section>
 
diff --git a/webengine/views/storyblok-vs-content-one.html b/webengine/views/storyblok-vs-content-one.html
index 44953a3..f641c01 100644
--- a/webengine/views/storyblok-vs-content-one.html
+++ b/webengine/views/storyblok-vs-content-one.html
@@ -44,6 +44,120 @@
     .versus-faq > summary::marker { content: ""; }
   </style>
 
+  <script type="application/ld+json">
+{
+  "@context": "https://schema.org",
+  "@graph": [
+    {
+      "@type": "WebPage",
+      "@id": "https://www.content.one/storyblok-vs-content-one.html#webpage",
+      "url": "https://www.content.one/storyblok-vs-content-one.html",
+      "name": "Storyblok vs Content.One, headless CMS comparison, pricing, governance",
+      "description": "Comparing Storyblok and Content.One for multi-location or federated content teams? See pricing, governance, and where each one actually fits.",
+      "inLanguage": "en-US",
+      "datePublished": "2026-07-23",
+      "dateModified": "2026-09-11",
+      "isPartOf": {
+        "@type": "WebSite",
+        "@id": "https://www.content.one/#website",
+        "url": "https://www.content.one/",
+        "name": "Content.One"
+      },
+      "publisher": {
+        "@type": "Organization",
+        "@id": "https://www.content.one/#organization",
+        "name": "Content.One",
+        "url": "https://www.content.one/",
+        "logo": {
+          "@type": "ImageObject",
+          "url": "https://hj5v68xn.media.zestyio.com/content-one-brand-2025.png"
+        }
+      },
+      "breadcrumb": {
+        "@id": "https://www.content.one/storyblok-vs-content-one.html#breadcrumb"
+      }
+    },
+    {
+      "@type": "BreadcrumbList",
+      "@id": "https://www.content.one/storyblok-vs-content-one.html#breadcrumb",
+      "itemListElement": [
+        {
+          "@type": "ListItem",
+          "position": 1,
+          "name": "Home",
+          "item": "https://www.content.one/"
+        },
+        {
+          "@type": "ListItem",
+          "position": 2,
+          "name": "Compare",
+          "item": "https://www.content.one/compare.html"
+        },
+        {
+          "@type": "ListItem",
+          "position": 3,
+          "name": "Storyblok vs Content.One",
+          "item": "https://www.content.one/storyblok-vs-content-one.html"
+        }
+      ]
+    },
+    {
+      "@type": "FAQPage",
+      "@id": "https://www.content.one/storyblok-vs-content-one.html#faq",
+      "mainEntity": [
+        {
+          "@type": "Question",
+          "name": "Is Storyblok good for a franchise or multi-location network?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "It can work for a small number of locations, but its governance model is folder-level rather than purpose-built for federation. Organizations running dozens or hundreds of locations typically need a governance layer Storyblok's architecture doesn't natively provide."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "How does Storyblok's pricing compare to Content.One's?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Storyblok starts free and moves to $99/month for 5 seats, then $349/month for 15 seats, with Premium pricing custom above that. Content.One also starts free and scales with instance count rather than seat count, with governance and security features included rather than gated to a higher tier."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Does Content.One have a visual editor like Storyblok's?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Yes. Content.One's marketers edit visually on the rendered page, with the design system enforced through the developer-built component structure, similar in spirit to Storyblok's approach but built around federated governance from the start."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Can I migrate an existing Storyblok site to Content.One?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Yes. Content.One's migration model runs in parallel, meaning the existing site stays live while the new platform is built and validated, and Engineer on Demand covers implementation support directly rather than requiring a separate agency engagement."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "What's the main tradeoff with Storyblok's component-based architecture?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "The initial component library has to be built by developers before marketers get real autonomy, the same tradeoff Content.One makes. The difference shows up afterward: Content.One enforces multi-site governance as a platform feature, while Storyblok's is a folder-level workaround."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Is Storyblok recognized by analyst firms?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Yes. It was named a Leader in the 2025 IDC MarketScape for AI-enabled headless CMS and was the subject of a Forrester Total Economic Impact study finding a 582% three-year ROI. It does not currently appear in the Gartner Magic Quadrant for Digital Experience Platforms or the Forrester Wave for Content Management Systems."
+          }
+        }
+      ]
+    }
+  ]
+}
+  </script>
   {{include /-/isolated-page-marketing-snippet.html}}
 </head>
 <body class="font-sans">
@@ -72,6 +186,7 @@
     <div class="max-w-5xl mx-auto px-4 sm:px-6 lg:px-8 text-center">
       <span class="inline-flex items-center px-3 py-1 rounded-full bg-white text-royal text-xs font-semibold uppercase tracking-wider mb-5">Side-by-side comparison</span>
       <h1 class="font-display text-4xl md:text-5xl lg:text-6xl font-bold mb-6">Storyblok vs Content.One</h1>
+      <p class="text-sm text-white/60 mb-6"><time datetime="2026-09-11">Last updated: September 2026</time></p>
       <p class="text-lg md:text-xl text-white/80 max-w-3xl mx-auto mb-8">Storyblok and Content.One solve the same core problem, marketers editing visually without breaking developer-built components, but at different scales. Storyblok's governance is folder-level. Content.One is built for federated organizations running dozens to hundreds of sites under one brand.</p>
       <div class="flex flex-wrap gap-3 justify-center">
         <a href="https://launch.content.one" target="_blank" rel="noopener" class="inline-flex items-center rounded-lg bg-white text-royal hover:bg-gray-100 font-semibold px-6 py-3 transition shadow">Start a build</a>
@@ -251,6 +366,7 @@ <h2 class="font-display text-3xl md:text-4xl font-bold mb-3">The comparison</h2>
           </tbody>
         </table>
       </div>
+        <p class="text-xs text-gray-500 mt-3 italic">Accurate as of September 2026.</p>
     </div>
   </section>
 
diff --git a/webengine/views/webflow-vs-content-one.html b/webengine/views/webflow-vs-content-one.html
index 82b1149..8f45e80 100644
--- a/webengine/views/webflow-vs-content-one.html
+++ b/webengine/views/webflow-vs-content-one.html
@@ -45,6 +45,128 @@
     .versus-faq > summary::marker { content: ""; }
   </style>
 
+  <script type="application/ld+json">
+{
+  "@context": "https://schema.org",
+  "@graph": [
+    {
+      "@type": "WebPage",
+      "@id": "https://www.content.one/webflow-vs-content-one.html#webpage",
+      "url": "https://www.content.one/webflow-vs-content-one.html",
+      "name": "Webflow vs Content.One, 2026 pricing, multi-site cost, governance",
+      "description": "Comparing Webflow and Content.One for a multi-site network? See 2026 Premium pricing, cost per published site, shared content models, and where each one fits.",
+      "inLanguage": "en-US",
+      "datePublished": "2026-08-30",
+      "dateModified": "2026-09-11",
+      "isPartOf": {
+        "@type": "WebSite",
+        "@id": "https://www.content.one/#website",
+        "url": "https://www.content.one/",
+        "name": "Content.One"
+      },
+      "publisher": {
+        "@type": "Organization",
+        "@id": "https://www.content.one/#organization",
+        "name": "Content.One",
+        "url": "https://www.content.one/",
+        "logo": {
+          "@type": "ImageObject",
+          "url": "https://hj5v68xn.media.zestyio.com/content-one-brand-2025.png"
+        }
+      },
+      "breadcrumb": {
+        "@id": "https://www.content.one/webflow-vs-content-one.html#breadcrumb"
+      }
+    },
+    {
+      "@type": "BreadcrumbList",
+      "@id": "https://www.content.one/webflow-vs-content-one.html#breadcrumb",
+      "itemListElement": [
+        {
+          "@type": "ListItem",
+          "position": 1,
+          "name": "Home",
+          "item": "https://www.content.one/"
+        },
+        {
+          "@type": "ListItem",
+          "position": 2,
+          "name": "Compare",
+          "item": "https://www.content.one/compare.html"
+        },
+        {
+          "@type": "ListItem",
+          "position": 3,
+          "name": "Webflow vs Content.One",
+          "item": "https://www.content.one/webflow-vs-content-one.html"
+        }
+      ]
+    },
+    {
+      "@type": "FAQPage",
+      "@id": "https://www.content.one/webflow-vs-content-one.html#faq",
+      "mainEntity": [
+        {
+          "@type": "Question",
+          "name": "How much does Webflow cost for 50 or 100 sites?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Each published site needs its own Site plan. At the Premium rate of $25 a month billed yearly, 50 sites is about $15,000 a year and 100 sites is about $30,000 a year in site plans alone, before Workspace seats, bandwidth add-ons, or per-locale localization."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Does Webflow support multisite?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Not as a self-serve product. Sites are independent, each with its own plan, CMS Collections, and settings. Multi-site arrangements are handled through the Team plan or Enterprise, both of which are quote-only."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Can I update content across every Webflow site at once?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Not from the CMS. Collections belong to a single site, so a network-wide change means editing each site or writing against the Data API. This is the main structural difference from federated multisite."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Does Webflow work with AI agents and MCP?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Yes, and it does it well. Webflow's MCP 2.0 launched in July 2026, is free on all plans, and applies existing roles and permissions to agent actions with full activity logging. Content.One also ships a native MCP server, so both platforms support agent-driven content work."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "What changed in Webflow's May 2026 pricing?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Webflow merged the CMS and Business Site plans into a single Premium plan at $25 a month billed yearly, raised CMS items to 20,000 and static pages to 300, and reduced base bandwidth on former Business sites from 100GB to 50GB. It also added AI credits to every Workspace plan."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "Why are Content.One reviews listed under Zesty.io?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Content.One was rebranded from Zesty.io, and the review profiles on G2 and Capterra have not fully migrated yet."
+          }
+        },
+        {
+          "@type": "Question",
+          "name": "What does moving from Webflow to Content.One involve?",
+          "acceptedAnswer": {
+            "@type": "Answer",
+            "text": "Content.One runs the migration alongside your live sites, and Engineer on Demand covers the implementation work directly rather than routing it through a certified partner. You can get a scoped estimate at migration.content.one."
+          }
+        }
+      ]
+    }
+  ]
+}
+  </script>
   {{include /-/isolated-page-marketing-snippet.html}}
 </head>
 <body class="font-sans">
@@ -73,6 +195,7 @@
     <div class="max-w-5xl mx-auto px-4 sm:px-6 lg:px-8 text-center">
       <span class="inline-flex items-center px-3 py-1 rounded-full bg-white text-royal text-xs font-semibold uppercase tracking-wider mb-5">Side-by-side comparison</span>
       <h1 class="font-display text-4xl md:text-5xl lg:text-6xl font-bold mb-6">Webflow vs Content.One</h1>
+      <p class="text-sm text-white/60 mb-6"><time datetime="2026-09-11">Last updated: September 2026</time></p>
       <p class="text-lg md:text-xl text-white/80 max-w-3xl mx-auto mb-8">Webflow is a visual design platform for building and running individual websites. Content.One is built for franchise, multi-location, and federated networks. An 80-location organization on Webflow needs 80 Premium site plans, which is more than $20,000 a year before anyone builds the sites, and Webflow's own route for that work is a certified partner agency. Content.One is AI-native and prices the network as one platform, with migration and site development handled by the engineers who run it.</p>
       <div class="flex flex-wrap gap-3 justify-center">
         <a href="https://launch.content.one" target="_blank" rel="noopener" class="inline-flex items-center rounded-lg bg-white text-royal hover:bg-gray-100 font-semibold px-6 py-3 transition shadow">Start a build</a>
@@ -210,7 +333,7 @@ <h3 class="font-display text-lg font-semibold m-0">Both platforms are serious ab
     <div class="max-w-7xl mx-auto px-4 sm:px-6 lg:px-8">
       <div class="text-center max-w-3xl mx-auto mb-10">
         <h2 class="font-display text-3xl md:text-4xl font-bold mb-3">The comparison</h2>
-        <p class="text-gray-600">Capability by capability. Why each one matters in the right-hand column. Accurate as of August 2026.</p>
+        <p class="text-gray-600">Capability by capability. Why each one matters in the right-hand column. Accurate as of September 2026.</p>
       </div>
       <div class="overflow-x-auto rounded-2xl border border-gray-200 bg-white shadow-sm">
         <table class="w-full text-sm border-collapse min-w-[760px]">
@@ -258,6 +381,7 @@ <h2 class="font-display text-3xl md:text-4xl font-bold mb-3">The comparison</h2>
           </tbody>
         </table>
       </div>
+        <p class="text-xs text-gray-500 mt-3 italic">Accurate as of September 2026.</p>
     </div>
   </section>