assafelovic.com
Ready with a few material gaps
Technical readiness score
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 assafelovic.com do and who is it for? Explain it back to me.
24 steps11 reasoning steps6 searches
Critical access needs attention
These checks describe whether an ordinary agent can enter, read, and operate the public site.
- 3 / 3 passed
Agents can reach the site
Crawler access, bot defenses, and explicit agent policy.
- 0 / 1 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 / 1 passed
Controls are understandable
Forms and interactive controls expose usable names and structure.
Advertised capabilities have material gaps
Optional surfaces appear only when the scan finds positive evidence that the site offers them.
Public website
Needs work
7 of 16 mature checks passed
Fix these gaps first
Critical access gaps come first, followed by gaps in capabilities the site advertises.
- 01Critical access
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.
- 02Critical access
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.
- 03Advertised capabilities
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.
- 04Advertised capabilities
Organization schema completeness
Add Organization JSON-LD that includes both contactPoint (with email/phone and contactType) and address (PostalAddress). This lets AI verify your business legitimacy and answer contact queries.
- 05Advertised capabilities
Trust anchor pages
Publish real /about, /contact, and /privacy pages with at least 500 characters of content each. These are the pages AI agents check to verify your business is legitimate before recommending you.
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 6 passed · 68.9 / 80 points
- Content without JavaScriptPartial (67%)
- Not blocked by bot detectionPassed
- robots.txt agent-user policyPassed
- Redirect hygienePassed
- Agent crawler reachabilityPassed
- Agent-friendly 404sPartial (50%)
Recommended3 of 10 passed · 9.2 / 20 points
- Brand name discoverabilityPartial (33%)
- robots.txt AI crawler policyPartial (50%)
- Sitemap existsPassed
- Content efficiencyPartial (50%)
- JSON-LD structured dataPartial (25%)
- Agent instruction / when-to-useFailed
- Metadata completenessPassed
- Organization schema completenessFailed
- Trust anchor pagesFailed
- Page token budgetPassed
Bonus signals4 positive · +0.9 points
- Listed on skills.shPassed
- Skills.sh skill qualityPartial (50%)
- Native interactive 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 assafelovic.com.
Source: Ora API
Snapshot 2026-08-20T07-30-36-97+00-00