Holding all else equal: how comprehensive schema drove +45% MoM organic clicks for a mid-market cybersecurity SaaS.

The client was a mid-market cybersecurity SaaS in the XDR space: a competitive category, enterprise-adjacent buyers, commercial-intent queries dominated by rich SERPs. Organic traffic had been growing slowly, but the site was systematically under-indexed relative to its content surface.

Two things were underneath it. The first: fragmentation. The foundational content (what the market calls a "learn" or "resources" hub) lived under 26 disconnected URL folders, many overlapping in topic, none acting as pillars. Google saw a sprawl, not a structure.

The second: illegibility to the engine. Across BOFU and blog surfaces, structured data was inconsistent or absent. Pages eligible for rich listings (product pages, FAQ blocks, review modules) were rendering as plain blue links. On commercial queries where competitors had stars, prices, and expandable FAQs, this client didn't. Impressions were stacking up; clicks weren't.

If the system is underperforming, the cleanest diagnostic is to change one thing and watch what moves. So I ran it that way: schema only, comprehensively. No new content. No internal-linking revamp. No technical cleanup wave.

Eight schema types, rolled out across the BOFU and blog page sets: Product, SoftwareApplication, FAQ, Review, Organization, Breadcrumb, Article, HowTo. The decision wasn't "which plugin." It was treating structured data as a systemic surface and implementing it everywhere it applied, not page-by-page when someone remembered.

In the same window I restructured the fragmented resources hub. 26 URL folders consolidated into 8 pillars under a single "Security Foundations" parent: Cybersecurity, Managed Service Providers, Attack Techniques, Endpoint Security, Incident Response, AI and Machine Learning, Threat Intelligence, and Managed Detection and Response. Each pillar maps directly to the client's product surface, XDR + MDR + MSP, not generic SEO topics.

The framing I used with the CMO was deliberately narrow: we are going to make your site more legible to the engine, and we expect the lift to show up first on commercial queries, where enhanced SERPs have the most leverage. Setting that expectation mattered. Senior stakeholders have seen every "aggressive content plan" and rightly discount them. A single-variable test that predicts a specific shape of outcome is a different kind of promise.

The last piece was measurement discipline. I instrumented the MoM window specifically so the read would be honest: Jan 2026 as the clean baseline, Feb 2026 as the first full month post-rollout. I also pre-registered the BOFU regex I'd use for the commercial-query cut (platform | software | tool | provider) so the result couldn't drift toward cherry-picked language after the fact.