Skip to content

news.ycombinator.com

Important blockers remain

68/ 100

Technical readiness score

What should the prompt cover?

15 findings · 5 selected

Failures (8)

Warnings (7)

The agent completed the observed task

One run shows how an agent performed, but it does not determine the technical score.

Task

What does news.ycombinator.com do and who is it for? Explain it back to me.

12 steps2 reasoning steps2 searches

home
docs
/newsguidelines.html
/guidelines
/faq
/newsfaq.html
/item
search
search
/item
1 observed runView journey ↗

Critical access blockers remain

These checks describe whether an ordinary agent can enter, read, and operate the public site.

  • Agents can reach the site

    Crawler access, bot defenses, and explicit agent policy.

    3 / 3 passed
  • Core content is available

    Useful content remains accessible without a fragile browser-only path.

    0 / 2 passed
  • Navigation fails safely

    Redirects and missing pages give agents a recoverable path.

    1 / 2 passed
  • Controls are understandable

    Forms and interactive controls expose usable names and structure.

    2 / 2 passed

Advertised capabilities have material gaps

Optional surfaces appear only when the scan finds positive evidence that the site offers them.

Public website

Blocked

45%

6 of 19 mature checks passed

MCP

Blocked

33%

0 of 2 mature checks passed

Fix these gaps first

Critical access gaps come first, followed by gaps in capabilities the site advertises.

  1. 01

    Content without JavaScript

    Server-side render your homepage so AI crawlers see meaningful content without JavaScript. Ensure an H1 and 500+ chars of text in raw HTML.

    Critical access
  2. 02

    Content behind auth

    Serve your content pages without a login wall. Agents cannot complete auth flows while browsing - a 401/403 or a login-form page is invisible content. Keep public documentation public; if some content must stay gated, publish an ungated summary so agents can still represent it.

    Critical access
  3. 03

    Agent-friendly 404s

    Return a real HTTP 404 (or 410) status for nonexistent paths - never a 200 with your app shell, which makes agents believe every path exists. For full credit, give the 404 response a short markdown body pointing agents at your sitemap, llms.txt, or docs index. Verify with `curl -s -o /dev/null -w "%{http_code}" https://yourdomain.com/some-path-that-does-not-exist` - it must print 404.

    Critical access
  4. 04

    MCP Apps support

    Add MCP Apps support to your MCP server using @modelcontextprotocol/ext-apps. Expose ui:// resources and add _meta.ui.resourceUri to tools so agents can render interactive UIs directly in conversation.

    Advertised capabilities
  5. 05

    robots.txt AI crawler policy

    Add explicit AI crawler directives in robots.txt. Allow the crawlers that feed answer engines ('User-agent: GPTBot' / 'Allow: /', same for ClaudeBot, PerplexityBot, OAI-SearchBot), and restrict training-only crawlers (CCBot, ByteSpider) with 'Disallow: /'. Content Signals ('Content-Signal: search=yes, ai-train=no') earns the same credit.

    Advertised capabilities

Audit the checks behind the score

Applicable evidence is grouped by how it contributes to this preview model. Bonus checks appear only when they add points.

Essential4 of 7 passed · 61 / 80 points
  • Content without JavaScriptPartial (33%)
  • Not blocked by bot detectionPassed
  • robots.txt agent-user policyPassed
  • Redirect hygienePassed
  • Content behind authPartial (50%)
  • Agent crawler reachabilityPassed
  • Agent-friendly 404sPartial (50%)
Recommended2 of 14 passed · 5.5 / 20 points
  • Developer resource discoverabilityPartial (33%)
  • Brand name discoverabilityPartial (33%)
  • robots.txt AI crawler policyFailed
  • Sitemap existsFailed
  • Content efficiencyPassed
  • Content crawl depth signalsFailed
  • JSON-LD structured dataFailed
  • Agent instruction / when-to-useFailed
  • Metadata completenessPartial (50%)
  • Organization schema completenessFailed
  • Trust anchor pagesFailed
  • Page token budgetPassed
  • MCP server / manifestPartial (67%)
  • MCP Apps supportFailed
Bonus signals4 positive · +1 points
  • Agent platform configsPassed
  • Native interactive controlsPassed
  • Accessible names on controlsPassed
  • Accessibility-tree injection safety (bonus)Passed

Inspect the underlying audit

The complete Ora audit uses evidence from the scan on . After applying changes, run another scan from the homepage to refresh these recommendations.

Score alerts

A weekly report with ranking changes, new agent feedback, and score alerts for news.ycombinator.com.

Source: Ora API

Snapshot 2026-08-19T19-08-24-775Z