termiprotocol.comscanned Aug 13, 2026 · 11:020.19s

Public AI visibility report

termiprotocol.comAI visibilityAI-Readable

This site is mostly readable by AI tools, with a few improvements still recommended.

Key strengths include homepage access and AI guidance file, while plain-text page access and crawler policy need attention.

Recommended next step

add content negotiation for Accept: text/markdown on the homepage and return a markdown representation with Content-Type: text/markdown.

Keep the HTML response for regular browser requests.

Overall score

76/100

AI-Readable

What happens next

Monitor this score as your site changes

Weekly checks catch robots, sitemap, schema, and content regressions before AI systems stop reusing your pages.

Monitor changes

Download PDF

Go to fixes Overall position199 out of 1,787Leaderboard

// score breakdown

Points by check

8 checks

Crawlability20/20PASS

Robots.txt7.5/15WARN

llms.txt15/15PASS

Sitemap10/10PASS

Markdown support0/15FAIL

Semantic HTML8.6/10WARN

Structured data10/10PASS

Content signals5/5PASS

5pass2warn1fail

Public link

llmscan.dev/scan/O3mZgUMoOEucvRWg7CnKk

Signals checked

8 AI visibility signals

Fix bundle

4 copy-ready files

Share badge

AI-Readable · 76/100

Add a polished proof badge

A compact badge for footer, press, or trust sections that links visitors to this public report.

Embed codellmscan.dev/scan/O3mZgUMoOEucvRWg7CnKk

<a href="https://www.llmscan.dev/scan/O3mZgUMoOEucvRWg7CnKk"
  target="_blank"
  rel="noopener"
>
  <img
    src="https://www.llmscan.dev/scan/O3mZgUMoOEucvRWg7CnKk/badge.png"
    alt="LLM Scan AI visibility score badge"
    width="460"
    height="120"
    style="width: 260px; max-width: 100%; height: auto;"
  />
</a>

Open badge

LLM Scan

AI-Readable

Score

76/100

Share your score

Post the public report with: “We scored 76/100 for AI-readability.”

Download fixes

Grab generated files and implementation notes for the highest-impact gaps.

Rescan weekly

Save this domain to catch regressions after content, sitemap, or robots changes.

Monitor weekly

// signal breakdown

8 signals AI systems depend on

The homepage resolves, connects, returns HTTP 200 OK, exposes a canonical URL, and is not blocked by robots.txt.

Signal weight

20/20

Pass

Evidence

url: https://termiprotocol.com/
finalUrl: https://termiprotocol.com/
status: 200

The robots.txt file was found, but it contains formatting issues.

Signal weight

8/15

Warn

Evidence

robotsTxtUrl: https://termiprotocol.com/robots.txt
exists: true
rawRobotsTxt: # robots.txt — https://termiprotocol.com # The Termi Protocol — a 3D simulation of AI coding agent workflows. # Watch agents you run yourself build, live, in a game-like 3D room. User-agent: * Allow: / Content-Signal: search=yes, ai-input=yes, ai-train=yes # ── AI / LLM crawlers (explicitly allowed for maximum discoverability) ── User-agent: GPTBot Allow: / User-agent: OAI-SearchBot Allow: / User-agent: ChatGPT-User Allow: / User-agent: ClaudeBot Allow: / User-agent: Claude-Web Allow: / User-agent: anthropic-ai Allow: / User-agent: Google-Extended Allow: / User-agent: PerplexityBot Allow: / User-agent: Applebot-Extended Allow: / User-agent: CCBot Allow: / Sitemap: https://termiprotocol.com/sitemap.xml

Recommendation

Next step: Fix robots.txt syntax issues so each rule uses Field: value format, directives appear under a User-agent, and Sitemap entries use absolute URLs.

The llms.txt file was found and includes the expected text, length, heading, and URL signals.

Signal weight

15/15

Pass

Evidence

llmsTxtUrl: https://termiprotocol.com/llms.txt
present: true
accessible: true

