Curry Station

What to fix first

1. The site turns every visitor without a browser away, AI agents included +25 points

   A plain fetch was refused (http_503); 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

2. No structured data for the business +15 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). It is the one block every assistant reads first; the fix kit below has it filled in. How to fix it

3. Ordering through an unrecognised third party +9 points

   Check that the provider keeps you as the merchant of record. How to fix it

4. 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

No one is listed yet to fix this in Berlin. List your agency or yourself: free, reviewed by hand.

Already right

• robots.txt lets AI crawlers in No rule blocks the key AI user agents.

Builder: wordpress · Front: cloudflare · A plain fetch got http_503; 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 wordpress is in the guides.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Curry Station",
  "url": "http://www.curry-station.com",
  "telephone": "+494915143132091",
  "address": "Teltower Damm 35, 14169, Berlin",
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": 52.431645,
    "longitude": 13.259593
  }
}
</script>