Fix everything the independent review found

The review returned `fix` with eight findings. All eight are addressed.

Truth and SEO:
- Three articles linked to `/leistungen/lokale-seo/` and `/leistungen/astro-website/`,
  neither of which is a real slug. On a site whose pitch is "I measure what I
  sell", shipping 404s was the worst defect in the build, and nothing was
  catching internal links at all. Fixed, and `scripts/check-links.mjs` now runs
  in `npm run verify` and in the deploy: 371 references checked, none broken.
- `referenzen.astro` claimed "Ladezeit auf dem Handy unter einer Sekunde" — a
  measured result from client work, on the same page that promises no client
  metrics. Replaced with a build property.

Contract fidelity:
- The header action rendered as a transparent box with a shadow, not tape:
  `.nav a` out-specified `.tape`. Same bug class as the diagram below.
- The mechanism diagram shipped both drawings at every width — `.mech svg`
  out-specified `.mech__tall`, so the hide never applied. On a phone the
  horizontal version also hid "IHRE SEITE" and "DIE ANTWORT" behind an inner
  scroll. There is now a vertical drawing for narrow screens, and the
  per-class display rules actually win.
- The FAQ `+`/`–` glyphs were tinted orange, so the accent no longer meant
  only "the action". Back to ink.

Rhythm and craft:
- The page had one dark band a third of the way down and then six identical
  light sections. It now closes on a second dark band, so the back half has a
  destination.
- The emboss — the world's signature — was a 1px shadow, invisible at the 5.5rem
  hero size, so the focal tape read flat. The strip now has a lit top edge and a
  dark bottom edge and the letters carry a bevel that survives the scale.

Mobile:
- Five nav items plus the action wrapped to four rows in the sticky header and
  ate the first viewport. Secondary items move to the footer on small screens,
  the action takes a short label, and the bar is 68px instead of ~180px with the
  action above the fold.

Also: `PRODUCT.md` and `DESIGN.md` returned to the project root so the design
tooling finds them, and are now gitignored — on disk, out of the repo.
`impeccable concept-seed --check-seed none` returns 0, corroborating the
recorded seed.

Author: RelayStack

.github/workflows/deploy.yml

@@ -34,6 +34,10 @@ jobs:
           for f in dist/sitemap.xml dist/robots.txt dist/llms.txt; do
             test -s "$f" || { echo "missing or empty: $f"; exit 1; }
           done
+      # Three articles shipped 404s to non-existent service slugs. Nothing was
+      # checking internal links at all.
+      - name: No broken internal links
+        run: node scripts/check-links.mjs
       - uses: actions/upload-pages-artifact@v5
         with:
           path: dist

.gitignore

@@ -21,3 +21,8 @@ dist/
 # is tracked because it regenerates a published asset; these two are not.
 scripts/shoot.mjs
 scripts/measure.mjs
+
+# The product record and the design system. Kept at the project root so the
+# design tooling can find them, and deliberately not published.
+PRODUCT.md
+DESIGN.md

DEVELOPING.md

@@ -25,9 +25,14 @@ npm run dev        # http://localhost:4321
 npm run build      # -> dist/
 npm run preview    # serve the built output
 npm run check      # astro check: types, content schemas, a11y hints
