Scan summary

Ready

sbox.ac

Scanned
CachedRe-check after fixes to refresh the report.
Pages scanned1 / 1
Priority fixes2
Checks passing61 / 66
93/100

Score verdict

Nearly ready

Level 4

See something off? Mention @kordugg on X.

Findable

9724.3/25 pts
24.3 of 25 answer engine points

Quotable

9523.8/25 pts
23.8 of 25 answer engine points

Understandable

10025/25 pts
25 of 25 answer engine points

Trustworthy

8220.5/25 pts
20.5 of 25 answer engine points

AI Readiness

9010/12
10 of 12 passing

Technical SEO

9320/26
20 of 26 passing

Security

1007/10
7 of 10 passing

Performance

No signal
No public signal

Production Quality

908/14
8 of 14 passing

Report brief

What stands out

sbox.ac scored 93/100 on this public readiness scan. 1 page were checked from 1 discovered URLs.

Top findings

  1. Needs workOAuth discoveryAI Readiness

    OAuth or OIDC discovery metadata is missing or incomplete

  2. Needs workx402Production Quality

    No x402 discovery markers were detected

Category context

  • AI Readiness: 90/100
  • Technical SEO: 93/100
  • Security: 100/100
  • Performance: no signal
  • Production Quality: 90/100

AI Readiness

OAuth discovery

Needs work
Goal

Expose OAuth/OIDC discovery metadata so agents can authenticate against your APIs programmatically.

Issue

OAuth or OIDC discovery metadata is missing or incomplete

How to fix

If your site has protected APIs, publish /.well-known/openid-configuration (for OpenID Connect) or /.well-known/oauth-authorization-server (for OAuth 2.0) with `issuer`, `authorization_endpoint`, `token_endpoint`, `jwks_uri`, and `grant_types_supported`. This lets agents discover how to authenticate without parsing your docs.

Resources

AI bot rules

Watch
Goal

Set robots.txt rules for AI search, user-triggered browsing, and training crawlers that match your content policy.

Issue

AI search/user crawlers are allowed, while one or more training/data-use crawlers are blocked as a policy choice

How to fix

Add explicit User-agent entries for AI crawlers — GPTBot, OAI-SearchBot, ClaudeBot, Claude-Web, Google-Extended, PerplexityBot, CCBot — with Allow/Disallow rules that reflect your policy. Decide per-bot whether you want training access, search indexing, or both, and document the choice in source so it doesn't silently drift in future edits.

Fix guide

Technical SEO

Internal Link Quality

Watch
Goal

Internal links use descriptive anchor text and form a reachable graph so crawlers, readers, and AI agents can navigate context.

Issue

1 link crawlability or anchor-text warning(s) were detected.

How to fix

Use real `<a href="...">` elements for navigation — never `<div onclick>` or button-styled spans, which crawlers can't follow. Write descriptive anchor text that summarizes the destination (avoid "click here", "read more", or naked URLs). Keep important pages within ~3 clicks of the homepage so crawl depth doesn't starve them.

Affected pages (1)

Content Depth and Duplication

Watch
Goal

Each indexable page carries enough unique, substantive content to merit indexing on its own without overlapping siblings.

Issue

0 page(s) are under 100 words; 1 page(s) are between 100 and 300 words; 0 duplicate-content fingerprint group(s) were detected.

How to fix

Audit indexable pages for substantive, unique content — at minimum a few hundred words of original copy that delivers on the title and description. Consolidate near-duplicate pages with canonical tags or merge them into a single richer page. Don't ship placeholder "Coming soon" pages to production indexable URLs.

Affected pages (1)

External Citation Links

Observed
Result

No article-like content pages requiring external citations were detected in the sample.

How to fix

Add outbound citations only where the page makes claims that benefit from primary sources, standards, or official documentation.

FAQ Content

Observed
Result

No visible FAQ-style questions or FAQPage JSON-LD were detected.

How to fix

Add visible question-and-answer sections only where they genuinely help users make a decision or complete a task.

Hreflang Annotations

Observed
Goal

Pages declare language and region alternates with hreflang annotations when content varies by locale, so search engines route the right version to the right reader.

Result

No hreflang annotations were detected in the sampled pages.

How to fix

On each localized page, add `<link rel="alternate" hreflang="...">` tags pointing to every language/region variant (including a self-reference). Use valid IANA language-region codes (e.g. `en-US`, `fr-FR`), absolute `href` URLs, and one `hreflang="x-default"` entry pointing to the version for unspecified locales. Each variant must reciprocally link back.

Page and Server Snapshot

Observed
Goal

Lightweight server and document metrics from the sampled homepage are captured every scan so drift in HTML size, server stack, or DOM complexity is observable across reports.

Result

Captured lightweight server and document metrics from the sampled homepage.

Security

Cloudflare Challenge Signals

Observed
Result

No Cloudflare Challenge Page marker was detected on the homepage response.

DNSSEC Signals

Observed
Result

No DNSSEC DS or DNSKEY records were detected for the DNS zone.

Domain Trust

Unavailable
Issue

Domain registration data is temporarily unavailable.

Performance

Cloudflare Cache Signals

Observed
Result

Cloudflare reported cache status DYNAMIC.

PageSpeed Insights

Unavailable

PageSpeed Insights returned no Lighthouse result.

PageSpeed sometimes throttles or skips a URL. The miss is cached on our side for ~15 minutes, so refreshing this report often returns the same answer. A fresh scan is the surest fix.

What this means
  • The URL might be unsupported (e.g. a single-page route Lighthouse can't reach).
  • Google could be rate-limiting our project key — usually clears within a few minutes.
  • The page returned a redirect chain or a non-200 that Lighthouse refused to score.
Run fresh scan

CrUX Field Data

No field data

Chrome doesn't have enough real-user traffic for this site to publish field metrics yet — this isn't a failure on your side.

The Chrome User Experience Report only covers public origins with enough opted-in Chrome traffic. Smaller or newly launched sites typically appear after they accumulate sufficient sample size. Lab performance (PageSpeed Insights) below stays a useful proxy in the meantime.

Production Quality

x402

Needs work
Goal

Support x402-style HTTP 402 payment flows so agents can pay for API access machine-to-machine.

Issue

No x402 discovery markers were detected

How to fix

Add x402 payment middleware to your API routes so AI agents can pay for access via HTTP. Use `@x402/express`, `@x402/hono`, or `@x402/next` middleware with a facilitator URL and wallet address. Protected routes will return HTTP 402 with payment requirements that agents can fulfill automatically.

Resources

Scan Coverage

Observed
Result

Scanned every discovered page (1).

Cloudflare Error Diagnostics

Observed
Result

No Cloudflare-generated error diagnostics were detected on the homepage response.

HTML Validation

Unavailable
Issue

HTML validation is temporarily unavailable.