Willow & Thread is an invented apparel store on the reserved .example domain. All findings, scores, prices, capture times and references are fictional. No live scan or transaction took place.
View all free and detailed samplesFictitious sample · all data made up · no real merchant assessed
An evidence-based assessment of how AI systems and autonomous agents discover, understand, trust and act on this website.
Fictitious sample · all data made up · no real merchant assessed
Fictitious sample · all data made up · no real merchant assessed
This fictional snapshot illustrates public-content gaps and unverified agent controls. Review the individual findings and their scope.
ARC's methodology defines 50 checks. This report ran 45 automated checks; 29 produced a scored result, 6 were not applicable and 10 could not be verified. 4 operator-verified checks remain pending. Not applicable and not verified checks carry no points and are not failures.
Categories without a numeric score and why: AI Visibility & Recommendation (PENDING MANUAL) — it depends on operator verification that is still pending; Identity, Authentication & Agent Access (NOT VERIFIED) — the checks that ran could not be verified.
Fictitious sample · all data made up · no real merchant assessed
Each category is scored only from checks that actually ran and could be scored. Where nothing was scored, a state is shown instead of a number — a category with no evaluated tests is not a zero-score failure.
Fictitious sample · all data made up · no real merchant assessed
Whether a control applies depends on what this business actually presents to AI systems and what it intends — not on whether the control happens to exist. Protocol support is shown as evidence, never as credit: a business can be correctly agent-ready while intentionally keeping an agent away from a consequential action.
| SURFACE | CERTAINTY | EVIDENCE |
|---|---|---|
| Commerce (cart and checkout) | ESTABLISHED | cart/checkout path: /cart; purchase control: "Add to cart" |
| Lead generation | ESTABLISHED | contact/enquiry/quote path: /contact |
| Product and service discovery | INDICATED | catalogue/listing path: /products/linen-shirt |
ARC established the following surface(s): commerce (cart and checkout), lead generation, product and service discovery (indicated). The most consequential action an agent could attempt is: consequential.
Observed independently of any agent protocol; protocol presence is listed as context, not credit.
9 of 10 scored checks passed.
9 of 16 scored checks passed.
2 of 3 scored checks passed.
Controls and boundaries below were observed or declared; an absent entry is simply not evidenced, not a failure.
Behaviour against policy is only judged from an independently observed attempt.
Not verified means ARC could not establish an answer. It is neither a pass nor a failure and carries no points.
Consequences are qualitative and only attached to findings that failed or need attention. ARC does not estimate revenue or financial impact.
Protocol-neutral states. Each row says what was evidenced, through which channel, and whether it was observed by ARC or declared by the business. A declared stance is evidence of intent, not of behaviour.
| STATE | RESULT | CHANNEL | WHAT ARC FOUND |
|---|---|---|---|
| Automation observed observed |
EVIDENCED | http probe | ARC's declared-identity request (HoshiroLabsAgentReadyBot) was served normally. |
| Agent identity declared observed |
NOT EVIDENCED | robots txt | robots.txt does not address any named AI agent; the site's published policy does not distinguish declared agent identities. |
| Agent identity verifiable | NOT VERIFIED | none | ARC does not present verifiable agent credentials, so whether the site verifies agent identity cannot be tested from a scan. |
| Underlying principal identifiable | NOT VERIFIED | none | Nothing observed or declared shows who an agent acts for on this site. |
| Authentication mechanism observed observed |
NOT EVIDENCED | http probe | No authentication mechanism was observed on the interfaces ARC could see. |
| Read access allowed observed |
EVIDENCED | http probe | Public content was served to a declared automated client and no blanket robots.txt disallow applies. |
| Write / action access allowed observed |
NOT VERIFIED | structured data | Action paths exist (commerce (cart and checkout), lead generation), but whether an agent is permitted to use them was neither declared nor tested. |
| Consequential action allowed | NOT VERIFIED | none | A consequential surface was established, but whether agents may complete consequential actions was neither declared nor tested. |
| User confirmation required | NOT VERIFIED | none | Not declared and not observed for the consequential surface that was established. |
| Delegated authority evidenced observed |
NOT EVIDENCED | oauth metadata | No machine-readable description of how an agent obtains delegated authority was found. An authenticated or consequential surface was established (commerce (cart and checkout)), but the business has not declared whether agents are meant to act on it. |
| Authority scope / limits evidenced | NOT EVIDENCED | none | Nothing machine-readable states what an agent may do or where its authority ends. |
| Business policy evidenced observed |
EVIDENCED | published policy page | Human-readable policy pages are linked (Returns). They are not an agent-specific policy. |
| Observed behaviour consistent with policy | NOT VERIFIED | none | No independently observed agent attempt exists. ARC does not attempt consequential actions during a scan; behaviour against policy is verified separately. |
| Authority or policy unverifiable | EVIDENCED | none | Authority or policy cannot be fully verified: delegated authority evidenced; authority scope / limits evidenced; observed behaviour consistent with policy remain unresolved. |
| TEST | OUTCOME | REASON, IN TERMS OF THE BUSINESS |
|---|---|---|
| openapi_documentation_valid | NOT APPLICABLE | No API surface is indicated by independent evidence. |
| api_catalog_available | NOT APPLICABLE | No API surface is indicated by independent evidence. |
| public_transaction_interface_documented | NOT VERIFIED | A transaction surface exists, but the business has not declared whether agent-executed transactions are intended. |
| oauth_authorization_server_metadata | NOT VERIFIED | The well-known location could not be reached; that is not evidence of absence. |
| oauth_protected_resource_metadata | NOT VERIFIED | The well-known location could not be reached; that is not evidence of absence. |
| agent_authority_boundaries_evidenced | NOT VERIFIED | An action surface exists, but the business has not declared whether agents are meant to act on it. |
| emerging_commerce_protocol_signals | NOT APPLICABLE | Informational signal: it is evidence of a channel, not of readiness, so it carries no points either way. |
| meta_robots_ai_directive_detected | NOT APPLICABLE | Informational signal: it is evidence of a channel, not of readiness, so it carries no points either way. |
| agentic_web_signals_present | NOT APPLICABLE | Informational signal: it is evidence of a channel, not of readiness, so it carries no points either way. |
Fictitious sample · all data made up · no real merchant assessed
Not verified and not-applicable results are excluded from scoring entirely — never a silent pass, never a fail. A further 4 operator-verified checks are reported separately and are not counted in the 45.
Fictitious sample · all data made up · no real merchant assessed
Every finding below is a check that actually executed. Each carries its stable ARC test ID so it can be re-tested and verified after remediation.
| CHECK | CATEGORY | RESULT | WHY NO VERDICT |
|---|---|---|---|
| A2A agent card is valid a2a_agent_card_valid |
Agent Interfaces & Actionability | NOT VERIFIED | /.well-known/agent-card.json could not be resolved (network/DNS error); presence could not be verified. |
| A2A behavioral verification a2a_behavioral_verification |
Agent Interfaces & Actionability | NOT VERIFIED | No valid A2A agent card with a usable endpoint URL was found, so no task exchange could be attempted. |
| Agent Skills are discoverable and well-formed agent_skills_discoverable |
Agent Interfaces & Actionability | NOT VERIFIED | No publicly documented, standard discovery location exists yet for an Agent Skills manifest on a public website; automating this would require inventing a non-standard convention, so it is always reported as Not verified pending a documented standard. |
| API Catalog is discoverable api_catalog_available |
Agent Interfaces & Actionability | NOT APPLICABLE | No API Catalog was found, and no developer/API surface is indicated by the site's links, forms, structured data or sitemap. Why: No API surface is indicated by independent evidence. |
| MCP endpoint or manifest is discoverable mcp_descriptor_discoverable |
Agent Interfaces & Actionability | NOT VERIFIED | No documented, single well-known path exists for MCP manifest discovery, and no linked/referenced MCP manifest was found on the homepage or in llms.txt -- this check cannot distinguish absence from an undiscoverable-by-convention manifest, so it is reported as Not verified rather than guessed. |
| MCP handshake and tool quality mcp_real_handshake_verified |
Agent Interfaces & Actionability | NOT VERIFIED | No referenced MCP manifest was discoverable, so no handshake endpoint could be identified. |
| OpenAPI documentation is valid openapi_documentation_valid |
Agent Interfaces & Actionability | NOT APPLICABLE | No OpenAPI/Swagger document was found, and no developer/API surface is indicated by the site's links, forms, structured data or sitemap. Why: No API surface is indicated by independent evidence. |
| Public transaction interface is documented public_transaction_interface_documented |
Agent Interfaces & Actionability | NOT VERIFIED | A transaction surface was established (commerce (cart and checkout)). No documented transaction interface was found, but a documented API is only expected if the business intends agents to transact, which has not been declared. A human-only checkout is a valid design. Why: A transaction surface exists, but the business has not declared whether agent-executed transactions are intended. |
| Emerging agentic-commerce protocol signals emerging_commerce_protocol_signals |
Conversion & Agentic Commerce | NOT APPLICABLE | No emerging agentic-commerce protocol signal was found (not required for a typical business). This is an informational signal and is not scored; its absence is not a defect. Why: Informational signal: it is evidence of a channel, not of readiness, so it carries no points either way. |
| AI-specific meta directives detected meta_robots_ai_directive_detected |
Discovery & Crawl Access | NOT APPLICABLE | No AI-specific meta directive found (not a defect -- this is not an established standard). This is an informational signal and is not scored; its absence is not a defect. Why: Informational signal: it is evidence of a channel, not of readiness, so it carries no points either way. |
| Agent authority and limits are evidenced agent_authority_boundaries_evidenced |
Identity, Authentication & Agent Access | NOT VERIFIED | An authenticated or consequential surface was established (commerce (cart and checkout)), but the business has not declared whether agents are meant to act on it. No machine-readable statement of agent limits was found. Whether one is needed depends on intent the business has not declared; a human-only surface is a valid design. Declaring the intended agent policy makes this assessable. Why: An action surface exists, but the business has not declared whether agents are meant to act on it. |
| OAuth Authorization Server Metadata is discoverable oauth_authorization_server_metadata |
Identity, Authentication & Agent Access | NOT VERIFIED | /.well-known/oauth-authorization-server could not be resolved (network/DNS error). Why: The well-known location could not be reached; that is not evidence of absence. |
| OAuth Protected Resource Metadata is discoverable oauth_protected_resource_metadata |
Identity, Authentication & Agent Access | NOT VERIFIED | /.well-known/oauth-protected-resource could not be resolved (network/DNS error). Why: The well-known location could not be reached; that is not evidence of absence. |
| Agentic Web signals present agentic_web_signals_present |
Machine Readability & Content Structure | NOT APPLICABLE | No emerging Agentic Web convention detected (not a defect -- these are emerging, non-standard conventions). This is an informational signal and is not scored; its absence is not a defect. Why: Informational signal: it is evidence of a channel, not of readiness, so it carries no points either way. |
| llms-full.txt is available llms_full_txt_available |
Machine Readability & Content Structure | NOT APPLICABLE | llms-full.txt not found or too short |
| No duplicate/canonical content ambiguity detected duplicate_canonical_ambiguity |
Machine Readability & Content Structure | NOT VERIFIED | Not evaluated at homepage-only scan depth; duplicate-content comparison requires the multi-page sample gathered during a Comprehensive Audit. |
Fictitious sample · all data made up · no real merchant assessed
Category by category: what ARC evaluated, what it scored, and what it could not score. Counts are executed automated checks; operator-verified checks are reported separately.
This category asks: Can AI systems find and access the information you want them to see?
ARC considered 11 automated checks in this category for this assessment: Homepage is fetchable; robots.txt is available; Site is not globally blocked; Named AI crawlers are not blocked; Redirect chain and final host are correct; XML sitemap is available; Sitemap is valid XML; Meta robots / X-Robots-Tag restrictions are documented; WAF/CDN challenge does not block plain HTTP access; Primary content does not require JavaScript execution; AI-specific meta directives detected.
Of 11 automated checks: 9 passed, 1 need attention, 0 failed, 0 not verified, 1 not applicable.
The category score of 93/100 comes from 10 scored checks (9 passed, 1 need attention, 0 failed). Only pass, needs-attention and fail results carry points.
Needs-attention checks mean something relevant is present but incomplete, informational or constrained.
1 check was excluded from this score (1 not applicable, 0 not verified); they neither raised nor lowered it.
This category asks: Can machines reliably read and interpret the important content on your site?
ARC considered 13 automated checks in this category for this assessment: llms.txt is available; llms-full.txt is available; Markdown content negotiation or fallback is available; Descriptive title is present; Meta description is present; Canonical URL is declared; Valid JSON-LD exists; Structured data types are relevant to the business; Service/Product/Offer/FAQ schema exists; Structured data is consistent with visible content; No duplicate/canonical content ambiguity detected; Freshness/date information is present where material; Agentic Web signals present.
Of 13 automated checks: 6 passed, 1 need attention, 3 failed, 1 not verified, 2 not applicable.
The category score of 78/100 comes from 10 scored checks (6 passed, 1 need attention, 3 failed). Only pass, needs-attention and fail results carry points.
Failed checks mean the expected condition was not found in the evidence ARC recorded.
3 checks were excluded from this score (2 not applicable, 1 not verified); they neither raised nor lowered it.
This category asks: Can AI correctly explain what your business offers and answer the questions customers actually ask?
ARC considered 6 automated checks in this category for this assessment: Content is substantial enough to quote; Company/entity name is clear; Entity schema exists; Contact identity is visible; About, policies, or proof signals exist; Key buyer questions are answerable from retrieved content.
Of 6 automated checks: 3 passed, 1 need attention, 2 failed, 0 not verified, 0 not applicable.
The category score of 57/100 comes from 6 scored checks (3 passed, 1 need attention, 2 failed). Only pass, needs-attention and fail results carry points.
Failed checks mean the expected condition was not found in the evidence ARC recorded.
This category asks: Does your business appear when customers use AI to research and compare providers?
ARC considered 0 automated checks and 1 operator-verified check in this category for this assessment: Do AI systems mention and recommend you?.
No automated check result was recorded for this category. 1 operator-verified check has no recorded result yet.
No automated check in this category produced a scoreable result, and the category depends on operator-verified check with no recorded result yet. No numeric score is reported. This is not a zero and not a failure.
Complete the pending operator verification (see "What is missing").
If you believe the manual verification is complete or mis-scoped, contact Hoshiro Labs (reply to your report delivery email).
This category asks: Does your site expose reliable ways for AI agents to use its functions instead of guessing through the UI?
ARC considered 9 automated checks and 1 operator-verified check in this category for this assessment: Form or reachable contact path exists; OpenAPI documentation is valid; API Catalog is discoverable; MCP endpoint or manifest is discoverable; Agent Skills are discoverable and well-formed; A2A agent card is valid; MCP handshake and tool quality; A2A behavioral verification; Public transaction interface is documented; Your in-page AI tools actually work.
Of 9 automated checks: 0 passed, 0 need attention, 1 failed, 6 not verified, 2 not applicable. 1 operator-verified check has no recorded result yet.
The category score of 0/100 comes from 1 scored check (0 passed, 0 need attention, 1 failed). Only pass, needs-attention and fail results carry points.
Failed checks mean the expected condition was not found in the evidence ARC recorded.
8 checks were excluded from this score (2 not applicable, 6 not verified); they neither raised nor lowered it.
This category asks: Can legitimate agents identify themselves and securely access the capabilities they are authorised to use?
ARC considered 3 automated checks and 1 operator-verified check in this category for this assessment: OAuth Authorization Server Metadata is discoverable; OAuth Protected Resource Metadata is discoverable; Agent authority and limits are evidenced; Agent sign-in actually works as documented.
Of 3 automated checks: 0 passed, 0 need attention, 0 failed, 3 not verified, 0 not applicable. 1 operator-verified check has no recorded result yet.
3 checks in this category could not be verified, so no check carried points. NOT VERIFIED means ARC could not reach a conclusion from the evidence available. It is not a failure and no numeric score is reported.
1 operator-verified check in this category remains pending (see below).
If you can supply the endpoint, documentation or access that ARC could not find or reach, send it to Hoshiro Labs and request a reassessment. Contact Hoshiro Labs (reply to your report delivery email).
This category asks: Can an AI agent progress toward a real business outcome such as an enquiry, booking, signup or purchase?
ARC considered 3 automated checks and 1 operator-verified check in this category for this assessment: Clear conversion action is visible; Pricing or offer context is visible; Emerging agentic-commerce protocol signals; An AI agent can actually complete your primary action.
Of 3 automated checks: 2 passed, 0 need attention, 0 failed, 0 not verified, 1 not applicable. 1 operator-verified check has no recorded result yet.
The category score of 100/100 comes from 2 scored checks (2 passed, 0 need attention, 0 failed). Only pass, needs-attention and fail results carry points.
Every scored check met its pass condition.
1 check was excluded from this score (1 not applicable, 0 not verified); they neither raised nor lowered it.
No remediation is required for the checks evaluated in this category.
Fictitious sample · all data made up · no real merchant assessed
These checks are performed by a Hoshiro operator during paid-report fulfilment, never by the automated scanner. A check with no recorded result is NOT VERIFIED — not a pass.
Fictitious sample · all data made up · no real merchant assessed
Items are ordered by priority. Each states the problem, the outcome Hoshiro would deliver, the ARC tests it is verified against, and its commercial status. Implementation method is deliberately out of scope for this document.
Fictitious sample · all data made up · no real merchant assessed
| REMEDIATION ITEM | PRIORITY | DURATION | INDICATIVE PRICE |
|---|---|---|---|
| Answer more buyer questions in extractable text R-01 |
HIGH | To be scoped | Custom Scope Review Required |
| Provide a reliable action path R-02 |
HIGH | To be scoped | Custom Scope Review Required |
| Make primary content available without JS R-03 |
HIGH | To be scoped | Custom Scope Review Required |
| Mark up services and offers R-04 |
MEDIUM | To be scoped | Custom Scope Review Required |
| Create citation-ready answer content R-05 |
LOW | To be scoped | Custom Scope Review Required |
| Strengthen trust and proof R-06 |
LOW | To be scoped | Custom Scope Review Required |
| Publish an llms.txt summary R-07 |
LOW | To be scoped | Custom Scope Review Required |
| Offer a Markdown version of key pages R-08 |
LOW | To be scoped | Custom Scope Review Required |
| 8 items | Custom Scope Review Required | ||
Fictitious sample · all data made up · no real merchant assessed
Representative coverage — a bounded, intelligently selected sample of this site's public pages was assessed, not an exhaustive crawl of every page. Fetched and reviewed on 1 of 1 sampled pages. Detected platform: Unknown / Manual Assessment Required.
| CATEGORY | EXECUTED | PASS | NEEDS ATTENTION | FAIL | NOT VERIFIED | N/A | STATE |
|---|---|---|---|---|---|---|---|
| Discovery & Crawl Access | 11 | 9 | 1 | 0 | 0 | 1 | SCORED |
| Machine Readability & Content Structure | 13 | 6 | 1 | 3 | 1 | 2 | SCORED |
| Business Understanding & Answerability | 6 | 3 | 1 | 2 | 0 | 0 | SCORED |
| AI Visibility & Recommendation | 0 | 0 | 0 | 0 | 0 | 0 | PENDING MANUAL |
| Agent Interfaces & Actionability | 9 | 0 | 0 | 1 | 6 | 2 | SCORED |
| Identity, Authentication & Agent Access | 3 | 0 | 0 | 0 | 3 | 0 | NOT VERIFIED |
| Conversion & Agentic Commerce | 3 | 2 | 0 | 0 | 0 | 1 | SCORED |
| Total | 45 | 20 | 3 | 6 | 10 | 6 |
| CHECK | STATE | ARC TEST ID |
|---|---|---|
| Do AI systems mention and recommend you? | NOT VERIFIED · PENDING | ai_visibility_brand_mention_citation |
| Your in-page AI tools actually work | NOT VERIFIED · PENDING | webmcp_real_interaction_verified |
| Agent sign-in actually works as documented | NOT VERIFIED · PENDING | authenticated_agent_access_verification |
| An AI agent can actually complete your primary action | NOT VERIFIED · PENDING | agent_task_completion_verified |
| PAGES | OBSERVATION |
|---|---|
| 1 of 1 | Invented in-memory HTML; no network collection. |
Full per-URL evidence is in appendix B; it is not repeated in the narrative above.
Fictitious sample · all data made up · no real merchant assessed
Every automated check executed in this assessment, with its stable ARC test ID, result and recorded evidence. 45 checks, registry v2.2.0.
| CHECK | RESULT | EVIDENCE RECORDED BY ARC |
|---|---|---|
| Homepage is fetchable homepage_fetchable |
PASS | HTTP status: 200 Next: Return a stable 200 response for the canonical homepage and remove authentication or interstitial barriers. |
| ||
| robots.txt is available robots_txt_available |
PASS | HTTP status: 200 Next: Add /robots.txt with an explicit crawl policy and Sitemap directive. |
| ||
| Site is not globally blocked site_not_globally_blocked |
PASS | No global Disallow: / Next: Review robots.txt and remove `Disallow: /` for User-agent: * unless the site is intentionally private. |
| ||
| Named AI crawlers are not blocked named_ai_crawlers_not_blocked |
PASS | No explicit AI crawler block detected Next: Review named AI crawler rules and allow approved citation and discovery bots. |
| ||
| Redirect chain and final host are correct redirect_chain_resolves_cleanly |
PASS | 0 redirect hop(s) to final host willow-thread.example. Next: Reduce the homepage redirect chain to a single stable hop to its final host and remove any redirect loop. |
| ||
| XML sitemap is available xml_sitemap_available |
PASS | HTTP status: 200 Next: Generate /sitemap.xml with canonical public URLs and reference it in robots.txt. |
| ||
| Sitemap is valid XML xml_sitemap_valid |
PASS | Sitemap parses as a well-formed sitemap document. Next: Ensure /sitemap.xml is well-formed XML in the sitemap or sitemapindex namespace with real <url> entries. |
| ||
| Meta robots / X-Robots-Tag restrictions are documented meta_robots_restrictions_documented |
PASS | Meta robots/X-Robots-Tag directives found: 'none'. Next: Remove any unintended noindex/nosnippet meta robots or X-Robots-Tag directive that blocks AI-search visibility. |
| ||
| WAF/CDN challenge does not block plain HTTP access waf_challenge_blocks_legitimate_access |
PASS | Homepage response does not match known bot-challenge/interstitial markers (heuristic check). Next: Review WAF/CDN bot-challenge rules so they do not block well-identified AI crawlers along with malicious bots. |
| ||
| Primary content does not require JavaScript execution content_available_without_js |
NEEDS ATTENTION | Static HTML has 52 visible words -- present but modest; no strong JS-dependency signal detected. Next: Server-render or statically pre-render the primary homepage content so it does not require JavaScript execution. |
| ||
| AI-specific meta directives detected meta_robots_ai_directive_detected |
NOT APPLICABLE | No AI-specific meta directive found (not a defect -- this is not an established standard). This is an informational signal and is not scored; its absence is not a defect. Next: If an explicit AI-training opt-out is desired, add a noai/noimageai meta directive; otherwise no action is required. |
| ||
| CHECK | RESULT | EVIDENCE RECORDED BY ARC |
|---|---|---|
| llms.txt is available llms_txt_available |
FAIL | llms.txt not found or not well-formed Next: Add /llms.txt as a concise Markdown summary of the business, offerings and key pages for AI agents. |
| ||
| llms-full.txt is available llms_full_txt_available |
NOT APPLICABLE | llms-full.txt not found or too short Next: Add /llms-full.txt as a fuller Markdown reference alongside llms.txt. |
| ||
| Markdown content negotiation or fallback is available markdown_content_negotiation |
NEEDS ATTENTION | No Markdown content negotiation or /index.md fallback was found (not required). Next: Support Accept: text/markdown content negotiation or publish an /index.md fallback. |
| ||
| Descriptive title is present descriptive_title_present |
PASS | Title: Willow & Thread — fictional apparel store Next: Set a homepage <title> of at least 10 characters that clearly states the business/page identity. |
| ||
| Meta description is present meta_description_present |
PASS | Description metadata found Next: Add a unique meta description stating who the company serves and what it provides. |
| ||
| Canonical URL is declared canonical_url_tag_present |
PASS | Canonical URL: https://willow-thread.example/ Next: Add <link rel="canonical" href="..."> pointing at the preferred absolute homepage URL. |
| ||
| Valid JSON-LD exists valid_json_ld_exists |
PASS | Types: Organization Next: Embed tested schema.org JSON-LD in the homepage head. |
| ||
| Structured data types are relevant to the business schema_types_relevant_to_business |
PASS | Meaningful (non-boilerplate) schema types found: Organization Next: Replace boilerplate-only schema (WebSite/WebPage) with a type matching the actual business (e.g. LocalBusiness, Organization, Product). |
| ||
| Service/Product/Offer/FAQ schema exists service_product_offer_faq_schema |
FAIL | Service/Product/Offer/FAQ schema missing Next: Add appropriate Service, Product, Offer or FAQPage schema matching visible content. |
| ||
| Structured data is consistent with visible content structured_data_matches_visible_content |
PASS | No comparable structured-vs-visible fact (e.g. price) was found to cross-check. Next: Correct the JSON-LD or on-page copy so a fact stated in both places (e.g. price) does not contradict itself. |
| ||
| No duplicate/canonical content ambiguity detected duplicate_canonical_ambiguity |
NOT VERIFIED | Not evaluated at homepage-only scan depth; duplicate-content comparison requires the multi-page sample gathered during a Comprehensive Audit. Next: Review sampled pages for duplicate content and declare a canonical URL for each duplicate cluster. |
| ||
| Freshness/date information is present where material freshness_signals_present |
FAIL | No date/freshness signal was found even though pricing/offer language is present. Next: Add a dateModified/datePublished schema field or a visible last-updated date near pricing/offer content. |
| ||
| Agentic Web signals present agentic_web_signals_present |
NOT APPLICABLE | No emerging Agentic Web convention detected (not a defect -- these are emerging, non-standard conventions). This is an informational signal and is not scored; its absence is not a defect. Next: Consider publishing llms.txt, a documented API, or a referenced MCP manifest as these conventions mature -- not required today. |
| ||
| CHECK | RESULT | EVIDENCE RECORDED BY ARC |
|---|---|---|
| Content is substantial enough to quote content_substantial_enough_to_quote |
NEEDS ATTENTION | Visible word count: 52 Next: Publish concise factual sections that answer buyer questions with attributable claims. |
| ||
| Company/entity name is clear entity_name_clear |
PASS | Title provides entity context Next: Set a non-empty, descriptive homepage <title> that clearly identifies the business. |
| ||
| Entity schema exists entity_schema_exists |
PASS | Entity type detected Next: Add Organization or LocalBusiness JSON-LD with name, URL, logo and contact details. |
| ||
| Contact identity is visible contact_identity_visible |
PASS | Contact signal detected Next: Expose business name and an appropriate contact path in crawlable HTML. |
| ||
| About, policies, or proof signals exist about_policies_proof_signals |
FAIL | Trust/proof signals not detected Next: Add About, privacy or terms pages and substantiated credentials or case studies. |
| ||
| Key buyer questions are answerable from retrieved content business_answerability_extractive_coverage |
FAIL | Extractable support found for 2/9 buyer-question categories: contact, cost. This measures whether information is present, clear and extractable from retrieved content -- it is not a live test of whether an AI answer engine actually answers correctly; that is assessed separately during managed paid fulfilment. Next: Publish clear, extractable text sections answering the buyer questions currently missing (what/who/where/cost/how-to-buy/terms/cancellation/contact/differentiation). |
| ||
| CHECK | RESULT | EVIDENCE RECORDED BY ARC |
|---|---|---|
| Form or reachable contact path exists form_or_contact_path_exists |
FAIL | Forms: 0; /contact: None Next: Create an accessible contact or booking form with clear success and error states. |
| ||
| OpenAPI documentation is valid openapi_documentation_valid |
NOT APPLICABLE | No OpenAPI/Swagger document was found, and no developer/API surface is indicated by the site's links, forms, structured data or sitemap. Next: Serve a real, parseable OpenAPI/Swagger document at the documented API path instead of an SPA catch-all page. |
| ||
| API Catalog is discoverable api_catalog_available |
NOT APPLICABLE | No API Catalog was found, and no developer/API surface is indicated by the site's links, forms, structured data or sitemap. Next: Add /.well-known/api-catalog per RFC 9727 listing the site's public APIs. |
| ||
| MCP endpoint or manifest is discoverable mcp_descriptor_discoverable |
NOT VERIFIED | No documented, single well-known path exists for MCP manifest discovery, and no linked/referenced MCP manifest was found on the homepage or in llms.txt -- this check cannot distinguish absence from an undiscoverable-by-convention manifest, so it is reported as Not verified rather than guessed. Next: Link to the MCP server manifest from the homepage or llms.txt, and ensure it parses as valid JSON with the expected MCP shape. |
| ||
| Agent Skills are discoverable and well-formed agent_skills_discoverable |
NOT VERIFIED | No publicly documented, standard discovery location exists yet for an Agent Skills manifest on a public website; automating this would require inventing a non-standard convention, so it is always reported as Not verified pending a documented standard. Next: Once a standard discovery convention exists, publish and link an Agent Skills manifest there. |
| ||
| A2A agent card is valid a2a_agent_card_valid |
NOT VERIFIED | /.well-known/agent-card.json could not be resolved (network/DNS error); presence could not be verified. Next: Ensure /.well-known/agent-card.json includes identity (name, url) and a skills/capabilities declaration. |
| ||
| MCP handshake and tool quality mcp_real_handshake_verified |
NOT VERIFIED | No referenced MCP manifest was discoverable, so no handshake endpoint could be identified. Next: Ensure the MCP endpoint completes initialize + tools/list over the Streamable HTTP transport, and that every tool has a unique name and a usable description/inputSchema. |
| ||
| A2A behavioral verification a2a_behavioral_verification |
NOT VERIFIED | No valid A2A agent card with a usable endpoint URL was found, so no task exchange could be attempted. Next: Ensure the agent card's url endpoint accepts a message/send JSON-RPC call and returns a valid Task or Message result. |
| ||
| Public transaction interface is documented public_transaction_interface_documented |
NOT VERIFIED | A transaction surface was established (commerce (cart and checkout)). No documented transaction interface was found, but a documented API is only expected if the business intends agents to transact, which has not been declared. A human-only checkout is a valid design. Next: If transactions are supported, document a narrow public interface and its required approval or authentication controls. |
| ||
| CHECK | RESULT | EVIDENCE RECORDED BY ARC |
|---|---|---|
| OAuth Authorization Server Metadata is discoverable oauth_authorization_server_metadata |
NOT VERIFIED | /.well-known/oauth-authorization-server could not be resolved (network/DNS error). Next: Add /.well-known/oauth-authorization-server per RFC 8414 with issuer, endpoints and response_types_supported. |
| ||
| OAuth Protected Resource Metadata is discoverable oauth_protected_resource_metadata |
NOT VERIFIED | /.well-known/oauth-protected-resource could not be resolved (network/DNS error). Next: Add /.well-known/oauth-protected-resource per RFC 9728 with resource and authorization_servers. |
| ||
| Agent authority and limits are evidenced agent_authority_boundaries_evidenced |
NOT VERIFIED | An authenticated or consequential surface was established (commerce (cart and checkout)), but the business has not declared whether agents are meant to act on it. No machine-readable statement of agent limits was found. Whether one is needed depends on intent the business has not declared; a human-only surface is a valid design. Declaring the intended agent policy makes this assessable. Next: Decide what an agent may and may not do on this business (read, prepare, act, commit) and publish it where an agent will find it: OAuth scopes, MCP tool annotations (readOnlyHint/destructiveHint) or an agent-card security requirement. If the intent is that agents must not act, state that and keep the human-confirmation control in place -- no new capability is required. |
| ||
| CHECK | RESULT | EVIDENCE RECORDED BY ARC |
|---|---|---|
| Clear conversion action is visible clear_conversion_action_visible |
PASS | Action language/link detected Next: Add descriptive links or buttons for contact, booking, quote or purchase actions. |
| ||
| Pricing or offer context is visible pricing_offer_context_visible |
PASS | Pricing or offer language detected Next: If the missing pricing/offer language is not a deliberate sales-led choice, publish clear, current offer context suitable for prospective customers. |
| ||
| Emerging agentic-commerce protocol signals emerging_commerce_protocol_signals |
NOT APPLICABLE | No emerging agentic-commerce protocol signal was found (not required for a typical business). This is an informational signal and is not scored; its absence is not a defect. Next: Only relevant if agent-executed payments are part of the business model; not required today. |
| ||
Fictitious sample · all data made up · no real merchant assessed
The pages ARC fetched for this assessment. 1 of 1 were evaluated.
| PAGE TYPE | URL | STATUS | OBSERVATION |
|---|---|---|---|
| homepage | https://willow-thread.example/ | EVALUATED | Invented in-memory HTML; no network collection. |
Fictitious sample · all data made up · no real merchant assessed
Each ARC category is weighted equally. Within a category, a check's contribution reflects its registry scoring weight, scaled down for conditional and emerging-informational maturity checks. REACH and CAPABILITY pillar scores are reported separately, never blended beyond the overall score. Severity is a separate axis from points and drives remediation priority. Not verified and Not applicable checks are excluded from scoring entirely.
Fictitious sample · all data made up · no real merchant assessed
This assessment is a snapshot with an evidence trail. Every finding carries an ARC test ID, so the same tests can be re-run after remediation to verify the change against the criteria used here.