# 銀座鮨 佑: Agent-Direct Score C (66.2%)

Site: https://suyu.jp
Report: https://directindex.org/r/suyu.jp
Scanned: 2026-10-22 (Provisional, with the action test and the assistant citation check still to come. The hatched part of the bar isn't measured yet.)
銀座鮨 佑 is partly visible to agents.
An AI assistant can open 銀座鮨 佑's website. It can read what 銀座鮨 佑 offers. It finds a way to book or order directly, through TableCheck.

## Direct links
- Book directly: https://www.tablecheck.com/shops/ginza-sushi-yu/reserve (through tablecheck acting for the business)
- Menu: https://suyu.jp/menu/
- Phone: 03-6264-0165
- Address: 銀座3-14-17, 104-0061, 中央区
- Its menu mentions: vegetarian dishes
- Languages: English, Japanese, Korean, Chinese

## Nearby, also direct
Places near 銀座鮨 佑 that take a booking or an order on their own website, with no marketplace in between.
- 鮨めぐり ひとつ (130 m): https://directindex.org/r/sushimeguri-ginza.info
- 銀座壮石 (300 m): https://directindex.org/r/nishitani-sushi.com

## What to fix first
- **No structured data for the business.** (+14 points) Add schema.org JSON-LD for the business (Restaurant, LocalBusiness or the closest type, with name, address, telephone and openingHoursSpecification, plus servesCuisine and acceptsReservations). Every assistant reads this block first, and the fix kit below has it filled in. Guide: https://directindex.org/guides/structured-data-restaurant

## What the site tells visitors (Measured, not scored)
- **The footer says © 2018.** Visitors and assistants may read that year as the last time anyone looked after the site.

## Fix kit: What to paste

Structured data (JSON-LD). Paste it as one block in the page's head, or in the builder's custom code box. Change anything that's wrong.

```html
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "銀座鮨 佑",
  "url": "https://suyu.jp",
  "telephone": "03-6264-0165",
  "address": "銀座3-14-17, 104-0061, 中央区",
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": 35.6703234657976,
    "longitude": 139.7695598597878
  },
  "potentialAction": [
    {
      "@type": "ReserveAction",
      "target": {
        "@type": "EntryPoint",
        "urlTemplate": "https://www.tablecheck.com/shops/ginza-sushi-yu/reserve",
        "actionPlatform": [
          "http://schema.org/DesktopWebPlatform",
          "http://schema.org/MobileWebPlatform"
        ]
      },
      "result": {
        "@type": "Reservation",
        "name": "Reservation"
      }
    }
  ]
}
</script>
```

## Already right
- **robots.txt lets AI crawlers in.** No rule blocks the main AI user agents.
- **AI crawlers get the page.** GPTBot, ClaudeBot and PerplexityBot all got a normal response.
- **Menu or price list is an HTML page.** Agents can read the items and prices.
- **Booking through tablecheck on your own domain.** There's no marketplace commission, and the customer stays yours.

## Where it stands
1215 of 10292 in Tokyo. Top 12% of the sites scanned in this index.

| What the top 10% of the index does | Top 10% | This site |
|---|---|---|
| Take bookings or orders on their own domain | 77% | yes |
| Publish the menu or price list as HTML | 81% | yes |
| Let AI crawlers in (no block at the server or in robots.txt) | 89% | yes |
| Structured data with address, phone and hours | 17% | no |
| Have an llms.txt | 21% | yes |

Nearest places with a similar menu: 東銀座江戸銀 (C, 12 m, https://directindex.org/r/edogin-sushi.jp); 鮨めぐり ひとつ (C, 130 m, https://directindex.org/r/sushimeguri-ginza.info); Sushi Tomoki (F, 141 m, https://directindex.org/r/sushi-tomoki.jp); 鎌倉以ず美銀座 (F, 154 m, https://directindex.org/r/kamakura-izumi.com); ばぁーどはうす〇勝【まるかつ】 (D, 183 m, https://directindex.org/r/marukatu.jp); 銀座いち分 (D, 188 m, https://directindex.org/r/ginzaichibun.com); 鮨 やまけん (C, 258 m, https://directindex.org/r/sushi-yamaken-shinjuku.com); 鮨三原橋銀九郎 (F, 288 m, https://directindex.org/r/ginkuro.jp); 銀座壮石 (B, 304 m, https://directindex.org/r/nishitani-sushi.com); 寿司田銀座松屋B1店 (F, 336 m, https://directindex.org/r/sushiden.co.jp).

## What assistants answer
The assistants haven't been asked about this business yet. They're asked about the top-ranked businesses in each city index, and about any business as soon as it's claimed. Claim this page to be included.

The assistants were asked 22 everyday questions about Tokyo and named 111 places. 銀座鮨 佑 wasn't one of them. See who was named: https://directindex.org/city/tokyo/recommended


Compared with its peers: Sites built with WordPress 57% (28% A or B, 145483 sites); Sites using TableCheck 63% (29% A or B, 111 sites); This site 66.2%.

See what an AI agent reads on this site: https://directindex.org/r/suyu.jp/agent-view

## Businesses like 銀座鮨 佑 in Tokyo

| Group | Sites | Avg score | A or B | This site |
|---|---|---|---|---|
| Businesses of the same kind in Tokyo | 10292 | 41% | 8% | 66.2% |
| Sites built with WordPress in Tokyo | 3508 | 52% | 14% | 66.2% |
| Sites using TableCheck in Tokyo | 597 | 63% | 27% | 66.2% |
| Sites built with WordPress and using TableCheck in Tokyo | 362 | 67% | 38% | 66.2% |

The best of the sites built with WordPress and using TableCheck in Tokyo: Kamen Rider The Diner (A 93.8%, https://directindex.org/r/pasela.co.jp); Ginza Enzo (A 92.3%, https://directindex.org/r/createdining.com); La Oliva (A 92.3%, https://directindex.org/r/la-oliva.com); Mushroom Tokyo (A 92.3%, https://directindex.org/r/mushroomtokyo.com); グランサイファーキッチン (A 92.3%, https://directindex.org/r/pasela.co.jp).

With the fix above (No structured data for the business), the score would be about 87.7%. That would be 77th of 10,292 in Tokyo, up from 1215th.

## The direct record
What agents get for 銀座鮨 佑, as JSON: https://directindex.org/api/direct/suyu.jp
- Book: https://www.tablecheck.com/shops/ginza-sushi-yu/reserve (vendor on own site: TableCheck; found by the scan of 2026-10-22, not yet tested)
- Order: none on record
- Menu: https://suyu.jp/menu/ (html_page; from the scan)
- Hours: none on record
- Phone: 03-6264-0165
- Stable links that count: https://directindex.org/go/suyu.jp/book, https://directindex.org/go/suyu.jp/menu

## Can an agent transact?
Measured, not scored (the score stays at spec v1.0).
- UCP profile (/.well-known/ucp, Google and Shopify's Universal Commerce Protocol): no
- ACP discovery document (/.well-known/acp.json, OpenAI and Stripe's Agentic Commerce Protocol): no
- MCP server card (/.well-known/mcp/server-card.json): no
- Ordering vendor that takes agent orders (Square, Toast, or a vendor whose terms allow agents): no
- Vendor terms for agents, TableCheck: Not stated. The terms do not address an agent acting for a person (several bar scraping or data extraction only), could not be read on the date given, or the vendor has not been researched yet.

## Score breakdown
| Component | Points | Available |
|---|---|---|
| Reachable | 25 | 25 |
| Readable | 8 | 25 |
| Actionable | 10 | 15 (the action test: pending) |
| Cited | 0 | 0 (the assistant citation check: pending) |

## Agent readiness (Cloudflare)
Level 1 of 5, Basic Web Presence. Cloudflare's report: https://isitagentready.com/suyu.jp
- Link headers on the homepage: no (how: https://isitagentready.com/.well-known/agent-skills/link-headers/SKILL.md)
- sitemap.xml: yes
- AI bot rules in robots.txt: yes
- Content Signals in robots.txt: no (how: https://isitagentready.com/.well-known/agent-skills/content-signals/SKILL.md)
- Markdown on Accept: text/markdown: no (how: https://isitagentready.com/.well-known/agent-skills/markdown-negotiation/SKILL.md)
- llms.txt: yes
- API catalog (RFC 9727): no (how: https://isitagentready.com/.well-known/agent-skills/api-catalog/SKILL.md)
- MCP server card: no (how: https://isitagentready.com/.well-known/agent-skills/mcp-server-card/SKILL.md)
- A2A agent card: no (how: https://isitagentready.com/.well-known/agent-skills/a2a-agent-card/SKILL.md)
- Agent Skills index: no (how: https://isitagentready.com/.well-known/agent-skills/agent-skills/SKILL.md)
- OAuth or OIDC discovery: no (how: https://isitagentready.com/.well-known/agent-skills/oauth-discovery/SKILL.md)
- OAuth protected resource metadata: no (how: https://isitagentready.com/.well-known/agent-skills/oauth-protected-resource/SKILL.md)
- auth.md: no (how: https://isitagentready.com/.well-known/agent-skills/auth-md/SKILL.md)
- Web Bot Auth key directory: no (how: https://isitagentready.com/.well-known/agent-skills/web-bot-auth/SKILL.md)
- ARD capability manifest: no (how: https://isitagentready.com/.well-known/agent-skills/ard/SKILL.md)
- DNS-AID records: no (how: https://isitagentready.com/.well-known/agent-skills/dns-aid/SKILL.md)
- WebMCP tools on the page: no (how: https://isitagentready.com/.well-known/agent-skills/webmcp/SKILL.md)
- JSON-LD for the business: no

Keep watching this business (https://directindex.org/r/suyu.jp/plan): the assistants are asked again every month, and you see what changed. 2 EUR a month or 19 EUR a year.
Deep report: https://directindex.org/r/suyu.jp/deep. Ten questions phrased the way people ask them, each assistant's full answer, the eight nearest similar places, the fix plan and a PDF. 5 EUR, paid once. Reading and scanning stay free. These few euros pay for the questions sent to the assistants and for the servers.
Methodology: https://directindex.org/methodology · Rescan now: https://directindex.org/scan?url=suyu.jp&force=1