What an AI agent reads on Bean Bank Coffee
An assistant's crawler fetches the page once, without running JavaScript, and reads the text, the structured data and the links. Below is what it gets from beanbank.ch, taken from the copy the scanner kept.
356
characters of text without JavaScript, too few to answer questions from
LocalBusiness
structured data for the business
3
of 3 AI crawlers turned away at the edge (GPTBot, ClaudeBot, PerplexityBot)
The words an agent gets
Title: Bean Bank Coffee | Zürich · language en. First 356 of 356 characters:
Bean Bank Coffee | Zürich top of pageBean bank RoastersStoryAccountShopRoasteryContact Bean bank RoastersS C R O L Lnow who want's an espresso?PauseKemptpark Bärengasse Lagerstrasse Basel © 2024 by AlkemeDesign.chshippingPrivacy PolicyTerms & conditionsinfo@beanbank.coffee shippingPrivacyTermsQUICK LINKSIMPRESSUM© 2026 by Alkeme DesignHome bottom of page
What it can say about the business
| A business type in JSON-LD | LocalBusiness |
| Name | Bean Bank Coffee |
| Telephone | no |
| Address | yes |
| Opening hours | no |
| Menu or price list | nothing |
| Cuisine in structured data | no |
| JSON-LD blocks | 2 (LocalBusiness, PostalAddress, WebSite) |
The links it would act on
No booking or ordering link found. An agent has nothing to act on.
Everything here comes from fetching the homepage once as a crawler. The report turns it into a score and a list of fixes, with code to paste.