x.com
Technical readiness score
One run shows how an agent performed, but it does not determine the technical score.
Task
14 steps4 reasoning steps5 searches
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.
Core content is available
Useful content remains accessible without a fragile browser-only path.
Navigation fails safely
Redirects and missing pages give agents a recoverable path.
Controls are understandable
Forms and interactive controls expose usable names and structure.
Optional surfaces appear only when the scan finds positive evidence that the site offers them.
Blocked
7 of 18 mature checks passed
Ready with gaps
6 of 9 mature checks passed
Strong
2 of 3 mature checks passed
Needs work
2 of 4 mature checks passed
Critical access gaps come first, followed by gaps in capabilities the site advertises.
Stop blocking user-triggered agents in robots.txt. Remove any 'Disallow: /' that applies to ChatGPT-User, Claude-User or Perplexity-User - including a blanket 'User-agent: * / Disallow: /', which covers them by default. These agents fetch a page only because a person just asked about you, so a block turns away your highest-intent traffic.
Allowlist the major AI crawler/agent User-Agents (ChatGPT-User, ClaudeBot, Google-Extended, ora-agent, DeepSeekBot) in your WAF, bot-detection rules, and robots.txt so agents can reach your homepage.
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.
Server-side render your homepage so AI crawlers see meaningful content without JavaScript. Ensure an H1 and 500+ chars of text in raw HTML.
Return structured JSON error responses with error codes, messages, and resolution hints. Agents can't parse HTML error pages.
Applicable evidence is grouped by how it contributes to this preview model. Bonus checks appear only when they add points.
The complete Ora audit uses evidence from the scan on . After applying changes, run another scan from the homepage to refresh these recommendations.
A weekly report with ranking changes, new agent feedback, and score alerts for x.com.
Source: Ora API
Snapshot 2026-08-18T06-19-38-043Z