The sitemap.xml file is valid and contains URL entries.

Signal weight

10/10

Pass

Evidence

sitemapUrl: https://termiprotocol.com/sitemap.xml
sitemapUrls: [https://termiprotocol.com/sitemap.xml]
robotsSitemapUrls: []

The homepage returned HTML when requested with Accept: text/markdown, so the server appears to ignore markdown content negotiation.

Signal weight

0/15

Fail

Evidence

url: https://termiprotocol.com/
acceptHeader: text/markdown
status: 200

Recommendation

Next step: Add content negotiation for Accept: text/markdown on the homepage and return a markdown representation with Content-Type: text/markdown. Keep the HTML response for regular browser requests.

The homepage has some semantic HTML signals, but one or more title, metadata, heading, landmark, content, or link text checks need improvement.

Signal weight

9/10

Warn

Evidence

url: https://termiprotocol.com/
quality: partial
score: 86

Recommendation

Next step: Add missing semantic elements: main, article, nav, footer.

Valid JSON-LD structured data was found with core Organization or WebSite schema.org types.

Signal weight

10/10

Pass

Evidence

url: https://termiprotocol.com/
quality: good
hasStructuredData: true

AI content usage signals detected via Content-Signal robots.txt directives.

Signal weight

5/5

Pass

Evidence

url: https://termiprotocol.com/
hasContentSignals: true
hasContentSignalHeader: false

Recommendation

Next step: Consider adding Content-Signal HTTP header, AI-specific head meta tags, robots noai/noimageai directive so AI systems can consistently discover content usage preferences across robots.txt, HTTP headers, and HTML metadata.

What happens next

Keep watching this score

Scores move when sites and models change. This one was measured once, on Aug 13, 2026.

Watch weekly

// generated fixes

Downloadable fix files

Preview the generated files below. Enter your email to reveal the full fixes, download the bundle, or copy the agent-ready implementation prompt.

Done-for-you

Agency package

Not sure how to ship the technical fixes? Book a call and we can help turn this report into implemented updates.

Fix planning from your scan

Implementation guidance

AI visibility monitoring

llms.txtMarkdown

# Vibe Coding in 3D: Watch AI Coding Agents | Termi > Turn vibe coding into a live 3D workspace. Watch Claude Code, Codex, Gemini CLI and other AI coding agents read, write and run commands on your machine. This llms.txt file summarizes the public, canonical resources that AI assistants and crawlers should use to understand this site. ## Site Overview - Canonical URL: https://termiprotocol.com/- Site type: organization

robots.txtTXT

# robots.txt additions# Copy these blocks into the existing robots.txt file. Keep current rules unless a note calls out a conflicting Disallow. # Crawl-rate guidance

schema.jsonJSON

{  "@context": "https://schema.org",  "@graph": [    {      "@type": "Organization",      "@id": "https://termiprotocol.com/#organization",      "name": "Vibe Coding in 3D: Watch AI Coding Agents | Termi",      "description": "Turn vibe coding into a live 3D workspace. Watch Claude Code, Codex, Gemini CLI and other AI coding agents read, write and run commands on your machine.",      "url": "https://termiprotocol.com/",

head metaHTML

# Content-Signal recommendations Use these directives to make AI-use preferences explicit for compliant crawlers and AI systems. They are advisory signals, so keep them aligned with robots.txt, terms, and access controls. ## Recommended values - ai-train=no: AI model training, fine-tuning, and dataset creation.- search=yes: AI search indexing, snippets, and discovery.- ai-input=yes: AI answer grounding, retrieval, and generated-response context.

What happens next

Monitor this score as your site changes

Weekly checks catch robots, sitemap, schema, and content regressions before AI systems stop reusing your pages.

Watch weekly

termiprotocol.comAI visibilityAI-Readable

Points by check

Add a polished proof badge

8 signals AI systems depend on

Downloadable fix files

Similar AI visibility reports