Hospitality Customer Story
A conversation with Johannes Rupp — Managing Partner & Host, Schwitzer's Hotel am Park
Industry | Hospitality — 4-star superior hotel, Michelin-starred fine dining |
Company size | ~100 employees (incl. 30 apprentices); single property with 4 restaurants |
Headquarters | Waldbronn, Northern Black Forest (Albtal), Baden-Württemberg, Germany |
Website | schwitzers.com |
Founded / ownership | Family-owned; Johannes Rupp took over leadership in 2014 |
Notable | Michelin-starred Restaurant Schwitzer's; Brasserie holds a Bib Gourmand (2019); adjacent to and integrated with Albtherme Waldbronn spa |
Plan | Discovery+ (€299/month) — full technical implementation tier, not just monitoring |
Relationship | Signed, live, paying customer — introduced via Blütezeit (their marketing/web agency); Bluerails' flagship marketing reference by mutual agreement |
Key features used | Agent Identity, Agent Readability (llms.txt, agent-permissioned robots.txt, sitemap.xml), Discovery Score scan |
Schwitzer's is one of the most decorated independent hotels in Baden-Württemberg — four-star superior, a Michelin star at Restaurant Schwitzer's, a Bib Gourmand at the Brasserie, five-star Google reviews, and a deep, well-maintained WordPress site with dozens of pages covering rooms, arrangements, dining and the adjoining Albtherme spa. Johannes Rupp himself sits on the DEHOGA Baden-Württemberg (Karlsruhe chapter) and FHG e.V. boards — exactly the kind of property that should be a first result when an AI agent is asked for “best hotel near the Black Forest” or “Michelin restaurant Baden-Württemberg.”
But, like almost every independent hotel, none of that reputation had been translated into a machine-readable form. There was no llms.txt, no explicit policy welcoming AI/answer-engine crawlers (the default is that they're not addressed at all, which agents often treat as a soft no), and no structured signal connecting Schwitzer's rich content — rooms, arrangements, restaurants, spa access — to the way agents actually retrieve and cite information. Every booking that instead routed through an OTA meant 15–25% in commission on a guest who may well have searched for Schwitzer's by name.
Schwitzer's became a signed, paying Discovery+ customer on 8 July 2026. Bluerails was given direct WordPress admin access (schwitzers.com) and WooCommerce admin access (shop.schwitzers.com, for the gift-voucher/ice-cream shop) and shipped the technical remediation the same day:
llms.txt implementation — live and verified: a structured file (served via the Rank Math SEO plugin) enumerating ~50 pages — hotel overview, all room types, all four restaurants, arrangements, spa/wellness, activities — each with a clear description for LLMs to parse, plus a pointer to the XML sitemap
Agent-permissioned robots.txt — live and verified: explicit Allow: / rules for OpenAI (OAI-SearchBot, ChatGPT-User, GPTBot), Anthropic (Claude-SearchBot, Claude-User, ClaudeBot, anthropic-ai), Perplexity (PerplexityBot, Perplexity-User), Google (Google-Extended) and Common Crawl (CCBot) — annotated inline as “AI search & answer-engine crawlers — explicitly welcomed (Bluerails)”
Sitemap.xml — referenced and current
Schema.org / JSON-LD structured data — per Bluerails' standard Discovery+ implementation playbook (Hotel/Organization + FAQ JSON-LD); not independently re-verified in this draft, flag to confirm on next scan
This is the Visibility layer (Agent Identity + Agent Readability) live end-to-end. Booking still runs through Schwitzer's existing engine — Action/Settlement wasn't in scope here.
Agent-Readiness Score: [PLACEHOLDER — baseline] → [PLACEHOLDER — post-implementation] (Ashwin to pull from Discovery scan history)
Agent traffic to schwitzers.com: [PLACEHOLDER — %/absolute change since 8 July]
Direct bookings / inquiries: [PLACEHOLDER — %/absolute change] — the cherry on top once attributable
Time to live: same-day technical remediation, live 8 July 2026
Schwitzer's Hotel am Park has spent a decade building a reputation most independent hotels would envy: a four-star superior property directly on the Kurpark in Waldbronn, home to the Michelin-starred Restaurant Schwitzer's alongside three further dining concepts (PUR, Brasserie — Bib Gourmand 2019 — and a Bistro inside the neighbouring Albtherme spa), a full wellness offering, and a team of around 100 across a wide range of nationalities, including 30 apprentices. Johannes Rupp, who took over the family business in 2014, has grown it with what the team calls “the courage to explore new ideas” — he sits on the board of DEHOGA Baden-Württemberg's Karlsruhe chapter and of FHG e.V., and is known for spotting trends early.
Despite that pedigree, Schwitzer's faced the same structural gap as every independent hotel: its site was built for guests and search engines, not for the AI agents now doing a growing share of travel research and shopping. No llms.txt, no explicit invitation to AI crawlers in robots.txt, and no clean, agent-parseable description of its four restaurants, its room types or its Albtherme partnership. For a hotel this decorated, that gap matters more than most — the brand equity was there; the machine-readable layer to carry it into agent answers wasn't.
Soon after our first interaction with Schwitzer's, the commercial relationship closed and the technical work shipped immediately — WordPress and WooCommerce access handed over the same day, remediation live shortly after.
An in person meeting between Bluerails and Johannes Rupp further strengthened the symbiotic relationship and the miles to be covered together, wherein Johannes acknowledged the value visible already.
Getting found and read by agents. With llms.txt and an explicitly agent-permissioned robots.txt in place, the eleven major AI/answer-engine crawlers Bluerails targets (OpenAI, Anthropic, Perplexity, Google, Common Crawl) now have both permission and a structured map to Schwitzer's rooms, restaurants, arrangements and spa access — rather than having to infer it from page copy, or not crawling it at all.
A single technical partner instead of hand-rolled fixes. Rather than Schwitzer's or Blütezeit having to research and implement agent-readability standards themselves, Bluerails shipped the full llms.txt + robots.txt + sitemap package directly against their WordPress stack in a same-day turnaround.
A relationship that compounds. Beyond the technical scan, Schwitzer's becoming Bluerails' named reference customer is unlocking a DEHOGA Baden-Württemberg relationship — a channel into the wider DACH independent-hotel long tail.
Score movement — baseline and post-implementation Agent-Readiness Score. [PLACEHOLDER]
Agent traffic — change in AI-agent/crawler visits to schwitzers.com since 8 July. [PLACEHOLDER]
Direct bookings/inquiries — change in direct booking volume vs. OTA-routed bookings. [PLACEHOLDER]
“[Placeholder quote from Johannes Rupp on working with Bluerails — to be collected on a follow-up call; he met the team in person on 13 July 2026 and immediately committed to being the flagship reference.]”
— Johannes Rupp, Managing Partner & Host, Schwitzer's Hotel am Park