Is studiometrodesk.com AI agent ready? A+ · 94/100
Scan history · 12 public scans of studiometrodesk.com
| When | Score | Grade | Snapshot |
|---|---|---|---|
| 7 Sept 2026, 16:52 UTCcae8b3ec | 94/100 | A+ | View → |
| 7 Sept 2026, 16:52 UTC57cffece | 94/100 | A+ | View → |
| 28 Aug 2026, 12:33 UTC34347714 | 94/100 | A+ | View → |
| 5 Jul 2026, 12:30 UTC12966986 | 100/100 | A+ | View → |
| 5 Jul 2026, 7:31 UTC5677b1d4 | 100/100 | A+ | View → |
| 5 Jul 2026, 6:17 UTCeb332790 | 67/100 | B | View → |
| 4 Jul 2026, 19:06 UTC63e10913 | 36/100 | D | View → |
| 4 Jul 2026, 15:58 UTC144d16a6 | 36/100 | D | View → |
| 4 Jul 2026, 7:34 UTC2dbbd699 | 36/100 | D | View → |
| 4 Jul 2026, 7:33 UTC88fffb74 | 36/100 | D | View → |
| 4 Jul 2026, 6:39 UTCb3e4e413 | 36/100 | D | View → |
| 3 Jul 2026, 9:40 UTC58cf1485 | 36/100 | D | View → |
1 failed out of 11 that apply to your site.
Fix automatically with AIScan
1 open check (1 failing) can be handed to an AI agent: E5. Pick one route — each returns the full, check-by-check instructions.
npx add-skill https://aiscan.site/aiscan-skill.jsonThen ask your agent: “Fix the failing AI readiness checks for https://studiometrodesk.com/”.
curl -o CLAUDE.md https://aiscan.site/CLAUDE.mdDrop it in your project root, then ask Claude Code to fix the failing AIScan checks.
https://aiscan.site/api/mcpTools: scan_website, get_fixes, get_grade. Call get_fixes { "url": "https://studiometrodesk.com/" }.
curl -s 'https://aiscan.site/api/public/scan?url=https%3A%2F%2Fstudiometrodesk.com%2F'Returns every check with its complete fix guide.
Verify: Re-scan at https://aiscan.site after applying fixes, or run npx aiscan-cli https://studiometrodesk.com/. Individual checks that need a specific probe list it in their own guide.
Quick Wins
Top 1 fixes ranked by score impact
- 01Fail+3 pts if fixed
Content feed (RSS / Atom / JSON Feed)
See full detailsPublish an RSS, Atom, or JSON Feed of new content and declare it in <head> with <link rel="alternate" type="application/rss+xml">. Feeds give agents a cheap, dated changelog of your site that a sitemap doesn't.
# Agent-readiness remediation brief Site: https://studiometrodesk.com/ Platform: unknown (0% confidence) AIScan score: 94/100 — Level 5 (Agent-Native) Rubric: v2026.08.2 ## Failing checks (sorted by weight) - **[E5] Content feed (RSS / Atom / JSON Feed)** — FAIL - Evidence: no RSS, Atom or JSON Feed found at the conventional paths - Fix: Publish an RSS, Atom, or JSON Feed of new content and declare it in <head> with <link rel="alternate" type="application/rss+xml">. Feeds give agents a cheap, dated changelog of your site that a sitemap doesn't. ## 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.
How this score is calculated
Every check earns points against a weight. We divide the points you earned by the points that actually apply to a site like yours — so checks that don't apply never drag you down.
Baseline every site should meet.
Strong signals most sites benefit from.
Emerging standards. Can only add points.
Not counted (7): B1, B3, P1, P2, P3, P4, E2 — either not applicable to this site profile or optional and not yet adopted. Expand any check to see the exact evidence we based it on.
Discoverability
100Can agents find your pages? robots, sitemaps, llms.txt.
Content
88Can agents read your content cleanly? Markdown, structured data.
Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · E5
What we foundno RSS, Atom or JSON Feed found at the conventional paths
Measured againstHow to fix itPublish an RSS, Atom, or JSON Feed of new content and declare it in <head> with <link rel="alternate" type="application/rss+xml">. Feeds give agents a cheap, dated changelog of your site that a sitemap doesn't.
Publish a feed
RSS, Atom, or JSON Feed — any of them gives agents a cheap, dated changelog of new content that a sitemap can't.
Declare it in <head>
<link rel="alternate" type="application/rss+xml" title="Blog" href="/feed.xml" />
Keep dates accurate
Each item needs a real publish date; that's the freshness signal agents actually use.
Bot Access
100Are AI crawlers explicitly allowed or blocked?
Share as a social image
Download a 1200×630 social card or post straight to X, LinkedIn or Facebook — sized for every feed.
Tip: for X and LinkedIn, upload the downloaded PNG with your post so the card shows in the feed. Posts that include just the link will still preview AIScan.site.
Embed your AIScan badge
Drop this badge into your site footer, GitHub README, or docs. It links back to a fresh scan of studiometrodesk.com on AIScan.site.
<!-- AIScan.site agent-readiness badge --> <a href="https://aiscan.site/?u=https%3A%2F%2Fstudiometrodesk.com%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade A+ (94/100) — AIScan.site"> <img src="https://aiscan.site/api/public/badge.svg?score=94&grade=A%2B&host=studiometrodesk.com" alt="AIScan.site Grade A+ — 94/100" width="240" height="64" loading="lazy" /> </a>
[](https://aiscan.site/?u=https%3A%2F%2Fstudiometrodesk.com%2F)
Create a free account to track this site over time
- Save scan history
- See score trends
- Re-scan anytime
Dig deeper
studiometrodesk.com is built on Custom / Unknown. AI-agent readiness for custom and unrecognised stacks walks through the same checks on that platform.
This page always shows the most recent public scan for studiometrodesk.com.