-npm run verify     # check + README price sync + build, the same gates CI runs
+npm run verify     # check + README price sync + build + link check — the gates CI runs
+npm run study      # measure a domain list; see below
 ```
 
+`PRODUCT.md` and `DESIGN.md` sit at the project root so the design tooling can find them, and are
+**gitignored** — they record product truth and the visual system, and are deliberately not
+published.
+
 ## Editing the business
 
 **`src/config.ts` is the one file that matters.** Business name, the Telegram contact, the service
@@ -162,5 +167,33 @@ src/
 public/
   fonts/                 variable woff2
   og-card.png            generated; see above
-scripts/og-card.mjs      regenerates it
+scripts/
+  og-card.mjs            regenerates the share card (needs puppeteer, installed ad hoc)
+  sync-readme.mjs        splices the price table into README.md from src/config.ts
+  check-links.mjs        fails on any internal link whose target does not exist
+  visibility-study.mjs   measures a list of sites; see "The visibility study" below
+```
+
+## The visibility study
+
+`scripts/visibility-study.mjs` measures, for a list of real business websites, whether a search
+engine or an assistant can read and quote them: HTTPS, viewport, meta description, canonical,
+structured data (including LocalBusiness and FAQPage), sitemap, `llms.txt`, whether `robots.txt`
+blocks AI crawlers, and page weight.
+
+```bash
+npm run study data/domains.txt --out data/study-2026.json
 ```
+
+The input is one domain per line, optionally `domain,country,sector`. It runs sequentially,
+rate-limits itself, identifies itself in the user agent, and reads only public pages.
+
+**Two limits it will not hide, and a published study must state both:**
+
+1. **It does not measure AI mentions.** That needs model API keys and a fixed prompt set. The
+   generated summary says so explicitly, so the numbers cannot be reported as AI visibility.
+2. **It reads server-rendered HTML only.** Sites that inject JSON-LD with JavaScript are counted as
+   having none. It understates and never overstates.
+
+Nothing here is a substitute for the sample: the domain list has to be a real, defined population,
+and the study is only as honest as that list.

package.json

@@ -13,7 +13,7 @@
     "preview": "astro preview",
     "check": "astro check",
     "sync:readme": "node --experimental-strip-types scripts/sync-readme.mjs",
