Skip to content
Is Agentic

agent-rubric.com

Ready with a few material gaps

79/ 100

Technical readiness score

What should the prompt cover?

8 findings · 5 selected

Failures (4)

Warnings (4)

How the score adds up

18 checks

The agent partially completed the observed task

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

Task

What does agent-rubric.com do and who is it for? Explain it back to me.

29 steps10 reasoning steps9 searches

home
docs
home
search
docs
docs
/how-it-works
search
agentscore-five.home
search
docs
home
search
search
search
search
search
home
search
1 observed runView journey ↗

Critical access needs attention

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.

    1 / 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.

    4 / 4 passed

Advertised capabilities have material gaps

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

Public website

Needs work

66%

10 of 18 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

    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
  3. 03

    Brand name discoverability

    Make sure a clean search for your brand name returns your own domain in the top results. If it does not, your brand may be too generic, conflict with a more established term, or not yet indexed. Strengthen brand-name search by claiming consistent NAP across listings, earning press mentions that link to the canonical domain, and avoiding redirect chains that mask the apex domain in search results.

    Advertised capabilities
  4. 04

    Agent instruction / when-to-use

    Tell agents when to reach for you: add a 'when to use this' section to your llms.txt (or a dedicated agent-instructions file) that names your best-fit use cases and how an agent should call you. Be specific about the jobs you are right for - generic marketing copy does not read as guidance.

    Advertised capabilities
  5. 05

    Content efficiency

    Reduce markup overhead so readable text is at least 5% of your HTML. Strip unused inline scripts/styles, server-render content instead of shipping large JSON hydration blobs, and keep wrapper nesting shallow.

    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.

Essential5 of 7 passed · 66.7 / 80 points
  • Content without JavaScriptPartial (33%)
  • Not blocked by bot detectionPassed
  • robots.txt agent-user policyPassed
  • Redirect hygienePassed
  • Content behind authPassed
  • Agent crawler reachabilityPassed
  • Agent-friendly 404sPartial (50%)
Recommended5 of 11 passed · 10.9 / 20 points
  • Brand name discoverabilityFailed
  • robots.txt AI crawler policyPartial (50%)
  • Sitemap existsPassed
  • Content efficiencyFailed
  • JSON-LD structured dataPassed
  • Agent instruction / when-to-useFailed
  • Metadata completenessPassed
  • Organization schema completenessFailed
  • Trust anchor pagesPartial (50%)
  • Page token budgetPassed
  • Code fence validityPassed
Bonus signals7 positive · +1.6 points
  • llms.txt existsPassed
  • llms.txt formattingPartial (50%)
  • Accessible document structurePassed
  • Native interactive controlsPassed
  • Accessible names on controlsPassed
  • Form control labelingPassed
  • 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 agent-rubric.com.

Source: Ora API

Snapshot 2026-08-19T01-18-59-572+00-00