Social presence not yet detected — Echo will look for it on next scan.
Reviews not yet detected — Echo will look for them on next scan.
Recover $1,513/mo and lift your score by +21.1 pts if all are resolved.
All four scanners ran clean. No protocol-layer endpoints detected yet.
Crawlers are unblocked, but engines aren't yet citing you. We'll fix that.
Two layers flagged orange: citation density and off-site authority.
3 fixes ready to ship the moment you activate. No LLM call needed — these are deterministic drafts from your scan signals.
# Flue
> The Agent Harness Framework
This file helps AI agents (ChatGPT, Claude, Perplexity, Gemini) find the most important content on Flue. Generated by AISO Nova — see https://llmstxt.org for the spec.
## Important pages
- [Home](/): primary landing page — replace with a one-line description
## Optional
- [Blog](/blog): supplementary content not required for primary tasks
## Pricing & about
- [Pricing](/pricing): plans and pricing — replace with the canonical pricing URL
Generated minimum-viable llms.txt per llmstxt.org spec using the brand profile's oneLiner as the tagline. Replace placeholder bullets with real top-page descriptions.
AI engines weight five trust layers when deciding whether to cite you. Lift the weakest layer first; the composite score and grade move fastest there.
Citation-crawl observations weren't recorded on this scan (likely missing PERPLEXITY_API_KEY / GOOGLE_AI_API_KEY). Once citation-crawl runs you'll see per-platform rate sparklines here on every re-scan.
Each finding maps to a specific agent and a fix path.
| # | SEV | CODE | FINDING | LEAK / MO | EFFORT | ACTION |
|---|---|---|---|---|---|---|
| 01 | LOW | template_coverage | Template coverage is limited in homepage-only scans | −$95 | — | |
| 02 | MED | content_gaps | 2 high-impact content gaps detected | −$200 | — | |
| 03 | LOW | content_gaps | 4 entity page gaps detected | −$160 | — | |
| 04 | HIGH | structure | No definition-lead opener in the first 150 tokens | −$325 | — | |
| 05 | HIGH | structure | No FAQ section detected | −$325 | — | |
| 06 | HIGH | citations | External links exist but none hit the authoritative allowlist | −$413 | — | |
| 07 | HIGH | schema | No valid Organization JSON-LD | −$400 | — | |
| 08 | LOW | schema | Core meta tags are incomplete | −$225 | — | |
| 09 | HIGH | llmstxt | No /llms.txt file found | −$300 | — | |
| 10 | MED | freshness | No last-updated signal on homepage | −$275 | — | |
| 11 | MED | entity | No clear self-identification in the opening paragraph | −$200 | — | |
| 12 | LOW | entity | No named author or byline visible | −$160 | — | |
| 13 | MED | entity | No /about or /team page with credentials | −$200 | — | |
| 14 | LOW | entity | Organization JSON-LD missing founder | −$160 | — | |
| 15 | LOW | offsite | No social/authority footprint linked from header or footer | −$95 | — | |
| 16 | HIGH | agent_readiness | No API or OpenAPI entrypoint detected | −$500 | — | |
| 17 | MED | agent_readiness | No MCP entrypoint detected | −$400 | — | |
| 18 | LOW | agent_readiness | No WebMCP access signal detected | −$320 | — | |
| 19 | LOW | agent_readiness | No Portal visit layer detected | −$320 | — | |
| 20 | LOW | agent_readiness | No x402 payment support detected | −$320 | — | |
| 21 | MED | agent_readiness | No agent discovery file detected | −$400 | — | |
| 22 | MED | agent_readiness | No agent skills or action manifest detected | −$400 | — | |
| 23 | LOW | agent_readiness | No clear agent navigation path detected | −$320 | — | |
| 24 | LOW | content_decay | Volatile content lacks update signals | −$225 | — | |
| 25 | MED | ai-discovery | No /.well-known/ai.txt published | −$125 | — | |
| 26 | MED | ai-discovery | No /ai/summary.json published | −$125 | — | |
| 27 | LOW | ai-discovery | No /ai/faq.json published | −$95 | — | |
| 28 | LOW | ai-discovery | No /ai/service.json published | −$95 | — | |
| 29 | LOW | ai-discovery | No /.well-known/agent.json manifest | −$95 | — | |
| 30 | LOW | hreflang | Site is single-locale; hreflang not applicable | −$95 | — | |
| 31 | HIGH | csp-audit | Add a Content-Security-Policy to enable directive-level audit | −$163 | — | |
| 32 | HIGH | answer-extractability | No definition / TL;DR / direct-answer pattern at the top of any sampled page | −$200 | — | |
| 33 | HIGH | answer-extractability | Only 0 list items per page — content lacks scannable structure | −$200 | — | |
| 34 | HIGH | answer-extractability | Fewer than 1 H2/H3 per 500 words — long content lacks structural breaks | −$200 | — | |
| 35 | HIGH | answer-extractability | 1 paragraph exceed 400 words without breaks | −$200 | — | |
| 36 | HIGH | definition-authority | No glossary page or DefinedTerm schema found | −$200 | — | |
| 37 | HIGH | definition-authority | No inline definition patterns found in content | −$200 | — | |
| 38 | LOW | definition-authority | Improvement: Wrap term/definition pairs in <dl><dt>term</dt><dd>def</dd></dl> markup | −$95 | — | |
| 39 | HIGH | comparison-coverage | No dedicated /vs/ or /comparison/ URL | −$200 | — | |
| 40 | HIGH | comparison-coverage | No 'X vs Y' heading patterns found | −$200 | — | |
| 41 | HIGH | comparison-coverage | No pros/cons or advantages/disadvantages sections | −$200 | — | |
| 42 | HIGH | comparison-coverage | No feature comparison tables found | −$200 | — | |
| 43 | LOW | comparison-coverage | Improvement: Add ItemList JSON-LD schema to comparison pages | −$95 | — | |
| 44 | HIGH | internal-link-graph | Not enough data to build a link graph (single page sampled) | −$200 | — | |
| 45 | LOW | patent-news-mentions | Patent + news APIs unreachable — could not measure citation footprint | −$95 | — | |
| 46 | HIGH | delegate_economy | No JSON-LD structured data on homepage | −$200 | — | |
| 47 | MED | factual_accuracy | No measurable factual claims detected on homepage | −$125 | — | |
| 48 | MED | citability | Only 0/2 sections in 134-167 word citable range | −$125 | — | |
| 49 | MED | citability | Only 0% of sections have source-attribution hooks | −$125 | — | |
| 50 | LOW | citability | Specificity low (0%): few numbers, dates, or proper nouns | −$95 | — | |
| 51 | MED | brand_extraction | 'FlueContext' (8×) mentioned more often than your own brand 'Flue' (6×) | −$125 | — | |
| 52 | HIGH | audience_reviews | No JSON-LD blocks on homepage — audience/review signals impossible | −$163 | — | |
| 53 | LOW | webmcp_readiness | No WebMCP manifest detected | −$95 | — | |
| 54 | HIGH | faq-coverage | No FAQPage JSON-LD detected on homepage or sampled pages. | −$200 | — | |
| 55 | HIGH | faq-coverage | No /faq, /help, or /support route surfaced. | −$200 | — | |
| 56 | HIGH | faq-coverage | No question-style subheadings found. | −$200 | — | |
| 57 | HIGH | entity-disambiguation | No Organization JSON-LD detected. | −$200 | — | |
| 58 | HIGH | entity-disambiguation | No founding-year or location anchor in homepage prose. | −$200 | — | |
| 59 | HIGH | entity-disambiguation | Brand "Flueframework" never appears with a disambiguating descriptor (e.g., 'is an X platform'). | −$200 | — | |
| 60 | HIGH | internal_link_graph_scanner | No internal links detected across sampled pages | −$200 | — | |
| 61 | HIGH | trust_stack | Authority trust layer is weak: 0/100 (lowest contributor: citations at 0) | −$163 | — | |
| 62 | HIGH | trust_stack | Identity trust layer is weak: 12/100 (lowest contributor: entity at 0) | −$163 | — | |
| 63 | MED | trust_stack | Safety trust layer is weak: 40/100 (lowest contributor: negative_signals at 10) | −$125 | — | |
| 64 | MED | trust_stack | Consistency trust layer is weak: 47/100 (lowest contributor: freshness at 0) | −$125 | — | |
| 65 | MED | trust_stack | Technical trust layer is weak: 48/100 (lowest contributor: schema at 0) | −$125 | — | |
| 66 | LOW | platform_profiles | Chatgpt readiness is underdeveloped | −$95 | — | |
| 67 | LOW | platform_profiles | Perplexity readiness is underdeveloped | −$95 | — | |
| 68 | LOW | platform_profiles | Google ai readiness is underdeveloped | −$95 | — | |
| 69 | LOW | platform_profiles | Claude readiness is underdeveloped | −$95 | — |
Estimated total recovered: $870/mo.$870/mo TOTAL RECOVERABLE
Weak JSON-LD for product p… — $225
+$225 RECOVERED
3 high-impact content gaps … — $260
4 entity page gaps detected — $100
+$360 RECOVERED
Only direct HTTP certificate… — $95
+$95 RECOVERED
Q3 2026 · early signal — we recommend you ship the missing endpoints now.
The next layer is AI agents that book, buy & transact on behalf of users. Protocols like MCP, x402 and agent-skills turn your site into something agents can actually use — not just read. You’re missing all of them.
| PROTOCOL | WHAT IT DOES | PROBE | STATUS | FIX |
|---|---|---|---|---|
MCP Required | Model Context Protocol Lets agents call your tools & data directly. | GET /mcp.json → 404 | MISSING | 4h · Echo |
x402 Required | Agent Payment Protocol Per-call micropayments — agents pay to reach you. | Accept-Payment header → not advertised | MISSING | 3h · Atlas |
CLI Recommended | CLI / Programmatic access CLI exists, no docs or API spec exposed. | OpenAPI spec → not found · loading API by header | PARTIAL | 3h · Echo |
SKILLS Recommended | Agent Skills manifest Discovered verbs agents can invoke — "book room", "check rates". | GET /agent.json → 404 | MISSING | 3h · Orbit |
6 questions. Sharpens the $ estimate below — no data leaves this device.
Four agents. Four tiers. Grow starts with the first month free. Your team is 3 minutes away.
Join waitlist →Template coverage is limit… — $95
Safety trust layer is weak — $95
+$190 RECOVERED