Methodology · Four Pillars for Global Topic Authority

How the ChinaYung Allergen Pipeline
Builds Global Topic Authority

BLS data foundation · EU-14 mapping · Schema.org FAQPage · LLM optimization — and how these four pillars cumulate into worldwide visibility across 39 countries (300+ hits, 5 verified top-7 queries).

My name is Chikei Yung. I built the ChinaYung allergen pipeline because I needed it for my own restaurant, China Restaurant YUNG in Frankfurt, and because nothing on the market combined the four things I needed in one place: a BLS-backed nutrition basis, a clean EU-14 allergen mapping, Schema.org FAQPage output, and LLM-readable answer surfaces.

This page is the methodology document. If you want to see the result first — over 300 Google Pos-1 queries worldwide, visibility in 39 countries — read the case study from China Restaurant YUNG Frankfurt. If you want to understand reproducibly why the pipeline produces that level of authority on cuisine and allergen queries, this is the page to read. I keep the language plain and concrete. Method, not magic.

The Four Pillars

Each pillar is independently solid. The combination is what produces ranking outcomes that single-purpose tools do not.

01

BLS Data Foundation

The Bundeslebensmittelschlüssel (BLS) is the German Federal Food Code, maintained by the Max Rubner-Institut. It is the reference dataset for nutrition data and ingredient-level allergen mapping in German-speaking food regulation.

For each ingredient in your recipe database, the pipeline maps to a BLS entry. From that mapping you get a deterministic 14-flag allergen profile and a complete nutrition profile (energy, fat, saturated fat, carbohydrates, sugars, protein, salt, key micronutrients). A BLS license is required for commercial use — your restaurant procures it, the software provides the integration.

Authority gain: citable source
BLS Bundeslebensmittel­schlüssel

Official reference of the Max Rubner-Institut — mandatory base for every allergen derivation in the pipeline

ChinaYung software: dish detail Dim Sum Orange Cauliflower with automatically calculated EU-14 allergen matrix (14 categories as checkbox grid) plus health-benefits box with BLS source citation per Greger

Live backend: EU-14 allergen matrix is calculated automatically from BLS-mapped ingredients, edge cases as separate cell status

02

EU-14 Mapping

EU regulation 1169/2011 defines 14 allergen groups that must be declared on every menu in the European Union: gluten, crustaceans, eggs, fish, peanuts, soybeans, milk and lactose, nuts, celery, mustard, sesame, sulphur dioxide and sulphites, lupin, molluscs.

The pipeline computes the 14-flag matrix at three levels: ingredient, dish, menu category. Each level is queryable, exportable and auditable. When a guest with a peanut allergy asks „which of your dishes contain peanuts?“, the answer is a database query, not a kitchen consultation. Edge cases like „contains traces“, „may contain traces from shared facility“, „available without ingredient X on request“ are separate status per cell, not footnotes.

Authority gain: long-tail reach
03

Schema.org FAQPage

Every Q&A block on the published pages is also embedded as FAQPage JSON-LD in the page head. Google reads the JSON-LD and frequently shows the answers as rich results, expandable accordions or „people also ask“ entries.

What Schema.org delivers:

  • Google reads the question-answer structure directly and can show rich results
  • LLM crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended) extract answers as citable facts
  • Voice assistants and smart speakers use FAQPage markup as preferred answer source

The HTML and the JSON-LD share one source — the database — so they cannot drift. Schema is generated automatically; you do not write it by hand.

Authority gain: machine-readability
ChinaYung software bot-manager backend: FAQ editor with trilingual triggers (German / English / 中文) for opening hours and address — automatically embedded as FAQPage schema

FAQ editor with trilingual triggers (DE·EN·中文) — every FAQ is automatically embedded as FAQPage schema

llms.txt + FAQPage + Facts Page

Belt-and-suspenders setup: /llms.txt as crawl hint + frontend-visible LLM facts page with FAQPage schema and Speakable selectors

04

LLM Optimization

The pipeline maintains a /llms.txt endpoint listing the canonical answer URLs and produces dense, factual long-form FAQ pages that LLM crawlers index and cite. The pages use the <details><summary> pattern so the answer is structurally clear to both humans and parsers.

ChatGPT, Perplexity, Gemini and Claude treat well-formed FAQ pages with consistent Schema as authoritative sources for narrow factual queries. Allergen, gluten and cuisine questions are exactly that type of query. Which LLM prefers which mechanism shifts regularly — the dual setup keeps the position robust.

Authority gain: distribution beyond Google

Why Worldwide Visibility (300+ Hits, 5 Verified Top-7) Is Not Luck

Each pillar individually is a standard best-practice. The multiplier effect comes from their combination and consistency across the entire section.

1
Per-page completenessEach FAQ page covers 10–20 distinct guest questions. A typical competitor page covers 1–3.
2
Per-topic consistencySchema, wording, cross-link structure are uniform. Google’s helpful-content systems read consistency as a domain-level quality signal.
3
Cross-topic transferOnce Google trusts chinayung.de for Peking Duck, the same trust transfers to dim sum, hoisin, dumplings, har gao.
4
Pipeline operationalizes all threeThat is why the result is reproducible and not a Frankfurt accident.
Result: A Frankfurt restaurant page ranks for „peking duck baltimore“ because Google, evaluating the global authority landscape for „Peking Duck × allergens × structured answers“, finds no better candidate. Wikipedia has no per-variant allergen entry. Eater has no FAQPage schema depth. Restaurants in Baltimore have no machine-readable allergen data. We fill the gap — and Google confirms it with Pos 1.

What the ChinaYung Software Automates

Eight modules that together make the four pillars maintainable — without you ever editing JSON-LD or XML sitemaps.

Menu editor with allergen-aware ingredients, variant management and version history
Allergen matrix calculation automatically from BLS-mapped ingredients
FAQ generator producing thematic Q&A clusters from the matrix
Schema auto-injection for FAQPage, Restaurant, Menu, Person, Organization
Sitemap maintenance with automatic regeneration on page changes
IndexNow push to Bing and Yandex on every publish event
llms.txt generator with curated page list
LLM facts page generator as frontend-visible pilot pattern
ChinaYung software menu editor: categories Peking Duck / Dim Sums Poultry / Vegan Dim Sums with dishes, status badges (Draft/OK/Onboarding open), prices and visibility control

Menu editor — backend overview with status tracking per dish

ChinaYung live frontend chinayung.de: menu advisor on the right with filter buttons Gluten-free, Dairy-free, Nut-free, Shellfish-free, Vegetarian — answers 'Which dishes are gluten-free?' with live link 'Chao Fan Garnelen'

Live frontend chinayung.de — menu advisor with allergen filter and live answer

Module details on the product page.

What You Need to Do Yourself

Three things require your involvement, and they are not negotiable, because they are the reasons the output is trustworthy.

Prerequisite 01

Procure and verify the BLS license

BLS is licensed by the Max Rubner-Institut. Your restaurant signs the license. The software supports the integration but does not provide the data.

Prerequisite 02

Enter your menu correctly

Recipes must reflect what is actually served. If your kitchen quietly substitutes oyster sauce in a „vegan“ dish, no software will catch that — the data has to be honest at the source. Plan for one focused day of menu data entry per location at onboarding.

Prerequisite 03

Periodic re-audit

Recipes drift. Suppliers change. New dishes get added. A quarterly review of the allergen matrix against actual kitchen practice is the minimum cadence I recommend, and the software produces a printable diff report to make that review fast.

30-Minute Walk-Through — on a Real Menu

A 30-minute live demo is usually enough to see the pipeline end to end on a real menu — your menu, if you bring it. I do the demo myself.