yelp.de
yelp.de is largely invisible to agents.
AI assistants cannot open the website of yelp.de, so they rely on what other sites say about it.
See what an AI agent reads on this site →
8 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.
What assistants answer
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.
How yelp.de compares
What to fix first
- The site turns every visitor without a browser away, AI agents included +15 points
A plain fetch was refused (challenge:datadome); 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
- No booking or ordering link on the website +15 points
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
- Structured data is incomplete +7 points
Missing: address, telephone, opening hours. How to fix it
- No menu or price list found +7 points
Agents answer 'what do they offer' from marketplaces instead. Add a menu or price list page and link it from the homepage. How to fix it
- robots.txt blocks GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, Claude-User, Perplexity-User no points, still 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
Already right
- Structured data present (Organization) but without address, phone or hours
Builder: unknown · Front: cloudflare · A plain fetch got challenge:datadome; a real browser got the page, so the scan continues on the rendered page.
What to paste
Filled from the business's own record and this scan. Check every line before it goes live; where it goes on your builder is in the guides.
Show the code to paste
Structured data (JSON-LD)
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": "Organization",
"name": "Yelp",
"url": "https://www.restaurant-kritik.de/99085"
}
</script>
robots.txt
Add these lines to /robots.txt and delete any Disallow rule that names these crawlers. Guide.
# 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: /
Own this business?
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
Show the score
Owners who score well embed the badge; it links back here and updates with every scan.
<a href="https://directindex.org/r/yelp.de"><img src="https://directindex.org/badge/yelp.de.svg" alt="Agent-Direct Score F" width="236" height="40"></a>
What agents get, and what the site publishes
The direct record an agent is served for this business, the rails it could transact through, and the agent standards the site publishes.
Show the details
What agents get for Yelp
No direct path on record: the scan of 2026-10-15 found no booking or ordering link on yelp.de or on a vendor's site. The same record is served as JSON at /api/direct/yelp.de, through the MCP tool direct_record.
| Path | Link | Status |
|---|---|---|
| Book | none on record | |
| Order | none on record | |
| Menu | none on record | |
| Hours | none on record | |
| Phone | none on record |
Owners: claim the business below to correct this record; the claim email carries the link.
Can an agent transact?
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:datadome); Readable and Actionable were measured on the rendered page.
Not measured
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 | yes |