Skip to content
Is Agentic

shopify.com

Ready with a few material gaps

73/ 100

Technical readiness score

What should the prompt cover?

13 findings · 5 selected

Failures (8)

Warnings (5)

How the score adds up

30 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 shopify.com do and who is it for? Explain it back to me.

21 steps10 reasoning steps5 searches

home
docs
/products
/features
search
search
/en/blog
search
search
search
/solutions
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.

    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

63%

9 of 18 mature checks passed

API

Needs work

56%

5 of 9 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

    JSON error responses

    Return structured JSON error responses with error codes, messages, and resolution hints. Agents can't parse HTML error pages.

    Advertised capabilities
  5. 05

    Developer resource discoverability

    Make your developer resources (API docs, OpenAPI spec, auth docs, webhooks, MCP server) discoverable by name. Publish them at predictable URLs, list them in llms.txt, and include your product name in page titles and headings so search engines surface them for name-based queries.

    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.

Essential6 of 10 passed · 57.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 responsesFailed
  • Agent-friendly 404sPartial (50%)
Recommended11 of 20 passed · 12.1 / 20 points
  • Developer resource discoverabilityFailed
  • Brand name discoverabilityPartial (33%)
  • robots.txt AI crawler policyFailed
  • Sitemap existsPassed
  • Content efficiencyPartial (50%)
  • JSON-LD structured dataPartial (25%)
  • Public API/docs linked from homepagePassed
  • Agent instruction / when-to-useFailed
  • Metadata completenessPassed
  • Organization schema completenessFailed
  • Trust anchor pagesPassed
  • Page token budgetPassed
  • Code fence validityPassed
  • Developer portalPassed
  • Public API with reachable endpointsPassed
  • Agent onboarding frictionPassed
  • CLI tool availablePassed
  • Multi-language SDK packagesPassed
  • API schema complexity analysisFailed
  • Function calling compatibilityFailed
Bonus signals17 positive · +3.9 points
  • Wikipedia / Wikidata entity presencePartial (50%)
  • NPM/PyPI SDK packagePassed
  • Listed on skills.shPassed
  • ChatGPT app listedPassed
  • MCP well-known discoveryPartial (50%)
  • Sitemap freshness (lastmod)Passed
  • llms.txt existsPassed
  • llms.txt formattingPassed
  • Skills.sh skill qualityPassed
  • JSON-LD entity linking (sameAs)Passed
  • llms.txt links resolvePassed
  • Web Bot Auth directoryPartial (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 shopify.com.

Source: Ora API

Snapshot 2026-08-19T23-51-20-234Z