Skip to content
Is Agentic

www.bigcommerce.com

Ready with a few material gaps

79/ 100

Technical readiness score

What should the prompt cover?

15 findings · 5 selected

Failures (11)

Warnings (4)

How the score adds up

35 checks

The agent completed the observed task

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

Task

What does www.bigcommerce.com do and who is it for? Explain it back to me.

19 steps4 reasoning steps7 searches

home
docs
/enterprise
/features
/solutions
search
search
search
/compare/bigcommerce-v…
search
search
search
search
docs
docs
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.

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

Ready with gaps

71%

11 of 18 mature checks passed

API

Blocked

43%

6 of 14 mature checks passed

Authentication

Strong

100%

3 of 3 mature checks passed

Fix these gaps first

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

  1. 01

    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
  2. 02

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

    OpenAPI spec published

    Publish an OpenAPI (Swagger) specification at /openapi.json or /api/openapi.yaml. This is how agents understand your API surface automatically.

    Advertised capabilities
  4. 04

    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
  5. 05

    Idempotency-Key support

    Support an idempotency key on your write operations and declare it where agents can read it: an Idempotency-Key header parameter on your POST/PUT/PATCH operations in your OpenAPI spec for REST, or a client-supplied id argument on your GraphQL mutations. Agents retry on network failures, and without this a retry can double-charge or duplicate a record.

    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.

Essential7 of 10 passed · 65.3 / 80 points
  • Content without JavaScriptPartial (67%)
  • Not blocked by bot detectionPassed
  • robots.txt agent-user policyPassed
  • Redirect hygienePassed
  • OpenAPI spec publishedFailed
  • Agent crawler reachabilityPassed
  • OAuth 2.0 supportPassed
  • Scoped permissionsPassed
  • JSON error responsesPassed
  • Agent-friendly 404sPartial (50%)
Recommended13 of 25 passed · 10.9 / 20 points
  • Developer resource discoverabilityPassed
  • Brand name discoverabilityPartial (33%)
  • robots.txt AI crawler policyFailed
  • Sitemap existsPassed
  • Content efficiencyFailed
  • JSON-LD structured dataPartial (25%)
  • Public API/docs linked from homepagePassed
  • Agent instruction / when-to-usePassed
  • Metadata completenessPassed
  • Organization schema completenessFailed
  • Trust anchor pagesPassed
  • Page token budgetPassed
  • Code fence validityPassed
  • Developer portalPassed
  • Public API with reachable endpointsPassed
  • Agent onboarding frictionPassed
  • Rate limit response headersFailed
  • Idempotency-Key supportFailed
  • REST typed error modelFailed
  • REST versioning / deprecation policyFailed
  • REST async-job patternFailed
  • CLI tool availablePassed
  • Multi-language SDK packagesPassed
  • API schema complexity analysisFailed
  • Function calling compatibilityFailed
Bonus signals12 positive · +2.5 points
  • Wikipedia / Wikidata entity presencePartial (50%)
  • NPM/PyPI SDK packagePassed
  • Agent platform configsPassed
  • Agent mode viewPassed
  • Sitemap freshness (lastmod)Passed
  • llms.txt existsPassed
  • llms.txt formattingPartial (50%)
  • JSON-LD entity linking (sameAs)Partial (50%)
  • REST batch / bulk endpointPartial (50%)
  • 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 www.bigcommerce.com.

Source: Ora API

Snapshot 2026-08-19T23-52-20-945Z