Acme Cloud is a fictional company. Every answer on this page is written by us to show the report's panels; no engine produced them. The engine names and model labels are illustrative too: they mark where a real engine's answer would sit, not anything an engine said. Your report runs on your live data across all 23 questions on ChatGPT, Claude, Gemini and Perplexity, every answer stored, every number opening its receipt. Run it for your brand →
Sign in to run your ownSAYLENT · REPORT · 18 Jun 2026 · SNAPSHOT (single run)
The quotes in this report are verbatim outputs the named AI engines generated on the dates shown, in response to Saylent's standardized prompts. They document what each AI said. They are not statements of fact by Saylent, and AI systems can state inaccurate things about real companies.
Measured across ChatGPT, Claude, Gemini, Perplexity on 18 Jun 2026: 11 asked · 11 answered · 48 scored.How we measure →
How engines could describe you: flat, public pricing · unusually fast human support · p95 latency within 4% of the market leader · 18-month clean incident record
You lose every head-to-head answer: 0 of 2 recommend Acme Cloud. Perplexity recommends Acme Cloud in 2 of 12 buyer questions; Gemini never does. Nimbus owns the share of voice: 31 mentions to your 6. One gate is costing you: live fetch as PerplexityBot, http 403 while robots.txt allows it. a cdn/waf "ai bots" toggle is overriding your robots.txt. perplexity cannot cite what it cannot read.
Recommended in 2–5 of 48 scored answers. We ask every scored question at least twice (and a third time whenever the answers disagree); the range is how much the answers moved between draws.
Your gap is buyers describe their problem. The engines don't surface you at all there. Click a stage to read those answers.
What we found · your 3 moves
Where each engine gets its answers
Each engine builds its answers from a different corner of the web. The counts are citations on this run. The sources you have to win are the ones the engines already trust.
builds answers from best-of listicles.
builds answers from best-of listicles.
builds answers from best-of listicles.
builds answers from head-to-head comparisons.
36% of the pages behind these answers are head-to-head comparisons. You appear on 1 of the 4 we could verify.
The divergence that matters: ChatGPT leans on best-of listicles: where you're least present.
01 · Battlefield map: the pages the answers are built from
11 pages cited · 4 comparisons · 3 listicles · 1 brand site · 1 forum thread · 1 news article · 1 review platform. You appear on 3 of the 11. 1 of them sits on a rival's own domain.
Nimbus is on 10 of the 11 pages behind these answers we could verify; you're on 3.
4 pages 2+ engines trust: you're absent from all 4. Two or more of the 4 engines cite each one. A listing here moves several engines at once.
| Cited× | Source | You | Competitors on page |
|---|---|---|---|
| 13 | listiclechatgpt×6gemini×4claude×3cloudreview.example | ABSENT | Nimbus, StratoCDN, Fleetly |
| 7 | forumperplexity×5claude×2devforum.example | PRESENT | Nimbus, Fleetly |
| 5 | review_platformgemini×3chatgpt×2saastools.example | ABSENT | Nimbus, StratoCDN, Fleetly |
| 5 | listiclechatgpt×3gemini×2stackship.example | ABSENT | Nimbus, StratoCDN |
| 4 | comparisonchatgpt×2perplexity×2uptimewatch.example | ABSENT | StratoCDN, Nimbus, Fleetly |
| 3 | comparisonperplexity×3benchmarks.example | PRESENT | Nimbus, StratoCDN |
| 3 | comparisonchatgpt×2gemini×1nimbus.example | Rival's own site (Nimbus) | Nimbus |
| 2 | comparisongemini×2cdncompare.example | ABSENT | Nimbus, StratoCDN |
| 2 | listicleperplexity×2reviewsignal.example | ABSENT | Nimbus, Fleetly |
| 1 | brand_ownedclaude×1acmecloud.example | PRESENT | — |
| 1 | newsclaude×1apidigest.example | ABSENT | Nimbus |
The page beating you, per question
4 of the 5 questions have a single page that beats you: the one page the engines read instead, where a listing moves the answer. The other 1 either name you already or spread across too many sources to point at one.
| Q | Question | The page beating you | Engines | Rivals on page |
|---|---|---|---|---|
| q05 | Most reliable edge CDN platform for a high-traffic SaaS? | cloudreview.example | 3 | Nimbus, StratoCDN, Fleetly |
| q09 | Acme Cloud vs Nimbus: which is better for a high-traffic SaaS? | cloudreview.example | 3 | Nimbus, StratoCDN, Fleetly |
| q14 | How do I cut origin egress costs at peak traffic? Which providers help? | stackship.example | 2 | Nimbus, StratoCDN |
| q18 | What is Acme Cloud? Is it any good? | acmecloud.example | 1 |
Entity clarity
Gemini confused you with a different ‘Acme Cloud’ in 1 answer (an entity-clarity problem).
02 · Question verdicts: click any tag to read the raw answer
| Question ID | Question | Verdict by engine |
|---|---|---|
| q01 | What is the best edge CDN platform for a high-traffic SaaS? “For a high-traffic SaaS, the strongest options today are: 1. Nimbus — the most complete platform…” | |
| q05 | Most reliable edge CDN platform for a high-traffic SaaS? “Reliability leaders: StratoCDN (99.999% SLA, strongest track record) and Nimbus…” | Claude · no answerGemini · no answer |
| q09 | Acme Cloud vs Nimbus: which is better for a high-traffic SaaS? “Acme Cloud counters with simpler, predictable pricing and strong support.” | Claude · no answerPerplexity · no answer |
| q14 | How do I cut origin egress costs at peak traffic? Which providers help? “Nimbus and Fleetly both offer origin shield included; StratoCDN prices it as an add-on…” | ChatGPT · no answerGemini · no answerPerplexity · no answer |
| q18 | What is Acme Cloud? Is it any good? “Acme Cloud is an edge CDN platform aimed at SaaS teams. It's known for transparent flat pricing…” | Claude · no answerPerplexity · no answer |
absent: not in the answer at all · listed: named in a list, not recommended · compared: named in a comparison, not recommended · recommended: the engine tells the buyer to pick you
1 answer is about a different company that shares your name. Everything mined from it carries a badge below, and Entity clarity above explains it.
How they frame you when you ARE mentioned
Tone in the 6 answers that name you, across every question type: positive ×4 · neutral ×2
Where you land in the answer: named first ×1 · named early ×3 · buried in the list ×2
Mentioned but framed weakly: 2 answers (a mention that doesn't sell you is rented ground).
What the engines say about Acme Cloud, grouped by how it lands with a buyer. We show what was said; we don't guess what's true. A false claim is a fix-worthy finding.
What they praise
- transparent pricingClaude
- unusually fast supportClaude
- predictable pricingPerplexity
- cache-hit latency within 4% of NimbusPerplexity
- roughly 60% of the cost of NimbusPerplexity
- 18-month clean incident recordPerplexity
- simpler, predictable pricingChatGPT
- strong supportChatGPT
- +4 more in the stored answers above.
What buyers hear as doubts
2 of 4 engines tell buyers: “smaller network than the market leaders”
- smaller network than the market leadersClaudeChatGPT
- shorter tracker history than incumbentsPerplexity
Facts they repeat
- a solid mid-market optionChatGPT
What the engines say you cost
The engines quote 4 different fee figures about you.
The figures: 60% · $0.04 · $0.06 · $49
Check these against your real pricing. Engines repeating wrong prices is a fix-worthy finding.
- ClaudeGemini
- ChatGPT
- Perplexity
- Perplexity
- ChatGPT
03 · Who gets mentioned most
Counted over every answer this run collected, scored or not: an answer counts when it lists, compares or recommends the name. The summary's “of 48” counts scored answers only.
| Brand or competitor | Share of mentions | Mentions |
|---|---|---|
| Nimbus | 31 | |
| StratoCDN | 22 | |
| Fleetly | 14 | |
| Acme Cloud | 6 | |
| EdgeBox | 4 |
Where rivals beat you
In the 5 answers that skip you, these rivals keep appearing, and here's the engines' stated reason why.
- “developer-first, programmable edge logic” ×1
- “best programmable edge” ×1
- “the most complete platform” ×1
- “most popular; excellent developer experience” ×1
- “enterprise-grade, largest points-of-presence footprint” ×1
- “the enterprise pick” ×1
- “budget option” ×1
Who the engines send elsewhere, and why
Engines make you the default for: SaaS teams that want predictable pricing, teams optimizing for cost clarity, teams optimizing for predictable cost and fast support, teams prioritizing predictable costs.
When a buyer fits a specific profile, the engines steer them to a rival. Here's the segment, the rival, and the engines' stated reason.
- most SaaS teams wanting one all-in-one default: “the most complete platform”
- teams that need raw global scale: “broadest feature set and ecosystem”
- teams wanting the safest popular default: “most popular, excellent developer experience”
- teams that value live status transparency: “excellent status transparency”
- most high-traffic SaaS wanting the safer, more complete platform: “bigger network and an integrated security suite”
- teams prioritizing network size and features: “wins on network size and features”
- +1 more segment: see the stored answers.
- compliance-heavy, SLA-driven enterprises: “deeper audit tooling and the largest PoP footprint”
- enterprises with strict compliance: “strongest compliance story”
- mission-critical SaaS that cannot take an outage: “99.999% SLA and the strongest track record”
- buyers who want the longest proven uptime history: “top of the independent uptime trackers”
- teams writing custom edge logic: “developer-first, programmable edge”
- teams already running programmable edge logic: “origin shield included”
+1 more rival was steered a single segment each: see the stored answers.
04 · Can the AI crawlers read your site?
Not crawled = not cited.
We fetched acmecloud.example as PerplexityBot on 18 Jun 2026: HTTP 403 while robots.txt allows it. A CDN/WAF "AI bots" toggle is overriding your robots.txt. Perplexity cannot cite what it cannot read.
2 fail · 2 warn · 1 info · 3 pass of 8 checks
| Status | Check | Detail |
|---|---|---|
| fail | live fetch as PerplexityBot | HTTP 403 while robots.txt allows it. A CDN/WAF "AI bots" toggle is overriding your robots.txt. Perplexity cannot cite what it cannot read. |
| fail | content coverage | No page on acmecloud.example answers 3 of your 17 buyer questions. Top gaps: [q05] Most reliable edge CDN platform? · [q14] How do I cut origin egress costs at peak? · [q01] best edge CDN for high-traffic SaaS |
| warn | JSON-LD FAQPage | No FAQPage schema found on crawled pages. |
| warn | homepage entity clarity | The homepage's first 800 chars never say "CDN": engines must guess what Acme Cloud is. |
| info | live-fetch caveat | IP-verifying CDNs may treat our test differently than real bots; your server logs are ground truth. |
3 checks passed
| Status | Check | Detail |
|---|---|---|
| pass | robots: GPTBot | allowed |
| pass | robots: OAI-SearchBot | allowed |
| pass | JSON-LD Organization | present |
Your site vs the buyer questions
The pages we crawled on your site, and the buyer questions the engines cited no page of yours for. 1 of 5 questions have one of your pages in their sources.
Pages we crawled (6)
Questions with no page of yours (4)
05 · Fix plan: ranked by evidence weight, drafted for you
Evidence weight is the number on each card. Each fix family starts from a fixed base (crawler access 9.5, a coverage hub 9.0, a source pitch 8.5, wrong claims and entity confusion 7.0, missing schema 5.5, stale titles 4.0). The two source families are re-scored from where this run's citations actually come from, and a pitch gains 0.1 for every citation the target page already has, up to half a point. Higher means more of this run's evidence points at it.
01Unblock the AI crawlers your buyers' engines depend on
Honest time-to-impact: days–2 weeks (bots recrawl quickly once allowed)
- live fetch as PerplexityBot: HTTP 403 while robots.txt allows it. A CDN/WAF "AI bots" toggle is overriding your robots.txt. Perplexity cannot cite what it cannot read.
- Perplexity is your STRONGEST engine (recommended 2/12), and it's the one being blocked
Copy-ready draft
robots.txt: AI crawler block (paste, then check the CDN toggle)
User-agent: OAI-SearchBot Allow: /
User-agent: ChatGPT-User Allow: /
User-agent: Claude-SearchBot Allow: /
User-agent: Claude-User Allow: /
User-agent: PerplexityBot Allow: /
User-agent: Perplexity-User Allow: /
Your choice: training crawlers (blocking is legitimate):
User-agent: GPTBot
Disallow: /
User-agent: ClaudeBot
Disallow: /
Verify the real gate (robots.txt is only a request):
- CDN dashboard → Security → Bot management → disable the "Block AI bots" preset (or allowlist PerplexityBot).
- Re-test: curl -A "PerplexityBot" https://acmecloud.example/ → expect 200.
- Watch server logs for PerplexityBot hits over the next 48h.
02Get onto the 4 listicles the engines trust: a drafted pitch for each
evidence weight 9.3Get added to "Best Edge CDNs compared (2026)" (cloudreview.example): the engines cite it and you're not on it
Honest time-to-impact: 2–4 weeks (ChatGPT) → 4–8 weeks (Gemini)
- Cited chatgpt×6, gemini×4, claude×3 for q01, q05, q09
- Competitors on the page: Nimbus, StratoCDN, Fleetly
- URL: cloudreview.example
- Submit via: cloudreview.example
- The page winning this question runs ~2,400 words / 12 sections. Match its depth.
- 91% of the pages the engines cited are third-party. 9% are acmecloud.example
Copy-ready draft
Subject: A data point for your Edge CDN comparison
Hi {author name},
Your "Best Edge CDNs compared" guide is one of the most-cited pages when AI assistants answer CDN questions. We measured it used 13 times across ChatGPT, Gemini and Claude answers.
One gap you might find worth closing: Acme Cloud. The independent 2026 latency benchmark measured our p95 cache-hit latency within 4% of Nimbus at ~60% of the cost, and we publish flat, public pricing: a genuinely different trade-off from the three platforms you cover.
Happy to send benchmark data, a test account, or answer anything directly. No expectations. The guide is excellent either way.
Disclosure: I work at Acme Cloud.
{maintainer name}, Acme Cloud
Get added to "The SaaS CDN buyer's guide" (stackship.example): the engines cite it and you're not on it
Honest time-to-impact: 2–4 weeks (ChatGPT) → 4–8 weeks (Gemini)
- Cited chatgpt×3, gemini×2 for q01, q14
- Competitors on the page: Nimbus, StratoCDN
- URL: stackship.example
- Submit via: email editors@stackship.example
- The page winning this question runs ~1,800 words / 9 sections. Match its depth.
- 91% of the pages the engines cited are third-party. 9% are acmecloud.example
Claim your presence on "CDN category: SaaSTools directory" (saastools.example): the engines cite it and you're not on it
Honest time-to-impact: 2–4 weeks (ChatGPT) → 4–8 weeks (Gemini)
- Cited gemini×3, chatgpt×2 for q01, q09
- Competitors on the page: Nimbus, StratoCDN, Fleetly
- URL: saastools.example
- Submit via: claim your profile at saastools.example
- 91% of the pages the engines cited are third-party. 9% are acmecloud.example
Copy-ready draft
Claim & complete your SaaSTools directory profile (checklist)
Why: this directory is cited by Gemini and ChatGPT for CDN questions, and every rival is listed. You are not.
- Verify ownership: request the claim link at saastools.example/claim, confirm via the DNS TXT record or the admin@acmecloud.example email.
- Fill every field the engines read: one-line category ("Edge CDN for high-traffic SaaS"), founding year, HQ, pricing model (flat/public), and a 40-word description whose FIRST sentence says "Acme Cloud is an edge CDN platform."
- Feature 3 factual differentiators (from your own data only): flat public pricing; p95 latency within 4% of Nimbus at ~60% of cost; 18-month clean incident record.
- Add the direct product URL and a current logo.
- Invite reviews compliantly: email recent customers a neutral request; never incentivize or script the wording.
JSON-LD the profile page should carry: Organization.
Get into "CDN reliability report" (uptimewatch.example): the engines cite it and you're not on it
Honest time-to-impact: hours–days (Perplexity) → 2–4 weeks (ChatGPT)
- Cited chatgpt×2, perplexity×2 for q05
- Competitors on the page: StratoCDN, Nimbus, Fleetly
- URL: uptimewatch.example
- Submit via: email hello@uptimewatch.example
- The page winning this question runs ~2,100 words / 10 sections. Match its depth.
- 91% of the pages the engines cited are third-party. 9% are acmecloud.example
Copy-ready draft
Subject: Adding Acme Cloud to your CDN reliability report
Hi {author name},
Your CDN reliability report is one of the pages AI assistants cite when buyers ask which CDN is most reliable. Acme Cloud is missing from it, and here are exactly 3 factual differentiators you can verify:
- 18-month clean incident record across all regions (public status page: status.acmecloud.example).
- Published SLA with credits, no support-tier gating.
- Independent 2026 benchmark: p95 cache-hit latency within 4% of Nimbus.
Happy to share the raw uptime data. No expectations either way.
Disclosure: I work at Acme Cloud.
{maintainer name}, Acme Cloud
03Counter the competitor pages the engines trust: 1 cited page is owned by your rivals
Honest time-to-impact: 2–4 weeks (ChatGPT) → 4–8 weeks (Gemini)
- You can't pitch a rival's own page. Publish your own answer the engines can cite instead.
- nimbus.example (owned by Nimbus): cited chatgpt×2, gemini×1 for q09, q01
- Engines' stated reason Nimbus wins: "the most complete platform" (×3)
- 91% of the pages the engines cited are third-party. 9% are acmecloud.example
Copy-ready draft
Page outline: "Acme Cloud vs Nimbus: an honest, sourced comparison"
H1: Acme Cloud vs Nimbus: where each one actually wins
Opening (≤60 words, answer-first): Nimbus has the larger network and a broader security suite; Acme Cloud wins on flat public pricing, support responsiveness, and cost-for-performance. For globally distributed, compliance-heavy workloads, Nimbus. For predictable cost and fast human support at high traffic, Acme Cloud. Here is the sourced, side-by-side detail.
H2: Network & points of presence (state the gap honestly) H2: Pricing: flat and public vs usage-metered (with a worked example) H2: Performance: the independent 2026 benchmark (within 4% of Nimbus at ~60% cost) H2: Support & reliability: 18-month clean incident record, published SLA
FAQ (4 Q&As): Is Acme Cloud cheaper than Nimbus? · Is Acme Cloud's network big enough for global SaaS? · Which has better support? · Can I migrate from Nimbus to Acme Cloud?
- JSON-LD FAQPage stub with the four questions above. (Do NOT pitch nimbus.example: this is your own citable answer page.)
04Work the long tail: 3 more outlets the engines cite, same playbook
Honest time-to-impact: hours–days (Perplexity) → 4–8 weeks (Gemini)
- Beyond the pitches above, 3 more third-party pages the engines cite lack Acme Cloud. The SAME outreach playbook applies to each.
- reviewsignal.example: cited perplexity×2 · email tips@reviewsignal.example
- cdncompare.example: cited gemini×2 · cdncompare.example
- apidigest.example: cited claude×1
- 91% of the pages the engines cited are third-party. 9% are acmecloud.example
Copy-ready draft
Same playbook as the pitches above: reuse those drafts, swapping in each outlet's angle and the contact channel listed in the evidence. No separate draft is needed. The pitches above ARE the template for these outlets.
05Take back the 3 questions the engines answer without you
Honest time-to-impact: 2–4 weeks (ChatGPT) → 4–8 weeks (Gemini)
- [q01] "What is the best edge CDN platform for a high-traffic SaaS?": no matching page on acmecloud.example (absent on: chatgpt, gemini). Engines answer this from cloudreview.example (cited ×13)
- [q05] "Most reliable edge CDN platform for a high-traffic SaaS?": no matching page on acmecloud.example (absent on: chatgpt). Engines answer this from cloudreview.example (cited ×13)
- [q14] "How do I cut origin egress costs at peak traffic? Which providers help?": no matching page on acmecloud.example (absent on: claude). Engines answer this from stackship.example (cited ×5)
- The page winning this question runs ~2,400 words / 12 sections. Match its depth.
- 91% of the pages the engines cited are third-party. 9% are acmecloud.example
Copy-ready draft
Hub page outline: "Acme Cloud for high-traffic SaaS: the questions buyers ask"
H1: Acme Cloud for high-traffic SaaS
Opening (≤60 words, answer-first): Acme Cloud is an edge CDN for high-traffic SaaS teams that want flat, public pricing and fast human support, with p95 latency within 4% of the market leader at ~60% of the cost and an 18-month clean incident record. This page answers the questions buyers actually ask.
H2: What is the best edge CDN for a high-traffic SaaS? (≤60-word direct answer, then the honest trade-offs) H2: How reliable is Acme Cloud? (≤60-word answer: 18-month clean record, published SLA, live status page) H2: How does Acme Cloud cut origin egress costs at peak? (≤60-word answer: tiered caching + origin shield included, worked example)
FAQ (4 Q&As mirroring the H2s + pricing).
- JSON-LD FAQPage stub covering the four questions.
06Correct the record: engines repeat negative or wrong claims about Acme Cloud
Honest time-to-impact: 2–4 weeks (ChatGPT)
- [q18] chatgpt: "smaller network than the market leaders"
- This rides on an otherwise positive answer: a doubt a buyer hears even when you're praised. If it's outdated, the fix is a page that states your current PoP footprint, sourced.
Copy-ready draft
FAQ / About section: address the "smaller network" doubt with facts
Answer-first (≤60 words): Acme Cloud operates {N} points of presence across {regions}: publish the current number and map. Where AI answers still call the network "smaller," it's citing older coverage; this page is the sourced, current record.
Q: How large is Acme Cloud's network? A: {N} PoPs across {regions}, with p95 cache-hit latency within 4% of Nimbus in the independent 2026 benchmark.
Q: Is Acme Cloud's network big enough for global SaaS? A: {factual coverage statement: no spin, no invented figures}.
- JSON-LD FAQPage stub. Fill every {placeholder} with your real, verifiable data before publishing. Never invent coverage numbers.
07Rewrite your homepage hero to state what you are, machine-readably
Honest time-to-impact: 2–6 weeks
- homepage entity clarity: The homepage's first 800 chars never say "CDN": engines must guess what Acme Cloud is.
08Add Organization and Product JSON-LD to acmecloud.example
Honest time-to-impact: 2–6 weeks
- JSON-LD FAQPage: No FAQPage schema found on crawled pages.
06 · Methodology & honesty
What this is: the answers 4 AI engines gave to your buyers' questions, the pages those answers were built from, and what we found on each. This run: 11 asked · 11 answered · 48 scored. Every number above opens its stored receipt.
The two labels in the header: the profile is the question set (smoke is the short sample set, full is the complete one), and the judge is who scored the answers (cross-family means every answer was judged by a model from a different provider family, which lowers self-preference bias; single-family means one provider served every role).
What this is not: a guarantee, a ranking factor list, or a delta. One run is a snapshot. We label it. Movement is measured set-vs-set on the same frozen questions, and if nothing moved yet, we say so.
What we won't do: scrape AI apps against their terms, invent "AI search volume", sell you an llms.txt file, or show a before/after gap that's really just luck. Full methodology →
Run this on your own brand
Saylent is the open-source audit of what AI assistants say about your brand, with the receipts. The method is documented at yotambraun.github.io/saylent and every line of it is readable at github.com/yotambraun/saylent.
npx saylent audit <your domain>
Two weeks later: the verify re-run
Written by us, like the rest of this sample. A real verify re-run reports whatever the engines say, including no movement.
Recommended 1/12 → 3/12 of category answers
- •Unblock the AI crawlers: +2 questions now name you on Perplexity, including "most reliable edge CDN"
- •Take back the 3 questions: your new reliability page is now cited by Perplexity for [q05]
- •Get added to Best Edge CDNs compared: no movement yet, within the stated 2–8 weeks
Every audit includes one verify re-run on the same frozen questions: honest movement, and "no movement yet" when that's the truth. How often you can re-measure after that is set by whoever operates this deployment.
Every number in your report will be yours.
Real answers from the four engines, the real pages they cite, your real gaps, and the fixes drafted, ready to ship.
Sign in to run your own