Is studyfetch.com agent ready?
studyfetch.com is partly agent ready: it scores 46/100 (grade C) on the w2agent rubric. Weakest areas: Agent Auth (0), Agent Protocols (20), Agent Discovery (35).
How studyfetch.com compares
Better than 41% of measured sites
vs other Next.js sites: better than 22% of 334 Next.js sites
Next.js median: 56/100
Among 1299 websites measured under rubric v3.0
Changed since last check
+23 points since the previous check (2026-09-15)
Fixed: FAQ content, Answer-first content, Content length, XML sitemap exists, Appropriate Schema.org type, Lists and tables for structured info, llms.txt links resolve, Reachable as Google-Agent, Reachable as Perplexity-User
Regressed: Response time, Security headers
Changed: OpenGraph meta tags (fail → partial), Semantic HTML elements (fail → partial), Canonical URLs (fail → partial), Heading hierarchy (fail → partial), Schema.org JSON-LD present (fail → partial), Schema.org completeness (fail → partial)
Files added: sitemap.xml
Category scores
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryNot measured
- MCP discoveryNot found
- llms.txt validityPresent
Check results
Bot Accessibility
- ~No error status codespartial
- ✗Response timefail
- ✓XML sitemap existspass
- ✓AI agent accesspass
- ?Edge treatment of agent user-agentstracked, not scorederror
- ✓robots.txt existspass
- ✗Content negotiation (Markdown)fail
- —Declared AI usage preferencestracked, not scoredskip
Structured Data
- ~OpenGraph meta tagspartial
- ~Semantic HTML elementspartial
- ✓Appropriate Schema.org typepass
- ✓JSON-LD validpass
- ~Heading hierarchypartial
- ~Schema.org JSON-LD presentpartial
- ~Schema.org completenesspartial
Content Quality
- ✓FAQ contentpass
- ✓Answer-first contentpass
- ✓Content lengthpass
- ✓Token efficiency (HTML-to-text ratio)pass
- ✗Freshness signalsfail
- ✗Author attributionfail
- ✓Citation readinesspass
- ✓Lists and tables for structured infopass
Agent Discovery
- ✓llms.txt follows specpass
- ✓llms.txt existspass
- —MCP server cardtracked, not scoredskip
- ✗Markdown alternate linksfail
- ✗/.well-known/agent-card.jsonfail
- ✓llms.txt links resolvepass
Agent Protocols
- ✗Discoverable API endpointsfail
- ✗MCP endpointfail
- ✗Action schemasfail
- —/.well-known/ucpskip
- —Structured formsskip
- —WebMCP imperative APItracked, not scoredskip
- —WebMCP declarative APItracked, not scoredskip
- ✓Reachable as Google-Agentpass
- ✗Reachable as ChatGPT-Userfail
- ✓Reachable as Perplexity-Userpass
Agent Auth
- —MCP authorization (401 challenge → protected resource metadata)skip
- —PKCE S256 supportskip
- ✗Public API surfacefail
- —Client ID Metadata Documents (bonus)skip
- —OpenAPI specificationskip
- —Agent/bot auth documentationskip
- —OAuth discovery chain (RFC 9728 → RFC 8414)skip
- —Developer portalskip
- —Scoped API permissionsskip
- —API catalog (RFC 9727)skip
- —Agent operator signing directorytracked, not scoredskip
Technical
- ✓HTTPSpass
- ✓UTF-8 charsetpass
- ~Canonical URLspartial
- ✓Mobile viewportpass
- ✓Content accessible without JSpass
- ~Security headerspartial
Other
- ~nextjs-metadata-apipartial
- ~nextjs-static-generationpartial
- ✗nextjs-well-known-servedfail
Score history
- 46/100 · rubric v3.0
- 23/100 · rubric v3.0
- 25/100 · rubric v2.0
- 25/100 · rubric v2.0
- 25/100 · rubric v2.0
- 25/100 · rubric v2.0