Why we think this is Astro (2 signals)
- · meta generator: Astro
- · /_astro/ asset path
1 failed out of 9 that apply to your site.
Quick Wins
Top 1 fixes ranked by score impact
- 01Fail+4 pts if fixed
OAuth discovery metadata
See full detailsPublish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.
# Agent-readiness remediation brief Site: https://xspeedcache.com/ Platform: astro (99% confidence) AIScan score: 86/100 — Level 4 (Interactive) Rubric: v2026-06-08.1 ## Failing checks (sorted by weight) - **[P4] OAuth discovery metadata** — FAIL - Evidence: auth-server: 404, protected-resource: 404 - Fix: Publish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints. ## General guidance - Static-first: `robots.txt`, `llms.txt`, `/.well-known/*` JSON cards. - Markdown negotiation: serve `text/markdown` when requested via `Accept` header or `?format=md`. - Bot access: explicit allow/deny per AI user-agent (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, Applebot-Extended, Bytespider, Amazonbot, CCBot, meta-externalagent, cohere-ai, Diffbot). - Capabilities: publish an MCP server card and (optionally) an Agent Skills manifest even if the runtime isn't live — discovery first. - Re-scan at aiscan.site after deploying.
Discoverability
100Can agents find your pages? robots, sitemaps, llms.txt.
Content
100Can agents read your content cleanly? Markdown, structured data.
Bot Access
100Are AI crawlers explicitly allowed or blocked?
Capabilities
50Can agents do things? APIs, auth, MCP, Agent Skills.
Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · P4
What we foundauth-server: 404, protected-resource: 404
How to fix itPublish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.
⚡ Fix automatically with AIScan
Option A — Agent Skill (any agent runtime)
Install the AIScan skill in one command:
```
npx add-skill https://aiscan.site/aiscan-skill.json
```
Or download it directly: https://aiscan.site/aiscan-skill.json
Then ask your agent: "Fix the failing AI readiness checks for <your-url>"Option B — Claude Code skill (CLAUDE.md)
- Download
CLAUDE.mdfrom https://aiscan.site/CLAUDE.md and place it in your project root. - Ask Claude Code: "Fix the failing AIScan checks for <your-url>" — it reads the skill, calls our API, and applies the fix.
Option C — MCP (Claude Desktop, Cursor, or any MCP client)
- Endpoint:
https://aiscan.site/api/mcp - Tools:
scan_website,get_fixes,get_grade - Call
get_fixeswith your URL for machine-readable fix instructions.
Option D — REST API
```
GET https://aiscan.site/api/public/scan?url=YOUR_URL
```
Returns the full report with all checks and fix details.Re-scan at https://aiscan.site to verify after applying fixes.
Publish OAuth discovery metadata
If your API supports OAuth, serve RFC 8414 metadata at
/.well-known/oauth-authorization-serverand/or RFC 9728 at/.well-known/oauth-protected-resource.Verify
After deploying, re-scan at https://aiscan.site. You can also test with
curl -Iorcurldirectly.- Download
Embed your AIScan badge
Drop this badge into your site footer, GitHub README, or docs. It links back to a fresh scan of xspeedcache.com on AIScan.site.
<!-- AIScan.site agent-readiness badge --> <a href="https://aiscan.site/?u=https%3A%2F%2Fxspeedcache.com%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade A (86/100) — AIScan.site"> <img src="https://aiscan.site/api/public/badge.svg?score=86&grade=A&host=xspeedcache.com" alt="AIScan.site Grade A — 86/100" width="240" height="64" loading="lazy" /> </a>
[](https://aiscan.site/?u=https%3A%2F%2Fxspeedcache.com%2F)
Create a free account to track this site over time
- Save scan history
- See score trends
- Re-scan anytime
Automate your AI-readiness
Plug AIScan into your agent stack or chat with it on the go.
Scan your own site
Get a plain-English agent-readiness report you can hand straight to ChatGPT or Claude.