Identify the product
Couldn't verify
Public product data
Can an agent identify the product and its key specifications?
oriano.com
Scanned from public pages
Identify the product is the first gap for oriano.com
No qualifying RFQ or sales handoff was measurable, so B2B RFQ readiness is capped at 39.
Qualify the requirement
Couldn't verify
Technical documents + terms
Can an agent understand fit and the constraints needed to quote?
Reach sales
Needs work
Public RFQ path
Can an agent hand a qualified request to the right sales path?
Why — machine readability
Scanned Aug 8, 2026
No AX Score published for oriano.com
B2B RFQ readiness — beta
No qualifying RFQ or sales handoff was measurable, so B2B RFQ readiness is capped at 39.
The scan could not verify a product page, so site-level signals are shown without an AX headline score.
No score
Not measured
Commercial Terms
Whether an agent can find the terms a quote depends on — minimum order, lead time, payment, and who to contact
0/ 100
Checks: Commercial Clarity
- Commercial Clarity
- Buying terms — minimum order, lead time, payment terms and who to contact — are published as text.
Catalog Reach
Whether agents can find your products and reach a quote — feeds, identifiers, and a working RFQ path
33/ 100
Checks: Product Feed · Feed Enrichment · Product Enrichment · Product Identifiers · WebMCP Discovery · RFQ Buying Path
- Product Feed
- A machine-readable product feed is discoverable on the site.
- Feed Enrichment
- The product feed carries enriched attributes, not just id/title/price.
- Product Enrichment
- Product schema goes beyond core fields — specifications as additionalProperty entries.
- Product Identifiers
- Products expose GTIN / MPN / SKU identifiers in schema.
- WebMCP Discovery
- An MCP endpoint is discoverable at /.well-known/mcp.json.
- RFQ Buying Path
- A quote or enquiry path is published that an agent can find and follow without a phone call.
Structured Output
Machine-readable product data embedded in your pages for AI to parse
50/ 100
Checks: JSON-LD Presence · Product Fields · Organization Entity · FAQ Quality · Technical Product Documents
- JSON-LD Presence
- Product pages carry Schema.org JSON-LD (Product, Organization, FAQPage) readable in the raw HTML.
- Product Fields
- Product schema includes the core fields: name, image, price, availability, description.
- Organization Entity
- An Organization or LocalBusiness schema identifies who runs the site.
- FAQ Quality
- Buyer questions are answered in FAQPage schema.
- Technical Product Documents
- Product pages link datasheets, spec sheets or manuals an agent can open and read.
No Barriers
How freely AI shopping bots can access and crawl your site
70/ 100
Checks: AI Bot Access · Sitemap · SSR Detection · Response Time · Geo-Redirect · llms.txt
- AI Bot Access
- robots.txt permits AI crawlers (GPTBot, ClaudeBot, PerplexityBot & co).
- Sitemap
- A sitemap.xml lists the catalog for crawlers.
- SSR Detection
- Content is present in the server response, not only after JavaScript runs.
- Response Time
- Pages respond fast enough for agent timeouts.
- Geo-Redirect
- Visitors and crawlers aren’t force-redirected by geography.
- llms.txt
- An llms.txt file guides AI systems to the content that matters.
The diagnostic findings remain visible, but they are not presented as a comparable AX score.
Assessed from public HTTP responses by AX Score. Site owner? Request removal.