"I ran the nine-query test from your last post. We appeared twice out of nine. I know that's bad. What I don't know is whether the problem is our schema, our G2 profile, our product description, or something else entirely. I don't want to guess and spend three months fixing the wrong thing."

That message came in the day after the post on the five reasons your SaaS is invisible to AI chatbots went up. It captures the exact question this post is written to answer. Knowing you have a gap is step one. Knowing which gap to close first, with actual data behind the ranking, is what makes the difference between fast progress and wasted quarters.

This is a complete breakdown of what the $197 LLMRadar Audit measures: the engines it runs, the queries it uses, the signals it checks, and the sections of the PDF report you receive. Nothing is held back. If you want to run this yourself manually, you can. If you want it done in 24 hours with the analysis already structured, the order link is at the bottom.

Want the data without doing it yourself?

The LLMRadar Audit runs 40 buyer-intent queries across ChatGPT, Perplexity, and Claude. You get your share of voice score, framing analysis, and prioritized fix list as a PDF within 24 hours. No calls required.

Get the $197 LLMRadar Audit

Full details at operatoriq.io/llmradar-audit

Which engines the audit covers, and why those three

The LLMRadar Audit runs queries across three AI engines: ChatGPT (GPT-4o), Perplexity AI, and Claude (Anthropic). These three account for the majority of AI-assisted B2B vendor research as of mid-2026.

Engine Retrieval type Why it matters for B2B SaaS
ChatGPT (GPT-4o) Hybrid: training data + live browsing on some queries Highest install base. Many enterprise buyers use it as the first research step. Training data coverage is the primary signal here.
Perplexity AI Live retrieval first, then synthesis The most citation-dense engine for vendor comparisons. Uses real-time web data, so schema and entity signals matter more here than training data.
Claude (Anthropic) Training data primary; web retrieval on Claude.ai Pro Growing fast among technical founders and product teams. Framing and vocabulary alignment have outsized impact on citation rate.

Each engine surfaces your product through different mechanisms. A brand that appears in ChatGPT but not Perplexity has a different gap profile than one that appears in Perplexity but not Claude. The audit captures your performance on each engine separately so you can see where your effort is best spent.

The 40 queries: how they are structured

The audit does not run generic searches. Every query is written to match the language real buyers use at different stages of vendor evaluation.

40
buyer-intent queries run across all three engines. Queries are distributed across four types: category-level searches (what tools exist), comparison requests (compare X vs. alternatives), use-case-specific prompts (I need a tool that does Y), and ICP-targeted prompts (I am a [role] at a [company type], what do you recommend).

Here is the query distribution by type:

The queries are customized to your actual product and category before the audit runs. You provide your product URL and a one-paragraph description of what it does. The audit team maps your category vocabulary, identifies the top three competitor names, and writes the 40 queries from that foundation.

The five signals the audit checks

After the queries run, the audit analyzes five structural signals that determine citation rate. These are the same five signals that separate the 27% of B2B SaaS brands that get cited from the 73% that do not.

Signal 1
Schema markup completeness
The audit checks for SoftwareApplication JSON-LD on your product page. It verifies the presence and accuracy of: name, applicationCategory, description, featureList, offers, url, and sameAs. It also checks for Organization schema and FAQ schema. Missing or incomplete fields are listed with the specific text needed to complete them.
Signal 2
Entity signal density
The audit checks your presence on G2, Capterra, Product Hunt, Trustpilot, and Crunchbase. It counts the number of reviews, the freshness of your profile description, and whether your description on each platform uses the same vocabulary as your product page. Entity signals on two or more high-authority aggregators are required for reliable Perplexity citations. The audit scores each platform and identifies which ones are absent or outdated.
Signal 3
Vocabulary alignment
The audit compares the language used in the 40 buyer-intent queries against the language used on your product page, in your schema, and in your aggregator profiles. Vocabulary gaps are the most common cause of use-case query failure. A product that solves the problem but describes it in different words than buyers use will consistently fail the use-case and ICP query types even with strong schema and entity signals.
Signal 4
Community mention density
The audit checks Reddit, Hacker News, and relevant community forums for mentions of your product in context-relevant threads. Community mention density is a proxy for training data coverage for newer products. A product mentioned in 10 or more relevant threads has meaningfully higher citation rates in ChatGPT and Claude than an identical product with fewer than 3 mentions. The audit counts current mentions and identifies the top threads where your competitors appear but you do not.
Signal 5
Category declaration clarity
The audit reads the first 200 words of your product page and checks whether your category is explicitly stated. "We help businesses grow" fails this test. "Automated post-payment file delivery for SaaS products built on Stripe" passes it. Explicit category declaration in the opening paragraph is present in 88% of consistently cited brands and only 22% of invisible brands. The audit rates yours as clear, ambiguous, or absent.

What the PDF report contains, section by section

The deliverable is a PDF report, typically 12 to 18 pages, sent to your email within 24 hours of order. Here is what is in each section.

