Identify the product
Ready
Public product data
Can an agent identify the product and its key specifications?
toshiba-business.com.au
Measured via llm.toshiba-business.com.au
Qualify the requirement is the first gap for toshiba-business.com.au
Qualify the requirement
Needs work
Technical documents + terms
Can an agent understand fit and the constraints needed to quote?
Reach sales
Ready
Public RFQ path
Can an agent hand a qualified request to the right sales path?
Why — machine readability
Scanned Aug 8, 2026
AI reads toshiba-business.com.au at 65/100
B2B RFQ readiness — beta
An assistant can only quote what it can parse. Weakest first:
65/ 100
Needs improvement
Catalog Reach
Whether agents can find your products and reach a quote — feeds, identifiers, and a working RFQ path
42/ 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.
Commercial Terms
Whether an agent can find the terms a quote depends on — minimum order, lead time, payment, and who to contact
50/ 100
Checks: Commercial Clarity
- Commercial Clarity
- Buying terms — minimum order, lead time, payment terms and who to contact — are published as text.
Structured Output
Machine-readable product data embedded in your pages for AI to parse
60/ 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
92/ 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.
65/100 only includes categories we could measure. A category whose checks did not run is reported as not measured, never as a zero.
Assessed from public HTTP responses by AX Score. Site owner? Request removal.