123watches.nl
Finalizing the report
Preparing the stored Is Agentic score
Essential—
Recommended—
Bonus signals—
123watches.nl
Preparing the stored Is Agentic score
123watches.nl
These checks describe whether an ordinary agent can enter, read, and operate the public site.
Agents can reach the site
Crawler access and bot defenses.
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.
The public website is always evaluated. Optional surfaces appear when the scan finds positive evidence that they apply.
Needs work
Weighted across 16 applicable checks
Blocked
Weighted across 8 applicable checks
Blocked
Weighted across 3 applicable checks
Needs work
Weighted across 2 applicable checks
Blocked
Weighted across 1 applicable check
Critical access gaps come first, followed by other applicable readiness gaps.
Keep the correct HTTP 404 status. The remaining requirement is a Markdown error body when agents request Accept: text/markdown. Include at least 20 characters explaining the error and a link to your docs, sitemap, or llms.txt. Verify with curl -sS -L -i -H 'Accept: text/markdown' https://yourdomain.com/some-path-that-does-not-exist. Check both the final 404 status and the Markdown body with Content-Type: text/markdown. Checking the status alone does not verify the missing requirement.
Serve at least 500 characters of meaningful homepage content in raw HTML. Add a clear H1, keep deeper heading levels sequential, and remove excessive non-content markup.
Enable Markdown negotiation on the scanned homepage. Supporting it only on /docs or a separate .md URL does not satisfy this check. Requests with Accept: text/markdown must receive a nonempty Markdown body with Content-Type: text/markdown and Vary: Accept. Keep serving HTML for Accept: text/html. Adding Vary alone does not create a Markdown response. Verify both with curl -sS -L -i -H 'Accept: text/markdown' https://yourdomain.com/ and curl -sS -L -i -H 'Accept: text/html' https://yourdomain.com/. Check the final response headers and body: Markdown with Vary: Accept for the first request, HTML for the second.
Put price data in each product page's JSON-LD or microdata. Use a schema.org/Product whose offers is a schema.org/Offer with price, priceCurrency, and availability, or AggregateOffer for a variant price range, so agents can read prices without scraping a marketing page.
Add description to the Organization JSON-LD entity for full score.
Checks are grouped by relevance for Commerce sites.
14008 chars with H1, but heading hierarchy skips H1 to H4; 3.6% content ratio is below the 5% target
How to pass
Serve at least 500 characters of meaningful homepage content in raw HTML. Add a clear H1, keep deeper heading levels sequential, and remove excessive non-content markup.
Site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot).
No meta-refresh stubs, JavaScript-redirect stubs, or cross-domain hops across 1 checked page
Could not probe both Accept: text/markdown and Accept: text/html on the homepage https://123watches.nl
How to pass
Enable Markdown negotiation on the scanned homepage. Supporting it only on /docs or a separate .md URL does not satisfy this check. Requests with Accept: text/markdown must receive a nonempty Markdown body with Content-Type: text/markdown and Vary: Accept. Keep serving HTML for Accept: text/html. Adding Vary alone does not create a Markdown response. Verify both with curl -sS -L -i -H 'Accept: text/markdown' https://yourdomain.com/ and curl -sS -L -i -H 'Accept: text/html' https://yourdomain.com/. Check the final response headers and body: Markdown with Vary: Accept for the first request, HTML for the second.
The nonexistent path https://123watches.nl/__ora-404-probe-od4wkusc correctly returns HTTP 404. Partial credit: no Markdown error body was detected.
How to pass
Keep the correct HTTP 404 status. The remaining requirement is a Markdown error body when agents request Accept: text/markdown. Include at least 20 characters explaining the error and a link to your docs, sitemap, or llms.txt. Verify with curl -sS -L -i -H 'Accept: text/markdown' https://yourdomain.com/some-path-that-does-not-exist. Check both the final 404 status and the Markdown body with Content-Type: text/markdown. Checking the status alone does not verify the missing requirement.
No noindex on the homepage: no robots, googlebot or bingbot meta tag and no X-Robots-Tag header hides it from search.
Valid sitemap found at https://123watches.nl/sitemap.xml with multiple sitemaps entries
JSON-LD Organization found - missing description on this entity
How to pass
Add description to the Organization JSON-LD entity for full score.
No pricing page or pricing data found
How to pass
Put price data in each product page's JSON-LD or microdata. Use a schema.org/Product whose offers is a schema.org/Offer with price, priceCurrency, and availability, or AggregateOffer for a variant price range, so agents can read prices without scraping a marketing page.
3/4 metadata signals present - missing: og:image
How to pass
Add all four signals to your homepage: <link rel="canonical">, <html lang="...">, <meta property="og:image">, and <meta property="og:type">. Agents use these for entity resolution and attribution.
Organization schema found but missing: contactPoint, address
How to pass
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.
Only Privacy page verified - missing: About, Contact
How to pass
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.
All 2 measured pages fit an agent context budget (largest ~4K tokens)
Agent found 2 pages by name but no recognizable developer-resource type. Found on site but absent from this search sample: API docs. Not found in this search sample: OpenAPI spec, SDK documentation
How to pass
Check whether your developer resources (API docs, OpenAPI spec, auth docs, developer portal, MCP server, SDK documentation) surface in name-based searches. If they do not, use predictable URLs, link them in llms.txt, and include your product name in page titles and headings. This result reflects one search sample.
Agent discovery file found at /agents.md
MCP server referenced in llms.txt
Found the llms.txt at https://123watches.nl/llms.txt.
The llms.txt is well-formatted: 48 lines with markdown links, 5,758 characters in total.
All 5 probed llms.txt links resolve to real content
Code fences balanced across 1 markdown document
Path-suffix markdown docs served with text/markdown content-type: /agents.md
All 13 tools on product MCP have detailed descriptions (>= 20 chars)
13/13 tools on product MCP have parameter schemas, 13 with required fields
product MCP exposes 13 tools - substantial tool surface. 6 outputSchema(s) were not checked (over the compile budget for one server)
All 13 tool names follow consistent convention, descriptive, and non-generic
API described in documentation at https://123watches.nl/agents.md but no machine-verifiable API surface confirmed. Best-of-protocols score: 3/7.
How to pass
Expose a public REST or GraphQL API. AI agents need programmatic access - not just a web UI - to integrate with your product.
OpenID Connect discovery endpoint found at https://123watches.nl
RFC 9728 metadata: resource=https://123watches.nl, authorization_servers (1), bearer_methods_supported
Only PRM present; spec calls for both PRM and AS metadata
How to pass
Publish RFC 9728 protected-resource metadata at /.well-known/oauth-protected-resource on your resource server (the host that actually serves the API, e.g. api.<apex>) with resource and authorization_servers. Publish RFC 8414 authorization-server metadata at /.well-known/oauth-authorization-server on the AS origin, and include the WorkOS auth.md agent_auth block with identity_endpoint, identity_types_supported drawn from the spec enum (anonymous, identity_assertion, service_auth - the assertion variant, the ID-JAG URN urn:ietf:params:oauth:token-type:id-jag, belongs inside identity_assertion.assertion_types_supported, not at the top level), and the identity_assertion.assertion_types_supported block when you advertise that type, so agents can check their assertion shape is accepted before minting. Cross-link by listing the AS origin in PRM authorization_servers, and point agent_auth.skill back at your published /auth.md. Spec: https://github.com/workos/auth.md.
MCP server connected via Streamable HTTP - universal-commerce v0.1.0 (protocol 2025-11-25)
product MCP returns structured JSON-RPC errors with code and message
product MCP uses modern Streamable HTTP transport
285 native controls, 0 non-native div-soup affordances (100% native).
267/269 interactive elements have a computable accessible name (99%).
6/6 form controls have an associated label (100%).
No hidden instruction text detected in accessibility-tree attributes or off-screen content.
UCP discovery profile at https://123watches.nl/.well-known/ucp; version 2026-08-25; capabilities: dev.ucp.shopping.checkout, dev.ucp.shopping.fulfillment, dev.ucp.shopping.discount, dev.ucp.shopping.cart
What does 123watches.nl do and who is it for? Explain it back to me.
Sign me up for Vercel product updates and marketing emails.
Unsubscribe anytime. Privacy Notice
Source: Ora API
What does 123watches.nl do and who is it for? Explain it back to me.
23 steps12 reasoning steps4 searches
The agent assembled a coherent explanation of 123watches.nl by working around direct site inaccessibility—the homepage was rate-limited from the start—and relying entirely on third-party review sites and search snippets. It delivered a complete overview of business model, pricing, positioning, and customer sentiment, but could not verify the site's own messaging, full product range, or verify claims directly from their copy.