Section 1: Share of voice scorecard. A table showing how many of the 40 queries your product appeared in, broken down by engine and query type. Your overall share of voice score (appearances divided by total queries) is compared against the category average and the top competitor's score. This gives you the headline number: you appear in X of 40 queries; the category leader appears in Y.

Section 2: Raw AI response excerpts. The actual text each engine produced for a representative sample of queries. You see exactly how ChatGPT, Perplexity, and Claude describe your product category, which competitors they name, and what language they use. When your product does appear, you see the exact framing. When it does not appear, you see which competitors were named instead.

Section 3: Framing analysis. When your product appears in AI responses, how is it described? The framing analysis compares the AI-generated description to your intended positioning. Common framing gaps: AI engines describe your product as a tool for a different ICP than you target, assign you to a broader or narrower category than you occupy, or emphasize features you consider secondary while ignoring your primary value. Framing gaps require vocabulary fixes, not engineering work.

Section 4: Signal gap analysis. A scoring table for each of the five signals above, rated as Strong, Adequate, Weak, or Absent. Each weak or absent signal includes a specific action: the exact schema field to add, the aggregator profile to update, the vocabulary phrase to add to your product page, or the community thread to engage with.

Section 5: Prioritized fix list. The actions ranked by expected impact on citation rate. Not every gap is equally urgent. A brand with absent schema and strong entity signals should fix schema first. A brand with strong schema but thin community mentions has a different priority order. The fix list is sequenced based on your actual gap profile, not a generic template.

24h
turnaround from order to PDF delivery. The audit team runs all 40 queries fresh at order time, so the results reflect current AI model behavior rather than cached snapshots. You receive the PDF by email. No login required, no dashboard to check.

What the audit does not cover

Three things are explicitly outside the scope of the $197 audit:

Implementation. The audit tells you exactly what to fix and in what order. It does not implement the fixes for you. Schema edits, aggregator profile updates, and vocabulary revisions are things your team can execute directly from the fix list. Most founders complete the top three fixes within a week of receiving the report.

Ongoing monitoring. AI citation rates change as models update and competitors make changes. The audit is a point-in-time measurement. It reflects where you stand on the day the queries ran. Re-auditing in 60 to 90 days after implementing fixes is the standard practice to measure lift.

Paid search or traditional SEO. The LLMRadar Audit is scoped entirely to AI citation signals. It does not assess your Google rankings, backlink profile, or paid acquisition performance. Those require a separate audit methodology.

How to read your share of voice score

The share of voice score ranges from 0 to 100, representing the percentage of 40 queries in which your product appeared in the AI response. Here is how to interpret it:

Score range What it means Typical gap profile
0 to 5 Near-total invisibility Missing schema, absent aggregator profiles, low community mention density. All five signals need work.
6 to 20 Sporadic citation Appears in broad category queries but vanishes in comparison and use-case queries. Schema exists but vocabulary alignment is weak.
21 to 45 Partial presence Named in one or two engines consistently, absent in others. Entity signal density is typically the differentiating gap here.
46 to 70 Competitive presence Appears across most query types. Framing gaps and ICP mismatch are the remaining issues. Fine-tuning phase.
71 to 100 Category authority Consistent citation across all engines and query types. Maintenance and competitive monitoring are the primary needs.

Most B2B SaaS products that have not done deliberate AI visibility work score in the 0 to 10 range. Moving from that range to 21 or above typically requires fixing schema, updating two aggregator profiles, and making three to five vocabulary adjustments to the product page. That is work that can be completed in a week by a non-technical founder.

The difference between doing this yourself and ordering the audit

You can replicate most of what the LLMRadar Audit covers manually. The process looks like this:

  1. Write 40 queries across the four types described above, customized to your product and category.
  2. Run them across ChatGPT, Perplexity, and Claude, one at a time, recording responses in a spreadsheet.
  3. Score your appearance rate by engine and query type.
  4. Check each of the five signals manually: validate your schema with Google's Rich Results Test, check your G2 and Capterra profiles, read your product page first 200 words for category declaration, search Reddit for your product name, and compare your vocabulary to your top competitor's product page.
  5. Build a prioritized fix list based on the gap scores.

That process takes four to six hours if you are organized and have not done it before. The audit takes 24 hours from your side: 10 minutes to submit the order form, then waiting for the PDF. The difference is structured analysis versus raw data. The audit produces a scored gap profile with context on what each gap means for your specific category and competitive set. The manual process produces a list of things you noticed without a benchmark to interpret them against.

Either approach works. The manual path costs more time. The audit path costs $197 and delivers a structured report you can act on immediately.

Order the LLMRadar Audit

40 buyer-intent queries across ChatGPT, Perplexity, and Claude. Share of voice score, framing analysis, five-signal gap report, and prioritized fix list. PDF delivered to your email within 24 hours. Send questions to theresanagentforthat@gmail.com before ordering.

Get the $197 LLMRadar Audit

Full details at operatoriq.io/llmradar-audit