sushistory.com is hard for agents to use.
32 of 65 points available
agent-readiness level, Basic Web Presence
things to fix
Provisional: the action test and the assistant citation check still to come; the hatched part of the bar is not measured yet.
Add schema.org JSON-LD for the business (Restaurant, LocalBusiness or the closest type) with name, address, telephone and openingHoursSpecification, plus servesCuisine and acceptsReservations for a restaurant. It is the one block every assistant reads first. How to fix it
Agents have nothing to act on. Add a booking or ordering page on your own domain. How to fix it
Optional today, cheap to add: a short text file describing the business for language models. How to fix it
No one is listed yet to fix this in Warsaw. List your agency or yourself: free, reviewed by hand.
Builder: unknown · Front: cloudflare
Top 47% of the sites scanned in this index. Just above: Stary Dom D, Sushi Kado D. Just below: Tendur D, Trattoria Pecorino D.
| What the top tenth of the index does | Top 10% | This site |
|---|---|---|
| Take bookings or orders on their own domain | 28% | no |
| Publish the menu or price list as HTML | 95% | yes |
| Let AI crawlers in (no edge block, no robots.txt block) | 98% | yes |
| Structured data with address, phone and hours | 76% | no |
| Have an llms.txt | 14% | no |
The top tenth is the 80 best-scoring reachable sites of the index at the last refresh.
| Place | Distance | Grade | Direct booking or ordering |
|---|---|---|---|
| Geisha Sushi sushi | 597 m | F | no |
| Fat Cat Sushi&Ramen japanese, sushi, ramen | 1.5 km | C | yes |
| Sushi Niwa japanese, sushi | 1.5 km | D | no |
| Midori sushi | 2.7 km | D | no |
| Neko Sushi sushi | 3.3 km | B | no |
| Akana Sushi japanese, sushi | 4.5 km | D | no |
The standards an agent looks for before it reads a page, on the same criteria as Cloudflare's Agent Readiness scan. Not part of the score; each missing item links to a how-to.
| Link headers on the homepage | no how |
| sitemap.xml | yes |
| AI bot rules in robots.txt | yes |
| Content Signals in robots.txt | no how |
| Markdown on Accept: text/markdown | no how |
| llms.txt | no how |
| API catalog (RFC 9727) | no how |
| MCP server card | no how |
| A2A agent card | no how |
| Agent Skills index | no how |
| OAuth or OIDC discovery | no how |
| OAuth protected resource metadata | no how |
| auth.md | no how |
| Web Bot Auth key directory | no how |
| ARD capability manifest | no how |
| DNS-AID records | no how |
| WebMCP tools on the page | no how |
| JSON-LD for the business | no |
Each assistant is asked three questions about this business: the official website, where to book, where to order. The cell says where the answer sent people.
Not asked yet. Assistants are asked about the top-ranked businesses in each city index, and about every claimed business the moment it is claimed; claim this page to be included.
Owners who score well embed the badge; it links back here and updates with every scan.
<a href="https://directindex.org/r/sushistory.com"><img src="https://directindex.org/badge/sushistory.com.svg" alt="Agent-Direct Score D" width="236" height="40"></a>
Fixed something, or think a check is wrong? Rescans are free. Claiming takes one email to confirm; after that the three assistants are asked about the business right away, the site is rescanned weekly, and you get a message only when the score changes.