Udatsu Sushi

Places near Udatsu Sushi that take a booking or an order on their own website, with no marketplace in between.

• くずし割烹おにかい200 m · sushi
• すし匠寿々木670 m · sushi
• 鮨 つきうだ760 m · sushi
• 寿し屋のなか村1.1 km · sushi

What assistants answer

Each assistant gets three questions about this business: the official website, where to book and where to order. Each cell shows where the answer sent people.

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. Udatsu Sushi wasn't one of them. See who was named →

What to fix first

1. The site turns away every visitor that isn't a browser, AI agents included +21.3 points

   A plain fetch was refused (origin_timeout). Only a real browser got the page. Every AI crawler and agent gets turned away the same way, so Reachable scores 0 and the rest is measured on the page as the browser rendered it. Ask the host to let the AI user agents through. How to fix it

2. Structured data is incomplete +3 points

   Missing: opening hours. How to fix it

3. robots.txt blocks GPTBot, ClaudeBot, Google-Extended no points, but worth doing

   These are the crawlers behind ChatGPT, Claude, Perplexity and Google's AI features. Remove the Disallow lines for them, or add explicit Allow rules. How to fix it

Send the fixes to your web person

No one is listed yet to fix this in Tokyo. List your agency or yourself. It's free, and every listing is reviewed by hand.

Already right

• Structured data found (Restaurant) address, phone
• Menu or price list is an HTML page Agents can read the items and prices.
• Booking on your own site Agents can book without going through a marketplace.

Builder: unknown · A plain fetch got origin_timeout; a real browser got the page, so the scan continues on the rendered page.

What to paste

Filled in from the business's own record and this scan. Check every line before it goes live. The guides show where it goes on your builder.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Restaurant",
  "name": "Udatsu Sushi",
  "url": "http://udatsu-sushi.com/",
  "telephone": "+815035505938",
  "address": "2 Chome-48-10 Kamimeguro, 153-0051, 目黒区",
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": 35.64196135,
    "longitude": 139.69526257
  },
  "servesCuisine": [
    "sushi"
  ],
  "acceptsReservations": "https://udatsu-sushi.jp/reservation",
  "hasMenu": "https://udatsu-sushi.jp/menu",
  "potentialAction": [
    {
      "@type": "ReserveAction",
      "target": {
        "@type": "EntryPoint",
        "urlTemplate": "https://udatsu-sushi.jp/reservation",
        "actionPlatform": [
          "http://schema.org/DesktopWebPlatform",
          "http://schema.org/MobileWebPlatform"
        ]
      },
      "result": {
        "@type": "Reservation",
        "name": "Reservation"
      }
    }
  ]
}
</script>

# Let AI assistants read the site: they send people to you; a marketplace keeps them.
# Remove any Disallow lines for these names elsewhere in this file.
User-agent: GPTBot
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: Google-Extended
Allow: /

User-agent: OAI-SearchBot
Allow: /

User-agent: ChatGPT-User
Allow: /

User-agent: Claude-User
Allow: /

User-agent: Perplexity-User
Allow: /