This site is mostly readable by AI tools, with a few improvements still recommended.
Key strengths include AI guidance file and plain-text page access, while content signals and homepage access need attention.
Recommended next step
add the standard directive 'Content-Signal: ai-train=no, search=yes, ai-input=yes' to the crawler policy file, HTML metadata, or HTTP headers so AI systems can discover content usage preferences.
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.
Overall score
// score breakdown
8 checks
Public link
llmscan.dev/scan/Dxbv0DKIAlOeA2C3HG1ST
Signals checked
8 AI visibility signals
Fix bundle
4 copy-ready files
Share badge
AI-Readable · 73/100A compact badge for footer, press, or trust sections that links visitors to this public report.
<a href="https://www.llmscan.dev/scan/Dxbv0DKIAlOeA2C3HG1ST"
target="_blank"
rel="noopener"
>
<img
src="https://www.llmscan.dev/scan/Dxbv0DKIAlOeA2C3HG1ST/badge.png"
alt="LLM Scan AI visibility score badge"
width="460"
height="120"
style="width: 260px; max-width: 100%; height: auto;"
/>
</a>Share your score
Post the public report with: “We scored 73/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
The homepage is reachable, but the requested URL redirects before reaching the homepage.
Signal weight
Evidence
Recommendation
Next step: Serve a non-empty HTML homepage with a canonical link tag that points to the preferred public URL.The robots.txt file was found, but it contains formatting issues.
Signal weight
Evidence
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
Evidence
The sitemap.xml file is valid and contains URL entries.
Signal weight
Evidence
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
Evidence
The homepage has some semantic HTML signals, but one or more title, metadata, heading, landmark, content, or link text checks need improvement.
Signal weight
Evidence
Recommendation
Next step: Shorten the meta description to 160 characters or fewer. Avoid skipped heading levels so sections progress from h1 to h2 to h3 without gaps. Add missing semantic elements: article.Valid JSON-LD structured data was found with core Organization or WebSite schema.org types.
Signal weight
Evidence
Content-Signal directive not detected in headers, HTML metadata, or robots.txt.
Signal weight
Evidence
Recommendation
Next step: Add the standard directive 'Content-Signal: ai-train=no, search=yes, ai-input=yes' to robots.txt, HTML metadata, or HTTP headers so AI systems can discover content usage preferences.// generated fixes
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
# Requesty - AI Gateway for 400+ Models > AI gateway and LLM router for 400+ models. Intelligent routing, caching, failover, observability, and enterprise governance through a single OpenAI-compatible API. 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://www.requesty.ai/- Site type: organization# 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.{ "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://www.requesty.ai/#organization", "name": "Requesty - AI Gateway for 400+ Models", "description": "AI gateway and LLM router for 400+ models. Intelligent routing, caching, failover, observability, and enterprise governance through a single OpenAI-compatible API.", "url": "https://www.requesty.ai/", "logo": "https://www.requesty.ai/favicon.ico",# 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.