I Audited an $18M SaaS Company.
462 Blog Posts,
Zero Article Schema.

This company has real revenue. $18 million ARR. Five distinct product tiers. A content team that has published 462 blog posts. G2 reviews, Capterra listings, a 4.5-star rating on a major channel partner platform. Their founders are former executives at one of the biggest tech companies in the world.

When I audited their website, I found a company that has done almost everything right from a product and content perspective but has left enormous amounts of structured visibility on the table. Their blog is a content engine with no schema. Their product pages describe five software tiers with no SoftwareApplication markup. Their Organization schema description literally just repeats the company name.

If you run a SaaS company -- especially one in the B2B or managed services space -- these findings probably apply to your site too.

The Scores

An 80 in Content with a 15 in Schema tells you everything. This company has invested heavily in creating content. They just haven't told machines what any of it is.

Finding #1: Organization Schema That Says Nothing

The site has Organization schema. That's good -- most SaaS companies don't even get that far. But the description field just repeats the company name. Literally. The description property that is supposed to tell Google and AI systems what this company does, who it serves, and why it matters contains nothing but the brand name repeated.

When ChatGPT or Perplexity pulls Organization schema to understand what a company does, they get: the company name. Not "cloud-based IT management platform for managed service providers." Not "endpoint monitoring and SaaS license management for MSPs." Just the name.

This is like handing someone your business card with your name on both sides and nothing else. The schema exists. It just communicates nothing.

Finding #2: Five Product Tiers, No SoftwareApplication Schema

This company sells five distinct product tiers. Each one has its own pricing page, feature list, and target audience. Together they cover endpoint management, SaaS optimization, compliance automation, and more. It's a genuinely comprehensive platform.

None of them have SoftwareApplication schema. Which means Google can't show:

When someone asks ChatGPT "what's the best endpoint management tool for MSPs," the AI pulls from structured product data, review platforms, and comparison sites. Without SoftwareApplication schema, this $18M product is structurally invisible to that recommendation engine.

Finding #3: 462 Blog Posts With Zero Article Schema

This is the finding that stopped me. Four hundred and sixty-two blog posts. That's years of consistent content production. Topics covering industry trends, product updates, best practices, compliance guides, and thought leadership. A genuine content library.

Not a single post has Article schema. No headline markup. No author attribution. No datePublished. No description. Google sees 462 pages of unstructured HTML. AI systems see 462 pages they can't confidently classify, attribute, or cite.

Article schema is not optional for content-heavy sites. It's what tells Google this is a published article by a specific author on a specific date about a specific topic. Without it, your content competes without its credentials attached. With 462 posts, implementing Article schema across the blog would immediately create 462 new structured data signals for Google and AI systems to process.

Finding #4: Founders With Big Credentials, No Person Schema

The founding team includes former executives from one of the most recognizable tech companies on the planet. That's exactly the kind of credential that builds trust with enterprise buyers and, increasingly, with AI systems evaluating E-E-A-T signals.

But there's no Person schema for any of them. No structured data connecting their names, roles, credentials, or expertise to the company. When AI systems try to evaluate the authority behind this product, they can't find machine-readable evidence that the leadership team has relevant expertise.

For a SaaS company selling to IT professionals, having founders with deep enterprise tech backgrounds is a trust accelerator. It just needs to be structured so machines can read it, not just humans.

Finding #5: AI Crawlers Slowed to a Crawl

The robots.txt file includes a Crawl-delay of 10 seconds. That means every AI crawler -- GPTBot, ClaudeBot, Google-Extended -- has to wait 10 seconds between each page request. For a site with 462 blog posts plus product pages, pricing pages, and resource pages, that delay turns what should be a fast crawl into a multi-hour process.

There are also no explicit directives for AI crawlers. No allow rules, no specific instructions. The site isn't blocking AI crawlers outright, which is good. But it's not welcoming them either. And the crawl delay makes the entire site slower to index and process.

For a SaaS company that wants to be recommended when buyers ask AI for tool suggestions, making your site fast and easy for AI crawlers to process is a competitive advantage. Right now, competitors without crawl delays are getting indexed faster.

Finding #6: Zero Reddit Presence Where Buyers Discover Tools

The managed services industry has a highly active subreddit where MSP owners discover, evaluate, and recommend tools to each other. Thousands of threads about stack recommendations, vendor comparisons, and tool reviews. It's one of the most influential communities in the B2B IT channel.

This company has no presence there. No official account participating in discussions. No community engagement. No mentions in recommendation threads.

This matters for AI discoverability because AI systems increasingly pull from Reddit as a trust signal. When someone asks ChatGPT for MSP tool recommendations, Reddit threads where real users discuss and recommend tools are part of the citation pool. Being absent from that conversation means being absent from those recommendations.

What's Actually Working

Does This Look Like Your SaaS?

If you run a SaaS company -- especially B2B -- and you recognize these patterns, you're in good company. Most SaaS websites were built by product teams and marketers who focused on conversion (rightfully so) but didn't think about schema markup or AI discoverability. The content exists. The product exists. The reviews exist. What's missing is the structured layer that makes it all machine-readable.

The gap between an 80 in Content and a 15 in Schema is not a content problem. It's an infrastructure problem. And infrastructure problems are fixable -- usually faster than creating 462 more blog posts.

Frequently Asked Questions