restaurant-diemeise-potsdam.de is largely invisible to agents.
AI assistants cannot open the website of Die Meise, so they rely on what other sites say about it.
This listing was retired on 2026-10-15: it no longer appears in the index's source for its city. The report stays; the business is out of the rankings and counts.
Listed by OpenStreetMap.
Menu: www.restaurant-diemeise-potsdam.de/a-la-carte/
See what an AI agent reads on this site →
7 of 65 points available
agent-readiness level
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.
Since the scan of 2026-10-14: fixed The site could not be read at all. new The site turned every visitor without a browser away; No structured data for the business; No booking or ordering path at all.
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.
The ranking refreshes hourly; this site joins it on the next refresh.
| What the top tenth of the index does | Top 10% | This site |
|---|---|---|
| Take bookings or orders on their own domain | 84% | no |
| Publish the menu or price list as HTML | 75% | yes |
| Let AI crawlers in (no edge block, no robots.txt block) | 83% | no |
| Structured data with address, phone and hours | 41% | no |
| Have an llms.txt | 26% | no |
The top tenth is the 510 best-scoring reachable sites of the index at the last refresh.
| Average score | A or B | This site | |
|---|---|---|---|
| Sites built with Jimdo 600 sites | 38% | 0% | 10.8% |
| Group | Sites | Avg score | A or B | This site |
|---|---|---|---|---|
| Businesses of the same kind in Berlin | 4,748 | 46% | 19% | 10.8% |
| Sites built with Jimdo in Berlin | 78 | 34% | 0% | 10.8% |
Budike C 63.5% · Aapka C 62% · Ajanta C 62% · Apeccino C 62% · Blue Nile C 62%
With the three fixes above (The site turns every visitor without a browser away, AI agents included; No structured data for the business; No booking or ordering link on the website) the score would be about 95.4%: 37th of 4,748 in Berlin, up from not ranked today.
Peers are the businesses of the same index with a reachable site, latest scan of each; the rank uses the index's current ranking.
A plain fetch was refused (challenge:attention required); only a real browser got the page. Every AI crawler and agent is turned away the same way, so Reachable scores 0 and the rest is measured on the rendered page. Ask the host to let the AI user agents through. How to fix it
Add schema.org JSON-LD for the business (Restaurant, LocalBusiness or the closest type, with name, address, telephone and openingHoursSpecification, plus servesCuisine and acceptsReservations). It is the one block every assistant reads first; the fix kit below has it filled in. How to fix it
Agents find no link to follow on the site. If you take bookings or orders through a platform, link to it from the site so an agent can find it. Add a booking or ordering page on your own domain. How to fix it
No one is listed yet to fix this in Berlin. List your agency or yourself: free, reviewed by hand.
Builder: jimdo · Front: cloudflare · A plain fetch got challenge:attention required; a real browser got the page, so the scan continues on the rendered page.
Filled from the business's own record and this scan. Check every line before it goes live; where it goes on jimdo is in the guides.
One block in the page's head, or in the builder's custom-code slot. Replace anything that is wrong. Guide.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Restaurant",
"name": "Die Meise",
"url": "https://www.restaurant-diemeise-potsdam.de/",
"telephone": "+49 331 8872297",
"email": "hcp1@gmx.de",
"address": {
"@type": "PostalAddress",
"streetAddress": "Meisenweg 13",
"postalCode": "14478",
"addressLocality": "Potsdam",
"addressCountry": "DE"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": 52.3704568,
"longitude": 13.1006651
},
"openingHours": "Th 17:00-24:00+; Mo,Tu,We,Fr,Sa,Su \"Nur auf Vorbestellung / Reservierung\"",
"servesCuisine": [
"german"
],
"hasMenu": "https://www.restaurant-diemeise-potsdam.de/a-la-carte/"
}
</script>
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.
Rescan now · Markdown · Dispute a check
Keep watching this business: the assistants asked again every month, with what changed; 2 EUR a month or 19 EUR a year. Deep report: ten questions to each assistant and the places nearby; 5 EUR once. Reading and scanning stay free; these few euros pay for the questions sent to the assistants and for the servers.
Owners who score well embed the badge; it links back here and updates with every scan.
<a href="https://directindex.org/r/restaurant-diemeise-potsdam.de"><img src="https://directindex.org/badge/restaurant-diemeise-potsdam.de.svg" alt="Agent-Direct Score F" width="236" height="40"></a>
The direct record an agent is served for this business, the rails it could transact through, and the agent standards the site publishes.
The links an assistant is sent when it books, orders or reads the menu for this business, where each leads, and when a browser last checked it. The same record is served as JSON at /api/direct/restaurant-diemeise-potsdam.de, through the MCP tool direct_record and in the city feed /city/berlin/direct.json.
| Path | Link | Status |
|---|---|---|
| Book | none on record | |
| Order | none on record | |
| Menu | www.restaurant-diemeise-potsdam.de/a-la-carte/ html_page | from the scan |
| Hours | Th 17:00-24:00+; Mo,Tu,We,Fr,Sa,Su "Nur auf Vorbestellung / Reservierung" | from OpenStreetMap |
| Phone | +49 331 8872297 |
Stable links that count: /go/restaurant-diemeise-potsdam.de/menu answer 302 to the links above; the count is the line "followed N direct links" on this page.
Owners: claim the business below to correct this record; the claim email carries the link.
Measured, not scored: the Agent-Direct Score stays at specification v1.0. This says which rails an agent could transact through today, and what the booking or ordering vendor's terms allow.
| 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 |
Only a real browser got this page (a plain fetch got challenge:attention required); Readable and Actionable were measured on the rendered page.
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. Cloudflare's report.
| JSON-LD for the business | no |