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://isitagentready.com/
- finalUrl
- https://isitagentready.com/
- status
- 200
Public AI visibility report
isitagentready.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 structured data and crawler policy need attention.
Recommended next step
add JSON-LD structured data with Organization or WebSite schema so AI systems can identify the site owner or website entity.
Overall score
81/100
AI-ReadableWhat 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.
// score breakdown
Points by check
8 checks
Crawlability20/20PASS
Robots.txt7.5/15WARN
llms.txt15/15PASS
Sitemap10/10PASS
Markdown support15/15PASS
Semantic HTML8.6/10WARN
Structured data0/10FAIL
Content signals5/5PASS
5pass2warn1fail
Public link
llmscan.dev/scan/mK3M0syqWdt4SgfUAMYJC
Signals checked
8 AI visibility signals
Fix bundle
4 copy-ready files
Share badge
AI-Readable · 81/100Add a polished proof badge
A compact badge for footer, press, or trust sections that links visitors to this public report.
Embed codellmscan.dev/scan/mK3M0syqWdt4SgfUAMYJC
<a href="https://www.llmscan.dev/scan/mK3M0syqWdt4SgfUAMYJC"
target="_blank"
rel="noopener"
>
<img
src="https://www.llmscan.dev/scan/mK3M0syqWdt4SgfUAMYJC/badge.png"
alt="LLM Scan AI visibility score badge"
width="460"
height="120"
style="width: 260px; max-width: 100%; height: auto;"
/>
</a>L
LLM Scan
AI-Readable
Score
81/100
Share your score
Post the public report with: “We scored 81/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 robots.txt file was found, but it contains formatting issues.
Signal weight
8/15
Warn
Evidence
- robotsTxtUrl
- https://isitagentready.com/robots.txt
- exists
- true
- rawRobotsTxt
- # Is Your Site Agent-Ready? - https://isitagentready.com # This site welcomes AI agents and crawlers. User-agent: * Allow: / Content-Signal: ai-train=yes, search=yes, ai-input=yes Sitemap: https://isitagentready.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://isitagentready.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://isitagentready.com/sitemap.xml
- sitemapUrls
- [https://isitagentready.com/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://isitagentready.com/
- acceptHeader
- text/markdown
- status
- 200
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://isitagentready.com/
- quality
- partial
- score
- 86
Recommendation
Next step: Add missing semantic elements: article.No JSON-LD, Microdata, or RDFa structured data was found on the page.
Signal weight
0/10
Fail
Evidence
- url
- https://isitagentready.com/
- quality
- none
- hasStructuredData
- false
Recommendation
Next step: Add JSON-LD structured data with Organization or WebSite schema so AI systems can identify the site owner or website entity.AI content usage signals detected via Content-Signal robots.txt directives.
Signal weight
5/5
Pass
Evidence
- url
- https://isitagentready.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 6, 2026.
// 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 packageNot 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
# Is Your Site Agent-Ready? > Scan your website to see if it's ready for AI agents. Check for llms.txt, MCP, agent skills, and other agent-friendly standards. 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://isitagentready.com/- Site type: websiterobots.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: GPTBotAllow: / User-agent: ChatGPT-UserAllow: /schema.jsonJSON
{ "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://isitagentready.com/#organization", "name": "Is Your Site Agent-Ready?", "description": "Scan your website to see if it's ready for AI agents. Check for llms.txt, MCP, agent skills, and other agent-friendly standards.", "url": "https://isitagentready.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.