raison.istscanned Jun 4, 2026 · 08:241.29s

Public AI visibility report

raison.istAI visibilityAI-Ready

This site is in strong shape for AI discovery and readability.

Key strengths include homepage access and AI guidance file, while crawler policy needs attention.

Recommended next step

fix the crawler policy file syntax issues so each rule uses Field: value format, directives appear under a User-agent, and Sitemap entries use absolute URLs.

Turn this scan into weekly monitoring.

Create a free workspace first, then unlock weekly monitoring for AI visibility changes after site, pricing, docs, sitemap, or crawler-rule updates.

Unlock monitoring View AI Optimization docs

Overall score

93/100

AI-Ready

Go to fixes Overall position11 out of 550Leaderboard

// score breakdown

Points by check

8 checks

Crawlability20/20PASS

Robots.txt7.5/15WARN

llms.txt15/15PASS

Sitemap10/10PASS

Markdown support15/15PASS

Semantic HTML10/10PASS

Structured data10/10PASS

Content signals5/5PASS

7pass1warn0fail

Public link

llmscan.dev/scan/koTcIbYY30Fce9F71MT0x

Signals checked

8 AI visibility signals

Fix bundle

4 copy-ready files

Share badge

AI-Ready · 93/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/koTcIbYY30Fce9F71MT0x

<a href="https://www.llmscan.dev/scan/koTcIbYY30Fce9F71MT0x"
  target="_blank"
  rel="noopener"
>
  <img
    src="https://www.llmscan.dev/scan/koTcIbYY30Fce9F71MT0x/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-Ready

Score

93/100

Share your score

Post the public report with: “We scored 93/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://raison.ist/
finalUrl: https://raison.ist/
status: 200

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

Signal weight

8/15

Warn

Evidence

robotsTxtUrl: https://raison.ist/robots.txt
exists: true
rawRobotsTxt: User-agent: * Content-Signal: ai-train=no, search=yes, ai-input=yes Allow: / # AI crawler access # Add explicit Allow rules for AI crawlers so public content permissions are clear. User-agent: GPTBot Allow: / User-agent: ChatGPT-User Allow: / Sitemap: https://raison.ist/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://raison.ist/llms.txt
present: true
accessible: true

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

Signal weight

10/10

Pass

Evidence

sitemapUrl: https://raison.ist/sitemap.xml
sitemapUrls: [https://raison.ist/sitemap.xml]
robotsSitemapUrls: []

The homepage returns markdown content when requested with Accept: text/markdown, giving AI systems a cleaner text representation with less navigation chrome to parse.

Signal weight

15/15

Pass

Evidence

url: https://raison.ist/
acceptHeader: text/markdown
status: 200

The homepage has a valid title, meta description, heading structure, semantic landmarks, substantial body copy, and descriptive anchor text.

Signal weight

10/10

Pass

Evidence

url: https://raison.ist/
quality: good
score: 100

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

Signal weight

10/10

Pass

Evidence

url: https://raison.ist/
quality: good
hasStructuredData: true

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

Signal weight

5/5

Pass

Evidence

url: https://raison.ist/
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.

// 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

# Raison - Version Control for AI Prompts | Ship Prompts Like Code > Version, govern, and ship AI prompts with confidence. Built-in version control, approval workflows, evaluations, and rollback. In beta with select partners. 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://raison.ist/- Site type: software application

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. # AI crawler access# Add explicit Allow rules for AI crawlers so public content permissions are clear.User-agent: ClaudeBotAllow: /

schema.jsonJSON

{  "@context": "https://schema.org",  "@graph": [    {      "@type": "Organization",      "@id": "https://raison.ist/#organization",      "name": "Raison - Version Control for AI Prompts | Ship Prompts Like Code",      "description": "Version, govern, and ship AI prompts with confidence. Built-in version control, approval workflows, evaluations, and rollback. In beta with select partners.",      "url": "https://raison.ist/",

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.