I Audited an $18M MSP
Security Platform.
Zero Schema Markup.

This company has what most B2B SaaS startups spend years building: two founders who previously sold a company for $120M, a fresh $18M Series A, SOC 2 Type II certification, 100+ reviews on G2 at 4.5 stars, and 418 blog posts covering their entire market. The product is real. The credentials are real. The business is growing.

When I looked under the hood of their website, I found a WordPress/Elementor site with strong content, an active publishing cadence, and -- surprisingly -- an llms.txt file already in place. That last detail tells me someone on the team is thinking about AI discoverability. But the foundation underneath has a critical gap that is quietly undermining all of that effort.

The Scores

Content is the strongest category at 78/100. Schema is the weakest at 8/100. That gap is the story of this audit.

Finding #1: Zero JSON-LD Schema on an $18M SaaS

No Organization schema. No SoftwareApplication schema. No Person schema for the founders. No FAQPage schema despite having FAQ content on product pages. No BreadcrumbList. Nothing.

This means when AI systems try to understand what this company sells, they are parsing marketing copy and blog posts rather than reading structured, machine-readable data. The company has a clear entity statement on their site -- "a centralized SaaS security platform built for MSPs" -- but it lives in a paragraph, not in schema. AI can find it, but it has to work harder, and it trusts it less.

For a company that just raised $18M to scale go-to-market, this is the equivalent of building a warehouse but never putting up a sign on the door. The product exists. The credentials exist. But the structured metadata that helps search engines and AI confidently identify and recommend the product does not exist.

Finding #2: The llms.txt Paradox

Here is where it gets interesting. This company has an llms.txt file -- an emerging standard that helps AI systems understand your site. It lists their products, features, content resources, and even provides 100+ markdown exports for technical reference. That is more advanced AI infrastructure than 99% of websites.

But they have zero schema markup. It is like installing solar panels on a house with no electrical wiring. The energy source exists, but there is no way to distribute it through the building. The llms.txt file tells AI "here is what we do." Schema tells every search engine and AI model "here is what we do, in a format you already understand and trust." You need both.

Finding #3: 418 Blog Posts, Zero FAQ Schema

The content engine is impressive. 418 blog posts, actively publishing, covering Microsoft 365 security, MSP management, compliance, and product updates. The most recent post was from the last week. Categories are well-organized. The titles are keyword-relevant.

But the product pages have FAQ sections with genuine, useful questions -- and none of them have FAQPage schema. Those FAQs are invisible to Google's rich results. Every question that could appear as an expandable rich snippet in search results is hidden behind unstructured HTML. For an MSP buyer searching "how does M365 security automation work," this company's FAQ content exists but does not surface in the format Google uses for featured answers.

Finding #4: Three Social Platforms, Zero Video

LinkedIn (with thousands of followers), Facebook, and X/Twitter. That is the entire social footprint. No YouTube channel. No Instagram. No TikTok. No video content at all.

For a B2B SaaS selling to MSPs, LinkedIn is the right primary channel. But video is the fastest-growing discovery surface for B2B buyers. Product demos, security walkthroughs, customer testimonials on video, and short-form clips from webinars are all high-value content that MSPs consume during research. Without video, the company is invisible on the platform where the fastest-growing share of B2B discovery happens.

Finding #5: Missing from the Roundups AI Cites

According to AirOps' analysis of 21,311 brand mentions across GPT-5, Claude, and Perplexity (October 2025), 85% of brand mentions in AI search come from third-party sources -- not the company's own website. The company is not listed in the major "best SaaS management platforms" roundups from the publications AI frequently cites. Their direct competitor has a published comparison page targeting them by name. When an MSP asks AI "what is the best M365 security tool," the roundups and comparison articles that AI pulls from either do not mention this company or frame the competitor as the alternative.

What Is Actually Working

• Content volume and quality -- 418 posts with active publishing is a genuine competitive moat
• llms.txt file with comprehensive product documentation -- more advanced than most enterprise SaaS sites
• Clear entity statements and value proposition on the homepage and company page
• SOC 2 Type II certification and GDPR compliance -- real trust signals
• 100+ G2 reviews at 4.5 stars -- strong social proof on a platform AI trusts
• Recent press coverage from Series A funding round
• Active LinkedIn presence with thousands of engaged followers

The Bottom Line

This is a company with excellent content, real credentials, and growing revenue -- but the infrastructure that connects those assets to search engines and AI is missing. Adding schema markup, completing the social footprint, and building earned visibility through roundup placement would turn an already-strong content engine into a compounding growth machine. The hard part -- building the product and the content -- is already done. The remaining work is structural, not creative.

Does This Look Like Your SaaS?

Strong product. Growing customer base. Active blog. But when you search for your category on ChatGPT or Perplexity, your competitors show up and you do not. The problem is not awareness. The problem is the layer between your content and the systems that decide who to recommend.

FAQ