Honda: 66 of 100 on Ora's agent-readiness scan

The score

Honda is a carmaker and motorcycle maker based in Tokyo, with a global site separate from its country sites.

• 66of 100, grade C
  Ora's agent-readiness scan of global.honda, read 9 November 2026.
• 8Discovery, of 9
  Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
• 19Access, of 37
  Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
• 11Usability, of 17
  Whether they can act through it: an MCP server, an API with a specification, sign-in for agents.
• 0Payments, of 0
  No check in this layer applied to the site.

79 percent of the 132,085 domains Ora ranks score under 60, and the average score is 44.

Ora's one-line summary: Honda's global site offers strong discovery and crawler access, but lacks WebMCP support for agent-driven interactions.

What an assistant meets at the door

Before an assistant can read, compare or buy, it has to get in. These rows are the door: whether the bot shield lets the main agents through, what robots.txt tells the search, training and user-triggered agents, and whether the home page has text without running JavaScript.

What it can read, and what it can do

The reading layer is what an assistant takes away from the pages: a text file written for it, markdown on request, structured data about the company, a sitemap. The act layer is whether it can do anything through a published interface rather than by clicking through the site.

The six payment checks did not apply on this read: Ora did not read the site as a shop.

Three fixes to hand to the web team

Ora estimates how many points each open check would return. These are the largest on this read, in Ora's words where it gave them, so a leader can hand the list over without translating it.

1. WebMCP support, worth about 13.1 points by Ora's estimate: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 14 of 14 same-origin script bundle(s) for modelContext registrations).
2. Agent instruction / when-to-use, worth about 2.7 points by Ora's estimate: No agent instruction file with when-to-use guidance found.
3. Agent-friendly 404s, worth about 2.6 points by Ora's estimate: The nonexistent path https://global.honda/__ora-404-probe-34zjtmi9 correctly returns HTTP 404. Partial credit: no Markdown error body was detected.

Our read

Honda's global site scores 66 on a short denominator. All four agent user agents reach global.honda and the crawlers are allowed, though there is no robots.txt file at all, so permission is the default rather than a decision; the home page gives 1,259 characters with an H1, the metadata is complete and the Organization block lacks only its description, but there is no sitemap and no llms.txt, and the five sampled inner pages were skipped as forms and login pages, so the Access layer reads 19 of 37. The act layer is empty, as for most carmakers here, which is why the Usability layer has a maximum of 17 and the WebMCP estimate of 13.1 points is large only because so few checks apply. The Discovery layer is nearly full at 8 of 9. A sitemap and an llms.txt are the two cheap rows; the C is honest about a site built for people who know where they are going.

Test your own site

Run the same scan on your own domain at ora.ai. The score, the layers and the fixes on this page come from its public result for global.honda; a scan of a public site takes a few minutes and needs no account.

• Scan your domain on OraThe same checks, the same scoring, on your own site.
• The self-check, 18 questionsWhat to ask for, in business terms, before the scan.
• All the 360 checksThe other companies in this series, newest first.