-    "verify": "npm run check && npm run sync:readme -- --check && npm run build",
+    "verify": "npm run check && npm run sync:readme -- --check && npm run build && node scripts/check-links.mjs",
     "study": "node scripts/visibility-study.mjs"
   },
   "dependencies": {

public/og-card.png

@@ -0,0 +1,69 @@
+/**
+ * Fails if any internal link in the built site points at a page that does not
+ * exist. Three did — two articles linked to `/leistungen/lokale-seo/` and
+ * `/leistungen/astro-website/`, neither of which is a real slug. On a site
+ * whose whole pitch is "I measure what I sell", a 404 is the worst defect in
+ * the build, and nothing was catching it.
+ *
+ *   node scripts/check-links.mjs [dist]
+ */
+import { readdir, readFile, stat } from "node:fs/promises";
+import { join, relative } from "node:path";
+
+const dist = process.argv[2] ?? "dist";
+
+async function walk(dir, out = []) {
+  for (const entry of await readdir(dir, { withFileTypes: true })) {
+    const full = join(dir, entry.name);
+    if (entry.isDirectory()) await walk(full, out);
+    else out.push(full);
+  }
+  return out;
+}
+
+const files = await walk(dist);
+const htmlFiles = files.filter((f) => f.endsWith(".html"));
+const all = new Set(files.map((f) => f.replace(dist, "")));
+
+const exists = async (path) => {
+  if (all.has(path)) return true;
+  try {
+    return (await stat(join(dist, path))).isFile();
+  } catch {
+    return false;
+  }
+};
+
+const skip = /^(https?:|\/\/|mailto:|tel:|data:|#|javascript:)/i;
+const broken = [];
+let checked = 0;
+
+for (const file of htmlFiles) {
+  const html = await readFile(file, "utf8");
+  const page = relative(dist, file);
+  for (const [, attr, url] of html.matchAll(/\b(href|src)="([^"]+)"/g)) {
+    if (skip.test(url)) continue;
+    const path = url.split("#")[0].split("?")[0];
+    if (!path) continue;
+    checked++;
+
+    const candidates = path.endsWith("/")
+      ? [`${path}index.html`]
+      : /\.[a-z0-9]{2,5}$/i.test(path)
+        ? [path]
+        : [`${path}/index.html`, `${path}.html`];
+
+    if (!(await Promise.all(candidates.map(exists))).some(Boolean)) {
+      broken.push({ page, attr, url });
+    }
+  }
+}
+
+if (broken.length > 0) {
+  console.error(`\n${broken.length} broken internal reference(s) in ${htmlFiles.length} page(s):\n`);
+  for (const b of broken) console.error(`  ${b.page}\n    ${b.attr}="${b.url}"`);
+  console.error("");
+  process.exit(1);
+}
+
+console.log(`Checked ${checked} internal references across ${htmlFiles.length} pages — none broken.`);

scripts/check-links.mjs

@@ -3,40 +3,42 @@
  * The mechanism, drawn. A schematic rather than a photograph: it explains how a
  * question becomes an answer, which is the whole product. Pure geometry in the
  * world's own palette — no invented data, nothing that pretends to be a chart.
+ *
+ * Two drawings, not one that scrolls: on a phone the horizontal flow hid both
+ * payload nodes ("IHRE SEITE", "DIE ANTWORT") behind an inner horizontal scroll.
+ * The narrow version stacks the same four steps vertically and keeps the last
+ * line, in that order, on screen.
  */
+const label = "Eine Frage erreicht Google oder einen KI-Assistenten. Beide lesen, was maschinenlesbar auf der Seite steht: Sitemap, strukturierte Daten und zitierfähige Absätze. Daraus entsteht die Antwort.";
 ---
 <div class="mech">
   <svg
+    class="mech__wide"
     viewBox="0 0 1160 400"
     role="img"
-    aria-label="Eine Frage erreicht Google oder einen KI-Assistenten. Beide lesen, was maschinenlesbar auf der Seite steht: Sitemap, strukturierte Daten und zitierfähige Absätze. Daraus entsteht die Antwort."
+    aria-label={label}
     font-family="Archivo Narrow, Archivo, sans-serif"
   >
     <defs>
-      <marker id="mech-arrow" viewBox="0 0 10 10" refX="9" refY="5"
-              markerWidth="7" markerHeight="7" orient="auto-start-reverse">
+      <marker id="ma" viewBox="0 0 10 10" refX="9" refY="5" markerWidth="7" markerHeight="7" orient="auto-start-reverse">
         <path d="M0 0 L10 5 L0 10 z" fill="#1b1b1e"/>
       </marker>
     </defs>
 
-    <!-- the question -->
     <rect x="8" y="150" width="196" height="76" fill="none" stroke="#1b1b1e" stroke-width="2"/>
     <text x="106" y="196" text-anchor="middle" font-size="26" font-weight="700" fill="#16181c" letter-spacing="1">DIE FRAGE</text>
     <text x="106" y="252" text-anchor="middle" font-size="19" fill="#5a5750">„Wer macht das bei mir?“</text>
 
-    <line x1="212" y1="188" x2="288" y2="188" stroke="#1b1b1e" stroke-width="2" marker-end="url(#mech-arrow)"/>
+    <line x1="212" y1="188" x2="288" y2="188" stroke="#1b1b1e" stroke-width="2" marker-end="url(#ma)"/>
 
-    <!-- the two readers -->
     <rect x="296" y="96" width="232" height="60" fill="#1b1b1e"/>
     <text x="412" y="134" text-anchor="middle" font-size="24" font-weight="700" fill="#f5f4f0" letter-spacing="1.4">GOOGLE</text>
-
     <rect x="296" y="222" width="232" height="60" fill="#1b1b1e"/>
     <text x="412" y="260" text-anchor="middle" font-size="24" font-weight="700" fill="#f5f4f0" letter-spacing="1.4">KI-ASSISTENT</text>
 
-    <line x1="536" y1="126" x2="608" y2="176" stroke="#1b1b1e" stroke-width="2" marker-end="url(#mech-arrow)"/>
-    <line x1="536" y1="252" x2="608" y2="202" stroke="#1b1b1e" stroke-width="2" marker-end="url(#mech-arrow)"/>
+    <line x1="536" y1="126" x2="608" y2="176" stroke="#1b1b1e" stroke-width="2" marker-end="url(#ma)"/>
+    <line x1="536" y1="252" x2="608" y2="202" stroke="#1b1b1e" stroke-width="2" marker-end="url(#ma)"/>
 
-    <!-- what both of them can read -->
     <rect x="616" y="84" width="238" height="210" fill="#dedbd4" stroke="#1b1b1e" stroke-width="2"/>
     <text x="735" y="120" text-anchor="middle" font-size="19" font-weight="700" fill="#16181c" letter-spacing="1.6">IHRE SEITE</text>
     <line x1="636" y1="136" x2="834" y2="136" stroke="#1b1b1e" stroke-width="1"/>
@@ -46,25 +48,70 @@
       <text x="640" y="252">· zitierfähige Absätze</text>
     </g>
 
-    <line x1="862" y1="188" x2="930" y2="188" stroke="#1b1b1e" stroke-width="2" marker-end="url(#mech-arrow)"/>
+    <line x1="862" y1="188" x2="930" y2="188" stroke="#1b1b1e" stroke-width="2" marker-end="url(#ma)"/>
 
-    <!-- the answer -->
     <rect x="938" y="150" width="214" height="76" fill="#e2542a"/>
     <text x="1045" y="196" text-anchor="middle" font-size="26" font-weight="700" fill="#1b1b1e" letter-spacing="1">DIE ANTWORT</text>
     <text x="1045" y="256" text-anchor="middle" font-size="19" fill="#5a5750">genannt, oder nicht</text>
 
-    <!-- the part nobody can skip -->
     <line x1="8" y1="330" x2="1152" y2="330" stroke="#cfccc4" stroke-width="1"/>
-    <text x="8" y="364" font-size="19" fill="#5a5750">
-      Ohne Indexierung gibt es nichts zu zitieren: erst gefunden, dann genannt.
-    </text>
+    <text x="8" y="364" font-size="19" fill="#5a5750">Ohne Indexierung gibt es nichts zu zitieren: erst gefunden, dann genannt.</text>
+  </svg>
+
+  <svg
+    class="mech__tall"
+    viewBox="0 0 420 660"
+    role="img"
+    aria-label={label}
+    font-family="Archivo Narrow, Archivo, sans-serif"
+  >
+    <defs>
+      <marker id="mb" viewBox="0 0 10 10" refX="9" refY="5" markerWidth="7" markerHeight="7" orient="auto-start-reverse">
+        <path d="M0 0 L10 5 L0 10 z" fill="#1b1b1e"/>
+      </marker>
+    </defs>
+
+    <rect x="86" y="14" width="248" height="58" fill="none" stroke="#1b1b1e" stroke-width="2"/>
+    <text x="210" y="52" text-anchor="middle" font-size="24" font-weight="700" fill="#16181c" letter-spacing="1">DIE FRAGE</text>
+    <text x="210" y="96" text-anchor="middle" font-size="17" fill="#5a5750">„Wer macht das bei mir?“</text>
+
+    <line x1="210" y1="110" x2="210" y2="140" stroke="#1b1b1e" stroke-width="2" marker-end="url(#mb)"/>
+
+    <rect x="70" y="146" width="280" height="52" fill="#1b1b1e"/>
+    <text x="210" y="180" text-anchor="middle" font-size="23" font-weight="700" fill="#f5f4f0" letter-spacing="1.4">GOOGLE</text>
+    <rect x="70" y="210" width="280" height="52" fill="#1b1b1e"/>
+    <text x="210" y="244" text-anchor="middle" font-size="23" font-weight="700" fill="#f5f4f0" letter-spacing="1.4">KI-ASSISTENT</text>
+
+    <line x1="210" y1="270" x2="210" y2="300" stroke="#1b1b1e" stroke-width="2" marker-end="url(#mb)"/>
+
+    <rect x="46" y="306" width="328" height="182" fill="#dedbd4" stroke="#1b1b1e" stroke-width="2"/>
+    <text x="210" y="342" text-anchor="middle" font-size="18" font-weight="700" fill="#16181c" letter-spacing="1.6">IHRE SEITE</text>
+    <line x1="68" y1="358" x2="352" y2="358" stroke="#1b1b1e" stroke-width="1"/>
+    <g font-size="18" fill="#3c3f45">
+      <text x="72" y="394">· Sitemap</text>
+      <text x="72" y="428">· strukturierte Daten</text>
+      <text x="72" y="462">· zitierfähige Absätze</text>
+    </g>
+
+    <line x1="210" y1="496" x2="210" y2="526" stroke="#1b1b1e" stroke-width="2" marker-end="url(#mb)"/>
+
+    <rect x="86" y="532" width="248" height="58" fill="#e2542a"/>
+    <text x="210" y="570" text-anchor="middle" font-size="24" font-weight="700" fill="#1b1b1e" letter-spacing="1">DIE ANTWORT</text>
+
+    <line x1="0" y1="606" x2="420" y2="606" stroke="#cfccc4" stroke-width="1"/>
+    <text x="0" y="632" font-size="14" fill="#5a5750">Ohne Indexierung gibt es nichts zu zitieren.</text>
+    <text x="0" y="652" font-size="14" fill="#5a5750">Erst gefunden, dann genannt.</text>
   </svg>
 </div>
 
 <style>
-  .mech svg { width: 100%; height: auto; display: block; }
+  .mech svg { width: 100%; height: auto; }
+  /* Set per class, not on `.mech svg` — that selector out-specifies both
+     classes and would show both drawings at every width. */
+  .mech__wide { display: block; }
+  .mech__tall { display: none; }
   @media (max-width: 52rem) {
-    .mech svg { min-width: 640px; }
-    .mech { overflow-x: auto; }
+    .mech__wide { display: none; }
+    .mech__tall { display: block; }
   }
 </style>

src/components/Mechanism.astro

@@ -86,4 +86,4 @@ Nein. Google nennt das „Keyword Stuffing“ und kann das Profil sperren. Der N
 
 ---
 
-*Passende Leistung: [Lokale SEO](/leistungen/lokale-seo/) — Profil, Website und Verzeichnisse auf einen Stand bringen.*
+*Passende Leistung: [Lokale SEO](/leistungen/lokale-sichtbarkeit/) — Profil, Website und Verzeichnisse auf einen Stand bringen.*

src/content/wissen/google-unternehmensprofil-pflichtangaben.md

@@ -103,4 +103,4 @@ Ja — Antworten erhöhen die Sichtbarkeit des Profils und sind das, was neue Ku
 
 ---
 
-*Passende Leistung: [Lokale SEO](/leistungen/lokale-seo/) — Unternehmensprofil, Bewertungsprozess und Website-Angaben auf einen Stand bringen.*
+*Passende Leistung: [Lokale SEO](/leistungen/lokale-sichtbarkeit/) — Unternehmensprofil, Bewertungsprozess und Website-Angaben auf einen Stand bringen.*

src/content/wissen/mehr-google-bewertungen-bekommen.md

@@ -86,4 +86,4 @@ Ja. Ihr Google-Unternehmensprofil und Ihre Social-Profile sind fremde Plattforme
 
 ---
 
-*Passende Leistung: [Website erstellen lassen](/leistungen/astro-website/) — Festpreis, ohne laufende Plugin-Kosten. Oder sehen Sie sich die [Preise](/preise/) an.*
+*Passende Leistung: [Website erstellen lassen](/leistungen/website/) — Festpreis, ohne laufende Plugin-Kosten. Oder sehen Sie sich die [Preise](/preise/) an.*