dynamisch barcode

feat: implement pricing strategy, subscription tiers, and core infrastructure for QR code management
aufräumen
2026-04-14 19:46:14 +02:00 · 2026-04-14 19:34:47 +02:00 · 2026-04-14 11:21:17 +02:00 · 2026-04-14 10:35:29 +02:00 · 2026-04-14 10:29:47 +02:00 · 2026-04-12 23:41:33 +02:00
595 changed files with 79228 additions and 24696 deletions
--- a/..md
+++ b/..md
--- a/.agents/pricing-strategy.md
+++ b/.agents/pricing-strategy.md
@@ -0,0 +1,234 @@
+# QR Master — Pricing Strategy
+*Erstellt: April 2026 | Basiert auf Marktforschung, Competitor-Scraping & SaaS-Benchmarks*
+
+---
+
+## 1. Marktkontext
+
+### QR-Code-Markt 2025/2026
+| Metrik | Wert |
+|--------|------|
+| Globale Marktgröße | $15,3 Mrd. (2025) |
+| CAGR bis 2030 | 16,1% |
+| US-Smartphone-User die QR scannen | 100+ Mio. monatlich |
+| Business-Adoption | 50% der Unternehmen nutzen QR-Codes aktiv |
+
+**Fazit:** Wachstumsmarkt mit noch großem Potenzial, besonders im KMU-Segment.
+
+---
+
+## 2. Wettbewerbs-Pricing-Map
+
+### Vollständige Marktübersicht (aus Firecrawl-Recherche)
+
+| Tool | Preis/Monat | Analytics | Dynamic | Bulk | Branding | Positionierung |
+|------|------------|-----------|---------|------|----------|----------------|
+| TQRCG | $5 | ✅ | ✅ | ❌ | ✅ | Value-Leader |
+| QRStuff | $5 | ❌ | ❌ | ✅ | ❌ | Budget |
+| ViralQR | $1,49 | ✅ | ✅ | ❌ | ✅ | Ultra-Budget |
+| Beaconstac | $5–24 | ✅ | ✅ | ✅ | ✅ | SMB–Enterprise |
+| Bitly QR | $10 | ✅ | ✅ | ❌ | ✅ | Mid-Market |
+| Unitag | $10 | ❌ | ✅ | ✅ | ✅ | Mid-Market |
+| ZebraQR | $9 | ✅ | ✅ | ❌ | ✅ | Hospitality-Nische |
+| QR Tiger | $12–15 | ✅ | ✅ | ✅ | ✅ | Mid-Market+ |
+| Hovercode | $15 | ✅ | ✅ | ✅ | ✅ | Growth-Fokus |
+| Flowcode | $10–15 | ✅ | ✅ | ❌ | ✅ | Design-Fokus |
+| Scanova | $20 | ✅ | ✅ | ✅ | ✅ | Premium |
+| QR Code Chimp | $20 | ✅ | ✅ | ✅ | ✅ | Premium-Design |
+| Uniqode | $10–30 | ✅ | ✅ | ✅ | ✅ | Enterprise |
+| QRFY | $25 | ✅ | ✅ | ✅ | ✅ | Premium-Flat |
+| QR Code Generator Pro | $15–29 | ✅ | ✅ | ✅ | ✅ | Agency |
+
+### Marktlücke für QR Master
+> **Kein einziges Tool unter $12 bietet Analytics + Bulk + Custom Branding + DSGVO gleichzeitig.**
+> Das ist exakt QR Masters Sweet Spot.
+
+---
+
+## 3. SaaS-Benchmark-Daten (Industrie)
+
+| Metrik | Benchmark | Quelle |
+|--------|-----------|--------|
+| Median Entry-Level Preis (SaaS) | $29/mo | Monetizely 2025 |
+| Free-to-Paid Conversion | ~5% | RevenueCat 2026 |
+| Anteil Jahres-Abos (vs. Monatlich) | 68% annual / 32% monthly | RevenueCat 2026 |
+| ARPU (Subscription Apps) | ~$30 | RevenueCat 2026 |
+| Freemium-Anteil unter SaaS | 38% der Unternehmen | Monetizely 2025 |
+| Hybrid-Pricing-Adoption | 61% | Monetizely 2025 |
+| SaaS Churn (SMB) | 3–5%/Monat | Benchmark |
+
+**Key Insight:** 68% der Subscriber wählen Jahrestarife. Das ist der wichtigste Hebel für Cashflow und Churn-Reduktion.
+
+---
+
+## 4. Value Metric Empfehlung
+
+### Aktuelles Modell: Anzahl dynamischer QR-Codes
+**Bewertung: Gut, aber optimierbar.**
+
+Die Anzahl dynamischer Codes skaliert mit dem wahrgenommenen Wert (mehr Codes = mehr Kampagnen = mehr Wert). Jedoch:
+- Limit von 8 FREE / 50 PRO / 500 BUSINESS ist nicht intuitiv kommuniziert
+- Kunden denken in "Projekten" oder "Kampagnen", nicht in "Codes"
+
+### Empfehlung: Hybrid-Metric einführen
+Primär-Metric behalten (Dynamic Codes), aber mit Sekundär-Metriken ergänzen:
+
+| Tier | Primär-Metric | Sekundär-Metriken |
+|------|--------------|-------------------|
+| FREE | 8 Dynamic Codes | 1 User, Basic Analytics, 30 Tage History |
+| PRO | 50 Dynamic Codes | 1–3 User, Full Analytics, 1 Jahr History, Custom Domain |
+| BUSINESS | 500 Dynamic Codes | Unlimitierte User, Advanced Analytics, Bulk, API |
+
+---
+
+## 5. Empfohlene Pricing-Struktur
+
+### Tier-Empfehlung (Monatlich / Jährlich)
+
+#### FREE — Kostenlos, für immer
+- **8 dynamische QR-Codes** (klar kommuniziert als "8 Kampagnen")
+- Unlimitierte statische Codes
+- Basis-Analytics (Scans, Datum)
+- QR Master Branding (nicht entfernbar)
+- **Ziel:** Acquisition, Habit-Building, Virality durch Branding
+
+#### PRO — €9/Monat (monatlich) | **€7/Monat (jährlich = €84/Jahr)**
+*Empfohlen für: Restaurants, lokale Unternehmen, Marketing-Einsteiger*
+- **50 dynamische QR-Codes**
+- Custom Branding (kein QR Master Logo)
+- Vollständige Analytics (Device, Location, OS, UTM)
+- 1 Jahr Analytics-History
+- Custom Domain für Redirects
+- Prioritäts-Support
+- **Rationale:** $7–9 liegt im bewiesenen Sweet Spot ($5–$10) für diese Zielgruppe. Beaconstac Starter bei $5 hat nur 100 Scans — wir haben keine Scan-Limits.
+
+#### BUSINESS — €24/Monat (monatlich) | **€19/Monat (jährlich = €228/Jahr)**
+*Empfohlen für: Agenturen, Retail-Chains, Event-Organisatoren*
+- **500 dynamische QR-Codes**
+- Bulk-Upload (Excel/CSV bis 1.000 Zeilen)
+- API-Zugriff
+- Team-Management (bis 5 User)
+- Erweiterte Analytics + Export (CSV, PDF)
+- White-Label Option
+- DSGVO-Compliance-Report
+- **Rationale:** $19–24 ist der Bereich wo Scanova ($20), Hovercode ($15) und QR Code Chimp ($20) spielen — aber keiner hat DSGVO + Bulk + Analytics zusammen.
+
+#### ENTERPRISE — Auf Anfrage (ab €99/Monat)
+*Für: Corporations, Franchise-Ketten*
+- Unlimitierte Codes
+- Dedizierter Account Manager
+- Custom SLA
+- SSO / SAML
+- On-Premise Option (optional)
+
+---
+
+## 6. Psychologische Preisgestaltung
+
+### Anchoring-Strategie
+Reihenfolge auf Pricing-Page: **BUSINESS → PRO → FREE** (von teuer nach günstig)
+→ PRO wirkt dadurch als "vernünftiger Kompromiss"
+
+### Decoy-Effekt
+PRO muss der offensichtliche "Best Deal" sein:
+- BUSINESS ist 2,7× teurer als PRO aber hat 10× mehr Codes → Nur für Power-User
+- FREE hat 6× weniger Codes als PRO → Upgrade liegt nahe
+
+### Jahres-Pricing-Push
+- Monatlich: €9 / €24
+- Jährlich: €7 / €19 (sparst 22% / 21%)
+- **Wichtig:** Jahrespreis prominent anzeigen mit "Spare 2 Monate" statt Prozent
+- Default-Toggle: **Jährlich** (da 68% aller Subscriber Jahrestarife wählen)
+
+### Charm vs. Round Pricing
+- PRO: **€9** (nicht €10) → Charm Pricing für Conversion
+- BUSINESS: **€24** (nicht €25) → Knapp unter psychologischer Grenze
+- Jahrestarife: **€84/Jahr** und **€228/Jahr** (rund → Premium-Signal)
+
+---
+
+## 7. Jahres-Discount-Strategie
+
+| Tier | Monatlich | Jährlich | Ersparnis |
+|------|-----------|----------|-----------|
+| PRO | €9/Mo | €84/Jahr (€7/Mo) | 22% / 2 Monate gratis |
+| BUSINESS | €24/Mo | €228/Jahr (€19/Mo) | 21% / 2,5 Monate gratis |
+
+**Kommunikation:** "2 Monate kostenlos bei jährlicher Zahlung" schlägt "20% Rabatt" in A/B-Tests regelmäßig.
+
+---
+
+## 8. Free-Tier-Optimierung
+
+### Ziel des Free-Tiers
+Nicht monetarisieren — **qualifizieren und konvertieren**.
+
+### Empfohlene Trigger für Upgrade-Prompts
+1. **Code-Limit erreicht** → "Du hast 8/8 Codes verwendet. Upgrade auf PRO für 50 Codes."
+2. **Analytics-Feature geklickt** → "Detaillierte Location-Analytics nur in PRO."
+3. **Custom Branding versucht** → "Entferne das QR Master Logo — upgrade auf PRO."
+4. **Bulk-Upload versucht** → "Bulk-Upload ist nur in BUSINESS verfügbar."
+5. **Nach 7 Tagen aktive Nutzung** → In-App Prompt: "Du nutzt QR Master aktiv — hole mehr raus."
+
+### Virality-Mechanismus
+- FREE-Codes enthalten subtiles "Made with QR Master" in Metadaten
+- QR-Code-Landing-Pages (bei Dynamic Redirects) zeigen "Powered by QR Master" Footer
+- Jeder Scan ist eine potenzielle Akquisition
+
+---
+
+## 9. Positioning Statement je Tier
+
+**FREE:**
+> "Starte kostenlos mit 8 professionellen QR-Codes — keine Kreditkarte erforderlich."
+
+**PRO:**
+> "Für Restaurants, lokale Geschäfte und Marketer: Unbegrenzte Änderungen, echte Analytics, dein Branding — für weniger als ein Mittagessen pro Monat."
+
+**BUSINESS:**
+> "Für Agenturen und Retail-Chains: Erstelle 500 Codes auf einmal, per Excel-Upload — DSGVO-konform, skalierbar, professionell."
+
+---
+
+## 10. Pricing Page Struktur (Empfehlung)
+
+### Elemente above the fold
+1. **Toggle: Monatlich / Jährlich** (Default: Jährlich)
+2. **3 Tier-Karten** in Reihenfolge: FREE → PRO (highlighted "Beliebteste Wahl") → BUSINESS
+3. **CTA je Tier:** "Kostenlos starten" / "14 Tage gratis testen" / "Jetzt upgraden"
+4. **Trust-Signal:** "Keine Kreditkarte für Free • DSGVO-konform • Jederzeit kündbar"
+
+### Weitere Sektionen
+- Feature-Vergleichstabelle (vollständig)
+- ROI-Rechner: "Wie viel sparst du durch dynamische QR-Codes vs. Neudruck?"
+- FAQ (Objections aus Product-Marketing-Context)
+- Testimonials-Sektion (Platzhalter für spätere echte Reviews)
+- Enterprise-CTA am Ende
+
+---
+
+## 11. Kurzfristige Maßnahmen (Quick Wins)
+
+| Priorität | Maßnahme | Impact |
+|-----------|----------|--------|
+| 🔴 Hoch | Jahrestarif als Default auf Pricing-Page setzen | +20–30% ARPU sofort |
+| 🔴 Hoch | "2 Monate gratis" Kommunikation (statt %) | +Conversion |
+| 🟡 Mittel | Upgrade-Prompts bei Feature-Gates einbauen | +Free-to-Paid |
+| 🟡 Mittel | 14-Tage PRO Trial (kreditkartenlos) | +Trial Signups |
+| 🟢 Niedrig | BUSINESS Jahrespreis auf €228 festlegen | Cashflow |
+| 🟢 Niedrig | Enterprise-Kontaktformular ergänzen | Upmarket |
+
+---
+
+## 12. Risiken & Gegenmaßnahmen
+
+| Risiko | Wahrscheinlichkeit | Gegenmaßnahme |
+|--------|-------------------|---------------|
+| ViralQR mit $1,49 unterbietbar | Mittel | Auf Analytics + DSGVO differenzieren, nicht Preis |
+| FREE-User konvertieren nicht | Hoch | Smarte Feature-Gates + E-Mail-Nurturing |
+| BUSINESS-Preis zu hoch für KMU | Mittel | Jährlich-Preis betonen: €19/mo fühlt sich zugänglich an |
+| Konkurrenten senken Preise | Niedrig | Value-Story stärken, nicht mitziehen |
+
+---
+
+*Datenbasis: Firecrawl-Scraping von 5+ Competitor-Seiten, QR Marktstatistiken 2026, RevenueCat State of Subscription Apps 2026, Monetizely SaaS Benchmark 2025, Product Marketing Context QR Master.*
--- a/.agents/product-marketing-context.md
+++ b/.agents/product-marketing-context.md
@@ -0,0 +1,98 @@
+# Product Marketing Context
+
+*Last updated: 03. März 2026*
+
+## Product Overview
+**One-liner:** Professionelle dynamische QR-Codes mit Fokus auf Analytics, Bulk-Erstellung und Datenschutz.
+**What it does:** QR Master ermöglicht es Unternehmen und Marketern, QR-Codes zu erstellen, deren Zieladresse auch nach dem Druck geändert werden kann (Dynamic QRs). Es bietet detaillierte Scan-Statistiken, Bulk-Generierung für große Mengen und spezifische Tools für WiFi, Menüs, vCards etc.
+**Product category:** QR Code Management Platform / Marketing Analytics Tool.
+**Product type:** SaaS (Next.js/Prisma Stack).
+**Business model:** Freemium (Abonnement-Modell über Stripe).
+- **FREE:** 8 dynamische Codes, unlimitierte statische Codes.
+- **PRO:** 50 dynamische Codes, Custom Branding, erweiterte Analytics.
+- **BUSINESS:** 500 dynamische Codes, Bulk-Upload, API-Zugriff.
+
+## Target Audience
+**Target companies:** Gastronomie (Restaurants, Cafés), Marketing-Agenturen, Event-Veranstalter, Einzelhandel (Packaging/Labels).
+**Decision-makers:** Marketing Manager, Restaurant-Inhaber, Betriebsleiter, IT-Verantwortliche (wegen DSGVO/Security).
+**Primary use case:** Aktualisierbare QR-Codes für Print-Materialien, um Druckkosten bei Änderungen zu sparen.
+**Jobs to be done:**
+- "Ersetze meine gedruckte Speisekarte digital, ohne bei jeder Preisänderung neu drucken zu müssen."
+- "Miss den Erfolg meiner Flyer-Kampagne durch genaue Scan-Daten."
+- "Erstelle 1.000 individuelle QR-Codes für meine Produktverpackungen in einem Rutsch."
+**Use cases:**
+- Digitale Speisekarten (PDF QR).
+- Kontaktlose Vernetzung (vCard).
+- WLAN-Zugang für Kunden (WiFi QR).
+- Marketing-Kampagnen mit Tracking (UTM-Support).
+
+## Personas
+| Persona | Cares about | Challenge | Value we promise |
+|---------|-------------|-----------|------------------|
+| Restaurant-Inhaber | Kosten, Einfachheit | Menüänderungen erfordern Neudruck | Ein QR-Code für immer, Menü online ändern |
+| Marketing Manager | Daten, ROI | Erfolg von Print-Kampagnen ist schwer messbar | Detaillierte Analytics (Scans, Location, Device) |
+| Logistik/Retail | Skalierung, Zeit | Tausende Codes manuell erstellen | Bulk-Generierung via Excel/CSV (bis 1.000 Stk.) |
+| IT-Sicherheitsbeauftragter | Datenschutz, DSGVO | Tracking von IPs ist rechtlich kritisch | Hashed IPs & Anonymisierung (GDPR-ready) |
+
+## Problems & Pain Points
+**Core problem:** Statische QR-Codes sind nach dem Druck "tot", wenn sich der Link ändert. Das führt zu teuren Nachdrucken und Müll.
+**Why alternatives fall short:**
+- Viele kostenlose Generatoren leiten nach einiger Zeit auf Werbung um oder verlangen plötzlich Geld.
+- Enterprise-Lösungen (Beaconstac etc.) sind für KMUs oft zu teuer und überladen.
+- Mangelnder Datenschutz bei vielen US-Anbietern.
+**What it costs them:** Zeit für manuelle Erstellung, hohe Druckkosten bei Fehlern, verlorene Tracking-Daten.
+**Emotional tension:** Stress bei Fehlern im Druck; Sorge vor Abmahnungen (Datenschutz).
+
+## Competitive Landscape
+**Direct:** QR-Code-Generator.com, Beaconstac, Flowcode.
+**Secondary:** Canva (QR Feature), Adobe Express.
+**Indirect:** Linktree, NFC-Tags.
+**Unterschied:** QR Master ist spezialisierter als Design-Tools, aber preiswerter und datenschutzfreundlicher als US-Enterprise-Lösungen.
+
+## Differentiation
+**Key differentiators:**
+- **Privacy-First:** Hashed IPs (DSGVO-konform), kein PII-Storage.
+- **Bulk-Power:** Excel/CSV-Import bis zu 1.000 Zeilen im Business Plan.
+- **Nischen-Tools:** Hochspezialisierte Generatoren für WiFi, Crypto, Feedback etc.
+**How we do it differently:** Wir trennen die Erstellung (Tools) klar vom Management (Dashboard) und bieten für beides optimierte Flows.
+**Why that's better:** Nutzer finden sofort das richtige Tool für ihr Problem und können später nahtlos ins Management-System wechseln.
+
+## Objections
+| Objection | Response |
+|-----------|----------|
+| "Warum für QR-Codes bezahlen?" | Statische sind kostenlos, aber dynamische sparen Druckkosten bei Link-Änderungen und bieten Tracking. |
+| "Ist Tracking erlaubt?" | Ja, wir nutzen Hashed IPs und IP-Anonymisierung, um DSGVO-konform zu bleiben. |
+| "Was passiert, wenn ich kündige?" | Statische Codes bleiben ewig aktiv. Dynamische werden pausiert, können aber jederzeit reaktiviert werden. |
+
+## Switching Dynamics
+**Push:** Frust über teure Nachdrucke oder unzuverlässige Gratis-Generatoren.
+**Pull:** Wunsch nach professionellen Analytics und einfacher Bulk-Verarbeitung.
+**Habit:** "Wir drucken einfach neue Flyer" (Teuer und ineffizient).
+**Anxiety:** Sorge, dass QR-Codes nach dem Wechsel nicht mehr funktionieren.
+
+## Customer Language
+**How they describe the problem:**
+- "Link ändern nach Druck"
+- "QR-Code Tracking DSGVO"
+- "Bulk QR Code erstellen Excel"
+**Words to use:** "Dynamisch", "Trackbar", "DSGVO-konform", "Änderbar nach Druck", "Bulk-Power".
+**Words to avoid:** "Permanent" (wenn dynamisch gemeint ist), "Tracking" (ohne Datenschutz-Hinweis).
+
+## Brand Voice
+**Tone:** Professionell, vertrauenswürdig, effizient.
+**Style:** Direkt, technisch versiert, aber einfach verständlich.
+**Personality:** Der zuverlässige Partner für moderne Print-Digital-Workflows.
+
+## Proof Points
+**Metrics:** Bis zu 1.000 Codes pro Upload, 8 kostenlose dynamische QRs.
+**Testimonials:** (Noch zu ergänzen basierend auf User-Feedback)
+**Value themes:**
+| Theme | Proof |
+|-------|-------|
+| Kosten sparen | Reprint-Calculator zeigt Ersparnis bei dynamischen Codes. |
+| Datenschutz | Hashed IP Implementation im Codebase (`src/lib/hash.ts`). |
+| Skalierung | Bulk-Feature im Business Plan (`src/app/(main)/(app)/bulk-creation`). |
+
+## Goals
+**Business goal:** Erhöhung der PRO- und BUSINESS-Abonnements.
+**Conversion action:** Account-Erstellung (Signup) oder Start eines Free-Trials.
--- a/.claude/settings.local.json
+++ b/.claude/settings.local.json
@@ -25,7 +25,9 @@
      "Bash(echo \"\n\n## CSRF Debug aktiviert!\n\nBitte teste jetzt:\n1. Browser zu http://localhost:3050/create\n2. Dynamic QR Code erstellen versuchen\n3. Server-Logs zeigen jetzt [CSRF Debug] Output\n\nIch sehe dann:\n- Ob headerToken vorhanden ist\n- Ob cookieToken vorhanden ist  \n- Ob sie übereinstimmen\n\n---\n\nStripe Portal 500 Error ist separates Problem:\nhttps://dashboard.stripe.com/test/settings/billing/portal\n→ Customer Portal Configuration muss erstellt werden\n\")",
      "Bash(pkill:*)",
      "Skill(shadcn-ui)",
-      "Bash(find:*)"
+      "Bash(find:*)",
+      "Bash(ls -la \"/c/Users/User/Documents/QR-master/src/app/\\(main\\)/\\(marketing\\)/\")",
+      "Bash(npx tsc:*)"
    ],
    "deny": [],
    "ask": []
--- a/.codex-temp/awesome-design-md-SKILL.md
+++ b/.codex-temp/awesome-design-md-SKILL.md
@@ -0,0 +1,60 @@
+---
+name: awesome-design-md
+description: Use VoltAgent's awesome-design-md collection when the user wants UI inspired by a specific brand or asks for a DESIGN.md reference, visual system, or brand-style implementation such as Stripe, Linear, Vercel, Claude, or Supabase. Resolve the brand slug from the installed `design-md/` folder, fetch the matching `getdesign.md` design document for that slug, and apply it as the design-system reference for implementation.
+---
+
+# Awesome DESIGN.md
+
+Use this skill to turn the installed `awesome-design-md` collection into a practical design reference workflow.
+
+The local `design-md/` directory is the index of supported brand slugs. Its per-brand `README.md` files are only pointers. The actual design-system document lives at:
+
+```text
+https://getdesign.md/<slug>/design-md
+```
+
+## Workflow
+
+1. Identify the target brand or closest visual reference.
+2. Resolve the brand slug from the local `design-md/` folder.
+3. Prefer exact folder names for dotted brands such as `linear.app`, `mistral.ai`, `opencode.ai`, `together.ai`, and `x.ai`.
+4. Fetch `https://getdesign.md/<slug>/design-md`.
+5. Use the fetched document in one of two ways:
+   - write or update the project's root `DESIGN.md`
+   - keep it as an external design reference while implementing UI
+6. Preserve the user's product semantics and content model. Borrow visual language, spacing, typography, motion, and component patterns, not product-specific copy.
+
+## Local Source Of Truth
+
+Use the installed folder below to confirm which slugs exist before fetching:
+
+```text
+C:\Users\a931627\.claude\skills\awesome-design-md\design-md
+```
+
+If needed, list the available slugs with:
+
+```powershell
+Get-ChildItem -Name C:\Users\a931627\.claude\skills\awesome-design-md\design-md
+```
+
+## Practical Rules
+
+- Treat `DESIGN.md` as a visual system reference, not as code to mirror verbatim.
+- If the user asks for "something like X, but lighter, warmer, or more minimal", adapt the reference instead of cloning it literally.
+- If multiple brands fit, choose the closest one and state the choice.
+- If a slug is missing locally or the remote fetch fails, pick the nearest available brand or ask the user for a replacement target.
+- When working inside an existing design system, merge the borrowed visual cues with the established component structure instead of replacing everything.
+
+## Common Slug Examples
+
+- `stripe`
+- `vercel`
+- `claude`
+- `cursor`
+- `supabase`
+- `linear.app`
+- `mistral.ai`
+- `opencode.ai`
+- `together.ai`
+- `x.ai`
--- a/.dockerignore
+++ b/.dockerignore
@@ -1,55 +1,55 @@
-# Dependencies
-node_modules
-npm-debug.log
-yarn-error.log
-pnpm-debug.log
-
-# Testing
-coverage
-.nyc_output
-
-# Next.js
-.next
-out
-dist
-build
-
-# Environment files
-.env
-.env.local
-.env.development.local
-.env.test.local
-.env.production.local
-
-# IDEs
-.vscode
-.idea
-*.swp
-*.swo
-*~
-
-# OS
-.DS_Store
-Thumbs.db
-
-# Git
-.git
-.gitignore
-
-# Docker
-Dockerfile
-docker-compose*.yml
-.dockerignore
-
-# Misc
-README.md
-.prettierrc
-.eslintrc.json
-*.md
-
-# Logs
-logs
-*.log
-
-# Prisma
-prisma/migrations
+# Dependencies
+node_modules
+npm-debug.log
+yarn-error.log
+pnpm-debug.log
+
+# Testing
+coverage
+.nyc_output
+
+# Next.js
+.next
+out
+dist
+build
+
+# Environment files
+.env
+.env.local
+.env.development.local
+.env.test.local
+.env.production.local
+
+# IDEs
+.vscode
+.idea
+*.swp
+*.swo
+*~
+
+# OS
+.DS_Store
+Thumbs.db
+
+# Git
+.git
+.gitignore
+
+# Docker
+Dockerfile
+docker-compose*.yml
+.dockerignore
+
+# Misc
+README.md
+.prettierrc
+.eslintrc.json
+*.md
+
+# Logs
+logs
+*.log
+
+# Prisma
+# prisma/migrations  # Now included in Docker image for deployment
--- a/.editorconfig
+++ b/.editorconfig
@@ -1,14 +1,14 @@
-root = true
-
-[*]
-charset = utf-8
-end_of_line = lf
-insert_final_newline = true
-trim_trailing_whitespace = true
-
-[*.{js,jsx,ts,tsx,json,css,scss,md}]
-indent_style = space
-indent_size = 2
-
-[*.md]
+root = true
+
+[*]
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[*.{js,jsx,ts,tsx,json,css,scss,md}]
+indent_style = space
+indent_size = 2
+
+[*.md]
 trim_trailing_whitespace = false
--- a/.env.example
+++ b/.env.example
@@ -1,12 +1,26 @@
-NODE_ENV=production
-PORT=3000
-DATABASE_URL=postgresql://postgres:postgres@db:5432/qrmaster?schema=public
-DIRECT_URL=postgresql://postgres:postgres@db:5432/qrmaster?schema=public
-NEXTAUTH_URL=http://localhost:3000
-NEXTAUTH_SECRET=CHANGE_ME
-NEXT_PUBLIC_APP_URL=http://localhost:3000
-GOOGLE_CLIENT_ID=
-GOOGLE_CLIENT_SECRET=
-REDIS_URL=redis://redis:6379
-IP_SALT=CHANGE_ME_SALT
-ENABLE_DEMO=true
+# Database credentials (used by both db and web services in docker-compose.yml)
+POSTGRES_USER=postgres
+POSTGRES_PASSWORD=postgres
+POSTGRES_DB=qrmaster
+
+# Note: DATABASE_URL and DIRECT_URL are auto-generated from POSTGRES_* vars in docker-compose.yml
+# You don't need to set them here when using Docker Compose
+NODE_ENV=production
+PORT=3000
+NEXTAUTH_URL=http://localhost:3000
+NEXTAUTH_SECRET=CHANGE_ME
+NEXT_PUBLIC_APP_URL=http://localhost:3000
+GOOGLE_CLIENT_ID=
+GOOGLE_CLIENT_SECRET=
+REDIS_URL=redis://redis:6379
+IP_SALT=CHANGE_ME_SALT
+ENABLE_DEMO=true
+
+# SMTP (for welcome + retention emails via nodemailer)
+SMTP_HOST=smtp.qrmaster.net
+SMTP_PORT=465
+SMTP_USER=timo@qrmaster.net
+SMTP_PASS=
+
+# Cron job protection — generate with: openssl rand -base64 32
+CRON_SECRET=
--- a/.eslintrc.json
+++ b/.eslintrc.json
@@ -0,0 +1,6 @@
+{
+  "extends": [
+    "next/core-web-vitals",
+    "next/typescript"
+  ]
+}
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -1,26 +1,26 @@
-name: CI
-
-on: [push]
-
-jobs:
-  build:
-    runs-on: ubuntu-latest
-    
-    steps:
-      - uses: actions/checkout@v4
-      
-      - uses: actions/setup-node@v4
-        with:
-          node-version: 20
-          
-      - name: Install dependencies
-        run: npm ci
-        
-      - name: Generate Prisma Client
-        run: npx prisma generate
-        
-      - name: Build application
-        run: npm run build
-        
-      - name: Run linter
+name: CI
+
+on: [push]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    
+    steps:
+      - uses: actions/checkout@v4
+      
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 20
+          
+      - name: Install dependencies
+        run: npm ci
+        
+      - name: Generate Prisma Client
+        run: npx prisma generate
+        
+      - name: Build application
+        run: npm run build
+        
+      - name: Run linter
        run: npm run lint
--- a/.gitignore
+++ b/.gitignore
@@ -1,51 +1,52 @@
-# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
-
-# dependencies
-/node_modules
-/.pnp
-.pnp.js
-
-# testing
-/coverage
-
-# next.js
-/.next/
-/out/
-
-# production
-/build
-
-# misc
-.DS_Store
-*.pem
-
-# debug
-npm-debug.log*
-yarn-debug.log*
-yarn-error.log*
-
+# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
+
+# dependencies
+/node_modules
+/.pnp
+.pnp.js
+
+# testing
+/coverage
+
+# next.js
+/.next/
+/out/
+
+# production
+/build
+
+# misc
+.DS_Store
+*.pem
+
+# debug
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+
 # local env files
 .env*.local
 .env

 # vercel
 .vercel
-
-# typescript
-*.tsbuildinfo
-next-env.d.ts
-
-# prisma
-/prisma/migrations/
-
+
+# typescript
+*.tsbuildinfo
+next-env.d.ts
+
+# prisma
+# /prisma/migrations/  # Now tracked in Git for deployment
+
 # docker
 docker-compose.override.yml
 *.sql
+!prisma/migrations/**/*.sql
 /backups/
-
-# logs
-logs
-*.log
-
-# local dev script
-dev-server.js
+
+# logs
+logs
+*.log
+
+# local dev script
+dev-server.js
--- a/.mcp.json
+++ b/.mcp.json
@@ -0,0 +1,11 @@
+{
+  "mcpServers": {
+    "apify": {
+      "type": "sse",
+      "url": "https://mcp.apify.com/sse",
+      "headers": {
+        "Authorization": "Bearer apify_api_0D7RWI6eW1H9LETBuLY7PHNpAErxL72ua6lo"
+      }
+    }
+  }
+}
--- a/.npmrc
+++ b/.npmrc
@@ -1,2 +1,2 @@
-registry=https://registry.npmjs.org/
+registry=https://registry.npmjs.org/
 legacy-peer-deps=true
--- a/.planning/industry-pages-batch2.md
+++ b/.planning/industry-pages-batch2.md
--- a/.prettierrc
+++ b/.prettierrc
@@ -1,8 +1,8 @@
-{
-  "semi": true,
-  "trailingComma": "es5",
-  "singleQuote": true,
-  "printWidth": 80,
-  "tabWidth": 2,
-  "useTabs": false
+{
+  "semi": true,
+  "trailingComma": "es5",
+  "singleQuote": true,
+  "printWidth": 80,
+  "tabWidth": 2,
+  "useTabs": false
 }
--- a/.vercelignore
+++ b/.vercelignore
@@ -1,10 +1,10 @@
-node_modules
-.next
-.git
-*.log
-.env
-.env.local
-.vercel
-*.sql
-/backups/
-.npmrc
+node_modules
+.next
+.git
+*.log
+.env
+.env.local
+.vercel
+*.sql
+/backups/
+.npmrc
--- a/.vscode/settings.json
+++ b/.vscode/settings.json
@@ -1,3 +1,3 @@
-{
-    "codium.codeCompletion.enable": false
+{
+    "codium.codeCompletion.enable": false
 }
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -0,0 +1,307 @@
+# Universal AI Coding Agent Workflow (Codex / Gemini / Claude)
+
+## Workflow Orchestration
+
+### 1. Plan Mode Default
+- Enter planning mode for ANY non-trivial task (3+ steps or architecture decisions)
+- Analyze the codebase before making changes
+- Break problems into clear subtasks
+- Produce an implementation plan before writing code
+- If assumptions are uncertain, inspect files or run tools first
+- Prefer incremental progress over large rewrites
+
+Plan format:
+
+PLAN
+1. Understand the task
+2. Identify affected files
+3. Design the implementation
+4. Implement step-by-step
+5. Verify results
+
+
+---
+
+# Multi-Agent Strategy
+
+### 2. Agent Decomposition
+
+Use specialized agents for complex work.
+
+Core roles:
+
+- Orchestrator Agent
+- Research Agent
+- Implementation Agent
+- Test Agent
+- Code Review Agent
+- Debug Agent
+- Documentation Agent
+
+Rules:
+- One responsibility per agent
+- Prefer parallel execution
+- Agents should operate on independent files when possible
+- The orchestrator coordinates execution
+
+
+---
+
+# Agent Responsibilities
+
+### Orchestrator Agent
+- analyzes the user request
+- creates task list
+- assigns tasks to agents
+- merges results
+
+### Research Agent
+- scans repository
+- searches dependencies
+- analyzes architecture
+- produces context summary
+
+### Implementation Agent
+- writes code
+- edits files
+- follows project conventions
+- implements features
+
+### Test Agent
+- writes tests
+- verifies functionality
+- checks edge cases
+
+### Code Review Agent
+- reviews diffs
+- checks maintainability
+- suggests improvements
+
+### Debug Agent
+- analyzes logs
+- identifies root causes
+- implements fixes
+
+### Documentation Agent
+- updates docs
+- writes README sections
+- explains new features
+
+
+---
+
+# Execution Pipeline
+
+### 3. Execution Phases
+
+PHASE 1 — Discovery
+- explore repository
+- load relevant files
+- understand architecture
+
+PHASE 2 — Planning
+- generate implementation plan
+- break plan into tasks
+
+PHASE 3 — Task Creation
+
+Create tasks like:
+
+[ ] analyze codebase  
+[ ] implement feature  
+[ ] add tests  
+[ ] review code  
+[ ] update documentation  
+
+PHASE 4 — Implementation
+- execute tasks sequentially or in parallel
+- commit progress
+
+PHASE 5 — Verification
+- run tests
+- check logs
+- verify feature works
+
+PHASE 6 — Review
+- review code quality
+- refactor if necessary
+
+PHASE 7 — Documentation
+- document changes
+
+
+---
+
+# Verification System
+
+### 4. Verification Before Done
+
+Never mark a task complete without proof.
+
+Checks:
+- code compiles
+- feature works
+- tests pass
+- no new errors introduced
+
+Ask:
+
+"Would a senior engineer approve this implementation?"
+
+
+---
+
+# Autonomous Debugging
+
+### 5. Autonomous Bug Fixing
+
+When encountering a bug:
+
+1. analyze error message
+2. inspect stack trace
+3. identify root cause
+4. implement fix
+5. verify with tests
+
+Rules:
+- Never apply random fixes
+- Always understand the root cause first
+
+
+---
+
+# Context Management
+
+### 6. Context Awareness
+
+Before implementing anything:
+
+- load relevant files
+- inspect dependencies
+- understand architecture
+- read configuration files
+
+Always maintain awareness of:
+
+- system architecture
+- data flow
+- dependencies
+
+
+---
+
+# Memory System
+
+### 7. Persistent Memory
+
+Store long-term knowledge in:
+
+memory/
+- project_summary.md
+- architecture.md
+- lessons.md
+- coding_standards.md
+
+This prevents repeated mistakes.
+
+
+---
+
+# Learning Loop
+
+### 8. Self-Improvement
+
+After errors or corrections:
+
+Update:
+
+tasks/lessons.md
+
+Include:
+- mistake pattern
+- root cause
+- prevention rule
+
+Example:
+
+Lesson:  
+Always validate API responses before processing them.
+
+
+---
+
+# Safety Rules
+
+### 9. Safety
+
+Never perform dangerous actions automatically.
+
+Rules:
+
+- never delete files without confirmation
+- avoid modifying production configuration automatically
+- create backups before large refactors
+- avoid irreversible operations
+
+
+---
+
+# Iteration Control
+
+### 10. Infinite Loop Protection
+
+If the same error happens more than 3 times:
+
+STOP
+
+- re-evaluate the strategy
+- re-plan the solution
+- choose a different debugging approach
+
+
+---
+
+# Core Engineering Principles
+
+### Simplicity First
+Prefer the simplest solution that works.
+
+### Root Cause Fixes
+Always fix the underlying problem, not symptoms.
+
+### Minimal Impact
+Touch the smallest amount of code possible.
+
+### Maintainability
+Code should remain readable and maintainable.
+
+
+---
+
+# Final Rule
+
+Before delivering a solution ask:
+
+Is this solution correct, maintainable, and verifiable?
+
+If not:
+
+Refine it before presenting it.
+
+
+---
+
+# Recommended File Usage
+
+You can place this workflow in one of the following files:
+
+AGENT_WORKFLOW.md  
+CLAUDE.md  
+AGENTS.md  
+
+This allows it to be used by:
+
+- Claude Code Agent Teams
+- Codex CLI
+- Gemini Code Assist
+- Cursor Agents
--- a/AI-SEO-CONTENT-PRIORITIES.md
+++ b/AI-SEO-CONTENT-PRIORITIES.md
@@ -0,0 +1,48 @@
+# AI SEO Content Priorities
+
+Last updated: 2026-04-14
+
+Purpose: prioritize the next content pass after the raw rollout, visible freshness fix, and `llms.txt` expansion.
+
+## Priority 1
+
+1. `qr-code-scan-statistics-2026`
+Reason: strongest citation potential because statistics pages are the easiest source type for LLMs to quote.
+Next move: verify every stat has a current primary source and an explicit inline citation in the article body.
+
+2. `qr-code-analytics`
+Reason: high commercial intent and strong fit for QR Master's differentiation around measurement and ROI.
+Next move: sharpen answer blocks around scan metrics, dashboards, and campaign decisions.
+
+3. `qr-code-marketing`
+Reason: bridges informational and product-intent queries around campaign ROI, CTAs, and tracking.
+Next move: tighten the first-screen answer and add more comparative guidance for common campaign use cases.
+
+4. `free-vs-paid-qr-generator`
+Reason: strong comparison intent and a natural path into dynamic QR, tracking, and upgrade logic.
+Next move: strengthen side-by-side comparison blocks and source any claims about reliability or limits.
+
+## Priority 2
+
+5. `best-qr-code-generator-2026`
+Reason: "best" queries are heavily represented in AI answers but need balanced, defensible comparisons.
+Next move: review neutrality, keep claims sourced, and make evaluation criteria more explicit.
+
+6. `bulk-qr-code-generator-excel`
+Reason: strong workflow intent and direct fit with a high-value product capability.
+Next move: improve step extraction and source support for operational best practices where possible.
+
+7. `qr-code-events`
+Reason: clear use-case page with practical intent and good overlap with tracking and dynamic QR value.
+Next move: add stronger answer passages around tickets, check-in, UTMs, and event ROI.
+
+8. `qr-code-security`
+Reason: security content earns citations when it is current, specific, and source-heavy.
+Next move: validate the quishing data points and make safe-deployment recommendations easier to quote.
+
+## Review Criteria
+
+- The first 40 to 60 words should answer the core query directly.
+- Major claims should point to a primary source, not an unsourced assertion.
+- Comparison and checklist content should prefer tables or tightly structured blocks over long prose.
+- Posts that support product evaluation should link clearly into the relevant QR Master marketing pages.
--- a/AI-SEO-TOP5-REWRITE-PLAN.md
+++ b/AI-SEO-TOP5-REWRITE-PLAN.md
@@ -0,0 +1,419 @@
+# AI SEO Top 5 Rewrite Plan
+
+Last updated: 2026-04-14
+
+Method: `ai-seo`
+
+Goal: define the exact AEO/GEO rewrite moves for the five blog posts with the strongest combination of keyword demand, product fit, and AI citation potential.
+
+## 1. `dynamic-vs-static-qr-codes`
+
+File reference: [src/lib/blog-data.ts](/abs/path/C:/Users/a931627/Documents/QRMASTER/src/lib/blog-data.ts:707)
+
+### Target queries
+
+- `dynamic qr code`
+- `dynamic qr code generator`
+- `create dynamic qr code`
+- `static qr codes`
+- `editable qr code`
+
+### What already works
+
+- Strong `quickAnswer`
+- Clear FAQ intent
+- Good internal link path into tracking and comparison content
+- Sources already exist
+
+### Exact sections to change
+
+1. Replace the opening body paragraph with a direct definition + decision summary.
+Current issue: the intro starts with a conversational framing instead of a highly extractable answer block.
+Change to: a 40 to 60 word paragraph that answers:
+"A static QR code cannot be edited after printing. A dynamic QR code can be updated, tracked, and reused. For business campaigns, menus, and promotions, dynamic QR codes are usually the better choice because they prevent reprints and enable analytics."
+
+2. Add an early comparison table directly after the intro.
+New section:
+`## Static vs Dynamic QR Code Comparison`
+Include rows for:
+- editable after printing
+- analytics
+- best use case
+- risk of reprint cost
+- ideal for marketing
+- ideal for permanent utility use
+
+3. Add a decision section that maps user intent to format choice.
+New section:
+`## When To Use Static QR Codes`
+New section:
+`## When To Use Dynamic QR Codes`
+Each section should open with a one-sentence answer, then 3 to 5 bullets.
+
+4. Add a cost/risk section.
+New section:
+`## Why Dynamic QR Codes Save Money`
+This should translate product value into a business outcome:
+- changed menu URL
+- campaign landing page update
+- print correction avoidance
+
+5. Expand FAQ to cover high-intent objections.
+Add:
+- "Are dynamic QR codes worth paying for?"
+- "Can a dynamic QR code become inactive?"
+- "Is a static QR code ever better than a dynamic one?"
+
+### AEO focus
+
+- Make the first screen answer self-contained.
+- Prefer table + decision logic over generic prose.
+- Keep the distinction between "editable" and "trackable" explicit in every major section.
+
+### Authority upgrades
+
+- Add at least one explicit sourced statement in the intro or first comparison section.
+- Where possible, cite original sources for adoption or tracking claims rather than broad vendor summaries.
+
+### Internal linking
+
+- Link to `/dynamic-qr-code-generator`
+- Link to `/qr-code-tracking`
+- Link to `/pricing`
+- Keep links to `trackable-qr-codes` and `free-vs-paid-qr-generator`
+
+## 2. `qr-code-tracking-guide-2025`
+
+File reference: [src/lib/blog-data.ts](/abs/path/C:/Users/a931627/Documents/QRMASTER/src/lib/blog-data.ts:653)
+
+### Target queries
+
+- `qr code tracking`
+- `track qr scans`
+- `dynamic qr code analytics`
+- `google analytics qr`
+- `utm qr codes`
+
+### What already works
+
+- High commercial relevance
+- Strong `quickAnswer`
+- Good `keySteps`
+- FAQ already aligned to the query
+
+### Exact sections to change
+
+1. Replace `Why Track QR Codes?` with a sharper query-matching heading.
+Rename to:
+`## What Is QR Code Tracking?`
+The first paragraph should define tracking in one extractable block:
+"QR code tracking means measuring what happens after a scan. With a dynamic QR code, you can log scan time, device type, location, and destination performance. If you also add UTM parameters, you can measure campaign attribution in tools like GA4."
+
+2. Split "tracking" and "analytics" clearly.
+New section:
+`## QR Code Tracking vs QR Code Analytics`
+Reason: this is already in the FAQ and deserves a visible answer block because it is highly citable.
+
+3. Add a metrics section with a structured list.
+New section:
+`## What Metrics Should You Track?`
+Use a table with:
+- total scans
+- unique scans
+- scan time
+- device type
+- location
+- landing page conversions
+- cost per conversion
+
+4. Add an implementation section for GA4 and UTMs.
+New section:
+`## How To Track QR Codes In Google Analytics 4`
+Keep it procedural:
+- create dynamic QR destination
+- append UTM parameters
+- define conversion event in GA4
+- compare placements
+
+5. Add a limitations section.
+New section:
+`## What QR Tracking Can And Cannot Measure`
+This improves trust and helps citation because it sounds more rigorous.
+
+### AEO focus
+
+- The first H2 should match the core query exactly.
+- One section should answer "Can I track a static QR code?" before the FAQ.
+- Use one metric table instead of only prose.
+
+### Authority upgrades
+
+- Keep Bitly and Google Analytics references, but tighten them around specific claims.
+- If scan or attribution claims are broad, attach dates and exact measurement context.
+
+### Internal linking
+
+- Link to `/qr-code-tracking`
+- Link to `utm-parameter-qr-codes`
+- Link to `qr-code-analytics`
+- Link to `/dynamic-qr-code-generator`
+
+## 3. `bulk-qr-code-generator-excel`
+
+File reference: [src/lib/blog-data.ts](/abs/path/C:/Users/a931627/Documents/QRMASTER/src/lib/blog-data.ts:759)
+
+### Target queries
+
+- `bulk qr code generator`
+- `qr code generator bulk`
+- `qr code generator excel`
+- `qr codes from excel`
+- `csv qr code generator`
+
+### What already works
+
+- Strong workflow intent
+- Good step list
+- Good FAQ coverage
+- Strong product fit for a paid/business feature
+
+### Exact sections to change
+
+1. Rewrite the intro to answer the exact workflow query faster.
+Current issue: the intro starts with narrative scale examples before the direct instruction.
+Change to:
+"To generate bulk QR codes from Excel, prepare a spreadsheet with one row per QR destination, export it as CSV, upload it to a bulk QR generator, and download the generated batch. This is the standard workflow for product labels, badges, inventory, and large campaigns."
+
+2. Add a file format section.
+New section:
+`## Excel vs CSV: Which Format Do You Actually Need?`
+This should explicitly explain that CSV is usually the upload format even when users say Excel.
+
+3. Add a required-column section.
+New section:
+`## Recommended Spreadsheet Columns`
+Use a table:
+- `url`
+- `label`
+- `campaign`
+- `utm_source`
+- `utm_medium`
+- `utm_campaign`
+- optional `filename`
+
+4. Add a common-errors section.
+New section:
+`## Common Bulk QR Upload Errors`
+Include:
+- broken URLs
+- inconsistent columns
+- spaces in headers
+- mixed protocols
+- untested redirect destinations
+
+5. Add a dynamic-vs-static decision block for batches.
+New section:
+`## Should Bulk QR Codes Be Static Or Dynamic?`
+This should explicitly tie bulk use cases to tracking, editing, and reprint risk.
+
+6. Add a QA checklist before production.
+New section:
+`## Pre-Print Quality Check`
+Use a numbered list with 5 to 7 checks.
+
+### AEO focus
+
+- This post should behave like a procedural answer, not a generic guide.
+- The column table and error list are likely the most citable parts.
+- Make "Excel" and "CSV" relationship explicit because users search for Excel but often need CSV.
+
+### Authority upgrades
+
+- Existing sources are serviceable, but add at least one stronger operational source if available.
+- Where no authoritative external source exists, use precise first-party workflow guidance without overclaiming.
+
+### Internal linking
+
+- Link to `/bulk-qr-code-generator`
+- Link to `qr-code-print-size-guide`
+- Link to `qr-code-tracking-guide-2025`
+- Link to `dynamic-vs-static-qr-codes`
+
+## 4. `vcard-qr-code-generator`
+
+File reference: [src/lib/blog-data.ts](/abs/path/C:/Users/a931627/Documents/QRMASTER/src/lib/blog-data.ts:504)
+
+### Target queries
+
+- `vcard qr code generator`
+- `vcard qr code`
+- `vcard generator`
+- `vcard qr`
+- `create vcard qr code`
+
+### What already works
+
+- Good keyword fit
+- Good query-to-tool match
+- Strong utility use case
+
+### Exact sections to change
+
+1. Tighten the opening definition.
+The first paragraph should answer:
+"A vCard QR code stores contact details such as name, phone number, email, company, and website. When someone scans it, they can save the contact directly to their phone without typing."
+
+2. Add a static-vs-dynamic contact section.
+New section:
+`## Static vs Dynamic vCard QR Codes`
+Cover:
+- when static is enough
+- when dynamic is better
+- when tracking matters
+
+3. Add a field breakdown section.
+New section:
+`## What Information Can A vCard QR Code Include?`
+Use a compact list or table:
+- full name
+- phone
+- email
+- company
+- job title
+- website
+- address
+- social profile
+
+4. Add a use-case section.
+New section:
+`## Best Use Cases For vCard QR Codes`
+Examples:
+- business cards
+- trade shows
+- packaging inserts
+- storefronts
+- service professionals
+
+5. Add a scannability and contact-save section.
+New section:
+`## Best Practices For High Save Rates`
+Focus on CTA language:
+- scan to save contact
+- add me instantly
+- connect without typing
+
+### AEO focus
+
+- Treat this as a definitional + use-case post, not just a tool page.
+- The definition block and field list are the most important extractable components.
+
+### Authority upgrades
+
+- If current sources are weak or missing, add at least one standards-oriented or platform-oriented source.
+- Avoid unsupported claims around conversion unless sourced.
+
+### Internal linking
+
+- Link to the vCard tool page
+- Link to `business-card-qr-code`
+- Link to `dynamic-vs-static-qr-codes`
+- Link to `/pricing` if dynamic/contact-management features are relevant
+
+## 5. `qr-code-print-size-guide`
+
+File reference: [src/lib/blog-data.ts](/abs/path/C:/Users/a931627/Documents/QRMASTER/src/lib/blog-data.ts:604)
+
+### Target queries
+
+- `minimum qr code size`
+- `qr code print size`
+- `qr code size guide`
+- `qr code scanning distance`
+
+### What already works
+
+- Very strong query structure
+- Excellent snippet potential
+- Good `quickAnswer`
+- Good FAQ fit
+
+### Exact sections to change
+
+1. Keep the 10:1 rule, but make it the first body paragraph in exact answer form.
+Suggested phrasing:
+"The standard starting rule for QR print size is 10:1: the code should be about one-tenth of the expected scanning distance. A QR code scanned from 2 meters away should usually be around 20 centimeters wide."
+
+2. Add a distance-to-size table immediately after the intro.
+New section:
+`## QR Code Size Chart By Scanning Distance`
+Include examples for:
+- 20 cm
+- 50 cm
+- 1 m
+- 2 m
+- 5 m
+
+3. Add format-specific minimums.
+New section:
+`## Minimum QR Code Sizes For Common Print Formats`
+Use rows for:
+- business card
+- flyer
+- poster
+- packaging
+- menu stand
+- window signage
+
+4. Add a density warning section.
+New section:
+`## Why More Data Requires A Larger QR Code`
+Cover:
+- long URLs
+- vCard payloads
+- WiFi payloads
+- error correction tradeoffs
+
+5. Add a print-production checklist.
+New section:
+`## Print Checklist Before You Go Live`
+Include:
+- SVG preferred
+- 300 DPI minimum for raster
+- quiet zone intact
+- strong contrast
+- test in real lighting
+- test with average phones, not only flagship devices
+
+### AEO focus
+
+- This post should be built around tables and formulas, not narrative.
+- The size chart is likely the strongest snippet and AI Overview asset.
+- Keep measurements concrete and example-heavy.
+
+### Authority upgrades
+
+- If possible, support the 10:1 rule with an external reference or state it clearly as an operational best-practice baseline.
+- Avoid over-precision if it is based on heuristics rather than a standard.
+
+### Internal linking
+
+- Link to `business-card-qr-code`
+- Link to `qr-code-restaurant-menu`
+- Link to `bulk-qr-code-generator-excel`
+- Link to relevant tool or generator pages
+
+## Execution Order
+
+1. `dynamic-vs-static-qr-codes`
+2. `qr-code-tracking-guide-2025`
+3. `bulk-qr-code-generator-excel`
+4. `qr-code-print-size-guide`
+5. `vcard-qr-code-generator`
+
+## Acceptance Criteria
+
+- The first paragraph on each post answers the target query directly.
+- Each post includes at least one visibly structured block that is easy to quote:
+  table, checklist, comparison block, or metric summary.
+- Claims that imply data, performance, or market adoption are tied to a source.
+- The post clearly routes users into the relevant QR Master product or feature page.
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,187 +0,0 @@
-# Changelog - PostgreSQL Migration
-
-## [2.0.0] - 2024-10-13
-
-### 🎉 Major Changes - Supabase to PostgreSQL Migration
-
-#### Removed
- ❌ **Supabase dependency** - Removed all Supabase-specific configurations
- ❌ **DIRECT_URL** - Removed connection pooling URL (Supabase-specific)
- ❌ **External database dependency** - Now fully self-hosted
-
-#### Added
- ✅ **PostgreSQL 16 in Docker** - Local PostgreSQL database with Docker support
- ✅ **Redis 7** - Caching and rate limiting with Redis
- ✅ **Adminer** - Database management UI (http://localhost:8080)
- ✅ **Docker Compose setups** - Both development and production configurations
- ✅ **Database initialization** - Automated database setup with extensions
- ✅ **Complete documentation** - Multiple guides for setup and migration
- ✅ **Setup scripts** - Automated setup for both Linux/Mac and Windows
- ✅ **npm scripts** - Convenient Docker commands via npm
-
-#### Modified Files
- 📝 `prisma/schema.prisma` - Removed directUrl field
- 📝 `src/lib/env.ts` - Removed DIRECT_URL, updated DATABASE_URL default
- 📝 `docker-compose.yml` - Complete rewrite with PostgreSQL, Redis, and networking
- 📝 `Dockerfile` - Enhanced with proper PostgreSQL support
- 📝 `package.json` - Added Docker scripts and tsx dependency
- 📝 `README.md` - Updated with new setup instructions
-
-#### New Files
- 📄 `docker-compose.dev.yml` - Development environment (database only)
- 📄 `docker/init-db.sh` - PostgreSQL initialization script
- 📄 `docker/README.md` - Docker-specific documentation
- 📄 `DOCKER_SETUP.md` - Comprehensive Docker setup guide
- 📄 `MIGRATION_FROM_SUPABASE.md` - Step-by-step migration guide
- 📄 `env.example` - Environment variable template
- 📄 `.dockerignore` - Docker build optimization
- 📄 `scripts/setup.sh` - Quick setup script (Linux/Mac)
- 📄 `scripts/setup.ps1` - Quick setup script (Windows)
- 📄 `CHANGELOG.md` - This file
-
-### 📦 Docker Services
-
-#### PostgreSQL Database
- **Image**: postgres:16-alpine
- **Port**: 5432
- **Features**: 
-  - Health checks
-  - Volume persistence
-  - UTF-8 encoding
-  - Extensions: uuid-ossp, pg_trgm
-
-#### Redis Cache
- **Image**: redis:7-alpine
- **Port**: 6379
- **Features**:
-  - AOF persistence
-  - 256MB max memory with LRU eviction
-  - Health checks
-
-#### Next.js Application
- **Port**: 3000
- **Features**:
-  - Multi-stage build
-  - Production optimization
-  - Health checks
-  - Automatic Prisma generation
-
-#### Adminer (Development)
- **Port**: 8080
- **Features**:
-  - Database management UI
-  - Optional (dev profile)
-  - Pre-configured for PostgreSQL
-
-### 🚀 Quick Start
-
-#### Development Mode
-```bash
-npm run docker:dev    # Start database
-npm run db:migrate    # Run migrations
-npm run dev           # Start app
-```
-
-#### Production Mode
-```bash
-npm run docker:prod   # Start all services
-```
-
-### 📚 Documentation
-
- **README.md** - Main documentation with quick start
- **DOCKER_SETUP.md** - Complete Docker guide with troubleshooting
- **MIGRATION_FROM_SUPABASE.md** - Migration guide from Supabase
- **docker/README.md** - Docker commands and operations
- **env.example** - Environment variable reference
-
-### 🔧 New npm Scripts
-
-```bash
-# Docker commands
-npm run docker:dev         # Start development services
-npm run docker:dev:stop    # Stop development services
-npm run docker:prod        # Start production stack
-npm run docker:stop        # Stop all services
-npm run docker:logs        # View all logs
-npm run docker:db          # PostgreSQL CLI
-npm run docker:redis       # Redis CLI
-npm run docker:backup      # Backup database
-```
-
-### 🔐 Environment Variables
-
-#### Required
- `DATABASE_URL` - PostgreSQL connection string
- `NEXTAUTH_SECRET` - NextAuth.js secret (generate with openssl)
- `NEXTAUTH_URL` - Application URL
- `IP_SALT` - Salt for IP hashing (generate with openssl)
-
-#### Optional
- `GOOGLE_CLIENT_ID` - Google OAuth client ID
- `GOOGLE_CLIENT_SECRET` - Google OAuth secret
- `REDIS_URL` - Redis connection string
- `ENABLE_DEMO` - Enable demo mode
-
-### 🎯 Benefits
-
-1. **Full Control** - Own your data and infrastructure
-2. **No Vendor Lock-in** - Standard PostgreSQL
-3. **Lower Latency** - Local network speed
-4. **Cost Effective** - No monthly database fees
-5. **Privacy** - Data stays on your infrastructure
-6. **Development** - Easy local testing
-7. **Offline Capable** - Works without internet
-
-### 🔄 Migration Path
-
-1. Backup Supabase data
-2. Update codebase
-3. Start local PostgreSQL
-4. Restore data or run migrations
-5. Update environment variables
-6. Deploy
-
-See [MIGRATION_FROM_SUPABASE.md](MIGRATION_FROM_SUPABASE.md) for detailed steps.
-
-### ⚠️ Breaking Changes
-
- `DIRECT_URL` environment variable removed
- Database now requires Docker or local PostgreSQL
- Supabase-specific features removed
-
-### 📊 Performance Improvements
-
- Local database reduces latency
- Redis caching improves response times
- Connection pooling via Prisma
- Optimized Docker images
-
-### 🐛 Bug Fixes
-
- Fixed database connection handling
- Improved error messages
- Better health checks
-
-### 🔜 Future Enhancements
-
- [ ] PostgreSQL replication for HA
- [ ] Redis Sentinel for failover
- [ ] Automated backup scripts
- [ ] Monitoring and alerting
- [ ] Database performance tuning
- [ ] Multi-region deployment
-
-### 📝 Notes
-
- Default PostgreSQL password should be changed in production
- Always backup data before migration
- Review security settings before deployment
- Set up automated backups in production
-
---
-
-**Migration completed successfully!** 🎉
-
-For support, see documentation or open an issue on GitHub.
-
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -0,0 +1,281 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## Project Overview
+
+**QR Master** is a production-ready SaaS application for creating and managing QR codes with advanced analytics, Stripe payment integration, and multi-tier subscription plans (FREE, PRO, BUSINESS).
+
+## Tech Stack
+
+- **Frontend**: Next.js 14 (App Router), React 18, TypeScript, Tailwind CSS, Framer Motion
+- **Backend**: Next.js API Routes, Prisma ORM, PostgreSQL
+- **Authentication**: NextAuth.js v4 (Credentials + Google OAuth)
+- **Payments**: Stripe (subscriptions, webhooks)
+- **Cache**: Redis (optional)
+- **Analytics**: PostHog (optional), QR scan tracking with IP hashing
+- **QR Generation**: qrcode, qr-code-styling libraries
+- **Bulk Operations**: Papa Parse (CSV), ExcelJS, JSZip
+- **Storage**: AWS S3 (via @aws-sdk)
+
+## Quick Development Commands
+
+```bash
+# Setup
+npm install
+npm run docker:dev              # Start PostgreSQL & Redis in Docker
+npx prisma migrate dev          # Run migrations
+npm run db:seed                 # Seed demo data
+
+# Development
+npm run dev                      # Start dev server (port 3050)
+npm run lint                     # Run ESLint
+
+# Database
+npm run db:migrate              # Run pending migrations (dev mode)
+npm run db:deploy               # Apply migrations (production)
+npm run db:studio               # Open Prisma Studio UI
+npx prisma migrate reset        # Reset database (drops, recreates, seeds)
+
+# Docker
+npm run docker:prod             # Start full production stack
+npm run docker:dev:stop         # Stop dev services
+npm run docker:logs             # View logs
+npm run docker:db               # PostgreSQL CLI
+npm run docker:redis            # Redis CLI
+npm run docker:backup           # Backup database to SQL file
+
+# Build & Deploy
+npm run build                   # Production build
+npm run start                   # Start production server
+```
+
+## Project Structure
+
+```
+src/
+├── app/
+│   └── (main)/
+│       ├── (app)/              # Authenticated app pages (dashboard, bulk-creation, settings)
+│       ├── (auth)/             # Auth pages (login, signup, forgot-password)
+│       ├── (marketing)/        # Public pages & marketing tools
+│       │   └── tools/          # QR code type-specific generators (20+ tools)
+│       └── api/                # API routes organized by domain
+│           ├── auth/           # Authentication (signin, signup, OAuth, password reset)
+│           ├── qrs/            # QR code CRUD (GET, POST, PATCH, DELETE)
+│           ├── analytics/      # Analytics summary endpoint
+│           ├── stripe/         # Payment webhooks & session management
+│           ├── user/           # User profile, plan, stats, password
+│           ├── newsletter/     # Subscription management
+│           └── [other]/        # admin, feedback, leads, bulk, etc.
+├── components/
+│   ├── ui/                     # Reusable UI primitives (Card, Dialog, Input, etc.)
+│   ├── generator/              # QR code generator components
+│   ├── analytics/              # Charts, maps, data visualization
+│   ├── dashboard/              # Dashboard-specific components
+│   ├── settings/               # Settings & account components
+│   └── SessionProvider.tsx     # NextAuth session provider
+├── lib/
+│   ├── auth.ts                 # NextAuth configuration
+│   ├── db.ts                   # Prisma client
+│   ├── stripe.ts               # Stripe utilities
+│   ├── email.ts                # Email sending (Resend)
+│   ├── qr.ts                   # QR code generation utilities
+│   ├── geo.ts                  # Geolocation utilities
+│   ├── hash.ts                 # IP hashing (privacy)
+│   ├── csrf.ts                 # CSRF token generation/validation
+│   ├── rateLimit.ts            # Rate limiting utilities
+│   ├── schema.ts               # Zod validation schemas
+│   ├── validationSchemas.ts    # Additional validation
+│   └── cookieConfig.ts         # Cookie configuration
+├── hooks/
+│   ├── useCsrf.ts              # CSRF token hook
+│   └── useTranslation.ts       # i18n hook
+└── types/
+    └── analytics.ts            # Analytics type definitions
+```
+
+## Database Architecture
+
+**Key Models** (see `prisma/schema.prisma`):
+
+- **User**: User accounts with Stripe subscription fields
+- **QRCode**: QR code records (static/dynamic, multiple content types)
+- **QRScan**: Analytics data (ts, ipHash, device, os, country, UTM params)
+- **Account/Session**: NextAuth authentication tables
+- **Integration**: Third-party integrations
+- **NewsletterSubscription**: Email subscribers
+- **Lead**: Lead generation data
+
+**QR Code Types**: URL, VCARD, GEO, PHONE, SMS, TEXT, WHATSAPP, PDF, APP, COUPON, FEEDBACK
+
+## API Architecture
+
+### Authentication Flow
+- Credentials-based login/signup via `/api/auth/signup` and `/api/auth/simple-login`
+- Google OAuth via `/api/auth/google`
+- NextAuth.js session management at `/api/auth/[...nextauth]`
+- Password reset: `/api/auth/forgot-password` + `/api/auth/reset-password`
+
+### QR Code Operations
+- **CRUD**: `GET/POST /api/qrs`, `GET/PATCH/DELETE /api/qrs/[id]`
+- **Static Generation**: `POST /api/qrs/static`
+- **Bulk Operations**: `POST /api/bulk/*` for CSV/Excel import
+- **Public Redirect**: `GET /r/[slug]` (redirect + analytics tracking)
+
+### Payments
+- Stripe webhooks: `POST /api/stripe/webhook`
+- Checkout session: `POST /api/stripe/checkout` or `/api/stripe/create-checkout-session`
+- Customer portal: `POST /api/stripe/portal`
+- Subscription sync: `POST /api/stripe/sync-subscription`
+- Cancellation: `POST /api/stripe/cancel-subscription`
+
+### Analytics
+- Summary endpoint: `GET /api/analytics/summary?qrId=<id>`
+- Scan tracking with hashed IP (GDPR-compliant)
+
+## Key Implementation Patterns
+
+### Authentication & Authorization
+- NextAuth.js v4 with Prisma adapter
+- Sessions stored in database
+- CSRF protection on all mutations (check `useCsrf` hook)
+- Password hashing with bcryptjs
+
+### API Security
+- Rate limiting on sensitive endpoints (auth, payments)
+- CSRF tokens validated on POST/PATCH/DELETE
+- IP hashing for privacy (IP_SALT environment variable)
+- DNT header respected for analytics
+
+### Database Operations
+- Prisma ORM for all database access
+- Migrations stored in `prisma/migrations/`
+- Seed script for demo data in `prisma/seed.ts`
+- Database indexes on frequently queried fields (userId, createdAt, etc.)
+
+### QR Code Generation
+- `qrcode` library for basic generation
+- `qr-code-styling` for advanced customization
+- `qrcode.react` for inline React components
+- Canvas/SVG export via `html-to-image`, `jspdf`, `jszip`
+
+### State & Validation
+- Zod schemas in `/lib/schema.ts` for runtime validation
+- TypeScript strict mode enabled
+- Prisma provides type safety at database layer
+
+## Environment Variables
+
+**Required**:
+- `DATABASE_URL` - PostgreSQL connection string
+- `NEXTAUTH_SECRET` - JWT encryption secret
+- `NEXTAUTH_URL` - Application URL (default: `http://localhost:3050`)
+- `IP_SALT` - Salt for IP hashing
+
+**Optional but Important**:
+- `STRIPE_SECRET_KEY`, `STRIPE_WEBHOOK_SECRET`, `NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY`
+- `GOOGLE_CLIENT_ID`, `GOOGLE_CLIENT_SECRET` - OAuth
+- `REDIS_URL` - Redis connection
+- `NEXT_PUBLIC_POSTHOG_KEY`, `NEXT_PUBLIC_POSTHOG_HOST` - Analytics
+- `NEXT_PUBLIC_INDEXABLE` - Set to `true` for production (enables search engine indexing)
+
+**Generate Secrets**:
+```bash
+openssl rand -base64 32  # NEXTAUTH_SECRET and IP_SALT
+```
+
+## Common Tasks
+
+### Adding a New QR Code Type
+1. Add type to `ContentType` enum in `prisma/schema.prisma`
+2. Create generator component in `src/components/generator/` or `src/app/(main)/(marketing)/tools/`
+3. Add validation schema in `src/lib/schema.ts`
+4. Create API endpoint if needed in `src/app/(main)/api/qrs/`
+
+### Creating a New Marketing Tool Page
+1. Create page at `src/app/(main)/(marketing)/tools/[tool-name]/page.tsx`
+2. Create generator component in same directory
+3. Add SEO metadata in page component
+4. Tool should be static (no database) or use public API endpoints
+
+### Adding a New API Endpoint
+1. Create route file in appropriate directory under `src/app/(main)/api/`
+2. Add Zod validation schema in `src/lib/schema.ts`
+3. Check authentication with `getServerSession()` if needed
+4. Implement rate limiting for sensitive operations
+5. Return typed responses with proper status codes
+
+### Database Schema Changes
+1. Update `prisma/schema.prisma`
+2. Run `npx prisma migrate dev --name <migration-name>`
+3. This creates migration file and updates Prisma client
+4. Test with `npm run db:seed` if demo data affected
+
+## Testing & Debugging
+
+- Demo account (after seed): email: `demo@qrmaster.com`, password: `demo123`
+- Prisma Studio: `npm run db:studio` - visual database browser
+- API testing: Check `/src/app/(main)/api/` for examples
+- Frontend: Pages hot-reload on changes during `npm run dev`
+
+## Performance Considerations
+
+- PostgreSQL indexes on `QRCode(userId, createdAt)` and `QRScan(qrId, ts)`
+- Redis optional but recommended for caching analytics
+- Static export for marketing pages when possible
+- Image optimization enabled in `next.config.mjs`
+- Prisma connection pooling recommended for production
+
+## Database Change Policy
+
+**IMPORTANT: No Prisma migrations.** All database schema changes (new columns, new enum values, new tables) must be applied via raw SQL commands directly against the running PostgreSQL instance.
+
+Workflow for schema changes:
+1. Write the raw SQL (e.g. `ALTER TABLE`, `ALTER TYPE ... ADD VALUE`)
+2. Run via Docker: `npm run docker:db` then execute SQL, or use `docker-compose exec db psql -U postgres -d qrmaster -c "..."`
+3. Update `prisma/schema.prisma` to match (so Prisma client types stay in sync)
+4. Run `npx prisma generate` to regenerate the client (no `migrate`)
+
+Example — adding an enum value:
+```sql
+ALTER TYPE "ContentType" ADD VALUE 'BARCODE';
+```
+
+## Common Pitfalls
+
+1. **Database Connection**: If "Can't reach database server", ensure Docker is running (`npm run docker:dev`)
+2. **Prisma Out of Sync**: Run `npx prisma generate` if TypeScript errors appear
+3. **Migration Conflicts**: Use `npx prisma migrate reset` to start fresh
+4. **Port 3050 in Use**: Change port in `package.json` dev script or kill process
+5. **Build Failures**: Check `NODE_OPTIONS='--max-old-space-size=4096'` in build script - set higher if needed
+
+## SEO & Content
+
+- Schema.org structured data implemented for products, organizations, FAQs
+- Breadcrumb navigation for UX/SEO
+- Meta tags configured per page
+- Open Graph images at `/api/og`
+- Sitemap generation via next-sitemap
+- Google Indexing API + IndexNow submission scripts available
+
+## Deployment Notes
+
+### Docker (Self-Hosted)
+```bash
+npm run docker:prod  # Builds and starts full stack
+docker-compose exec web npx prisma migrate deploy  # Run migrations in container
+```
+
+### Vercel
+- Push to GitHub and import in Vercel dashboard
+- Set environment variables in Vercel settings
+- Requires external PostgreSQL database (Vercel Postgres, Supabase, etc.)
+- Redis is optional
+
+## Additional Resources
+
+- README.md - Detailed setup and feature overview
+- DOCKER_SETUP.md - Complete Docker deployment guide
+- prisma/schema.prisma - Database schema and relationships
+- env.example - Environment variable template
--- a/DEPLOYMENT_CHECKLIST.md
+++ b/DEPLOYMENT_CHECKLIST.md
@@ -1,269 +0,0 @@
-# 🚀 Deployment Checklist für QR Master
-
-Diese Checkliste enthält alle notwendigen Änderungen vor dem Push nach Gitea und dem Production Deployment.
-
---
-
-## ✅ 1. Environment Variables (.env)
-
-### Basis URLs ändern
-```bash
-# Von:
-NEXT_PUBLIC_APP_URL=http://localhost:3050
-NEXTAUTH_URL=http://localhost:3050
-
-# Zu:
-NEXT_PUBLIC_APP_URL=https://www.qrmaster.net
-NEXTAUTH_URL=https://www.qrmaster.net
-```
-
-### Secrets generieren (falls noch nicht geschehen)
-```bash
-# NEXTAUTH_SECRET (für JWT/Session Encryption)
-openssl rand -base64 32
-
-# IP_SALT (für DSGVO-konforme IP-Hashing)
-openssl rand -base64 32
-```
-
-Bereits generiert:
- ✅ NEXTAUTH_SECRET: `PT8XVydC4v7QluCz/mV1yb7Y3docSFZeFDioJz4ZE98=`
- ✅ IP_SALT: `j/aluIpzsgn5Z6cbF4conM6ApK5cj4jDagkswzfgQPc=`
-
-### Database URLs
-```bash
-# Development (localhost):
-DATABASE_URL="postgresql://postgres:postgres@localhost:5435/qrmaster?schema=public"
-DIRECT_URL="postgresql://postgres:postgres@localhost:5435/qrmaster?schema=public"
-
-# Production (anpassen an deinen Server):
-DATABASE_URL="postgresql://USER:PASSWORD@HOST:5432/qrmaster?schema=public"
-DIRECT_URL="postgresql://USER:PASSWORD@HOST:5432/qrmaster?schema=public"
-```
-
---
-
-## 🔐 2. Google OAuth Configuration
-
-### Redirect URIs in Google Cloud Console hinzufügen
-
-1. Gehe zu: https://console.cloud.google.com/apis/credentials
-2. Wähle deine OAuth 2.0 Client ID: `683784117141-ci1d928jo8f9g6i1isrveflmrinp92l4.apps.googleusercontent.com`
-3. Füge folgende **Authorized redirect URIs** hinzu:
-
-```
-https://www.qrmaster.net/api/auth/callback/google
-```
-
-**Optional** (für Staging/Testing):
-```
-http://localhost:3050/api/auth/callback/google
-https://staging.qrmaster.net/api/auth/callback/google
-```
-
---
-
-## 💳 3. Stripe Configuration
-
-### ⚠️ WICHTIG: Von Test Mode zu Live Mode wechseln
-
-#### Current (Test Mode):
-```bash
-STRIPE_SECRET_KEY=sk_test_51QYL7gP9xM...
-NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY=pk_test_51QYL7gP9xM...
-```
-
-#### Production (Live Mode):
-1. Gehe zu: https://dashboard.stripe.com/
-2. Wechsle von **Test Mode** zu **Live Mode** (Toggle oben rechts)
-3. Hole dir die **Live Keys**:
-   - `API Keys` → `Secret key` (beginnt mit `sk_live_`)
-   - `API Keys` → `Publishable key` (beginnt mit `pk_live_`)
-
-```bash
-# Production Keys:
-STRIPE_SECRET_KEY=sk_live_XXXXX
-NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY=pk_live_XXXXX
-```
-
-#### Webhook Secret (Production)
-1. Erstelle einen neuen Webhook Endpoint: https://dashboard.stripe.com/webhooks
-2. Endpoint URL: `https://www.qrmaster.net/api/webhooks/stripe`
-3. Events to listen:
-   - `checkout.session.completed`
-   - `customer.subscription.updated`
-   - `customer.subscription.deleted`
-   - `invoice.payment_succeeded`
-   - `invoice.payment_failed`
-4. Kopiere den **Signing Secret** (beginnt mit `whsec_`)
-
-```bash
-STRIPE_WEBHOOK_SECRET=whsec_XXXXX
-```
-
-#### Price IDs aktualisieren
-Erstelle Produkte und Preise in **Live Mode**:
-1. https://dashboard.stripe.com/products
-2. Erstelle "Pro" und "Business" Pläne
-3. Kopiere die Price IDs (beginnen mit `price_`)
-
-```bash
-STRIPE_PRICE_ID_PRO_MONTHLY=price_XXXXX
-STRIPE_PRICE_ID_PRO_YEARLY=price_XXXXX
-STRIPE_PRICE_ID_BUSINESS_MONTHLY=price_XXXXX
-STRIPE_PRICE_ID_BUSINESS_YEARLY=price_XXXXX
-```
-
---
-
-## 📧 4. Resend Email Configuration
-
-### Domain Verification
-1. Gehe zu: https://resend.com/domains
-2. Füge Domain hinzu: `qrmaster.net`
-3. Konfiguriere DNS Records (SPF, DKIM, DMARC)
-4. Warte auf Verification
-
-### From Email anpassen
-Aktuell verwendet alle Emails: `onboarding@resend.dev` (Resend's Test Domain)
-
-Nach Domain Verification in `src/lib/email.ts` ändern:
-```typescript
-// Von:
-from: 'Timo from QR Master <onboarding@resend.dev>',
-
-// Zu:
-from: 'Timo from QR Master <hello@qrmaster.net>',
-// oder
-from: 'Timo from QR Master <noreply@qrmaster.net>',
-```
-
---
-
-## 🔍 5. SEO Configuration
-
-### Bereits korrekt konfiguriert ✅
-```bash
-NEXT_PUBLIC_INDEXABLE=true  # ✅ Bereits gesetzt
-```
-
-### Sitemap & robots.txt prüfen
- Sitemap: `https://www.qrmaster.net/sitemap.xml`
- Robots: `https://www.qrmaster.net/robots.txt`
-
-Nach Deployment testen!
-
---
-
-## 📊 6. PostHog Analytics (Optional)
-
-Falls du PostHog nutzt:
-```bash
-NEXT_PUBLIC_POSTHOG_KEY=phc_XXXXX
-NEXT_PUBLIC_POSTHOG_HOST=https://us.i.posthog.com
-```
-
---
-
-## 🐳 7. Docker Deployment
-
-### docker-compose.yml prüfen
-Stelle sicher, dass alle ENV Variables korrekt gemappt sind:
-
-```yaml
-environment:
-  NEXTAUTH_URL: https://www.qrmaster.net
-  NEXT_PUBLIC_APP_URL: https://www.qrmaster.net
-  # ... weitere vars
-```
-
-### Deployment Commands
-```bash
-# Build & Deploy
-docker-compose up -d --build
-
-# Database Migration (nach erstem Deploy)
-docker-compose exec web npm run db:migrate
-
-# Logs checken
-docker-compose logs -f web
-
-# Health Check
-curl https://www.qrmaster.net
-```
-
---
-
-## 🔒 8. Security Checklist
-
- [ ] ✅ NEXTAUTH_SECRET ist gesetzt und sicher (32+ Zeichen)
- [ ] ✅ IP_SALT ist gesetzt und sicher
- [ ] ⚠️ Stripe ist auf **Live Mode** umgestellt
- [ ] ⚠️ Google OAuth Redirect URIs enthalten Production URL
- [ ] ⚠️ Resend Domain ist verifiziert
- [ ] ⚠️ Webhook Secrets sind für Production gesetzt
- [ ] ⚠️ Database URLs zeigen auf Production DB
- [ ] ⚠️ Keine Test/Dev Secrets in Production
-
---
-
-## 📝 9. Vor dem Git Push
-
-### Files prüfen
-```bash
-# .env sollte NICHT committet werden!
-git status
-
-# Falls .env in Git ist:
-git rm --cached .env
-echo ".env" >> .gitignore
-```
-
-### Sensible Daten entfernen
- [ ] Keine API Keys im Code
- [ ] Keine Secrets in Config Files
- [ ] `.env` ist in `.gitignore`
-
---
-
-## 🎯 10. Nach dem Deployment testen
-
-### Funktionen testen
-1. **Google OAuth Login**: https://www.qrmaster.net/login
-2. **QR Code erstellen**: https://www.qrmaster.net/create
-3. **Stripe Checkout**: Testprodukt kaufen mit echten Stripe Test Cards
-4. **Email Delivery**: Password Reset testen
-5. **Analytics**: PostHog Events tracken
-
-### Monitoring
-```bash
-# Server Logs
-docker-compose logs -f
-
-# Database Status
-docker-compose exec db psql -U postgres -d qrmaster -c "SELECT COUNT(*) FROM \"User\";"
-
-# Redis Status
-docker-compose exec redis redis-cli PING
-```
-
---
-
-## 📞 Support Kontakte
-
- **Stripe Support**: https://support.stripe.com
- **Google Cloud Support**: https://support.google.com/cloud
- **Resend Support**: https://resend.com/docs
- **Next.js Docs**: https://nextjs.org/docs
-
---
-
-## ✨ Deployment erfolgreich!
-
-Nach erfolgreichem Deployment:
-1. ✅ Teste alle wichtigen Features
-2. ✅ Monitor Logs für Fehler
-3. ✅ Prüfe Analytics Dashboard
-4. ✅ Backup der Production Database erstellen
-
-**Good luck! 🚀**
--- a/DESIGN.md
+++ b/DESIGN.md
@@ -0,0 +1,322 @@
+# Design System Inspired by Stripe
+
+## 1. Visual Theme & Atmosphere
+
+Stripe's website is the gold standard of fintech design -- a system that manages to feel simultaneously technical and luxurious, precise and warm. The page opens on a clean white canvas (`#ffffff`) with deep navy headings (`#061b31`) and a signature purple (`#533afd`) that functions as both brand anchor and interactive accent. This isn't the cold, clinical purple of enterprise software; it's a rich, saturated violet that reads as confident and premium. The overall impression is of a financial institution redesigned by a world-class type foundry.
+
+The custom `sohne-var` variable font is the defining element of Stripe's visual identity. Every text element enables the OpenType `"ss01"` stylistic set, which modifies character shapes for a distinctly geometric, modern feel. At display sizes (48px-56px), sohne-var runs at weight 300 -- an extraordinarily light weight for headlines that creates an ethereal, almost whispered authority. This is the opposite of the "bold hero headline" convention; Stripe's headlines feel like they don't need to shout. The negative letter-spacing (-1.4px at 56px, -0.96px at 48px) tightens the text into dense, engineered blocks. At smaller sizes, the system also uses weight 300 with proportionally reduced tracking, and tabular numerals via `"tnum"` for financial data display.
+
+What truly distinguishes Stripe is its shadow system. Rather than the flat or single-layer approach of most sites, Stripe uses multi-layer, blue-tinted shadows: the signature `rgba(50,50,93,0.25)` combined with `rgba(0,0,0,0.1)` creates shadows with a cool, almost atmospheric depth -- like elements are floating in a twilight sky. The blue-gray undertone of the primary shadow color (50,50,93) ties directly to the navy-purple brand palette, making even elevation feel on-brand.
+
+**Key Characteristics:**
+- sohne-var with OpenType `"ss01"` on all text -- a custom stylistic set that defines the brand's letterforms
+- Weight 300 as the signature headline weight -- light, confident, anti-convention
+- Negative letter-spacing at display sizes (-1.4px at 56px, progressive relaxation downward)
+- Blue-tinted multi-layer shadows using `rgba(50,50,93,0.25)` -- elevation that feels brand-colored
+- Deep navy (`#061b31`) headings instead of black -- warm, premium, financial-grade
+- Conservative border-radius (4px-8px) -- nothing pill-shaped, nothing harsh
+- Ruby (`#ea2261`) and magenta (`#f96bee`) accents for gradient and decorative elements
+- `SourceCodePro` as the monospace companion for code and technical labels
+
+## 2. Color Palette & Roles
+
+### Primary
+- **Stripe Purple** (`#533afd`): Primary brand color, CTA backgrounds, link text, interactive highlights. A saturated blue-violet that anchors the entire system.
+- **Deep Navy** (`#061b31`): `--hds-color-heading-solid`. Primary heading color. Not black, not gray -- a very dark blue that adds warmth and depth to text.
+- **Pure White** (`#ffffff`): Page background, card surfaces, button text on dark backgrounds.
+
+### Brand & Dark
+- **Brand Dark** (`#1c1e54`): `--hds-color-util-brand-900`. Deep indigo for dark sections, footer backgrounds, and immersive brand moments.
+- **Dark Navy** (`#0d253d`): `--hds-color-core-neutral-975`. The darkest neutral -- almost-black with a blue undertone for maximum depth without harshness.
+
+### Accent Colors
+- **Ruby** (`#ea2261`): `--hds-color-accentColorMode-ruby-icon-solid`. Warm red-pink for icons, alerts, and accent elements.
+- **Magenta** (`#f96bee`): `--hds-color-accentColorMode-magenta-icon-gradientMiddle`. Vivid pink-purple for gradients and decorative highlights.
+- **Magenta Light** (`#ffd7ef`): `--hds-color-util-accent-magenta-100`. Tinted surface for magenta-themed cards and badges.
+
+### Interactive
+- **Primary Purple** (`#533afd`): Primary link color, active states, selected elements.
+- **Purple Hover** (`#4434d4`): Darker purple for hover states on primary elements.
+- **Purple Deep** (`#2e2b8c`): `--hds-color-button-ui-iconHover`. Dark purple for icon hover states.
+- **Purple Light** (`#b9b9f9`): `--hds-color-action-bg-subduedHover`. Soft lavender for subdued hover backgrounds.
+- **Purple Mid** (`#665efd`): `--hds-color-input-selector-text-range`. Range selector and input highlight color.
+
+### Neutral Scale
+- **Heading** (`#061b31`): Primary headings, nav text, strong labels.
+- **Label** (`#273951`): `--hds-color-input-text-label`. Form labels, secondary headings.
+- **Body** (`#64748d`): Secondary text, descriptions, captions.
+- **Success Green** (`#15be53`): Status badges, success indicators (with 0.2-0.4 alpha for backgrounds/borders).
+- **Success Text** (`#108c3d`): Success badge text color.
+- **Lemon** (`#9b6829`): `--hds-color-core-lemon-500`. Warning and highlight accent.
+
+### Surface & Borders
+- **Border Default** (`#e5edf5`): Standard border color for cards, dividers, and containers.
+- **Border Purple** (`#b9b9f9`): Active/selected state borders on buttons and inputs.
+- **Border Soft Purple** (`#d6d9fc`): Subtle purple-tinted borders for secondary elements.
+- **Border Magenta** (`#ffd7ef`): Pink-tinted borders for magenta-themed elements.
+- **Border Dashed** (`#362baa`): Dashed borders for drop zones and placeholder elements.
+
+### Shadow Colors
+- **Shadow Blue** (`rgba(50,50,93,0.25)`): The signature -- blue-tinted primary shadow color.
+- **Shadow Dark Blue** (`rgba(3,3,39,0.25)`): Deeper blue shadow for elevated elements.
+- **Shadow Black** (`rgba(0,0,0,0.1)`): Secondary shadow layer for depth reinforcement.
+- **Shadow Ambient** (`rgba(23,23,23,0.08)`): Soft ambient shadow for subtle elevation.
+- **Shadow Soft** (`rgba(23,23,23,0.06)`): Minimal ambient shadow for light lift.
+
+## 3. Typography Rules
+
+### Font Family
+- **Primary**: `sohne-var`, with fallback: `SF Pro Display`
+- **Monospace**: `SourceCodePro`, with fallback: `SFMono-Regular`
+- **OpenType Features**: `"ss01"` enabled globally on all sohne-var text; `"tnum"` for tabular numbers on financial data and captions.
+
+### Hierarchy
+
+| Role | Font | Size | Weight | Line Height | Letter Spacing | Features | Notes |
+|------|------|------|--------|-------------|----------------|----------|-------|
+| Display Hero | sohne-var | 56px (3.50rem) | 300 | 1.03 (tight) | -1.4px | ss01 | Maximum size, whisper-weight authority |
+| Display Large | sohne-var | 48px (3.00rem) | 300 | 1.15 (tight) | -0.96px | ss01 | Secondary hero headlines |
+| Section Heading | sohne-var | 32px (2.00rem) | 300 | 1.10 (tight) | -0.64px | ss01 | Feature section titles |
+| Sub-heading Large | sohne-var | 26px (1.63rem) | 300 | 1.12 (tight) | -0.26px | ss01 | Card headings, sub-sections |
+| Sub-heading | sohne-var | 22px (1.38rem) | 300 | 1.10 (tight) | -0.22px | ss01 | Smaller section heads |
+| Body Large | sohne-var | 18px (1.13rem) | 300 | 1.40 | normal | ss01 | Feature descriptions, intro text |
+| Body | sohne-var | 16px (1.00rem) | 300-400 | 1.40 | normal | ss01 | Standard reading text |
+| Button | sohne-var | 16px (1.00rem) | 400 | 1.00 (tight) | normal | ss01 | Primary button text |
+| Button Small | sohne-var | 14px (0.88rem) | 400 | 1.00 (tight) | normal | ss01 | Secondary/compact buttons |
+| Link | sohne-var | 14px (0.88rem) | 400 | 1.00 (tight) | normal | ss01 | Navigation links |
+| Caption | sohne-var | 13px (0.81rem) | 400 | normal | normal | ss01 | Small labels, metadata |
+| Caption Small | sohne-var | 12px (0.75rem) | 300-400 | 1.33-1.45 | normal | ss01 | Fine print, timestamps |
+| Caption Tabular | sohne-var | 12px (0.75rem) | 300-400 | 1.33 | -0.36px | tnum | Financial data, numbers |
+| Micro | sohne-var | 10px (0.63rem) | 300 | 1.15 (tight) | 0.1px | ss01 | Tiny labels, axis markers |
+| Micro Tabular | sohne-var | 10px (0.63rem) | 300 | 1.15 (tight) | -0.3px | tnum | Chart data, small numbers |
+| Nano | sohne-var | 8px (0.50rem) | 300 | 1.07 (tight) | normal | ss01 | Smallest labels |
+| Code Body | SourceCodePro | 12px (0.75rem) | 500 | 2.00 (relaxed) | normal | -- | Code blocks, syntax |
+| Code Bold | SourceCodePro | 12px (0.75rem) | 700 | 2.00 (relaxed) | normal | -- | Bold code, keywords |
+| Code Label | SourceCodePro | 12px (0.75rem) | 500 | 2.00 (relaxed) | normal | uppercase | Technical labels |
+| Code Micro | SourceCodePro | 9px (0.56rem) | 500 | 1.00 (tight) | normal | ss01 | Tiny code annotations |
+
+### Principles
+- **Light weight as signature**: Weight 300 at display sizes is Stripe's most distinctive typographic choice. Where others use 600-700 to command attention, Stripe uses lightness as luxury -- the text is so confident it doesn't need weight to be authoritative.
+- **ss01 everywhere**: The `"ss01"` stylistic set is non-negotiable. It modifies specific glyphs (likely alternate `a`, `g`, `l` forms) to create a more geometric, contemporary feel across all sohne-var text.
+- **Two OpenType modes**: `"ss01"` for display/body text, `"tnum"` for tabular numerals in financial data. These never overlap -- a number in a paragraph uses ss01, a number in a data table uses tnum.
+- **Progressive tracking**: Letter-spacing tightens proportionally with size: -1.4px at 56px, -0.96px at 48px, -0.64px at 32px, -0.26px at 26px, normal at 16px and below.
+- **Two-weight simplicity**: Primarily 300 (body and headings) and 400 (UI/buttons). No bold (700) in the primary font -- SourceCodePro uses 500/700 for code contrast.
+
+## 4. Component Stylings
+
+### Buttons
+
+**Primary Purple**
+- Background: `#533afd`
+- Text: `#ffffff`
+- Padding: 8px 16px
+- Radius: 4px
+- Font: 16px sohne-var weight 400, `"ss01"`
+- Hover: `#4434d4` background
+- Use: Primary CTA ("Start now", "Contact sales")
+
+**Ghost / Outlined**
+- Background: transparent
+- Text: `#533afd`
+- Padding: 8px 16px
+- Radius: 4px
+- Border: `1px solid #b9b9f9`
+- Font: 16px sohne-var weight 400, `"ss01"`
+- Hover: background shifts to `rgba(83,58,253,0.05)`
+- Use: Secondary actions
+
+**Transparent Info**
+- Background: transparent
+- Text: `#2874ad`
+- Padding: 8px 16px
+- Radius: 4px
+- Border: `1px solid rgba(43,145,223,0.2)`
+- Use: Tertiary/info-level actions
+
+**Neutral Ghost**
+- Background: transparent (`rgba(255,255,255,0)`)
+- Text: `rgba(16,16,16,0.3)`
+- Padding: 8px 16px
+- Radius: 4px
+- Outline: `1px solid rgb(212,222,233)`
+- Use: Disabled or muted actions
+
+### Cards & Containers
+- Background: `#ffffff`
+- Border: `1px solid #e5edf5` (standard) or `1px solid #061b31` (dark accent)
+- Radius: 4px (tight), 5px (standard), 6px (comfortable), 8px (featured)
+- Shadow (standard): `rgba(50,50,93,0.25) 0px 30px 45px -30px, rgba(0,0,0,0.1) 0px 18px 36px -18px`
+- Shadow (ambient): `rgba(23,23,23,0.08) 0px 15px 35px 0px`
+- Hover: shadow intensifies, often adding the blue-tinted layer
+
+### Badges / Tags / Pills
+**Neutral Pill**
+- Background: `#ffffff`
+- Text: `#000000`
+- Padding: 0px 6px
+- Radius: 4px
+- Border: `1px solid #f6f9fc`
+- Font: 11px weight 400
+
+**Success Badge**
+- Background: `rgba(21,190,83,0.2)`
+- Text: `#108c3d`
+- Padding: 1px 6px
+- Radius: 4px
+- Border: `1px solid rgba(21,190,83,0.4)`
+- Font: 10px weight 300
+
+### Inputs & Forms
+- Border: `1px solid #e5edf5`
+- Radius: 4px
+- Focus: `1px solid #533afd` or purple ring
+- Label: `#273951`, 14px sohne-var
+- Text: `#061b31`
+- Placeholder: `#64748d`
+
+### Navigation
+- Clean horizontal nav on white, sticky with blur backdrop
+- Brand logotype left-aligned
+- Links: sohne-var 14px weight 400, `#061b31` text with `"ss01"`
+- Radius: 6px on nav container
+- CTA: purple button right-aligned ("Sign in", "Start now")
+- Mobile: hamburger toggle with 6px radius
+
+### Decorative Elements
+**Dashed Borders**
+- `1px dashed #362baa` (purple) for placeholder/drop zones
+- `1px dashed #ffd7ef` (magenta) for magenta-themed decorative borders
+
+**Gradient Accents**
+- Ruby-to-magenta gradients (`#ea2261` to `#f96bee`) for hero decorations
+- Brand dark sections use `#1c1e54` backgrounds with white text
+
+## 5. Layout Principles
+
+### Spacing System
+- Base unit: 8px
+- Scale: 1px, 2px, 4px, 6px, 8px, 10px, 11px, 12px, 14px, 16px, 18px, 20px
+- Notable: The scale is dense at the small end (every 2px from 4-12), reflecting Stripe's precision-oriented UI for financial data
+
+### Grid & Container
+- Max content width: approximately 1080px
+- Hero: centered single-column with generous padding, lightweight headlines
+- Feature sections: 2-3 column grids for feature cards
+- Full-width dark sections with `#1c1e54` background for brand immersion
+- Code/dashboard previews as contained cards with blue-tinted shadows
+
+### Whitespace Philosophy
+- **Precision spacing**: Unlike the vast emptiness of minimalist systems, Stripe uses measured, purposeful whitespace. Every gap is a deliberate typographic choice.
+- **Dense data, generous chrome**: Financial data displays (tables, charts) are tightly packed, but the UI chrome around them is generously spaced. This creates a sense of controlled density -- like a well-organized spreadsheet in a beautiful frame.
+- **Section rhythm**: White sections alternate with dark brand sections (`#1c1e54`), creating a dramatic light/dark cadence that prevents monotony without introducing arbitrary color.
+
+### Border Radius Scale
+- Micro (1px): Fine-grained elements, subtle rounding
+- Standard (4px): Buttons, inputs, badges, cards -- the workhorse
+- Comfortable (5px): Standard card containers
+- Relaxed (6px): Navigation, larger interactive elements
+- Large (8px): Featured cards, hero elements
+- Compound: `0px 0px 6px 6px` for bottom-rounded containers (tab panels, dropdown footers)
+
+## 6. Depth & Elevation
+
+| Level | Treatment | Use |
+|-------|-----------|-----|
+| Flat (Level 0) | No shadow | Page background, inline text |
+| Ambient (Level 1) | `rgba(23,23,23,0.06) 0px 3px 6px` | Subtle card lift, hover hints |
+| Standard (Level 2) | `rgba(23,23,23,0.08) 0px 15px 35px` | Standard cards, content panels |
+| Elevated (Level 3) | `rgba(50,50,93,0.25) 0px 30px 45px -30px, rgba(0,0,0,0.1) 0px 18px 36px -18px` | Featured cards, dropdowns, popovers |
+| Deep (Level 4) | `rgba(3,3,39,0.25) 0px 14px 21px -14px, rgba(0,0,0,0.1) 0px 8px 17px -8px` | Modals, floating panels |
+| Ring (Accessibility) | `2px solid #533afd` outline | Keyboard focus ring |
+
+**Shadow Philosophy**: Stripe's shadow system is built on a principle of chromatic depth. Where most design systems use neutral gray or black shadows, Stripe's primary shadow color (`rgba(50,50,93,0.25)`) is a deep blue-gray that echoes the brand's navy palette. This creates shadows that don't just add depth -- they add brand atmosphere. The multi-layer approach pairs this blue-tinted shadow with a pure black secondary layer (`rgba(0,0,0,0.1)`) at a different offset, creating a parallax-like depth where the branded shadow sits farther from the element and the neutral shadow sits closer. The negative spread values (-30px, -18px) ensure shadows don't extend beyond the element's footprint horizontally, keeping elevation vertical and controlled.
+
+### Decorative Depth
+- Dark brand sections (`#1c1e54`) create immersive depth through background color contrast
+- Gradient overlays with ruby-to-magenta transitions for hero decorations
+- Shadow color `rgba(0,55,112,0.08)` (`--hds-color-shadow-sm-top`) for top-edge shadows on sticky elements
+
+## 7. Do's and Don'ts
+
+### Do
+- Use sohne-var with `"ss01"` on every text element -- the stylistic set IS the brand
+- Use weight 300 for all headlines and body text -- lightness is the signature
+- Apply blue-tinted shadows (`rgba(50,50,93,0.25)`) for all elevated elements
+- Use `#061b31` (deep navy) for headings instead of `#000000` -- the warmth matters
+- Keep border-radius between 4px-8px -- conservative rounding is intentional
+- Use `"tnum"` for any tabular/financial number display
+- Layer shadows: blue-tinted far + neutral close for depth parallax
+- Use `#533afd` purple as the primary interactive/CTA color
+
+### Don't
+- Don't use weight 600-700 for sohne-var headlines -- weight 300 is the brand voice
+- Don't use large border-radius (12px+, pill shapes) on cards or buttons -- Stripe is conservative
+- Don't use neutral gray shadows -- always tint with blue (`rgba(50,50,93,...)`)
+- Don't skip `"ss01"` on any sohne-var text -- the alternate glyphs define the personality
+- Don't use pure black (`#000000`) for headings -- always `#061b31` deep navy
+- Don't use warm accent colors (orange, yellow) for interactive elements -- purple is primary
+- Don't apply positive letter-spacing at display sizes -- Stripe tracks tight
+- Don't use the magenta/ruby accents for buttons or links -- they're decorative/gradient only
+
+## 8. Responsive Behavior
+
+### Breakpoints
+| Name | Width | Key Changes |
+|------|-------|-------------|
+| Mobile | <640px | Single column, reduced heading sizes, stacked cards |
+| Tablet | 640-1024px | 2-column grids, moderate padding |
+| Desktop | 1024-1280px | Full layout, 3-column feature grids |
+| Large Desktop | >1280px | Centered content with generous margins |
+
+### Touch Targets
+- Buttons use comfortable padding (8px-16px vertical)
+- Navigation links at 14px with adequate spacing
+- Badges have 6px horizontal padding minimum for tap targets
+- Mobile nav toggle with 6px radius button
+
+### Collapsing Strategy
+- Hero: 56px display -> 32px on mobile, weight 300 maintained
+- Navigation: horizontal links + CTAs -> hamburger toggle
+- Feature cards: 3-column -> 2-column -> single column stacked
+- Dark brand sections: maintain full-width treatment, reduce internal padding
+- Financial data tables: horizontal scroll on mobile
+- Section spacing: 64px+ -> 40px on mobile
+- Typography scale compresses: 56px -> 48px -> 32px hero sizes across breakpoints
+
+### Image Behavior
+- Dashboard/product screenshots maintain blue-tinted shadow at all sizes
+- Hero gradient decorations simplify on mobile
+- Code blocks maintain `SourceCodePro` treatment, may horizontally scroll
+- Card images maintain consistent 4px-6px border-radius
+
+## 9. Agent Prompt Guide
+
+### Quick Color Reference
+- Primary CTA: Stripe Purple (`#533afd`)
+- CTA Hover: Purple Dark (`#4434d4`)
+- Background: Pure White (`#ffffff`)
+- Heading text: Deep Navy (`#061b31`)
+- Body text: Slate (`#64748d`)
+- Label text: Dark Slate (`#273951`)
+- Border: Soft Blue (`#e5edf5`)
+- Link: Stripe Purple (`#533afd`)
+- Dark section: Brand Dark (`#1c1e54`)
+- Success: Green (`#15be53`)
+- Accent decorative: Ruby (`#ea2261`), Magenta (`#f96bee`)
+
+### Example Component Prompts
+- "Create a hero section on white background. Headline at 48px sohne-var weight 300, line-height 1.15, letter-spacing -0.96px, color #061b31, font-feature-settings 'ss01'. Subtitle at 18px weight 300, line-height 1.40, color #64748d. Purple CTA button (#533afd, 4px radius, 8px 16px padding, white text) and ghost button (transparent, 1px solid #b9b9f9, #533afd text, 4px radius)."
+- "Design a card: white background, 1px solid #e5edf5 border, 6px radius. Shadow: rgba(50,50,93,0.25) 0px 30px 45px -30px, rgba(0,0,0,0.1) 0px 18px 36px -18px. Title at 22px sohne-var weight 300, letter-spacing -0.22px, color #061b31, 'ss01'. Body at 16px weight 300, #64748d."
+- "Build a success badge: rgba(21,190,83,0.2) background, #108c3d text, 4px radius, 1px 6px padding, 10px sohne-var weight 300, border 1px solid rgba(21,190,83,0.4)."
+- "Create navigation: white sticky header with backdrop-filter blur(12px). sohne-var 14px weight 400 for links, #061b31 text, 'ss01'. Purple CTA 'Start now' right-aligned (#533afd bg, white text, 4px radius). Nav container 6px radius."
+- "Design a dark brand section: #1c1e54 background, white text. Headline 32px sohne-var weight 300, letter-spacing -0.64px, 'ss01'. Body 16px weight 300, rgba(255,255,255,0.7). Cards inside use rgba(255,255,255,0.1) border with 6px radius."
+
+### Iteration Guide
+1. Always enable `font-feature-settings: "ss01"` on sohne-var text -- this is the brand's typographic DNA
+2. Weight 300 is the default; use 400 only for buttons/links/navigation
+3. Shadow formula: `rgba(50,50,93,0.25) 0px Y1 B1 -S1, rgba(0,0,0,0.1) 0px Y2 B2 -S2` where Y1/B1 are larger (far shadow) and Y2/B2 are smaller (near shadow)
+4. Heading color is `#061b31` (deep navy), body is `#64748d` (slate), labels are `#273951` (dark slate)
+5. Border-radius stays in the 4px-8px range -- never use pill shapes or large rounding
+6. Use `"tnum"` for any numbers in tables, charts, or financial displays
+7. Dark sections use `#1c1e54` -- not black, not gray, but a deep branded indigo
+8. SourceCodePro for code at 12px/500 with 2.00 line-height (very generous for readability)
--- a/DOCKER_SETUP.md
+++ b/DOCKER_SETUP.md
@@ -1,461 +1,461 @@
-# 🐳 Docker Setup Guide for QR Master
-
-Complete guide for setting up and running QR Master with Docker and PostgreSQL.
-
-## Prerequisites
-
- Docker Desktop (Windows/Mac) or Docker Engine (Linux)
- Docker Compose V2
- Git
- Node.js 18+ (for local development)
-
-## 🚀 Getting Started
-
-### Option 1: Development Mode (Recommended for Development)
-
-Run only the database services in Docker and the Next.js app on your host machine:
-
-1. **Clone the repository**
-   ```bash
-   git clone <your-repo-url>
-   cd QRMASTER
-   ```
-
-2. **Install dependencies**
-   ```bash
-   npm install
-   ```
-
-3. **Set up environment variables**
-   ```bash
-   cp env.example .env
-   ```
-   Edit `.env` and update the values, especially:
-   - `NEXTAUTH_SECRET` (generate with: `openssl rand -base64 32`)
-   - `IP_SALT` (generate with: `openssl rand -base64 32`)
-
-4. **Start database services**
-   ```bash
-   npm run docker:dev
-   ```
-   This starts PostgreSQL, Redis, and Adminer.
-
-5. **Run database migrations**
-   ```bash
-   npm run db:migrate
-   ```
-
-6. **Seed the database (optional)**
-   ```bash
-   npm run db:seed
-   ```
-
-7. **Start the development server**
-   ```bash
-   npm run dev
-   ```
-
-8. **Access the application**
-   - **App**: http://localhost:3050
-   - **Database UI (Adminer)**: http://localhost:8080
-     - System: PostgreSQL
-     - Server: db
-     - Username: postgres
-     - Password: postgres
-     - Database: qrmaster
-
-### Option 2: Full Production Mode
-
-Run everything in Docker containers:
-
-1. **Clone and configure**
-   ```bash
-   git clone <your-repo-url>
-   cd QRMASTER
-   cp env.example .env
-   ```
-
-2. **Update environment variables in `.env`**
-   Make sure to set strong secrets in production!
-
-3. **Build and start all services**
-   ```bash
-   npm run docker:prod
-   ```
-
-4. **Run migrations inside the container**
-   ```bash
-   docker-compose exec web npx prisma migrate deploy
-   ```
-
-5. **Access the application**
-   - **App**: http://localhost:3050
-
-## 📦 What Gets Installed
-
-### Services
-
-1. **PostgreSQL 16** - Main database
-   - Port: 5432
-   - Database: qrmaster
-   - User: postgres
-   - Password: postgres (change in production!)
-
-2. **Redis 7** - Caching and rate limiting
-   - Port: 6379
-   - Max memory: 256MB with LRU eviction
-   - Persistence: AOF enabled
-
-3. **Next.js App** - The QR Master application
-   - Port: 3000
-   - Built with production optimizations
-
-4. **Adminer** - Database management UI (dev only)
-   - Port: 8080
-   - Lightweight alternative to pgAdmin
-
-## 🗄️ Database Management
-
-### Prisma Commands
-
-```bash
-# Generate Prisma Client
-npm run db:generate
-
-# Create a new migration
-npm run db:migrate
-
-# Deploy migrations (production)
-npm run db:deploy
-
-# Seed the database
-npm run db:seed
-
-# Open Prisma Studio
-npm run db:studio
-```
-
-### Direct PostgreSQL Access
-
-```bash
-# Connect to PostgreSQL
-docker-compose exec db psql -U postgres -d qrmaster
-
-# Backup database
-docker-compose exec db pg_dump -U postgres qrmaster > backup_$(date +%Y%m%d).sql
-
-# Restore database
-docker-compose exec -T db psql -U postgres qrmaster < backup.sql
-```
-
-## 🔧 Docker Commands
-
-### Starting Services
-
-```bash
-# Development mode (database only)
-npm run docker:dev
-# or
-docker-compose -f docker-compose.dev.yml up -d
-
-# Production mode (full stack)
-npm run docker:prod
-# or
-docker-compose up -d --build
-
-# Production with database UI
-docker-compose --profile dev up -d
-```
-
-### Stopping Services
-
-```bash
-# Stop all services
-npm run docker:stop
-# or
-docker-compose down
-
-# Stop and remove volumes (⚠️ deletes data!)
-docker-compose down -v
-```
-
-### Viewing Logs
-
-```bash
-# All services
-docker-compose logs -f
-
-# Specific service
-docker-compose logs -f web
-docker-compose logs -f db
-docker-compose logs -f redis
-```
-
-### Rebuilding
-
-```bash
-# Rebuild the web application
-docker-compose build web
-
-# Rebuild without cache
-docker-compose build --no-cache web
-
-# Rebuild and restart
-docker-compose up -d --build web
-```
-
-## 🌍 Environment Variables
-
-### Required Variables
-
-```env
-# Database (automatically set for Docker)
-DATABASE_URL=postgresql://postgres:postgres@db:5432/qrmaster?schema=public
-
-# NextAuth
-NEXTAUTH_URL=http://localhost:3050
-NEXTAUTH_SECRET=<generate-with-openssl-rand-base64-32>
-
-# Security
-IP_SALT=<generate-with-openssl-rand-base64-32>
-```
-
-### Optional Variables
-
-```env
-# OAuth (Google)
-GOOGLE_CLIENT_ID=
-GOOGLE_CLIENT_SECRET=
-
-# Redis (automatically set for Docker)
-REDIS_URL=redis://redis:6379
-
-# Features
-ENABLE_DEMO=false
-```
-
-### Generating Secrets
-
-```bash
-# On Linux/Mac
-openssl rand -base64 32
-
-# On Windows (PowerShell)
-[Convert]::ToBase64String((1..32 | ForEach-Object { Get-Random -Maximum 256 }))
-```
-
-## 🔍 Health Checks
-
-All services include health checks:
-
-```bash
-# Check status of all services
-docker-compose ps
-
-# Check database health
-docker-compose exec db pg_isready -U postgres
-
-# Check Redis health
-docker-compose exec redis redis-cli ping
-
-# Check web app health
-curl http://localhost:3050
-```
-
-## 🐛 Troubleshooting
-
-### Database Connection Failed
-
-```bash
-# Check database is running
-docker-compose ps db
-
-# Check database logs
-docker-compose logs db
-
-# Restart database
-docker-compose restart db
-
-# Test connection
-docker-compose exec db psql -U postgres -d qrmaster -c "SELECT version();"
-```
-
-### Port Already in Use
-
-```bash
-# Windows - find process using port
-netstat -ano | findstr :3050
-
-# Linux/Mac - find process using port
-lsof -i :3050
-
-# Kill the process or change the port in docker-compose.yml
-```
-
-### Migration Errors
-
-```bash
-# Reset the database (⚠️ deletes all data!)
-docker-compose exec web npx prisma migrate reset
-
-# Or manually
-docker-compose down -v
-docker-compose up -d db redis
-npm run db:migrate
-```
-
-### Container Won't Start
-
-```bash
-# Remove all containers and volumes
-docker-compose down -v
-
-# Remove dangling images
-docker image prune
-
-# Rebuild from scratch
-docker-compose build --no-cache
-docker-compose up -d
-```
-
-### Prisma Client Not Generated
-
-```bash
-# Generate Prisma Client
-npm run db:generate
-
-# Or in Docker
-docker-compose exec web npx prisma generate
-```
-
-## 🔐 Production Checklist
-
-Before deploying to production:
-
- [ ] Change PostgreSQL password
- [ ] Generate strong `NEXTAUTH_SECRET`
- [ ] Generate strong `IP_SALT`
- [ ] Set proper `NEXTAUTH_URL` (your domain)
- [ ] Configure OAuth credentials (if using)
- [ ] Set up database backups
- [ ] Configure Redis persistence
- [ ] Set up monitoring and logging
- [ ] Enable HTTPS/SSL
- [ ] Review and adjust rate limits
- [ ] Set up a reverse proxy (nginx/Traefik)
- [ ] Configure firewall rules
- [ ] Set up automated database backups
-
-## 📊 Monitoring
-
-### Resource Usage
-
-```bash
-# View resource usage
-docker stats
-
-# View specific container
-docker stats qrmaster-web qrmaster-db qrmaster-redis
-```
-
-### Database Size
-
-```bash
-# Check database size
-docker-compose exec db psql -U postgres -d qrmaster -c "
-SELECT 
-    pg_size_pretty(pg_database_size('qrmaster')) as db_size,
-    pg_size_pretty(pg_total_relation_size('\"QRCode\"')) as qrcode_table_size;
-"
-```
-
-### Redis Info
-
-```bash
-# Get Redis info
-docker-compose exec redis redis-cli info
-
-# Get memory usage
-docker-compose exec redis redis-cli info memory
-```
-
-## 🔄 Backup and Recovery
-
-### Automated Backups
-
-Create a backup script `backup.sh`:
-
-```bash
-#!/bin/bash
-BACKUP_DIR="./backups"
-TIMESTAMP=$(date +%Y%m%d_%H%M%S)
-
-mkdir -p $BACKUP_DIR
-
-# Backup database
-docker-compose exec -T db pg_dump -U postgres qrmaster > "$BACKUP_DIR/qrmaster_$TIMESTAMP.sql"
-
-# Backup Redis
-docker-compose exec redis redis-cli BGSAVE
-
-echo "Backup completed: $BACKUP_DIR/qrmaster_$TIMESTAMP.sql"
-```
-
-### Restore from Backup
-
-```bash
-# Stop the web service
-docker-compose stop web
-
-# Restore database
-cat backup_20241013.sql | docker-compose exec -T db psql -U postgres qrmaster
-
-# Restart
-docker-compose start web
-```
-
-## 🚀 Performance Tips
-
-1. **Increase PostgreSQL shared buffers** (in production):
-   Edit `docker-compose.yml`:
-   ```yaml
-   db:
-     command: postgres -c shared_buffers=256MB -c max_connections=100
-   ```
-
-2. **Enable Redis persistence**:
-   Already configured with AOF in docker-compose.yml
-
-3. **Use connection pooling**:
-   Prisma already includes connection pooling
-
-4. **Monitor slow queries**:
-   ```bash
-   docker-compose exec db psql -U postgres -d qrmaster -c "
-   SELECT query, mean_exec_time, calls 
-   FROM pg_stat_statements 
-   ORDER BY mean_exec_time DESC 
-   LIMIT 10;"
-   ```
-
-## 📚 Additional Resources
-
- [Docker Documentation](https://docs.docker.com/)
- [PostgreSQL Documentation](https://www.postgresql.org/docs/)
- [Redis Documentation](https://redis.io/documentation)
- [Prisma Documentation](https://www.prisma.io/docs/)
- [Next.js Documentation](https://nextjs.org/docs)
-
-## 🆘 Getting Help
-
-If you encounter issues:
-
-1. Check the logs: `docker-compose logs -f`
-2. Check service health: `docker-compose ps`
-3. Review this guide
-4. Check the `docker/README.md` for more details
-
---
-
-**Happy coding! 🎉**
-
+# 🐳 Docker Setup Guide for QR Master
+
+Complete guide for setting up and running QR Master with Docker and PostgreSQL.
+
+## Prerequisites
+
+- Docker Desktop (Windows/Mac) or Docker Engine (Linux)
+- Docker Compose V2
+- Git
+- Node.js 18+ (for local development)
+
+## 🚀 Getting Started
+
+### Option 1: Development Mode (Recommended for Development)
+
+Run only the database services in Docker and the Next.js app on your host machine:
+
+1. **Clone the repository**
+   ```bash
+   git clone <your-repo-url>
+   cd QRMASTER
+   ```
+
+2. **Install dependencies**
+   ```bash
+   npm install
+   ```
+
+3. **Set up environment variables**
+   ```bash
+   cp env.example .env
+   ```
+   Edit `.env` and update the values, especially:
+   - `NEXTAUTH_SECRET` (generate with: `openssl rand -base64 32`)
+   - `IP_SALT` (generate with: `openssl rand -base64 32`)
+
+4. **Start database services**
+   ```bash
+   npm run docker:dev
+   ```
+   This starts PostgreSQL, Redis, and Adminer.
+
+5. **Run database migrations**
+   ```bash
+   npm run db:migrate
+   ```
+
+6. **Seed the database (optional)**
+   ```bash
+   npm run db:seed
+   ```
+
+7. **Start the development server**
+   ```bash
+   npm run dev
+   ```
+
+8. **Access the application**
+   - **App**: http://localhost:3050
+   - **Database UI (Adminer)**: http://localhost:8080
+     - System: PostgreSQL
+     - Server: db
+     - Username: postgres
+     - Password: postgres
+     - Database: qrmaster
+
+### Option 2: Full Production Mode
+
+Run everything in Docker containers:
+
+1. **Clone and configure**
+   ```bash
+   git clone <your-repo-url>
+   cd QRMASTER
+   cp env.example .env
+   ```
+
+2. **Update environment variables in `.env`**
+   Make sure to set strong secrets in production!
+
+3. **Build and start all services**
+   ```bash
+   npm run docker:prod
+   ```
+
+4. **Run migrations inside the container**
+   ```bash
+   docker-compose exec web npx prisma migrate deploy
+   ```
+
+5. **Access the application**
+   - **App**: http://localhost:3050
+
+## 📦 What Gets Installed
+
+### Services
+
+1. **PostgreSQL 16** - Main database
+   - Port: 5432
+   - Database: qrmaster
+   - User: postgres
+   - Password: postgres (change in production!)
+
+2. **Redis 7** - Caching and rate limiting
+   - Port: 6379
+   - Max memory: 256MB with LRU eviction
+   - Persistence: AOF enabled
+
+3. **Next.js App** - The QR Master application
+   - Port: 3000
+   - Built with production optimizations
+
+4. **Adminer** - Database management UI (dev only)
+   - Port: 8080
+   - Lightweight alternative to pgAdmin
+
+## 🗄️ Database Management
+
+### Prisma Commands
+
+```bash
+# Generate Prisma Client
+npm run db:generate
+
+# Create a new migration
+npm run db:migrate
+
+# Deploy migrations (production)
+npm run db:deploy
+
+# Seed the database
+npm run db:seed
+
+# Open Prisma Studio
+npm run db:studio
+```
+
+### Direct PostgreSQL Access
+
+```bash
+# Connect to PostgreSQL
+docker-compose exec db psql -U postgres -d qrmaster
+
+# Backup database
+docker-compose exec db pg_dump -U postgres qrmaster > backup_$(date +%Y%m%d).sql
+
+# Restore database
+docker-compose exec -T db psql -U postgres qrmaster < backup.sql
+```
+
+## 🔧 Docker Commands
+
+### Starting Services
+
+```bash
+# Development mode (database only)
+npm run docker:dev
+# or
+docker-compose -f docker-compose.dev.yml up -d
+
+# Production mode (full stack)
+npm run docker:prod
+# or
+docker-compose up -d --build
+
+# Production with database UI
+docker-compose --profile dev up -d
+```
+
+### Stopping Services
+
+```bash
+# Stop all services
+npm run docker:stop
+# or
+docker-compose down
+
+# Stop and remove volumes (⚠️ deletes data!)
+docker-compose down -v
+```
+
+### Viewing Logs
+
+```bash
+# All services
+docker-compose logs -f
+
+# Specific service
+docker-compose logs -f web
+docker-compose logs -f db
+docker-compose logs -f redis
+```
+
+### Rebuilding
+
+```bash
+# Rebuild the web application
+docker-compose build web
+
+# Rebuild without cache
+docker-compose build --no-cache web
+
+# Rebuild and restart
+docker-compose up -d --build web
+```
+
+## 🌍 Environment Variables
+
+### Required Variables
+
+```env
+# Database (automatically set for Docker)
+DATABASE_URL=postgresql://postgres:postgres@db:5432/qrmaster?schema=public
+
+# NextAuth
+NEXTAUTH_URL=http://localhost:3050
+NEXTAUTH_SECRET=<generate-with-openssl-rand-base64-32>
+
+# Security
+IP_SALT=<generate-with-openssl-rand-base64-32>
+```
+
+### Optional Variables
+
+```env
+# OAuth (Google)
+GOOGLE_CLIENT_ID=
+GOOGLE_CLIENT_SECRET=
+
+# Redis (automatically set for Docker)
+REDIS_URL=redis://redis:6379
+
+# Features
+ENABLE_DEMO=false
+```
+
+### Generating Secrets
+
+```bash
+# On Linux/Mac
+openssl rand -base64 32
+
+# On Windows (PowerShell)
+[Convert]::ToBase64String((1..32 | ForEach-Object { Get-Random -Maximum 256 }))
+```
+
+## 🔍 Health Checks
+
+All services include health checks:
+
+```bash
+# Check status of all services
+docker-compose ps
+
+# Check database health
+docker-compose exec db pg_isready -U postgres
+
+# Check Redis health
+docker-compose exec redis redis-cli ping
+
+# Check web app health
+curl http://localhost:3050
+```
+
+## 🐛 Troubleshooting
+
+### Database Connection Failed
+
+```bash
+# Check database is running
+docker-compose ps db
+
+# Check database logs
+docker-compose logs db
+
+# Restart database
+docker-compose restart db
+
+# Test connection
+docker-compose exec db psql -U postgres -d qrmaster -c "SELECT version();"
+```
+
+### Port Already in Use
+
+```bash
+# Windows - find process using port
+netstat -ano | findstr :3050
+
+# Linux/Mac - find process using port
+lsof -i :3050
+
+# Kill the process or change the port in docker-compose.yml
+```
+
+### Migration Errors
+
+```bash
+# Reset the database (⚠️ deletes all data!)
+docker-compose exec web npx prisma migrate reset
+
+# Or manually
+docker-compose down -v
+docker-compose up -d db redis
+npm run db:migrate
+```
+
+### Container Won't Start
+
+```bash
+# Remove all containers and volumes
+docker-compose down -v
+
+# Remove dangling images
+docker image prune
+
+# Rebuild from scratch
+docker-compose build --no-cache
+docker-compose up -d
+```
+
+### Prisma Client Not Generated
+
+```bash
+# Generate Prisma Client
+npm run db:generate
+
+# Or in Docker
+docker-compose exec web npx prisma generate
+```
+
+## 🔐 Production Checklist
+
+Before deploying to production:
+
+- [ ] Change PostgreSQL password
+- [ ] Generate strong `NEXTAUTH_SECRET`
+- [ ] Generate strong `IP_SALT`
+- [ ] Set proper `NEXTAUTH_URL` (your domain)
+- [ ] Configure OAuth credentials (if using)
+- [ ] Set up database backups
+- [ ] Configure Redis persistence
+- [ ] Set up monitoring and logging
+- [ ] Enable HTTPS/SSL
+- [ ] Review and adjust rate limits
+- [ ] Set up a reverse proxy (nginx/Traefik)
+- [ ] Configure firewall rules
+- [ ] Set up automated database backups
+
+## 📊 Monitoring
+
+### Resource Usage
+
+```bash
+# View resource usage
+docker stats
+
+# View specific container
+docker stats qrmaster-web qrmaster-db qrmaster-redis
+```
+
+### Database Size
+
+```bash
+# Check database size
+docker-compose exec db psql -U postgres -d qrmaster -c "
+SELECT 
+    pg_size_pretty(pg_database_size('qrmaster')) as db_size,
+    pg_size_pretty(pg_total_relation_size('\"QRCode\"')) as qrcode_table_size;
+"
+```
+
+### Redis Info
+
+```bash
+# Get Redis info
+docker-compose exec redis redis-cli info
+
+# Get memory usage
+docker-compose exec redis redis-cli info memory
+```
+
+## 🔄 Backup and Recovery
+
+### Automated Backups
+
+Create a backup script `backup.sh`:
+
+```bash
+#!/bin/bash
+BACKUP_DIR="./backups"
+TIMESTAMP=$(date +%Y%m%d_%H%M%S)
+
+mkdir -p $BACKUP_DIR
+
+# Backup database
+docker-compose exec -T db pg_dump -U postgres qrmaster > "$BACKUP_DIR/qrmaster_$TIMESTAMP.sql"
+
+# Backup Redis
+docker-compose exec redis redis-cli BGSAVE
+
+echo "Backup completed: $BACKUP_DIR/qrmaster_$TIMESTAMP.sql"
+```
+
+### Restore from Backup
+
+```bash
+# Stop the web service
+docker-compose stop web
+
+# Restore database
+cat backup_20241013.sql | docker-compose exec -T db psql -U postgres qrmaster
+
+# Restart
+docker-compose start web
+```
+
+## 🚀 Performance Tips
+
+1. **Increase PostgreSQL shared buffers** (in production):
+   Edit `docker-compose.yml`:
+   ```yaml
+   db:
+     command: postgres -c shared_buffers=256MB -c max_connections=100
+   ```
+
+2. **Enable Redis persistence**:
+   Already configured with AOF in docker-compose.yml
+
+3. **Use connection pooling**:
+   Prisma already includes connection pooling
+
+4. **Monitor slow queries**:
+   ```bash
+   docker-compose exec db psql -U postgres -d qrmaster -c "
+   SELECT query, mean_exec_time, calls 
+   FROM pg_stat_statements 
+   ORDER BY mean_exec_time DESC 
+   LIMIT 10;"
+   ```
+
+## 📚 Additional Resources
+
+- [Docker Documentation](https://docs.docker.com/)
+- [PostgreSQL Documentation](https://www.postgresql.org/docs/)
+- [Redis Documentation](https://redis.io/documentation)
+- [Prisma Documentation](https://www.prisma.io/docs/)
+- [Next.js Documentation](https://nextjs.org/docs)
+
+## 🆘 Getting Help
+
+If you encounter issues:
+
+1. Check the logs: `docker-compose logs -f`
+2. Check service health: `docker-compose ps`
+3. Review this guide
+4. Check the `docker/README.md` for more details
+
+---
+
+**Happy coding! 🎉**
+
--- a/134
+++ b/134
@@ -1,64 +1,70 @@
-# ---- deps ----
-FROM node:20-alpine AS deps
-# Install OpenSSL for Prisma
-RUN apk add --no-cache openssl
-WORKDIR /app
-COPY package.json package-lock.json* pnpm-lock.yaml* yarn.lock* .npmrc* ./
-# Copy prisma schema for postinstall script
-COPY prisma ./prisma
-RUN \
-  if [ -f pnpm-lock.yaml ]; then \
-    npm i -g pnpm && pnpm i --frozen-lockfile; \
-  elif [ -f yarn.lock ]; then \
-    yarn --frozen-lockfile; \
-  elif [ -f package-lock.json ]; then \
-    npm ci; \
-  else \
-    npm install --legacy-peer-deps; \
-  fi
-
-# ---- builder ----
-FROM node:20-alpine AS builder
-# Install OpenSSL for Prisma
-RUN apk add --no-cache openssl
-WORKDIR /app
-COPY --from=deps /app/node_modules ./node_modules
-COPY . .
-ENV NEXT_TELEMETRY_DISABLED=1
-# Add build-time environment variables with defaults
-ENV DATABASE_URL="postgresql://postgres:postgres@db:5432/qrmaster?schema=public"
-ENV NEXTAUTH_URL="https://www.qrmaster.net"
-ENV NEXTAUTH_SECRET="build-time-secret"
-ENV IP_SALT="build-time-salt"
-ENV STRIPE_SECRET_KEY="sk_test_placeholder_for_build"
-ENV RESEND_API_KEY="re_placeholder_for_build"
-ENV NEXT_PUBLIC_APP_URL="https://www.qrmaster.net"
-# PostHog Analytics - REQUIRED at build time for client-side bundle
-ENV NEXT_PUBLIC_POSTHOG_KEY="phc_97JBJVVQlqqiZuTVRHuBnnG9HasOv3GSsdeVjossizJ"
-ENV NEXT_PUBLIC_POSTHOG_HOST="https://us.i.posthog.com"
-ENV NEXT_PUBLIC_INDEXABLE="true"
-RUN npx prisma generate
-RUN npm run build
-
-# ---- runner ----
-FROM node:20-alpine AS runner
-# Install OpenSSL for Prisma runtime
-RUN apk add --no-cache openssl
-WORKDIR /app
-ENV NODE_ENV=production
-ENV NEXT_TELEMETRY_DISABLED=1
-
-RUN addgroup --system --gid 1001 nodejs
-RUN adduser --system --uid 1001 nextjs
-
-COPY --from=builder /app/node_modules ./node_modules
-COPY --from=builder /app/prisma ./prisma
-COPY --from=builder /app/.next/standalone ./
-COPY --from=builder /app/.next/static ./.next/static
-COPY --from=builder /app/public ./public
-
-USER nextjs
-
-EXPOSE 3000
-
-CMD ["node", "server.js"]
+# ---- deps ----
+FROM node:20-alpine AS deps
+# Install OpenSSL for Prisma
+RUN apk add --no-cache openssl
+WORKDIR /app
+COPY package.json package-lock.json* pnpm-lock.yaml* yarn.lock* .npmrc* ./
+# Copy prisma schema for postinstall script
+COPY prisma ./prisma
+RUN \
+  if [ -f pnpm-lock.yaml ]; then \
+    npm i -g pnpm && pnpm i --frozen-lockfile; \
+  elif [ -f yarn.lock ]; then \
+    yarn --frozen-lockfile; \
+  elif [ -f package-lock.json ]; then \
+    npm ci; \
+  else \
+    npm install --legacy-peer-deps; \
+  fi
+
+# ---- builder ----
+FROM node:20-alpine AS builder
+# Install OpenSSL for Prisma
+RUN apk add --no-cache openssl
+WORKDIR /app
+COPY --from=deps /app/node_modules ./node_modules
+COPY . .
+ENV NEXT_TELEMETRY_DISABLED=1
+# Add build-time environment variables with defaults
+ENV NEXTAUTH_URL="https://www.qrmaster.net"
+ENV NEXTAUTH_SECRET="build-time-secret"
+ENV IP_SALT="build-time-salt"
+ENV STRIPE_SECRET_KEY="sk_test_placeholder_for_build"
+ENV RESEND_API_KEY="re_placeholder_for_build"
+ENV NEXT_PUBLIC_APP_URL="https://www.qrmaster.net"
+# PostHog Analytics - REQUIRED at build time for client-side bundle
+ENV NEXT_PUBLIC_POSTHOG_KEY="phc_97JBJVVQlqqiZuTVRHuBnnG9HasOv3GSsdeVjossizJ"
+ENV NEXT_PUBLIC_POSTHOG_HOST="https://us.i.posthog.com"
+ENV NEXT_PUBLIC_INDEXABLE="true"
+ENV NEXT_PUBLIC_FACEBOOK_PIXEL_ID="1601718491252690"
+RUN npx prisma generate
+RUN npm run build
+
+# ---- runner ----
+FROM node:20-alpine AS runner
+# Install OpenSSL for Prisma runtime
+RUN apk add --no-cache openssl
+WORKDIR /app
+ENV NODE_ENV=production
+ENV NEXT_TELEMETRY_DISABLED=1
+
+RUN addgroup --system --gid 1001 nodejs
+RUN adduser --system --uid 1001 nextjs
+
+COPY --from=builder /app/node_modules ./node_modules
+COPY --from=builder /app/prisma ./prisma
+COPY --from=builder /app/.next/standalone ./
+COPY --from=builder /app/.next/static ./.next/static
+COPY --from=builder /app/public ./public
+COPY --from=builder /app/docker/entrypoint.sh ./docker/entrypoint.sh
+
+RUN chmod +x ./docker/entrypoint.sh
+
+# --- NEU: Ordner erstellen und Rechte an den nextjs User geben ---
+RUN mkdir -p /app/.next/cache && chown nextjs:nodejs /app/.next/cache
+
+USER nextjs
+
+EXPOSE 3000
+
+CMD ["./docker/entrypoint.sh"]
--- a/FINAL_DELIVERY_PACKAGE_TIMO.md
+++ b/FINAL_DELIVERY_PACKAGE_TIMO.md
@@ -0,0 +1,157 @@
+# FINAL DELIVERY PACKAGE — QR Master Outreach
+
+> [!IMPORTANT]
+> **Recipient:** knuth.timo@gmail.com
+> **Sender:** Antigravity AI
+> **Date:** 2026-04-13
+>
+> This document contains all the outreach emails, guest post pitches, and corresponding articles prepared for the QR Master SEO and content marketing campaign.
+>
+> **Note:** I cannot send emails directly from this interface. Please copy the content below into your email client to send to the respective targets.
+
+---
+
+## Table of Contents
+1. [Guest Post Pitches & Articles](#1-guest-post-pitches--articles)
+   - [DigitalGpoint](#digitalgpoint)
+   - [Techdee](#techdee)
+   - [SEO Sandwitch](#seo-sandwitch)
+2. [Web 2.0 & Self-Publishing Articles](#2-web-20--self-publishing-articles)
+   - [Medium](#medium)
+   - [LinkedIn Pulse](#linkedin-pulse)
+   - [Substack Series](#substack-series)
+3. [Resource Outreach Emails (10 Targets)](#3-resource-outreach-emails-10-targets)
+
+---
+
+## 1. Guest Post Pitches & Articles
+
+### DigitalGpoint
+**Recipent:** digitalgpoint.webmail@gmail.com  
+**Article Type:** Guest Post
+
+#### Submission Email
+**Subject:** Solving the "print gap" for small businesses
+
+Hi [Name],
+
+I’ve noticed DigitalGpoint covers a lot of practical tools for business growth. One area that often gets overlooked is the bridge between physical marketing (flyers, menus, signage) and digital analytics.
+
+I’ve put together a practical guide on "Managing the Move from Static to Dynamic Print." It explains how small business owners are using dynamic redirect layers to make their physical materials editable after printing—saving them from costly reprints when a URL or price changes.
+
+It’s a straightforward, workflow-focused piece that I believe your readers would find highly actionable.
+
+Would you be open to reviewing a draft for a guest contribution?
+
+Best,
+
+Timo
+(Writer & Strategist)
+
+#### Accompanying Article: "Every Print Order Feels Final (Until You Use a Dynamic Layer)"
+[View full article content in digitalGpoint-dynamic-vs-static-qr-codes.md](file:///c:/Users/a931627/Documents/QRMASTER/articles/digitalGpoint-dynamic-vs-static-qr-codes.md)
+
+---
+
+### Techdee
+**Recipient:** Blayget@gmail.com  
+**Article Type:** Guest Post (Tier 2)
+
+#### Submission Email
+**Subject:** Offline-to-Online marketing workflows
+
+Hi [Name],
+
+I’ve been following Techdee’s tech and marketing tutorials for some time. 
+
+I’m currently finalizing a piece titled: **"Beyond the Scan: 5 Professional QR Strategies for Modern Marketing."**
+
+The article moves past the basic "link a code to a site" approach and explores practical technical workflows: using dynamic redirects to avoid reprints, pulling scan data into GA4 for attribution, and managing bulk physical assets.
+
+It’s a 700-word, list-style tutorial that fits your current format. Is this something you'd like to see for a guest contribution?
+
+Best,
+
+Timo
+(Writer & Strategist)
+
+#### Accompanying Article: "Beyond the Scan: 5 Professional QR Strategies for Modern Marketing"
+[View full article content in techdee-5-qr-code-strategies.md](file:///c:/Users/a931627/Documents/QRMASTER/articles/techdee-5-qr-code-strategies.md)
+
+---
+
+### SEO Sandwitch
+**Recipient:** joydeep@seosandwitch.com  
+**Article Type:** Guest Post (Tier 1 - High Value)
+
+#### Submission Email
+**Subject:** Attribution blind spots in physical marketing
+
+Hi Joydeep,
+
+I’ve been following SEO Sandwitch for a while—your recent piece on AI SEO and GEO was excellent.
+
+I’m reaching out because I’ve been working on a technical deep-dive that explores a massive attribution blind spot: physical marketing campaigns.
+
+The piece, **"QR Codes as an Offline-to-Online Signal,"** breaks down how marketers can pull scan data from flyers, packaging, and OOH materials into GA4 to finally close the loop on offline attribution. 
+
+It covers:
+- Using dynamic redirect layers as an attribution signal.
+- The indirect impact of physical touchpoints on branded search volume.
+- Technical setup for UTM-tagged dynamic codes.
+
+It’s not a superficial "marketing tips" post; it’s a strategist-level look at attribution data.
+
+I have a ~2,000 word draft ready. Would you be open to taking a look for a potential guest contribution?
+
+Best,
+
+Timo
+(Writer & Strategist)
+
+#### Accompanying Article: "QR Codes as an Offline-to-Online Signal"
+[View full article content in seosandwitch-qr-codes-offline-attribution.md](file:///c:/Users/a931627/Documents/QRMASTER/articles/seosandwitch-qr-codes-offline-attribution.md)
+
+---
+
+## 2. Web 2.0 & Self-Publishing Articles
+
+### Medium
+**Target Platform:** Medium.com  
+**Publication:** Self-publish or submit to a marketing pub (e.g., Better Marketing)
+
+#### Article: "Beyond the Menu: 5 Practical Ways to Use QR Codes for Business Growth"
+[View full article content in medium-5-underrated-qr-use-cases.md](file:///c:/Users/a931627/Documents/QRMASTER/articles/medium-5-underrated-qr-use-cases.md)
+
+---
+
+### LinkedIn Pulse
+**Target Platform:** LinkedIn Personal Account  
+
+#### Article: "Why Your Business Card Still Needs a QR Code in 2025"
+[View full article content in linkedin-business-card-qr.md](file:///c:/Users/a931627/Documents/QRMASTER/articles/linkedin-business-card-qr.md)
+
+---
+
+### Substack Series
+**Target Platform:** Substack Newsletter ("The QR Code Playbook")
+
+#### Content: 3-Issue Intro Series
+[View full issues content in substack-playbook-series.md](file:///c:/Users/a931627/Documents/QRMASTER/articles/substack-playbook-series.md)
+
+---
+
+## 3. Resource Outreach Emails (10 Targets)
+
+These are short link-request emails targeting sites that list QR tools or marketing resources.
+
+**Targets & Templates:**
+[View all 10 target details and templates in outreach-seo-emails.md](file:///c:/Users/a931627/Documents/QRMASTER/outreach-seo-emails.md)
+
+---
+
+> [!TIP]
+> **Next Steps:**
+> 1. Start with **Web 2.0 publishing** (Medium, LinkedIn, Substack) to build topical authority.
+> 2. Send the **Guest Post Pitches** (DigitalGpoint, Techdee, SEO Sandwitch) once the Web 2.0 posts are live so editors can see your writing quality.
+> 3. Send the **Resource Outreach** emails in a batch of 5-10 per week.
--- a/40
+++ b/40
@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2025 QR Master
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+MIT License
+
+Copyright (c) 2026 QR Master
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.
--- a/MIGRATION_FROM_SUPABASE.md
+++ b/MIGRATION_FROM_SUPABASE.md
@@ -1,321 +0,0 @@
-# Migration Guide: From Supabase to Local PostgreSQL
-
-This guide helps you migrate your QR Master application from Supabase to a local PostgreSQL database with Docker.
-
-## What Changed
-
-### ✅ Removed
- Supabase connection pooling (`DIRECT_URL` environment variable)
- Supabase-specific configurations
- External database dependency
-
-### ✨ Added
- Local PostgreSQL 16 database in Docker
- Redis cache for better performance
- Adminer database management UI
- Complete Docker setup with docker-compose
- Database initialization scripts
- Development and production Docker configurations
-
-## Migration Steps
-
-### 1. Backup Your Supabase Database (IMPORTANT!)
-
-Before making any changes, backup your existing data:
-
-```bash
-# If you have access to Supabase CLI
-supabase db dump > backup_$(date +%Y%m%d).sql
-
-# Or use pg_dump directly with your Supabase credentials
-pg_dump "postgresql://postgres:[PASSWORD]@[PROJECT_REF].supabase.co:5432/postgres" > backup.sql
-```
-
-### 2. Update Your Codebase
-
-Pull the latest changes or update these files:
-
-#### Updated Files:
- ✏️ `prisma/schema.prisma` - Removed `directUrl` field
- ✏️ `src/lib/env.ts` - Removed `DIRECT_URL` variable
- ✏️ `docker-compose.yml` - Updated with PostgreSQL setup
- ✏️ `Dockerfile` - Enhanced with PostgreSQL support
- ✏️ `package.json` - Added Docker scripts and tsx
-
-#### New Files:
- 📄 `docker-compose.dev.yml` - Development setup
- 📄 `docker/init-db.sh` - Database initialization
- 📄 `docker/README.md` - Docker documentation
- 📄 `DOCKER_SETUP.md` - Complete Docker guide
- 📄 `env.example` - Environment template
- 📄 `.dockerignore` - Docker build optimization
-
-### 3. Set Up Environment Variables
-
-1. Remove Supabase-specific variables:
-```bash
-# Remove these from .env:
-# DIRECT_URL=...
-# SUPABASE_URL=...
-# SUPABASE_ANON_KEY=...
-```
-
-2. Update database connection:
-```bash
-# For Docker (default):
-DATABASE_URL=postgresql://postgres:postgres@db:5432/qrmaster?schema=public
-
-# For local development (without Docker):
-DATABASE_URL=postgresql://postgres:postgres@localhost:5432/qrmaster?schema=public
-```
-
-3. Copy from template:
-```bash
-cp env.example .env
-```
-
-4. Generate secure secrets:
-```bash
-# Linux/Mac
-openssl rand -base64 32  # Use for NEXTAUTH_SECRET
-openssl rand -base64 32  # Use for IP_SALT
-
-# Windows PowerShell
-[Convert]::ToBase64String((1..32 | ForEach-Object { Get-Random -Maximum 256 }))
-```
-
-### 4. Start Local PostgreSQL
-
-#### Option A: Development Mode (Recommended)
-
-```bash
-# Start database only (run app on host)
-npm run docker:dev
-
-# Wait for database to be ready
-docker-compose -f docker-compose.dev.yml logs -f db
-```
-
-#### Option B: Full Docker
-
-```bash
-# Start all services
-npm run docker:prod
-
-# Wait for all services to be ready
-docker-compose logs -f
-```
-
-### 5. Restore Your Data
-
-#### Option 1: Using Prisma Migrations (Clean Start)
-
-```bash
-# Generate Prisma client
-npm run db:generate
-
-# Run migrations
-npm run db:migrate
-
-# Seed with demo data
-npm run db:seed
-```
-
-#### Option 2: Restore from Backup (Preserve Data)
-
-```bash
-# Restore your Supabase backup
-cat backup.sql | docker-compose exec -T db psql -U postgres qrmaster
-
-# Or if running locally
-psql -U postgres -d qrmaster < backup.sql
-
-# Then run migrations to update schema
-npm run db:deploy
-```
-
-### 6. Verify Migration
-
-1. **Check Database Connection:**
-```bash
-# Connect to database
-npm run docker:db
-
-# Or manually
-docker-compose exec db psql -U postgres -d qrmaster
-
-# Run test query
-SELECT COUNT(*) FROM "User";
-SELECT COUNT(*) FROM "QRCode";
-```
-
-2. **Access Adminer (Database UI):**
-   - URL: http://localhost:8080
-   - System: PostgreSQL
-   - Server: db
-   - Username: postgres
-   - Password: postgres
-   - Database: qrmaster
-
-3. **Test Your Application:**
-```bash
-# Start the app (if using dev mode)
-npm run dev
-
-# Access: http://localhost:3050
-```
-
-### 7. Update Your Deployment
-
-#### For Docker Production:
-
-```bash
-# Build and deploy
-docker-compose up -d --build
-
-# Run migrations
-docker-compose exec web npx prisma migrate deploy
-
-# Check logs
-docker-compose logs -f web
-```
-
-#### For Other Platforms (Vercel, Railway, etc.):
-
-Update your environment variables in the platform's dashboard:
- Remove: `DIRECT_URL`
- Update: `DATABASE_URL` to your new PostgreSQL connection string
-
-## Troubleshooting
-
-### Issue: Connection Refused
-
-```bash
-# Check if database is running
-docker-compose ps
-
-# Check database logs
-docker-compose logs db
-
-# Restart database
-docker-compose restart db
-```
-
-### Issue: Migration Errors
-
-```bash
-# Reset migrations (⚠️ deletes data!)
-npm run db:migrate reset
-
-# Or manually reset
-docker-compose down -v
-docker-compose up -d db
-npm run db:migrate
-```
-
-### Issue: Prisma Client Not Generated
-
-```bash
-# Regenerate Prisma client
-npm run db:generate
-
-# Or
-npx prisma generate
-```
-
-### Issue: Data Not Migrated
-
-```bash
-# Check if backup was restored correctly
-docker-compose exec db psql -U postgres -d qrmaster -c "
-SELECT 
-  schemaname,
-  tablename,
-  pg_size_pretty(pg_total_relation_size(schemaname||'.'||tablename)) AS size
-FROM pg_tables
-WHERE schemaname = 'public'
-ORDER BY pg_total_relation_size(schemaname||'.'||tablename) DESC;
-"
-```
-
-## Differences: Supabase vs Local PostgreSQL
-
-| Feature | Supabase | Local PostgreSQL |
-|---------|----------|------------------|
-| Hosting | Cloud (managed) | Self-hosted (Docker) |
-| Connection Pooling | Built-in (Supavisor) | Prisma built-in |
-| Database UI | Supabase Studio | Adminer (included) |
-| Backups | Automatic | Manual (or scripted) |
-| Cost | Free tier + paid | Free (infrastructure cost only) |
-| Latency | Internet dependent | Local network |
-| Setup | Account required | Docker only |
-| Scaling | Automatic | Manual |
-
-## Benefits of Local PostgreSQL
-
-✅ **Full Control**: Own your data and infrastructure  
-✅ **No Vendor Lock-in**: Standard PostgreSQL  
-✅ **Lower Latency**: Local network speed  
-✅ **Cost**: No monthly fees  
-✅ **Privacy**: Data stays on your infrastructure  
-✅ **Development**: Easy local testing  
-✅ **Offline**: Works without internet  
-
-## Next Steps
-
-1. ✅ Verify all data migrated correctly
-2. ✅ Test all application features
-3. ✅ Update your CI/CD pipelines
-4. ✅ Set up automated backups:
-```bash
-# Create backup script
-cat > backup.sh << 'EOF'
-#!/bin/bash
-BACKUP_DIR="./backups"
-mkdir -p $BACKUP_DIR
-docker-compose exec -T db pg_dump -U postgres qrmaster > "$BACKUP_DIR/backup_$(date +%Y%m%d_%H%M%S).sql"
-EOF
-
-chmod +x backup.sh
-
-# Run daily backups (cron example)
-# 0 2 * * * /path/to/backup.sh
-```
-
-5. ✅ Monitor your application
-6. ✅ Update documentation
-
-## Rollback Plan
-
-If you need to rollback to Supabase:
-
-1. Keep your Supabase project active during testing
-2. Keep your backup files safe
-3. To rollback, simply change `DATABASE_URL` back to Supabase
-4. Add back `DIRECT_URL` to `prisma/schema.prisma`:
-```prisma
-datasource db {
-  provider  = "postgresql"
-  url       = env("DATABASE_URL")
-  directUrl = env("DIRECT_URL")
-}
-```
-
-## Support
-
-For issues:
-1. Check [DOCKER_SETUP.md](DOCKER_SETUP.md) for detailed Docker help
-2. Check [docker/README.md](docker/README.md) for Docker commands
-3. Review logs: `docker-compose logs -f`
-4. Open an issue on GitHub
-
---
-
-🎉 **Congratulations!** You've successfully migrated from Supabase to local PostgreSQL!
-
-
-
-
-
-
-
--- a/PLAN_bulk_dynamic_and_barcode_.md
+++ b/PLAN_bulk_dynamic_and_barcode_.md
@@ -0,0 +1,179 @@
+# Feature Plan: Bulk Dynamic QR + Dynamic Barcode Generator
+
+## Feature 1: Bulk Generator → Dynamic QR freischalten
+
+### Ziel
+Nutzer können beim Bulk-Import wählen ob sie statische oder dynamische QR-Codes erstellen. Dynamisch = DB-Einträge mit Slugs + Tracking. Nur für PRO/BUSINESS.
+
+### Aktueller Stand (Ist)
+- `bulk-creation/page.tsx` generiert QR-Codes rein client-seitig (kein DB-Eintrag)
+- `generateStaticQRCodes()` rendert SVGs lokal via `qrcode`-Library
+- `saveQRCodesToDatabase()` sendet an `POST /api/qrs` mit `isStatic: true` — also immer statisch
+- Kein Toggle Static/Dynamic vorhanden
+- Kein Plan-Check für Dynamic im Bulk-Flow
+
+### Änderungen
+
+#### A) Frontend: `bulk-creation/page.tsx`
+
+1. **Toggle "Static / Dynamic" hinzufügen** (nach Plan-Check)
+   - Nur sichtbar/aktivierbar wenn `userPlan === 'PRO' || 'BUSINESS'`
+   - FREE-Nutzer sehen den Toggle gesperrt mit Upgrade-Hinweis
+   - State: `const [isDynamic, setIsDynamic] = useState(false)`
+
+2. **Interface erweitern**
+   ```ts
+   interface GeneratedQR {
+     title: string;
+     content: string;
+     svg: string;
+     slug?: string;       // nur bei dynamic, nach API-Antwort gesetzt
+     redirectUrl?: string; // z.B. https://qrmaster.net/r/abc123
+   }
+   ```
+
+3. **Generierungslogik aufteilen**
+   - Static (wie bisher): client-seitig SVG generieren, kein DB-Eintrag nötig
+   - Dynamic: direkt `POST /api/qrs` pro Eintrag mit `isDynamic: true` → API gibt Slug zurück → QR encodiert `/r/[slug]` statt Original-URL
+
+4. **Preview-Spalte erweitern**
+   - Bei dynamic: Slug-Link anzeigen + "Ziel änderbar" Badge
+   - Download-ZIP enthält QR-SVGs die `/r/[slug]` encodieren
+
+5. **Limit-Anzeige**
+   - PRO: max 50 dynamic / Bulk-Run (entspricht QR-Limit)
+   - BUSINESS: max 500
+
+#### B) Backend: `POST /api/qrs`
+
+Keine strukturelle Änderung nötig — der bestehende Endpunkt unterstützt bereits `isDynamic: false/true` und gibt `slug` zurück. Nur sicherstellen:
+
+- Plan-Limit-Check zählt korrekt bei Bulk-Erstellung (momentan prüft `POST /api/qrs` nur ob Gesamtanzahl < Limit — das bleibt so, aber Bulk erstellt X Requests nacheinander → ggf. Rate-Limit beachten)
+- Evtl. neuen Endpunkt `POST /api/qrs/bulk` der ein Array entgegennimmt und in einer DB-Transaktion schreibt (besser als 500 Einzelrequests)
+
+#### C) Optionaler neuer Endpunkt: `POST /api/qrs/bulk` (empfohlen)
+
+```ts
+// Body: { qrCodes: Array<{ title, content, contentType, isDynamic }>, plan }
+// Response: { created: Array<{ id, slug, redirectUrl }>, failed: number }
+// Vorteile: eine DB-Transaktion, ein CSRF-Check, schneller
+```
+
+Plan-Check: `if (isDynamic && plan === 'FREE') return 403`
+
+---
+
+### Reihenfolge der Umsetzung
+
+1. Toggle + Plan-Check im Frontend
+2. Dynamic-Generierungslogik (nutzt bestehenden `POST /api/qrs`)
+3. (Optional) `POST /api/qrs/bulk` für Performance
+4. ZIP-Download mit Redirect-URLs als Metadaten-CSV
+
+---
+
+## Feature 2: Dynamischer Barcode Generator
+
+### Aufteilung: Landingpage (Marketing) + Dashboard (Funktion)
+
+**Wichtig:** "Dynamic" existiert nur im Dashboard `/create`. Die Landingpage erklärt das Konzept und treibt Nutzer zum Signup/Login — sie hat keinen eigenen Dynamic-Modus.
+
+---
+
+### 2a) Landingpage: `/tools/dynamic-barcode-generator`
+
+**Ziel:** SEO-Traffic auf Keyword "barcode generator" (100k–1M, 0% Competition) konvertieren zu Signups.
+
+**Was die Landingpage NICHT hat:**
+- Keinen Dynamic-Toggle
+- Keine echte Dynamic-Funktionalität
+
+**Was die Landingpage HAT:**
+- Bestehenden `BarcodeGeneratorClient` eingebettet (statischer Generator, unverändert)
+- Erklärung was ein dynamischer Barcode ist + Vorteile
+- Klarer CTA: "Create Dynamic Barcode → Sign up / Dashboard"
+
+**Aufbau** (`src/app/(main)/(marketing)/tools/dynamic-barcode-generator/page.tsx`):
+
+```
+Hero-Section
+  H1: "Dynamic Barcode Generator — Update Any Barcode Without Reprinting"
+  Subtext: Erklärt Tracking + Redirect-Konzept
+  CTA-Button: "Create Dynamic Barcode" → /login oder /signup
+
+Tool-Section
+  BarcodeGeneratorClient (statisch, wie bisher, keine Änderungen)
+  Banner darunter: "Want dynamic barcodes? Sign up free →"
+
+How It Works (3 Schritte)
+  1. Sign up & create barcode in dashboard
+  2. Print it once
+  3. Update the destination anytime — no reprint needed
+
+Use Cases
+  Retail-Verpackungen, Logistik-Labels, Produktkataloge, Event-Badges
+
+FAQ-Section (schema.org FAQ markup)
+  - "Was ist ein dynamischer Barcode?"
+  - "Wie unterscheidet sich dynamisch von statisch?"
+  - "Welche Formate werden unterstützt?"
+
+RelatedTools-Komponente (bereits vorhanden)
+```
+
+**Metadata:**
+```ts
+title: 'Dynamic Barcode Generator — Trackable & Editable Barcodes'
+description: 'Create dynamic barcodes that you can update without reprinting. Track scans, change destinations, and manage all barcodes from one dashboard.'
+canonical: 'https://www.qrmaster.net/tools/dynamic-barcode-generator'
+keywords: ['dynamic barcode generator', 'barcode generator', 'trackable barcode', 'editable barcode']
+```
+
+**Sitemap:** `/tools/dynamic-barcode-generator` hinzufügen.
+
+---
+
+### 2b) Dashboard `/create` — BARCODE als ContentType
+
+**Ziel:** Eingeloggte Nutzer können Barcodes (statisch oder dynamisch) im Dashboard erstellen, speichern und tracken.
+
+**DB-Änderung (kein migrate!):**
+```sql
+-- Direkt gegen PostgreSQL ausführen (npm run docker:db)
+ALTER TYPE "ContentType" ADD VALUE 'BARCODE';
+```
+Danach: `npx prisma generate`
+
+**Änderungen `create/page.tsx`:**
+- BARCODE zu `contentTypes` Array hinzufügen
+- `renderContentFields()` Case: Barcode-Wert + Format-Picker (CODE128, EAN13, UPC, etc.)
+- Preview: `react-barcode` statt `QRCodeSVG` wenn ContentType === BARCODE
+- QR-spezifische Optionen ausblenden bei BARCODE (Frames, Logo, Corner Style)
+- Dynamic Barcode = encodiert `/r/[slug]` → nutzt bestehendes Redirect- + Tracking-System
+- Static Barcode = encodiert Rohwert direkt
+
+**Kein neues Backend nötig** — `POST /api/qrs` + `/r/[slug]`-Redirect funktionieren bereits.
+
+---
+
+### Reihenfolge der Umsetzung
+
+**Phase 1 — Landingpage (kein DB-Change):**
+1. `page.tsx` unter `/tools/dynamic-barcode-generator` erstellen
+2. Sitemap-Eintrag
+
+**Phase 2 — Dashboard BARCODE:**
+1. SQL ausführen: `ALTER TYPE "ContentType" ADD VALUE 'BARCODE'`
+2. `npx prisma generate`
+3. `create/page.tsx` erweitern
+
+---
+
+## Abhängigkeiten zwischen den Features
+
+| Feature | Hängt ab von |
+|---------|-------------|
+| Bulk Dynamic | Bestehendem `POST /api/qrs` (bereits fertig) |
+| Bulk Dynamic (optional) | Neuem `POST /api/qrs/bulk` Endpunkt |
+| Landingpage Dynamic Barcode | Bestehendem BarcodeGeneratorClient (keine Änderungen) |
+| Dashboard BARCODE | SQL-Enum-Erweiterung + `prisma generate` |
--- a/QR-Master-Analysis-April-2026.md
+++ b/QR-Master-Analysis-April-2026.md
@@ -0,0 +1,249 @@
+# QR Master — Deep Analysis & Growth Potential
+**Date:** April 1, 2026 | **Project Age:** 3 months (launched Jan 1, 2026)
+
+---
+
+## Executive Summary
+
+QR Master is a young but well-built QR code SaaS entering a **$1–7B market growing at 16%+ CAGR**. After just 3 months, the numbers tell an interesting story: explosive impression growth in Google Search (0 → 4,100/month), strong AI citation momentum (1,849 citations across 11 pages), and 169 unique visitors in the last 90 days with promising engagement metrics (8m 36s avg session, 16% bounce rate). However, organic search clicks remain very low, and there are zero paying customers visible yet. The opportunity is real, but execution over the next 6 months will determine everything.
+
+---
+
+## 1. Your Numbers — What They Tell Me
+
+### Google Search Console (Jan–Mar 2026)
+
+| Metric | January | February | March | Growth |
+|--------|---------|----------|-------|--------|
+| Impressions | 158 | 44 | 4,115 | **+2,504%** |
+| Clicks | 0 | 0 | 23 | From zero |
+| Avg Position | ~1.3 | ~3.3 | ~68.4 | Widened (more keywords) |
+
+**What this means:** Google discovered your site in late January, but the real indexing explosion happened in March. The jump from 44 impressions in February to 4,115 in March is dramatic — this is the "Google sandbox" lifting. The average position being ~68 means most of your keywords are on pages 6–7 of Google. That's normal for a 3-month-old domain, but it also means you're not getting meaningful organic traffic yet from competitive terms.
+
+**Top performing pages by impressions:**
+
+| Page | Impressions | Clicks | Avg Position |
+|------|-------------|--------|-------------|
+| Homepage | 356 | 15 | 4.0 |
+| Barcode Generator | 1,160 | 4 | 71.4 |
+| Dynamic QR Code Generator | 536 | 0 | 81.1 |
+| Restaurant Menu QR Blog | 425 | 0 | 80.9 |
+| Geolocation QR Code | 281 | 0 | 73.2 |
+| URL QR Code | 205 | 0 | 83.6 |
+| Twitter QR Code | 169 | 0 | 71.3 |
+
+**Key insight:** Your barcode generator page has 1,160 impressions but only 4 clicks because it's ranking at position 71. If you can move that to page 1, even position 8–10, you'd capture 20–50 clicks/day from that keyword cluster alone. Same story for "dynamic QR code generator" (536 impressions, position 81).
+
+### AI Citations (Google AI Overviews)
+
+| Week | Citations | Avg/Day | Trend |
+|------|-----------|---------|-------|
+| Week 9 (late Feb) | 123 | 30.8 | Baseline |
+| Week 10 | 328 | 46.9 | +167% |
+| Week 11 | 343 | 49.0 | +5% |
+| Week 12 | 514 | 73.4 | +50% |
+| Week 13 | 541 | 77.3 | +5% |
+
+**Total: 1,849 citations across up to 11 unique pages.**
+
+This is genuinely impressive for a 3-month-old site. AI citations at 77/day means Google's AI is actively referencing your content when answering QR-related queries. This is a leading indicator — AI citations often precede organic ranking improvements. You're building topical authority faster than traditional SEO alone would deliver.
+
+### PostHog Analytics (Last 90 Days)
+
+| Metric | Value | Assessment |
+|--------|-------|-----------|
+| Unique Visitors | 169 | Low, but expected for 3 months |
+| Page Views | 2,120 | ~12.5 pages/visitor — very high engagement |
+| Sessions | 417 | 2.5 sessions/visitor average |
+| Session Duration | 8m 36s | Excellent — users are exploring deeply |
+| Bounce Rate | 16% | Outstanding (industry avg is 40-60%) |
+
+**Traffic sources:**
+
+| Channel | Visitors | Views |
+|---------|----------|-------|
+| Referral | 100 | 803 |
+| Organic Social | 64 | 89 |
+| Direct | 17 | 1,123 |
+| Organic Search | 6 | 70 |
+
+**Critical insight:** Your 16% bounce rate and 8.5-minute session duration are exceptional. People who find your site actually use it. The problem isn't product quality — it's distribution. Only 6 visitors from organic search in 90 days confirms you're still in the early SEO growth phase.
+
+**Retention concern:** The cohort data shows near-zero retention after week 1 for most cohorts. This is the biggest red flag — users come, try the tool, but don't come back. This is typical for free QR generator users, but it means conversion to paid will depend heavily on capturing value during that first session.
+
+---
+
+## 2. Competitive Landscape
+
+### The Market You're Entering
+
+The QR code generator market is valued at **$1.1–6.8B in 2025** (estimates vary by definition) and growing at **16–17% CAGR**. Dynamic QR codes specifically are the revenue driver, accounting for 55-64% of market value.
+
+### Key Competitors
+
+| Company | Est. Revenue (2025) | Pricing | Key Strength |
+|---------|-------------------|---------|-------------|
+| **Flowcode** | $15.7M | Free / $5-25/mo | VC-backed, design-focused, landing pages |
+| **Bitly** | $200M+ (link shortening + QR) | $8–199/mo | Brand recognition, link ecosystem |
+| **Uniqode** (fka Beaconstac) | ~$10M est. | $5–99/mo | Enterprise (SOC2, HIPAA, ISO) |
+| **QR Tiger** | ~$5M est. | $7–37/mo | SEO-aggressive, content marketing |
+| **Trycon/Scanova** | $7.2M | $5–49/mo | 2,000+ businesses, enterprise |
+| **Mobilo** | $5.4M | $4.99–14.99/mo | Digital business cards focus |
+| **Unitag** | $2.3M | Free / $9.90+/mo | European market, design tools |
+| **QR Code Creator** | $1.5M | $4.99–14.99/mo | Long-established (since 2009) |
+| **QRCode Monkey** | Unknown | Free (ad-supported) | SEO dominant, free tools |
+
+### What This Means for QR Master
+
+The market has room. Even QR Code Creator, which has been around since 2009, only does $1.5M. The winner-take-all dynamics of pure SaaS don't apply as strongly here because QR codes are a utility — businesses often try 2-3 tools before settling. Key entry angles that still work: niche verticals (restaurants, real estate), better free tier to build SEO traffic, and superior analytics.
+
+---
+
+## 3. SEO Assessment
+
+### Current State: Early but Promising
+
+Your site is showing 700+ unique keywords with impressions — that's a lot of keyword surface area for a 3-month-old site. But almost all rankings are on pages 5-10 of Google (positions 50-100).
+
+### Biggest Keyword Opportunities (High Impression, Improvable Position)
+
+| Keyword | Monthly Impressions | Current Position | Difficulty |
+|---------|-------------------|-----------------|-----------|
+| barcode generator | 148+ | 74.8 | Very High |
+| dynamic qr code | 115+ | 80.3 | High |
+| dynamic qr code generator | 81+ | 85.8 | High |
+| restaurant qr code | 51+ | 75.0 | Medium |
+| qr code restaurant menu | 48+ | 82.8 | Medium |
+| twitter qr code | 46+ | 76.7 | Low-Medium |
+| instagram qr code generator | 35+ | 54.9 | Medium |
+| bulk qr code generator | 28+ | 94.4 | Medium |
+| vcard qr code generator | 9+ | 74.9 | Low-Medium |
+| teams qr code | 3+ | 34.7 | Low |
+
+### Quick Wins (Already Close to Page 1)
+
+- **"teams qr code"** — Position 34.7 with dedicated tool page already built. You already have traffic to this page (20 visitors in PostHog). Push this to page 1.
+- **"zoom qr code"** — Position 40.3. Similar opportunity.
+- **"qrmaster"** branded terms — Position 4.3 (already strong, but should be #1)
+- **"qr master"** — Position 8.1. Should be #1 for your own brand.
+
+### What's Holding You Back
+
+1. **Domain age (3 months):** Google inherently trusts older domains more. This improves automatically with time.
+2. **Backlink profile:** Likely thin. Your referral traffic (100 visitors) suggests some links, but you need more authoritative ones.
+3. **Competition on head terms:** "QR code generator" is dominated by Bitly, QRCode Monkey, QR Tiger with DA 50+ domains. You won't rank for this soon.
+4. **Content depth vs. competitors:** QR Tiger and Uniqode have 100+ blog posts each. You're early in content production.
+
+---
+
+## 4. Revenue Potential — Realistic Projections
+
+### Assumptions
+
+Based on your current pricing model (FREE / PRO / BUSINESS tiers) and market benchmarks:
+
+- **Free-to-paid conversion rate for QR tools:** 2-4% (industry benchmark)
+- **Average revenue per user (ARPU):** $10-20/month for SMB QR tools
+- **Churn rate:** 5-8% monthly for SMB SaaS
+
+### Scenario Modeling
+
+#### Conservative (SEO-only growth, no paid acquisition)
+
+| Month | Monthly Visitors | Signups (15% CVR) | Paying Users (cum.) | MRR |
+|-------|-----------------|-------------------|--------------------|----|
+| Month 3 (now) | 170 | 39 | 0 | $0 |
+| Month 6 | 1,000 | 150 | 8 | $120 |
+| Month 12 | 5,000 | 750 | 60 | $900 |
+| Month 18 | 15,000 | 2,250 | 200 | $3,000 |
+| Month 24 | 40,000 | 6,000 | 500 | $7,500 |
+
+**Year 1 ARR: ~$10,800 | Year 2 ARR: ~$90,000**
+
+#### Moderate (SEO + content marketing + some link building)
+
+| Month | Monthly Visitors | Signups | Paying Users (cum.) | MRR |
+|-------|-----------------|---------|--------------------|----|
+| Month 6 | 3,000 | 450 | 25 | $375 |
+| Month 12 | 15,000 | 2,250 | 180 | $2,700 |
+| Month 18 | 40,000 | 6,000 | 500 | $7,500 |
+| Month 24 | 80,000 | 12,000 | 1,200 | $18,000 |
+
+**Year 1 ARR: ~$32,400 | Year 2 ARR: ~$216,000**
+
+#### Aggressive (SEO + paid + partnerships + viral loops)
+
+| Month | Monthly Visitors | Signups | Paying Users (cum.) | MRR |
+|-------|-----------------|---------|--------------------|----|
+| Month 12 | 50,000 | 7,500 | 600 | $9,000 |
+| Month 24 | 200,000 | 30,000 | 3,000 | $45,000 |
+
+**Year 2 ARR: ~$540,000**
+
+### Revenue Benchmarks from Comparable Companies
+
+- QR Code Creator (17 years old): **$1.5M/year**
+- Unitag (10+ years old): **$2.3M/year**
+- Flowcode (7 years, VC-backed): **$15.7M/year**
+- Indie SaaS benchmarks: $5K–25K MRR is very achievable within 18-24 months with focused execution
+
+---
+
+## 5. Strengths & Risks
+
+### What's Working
+
+1. **Product quality is high.** 8.5-minute sessions, 16% bounce rate, 12.5 pages/visitor — these are remarkable engagement metrics. The product holds attention.
+2. **AI citations growing fast.** 77 citations/day after 3 months is a strong signal Google's AI trusts your content.
+3. **Broad keyword footprint.** 700+ keywords showing impressions means Google is indexing and considering your pages for a wide range of queries.
+4. **Niche tool pages (Teams, Zoom, WiFi, Instagram).** These long-tail pages are your fastest path to page 1 rankings.
+5. **Technical foundation is solid.** Next.js 14, Stripe, analytics, dynamic QR codes — the infrastructure is already at a paid-product level.
+
+### Risks & Concerns
+
+1. **Near-zero retention.** Cohort data shows almost no users returning after week 1. Without solving retention, paid conversion will be extremely difficult.
+2. **No revenue yet.** 3 months with 0 MRR is normal, but the clock is ticking. Need to see first paying user by month 4-5.
+3. **Competitive head terms are years away.** You won't rank for "QR code generator" anytime soon. The long-tail strategy is correct but requires patience.
+4. **Single-channel dependency.** Currently SEO-reliant. If Google changes its algorithm or sandbox behavior, growth stalls.
+5. **service_account.json in root.** If this is a live credential, it's a security risk. Remove from version control immediately.
+
+---
+
+## 6. Recommendations — Next 90 Days
+
+### Immediate (This Month)
+
+1. **Fix retention first.** Add email capture on first QR creation, build a "My QR Codes" dashboard value prop, and implement a follow-up email sequence showing scan analytics. Users need a reason to come back.
+2. **Push "quick win" keywords to page 1.** Teams QR code (pos 34), Zoom QR code (pos 40), and your branded terms. These need targeted backlinks and content optimization.
+3. **Add pricing friction at the right moment.** If you're not gating anything, users have no reason to pay. Consider limiting dynamic QR codes to 1-3 on free tier, then upsell.
+
+### Short-term (Months 4-6)
+
+4. **Build 10-15 high-quality backlinks.** Guest posts on marketing blogs, HARO/Connectively responses, tool directories. Domain authority is your bottleneck.
+5. **Double down on restaurant/menu niche.** You have 425 impressions on the restaurant menu QR blog. This is a vertical where local businesses actually pay for QR tools. Build a dedicated landing page.
+6. **Launch on Product Hunt, Indie Hackers, and relevant subreddits.** Free exposure that also builds backlinks.
+
+### Medium-term (Months 6-12)
+
+7. **Expand content to 50+ blog posts.** Target every long-tail QR keyword cluster. QR Tiger's content machine is the model to emulate.
+8. **Add a freemium viral loop.** "Powered by QR Master" branding on free QR codes (with option to remove on paid plan).
+9. **Consider German market positioning.** Your GSC data shows German-language queries (dynamische QR codes, etc.) and you appear to be German-speaking. The German QR code market is underserved compared to English.
+
+---
+
+## 7. Bottom Line
+
+**Is there real potential here?** Yes, absolutely. The QR code market is large, growing, and the barrier to entry is manageable with good technical execution — which you clearly have. Companies doing $1.5M–$15M in this space prove the model works.
+
+**How much can you realistically make?** With sustained effort, **$3K–$10K MRR by month 18** is realistic under a moderate growth scenario. That's $36K–$120K ARR — meaningful side-project revenue. The top end of $200K+ ARR is achievable within 24 months if you invest in content, backlinks, and conversion optimization.
+
+**What's the biggest risk?** Not retention, not competition — it's giving up too early. SEO-driven SaaS is a compounding game. Months 1-6 feel slow because organic traffic takes time to build. The hockey stick starts around months 9-12 when domain authority compounds with content volume. QR Code Creator took 17 years to hit $1.5M, but the market was 10x smaller then.
+
+**Your 3-month scorecard: B+.** Excellent product, strong engagement, growing search visibility. The missing pieces are retention mechanics, first revenue, and backlink authority. All fixable.
+
+---
+
+*Analysis based on Google Search Console data (Jan–Mar 2026), PostHog analytics (90 days), Google AI Performance data, and market research as of April 2026.*
+
+*Sources: [Mordor Intelligence QR Market Report](https://www.mordorintelligence.com/industry-reports/qr-codes-market), [GetLatka QR SaaS Companies](https://getlatka.com/companies/industries/i-qr-code-generator-software), [Bitly QR Code Statistics](https://bitly.com/blog/qr-code-statistics/), [360iResearch QR Market](https://www.360iresearch.com/library/intelligence/qr-code-generator), [QR Code Chimp Statistics](https://www.qrcodechimp.com/qr-code-statistics/)*
--- a/README.md
+++ b/README.md
@@ -1,475 +1,482 @@
-# QR Master - Create Custom QR Codes in Seconds
-
-A production-ready SaaS application for creating and managing QR codes with advanced tracking, analytics, and Stripe payment integration.
-
-## Features
-
- 🎨 **Custom QR Codes** - Create static and dynamic QR codes with full customization
- 📊 **Advanced Analytics** - Track scans, locations, devices, and user behavior
- 🔄 **Dynamic Content** - Edit QR code destinations anytime without reprinting
- 📦 **Bulk Operations** - Import CSV/Excel files to create up to 1,000 QR codes at once
- 💳 **Stripe Integration** - FREE, PRO, and BUSINESS subscription plans with secure billing
- 🎨 **Custom Branding** - Logo upload, custom colors (PRO+ plans)
- 🌍 **SEO Optimized** - Schema.org structured data, meta tags, breadcrumbs
- 🔒 **Privacy-First** - GDPR-compliant, hashed IPs, DNT headers respected
- 📱 **Responsive Design** - Works perfectly on all devices
-
-## Tech Stack
-
- **Frontend**: Next.js 14 (App Router), TypeScript, Tailwind CSS
- **Backend**: Next.js API Routes, Prisma ORM
- **Database**: PostgreSQL (with Prisma migrations)
- **Cache**: Redis (optional)
- **Auth**: NextAuth.js (Credentials + Google OAuth)
- **Payments**: Stripe (Subscriptions & Webhooks)
- **QR Generation**: qrcode library
- **Bulk Processing**: Papa Parse (CSV), XLSX, JSZip
- **Analytics**: PostHog (optional)
- **SEO**: next-sitemap, Schema.org structured data
-
-## Quick Start
-
-### Prerequisites
-
- Node.js 18+
- Docker and Docker Compose V2
- Git
-
-### Installation
-
-#### Option 1: Development Mode (Recommended)
-
-Run database in Docker, app on host machine:
-
-1. Clone the repository:
-
-```bash
-git clone https://github.com/yourusername/qr-master.git
-cd qr-master
-```
-
-2. Install dependencies:
-
-```bash
-npm install
-```
-
-3. Copy and configure environment:
-
-```bash
-cp env.example .env
-```
-
-Edit `.env` and set:
-
- `NEXTAUTH_SECRET` (generate: `openssl rand -base64 32`)
- `IP_SALT` (generate: `openssl rand -base64 32`)
- (Optional) Google OAuth credentials
-
-4. Start database services:
-
-```bash
-npm run docker:dev
-```
-
-5. Run database migrations and seed:
-
-```bash
-npx prisma migrate dev
-npm run db:seed
-```
-
-> **Note**: If you get migration errors, you can reset the database:
->
-> ```bash
-> npx prisma migrate reset
-> ```
->
-> This will drop the database, recreate it, run all migrations, and seed data.
-
-6. Start development server:
-
-```bash
-npm run dev
-```
-
-7. Access the application:
-   - **App**: http://localhost:3050
-   - **Database UI**: http://localhost:8080 (Adminer - username: `root`, password: `root`)
-   - **Database**: localhost:5435 (username: `postgres`, password: `postgres`)
-   - **Redis**: localhost:6379
-
-#### Option 2: Full Docker (Production)
-
-Run everything in Docker:
-
-1. Clone and setup:
-
-```bash
-git clone https://github.com/yourusername/qr-master.git
-cd qr-master
-cp env.example .env
-# Edit .env with your configuration
-```
-
-2. Build and start:
-
-```bash
-npm run docker:prod
-```
-
-3. Run migrations:
-
-```bash
-docker-compose exec web npx prisma migrate deploy
-```
-
-4. Access at http://localhost:3050
-
-📚 **For detailed Docker setup, see [DOCKER_SETUP.md](DOCKER_SETUP.md)**
-
-## Demo Account
-
-After running `npm run db:seed`, use these credentials to test the application:
-
- **Email**: demo@qrmaster.com
- **Password**: demo123
- **Plan**: FREE (3 QR codes limit)
-
-The seed script also creates sample QR codes for testing.
-
-## Development
-
-### Available Scripts
-
-```bash
-# Development
-npm run dev                    # Start Next.js dev server (port 3050)
-npm run build                  # Build for production
-npm run start                  # Start production server
-
-# Database
-npm run db:generate            # Generate Prisma Client
-npm run db:migrate             # Run migrations (dev mode)
-npm run db:deploy              # Deploy migrations (production)
-npm run db:seed                # Seed database with demo data
-npm run db:studio              # Open Prisma Studio UI
-npx prisma migrate reset       # Reset database (drop, recreate, migrate, seed)
-
-# Docker
-npm run docker:dev             # Start DB & Redis only
-npm run docker:dev:stop        # Stop dev services
-npm run docker:dev:clean       # Stop and clean containers
-npm run docker:prod            # Start full stack (production)
-npm run docker:stop            # Stop all services
-npm run docker:logs            # View container logs
-npm run docker:db              # PostgreSQL CLI
-npm run docker:redis           # Redis CLI
-npm run docker:backup          # Backup database to SQL file
-```
-
-### Local Development (without Docker)
-
-1. Install dependencies:
-
-```bash
-npm install
-```
-
-2. Set up PostgreSQL and Redis locally
-
-3. Configure `.env` with local database URL:
-
-```env
-DATABASE_URL=postgresql://postgres:postgres@localhost:5435/qrmaster?schema=public
-```
-
-4. Run migrations and seed:
-
-```bash
-npx prisma migrate dev
-npm run db:seed
-```
-
-5. Start dev server:
-
-```bash
-npm run dev
-```
-
-### Resetting the Database
-
-If you need to reset your database (drop all tables, recreate, and reseed):
-
-```bash
-# Full reset (drops database, reruns migrations, seeds data)
-npx prisma migrate reset
-
-# Or manually:
-npx prisma migrate reset --skip-seed  # Reset without seeding
-npm run db:seed                        # Then seed manually
-```
-
-This is useful when:
-
- Schema has changed significantly
- You have migration conflicts
- You want to start fresh with clean data
-
-### Project Structure
-
-```
-qr-master/
-├── src/
-│   ├── app/                    # Next.js app router pages
-│   ├── components/             # React components
-│   ├── lib/                   # Utility functions and configurations
-│   ├── hooks/                 # Custom React hooks
-│   ├── styles/                # Global styles
-│   └── i18n/                  # Translation files
-├── prisma/                    # Database schema and migrations
-├── docker/                    # Docker initialization scripts
-│   ├── init-db.sh            # PostgreSQL initialization
-│   └── README.md             # Docker documentation
-├── public/                    # Static assets
-├── docker-compose.yml         # Production Docker setup
-├── docker-compose.dev.yml     # Development Docker setup
-├── Dockerfile                # Container definition
-├── DOCKER_SETUP.md           # Complete Docker guide
-└── env.example               # Environment template
-```
-
-## API Endpoints
-
-### Authentication
-
- `POST /api/auth/signin` - Sign in with credentials
- `POST /api/auth/signout` - Sign out
- `GET /api/auth/session` - Get current session
-
-### QR Codes
-
- `GET /api/qrs` - List all QR codes
- `POST /api/qrs` - Create a new QR code (dynamic or static)
- `POST /api/qrs/static` - Create a static QR code
- `GET /api/qrs/[id]` - Get QR code details
- `PATCH /api/qrs/[id]` - Update QR code
- `DELETE /api/qrs/[id]` - Delete QR code
- `DELETE /api/qrs/delete-all` - Delete all user's QR codes
-
-### Analytics
-
- `GET /api/analytics/summary` - Get analytics summary for a QR code
-
-### User & Settings
-
- `GET /api/user/plan` - Get current user plan
- `GET /api/user/stats` - Get user statistics
- `POST /api/user/password` - Update password
- `POST /api/user/profile` - Update profile
- `DELETE /api/user/delete` - Delete account
-
-### Stripe Payments
-
- `POST /api/stripe/checkout` - Create checkout session
- `POST /api/stripe/portal` - Create customer portal session
- `POST /api/stripe/webhook` - Handle Stripe webhooks
- `POST /api/stripe/cancel-subscription` - Cancel subscription
-
-### Public Redirect
-
- `GET /r/[slug]` - Redirect and track QR code scan
-
-## Environment Variables
-
-| Variable                             | Description                   | Required | Default                                                                |
-| ------------------------------------ | ----------------------------- | -------- | ---------------------------------------------------------------------- |
-| `DATABASE_URL`                       | PostgreSQL connection string  | Yes      | `postgresql://postgres:postgres@localhost:5435/qrmaster?schema=public` |
-| `NEXTAUTH_URL`                       | Application URL               | Yes      | `http://localhost:3050`                                                |
-| `NEXTAUTH_SECRET`                    | Secret for JWT encryption     | Yes      | Generate with `openssl rand -base64 32`                                |
-| `IP_SALT`                            | Salt for IP hashing (privacy) | Yes      | Generate with `openssl rand -base64 32`                                |
-| `GOOGLE_CLIENT_ID`                   | Google OAuth client ID        | No       | -                                                                      |
-| `GOOGLE_CLIENT_SECRET`               | Google OAuth client secret    | No       | -                                                                      |
-| `STRIPE_SECRET_KEY`                  | Stripe secret key             | No       | -                                                                      |
-| `STRIPE_WEBHOOK_SECRET`              | Stripe webhook signing secret | No       | -                                                                      |
-| `NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY` | Stripe public key             | No       | -                                                                      |
-| `NEXT_PUBLIC_INDEXABLE`              | Allow search engine indexing  | No       | `false` (set to `true` in production)                                  |
-| `REDIS_URL`                          | Redis connection string       | No       | `redis://redis:6379`                                                   |
-| `NEXT_PUBLIC_POSTHOG_KEY`            | PostHog analytics key         | No       | -                                                                      |
-| `NEXT_PUBLIC_POSTHOG_HOST`           | PostHog host URL              | No       | -                                                                      |
-
-**Note**: Copy `env.example` to `.env` and update the values before starting.
-
-### Generating Secrets
-
-```bash
-# Generate NEXTAUTH_SECRET
-openssl rand -base64 32
-
-# Generate IP_SALT
-openssl rand -base64 32
-```
-
-## Security & Privacy
-
- **IP Hashing**: IP addresses are hashed with salt before storage (GDPR-compliant)
- **DNT Respect**: Honors Do Not Track browser headers
- **Rate Limiting**: API endpoints protected against abuse
- **CSRF Protection**: Token-based CSRF validation on mutations
- **Secure Sessions**: NextAuth.js with encrypted JWT tokens
- **Stripe Security**: PCI-compliant payment processing
- **SQL Injection Prevention**: Prisma ORM parameterized queries
-
-## Database Schema
-
-The application uses PostgreSQL with Prisma ORM. Key models:
-
- **User**: User accounts with Stripe subscription data
- **QRCode**: QR code records (static/dynamic, multiple content types)
- **QRScan**: Scan analytics data (hashed IP, device, location, UTM params)
- **Integration**: Third-party integrations (Zapier, etc.)
- **Account/Session**: NextAuth authentication data
-
-### Supported QR Code Types
-
- **URL**: Website links
- **VCARD**: Contact cards (name, email, phone, company)
- **GEO**: GPS locations
- **PHONE**: Phone numbers (tel: links)
- **TEXT**: Plain text
- **SMS**: SMS messages
- **WHATSAPP**: WhatsApp messages
-
-### Plans
-
- **FREE**: 3 dynamic QR codes, unlimited static
- **PRO**: 50 codes, custom branding, advanced analytics
- **BUSINESS**: 500 codes, bulk upload, API access, priority support
-
-## Deployment
-
-### Docker (Recommended for Self-Hosting)
-
-The application includes production-ready Docker configuration with PostgreSQL and Redis:
-
-```bash
-# Build and start all services
-docker-compose up -d --build
-
-# Run migrations
-docker-compose exec web npx prisma migrate deploy
-
-# View logs
-docker-compose logs -f
-```
-
-For detailed deployment instructions, see [DOCKER_SETUP.md](DOCKER_SETUP.md).
-
-### Vercel
-
-1. Push your code to GitHub
-2. Import the project in Vercel
-3. Add a PostgreSQL database (Vercel Postgres, Supabase, or other)
-4. Add environment variables in Vercel dashboard
-5. Deploy
-
-**Note**: For Vercel deployment, you'll need to set up a PostgreSQL database separately.
-
-## Troubleshooting
-
-### Database Issues
-
-**Problem**: Migration errors or schema conflicts
-
-```bash
-# Solution: Reset the database
-npx prisma migrate reset
-```
-
-**Problem**: "Error: P1001: Can't reach database server"
-
-```bash
-# Check if Docker containers are running
-docker ps
-
-# Restart database
-npm run docker:dev:stop
-npm run docker:dev
-```
-
-**Problem**: Prisma Client out of sync
-
-```bash
-# Regenerate Prisma Client
-npx prisma generate
-```
-
-**Problem**: Need to start completely fresh
-
-```bash
-# Stop all Docker containers
-npm run docker:dev:stop
-
-# Remove volumes (⚠️ deletes all data)
-docker volume prune
-
-# Restart everything
-npm run docker:dev
-npx prisma migrate dev
-npm run db:seed
-```
-
-### Port Already in Use
-
-If port 3050 is already in use:
-
-```bash
-# Find and kill the process (Windows)
-netstat -ano | findstr :3050
-taskkill /PID <PID> /F
-
-# Or change the port in package.json
-"dev": "next dev -p 3051"
-```
-
-### Docker Issues
-
-**Problem**: Permission denied errors
-
-```bash
-# Windows: Run PowerShell as Administrator
-# Linux/Mac: Use sudo for docker commands
-```
-
-**Problem**: Out of disk space
-
-```bash
-# Clean up Docker
-docker system prune -a
-```
-
-## Contributing
-
-1. Fork the repository
-2. Create your feature branch (`git checkout -b feature/amazing-feature`)
-3. Commit your changes (`git commit -m 'Add some amazing feature'`)
-4. Push to the branch (`git push origin feature/amazing-feature`)
-5. Open a Pull Request
-
-## License
-
-This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
-
-## Support
-
-For support, email support@qrmaster.net or open an issue on GitHub.
-
-## Acknowledgments
-
- Next.js team for the amazing framework
- Vercel for hosting and deployment
- All open-source contributors
-
---
-
-Built with ❤️ by QR Master Team
+# QR Master - Create Custom QR Codes in Seconds
+
+A production-ready SaaS application for creating and managing QR codes with advanced tracking, analytics, and Stripe payment integration.
+
+## Features
+
+- 🎨 **Custom QR Codes** - Create static and dynamic QR codes with full customization
+- 📊 **Advanced Analytics** - Track scans, locations, devices, and user behavior
+- 🔄 **Dynamic Content** - Edit QR code destinations anytime without reprinting
+- 📦 **Bulk Operations** - Import CSV/Excel files to create up to 1,000 QR codes at once
+- 💳 **Stripe Integration** - FREE, PRO, and BUSINESS subscription plans with secure billing
+- 🎨 **Custom Branding** - Logo upload, custom colors (PRO+ plans)
+- 🌍 **SEO Optimized** - Schema.org structured data, meta tags, breadcrumbs
+- 🔒 **Privacy-First** - GDPR-compliant, hashed IPs, DNT headers respected
+- 📱 **Responsive Design** - Works perfectly on all devices
+
+## Tech Stack
+
+- **Frontend**: Next.js 14 (App Router), TypeScript, Tailwind CSS
+- **Backend**: Next.js API Routes, Prisma ORM
+- **Database**: PostgreSQL (with Prisma migrations)
+- **Cache**: Redis (optional)
+- **Auth**: NextAuth.js (Credentials + Google OAuth)
+- **Payments**: Stripe (Subscriptions & Webhooks)
+- **QR Generation**: qrcode library
+- **Bulk Processing**: Papa Parse (CSV), XLSX, JSZip
+- **Analytics**: PostHog (optional)
+- **SEO**: next-sitemap, Schema.org structured data
+
+## Quick Start
+
+### Prerequisites
+
+- Node.js 18+
+- Docker and Docker Compose V2
+- Git
+
+### Installation
+
+#### Option 1: Development Mode (Recommended)
+
+Run database in Docker, app on host machine:
+
+1. Clone the repository:
+
+```bash
+git clone https://github.com/yourusername/qr-master.git
+cd qr-master
+```
+
+2. Install dependencies:
+
+```bash
+npm install
+```
+
+3. Copy and configure environment:
+
+```bash
+cp env.example .env
+```
+
+Edit `.env` and set:
+
+- `NEXTAUTH_SECRET` (generate: `openssl rand -base64 32`)
+- `IP_SALT` (generate: `openssl rand -base64 32`)
+- (Optional) Google OAuth credentials
+
+4. Start database services:
+
+```bash
+npm run docker:dev
+```
+
+5. Run database migrations and seed:
+
+```bash
+npx prisma migrate dev
+npm run db:seed
+```
+
+> **Note**: If you get migration errors, you can reset the database:
+>
+> ```bash
+> npx prisma migrate reset
+> ```
+>
+> This will drop the database, recreate it, run all migrations, and seed data.
+
+6. Start development server:
+
+```bash
+npm run dev
+```
+
+7. Access the application:
+   - **App**: http://localhost:3050
+   - **Database UI**: http://localhost:8080 (Adminer - username: `root`, password: `root`)
+   - **Database**: localhost:5435 (username: `postgres`, password: `postgres`)
+   - **Redis**: localhost:6379
+
+#### Option 2: Full Docker (Production)
+
+Run everything in Docker:
+
+1. Clone and setup:
+
+```bash
+git clone https://github.com/yourusername/qr-master.git
+cd qr-master
+cp env.example .env
+# Edit .env with your configuration
+```
+
+2. Build and start:
+
+```bash
+npm run docker:prod
+```
+
+3. Run migrations:
+
+```bash
+docker-compose exec web npx prisma migrate deploy
+```
+
+4. Access at http://localhost:3050
+
+📚 **For detailed Docker setup, see [DOCKER_SETUP.md](DOCKER_SETUP.md)**
+
+## Demo Account
+
+After running `npm run db:seed`, use these credentials to test the application:
+
+- **Email**: demo@qrmaster.com
+- **Password**: demo123
+- **Plan**: FREE (3 QR codes limit)
+
+The seed script also creates sample QR codes for testing.
+
+## Development
+
+### Available Scripts
+
+```bash
+# Development
+npm run dev                    # Start Next.js dev server (port 3050)
+npm run build                  # Build for production
+npm run start                  # Start production server
+
+# Database
+npm run db:generate            # Generate Prisma Client
+npm run db:migrate             # Run migrations (dev mode)
+npm run db:deploy              # Deploy migrations (production)
+npm run db:seed                # Seed database with demo data
+npm run db:studio              # Open Prisma Studio UI
+npx prisma migrate reset       # Reset database (drop, recreate, migrate, seed)
+
+# Docker
+npm run docker:dev             # Start DB & Redis only
+npm run docker:dev:stop        # Stop dev services
+npm run docker:dev:clean       # Stop and clean containers
+npm run docker:prod            # Start full stack (production)
+npm run docker:stop            # Stop all services
+npm run docker:logs            # View container logs
+npm run docker:db              # PostgreSQL CLI
+npm run docker:redis           # Redis CLI
+npm run docker:backup          # Backup database to SQL file
+```
+
+### Local Development (without Docker)
+
+1. Install dependencies:
+
+```bash
+npm install
+```
+
+2. Set up PostgreSQL and Redis locally
+
+3. Configure `.env` with local database URL:
+
+```env
+DATABASE_URL=postgresql://postgres:postgres@localhost:5435/qrmaster?schema=public
+```
+
+4. Run migrations and seed:
+
+```bash
+npx prisma migrate dev
+npm run db:seed
+```
+
+5. Start dev server:
+
+```bash
+npm run dev
+```
+
+### Resetting the Database
+
+If you need to reset your database (drop all tables, recreate, and reseed):
+
+```bash
+# Full reset (drops database, reruns migrations, seeds data)
+npx prisma migrate reset
+
+# Or manually:
+npx prisma migrate reset --skip-seed  # Reset without seeding
+npm run db:seed                        # Then seed manually
+```
+
+This is useful when:
+
+- Schema has changed significantly
+- You have migration conflicts
+- You want to start fresh with clean data
+
+### Project Structure
+
+```
+qr-master/
+├── src/
+│   ├── app/                    # Next.js app router pages
+│   ├── components/             # React components
+│   ├── lib/                   # Utility functions and configurations
+│   ├── hooks/                 # Custom React hooks
+│   ├── styles/                # Global styles
+│   └── i18n/                  # Translation files
+├── prisma/                    # Database schema and migrations
+├── docker/                    # Docker initialization scripts
+│   ├── init-db.sh            # PostgreSQL initialization
+│   └── README.md             # Docker documentation
+├── public/                    # Static assets
+├── docker-compose.yml         # Production Docker setup
+├── docker-compose.dev.yml     # Development Docker setup
+├── Dockerfile                # Container definition
+├── DOCKER_SETUP.md           # Complete Docker guide
+└── env.example               # Environment template
+```
+
+## API Endpoints
+
+### Authentication
+
+- `POST /api/auth/signin` - Sign in with credentials
+- `POST /api/auth/signout` - Sign out
+- `GET /api/auth/session` - Get current session
+
+### QR Codes
+
+- `GET /api/qrs` - List all QR codes
+- `POST /api/qrs` - Create a new QR code (dynamic or static)
+- `POST /api/qrs/static` - Create a static QR code
+- `GET /api/qrs/[id]` - Get QR code details
+- `PATCH /api/qrs/[id]` - Update QR code
+- `DELETE /api/qrs/[id]` - Delete QR code
+- `DELETE /api/qrs/delete-all` - Delete all user's QR codes
+
+### Analytics
+
+- `GET /api/analytics/summary` - Get analytics summary for a QR code
+
+### User & Settings
+
+- `GET /api/user/plan` - Get current user plan
+- `GET /api/user/stats` - Get user statistics
+- `POST /api/user/password` - Update password
+- `POST /api/user/profile` - Update profile
+- `DELETE /api/user/delete` - Delete account
+
+### Stripe Payments
+
+- `POST /api/stripe/checkout` - Create checkout session
+- `POST /api/stripe/portal` - Create customer portal session
+- `POST /api/stripe/webhook` - Handle Stripe webhooks
+- `POST /api/stripe/cancel-subscription` - Cancel subscription
+
+### Public Redirect
+
+- `GET /r/[slug]` - Redirect and track QR code scan
+
+## Environment Variables
+
+| Variable                             | Description                   | Required | Default                                                                |
+| ------------------------------------ | ----------------------------- | -------- | ---------------------------------------------------------------------- |
+| `DATABASE_URL`                       | PostgreSQL connection string  | Yes      | -                                                                      |
+| `NEXTAUTH_URL`                       | Application URL               | Yes      | `http://localhost:3050`                                                |
+| `NEXTAUTH_SECRET`                    | Secret for JWT encryption     | Yes      | - (Generate with `openssl rand -base64 32`)                            |
+| `IP_SALT`                            | Salt for IP hashing (privacy) | Yes      | Generate with `openssl rand -base64 32`                                |
+| `GOOGLE_CLIENT_ID`                   | Google OAuth client ID        | No       | -                                                                      |
+| `GOOGLE_CLIENT_SECRET`               | Google OAuth client secret    | No       | -                                                                      |
+| `STRIPE_SECRET_KEY`                  | Stripe secret key             | No       | -                                                                      |
+| `STRIPE_WEBHOOK_SECRET`              | Stripe webhook signing secret | No       | -                                                                      |
+| `NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY` | Stripe public key             | No       | -                                                                      |
+| `NEXT_PUBLIC_INDEXABLE`              | Allow search engine indexing  | No       | `false` (set to `true` in production)                                  |
+| `REDIS_URL`                          | Redis connection string       | No       | `redis://redis:6379`                                                   |
+| `NEXT_PUBLIC_POSTHOG_KEY`            | PostHog analytics key         | No       | -                                                                      |
+| `NEXT_PUBLIC_POSTHOG_HOST`           | PostHog host URL              | No       | -                                                                      |
+
+**Note**: Copy `env.example` to `.env` and update the values before starting.
+
+### Generating Secrets
+
+```bash
+# Generate NEXTAUTH_SECRET
+openssl rand -base64 32
+
+# Generate IP_SALT
+openssl rand -base64 32
+```
+
+## Security & Privacy
+
+- **IP Hashing**: IP addresses are hashed with salt before storage (GDPR-compliant)
+- **DNT Respect**: Honors Do Not Track browser headers
+- **Rate Limiting**: API endpoints protected against abuse
+- **CSRF Protection**: Token-based CSRF validation on mutations
+- **Secure Sessions**: NextAuth.js with encrypted JWT tokens
+- **Stripe Security**: PCI-compliant payment processing
+- **SQL Injection Prevention**: Prisma ORM parameterized queries
+
+## Database Schema
+
+The application uses PostgreSQL with Prisma ORM. Key models:
+
+- **User**: User accounts with Stripe subscription data
+- **QRCode**: QR code records (static/dynamic, multiple content types)
+- **QRScan**: Scan analytics data (hashed IP, device, location, UTM params)
+- **Integration**: Third-party integrations (Zapier, etc.)
+- **Account/Session**: NextAuth authentication data
+
+### Supported QR Code Types
+
+- **URL**: Website links
+- **VCARD**: Contact cards (name, email, phone, company)
+- **GEO**: GPS locations
+- **PHONE**: Phone numbers (tel: links)
+- **TEXT**: Plain text
+- **SMS**: SMS messages
+- **WHATSAPP**: WhatsApp messages
+
+### Plans
+
+- **FREE**: 3 dynamic QR codes, unlimited static
+- **PRO**: 50 codes, custom branding, advanced analytics
+- **BUSINESS**: 500 codes, bulk upload, API access, priority support
+
+## Deployment
+
+### Docker (Recommended for Self-Hosting)
+
+The application includes production-ready Docker configuration with PostgreSQL and Redis:
+
+```bash
+# Build and start all services
+docker-compose up -d --build
+
+# Run migrations
+docker-compose exec web npx prisma migrate deploy
+
+# View logs
+docker-compose logs -f
+```
+
+For detailed deployment instructions, see [DOCKER_SETUP.md](DOCKER_SETUP.md).
+
+### Vercel
+
+1. Push your code to GitHub
+2. Import the project in Vercel
+3. Add a PostgreSQL database (Vercel Postgres, Supabase, or other)
+4. Add environment variables in Vercel dashboard
+5. Deploy
+
+**Note**: For Vercel deployment, you'll need to set up a PostgreSQL database separately.
+
+## Troubleshooting
+
+### Database Issues
+
+**Problem**: Migration errors or schema conflicts
+
+```bash
+# Solution: Reset the database
+npx prisma migrate reset
+```
+
+**Problem**: "Error: P1001: Can't reach database server"
+
+```bash
+# Check if Docker containers are running
+docker ps
+
+# Restart database
+npm run docker:dev:stop
+npm run docker:dev
+```
+
+**Problem**: Prisma Client out of sync
+
+```bash
+# Regenerate Prisma Client
+npx prisma generate
+```
+
+**Problem**: Need to start completely fresh
+
+```bash
+# Stop all Docker containers
+npm run docker:dev:stop
+
+# Remove volumes (⚠️ deletes all data)
+docker volume prune
+
+# Restart everything
+npm run docker:dev
+npx prisma migrate dev
+npm run db:seed
+```
+
+### Port Already in Use
+
+If port 3050 is already in use:
+
+```bash
+# Find and kill the process (Windows)
+netstat -ano | findstr :3050
+taskkill /PID <PID> /F
+
+# Or change the port in package.json
+"dev": "next dev -p 3051"
+```
+
+### Docker Issues
+
+**Problem**: Permission denied errors
+
+```bash
+# Windows: Run PowerShell as Administrator
+# Linux/Mac: Use sudo for docker commands
+```
+
+**Problem**: Out of disk space
+
+```bash
+# Clean up Docker
+docker system prune -a
+```
+
+## Contributing
+
+1. Fork the repository
+2. Create your feature branch (`git checkout -b feature/amazing-feature`)
+3. Commit your changes (`git commit -m 'Add some amazing feature'`)
+4. Push to the branch (`git push origin feature/amazing-feature`)
+5. Open a Pull Request
+
+## License
+
+This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
+
+## Support
+
+For support, email support@qrmaster.net or open an issue on GitHub.
+
+## Acknowledgments
+
+- Next.js team for the amazing framework
+- Vercel for hosting and deployment
+- All open-source contributors
+
+---
+
+Built with ❤️ by QR Master Team
+
+
+
+Führe diese im Terminal aus:
+
+IndexNow (Bing/Yandex + Partner): npm run submit:indexnow
+Google Indexing API: npm run trigger:indexing
--- a/SETUP_COMPLETE.md
+++ b/SETUP_COMPLETE.md
@@ -1,301 +0,0 @@
-# ✅ Setup Complete - PostgreSQL Migration
-
-## 🎉 What Was Done
-
-Your QR Master application has been successfully migrated from Supabase to a local PostgreSQL database with Docker!
-
-### ✅ Completed Tasks
-
-1. **Removed Supabase Dependencies**
-   - ❌ Removed `DIRECT_URL` from Prisma schema
-   - ❌ Removed `DIRECT_URL` from environment validation
-   - ❌ Cleaned up all Supabase-specific configurations
-
-2. **Created Docker Infrastructure**
-   - ✅ Production Docker Compose (`docker-compose.yml`)
-   - ✅ Development Docker Compose (`docker-compose.dev.yml`)
-   - ✅ Optimized Dockerfile for Next.js
-   - ✅ PostgreSQL 16 Alpine with persistence
-   - ✅ Redis 7 Alpine with AOF persistence
-   - ✅ Adminer database UI (optional)
-   - ✅ Custom bridge network for services
-
-3. **Database Setup**
-   - ✅ PostgreSQL initialization script
-   - ✅ UUID and pg_trgm extensions
-   - ✅ Health checks for all services
-   - ✅ Volume persistence
-
-4. **Documentation**
-   - ✅ Updated README.md
-   - ✅ Created DOCKER_SETUP.md (comprehensive guide)
-   - ✅ Created MIGRATION_FROM_SUPABASE.md
-   - ✅ Created docker/README.md
-   - ✅ Created CHANGELOG.md
-   - ✅ Created env.example template
-
-5. **Developer Tools**
-   - ✅ Setup script for Linux/Mac (`scripts/setup.sh`)
-   - ✅ Setup script for Windows (`scripts/setup.ps1`)
-   - ✅ npm Docker scripts
-   - ✅ .dockerignore for optimization
-
-6. **Environment Configuration**
-   - ✅ Created env.example template
-   - ✅ Updated environment validation
-   - ✅ Simplified configuration
-
-## 🚀 How to Get Started
-
-### Option 1: Quick Setup (Recommended)
-
-#### Windows:
-```powershell
-cd scripts
-.\setup.ps1
-```
-
-#### Linux/Mac:
-```bash
-chmod +x scripts/setup.sh
-./scripts/setup.sh
-```
-
-### Option 2: Manual Setup
-
-#### Development Mode (Database in Docker, App on Host)
-```bash
-# 1. Copy environment file
-cp env.example .env
-
-# 2. Edit .env and set NEXTAUTH_SECRET and IP_SALT
-# Generate with: openssl rand -base64 32
-
-# 3. Install dependencies
-npm install
-
-# 4. Start database services
-npm run docker:dev
-
-# 5. Run migrations
-npm run db:migrate
-
-# 6. Seed database
-npm run db:seed
-
-# 7. Start development server
-npm run dev
-```
-
-#### Production Mode (Full Stack in Docker)
-```bash
-# 1. Copy and configure environment
-cp env.example .env
-# Edit .env with your settings
-
-# 2. Build and start
-npm run docker:prod
-
-# 3. Run migrations
-docker-compose exec web npx prisma migrate deploy
-
-# 4. Access at http://localhost:3050
-```
-
-## 📍 Access Points
-
-After setup, you can access:
-
- **🌐 Application**: http://localhost:3050
- **🗄️ Database UI (Adminer)**: http://localhost:8080
-  - System: PostgreSQL
-  - Server: db
-  - Username: postgres
-  - Password: postgres
-  - Database: qrmaster
- **💾 PostgreSQL**: localhost:5432
- **🔴 Redis**: localhost:6379
-
-## 📦 What's Included
-
-### Docker Services
-
-| Service | Image | Port | Purpose |
-|---------|-------|------|---------|
-| web | Next.js (custom) | 3050 | Application |
-| db | postgres:16-alpine | 5432 | Database |
-| redis | redis:7-alpine | 6379 | Cache |
-| adminer | adminer:latest | 8080 | DB UI |
-
-### File Structure
-
-```
-QRMASTER/
-├── docker/
-│   ├── init-db.sh              # PostgreSQL initialization
-│   └── README.md               # Docker commands
-├── scripts/
-│   ├── setup.sh                # Quick setup (Linux/Mac)
-│   └── setup.ps1               # Quick setup (Windows)
-├── src/                        # Application code
-├── prisma/
-│   └── schema.prisma           # Updated schema (no directUrl)
-├── docker-compose.yml          # Production setup
-├── docker-compose.dev.yml      # Development setup
-├── Dockerfile                  # Application container
-├── env.example                 # Environment template
-├── .dockerignore              # Docker build optimization
-├── DOCKER_SETUP.md            # Complete Docker guide
-├── MIGRATION_FROM_SUPABASE.md # Migration guide
-├── CHANGELOG.md               # What changed
-└── README.md                  # Updated main docs
-```
-
-## 🛠️ Useful Commands
-
-### Development
-```bash
-npm run dev              # Start dev server
-npm run docker:dev       # Start database only
-npm run docker:dev:stop  # Stop database
-```
-
-### Database
-```bash
-npm run db:migrate       # Run migrations
-npm run db:seed          # Seed database
-npm run db:studio        # Open Prisma Studio
-npm run docker:db        # PostgreSQL CLI
-```
-
-### Docker
-```bash
-npm run docker:prod      # Start all services
-npm run docker:stop      # Stop all services
-npm run docker:logs      # View logs
-npm run docker:backup    # Backup database
-```
-
-### Management
-```bash
-docker-compose ps                    # Check status
-docker-compose logs -f               # Follow logs
-docker-compose restart web           # Restart app
-docker-compose exec db psql -U postgres -d qrmaster  # DB CLI
-```
-
-## 📚 Documentation
-
- **[README.md](README.md)** - Main documentation with quick start
- **[DOCKER_SETUP.md](DOCKER_SETUP.md)** - Complete Docker guide with troubleshooting
- **[MIGRATION_FROM_SUPABASE.md](MIGRATION_FROM_SUPABASE.md)** - Migration guide from Supabase
- **[docker/README.md](docker/README.md)** - Docker commands and operations
- **[CHANGELOG.md](CHANGELOG.md)** - What changed in this version
-
-## 🔐 Security Checklist
-
-Before deploying to production:
-
- [ ] Change PostgreSQL password in docker-compose.yml
- [ ] Set strong NEXTAUTH_SECRET (generate with `openssl rand -base64 32`)
- [ ] Set strong IP_SALT (generate with `openssl rand -base64 32`)
- [ ] Update NEXTAUTH_URL to your domain
- [ ] Enable HTTPS/SSL
- [ ] Set up firewall rules
- [ ] Configure automated backups
- [ ] Review and test all environment variables
-
-## 🎯 Next Steps
-
-1. **Test the Application**
-   ```bash
-   npm run docker:dev
-   npm run dev
-   # Visit http://localhost:3050
-   ```
-
-2. **Review Configuration**
-   - Check `.env` file
-   - Verify database connection
-   - Test authentication
-
-3. **Set Up Backups**
-   ```bash
-   # Manual backup
-   npm run docker:backup
-   
-   # Or create automated backup script
-   # See DOCKER_SETUP.md for examples
-   ```
-
-4. **Customize**
-   - Update database passwords
-   - Configure OAuth providers
-   - Adjust resource limits
-   - Set up monitoring
-
-## 🆘 Need Help?
-
-### Common Issues
-
-**Database won't start:**
-```bash
-docker-compose logs db
-docker-compose restart db
-```
-
-**Port already in use:**
-```bash
-# Windows
-netstat -ano | findstr :3050
-
-# Change port in docker-compose.yml if needed
-```
-
-**Prisma errors:**
-```bash
-npm run db:generate
-npm run db:migrate
-```
-
-### Resources
-
- **DOCKER_SETUP.md** - Comprehensive troubleshooting
- **docker/README.md** - Common Docker commands
- **MIGRATION_FROM_SUPABASE.md** - Migration help
-
-### Support
-
-1. Check the documentation files
-2. Review logs: `docker-compose logs -f`
-3. Check service health: `docker-compose ps`
-4. Open an issue on GitHub
-
-## ✨ Features
-
-Your application now has:
-
- ✅ **Self-hosted PostgreSQL** - Full control over your data
- ✅ **Redis caching** - Improved performance
- ✅ **Docker Compose** - Easy deployment
- ✅ **Health checks** - Automatic monitoring
- ✅ **Data persistence** - Volumes for data safety
- ✅ **Database UI** - Adminer for easy management
- ✅ **Development mode** - Run only what you need
- ✅ **Production ready** - Optimized Docker builds
- ✅ **Complete docs** - Multiple guides and references
-
-## 🎊 Success!
-
-You're now ready to develop and deploy QR Master with your own PostgreSQL database!
-
-**Demo Credentials:**
- Email: demo@qrmaster.com
- Password: demo123
-
---
-
-**Happy coding!** 🚀
-
-Need more help? Check the documentation or run the setup scripts.
-
--- a/SIDE_PROJECT_STRATEGY.md
+++ b/SIDE_PROJECT_STRATEGY.md
@@ -0,0 +1,291 @@
+# 🚀 Side Project Marketing Strategy
+
+> **"Engineering as Marketing"** – Kostenlose Micro-Tools bauen, um SEO-Traffic abzufangen und in zahlende Kunden zu konvertieren.
+
+**Status:** Planung abgeschlossen, bereit für Implementierung  
+**Autor:** QR Master Team  
+**Letzte Aktualisierung:** 2026-01-08
+
+---
+
+## Executive Summary
+
+Wir nutzen die bewiesene "Engineering as Marketing" Strategie (bekannt von HubSpot's Website Grader, Ahrefs' Free Tools, Shopify's Business Tools), um organischen Traffic über spezialisierte, kostenlose QR-Generatoren zu gewinnen.
+
+### Das Konzept in einem Satz
+
+> Anstatt gegen "QR Code Generator" (DA 90+ Konkurrenz) zu kämpfen, bauen wir 10 spezialisierte Tools für Long-Tail-Keywords wie "WiFi QR Code erstellen" oder "VCard QR Generator".
+
+### Warum das funktioniert
+
+1. **Weniger Konkurrenz:** "WiFi QR Code Generator" hat 1/10 der Konkurrenz von "QR Code Generator"
+2. **Höhere Kaufabsicht:** Wer "Restaurant Menu QR Code" sucht, ist bereit für ein Premium-Tool
+3. **Natürliche Backlinks:** Leute teilen nützliche Tools ("Hier, dieser Generator ist kostenlos")
+4. **Zero Marginal Cost:** Client-Side Generierung = 0€ Serverkosten pro User
+
+---
+
+## ROI Projektion (Konservativ)
+
+| Metrik | Monat 3 | Monat 6 | Monat 12 |
+|--------|---------|---------|----------|
+| Organischer Traffic (alle Tools) | 2.000 | 10.000 | 25.000 |
+| Free Signups (20% Conv.) | 400 | 2.000 | 5.000 |
+| Paid Customers (3% der Signups) | 12 | 60 | 150 |
+| **Zusätzlicher MRR** | **108€** | **540€** | **1.350€** |
+
+> **Benchmarks verwendet:** 2-3% Free-to-Paid Conversion (Industry Standard), 20% Tool-to-Signup (optimistisch, aber erreichbar mit gutem UX).
+
+---
+
+## Die Tools-Roadmap
+
+### Phase 1: Quick Wins (Woche 1-2)
+
+Fokus auf **hohes Suchvolumen + geringe Komplexität**.
+
+| Tool | URL | Geschätztes SV | Implementierungs-Aufwand |
+|------|-----|----------------|-------------------------|
+| **WiFi QR Generator** | `/tools/wifi-qr-code` | 40.000/Monat | 4h |
+| **VCard QR Generator** | `/tools/vcard-qr-code` | 15.000/Monat | 4h |
+| **WhatsApp QR Generator** | `/tools/whatsapp-qr-code` | 20.000/Monat | 3h |
+
+### Phase 2: Monetization Focus (Woche 3-4)
+
+Fokus auf **hohe Conversion-Wahrscheinlichkeit** (B2B Use Cases).
+
+| Tool | URL | Geschätztes SV | Upsell-Hook |
+|------|-----|----------------|-------------|
+| **App Store Link QR** | `/tools/app-store-qr-code` | 5.000/Monat | Smart Routing (iOS/Android) |
+| **PDF to QR** | `/tools/pdf-qr-code` | 15.000/Monat | PDF Hosting (benötigt Account) |
+| **Menu QR Generator** | `/tools/menu-qr-code` | 8.000/Monat | Multi-Sprache, Analytics |
+
+### Phase 3: Differenzierung (Monat 2+)
+
+Fokus auf **Unique Features** die Konkurrenten nicht haben.
+
+| Tool | URL | Differenzierung |
+|------|-----|-----------------|
+| **Barcode Generator** | `/tools/barcode-generator` | EAN/UPC/ISBN Unterstützung |
+| **Bitcoin/Crypto QR** | `/tools/bitcoin-qr-code` | Multi-Wallet Format |
+| **AI Art QR (Viral)** | `/tools/ai-qr-code` | Stable Diffusion Integration |
+
+## Geplantes Portfolio: Kostenlose Statische Generatoren (15 Typen)
+
+Wir werden die folgenden 15 statischen QR-Code-Typen anbieten. Diese sind **dauerhaft kostenlos** und erfordern keine Server-Infrastruktur für Redirects (im Gegensatz zu dynamischen Codes).
+
+> **Wichtig:** Alle diese Generatoren stehen sowohl **öffentlich als SEO-Landingpages** zur Verfügung (zur Neukundengewinnung), als auch im **eingeloggten Bereich** für registrierte Nutzer (für Komfort und Zentralisierung).
+
+1. **URL / Link**: Der Standard. Öffnet eine Webseite.
+2. **Text**: Zeigt reinen Text an (bis zu 300 Zeichen).
+3. **WiFi**: Verbindet direkt mit einem WLAN-Netzwerk (WPA/WEP/Open).
+4. **VCard / Kontakt**: Speichert einen Kontakt direkt im Adressbuch.
+5. **WhatsApp**: Startet einen Chat mit einer Nummer (und optionalem Text).
+6. **E-Mail**: Öffnet das E-Mail-Programm mit Empfänger, Betreff und Body.
+7. **SMS**: Bereitet eine SMS an eine Nummer vor.
+8. **Anruf / Tel**: Startet einen Anruf an eine Nummer.
+9. **Event / Kalender**: Fügt einen Termin zum Kalender hinzu (.ics).
+10. **Geo / Maps**: Öffnet einen Standort in Google Maps/Apple Maps.
+11. **Facebook**: Öffnet ein Profil oder eine Seite.
+12. **Instagram**: Öffnet ein Instagram-Profil.
+13. **Twitter / X**: Öffnet ein Profil oder erstellt einen Tweet.
+14. **YouTube**: Öffnet ein Video oder einen Kanal.
+15. **TikTok**: Öffnet ein TikTok-Profil.
+
+Diese Breite deckt 99% der "Everyday Use Cases" ab und maximiert die SEO-Angriffsfläche.
+
+---
+
+## Technische Architektur
+
+### Warum Client-Side Generierung?
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│                      USER BROWSER                            │
+│                                                              │
+│  ┌─────────────┐    ┌──────────────┐    ┌────────────────┐  │
+│  │ Form Input  │ -> │ qrcode.js    │ -> │ Canvas/SVG     │  │
+│  │ (SSID, PW)  │    │ (generation) │    │ (download)     │  │
+│  └─────────────┘    └──────────────┘    └────────────────┘  │
+│                                                              │
+│                    KEINE Server-Calls!                       │
+└─────────────────────────────────────────────────────────────┘
+```
+
+**Vorteile:**
+- **Privatsphäre:** Passwörter verlassen nie den Browser
+- **Speed:** Instant Generation (kein Network Latency)
+- **Kosten:** 0€ pro generiertem Code
+- **Scale:** Kein Backend-Limit
+
+### Datei-Struktur (Next.js)
+
+```
+src/app/(marketing)/tools/
+├── wifi-qr-code/
+│   ├── page.tsx          # Server Component (SEO)
+│   └── WiFiGenerator.tsx # Client Component (Interaktion)
+├── vcard-qr-code/
+│   ├── page.tsx
+│   └── VCardGenerator.tsx
+└── [weitere tools]/
+```
+
+### Shared Components
+
+```typescript
+// src/components/tools/QRDownloadButtons.tsx
+// Wiederverwendbare Download-Buttons für alle Tools
+
+// src/components/tools/UpgradePrompt.tsx  
+// "Willst du Scans tracken?" CTA Box
+```
+
+---
+
+## SEO-Strategie pro Tool-Page
+
+Jede Seite folgt dem gleichen bewährten Muster:
+
+### 1. Above the Fold: Sofort nutzbar
+
+```
+┌────────────────────────────────────────┐
+│  H1: Free WiFi QR Code Generator       │
+│  Subline: Teile dein WLAN in Sekunden  │
+│                                        │
+│  ┌─────────────────────────────────┐   │
+│  │     [SSID]  [Password]  [WPA▼] │   │
+│  │                                 │   │
+│  │     [  Generate QR Code  ]      │   │
+│  └─────────────────────────────────┘   │
+└────────────────────────────────────────┘
+```
+
+**Regel:** Der User muss SOFORT interagieren können. Kein langer Intro-Text.
+
+### 2. Schema Markup (Pflicht!)
+
+```json
+{
+  "@context": "https://schema.org",
+  "@type": "SoftwareApplication",
+  "name": "WiFi QR Code Generator",
+  "applicationCategory": "UtilitiesApplication",
+  "operatingSystem": "Web Browser",
+  "offers": {
+    "@type": "Offer",
+    "price": "0",
+    "priceCurrency": "EUR"
+  },
+  "aggregateRating": {
+    "@type": "AggregateRating",
+    "ratingValue": "4.8",
+    "ratingCount": "1247"
+  }
+}
+```
+
+### 3. FAQ Section (Long-Tail Keywords)
+
+```markdown
+## Häufig gestellte Fragen
+
+### Wie funktioniert ein WiFi QR Code?
+Der QR Code enthält deine WLAN-Daten im Format...
+
+### Ist es sicher, mein WiFi Passwort in einem QR Code zu speichern?
+Ja, der QR Code wird nur lokal in deinem Browser generiert...
+
+### Kann ich den QR Code später bearbeiten?
+Dieser Generator erstellt statische Codes. Für editierbare...
+```
+
+### 4. Conversion Prompt (Der Hook)
+
+```
+┌─────────────────────────────────────────────────────────┐
+│  ✅ QR Code erfolgreich erstellt!                       │
+│                                                         │
+│  ⚠️ Hinweis: Dies ist ein statischer Code.             │
+│  Wenn du dein Passwort änderst, musst du neu drucken.  │
+│                                                         │
+│  → Erstelle einen dynamischen Code (jederzeit änderbar) │
+│                                                         │
+│  Bonus: Sieh wer deinen Code scannt (Datum, Standort)  │
+│                                                         │
+│  [ Kostenlos registrieren ]                             │
+└─────────────────────────────────────────────────────────┘
+```
+
+---
+
+## Conversion Optimierung
+
+### Die "Limitation Awareness" Methode
+
+Jedes Tool zeigt nach der Generierung **sanft** die Limitierungen auf:
+
+| Tool | Statische Limitation | Upsell-Feature |
+|------|---------------------|----------------|
+| WiFi | Passwort-Änderung = Neudruck | Dynamischer Code (editierbar) |
+| VCard | Kontakt-Update = Neudruck | Immer aktuelle Visitenkarte |
+| Menu | Neue Speisekarte = Neudruck | PDF-Hosting + Analytics |
+| App Store | Nur ein Store-Link | Smart Device Detection |
+
+### Email Capture vor Download
+
+**Optional (A/B testen):** 
+```
+"Gib deine Email ein, um den QR als hochauflösende PNG zu erhalten"
+```
+→ Baut Email-Liste, auch wenn User nicht sofort konvertiert.
+
+---
+
+## Erfolgsmetriken (KPIs)
+
+| KPI | Tool | Ziel (Monat 3) |
+|-----|------|----------------|
+| **Organic Sessions** | Google Analytics | 2.000/Monat |
+| **QR Generations** | PostHog Event | 500/Monat |
+| **Signup Clicks** | PostHog Event | 100/Monat |
+| **Actual Signups** | DB Query | 50/Monat |
+| **Paid Conversion** | Stripe | 5/Monat |
+
+### Tracking Events implementieren
+
+```typescript
+// Auf jeder Tool-Page
+posthog.capture('tool_qr_generated', { 
+  tool: 'wifi',
+  format: 'png' 
+});
+
+posthog.capture('tool_signup_cta_clicked', { 
+  tool: 'wifi' 
+});
+```
+
+---
+
+## Nächste Schritte
+
+1. [ ] **Heute:** WiFi QR Generator implementieren (`/tools/wifi-qr-code`)
+2. [ ] **Diese Woche:** VCard + WhatsApp Generator
+3. [ ] **Nächste Woche:** Google Search Console monitoren für erste Impressions
+4. [ ] **Monat 2:** A/B Test Email-Capture vs. Direct Download
+5. [ ] **Monat 3:** Phase 2 Tools (App Store, PDF, Menu)
+
+---
+
+## Referenzen & Inspiration
+
+- [HubSpot Website Grader](https://website.grader.com/) – Das Original "Engineering as Marketing"
+- [Ahrefs Free Tools](https://ahrefs.com/free-seo-tools) – 12+ Free Tools als Lead Magnets
+- [Shopify Business Tools](https://www.shopify.com/tools) – Logo Maker, Invoice Generator, etc.
+
+---
+
+*Dieses Dokument wird regelmäßig aktualisiert basierend auf Traffic-Daten und Conversion-Rates.*
--- a/v2.0.pdf
+++ b/v2.0.pdf
--- a/TODO.md
+++ b/TODO.md
@@ -0,0 +1,461 @@
+# QR Master — Growth TODO
+
+Based on: 3-month audit (PostHog + GSC + AI citations + full codebase review, April 2026)
+Domain age at audit: ~3 months | Visitors (90d): 169 | AI citations (33d): 1,849
+
+---
+
+## How to use this file
+
+Sections are ordered by impact-per-hour-of-work. Don't skip to section 5 before section 1.
+Each task has the exact file to touch and what to change. No hand-waving.
+
+---
+
+## Section 1 — Retention (do this week, nothing else matters until it's done)
+
+Cohort data shows ~10% week-1 retention, near-zero by week 3. Root cause: **no email is sent after signup**. Zero. The `sendWelcomeEmail` function does not exist. Users sign up and hear nothing.
+
+### 1.1 — Welcome email sequence (3 emails)
+
+**File to edit:** `src/lib/email.ts`
+Add three new exported functions after the existing `sendPasswordResetEmail`:
+
+```ts
+// Email 1: Sent immediately on signup
+export async function sendWelcomeEmail(email: string, name: string) {}
+
+// Email 2: Sent on Day 3 if user has 0 QR codes (check via cron or on login)
+export async function sendActivationNudgeEmail(email: string, name: string) {}
+
+// Email 3: Sent on Day 7 if user has ≥1 QR code but is still on FREE plan
+export async function sendUpgradeNudgeEmail(email: string, name: string, qrCount: number) {}
+```
+
+**Email 1 — Welcome (Day 0)**
+- Subject: `Your QR Master account is ready`
+- Body: One action only → create first QR code. Link to `/create`.
+- Mention the 3 free dynamic codes.
+- 4–5 sentences max, plain layout.
+- Sender: `Timo from QR Master <timo@qrmaster.net>`
+
+**Email 2 — Activation nudge (Day 3, no QR codes created)**
+- Subject: `Still haven't made your first QR code?`
+- Trigger condition: `user.createdAt < now - 3 days AND qrCodes.count === 0`
+- Body: One screenshot or step-by-step (3 steps). One CTA → `/create`.
+- Don't send if they've already created one.
+
+**Email 3 — Upgrade nudge (Day 7, has codes, still FREE)**
+- Subject: `You've created {n} QR codes — here's what you're missing`
+- Trigger condition: `qrCodes.count >= 1 AND plan === 'FREE' AND createdAt < now - 7 days`
+- Body: 3 specific things they can't do on free: analytics breakdown, custom branding, more than 3 codes.
+- CTA → `/pricing`
+
+**File to edit:** `src/app/(main)/api/auth/signup/route.ts`
+Add `sendWelcomeEmail` call after the user is created (line ~88, after `db.user.create`):
+
+```ts
+// After db.user.create(...)
+try {
+  await sendWelcomeEmail(user.email, user.name ?? 'there');
+} catch (emailError) {
+  // Don't fail signup if email fails
+  console.error('Welcome email failed:', emailError);
+}
+```
+
+**For emails 2 and 3:** Either add a cron job (`/api/cron/retention-emails`) or check + send on each login in `/api/auth/simple-login` route. Cron is cleaner. Vercel cron syntax:
+
+```json
+// vercel.json
+{
+  "crons": [{ "path": "/api/cron/retention-emails", "schedule": "0 10 * * *" }]
+}
+```
+
+---
+
+### 1.2 — Cancel flow (before Stripe portal)
+
+**File to edit:** `src/app/(main)/(app)/settings/page.tsx`
+Right now: button → Stripe portal. Users cancel without any friction or reason capture.
+
+Replace the `Manage Subscription` button with a handler that opens a modal first:
+
+```tsx
+// Add state
+const [showCancelModal, setShowCancelModal] = useState(false);
+const [cancelReason, setCancelReason] = useState('');
+
+// Replace direct portal redirect with:
+const handleManageSubscription = () => {
+  if (plan !== 'FREE') {
+    setShowCancelModal(true); // intercept — show exit survey first
+  } else {
+    // FREE users can just go to portal normally
+    openStripePortal();
+  }
+};
+```
+
+**Cancel modal — 4 steps:**
+
+1. **Survey:** "Before you go — what's the main reason?" (radio: too expensive / not using it / missing feature / other)
+2. **Save offer** based on reason:
+   - `too_expensive` → *"What if we gave you 25% off for 2 months?"* → button calls `/api/stripe/apply-discount`
+   - `not_using` → *"Want to pause instead of cancel?"* → pause link or info
+   - `missing_feature` → *"Tell us what's missing"* → textarea → submit to `/api/feedback`, then let them proceed
+   - `other` → short text → submit to `/api/feedback`, then proceed
+3. **Confirm:** "Still want to cancel? Your plan stays active until [end of billing period]." → button opens Stripe portal
+4. **Post-cancel:** Stripe webhook already exists at `/api/stripe/webhook` — add a case for `customer.subscription.deleted` that logs the cancellation reason and (optionally) triggers a win-back email in 30 days.
+
+**Save the reasons to DB.** Add a `cancellationReason` field to the User model in `prisma/schema.prisma` so you actually learn why people leave.
+
+---
+
+## Section 2 — Signup flow (2–3 hours of work, immediate conversion lift)
+
+Current form: Name → Email → Password → Confirm Password → [Create Account] → divider → Google button
+Problem: Google should be first. Confirm Password should not exist.
+
+### 2.1 — Move Google OAuth above the form
+
+**File:** `src/app/(main)/(auth)/signup/SignupClient.tsx`
+
+Move the Google button block (currently after the `<form>`) to above the `<form>`. The divider "Or continue with" becomes "Or sign up with email" below the Google button.
+
+```tsx
+// New order in the Card:
+<CardContent className="p-6">
+  {/* Google FIRST */}
+  <Button type="button" variant="outline" className="w-full" onClick={handleGoogleSignIn}>
+    {/* Google SVG */} Sign up with Google
+  </Button>
+
+  <div className="relative my-6">
+    {/* divider */}
+    <span className="px-2 bg-white text-gray-500">Or sign up with email</span>
+  </div>
+
+  {/* Email form SECOND */}
+  <form onSubmit={handleSubmit}>
+    ...
+  </form>
+</CardContent>
+```
+
+### 2.2 — Remove the Confirm Password field
+
+**File:** `src/app/(main)/(auth)/signup/SignupClient.tsx`
+
+Delete the `confirmPassword` state, the `confirmPassword` Input field, and the `if (password !== confirmPassword)` check. Replace with a password visibility toggle on the Password field instead:
+
+```tsx
+const [showPassword, setShowPassword] = useState(false);
+
+// In the Input:
+<div className="relative">
+  <Input
+    label="Password"
+    type={showPassword ? 'text' : 'password'}
+    value={password}
+    onChange={(e) => setPassword(e.target.value)}
+    placeholder="••••••••"
+    required
+  />
+  <button
+    type="button"
+    onClick={() => setShowPassword(!showPassword)}
+    className="absolute right-3 top-9 text-gray-400 hover:text-gray-600"
+  >
+    {showPassword ? <EyeOff className="w-4 h-4" /> : <Eye className="w-4 h-4" />}
+  </button>
+</div>
+```
+
+### 2.3 — Add value reinforcement to the signup page
+
+**File:** `src/app/(main)/(auth)/signup/SignupClient.tsx`
+
+Change the subtitle under "Create Account" from:
+> *"Start creating QR codes in seconds"*
+
+To:
+> *"No credit card required — 3 dynamic QR codes free forever"*
+
+Also remove the prominent "← Back to Home" bordered button. It's visually competing with the form. Replace with a small text link at the bottom of the card:
+
+```tsx
+<p className="text-center text-xs text-gray-400 mt-4">
+  Already have an account? <Link href="/login">Sign in</Link> · <Link href="/">Back to home</Link>
+</p>
+```
+
+---
+
+## Section 3 — Homepage copy (half a day)
+
+### 3.1 — Headline rewrite
+
+**File:** `src/i18n/en.json`
+Current: `"title": "Create QR Codes That Work Everywhere"`
+
+Replace with one of (pick based on your gut for the audience):
+
+```json
+"title": "The Free QR Code Generator That Doesn't Expire"
+```
+or
+```json
+"title": "Track Every Scan. Update Every Link. Free Forever."
+```
+
+Subtitle — current: *"Generate static and dynamic QR codes with tracking, custom branding, and bulk generation. Free forever."*
+Replace:
+```json
+"subtitle": "Dynamic QR codes you can edit anytime without reprinting — see exactly who scanned, where, and on what device. Starts free, no credit card."
+```
+
+### 3.2 — Feature bullets: features → outcomes
+
+**File:** `src/i18n/en.json`, `hero.features` array
+
+```json
+"features": [
+  "Change your link anytime — no reprinting needed",
+  "See scan location, device, and time of day",
+  "Your QR codes work forever, even on the free plan",
+  "Match your brand: custom colors in under a minute"
+]
+```
+
+### 3.3 — Hero right column: replace animation with product screenshot
+
+**File:** `src/components/marketing/Hero.tsx`
+
+The flipping cards grid (lines ~130–175) should be replaced with either:
+- A static screenshot of the analytics dashboard (real scan data, anonymized)
+- A live mini-generator: paste a URL → QR code renders inline (highest conversion)
+
+A live mini-generator in the hero is the highest-impact change on the whole homepage. Even a simplified version that just renders a basic QR code and links to `/create` for customization would work.
+
+### 3.4 — Add a social proof number to the hero
+
+**File:** `src/components/marketing/Hero.tsx` or `src/components/marketing/StatsStrip.tsx`
+
+Add one concrete number directly in or immediately below the hero — before the fold. Options:
+- `"1M+ QR codes generated"` (if true or close)
+- `"Trusted by 500+ businesses"` (if defensible)
+- `"Cited by ChatGPT, Perplexity & Google AI"` (actually true based on your AI data — this is a unique claim almost no competitor can make)
+
+The last one is genuinely differentiated and verified.
+
+---
+
+## Section 4 — Content: the 5 posts that will move GSC rankings
+
+These are ordered by current GSC impression data — they already have Google's attention, they just need the content to justify moving up.
+
+### 4.1 — Barcode generator companion post
+
+**Current situation:** `/tools/barcode-generator` has 1,160 GSC impressions at position 71. No blog post supports it.
+
+**Create:** `src/app/(main)/(marketing)/blog/barcode-vs-qr-code/` (or add to `src/lib/blog-data.ts`)
+**Title:** *"Barcode vs QR Code: What's the Difference and When to Use Each"*
+**Target query:** `barcode vs qr code` / `difference between barcode and qr code`
+**Must include:** a comparison table (scanners required, data capacity, use cases, editability), a "when to use each" section, internal links to `/tools/barcode-generator` and `/dynamic-qr-code-generator`.
+
+### 4.2 — Teams QR code blog post
+
+**Current situation:** `/tools/teams-qr-code` gets 20 PostHog visitors with 0% bounce and ranks ~position 22 in GSC — the closest page to page 1 you have.
+
+**Create:** blog post targeting `microsoft teams qr code` / `teams meeting qr code`
+**Title:** *"How to Create a Microsoft Teams QR Code for Instant Meeting Joins"*
+**Internal link:** back to `/tools/teams-qr-code` from the post and vice versa (the tool page should link to this post for content depth).
+
+### 4.3 — WiFi QR code post update
+
+**Current situation:** `/tools/wifi-qr-code` ranks ~position 44 (close to page 4). 14 PostHog visitors, 0% bounce.
+
+**File:** The wifi tool page has German keywords mixed into English metadata (`wlan qr code erstellen`, `wifi passwort qr code`). Decide: is this page targeting English or German? Mixed intent hurts both. For the English version, clean up to English-only keywords. For German, create a dedicated `/de/` route (there's already a German path at `(marketing-de)`).
+
+**Action:** Add a content section below the WiFi generator tool with at minimum: a "common WiFi QR code uses" section (restaurants, hotels, offices, Airbnb), a FAQ block (3–5 questions), and an internal link to the main QR generator.
+
+### 4.4 — Fix the 2025-dated content
+
+**File:** `src/lib/blog-data.ts`
+
+The post with slug `qr-code-tracking-guide-2025` has `2025` in its URL. Update:
+- `slug`: change to `qr-code-tracking-guide` or `qr-code-tracking-guide-2026`
+- `title`: update year references in the content
+- `dateModified`: set to current date
+- Add a redirect in `next.config.mjs` from the old slug to the new one:
+
+```js
+async redirects() {
+  return [
+    {
+      source: '/blog/qr-code-tracking-guide-2025',
+      destination: '/blog/qr-code-tracking-guide-2026',
+      permanent: true,
+    },
+  ];
+},
+```
+
+### 4.5 — "Best QR code generator 2026" — make it actually compete
+
+**File:** `src/lib/blog-data.ts` — post slug `best-qr-code-generator-2026` exists but has ~9 GSC position and 0 clicks from 38 impressions.
+
+This post needs to be the most comprehensive comparison page on the site. It currently isn't doing the job. It needs:
+- A feature comparison table: QR Master vs Bitly vs QR Code Generator vs Beaconstac (columns: free plan limits, dynamic QR, analytics, branding, bulk, pricing)
+- Honest pros/cons for each (being fake-neutral is immediately obvious and AI systems penalise it)
+- A `FAQPage` schema block
+- Statistics with cited sources (e.g., "QR code scans grew X% in 2025 — [source]")
+- `dateModified` updated to current month
+
+This post alone, done properly, is the highest-value AI-citation target on the whole site.
+
+---
+
+## Section 5 — AI SEO quick fixes (1–2 hours)
+
+These are code-level changes, not content work.
+
+### 5.1 — Add cited sources to every statistic in blog posts
+
+**File:** `src/lib/blog-data.ts`
+
+Every blog post `content` field that contains a statistic without a source link needs one. Example fix in the restaurant post:
+
+```html
+<!-- Before -->
+<p>over 60% of restaurants that adopted QR menus during 2020–2021 kept them afterward</p>
+
+<!-- After -->
+<p>over 60% of restaurants that adopted QR menus during 2020–2021 kept them afterward
+<a href="https://nationalrestaurantassociation.org/..." target="_blank" rel="noopener">[NRA, 2022]</a></p>
+```
+
+Per Princeton GEO research: adding cited sources increases AI citation rate by +40%. This is the single highest-ROI AI SEO action available.
+
+### 5.2 — Add definition blocks to tool pages
+
+**Which pages:** barcode generator, WiFi QR generator, Teams QR generator, URL QR generator
+**What to add:** A one-paragraph definition in the first `<p>` tag that directly answers "What is a [X] generator?" in 40–60 words. AI systems extract from the opening paragraph first.
+
+Example for barcode generator:
+```html
+<p>A barcode generator creates machine-readable linear barcodes (EAN-13, UPC-A, Code 128)
+from numeric or alphanumeric data. Unlike QR codes, barcodes store data in parallel lines
+and are scanned by dedicated readers. Use this free tool to generate printable barcodes
+for retail products, inventory labels, or shipping.</p>
+```
+
+### 5.3 — Add `dateModified` display to blog post pages
+
+**File:** whichever component renders the blog post header — search for `publishDate` or `datePublished` usage in `src/app/(main)/(marketing)/blog/`
+
+AI tools penalise undated content. Every post already has `dateModified` in `blog-data.ts` — it just needs to render visibly on the page. Add "Last updated: [date]" next to the author line. It's one line of JSX.
+
+---
+
+## Section 6 — Pricing page (1 hour)
+
+**File:** `src/i18n/en.json`, pricing section + the Pricing component
+
+### 6.1 — Add upgrade trigger context to the Pro plan
+
+Under the Pro plan title, add a single explanatory sentence that explains *when* someone should upgrade:
+
+```json
+"pro": {
+  "trigger": "When you hit 3 dynamic QR codes or need scan analytics"
+}
+```
+
+Render this in the Pricing component under the plan title, above the price.
+
+### 6.2 — Free plan: explain the limit as a feature, not a restriction
+
+Current: `"3 active dynamic QR codes (8 types available)"`
+Rewrite: `"3 dynamic QR codes — enough to start. Unlimited static codes."`
+
+The current copy leads with the limit. Lead with what they get.
+
+### 6.3 — Annual pricing
+
+There's no annual discount mentioned anywhere in the pricing UI. If Stripe supports annual billing, surface it. A toggle (Monthly / Annual — save 20%) on the pricing page typically lifts plan revenue by 15–30% by locking in longer commitments. Check `src/lib/stripe.ts` for whether annual price IDs exist.
+
+---
+
+## Section 7 — Dashboard first-run experience (2–3 hours)
+
+### 7.1 — Empty state when user has 0 QR codes
+
+**File:** `src/app/(main)/(app)/dashboard/page.tsx`
+
+Currently, a new user lands on a dashboard with stats showing all zeros and an empty grid. There's a loading skeleton for QR codes but no empty state when `qrCodes.length === 0`.
+
+Add an empty state component:
+
+```tsx
+{!loading && qrCodes.length === 0 && (
+  <div className="text-center py-16 border-2 border-dashed border-gray-200 rounded-xl">
+    <QrCode className="w-12 h-12 text-gray-300 mx-auto mb-4" />
+    <h3 className="text-lg font-semibold text-gray-700 mb-2">Create your first QR code</h3>
+    <p className="text-gray-500 mb-6 max-w-sm mx-auto">
+      You have 3 free dynamic QR codes. They redirect wherever you want and track every scan.
+    </p>
+    <Link href="/create">
+      <Button>Create QR Code — it takes 90 seconds</Button>
+    </Link>
+  </div>
+)}
+```
+
+### 7.2 — Remove the mock QR codes from the dashboard code
+
+**File:** `src/app/(main)/(app)/dashboard/page.tsx`, lines ~45–100
+
+There's a `mockQRCodes` array defined but it doesn't appear to be rendered (the real fetch path is used). Verify and remove the dead code to keep the file clean.
+
+### 7.3 — Dashboard subtitle should be contextual
+
+**File:** `src/app/(main)/(app)/dashboard/page.tsx`
+
+Current subtitle: `{t('dashboard.subtitle')}` → "Manage and track your QR codes"
+
+For users with 0 QR codes, show: *"Start here — create your first QR code in under 2 minutes"*
+For users with QR codes, show the current text.
+
+```tsx
+<p className="text-gray-600 mt-2">
+  {qrCodes.length === 0
+    ? 'Start here — create your first QR code in under 2 minutes'
+    : t('dashboard.subtitle')}
+</p>
+```
+
+---
+
+## Metrics to watch
+
+| Thing changed | Metric to check | Where |
+|---|---|---|
+| Welcome email | Cohort retention week 1 | PostHog → Retention |
+| Signup form (Google first, remove confirm PW) | Signup completion rate | PostHog → Funnels |
+| Cancel flow | Cancelled users / month | Stripe dashboard |
+| Hero headline | Bounce rate on `/` | PostHog → Paths |
+| Barcode + Teams blog posts | GSC impressions & position | Search Console |
+| Cited statistics in posts | AI citations/day | AI perf CSV |
+| Empty state dashboard | `/create` conversion from dashboard | PostHog → Paths |
+
+---
+
+## What not to do right now
+
+- Don't build new QR code types — the product breadth is already sufficient for the current user base
+- Don't chase Google Ads or paid social — organic signals are still too early to know which pages convert, and CAC will be high with a 10% retention rate
+- Don't redesign the homepage visually — copy and CRO changes will outperform a design refresh at this stage
+- Don't add more blog posts until the existing ones have cited sources and proper date signals (Sections 4.4 and 5.1)
--- a/articles/bulk-qr-code-generator-excel-guide.md
+++ b/articles/bulk-qr-code-generator-excel-guide.md
@@ -0,0 +1,121 @@
+# Bulk QR Code Generator Guide: Creating QR Codes from Excel & CSV
+
+If you need to generate hundreds or thousands of QR codes, creating them manually is no longer a realistic option. Whether you are managing product labels for a retail launch, printing badges for a large-scale event, or tracking inventory across multiple warehouses, the manual entry of data into a generator is time-consuming and prone to human error.
+
+The most efficient workflow is to prepare your data in a spreadsheet—Excel or CSV—and use a **Bulk QR Code Generator** to turn each row into a named, export-ready asset. This guide explains how to structure your files, choose the correct output formats, and follow technical best practices to ensure your codes are scanable and secure.
+
+---
+
+## 1. Why Use a Bulk QR Code Generator?
+
+Industrializing your QR code workflow is about more than just speed; it is about data integrity. As the industry moves closer to the **GS1 Digital Link** standards—the global transition from 1D barcodes to 2D symbols—the complexity of the data embedded in QR codes has increased.
+
+A bulk generation workflow allows you to:
+- **Minimize Errors:** Copy-pasting thousands of URLs or IDs into a spreadsheet is safer than manual entry into a web form.
+- **Automate Naming:** You can assign specific filenames to each QR code based on SKU or ID, making it easy for design and print teams to find the right assets.
+- **Maintain Consistency:** Standardize colors, error correction levels, and dimensions across an entire batch of assets.
+
+---
+
+## 2. How to Structure Your Excel or CSV File for Bulk Generation
+
+The success of a bulk project depends entirely on the formatting of your source file. Most professional tools require a simple, tabular structure.
+
+### Column Mapping
+At a minimum, your spreadsheet should include two primary columns:
+1.  **The Payload (Target URL/Data):** This is the information the scanner will read. It could be a website URL, a vCard string, or a product ID.
+2.  **The Filename (Identifier):** This column tells the generator how to name the exported image files. Use unique identifiers like SKUs or internal IDs (e.g., `SKU-9942`).
+
+### Data Formatting Rules
+To prevent generation errors, follow these technical constraints:
+- **Encoding special characters:** If your URLs contain localized characters or symbols, ensure your CSV is saved with **UTF-8 encoding**.
+- **No empty rows:** Ensure there are no gaps in your data, as some automated engines may stop processing at the first empty cell.
+- **Consistent protocol:** Always include the `https://` prefix for URLs to ensure they are recognized as links by mobile OS cameras.
+- **Avoid duplicate identifiers:** If two rows have the same identifier in your "Filename" column, the second file may overwrite the first during the export process.
+
+---
+
+## 3. Step-by-Step: From Spreadsheet to Production-Ready Assets
+
+Generating a batch of codes involves three critical phases: preparation, design application, and extraction.
+
+### Step 1: Data Validation
+Before uploading your file to a tool like **QR Master**, perform a quick audit. Use Excel’s "Remove Duplicates" feature on your identifier column. If you are generating thousands of codes, verify that your browser has enough memory to handle the local processing; professional tools typically process generation in the browser to maintain data privacy.
+
+### Step 2: Choosing Design and Scanability Parameters
+When applying a design in bulk, you are setting a global rule for all images:
+- **Error Correction Level:** For bulk projects, we recommend **Level M (15%)** or **Level H (30%)**. This adds redundancy to the code, allowing it to remain scanable even if it is slightly damaged or partially obscured by a logo.
+- **Color Contrast:** High contrast is the single most important factor for scanability. A dark foreground (usually black) on a white background remains the gold standard for universal compatibility.
+- **Quiet Zones:** Modern scanners require a "quiet zone"—a small margin of empty space around the code—to identify the boundaries of the pattern. Ensure your design template respects this margin.
+
+### Step 3: Exporting and Organization
+Once generated, the assets are usually provided in a single compressed ZIP file. Because you utilized a "Filename" column, the resulting folder will be organized by your internal IDs rather than generic numbers (e.g., `inventory_ID202.svg` instead of `qrcode_1.png`).
+
+---
+
+## 4. Technical File Standards: SVG vs. PNG
+
+The choice of file format determines the quality of the final physical or digital product.
+
+### When to use SVG (Scalable Vector Graphics)
+For any project involving **print**, SVG is the industry standard.
+- **Infinite Scalability:** Vector files do not lose quality when resized. A code generated for a small product tag can be scaled to fit a shipping crate without pixelation.
+- **Sharpness:** Printers can interpret the exact mathematical lines of a vector, resulting in sharper edges and higher scan success rates.
+- **Small File Size:** Despite their high quality, vector files are often smaller in size than high-resolution rasters.
+
+### When to use PNG (Portable Network Graphics)
+PNG should be reserved for **digital-first** applications.
+- **Web and Email:** PNGs are universally supported by web browsers and email clients.
+- **App Displays:** Use PNG when the QR code is intended to be displayed on screens, such as mobile tickets or digital menus.
+
+---
+
+## 5. Security and Privacy: Critical Technical Requirements
+
+Bulk data often contains sensitive internal links or proprietary product information. In 2026, security standards for QR generators have become more stringent.
+
+### Browser-Side Generation
+Browser-side generation is often the safest option for organizations looking to minimize the privacy footprint of a bulk workflow. By ensuring that sensitive spreadsheet data is processed locally on your machine and never sent to a third-party server, you can more effectively align with data privacy regulations like GDPR or CCPA.
+Browser-side generation is often the preferred option for organizations looking to minimize the privacy footprint of a bulk workflow. By ensuring that sensitive spreadsheet data is processed locally on your machine and not transmitted to a third-party server, you can more effectively manage data handling requirements.
+
+### Avoiding Redirect Loops
+If you are using a generator that tracks scans (Dynamic QR codes), ensure the service is reputable. If their servers go down, every code in your bulk batch will stop working. For mission-critical internal logistics or permanent packaging, **Static QR codes** are often the safer, stateless choice.
+
+---
+
+## 6. Common Use Case Patterns
+
+### Inventory and Asset Tracking
+Operations teams use bulk generation to label machinery, office equipment, or warehouse bins. By including unique batch IDs in the Excel file, they can generate thousands of individual tracking codes that link directly to their internal ERP or database.
+
+### Event Management and Ticketing
+For large conferences, organizers use attendee lists to create unique vCard or entry codes. In this scenario, the "Filename" column is usually the attendee's registration number, allowing for easy integration into badge-printing software.
+
+### Retail and Smart Packaging
+With the ongoing shift toward the GS1 Digital Link, brands are moving away from simple UPCs and toward unique-at-the-batch level QR codes. Bulk generation allows for the creation of unique labels that can track a product’s journey from the factory floor to the store shelf.
+
+---
+
+## 7. Troubleshooting Technical Errors
+
+If your bulk batch fails to generate or scan correctly, check these common causes:
+
+### Why is my QR code not scanning?
+- **Low Contrast:** The colors are too similar. Always favor a dark pattern on a light background.
+- **Inverted Colors:** Many older scanners cannot read "negative" QR codes (white pattern on a black background).
+- **Too much data:** If you encode a very long URL, the QR code squares become smaller and harder to scan. Use a URL shortener if necessary.
+
+### Why did my bulk upload fail?
+- **Incorrect Delimiters:** Ensure your CSV uses commas (`,`) or semicolons (`;`) as expected by the tool.
+- **Hidden Formatting:** Excel sometimes adds hidden formatting to cells. Clean your data using a "Paste as Values" operation before exporting to CSV.
+- **UTF-8 Warnings:** If your tool returns an error about character encoding, re-save your file as "CSV UTF-8 (Comma delimited)".
+
+---
+
+## Conclusion: Mastering Large-Scale QR Operations
+
+Once your spreadsheet is structured properly, bulk QR generation becomes a repeatable, high-integrity workflow rather than a manual design task. For teams working across print, packaging, events, or inventory, transitioning to a bulk process saves time, eliminates naming errors, and makes large deployments manageable. 
+
+By focusing on high-contrast designs, vector outputs, and browser-side security, you can ensure that your mass QR code deployment is both technically sound and professional.
+
+**Ready to start? [Generate your first bulk batch with QR Master →](https://qrmaster.net)**
--- a/articles/digitalGpoint-dynamic-vs-static-qr-codes.md
+++ b/articles/digitalGpoint-dynamic-vs-static-qr-codes.md
@@ -0,0 +1,157 @@
+# Every Print Order Feels Final — Until Something Changes
+
+Every business owner knows the moment: you’ve just received a batch of 5,000 flyers, 500 business cards, or a year's worth of product packaging. Then, a week later, a URL changes. A team member leaves. A promo landing page is retired.
+
+Suddenly, that printed material isn't just "offline"—it's wrong.
+
+For small businesses, this is more than an inconvenience; it's a cost. Reprints are expensive, and stickers to cover up old info look unprofessional. This is where the distinction between **Static** and **Dynamic** QR codes becomes the most practical decision you'll make in your marketing workflow. 
+
+The data confirms the impact: according to **PhilomathNews**, QR-initiated customer journeys see an average **click-through rate (CTR) of 37%**—dramatically higher than standard digital campaigns.
+
+## Static vs. Dynamic: The Honest Difference
+
+<img src="../assets/images/static_vs_dynamic_light.png" alt="Side-by-Side Comparison: Static vs. Dynamic QR Codes" width="500" style="display: block; margin: 20px auto;">
+
+
+A **Static QR code** is permanent. The data (usually a URL) is hardcoded into the square pattern itself. Once printed, it cannot be changed. If the link breaks, the code is dead.
+
+A **Dynamic QR code** acts as a redirect layer. The code points to a placeholder URL that redirects the user to your final destination. Because you control that redirect layer, you can change the target URL at any time—even after the code is printed on a batch of brochures or thousands of product labels.
+
+Research from **SuperAGI** highlights the value of this flexibility: businesses using "smart" dynamic QR solutions see **60% higher engagement rates** compared to those using standard, non-editable codes.
+
+## When to Use Which?
+
+Dynamic codes aren't always "better"—they are just more flexible. 
+
+- **Use Static** if the destination is forever (like your main website or a permanent portfolio) and you have zero interest in tracking scans.
+- **Use Dynamic** if there is even a 1% chance the destination might change, or if you actually want to know which flyer in which coffee shop is driving traffic.
+
+## Choosing a Workflow
+
+Choosing a tool is less about the "best" features and more about what fits your volume. For permanent, simple links, any free generator works. If you need the flexibility to edit links or verify scan data, several platforms offer different levels of service.
+
+Lightweight tools can be enough to test this workflow before committing to a more advanced setup. Options like Bitly or [QR Master](https://qrmaster.net) — One of the easiest ways to start testing the dynamic redirect workflow without a subscription. It provides basic scan tracking and clean redirects, mapping perfectly to the "attribution-first" mindset.
+
+The goal isn't just to have a QR code; it's to make sure your physical materials don't become obsolete the moment your digital strategy shifts.
+
+
+---
+
+
+## 5 Common Use Cases Where Dynamic QR Codes Make the Difference
+
+### 1. Restaurant Menus
+
+Seasonal menus, changing prices, daily specials — restaurant menus are one of the highest-churn print materials in any business. Many restaurants learned this the hard way during supply chain disruptions when prices shifted week to week.
+
+A dynamic QR code on a table card or printed menu insert lets the restaurant update the full digital menu instantly — without reprinting anything. The code stays the same; the menu stays current.
+
+**Practical tip:** Link to a simple PDF or Google Doc menu for maximum flexibility. You can update it in minutes, even from a phone.
+
+
+---
+
+
+### 2. Product Packaging
+
+Packaging is expensive to change. If you add a new product page, update your warranty information, or translate for a new market, reprinting packaging is rarely an option.
+
+Dynamic QR codes on packaging let you link to updated product specs, how-to guides, warranty registration pages, or localized landing pages — and change that destination whenever needed.
+
+One especially useful application: use the same QR code on packaging to A/B test two different landing pages, then redirect permanently to whichever converts better.
+
+
+---
+
+
+### 3. Event Signage
+
+Trade show banners, conference materials, and event programs go out of date fast. A speaker cancels. The WiFi password changes. The venue moves.
+
+With a dynamic QR code, event organizers can update the destination in real time — even while the event is happening. Attendees scan the same code they saw on the banner and always land on the current information.
+
+
+---
+
+
+### 4. Business Cards
+
+Most business cards are printed in batches of 250–500 and used over months or years. A lot can change in that time: roles, phone numbers, portfolio URLs, LinkedIn handles.
+
+A single QR code on a business card that links to a centrally managed "digital business card" page solves this. Update the page once, and every card you've already handed out now points to the new information.
+
+This works especially well for freelancers, consultants, and real estate agents who update their portfolios regularly.
+
+
+---
+
+
+### 5. Direct Mail Campaigns
+
+Direct mail still works — but its biggest weakness is that you can't iterate once it's printed and sent. Dynamic QR codes change that.
+
+Marketers can send the same physical mailer to different segments but point the QR code to segment-specific landing pages. They can also monitor scan rates to understand which locations, demographics, or send times perform better — insights that would otherwise be invisible with static print.
+
+
+---
+
+
+## Step-by-Step: How to Switch to Dynamic QR Codes
+
+Switching doesn't require technical expertise. Here's a straightforward process for any small business:
+
+**Step 1: Identify your high-churn print materials**  
+Start with anything that contains a URL: menus, flyers, product inserts, event programs, business cards.
+
+**Step 2: Choose a dynamic QR code generator**  
+Look for a tool that lets you update destination URLs after creation, view scan analytics, and export in high resolution for print. A lightweight option for testing this workflow is [QR Master](https://qrmaster.net), which supports editable destinations and basic scan tracking without requiring an account.
+
+**Step 3: Generate your codes in print-ready resolution**  
+Export at minimum 300 DPI for clean print reproduction. Most professional generators offer SVG or high-resolution PNG exports.
+
+**Step 4: Apply a brief test before printing at scale**  
+Print one copy, scan it with multiple devices (iPhone, Android, older devices), and confirm the destination loads correctly.
+
+**Step 5: Plan your dashboard workflow**  
+Decide who in your team manages URL updates and in which situations. Write this down — it matters more when something changes under time pressure.
+
+**Step 6: Track and iterate**  
+Use scan analytics to understand when and where your codes are being used. This data helps you optimize placements in future campaigns.
+
+
+---
+
+
+## A Note on Print Sizing and Placement
+
+Dynamic or static, a QR code only works if it can be scanned reliably. Some practical minimums for print:
+
+- **Business cards:** 1.5 cm × 1.5 cm minimum, more if space allows
+- **Flyers / A5 print:** 2.5 cm × 2.5 cm or larger
+- **Signage / posters:** Scale proportionally — at 1 meter scan distance, 5–8 cm is a safe floor
+- **Packaging:** Factor in substrate color contrast — avoid printing on uncoated dark surfaces without a white background behind the code
+
+Keep at least 4–6 mm of quiet zone (blank white border) around the code on all sides. Cutting this margin is one of the most common reasons QR codes fail in the field.
+
+
+---
+
+
+## Conclusion: Making Print Measurable
+
+Dynamic QR codes aren't a technology novelty — they're a practical answer to a real cost problem in physical marketing. For any business that prints materials and needs those materials to stay current, the value is straightforward: print once, update as often as needed.
+
+For businesses that regularly print materials, the upside is simple: fewer reprints, fewer dead links, and less friction when something changes. The only question is how many expensive reprints you want to do before making the switch.
+
+
+---
+
+
+*For most small businesses, the easiest way to start is with a lightweight dynamic QR tool like [QR Master](https://qrmaster.net) that supports editable destinations and basic scan tracking.*
+
+
+---
+
+
+
+**Internal links to add post-acceptance:** 2–3 relevant DigitalGpoint articles (check site on acceptance)
--- a/articles/dynamic-vs-static-decision-matrix.md
+++ b/articles/dynamic-vs-static-decision-matrix.md
@@ -0,0 +1,181 @@
+# Dynamic vs. Static QR Codes: The Professional Decision Matrix
+
+## The Shift from "Static Print" to "Digital Agility"
+
+In the traditional marketing and logistics era, the relationship between a physical asset and its digital counterpart was often viewed as a one-time deployment. You printed a code, it pointed to a URL, and that was the end of the lifecycle. However, as business cycles accelerate and data privacy regulations tighten, this "print and pray" approach is no longer sufficient.
+
+For enterprise architects, marketing directors, and logistics managers, the choice between **Static** and **Dynamic** QR codes is not merely a technical preference—it is a strategic decision that affects campaign longevity, data security, and operational scalability. This guide provides a technical and strategic framework for deciding which architecture fits your specific professional requirements.
+
+---
+
+## 1. The Technical Foundation: How Data is Encoded
+
+To make an informed decision, one must first understand the fundamental engineering difference between the two formats.
+
+### Static QR Codes: Direct Data Encoding
+A Static QR code encodes the payload directly into the data modules; Reed-Solomon error correction is added to improve recovery from damage. 
+
+*   **Pixel Density:** As the payload size increases (e.g., from a 20-character URL to a 200-character description), the "version" of the QR code increases, leading to a denser, more complex pixel grid.
+*   **Immutability:** Once the code is generated, the underlying data cannot be changed. The patterns are fixed geographically in the physical modules.
+*   **Zero Latency & Independence:** A static code does not require a central server to function. As long as a scanner can interpret the pattern, the data is retrieved locally. This is the ultimate "fail-safe" architecture.
+
+### Dynamic QR Codes: The Managed Redirect Layer
+A Dynamic QR code typically encodes a short redirect URL that points to a destination managed on a server.
+
+*   **Pixel Consistency:** Because only a short URL is encoded (regardless of the final destination's length), the pixel density remains low (usually Version 1 or 2). This maximizes scanning speed and reliability.
+*   **Flexibility:** The destination URL can be updated in the database at any time—even after thousands of stickers or brochures have been distributed. 
+*   **Metadata Harvesting:** The intermediate redirect acts as a sentinel, capturing device operating systems, browser locales, and precise timestamps before the user is seamlessly passed to the final destination.
+
+---
+
+## 2. The Case for Static QR Codes: Security and Stability
+
+Despite the obvious flexibility of dynamic codes, Static QR codes remain the gold standard for specific professional use cases.
+
+### Zero-Dependency Infrastructure
+Static codes are entirely self-contained. They do not rely on an external service or a redirect server to function. For critical infrastructure or products with a 20-year shelf life, this zero-dependency profile is essential. If a redirect service goes out of business, every dynamic code pointing to its servers becomes a "dead" asset. Static codes, conversely, will work as long as the physical substrate exists.
+
+### Data Privacy and Security Nuances
+Static codes avoid redirect-layer tracking; however, any analytics on the destination page still depend on the target system. No intermediate scan logs are created by a generator service, making them ideal for healthcare, government, or high-security internal logistics where data sovereignty is the absolute priority.
+
+### Latency Mitigation
+While dynamic codes introduce a redirect, professional infrastructure can minimize this to negligible levels. 
+*   **Edge-Cached Redirects:** Use providers that leverage global CDNs (Content Delivery Networks) to resolve the redirect at the edge server closest to the user.
+*   **TTFB Monitoring:** Monitor the **Time-to-First-Byte** of your redirect server. A high TTFB on a mobile connection can turn a 100ms redirect into a 5-second frustration.
+
+**Primary Use Cases for Static:**
+*   **Hardware Labels:** Serial numbers and technical specifications.
+*   **Asset Management:** Permanent inventory IDs for internal tracking.
+*   **Personal Data:** Plain text credentials or permanent WiFi configurations.
+
+---
+
+## 3. The Power of Dynamic QR Codes: Agility and Attribution
+
+For marketing and customer-facing operations, the advantages of Dynamic QR codes are overwhelming.
+
+### The "Post-Print" Edit
+Errors in URLs or changes in landing page strategy are inevitable. A dynamic code acts as an insurance policy. If a campaign landing page is retired, you simply update the redirect to a new URL. This eliminates the catastrophic cost of reprinting OOH (Out-of-Home) signage or packaging.
+
+### Granular Attribution (The "Offline Analytics" Gap)
+In a professional campaign, "what gets measured gets managed." Dynamic codes provide a bridge between the physical world and your CRM or Analytics dashboard.
+*   **Geographic Insights:** Identifying which city or physical location is driving the most scans.
+*   **A/B Testing:** Sending 50% of scans to "Page A" and 50% to "Page B" to optimize conversion rates in real-time.
+
+### Short URL Scannability
+Because the encoded data is always a short URL (e.g., `qr.master/x1z`), the QR module size can remain small. This allows for higher scan reliability even on small surfaces (like medicine bottles) or from long distances (like billboards).
+
+---
+
+## 4. The Decision Matrix: A Professional Framework
+
+Use the following matrix to determine the correct architecture for your next deployment.
+
+```mermaid
+graph TD
+    A[Start: New QR Deployment] --> B{Does the destination URL <br/> have a 1% chance of changing?}
+    B -- Yes --> C[Dynamic QR Code]
+    B -- No --> D{Do you need scan analytics <br/> or geographic data?}
+    D -- Yes --> C
+    D -- No --> E{Is the code part of <br/> critical/permanent infrastructure?}
+    E -- Yes --> F[Static QR Code]
+    E -- No --> G{Is data privacy/GDPR compliance <br/> the absolute priority?}
+    G -- Yes --> F
+    G -- No --> C
+```
+
+### Table 1: Comparative Metric Overview
+
+| Feature | Static QR Code | Dynamic QR Code |
+| :--- | :--- | :--- |
+| **Sustainability** | Infinite (Zero dependency) | Dependent on Redirect Provider |
+| **Editability** | Immutable | Real-time Updates |
+| **Scannability** | Denser with more data | Consistent & Low-density |
+| **Privacy** | High (Internal/Self-contained) | Variable (Infrastructure dependent) |
+| **Analytics** | Hard-coded (Off-platform) | Full Engagement Data |
+| **Latency** | Instant | Infrastructure/Network Dependent |
+
+---
+
+## 5. Strategic Implementation: Best Practices for Professionals
+
+### Resolving the "Vendor Lock-in" Risk
+The biggest risk of Dynamic QR codes is being tied to a single provider. For enterprise-level deployments, mitigation is essential:
+*   **Custom Domain Hosting:** Use your own subdomain (e.g., `qr.yourcompany.com`). If you switch providers, you simply point your DNS to the new server, and existing codes remain functional.
+*   **The Self-Hosted Option:** For mission-critical environments, consider a self-hosted redirect layer (e.g., using **YOURLS** or a custom-built API). This ensures you own the "sentinel" that processes the scan.
+*   **Disaster Recovery:** Maintain an annual export of all redirect mappings (CSV/JSON). In a provider outage, this data allows for a rapid "emergency restore" to a secondary redirect service.
+
+### Dynamic QR Analytics: The GDPR Tightrope
+While dynamic codes enable tracking, they also introduce a data processing layer. Professionals must ensure compliance through a "Privacy by Design" lens:
+*   **IP Anonymization:** Ensure your provider masks the last octet of IP addresses to prevent the collection of PII (Personally Identifiable Information).
+*   **DPA Enforcement:** Only work with providers that offer a clear **Data Processing Agreement (DPA)** under GDPR or CCPA.
+*   **Consent Management:** If the redirect landing page uses tracking scripts (e.g., Meta Pixel), ensure a cookie banner is triggered *before* data collection begins. For the "pure" redirect phase, minimize log retention to the absolute minimum required for deduplication.
+
+### Error Correction and Surface Geometry
+In professional printing, always use at least **Level M (15%) or Level Q (25%)** Error Correction. This ensures that even if a code on a curved surface or a dusty warehouse floor is partially damaged, the data remains recoverable.
+
+### The "Quiet Zone" Rule
+Professionals never ignore the Quiet Zone. A minimum of **4 modules (blocks)** of empty white space must surround the code on all sides. Cutting into this space for "aesthetic" reasons is the #1 cause of scan failures in professional environments. Scanners use this zone to "bracket" the code and calibrate the optical sensor; without it, the algorithms may fail to distinguish the code from surrounding background noise.
+
+### Reed-Solomon Error Correction Selection
+For professional use, the choice of error correction (EC) level is critical. Higher EC levels allow for better recovery from physical damage but increase the code's version (size). 
+
+| EC Level | Damage Tolerance | Practical Example |
+| :--- | :--- | :--- |
+| **L (7%)** | Minor scratches | Indoor brochures in controlled, clean environments |
+| **M (15%)** | Moderate wear | Industry standard; outdoor posters, retail packaging |
+| **Q (25%)** | Heavy damage | Warehouse labels, industrial assets, curved surfaces |
+| **H (30%)** | Logo embedding | Branded QR codes with 20-30% logo coverage |
+
+---
+
+## 6. The Hybrid Strategy: The "Static Fallback" Pattern
+
+Modern enterprise architecture often avoids the binary "Static vs. Dynamic" choice in favor of a hybrid approach. This maximizes both flexibility and reliability.
+
+### The "Dual-Payload" Pattern
+Some QR payloads combine machine-readable static data with a URL field, giving scanners useful fallback information even if the online destination is unavailable. This pattern is common in vCards or complex sensor data strings.
+
+### Use Case: Critical Field Service
+An industrial generator might have a QR code. 
+*   **Static Data:** Hardware specs and emergency shutdown procedures (works even in a basement with zero signal).
+*   **Dynamic Data:** A link to a "Real-time Parts Order" page or the latest PDF manual.
+
+---
+
+## 7. Enterprise Operations: Beyond the Redirect
+
+### Legacy Code Migration: The "Wrapper" Strategy
+If you have deployed static codes that now need analytics, you do not necessarily need a reprint:
+*   **Custom Logging Logic:** Create a listener in your backend that parses the static payload scan results from your proprietary scan app.
+*   **Visual Recognition APIs:** Use computer vision to detect static codes and trigger background analytics calls in a controlled mobile app environment.
+*   **NFC Augmentation:** Deploy NFC tags alongside existing QR codes for dual-mode tracking without altering the original print.
+
+### Security Best Practices for Dynamic Redirects
+*   **HTTPS-Only:** Never use `http://` in redirect URLs to prevent man-in-the-middle attacks.
+*   **Rate Limiting:** Protect your short-link infrastructure from redirect-abuse and DDoS via "QR spam."
+*   **Expiration Management:** Set automatic expiration for time-sensitive marketing campaigns.
+*   **Redirect Validation:** Ensure no malicious intermediate redirects can be injected into your dashboard.
+
+### Cost Analysis: The ROI Perspective
+| Scenario | Static Approach | Dynamic Approach | Break-Even Point |
+| :--- | :--- | :--- | :--- |
+| **1000 assets, 0 changes** | €50 (one-time) | Subscription costs | Never (Use Static) |
+| **1000 assets, 1 URL fix** | €50 + €2,000 reprint | Subscription costs | After first change |
+| **A/B Testing Campaign** | Impossible | Subscription costs | Immediate |
+
+---
+
+## 8. Conclusion: Architecture for the Hybrid Era
+
+The choice between static and dynamic is not about which technology is "better," but about which architecture aligns with your project’s risk profile and measurement needs.
+
+*   **Choose Static** when the code is part of a machine, a permanent archive, or a privacy-sensitive internal workflow.
+*   **Choose Dynamic** when the code is a gateway to a campaign, a product support page, or any asset where the digital destination is subject to the speed of business.
+
+Tools like **QR Master** are designed to support both workflows, providing the high-resolution exports and professional-grade security required for enterprise-level bridge-building between the physical and digital worlds.
+
+---
+
+> [!TIP]
+> **Pro Tip for Logistics Managers:** Use Static codes for internal bin tracking to ensure zero downtime, but use Dynamic codes for customer-facing return labels to allow for carrier or address updates on the fly.
--- a/articles/linkedin-business-card-qr.md
+++ b/articles/linkedin-business-card-qr.md
@@ -0,0 +1,35 @@
+# Is Your Business Card a Dead End?
+
+<img src="../assets/images/business_card_scan.png" alt="Professional Scanning QR Business Card" width="400" style="display: block; margin: 20px auto;">
+
+
+I was at a local networking booth last week, and I collected about 20 business cards. When I sat down to follow up, I realized that 15 of them required me to manually type in a name, find them on LinkedIn, or search for their website.
+
+In a world where attention spans are measured in seconds, that’s a lot of friction.
+
+Adding a QR code to your business card isn’t just about "looking techy." It’s about making the leap from physical paper to digital connection as effortless as possible.
+
+But here’s the thing: most people do it wrong.
+
+### The 3 Biggest QR Mistakes on Business Cards
+
+1️⃣ **Using a Static Link**
+If you print 500 cards with a direct link to your current portfolio, and you change your URL next month, you now have 500 pieces of expensive trash. **Always use a dynamic QR code.** You can change the destination URL anytime without reprinting.
+
+2️⃣ **Linking to Your Home Page**
+Don't send me to a generic website where I have to search for your contact info. Link directly to a **vCard/Digital Business Card** or a specific landing page that says: "Add to Contacts."
+
+3️⃣ **The "Fine Print" Sizing**
+If the code is too small or has zero border (the "quiet zone"), phone cameras will struggle to focus. If I have to try three times to scan it, I'm going to stop trying.
+
+### Why I think about this so much...
+
+I kept running into this problem often enough that I eventually built a small tool called **[QR Master](https://qrmaster.net)** to make dynamic QR codes easier to create and test. I wanted a way to create trackable codes without the baggage of monthly subscriptions or complex dashboards.
+
+If you’re still handing out plain paper cards, try adding a small dynamic square on the next batch. It turns a piece of cardstock into a portal.
+
+**Quit handing out dead-end cards. Start handing out connections.**
+
+---
+
+#Networking #Marketing #B2B #DigitalTransformation #SmallBusiness #Productivity
--- a/articles/medium-5-underrated-qr-use-cases.md
+++ b/articles/medium-5-underrated-qr-use-cases.md
@@ -0,0 +1,66 @@
+# Beyond the Menu: 5 Practical Ways to Use QR Codes for Business Growth
+
+
+---
+
+
+We’ve all seen the lazy QR code. It’s sitting in a window, sun-faded, linking to a 2018 PDF menu that takes forty seconds to load on a 4G connection. 
+
+QR codes are no longer just shortcuts to menus and homepages. In more useful setups, they act as measurable handoffs between physical attention and digital action. The financial impact is quantifiable: restaurants switching to digital QR ordering consistently see a **12-22% lift in average order value (AOV)**, according to **FoxiFood**.
+
+Used more deliberately, QR codes can help connect printed materials with measurable digital actions — without expensive software or technical overhead. Here are five practical use cases where better tracking makes physical marketing a lot more useful.
+
+---
+
+## 1. The "Abandoned Cart" for Physical Retail
+
+Imagine someone walks into your boutique, looks at a high-end jacket, and walks out. In e-commerce, you’d retarget them. In the physical world, they’re gone forever.
+
+**The Strategy:** Put a QR code on the physical price tag. Link it to a page that offers a "Save for Later" coupon via email or SMS. When they scan the tag at home, they have the link, the product photo, and a discount to pull them back in.
+
+<img src="../assets/images/lifestyle_retail_qr.png" alt="Apparel Store QR Tag Interaction" width="500" style="display: block; margin: 20px auto;">
+
+
+## 2. Real-Time Attribution for Local Partners
+
+You have your flyers in the local coffee shop. The owner is your friend, but is it actually working? 
+
+**The Strategy:** Use a dynamic QR code with a unique UTM parameter for *every single location*. Instead of wondering if the coffee shop flyers are better than the gym posters, you can check your analytics dashboard and know exactly which partner is driving the highest-quality leads. This level of precision is why **PM Group** found that including QR codes in direct mail campaigns can boost overall **subscriber and response rates by up to 35%**.
+
+## 3. The Interactive Service Sticker
+
+If you run a service business (HVAC, cleaning, landscaping), the most valuable real estate you own is the side of your customer’s furnace or the back of their cleaning cupboard.
+
+**The Strategy:** A weatherproof sticker with a QR code that links directly to a "Book Service" or "Request Refill" page. It turns a one-off job into a permanent interface.
+
+## 4. Turning TV/Video into a Checkout Counter
+
+We’ve seen the Coinbase Superbowl ad. You don't need a million-dollar budget to do this.
+
+**The Strategy:** If you’re running a YouTube ad or a local TV spot, keep the QR code on screen for at least 15 seconds. Make sure it isn't just a link to the homepage, but a direct link to the *exact promotional offer* shown in the video.
+
+## 5. Event Networking that Actually Works
+
+Paper business cards get lost. Typing a name into LinkedIn while standing in a noisy trade show aisle is annoying.
+
+**The Strategy:** A QR code on the back of your phone or your badge that links to a "Digital Contact Card" (vCard). Most people do this once, but the pro move is using a *dynamic* code. If you change your job title or portfolio link next month, the code on that expensive trade show banner still works.
+
+
+---
+
+
+## The Technical Detail: Why Dynamic Codes Matter
+
+The biggest mistake is using static QR codes for temporary campaigns. A static code is permanent. If your URL changes, the code is broken.
+
+**Dynamic QR codes** allow you to change the destination URL *after* the code is printed. This is the difference between a static billboard and a digital interface.
+
+You can test this setup using lightweight tools like [QR Master](https://qrmaster.net). It lets you create dynamic codes and track basic scan data without a subscription or an account—useful for seeing if the strategy works for you before scaling up.
+
+Don't let your physical marketing be a black hole for data. Start tracking the bridge between your real world and your digital one.
+
+
+---
+
+
+**Author Bio:** Timo is a founder and developer focused on closing the gap between offline and online marketing. He supports small business marketing through tools like [QR Master](https://qrmaster.net), focusing on making dynamic tracking accessible and simple.
--- a/articles/seosandwitch-qr-codes-offline-attribution.md
+++ b/articles/seosandwitch-qr-codes-offline-attribution.md
@@ -0,0 +1,186 @@
+# QR Codes as an Offline-to-Online Signal: How Marketers Can Measure Physical Campaigns More Reliably
+
+<img src="../assets/images/attribution_light.png" alt="Dynamic QR Code Attribution Flow" width="500" style="display: block; margin: 20px auto;">
+
+
+
+---
+
+
+## Introduction
+ 
+Marketers can usually tell you which ad got the click, which search term triggered the lead, or which email link generated the sale. But ask the same team which flyer at a trade show drove the most traffic, or which product insert is actually being read, and the answer often gets vague very quickly.
+
+This attribution gap isn't just a reporting annoyance; it's a budgeting problem. Without data on which physical touchpoints are working, marketers fly blind on where to spend their next dollar of offline budget.
+
+This article covers the mechanics of closing that gap: how QR codes function as a measurable offline-to-online signal, how to integrate scan data into a real attribution workflow, and what the indirect SEO implications are for the digital content those codes point to.
+ 
+---
+ 
+ 
+## Part 1: Understanding QR Codes as an Attribution Mechanism
+ 
+### Static vs. Dynamic: The Distinction That Actually Matters
+ 
+Not all QR codes generate useful data. A **static QR code** encodes a URL directly into the image. Scan it, go to the URL — and that's the end of the data trail. No tracking, no redirects, no analytics.
+ 
+**Dynamic QR codes** work differently. They point to a short redirect URL controlled by the QR code platform. When someone scans the code, they hit the redirect server first — which logs the event (timestamp, location, device type, scan count) — and then forwards them to the final destination.
+ 
+This redirect layer is what makes attribution possible. It functions the same way UTM-tagged short links function for social media clicks.
+ 
+### Dynamic QR Codes as UTM-Tagged Short Links for Physical Media
+ 
+A UTM parameter adds source, medium, and campaign data to a URL so your analytics platform can attribute sessions correctly. `?utm_source=google&utm_medium=cpc&utm_campaign=spring_sale` tells GA4 exactly where a visitor came from.
+ 
+The same logic applies to QR codes. A flyer at a farmers market can carry a dynamic QR code that redirects to:
+ 
+```
+https://yourdomain.com/landing-page?utm_source=flyer&utm_medium=print&utm_campaign=farmers_market_april
+```
+ 
+GA4 receives the session with full attribution. You can now measure:
+- How many sessions the flyer generated
+- Whether those sessions converted
+- How those users behaved compared to organic or paid visitors
+ 
+Applied systematically, this gives you cross-channel attribution that treats physical media as a first-class data source rather than a black box.
+ 
+ 
+### Beyond the Link: The Branding Impact
+
+Beyond the redirect mechanics, design plays a critical role in user conversion. **Wave Connect** reports that incorporating **logos or brand elements** into QR codes can increase scan rates by up to **80%**. In an offline environment, trust and visual recognition are just as important as technical functionality.
+
+---
+ 
+ 
+## Part 2: Building the Attribution Workflow
+ 
+### Step 1: Instrument Your Physical Materials
+ 
+Before printing anything, assign each physical asset a unique UTM combination. Don't collapse multiple materials into a single source — differentiation is the point.
+ 
+| Physical Material | UTM Source | UTM Medium | UTM Campaign |
+|-------------------|------------|------------|--------------|
+| Farmers market flyer | `farmers_market` | `print_flyer` | `spring_2025` |
+| Trade show banner | `conference_name` | `event_banner` | `spring_2025` |
+| Product insert | `product_box` | `insert` | `core_product` |
+| Business card | `business_card` | `networking` | `always_on` |
+ 
+Each combination gets its own dynamic QR code. Each code redirects to the destination URL with its UTM parameters appended.
+ 
+### Step 2: Track at Two Levels
+ 
+You now have two data sources:
+ 
+**QR Code Platform Analytics:** Scan count, location, device type, time of day. This is pre-click data — it tells you who engaged with the physical material.
+ 
+**Website Analytics (GA4):** Sessions, bounce rate, pages per session, goal completions. This is post-click data — it tells you what those people did once they arrived.
+ 
+The delta between scan count (pre-click) and session count (post-click) is your effective scan-to-session rate — a measure of how well the landing page matches the expectation the physical material set.
+ 
+### Step 3: Route Through One Redirect Layer
+ 
+The simplest architecture: your QR code platform generates the redirect URL (e.g., `qrm.st/abc123`), which redirects to your UTM-tagged destination URL (e.g., `yourdomain.com/page?utm_source=...`).
+ 
+Avoid using a generic URL shortener on top of a QR code platform on top of a UTM-tagged URL. Every additional redirect layer increases load time and the chance of a bounce before the session registers.
+ 
+### Step 4: Set Up a Dashboard
+ 
+Connect your QR scan data and GA4 attribution data in a single view. For most businesses, a simple Google Looker Studio dashboard pulling from GA4's campaign dimension plus a manual import of QR scan data from your platform works well.
+ 
+For higher-volume operations, look at whether your QR platform offers a GA4 or API integration. Some do. This makes automated reporting possible without manual data merging.
+ 
+ 
+---
+ 
+ 
+## Part 3: The SEO Implications
+ 
+QR codes do not directly improve rankings, but they can support better measurement, cleaner campaign attribution, and more qualified traffic to the pages they point to. In practice, QR-driven visits are often more qualified because the user has already engaged with the brand in a physical context. That makes the traffic commercially valuable even when the SEO effect remains indirect.
+ 
+### Offline Intent as a Quality Signal
+ 
+When a QR code scan sends a visitor to a targeted landing page, the resulting session behavior is often higher quality than a broad organic click. These users have high intent.
+ 
+High-quality traffic signals — low bounce rates, deeper session depth, and conversions — are indicators of a page's utility. While search engines have been cautious about confirming whether GA4 metrics are direct ranking factors, consistent engagement from high-intent audiences is a valid way to strengthen your content's overall signal profile.
+ 
+This is particularly relevant for Local SEO. A regional physical campaign driving engaged local sessions to a specific landing page provides the exact type of geographic relevance signals that matter for local results.
+ 
+### QR Codes and Content Distribution: The Link-Building Angle
+ 
+A more indirect application is using QR codes to drive high-intent eyes to link-worthy digital assets (data studies, calculators, or whitepapers).
+ 
+The workflow:
+1. You publish a high-quality resource on your site.
+2. You distribute a QR code linking to it via physical materials (conference handouts, product inserts).
+3. Professional users scan the code, discover the resource, and — because it's genuinely useful — some subset of them links to it or cites it from their own digital platforms.
+ 
+This turns physical distribution into a top-of-funnel discovery mechanism for link acquisition. It won't produce high volumes, but the links generated come from relevant, authoritative sources who discovered the content in the "real world."
+ 
+### Technical Execution and Crawling
+ 
+From a technical standpoint, the redirect of a dynamic QR code functions as a pass-through layer. For the end user, this is a 301 or 302 redirect to the target destination. This means:
+ 
+- The final destination URL retains full crawlability and indexability.
+- The redirect adds minimal latency (usually negligible), but keeping the destination page fast is critical since mobile users on cellular data have low patience.
+- Canonicalization: Ensure the destination page has a correct self-referencing canonical tag so that any traffic signals are consolidated correctly.
+ 
+ 
+---
+ 
+ 
+## Part 4: Case Study — Tracking Offline Foot Traffic Attribution
+ 
+Here is an example of the end-to-end data flow for a local business.
+ 
+**Scenario:** A local gym runs a seasonal campaign — posters in the neighborhood, flyers at a local health food store, and inserts in a physical "welcome kit."
+ 
+**Setup:**
+- Three dynamic QR codes created, one per material.
+- Each redirects to the same landing page with unique UTM parameters.
+- GA4 goal tracked: Trial Membership Booking.
+ 
+**Campaign Results (30 Days):**
+ 
+| Source | Scans | Sessions | Conversions | CVR (Scan-to-Trial) |
+|:-------|:------|:---------|:------------|:--------------------|
+| Neighborhood Poster | 94 | 61 | 4 | 4.2% |
+| Health Food Store | 212 | 164 | 19 | 8.9% |
+| Welcome Kit | 87 | 71 | 23 | 26.4% |
+ 
+**Analysis:** The health food store placement delivers the highest new-customer volume. The welcome kit has the highest conversion rate (existing relationship). The posters show lower conversion despite scans, suggesting the "buy-in" requirement for someone scanning on a sidewalk is higher than someone already inside a partner store.
+ 
+**Without tracking:** The gym would have no idea which print run was worth the money. With tracking, they know exactly where to reinvest.
+ 
+ 
+---
+ 
+ 
+## Part 5: Tooling Landscape
+ 
+Several tools handle dynamic QR code creation with analytics. They vary on analytics depth, link management features, and pricing.
+ 
+**QR Tiger** (qrtiger.com) — one of the more established platforms with bulk creation, folder organization, and basic scan analytics. Paid plans required for full analytics history.
+ 
+**QR Code Generator.com** — widely used, good brand recognition, analytics capped on free tier. Straightforward interface.
+ 
+**[QR Master](https://qrmaster.net)** — A simple, lightweight option for testing dynamic redirects. It provides scan counts and basic analytics without requiring an account or subscription, making it useful for testing the attribution workflow before committing to a complex setup.
+ 
+**Bitly** — primarily a URL shortener but includes QR code generation with click analytics. Useful if you're already using Bitly for link management.
+ 
+ 
+---
+ 
+ 
+## Conclusion
+
+QR codes are not an SEO tactic in themselves. They are a measurement layer for physical media.
+
+What makes them useful is not the square on the page, but the workflow behind it: unique routing, campaign attribution, landing-page alignment, and the ability to see which offline touchpoints actually lead to business outcomes.
+
+For marketers running print, events, packaging, or local campaigns, that closes a gap traditional analytics often leaves open. Instead of treating physical media as unmeasurable, QR codes make it possible to test, compare, and improve it with the same discipline applied to digital channels.
+
+The real opportunity is not just “using QR codes.” It is treating offline attention as something measurable, attributable, and worth optimizing. This move toward measurable print is part of a broader trend: as of late 2024, **62% of businesses** expect QR-driven initiatives to be a primary revenue driver in their 2025 strategy (**Uniqode**).
+
+
+---
--- a/articles/substack-playbook-series.md
+++ b/articles/substack-playbook-series.md
@@ -0,0 +1,63 @@
+# The QR Code Playbook: Issues 1-3
+
+
+---
+
+
+## Issue #1: The "Static is Dead" Manifesto
+*Date: Week 2*
+
+Welcome to the first issue of The QR Code Playbook. We’re starting with the most important rule of the game: **Never print a static QR code again.**
+
+A static code works fine — until something changes. Then it turns into a small but expensive operational problem. The moment your destination URL breaks, you’re stuck with permanent, dead-end assets.
+
+**The Dynamic Advantage:**
+Dynamic QR codes use a redirect layer. The printed pattern doesn't change, but you can change where it points from your computer. 
+
+**Scenario:** You print 1,000 menus for your restaurant. Your web developer changes the menu URL.
+- **Static:** You throw away 1,000 menus.
+- **Dynamic:** You spend 30 seconds changing the redirect link. 
+
+**This week's task:** Audit your current print materials. Anything with a QR code that isn't updateable is a liability. 
+
+
+---
+
+
+## Issue #2: The Event Marketer’s Secret Weapon
+*Date: Week 3*
+
+Events are chaos. Signage is expensive. ROI is hard to prove.
+
+This week, we’re looking at how to use "Contextual QR Codes" to track your booth’s performance. 
+
+**The Attribution Stack:**
+1. Create a unique code for your **Check-in Banner**.
+2. Create a unique code for your **Product Demo Flyer**.
+3. Create a unique code for your **Follow-up Postcard**.
+
+By tracking the scan rates of these three different codes, you can see where people dropped off. Did they check in but never look at the demo? Did they take the flyer but never scan the follow-up?
+
+Networking is where this shines: **82% of professionals** now prefer receiving a digital card over paper (**Forbes**), and data shows that users are **5x more likely to save a contact** when it's presented via QR (**HiHello**). 
+
+Now you aren't just "doing events"—you're measuring them.
+
+
+---
+
+
+## Issue #3: Closing the eCommerce "Blind Spot"
+*Date: Week 4*
+
+The moment your product box leaves the warehouse, you lose the data trail. You know it was delivered, but you don't know if the customer opened it, read the manual, or is actually using it. Customer sentiment is high here: **94% of consumers** who scan QR codes on product packaging find the information helpful for product usage or support (**Packaging Strategies**).
+
+**The Solution: Post-Purchase Redirection.**
+Include a QR code on the inside of the box lid.
+
+- **First 7 Days:** Link it to a "Getting Started" video.
+- **After 30 Days:** Change the redirect to a "Leave a Review" page.
+- **After 6 months:** Change the redirect to a "Reorder/Subscription" discount.
+
+One printed code. Three different stages of the customer lifecycle.
+
+*These workflows can be implemented with most dynamic QR platforms like [QR Master](https://qrmaster.net). The important part is choosing a tool that makes link updates and scan tracking easy to manage without unnecessary overhead.*
--- a/articles/techdee-5-qr-code-strategies.md
+++ b/articles/techdee-5-qr-code-strategies.md
@@ -0,0 +1,92 @@
+# 5 QR Code Strategies That Can Supercharge Small Business Marketing
+
+
+---
+
+
+Most small business owners use QR codes once, print them, and never think about them again. That works — but it usually means the QR code stays static, untracked, and much less useful than it could be.
+
+Used more deliberately, QR codes can help connect printed materials with measurable digital actions — without expensive software or technical overhead. Here are five practical strategies worth implementing this week.
+
+---
+
+
+## 1. Turn Business Cards Into a Living Portfolio
+
+Paper business cards have a lifespan problem. You print 500, use them over 18 months, and your website URL, phone number, or LinkedIn handle changes at least once in that time. The cards you already handed out become outdated the moment they leave your desk. This small addition to your physical networking can have a measurable impact on your digital footprint: adding QR codes to professional interactions (like business cards or email signatures) has been shown to increase **LinkedIn engagement by up to 15%** (**MySignature**).
+
+**The fix:** Add a dynamic QR code to your business card that links to a centrally managed contact page — your own "link-in-bio" page, a Google Site, or a simple landing page.
+
+Update the page whenever something changes. Every card you've already handed out automatically points to the current version. No reprints needed.
+
+Freelancers, consultants, and real estate agents with frequently updated portfolios get the most mileage out of this approach.
+
+
+---
+
+
+## 2. Track Which Offline Materials Actually Drive Traffic
+
+One of the biggest blind spots in small business marketing is not knowing which physical materials drive results. A flyer you handed out at a farmers market, a mailer you sent to the neighborhood, an insert in a product package — which one actually brought people to your site?
+
+**The fix:** Use a different dynamic QR code for each material and campaign. Track scan rates per code to see which placement and which audience responds.
+
+<img src="../assets/images/analytics_light.png" alt="Advanced QR Scan Analytics Dashboard" width="500" style="display: block; margin: 20px auto;">
+
+
+This isn't just a "big business" insight. Even basic scan analytics — how many scans, from which city, on which day — can tell a small business owner which trade show placement is worth paying for next year and which one isn't.
+
+You can test this attribution setup using lightweight tools like [QR Master](https://qrmaster.net). It lets you create dynamic codes and track basic scan data without a subscription—useful for seeing if the overhead of tracking is worth it for your business.
+
+
+---
+
+
+## 3. Make Product Packaging Evergreen
+
+If your business sells physical products, your packaging is one of the most expensive things to change. A new product page, an updated how-to guide, a warranty registration change — any of these would normally require a new print run.
+
+**The fix:** Put a dynamic QR code on the packaging and link it to a product resource page you control. When the page changes, the packaging doesn't have to.
+
+This is also useful for localization: if you start selling in a new market, redirect the code to a translated version of the page — without touching the packaging itself.
+
+
+---
+
+
+## 4. Run Contactless Event Check-Ins and Feedback Flows
+
+Events — whether a pop-up shop, a community workshop, or a trade show booth — generate a lot of friction around check-in, sign-ups, and post-event surveys. Paper forms take time to process. Verbal prompts are easy to forget.
+
+**The fix:** Post a QR code at check-in that links directly to a Google Form, Tally form, or Typeform. Do the same at the end of the event to collect feedback while the experience is still fresh.
+
+The code itself doesn't change between events — just swap the destination to a new form each time. Print one set of signage and reuse it.
+
+
+---
+
+
+## 5. A/B Test Landing Pages Without Reprinting
+
+Running a print campaign and not sure which landing page angle converts better? Normally, you'd have to commit to one before printing — and live with the results.
+
+**The fix:** Generate a single dynamic QR code, start with Landing Page A, then switch to Landing Page B halfway through the campaign. Compare scan-to-conversion rates across the two periods.
+
+This isn't a perfect controlled experiment, but it gives you directional data you wouldn't otherwise have from a print campaign — and it costs nothing extra to run.
+
+
+---
+
+
+## Getting Started
+
+The common thread across all five strategies is using dynamic QR codes rather than static ones. Dynamic codes let you update the destination after printing — which means your physical materials stay flexible. This move towards digital-first interaction isn't just a trend: according to **Salesforce**, **80% of marketers** now believe that a 'digital-first' approach is essential for staying competitive.
+
+For most small businesses, a free tool with basic analytics is enough to get started. The goal is data you can act on, not perfection.
+
+
+---
+
+
+
+**Format:** List-based, one-action-per-section, Techdee style
--- a/assets/images/analytics_dashboard_mockup.png
+++ b/assets/images/analytics_dashboard_mockup.png
--- a/assets/images/analytics_light.png
+++ b/assets/images/analytics_light.png
--- a/assets/images/attribution_flow.png
+++ b/assets/images/attribution_flow.png
--- a/assets/images/attribution_light.png
+++ b/assets/images/attribution_light.png
--- a/assets/images/business_card_scan.png
+++ b/assets/images/business_card_scan.png
--- a/assets/images/ecommerce_lifecycle.png
+++ b/assets/images/ecommerce_lifecycle.png
--- a/assets/images/lifecycle_light.png
+++ b/assets/images/lifecycle_light.png
--- a/assets/images/lifestyle_retail_qr.png
+++ b/assets/images/lifestyle_retail_qr.png
--- a/assets/images/static_vs_dynamic_comp.png
+++ b/assets/images/static_vs_dynamic_comp.png
--- a/assets/images/static_vs_dynamic_light.png
+++ b/assets/images/static_vs_dynamic_light.png
--- a/backlinks.md
+++ b/backlinks.md
--- a/blog-posts-improved/bulk-qr-excel-IMPROVED.md
+++ b/blog-posts-improved/bulk-qr-excel-IMPROVED.md
--- a/blog-posts-improved/qr-analytics-IMPROVED.md
+++ b/blog-posts-improved/qr-analytics-IMPROVED.md
--- a/blog-posts-seo-guide.md
+++ b/blog-posts-seo-guide.md
--- a/checklist/uploaded_image_0_1768484835516.png
+++ b/checklist/uploaded_image_0_1768484835516.png
--- a/checklist/uploaded_image_1_1768484835516.png
+++ b/checklist/uploaded_image_1_1768484835516.png
--- a/checklist/uploaded_image_2_1768484835516.png
+++ b/checklist/uploaded_image_2_1768484835516.png
--- a/checklist/uploaded_image_3_1768484835516.png
+++ b/checklist/uploaded_image_3_1768484835516.png
--- a/claude-artifact-template.md
+++ b/claude-artifact-template.md
@@ -1,134 +0,0 @@
-# Claude Artifact Template for QR Master Backlinks
-
-Use this template when creating Claude artifacts that link back to qrmaster.net.
-
---
-
-## How to Use
-
-1. Copy this template into Claude
-2. Customize for your specific topic
-3. Click "Publish Artifact"
-4. Add `www.qrmaster.net` to allowed domains
-5. Share the published link
-
---
-
-## Template: Dynamic QR Codes Guide
-
-```html
-<!DOCTYPE html>
-<html lang="en">
-<head>
-  <meta charset="UTF-8">
-  <meta name="viewport" content="width=device-width, initial-scale=1.0">
-  <title>Dynamic QR Codes: The Complete 2025 Guide</title>
-  <style>
-    body {
-      font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, sans-serif;
-      line-height: 1.6;
-      max-width: 800px;
-      margin: 0 auto;
-      padding: 40px 20px;
-      background: linear-gradient(135deg, #f8fafc 0%, #e2e8f0 100%);
-      color: #1e293b;
-    }
-    h1 { color: #0f172a; border-bottom: 3px solid #3b82f6; padding-bottom: 10px; }
-    h2 { color: #1e40af; margin-top: 2em; }
-    a { color: #2563eb; text-decoration: none; }
-    a:hover { text-decoration: underline; }
-    .cta {
-      background: linear-gradient(135deg, #3b82f6, #2563eb);
-      color: white;
-      padding: 20px 30px;
-      border-radius: 12px;
-      text-align: center;
-      margin: 30px 0;
-    }
-    .cta a { color: white; font-weight: bold; font-size: 1.1em; }
-    ul { margin: 1em 0; }
-    li { margin: 0.5em 0; }
-    .highlight { background: #dbeafe; padding: 15px; border-radius: 8px; margin: 20px 0; }
-  </style>
-</head>
-<body>
-  <h1>Dynamic QR Codes: The Complete 2025 Guide</h1>
-  
-  <p>Dynamic QR codes have revolutionized how businesses connect offline and online experiences. Unlike static codes, dynamic QR codes can be edited after printing, tracked in real-time, and optimized based on performance data.</p>
-  
-  <h2>What Makes Dynamic QR Codes Different?</h2>
-  <ul>
-    <li><strong>Editable:</strong> Change the destination URL anytime without reprinting</li>
-    <li><strong>Trackable:</strong> Monitor scans, locations, devices, and timing</li>
-    <li><strong>Smaller:</strong> Short redirect URLs create cleaner QR patterns</li>
-    <li><strong>Flexible:</strong> Perfect for campaigns where content may change</li>
-  </ul>
-  
-  <div class="highlight">
-    <strong>Pro Tip:</strong> Always use dynamic QR codes for printed materials. If your URL changes after printing 10,000 flyers, you won't need to reprint them.
-  </div>
-  
-  <h2>Best Use Cases</h2>
-  <ul>
-    <li>Restaurant menus that change seasonally</li>
-    <li>Event tickets with real-time updates</li>
-    <li>Product packaging with warranty info</li>
-    <li>Marketing campaigns with A/B testing</li>
-    <li>Business cards with contact details</li>
-  </ul>
-  
-  <h2>How to Create Dynamic QR Codes</h2>
-  <p>The easiest way is using a dedicated platform like <a href="https://www.qrmaster.net" target="_blank">QR Master</a>. Here's the process:</p>
-  <ol>
-    <li>Sign up for a free account</li>
-    <li>Click "Create QR Code" and select "Dynamic"</li>
-    <li>Enter your destination URL</li>
-    <li>Customize colors and add your logo</li>
-    <li>Download in SVG or PNG format</li>
-    <li>Track scans in your analytics dashboard</li>
-  </ol>
-  
-  <div class="cta">
-    <a href="https://www.qrmaster.net/signup" target="_blank">Create Your Free Dynamic QR Code →</a>
-  </div>
-  
-  <h2>Tracking & Analytics</h2>
-  <p>With dynamic QR codes, you get access to powerful analytics:</p>
-  <ul>
-    <li>Total and unique scan counts</li>
-    <li>Geographic distribution (city/country)</li>
-    <li>Device breakdown (iOS vs Android)</li>
-    <li>Time-based patterns (peak hours)</li>
-    <li>Conversion tracking integration</li>
-  </ul>
-  
-  <p>Learn more about <a href="https://www.qrmaster.net/qr-code-tracking" target="_blank">QR code tracking</a> and <a href="https://www.qrmaster.net/blog/qr-code-analytics" target="_blank">analytics best practices</a>.</p>
-  
-  <h2>Pricing</h2>
-  <p>Most platforms offer tiered pricing. <a href="https://www.qrmaster.net/pricing" target="_blank">QR Master pricing</a> starts with a free tier (3 dynamic codes) and scales up for businesses needing more codes and features.</p>
-  
-  <hr>
-  <p><em>This guide is provided by <a href="https://www.qrmaster.net" target="_blank">QR Master</a> - Free Dynamic QR Code Generator with Analytics.</em></p>
-</body>
-</html>
-```
-
---
-
-## Topic Ideas for More Artifacts
-
-1. **"QR Codes for Restaurants: Complete Setup Guide"** - Link to /blog/qr-code-restaurant-menu
-2. **"Digital Business Cards with QR Codes"** - Link to /blog/vcard-qr-code-generator
-3. **"QR Code Print Size Calculator"** - Link to /blog/qr-code-print-size-guide
-4. **"Small Business QR Code Marketing Playbook"** - Link to /blog/qr-code-small-business
-5. **"Static vs Dynamic QR Codes Comparison"** - Link to /blog/dynamic-vs-static-qr-codes
-
---
-
-## Publishing Steps
-
-1. Create artifact in Claude with HTML content above
-2. Click "Publish" button
-3. In "Allowed domains" field, enter: `www.qrmaster.net, qrmaster.net`
-4. Copy the embed code or share URL
-5. The links inside will count as backlinks once indexed
--- a/claude-seo-prompts.md
+++ b/claude-seo-prompts.md
@@ -1,180 +0,0 @@
-# Claude Artifact Prompts for Parasite SEO
-
-**Goal:** Publish educational content on claude.ai that naturally links to qrmaster.net  
-**Strategy:** Informative, helpful content that does NOT look like advertising
-
---
-
-## 🎯 Prompt 1: Restaurant QR Menu Guide
-
-```
-Create an informative HTML article titled "Restaurant Menu QR Codes: A Practical Guide for Restaurant Owners (2025)"
-
-The article should:
- Be 1500-2000 words long
- Contain practical tips for restaurant owners
- Cover the following topics:
-  1. Why digital menus are the new standard
-  2. PDF vs. online menu - pros and cons
-  3. Optimal placement of QR codes in restaurants
-  4. Mistakes restaurants should avoid
-  5. Using tracking and analytics
-
-Naturally incorporate these keywords:
- "restaurant menu qr code" (main keyword)
- "digital menu"
- "touchless menu"
- "qr code for restaurants"
-
-Link ONCE naturally to https://www.qrmaster.net as "a free tool for creating restaurant QR codes"
-
-Tone: Friendly, helpful, like an experienced consultant. NOT salesy.
-
-HTML with clean CSS, mobile-friendly. No external dependencies.
-```
-
---
-
-## 🎯 Prompt 2: Dynamic vs Static QR Comparison
-
-```
-Create a technical comparison article as HTML: "Static vs Dynamic QR Codes: What's the Difference and When to Use Each"
-
-Structure:
-1. Brief explanation of what QR codes are technically
-2. Static QR codes - how they work
-3. Dynamic QR codes - how they work
-4. Comparison table (very important!)
-5. Decision guide: When to use which type
-6. Realistic use cases for both
-
-The article should be NEUTRAL and EDUCATIONAL, like a Wikipedia article but more readable.
-
-Keywords:
- "dynamic vs static qr code" (main keyword)
- "editable qr code"
- "trackable qr code"
- "qr code types"
-
-At the end, include a short "Tools for Creating QR Codes" section with 3-4 options. One of them is https://www.qrmaster.net - listed as an equal entry, NOT as a recommendation.
-
-HTML with professional, minimalist design.
-```
-
---
-
-## 🎯 Prompt 3: Small Business Marketing Guide
-
-```
-Create a comprehensive HTML guide: "10 Ways Small Businesses Can Use QR Codes in 2025"
-
-The article is aimed at small businesses without technical knowledge.
-
-The 10 use cases:
-1. Digital business cards (vCard)
-2. Collecting Google reviews
-3. Contactless payments
-4. Sharing Wi-Fi access
-5. Growing social media followers
-6. Linking product information
-7. Simplifying appointment booking
-8. Discount promotions & coupons
-9. Event tickets & check-in
-10. Feedback & surveys
-
-For each point: Brief explanation + concrete example + one tip.
-
-Keywords:
- "qr code for small business"
- "qr code marketing"
- "qr code uses"
- "business qr codes"
-
-Link ONCE naturally in the context of vCard creation to https://www.qrmaster.net/blog/vcard-qr-code-generator
-
-Tone: Enthusiastic but not over the top. Like a helpful friend explaining technology.
-```
-
---
-
-## 🎯 Prompt 4: Print Size Technical Guide
-
-```
-Create a technical reference article as HTML: "QR Code Print Size Guide: Minimum Dimensions for Reliable Scanning"
-
-This article should become THE reference for QR code print sizes.
-
-Content:
-1. The science behind QR scanning (brief)
-2. The golden formula: Size = Distance ÷ 10
-3. LARGE table with applications, distances, min/recommended sizes
-4. Factors affecting scannability:
-   - Data density
-   - Error Correction Level
-   - Print quality (DPI)
-   - Contrast
-5. Quiet zone requirements
-6. File formats for printing (SVG vs PNG vs PDF)
-7. Checklist before printing
-
-Keywords:
- "qr code size for printing"
- "minimum qr code size"
- "qr code dimensions"
- "qr code print quality"
-
-Link ONCE to https://www.qrmaster.net/blog/qr-code-print-size-guide as "detailed guide with more examples"
-
-Tone: Technically precise, reference-style. For designers and marketers.
-```
-
---
-
-## 🎯 Prompt 5: QR Analytics Beginner Guide
-
-```
-Create a beginner's guide as HTML: "QR Code Analytics Explained: What You Can Track and Why It Matters"
-
-The article is aimed at marketing beginners who have never used QR tracking before.
-
-Structure:
-1. What is QR tracking and why is it important?
-2. What data can you track? (list with explanations)
-   - Scan count
-   - Geolocation
-   - Device types
-   - Timestamps
-   - Unique vs Total Scans
-3. How does it work technically? (simplified)
-4. Privacy & GDPR considerations
-5. Practical application: Measuring campaign ROI
-6. Common mistakes in QR tracking
-
-Keywords:
- "qr code tracking"
- "qr code analytics"
- "track qr code scans"
- "qr code scan data"
-
-Link ONCE naturally to https://www.qrmaster.net/blog/qr-code-analytics as an example: "For a deeper dive into analytics dashboards, see this comprehensive guide."
-
-Tone: Friendly and explanatory, like a teacher. No jargon without explanation.
-```
-
---
-
-## 📋 Usage Instructions
-
-1. **Copy prompt** → Paste into claude.ai
-2. **Let it create the artifact**
-3. **Click "Publish"** in Claude
-4. **Allowed Domain:** Add `www.qrmaster.net, qrmaster.net`
-5. **Share link** - Google indexes these!
-
-## 💡 Tips for Maximum Effectiveness
-
- **Don't publish all on the same day**
- About **1 article per week** for natural growth
- Publish the **more neutral articles first** (Prompt 2 & 4)
- **Share on social media** for faster indexing
- Register the published URLs in Google Search Console
--- a/claude_plan_restaurant.md
+++ b/claude_plan_restaurant.md
@@ -0,0 +1,464 @@
+ Here is Claude's plan:
+╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
+ Restaurant Menu QR Code - Dashboard Integration Plan
+
+ Executive Summary
+
+ Add "Restaurant Menu" as a new QR code content type in the dashboard at /create.    
+ Users can upload PDF menus, store them in Cloudflare R2, and generate dynamic QR    
+ codes that redirect to the PDF. This integrates with the existing QRCode model and  
+ tracking system.
+
+ Key Change: This is a dashboard feature (authenticated), not a public marketing     
+ tool.
+
+ Architecture Overview
+
+ Integration Approach
+
+ - New ContentType: Add MENU to existing ContentType enum
+ - Existing Models: Use existing QRCode and QRScan models (no new tables)
+ - PDF Storage: Cloudflare R2 (S3-compatible, zero egress fees)
+ - URL Structure: Use existing /r/[slug] redirect (not new route)
+ - Authentication: Required (dashboard feature for logged-in users)
+
+ Data Flow
+
+ 1. User logs in → Goes to /create → Selects "Restaurant Menu" type
+ 2. Uploads PDF → Validate → Upload to R2 → Get public URL
+ 3. Creates QR code with content: { pdfUrl: "...", restaurantName: "...", menuTitle: 
+  "..." }
+ 4. QR code redirects to: /r/[slug] → Redirect to PDF URL
+ 5. Scans tracked in existing QRScan table
+
+ Database Schema Changes
+
+ Update Existing Enum
+
+ Modify /prisma/schema.prisma:
+
+ enum ContentType {
+   URL
+   VCARD
+   GEO
+   PHONE
+   SMS
+   TEXT
+   WHATSAPP
+   MENU        // NEW: Restaurant menu PDFs
+ }
+
+ Migration Command: npx prisma migrate dev --name add_menu_content_type
+
+ No New Models Needed
+
+ The existing models handle everything:
+
+ QRCode model (already exists):
+ - contentType: MENU (new enum value)
+ - content: Json stores: { pdfUrl: string, restaurantName?: string, menuTitle?:      
+ string }
+ - userId: String (owner of QR code)
+ - slug: String (for /r/[slug] redirect)
+
+ QRScan model (already exists):
+ - Tracks all scans regardless of content type
+
+ Environment Configuration
+
+ New Environment Variables
+
+ Add to .env and production:
+
+ # Cloudflare R2 (S3-compatible API)
+ R2_ACCOUNT_ID=your-cloudflare-account-id
+ R2_ACCESS_KEY_ID=your-r2-access-key
+ R2_SECRET_ACCESS_KEY=your-r2-secret-key
+ R2_BUCKET_NAME=qrmaster-menus
+ R2_PUBLIC_URL=https://pub-xxxxx.r2.dev  # Or custom domain
+
+ # Menu upload limits
+ MAX_MENU_FILE_SIZE=10485760  # 10MB in bytes
+
+ Update env.ts
+
+ Add to /src/lib/env.ts schema:
+
+ const envSchema = z.object({
+   // ... existing fields ...
+   R2_ACCOUNT_ID: z.string().optional(),
+   R2_ACCESS_KEY_ID: z.string().optional(),
+   R2_SECRET_ACCESS_KEY: z.string().optional(),
+   R2_BUCKET_NAME: z.string().default('qrmaster-menus'),
+   R2_PUBLIC_URL: z.string().optional(),
+   MAX_MENU_FILE_SIZE: z.string().default('10485760'),
+ });
+
+ Critical Files to Modify/Create
+
+ 1. R2 Client Library
+
+ File: /src/lib/r2.ts (NEW)
+
+ Purpose: Handle PDF uploads to Cloudflare R2
+
+ import { S3Client, PutObjectCommand, DeleteObjectCommand } from
+ '@aws-sdk/client-s3';
+ import { env } from './env';
+
+ const r2Client = new S3Client({
+   region: 'auto',
+   endpoint: `https://${env.R2_ACCOUNT_ID}.r2.cloudflarestorage.com`,
+   credentials: {
+     accessKeyId: env.R2_ACCESS_KEY_ID!,
+     secretAccessKey: env.R2_SECRET_ACCESS_KEY!,
+   },
+ });
+
+ export async function uploadMenuToR2(
+   file: Buffer,
+   filename: string,
+   shortId: string
+ ): Promise<string> {
+   const key = `menus/${shortId}.pdf`;
+
+   await r2Client.send(
+     new PutObjectCommand({
+       Bucket: env.R2_BUCKET_NAME,
+       Key: key,
+       Body: file,
+       ContentType: 'application/pdf',
+       ContentDisposition: `inline; filename="${filename}"`,
+       CacheControl: 'public, max-age=31536000',
+     })
+   );
+
+   return `${env.R2_PUBLIC_URL}/${key}`;
+ }
+
+ export async function deleteMenuFromR2(r2Key: string): Promise<void> {
+   await r2Client.send(
+     new DeleteObjectCommand({
+       Bucket: env.R2_BUCKET_NAME,
+       Key: r2Key,
+     })
+   );
+ }
+
+ export function generateUniqueFilename(originalFilename: string): string {
+   const timestamp = Date.now();
+   const random = crypto.randomBytes(4).toString('hex');
+   const ext = originalFilename.split('.').pop();
+   return `menu_${timestamp}_${random}.${ext}`;
+ }
+
+ 2. Upload API Endpoint
+
+ File: /src/app/api/menu/upload/route.ts (NEW)
+
+ Purpose: Handle PDF uploads from the create page
+
+ Responsibilities:
+ - Accept multipart/form-data PDF upload
+ - Validate file type (PDF magic bytes), size (max 10MB)
+ - Rate limit: 10 uploads per minute per user (authenticated)
+ - Upload to R2 with unique filename
+ - Return R2 public URL
+
+ Request: FormData { file: File }
+
+ Response:
+ {
+   "success": true,
+   "pdfUrl": "https://pub-xxxxx.r2.dev/menus/menu_1234567890_abcd.pdf"
+ }
+
+ Key Implementation Details:
+ - Use request.formData() to parse upload
+ - Check PDF magic bytes: %PDF- at file start
+ - Verify authentication (userId from cookies)
+ - Rate limit by userId (not IP, since authenticated)
+ - Error handling: 401 (not authenticated), 413 (too large), 415 (wrong type), 429   
+ (rate limit)
+
+ 3. Update Redirect Route
+
+ File: /src/app/r/[slug]/route.ts (MODIFY)
+
+ Add MENU case to the switch statement (around line 33-64):
+
+ case 'MENU':
+   destination = content.pdfUrl || 'https://example.com';
+   break;
+
+ Explanation: When a dynamic MENU QR code is scanned, redirect directly to the PDF   
+ URL stored in content.pdfUrl
+
+ 4. Update Validation Schema
+
+ File: /src/lib/validationSchemas.ts (MODIFY)
+
+ Line 28: Update contentType enum to include MENU:
+
+ contentType: z.enum(['URL', 'VCARD', 'GEO', 'PHONE', 'SMS', 'WHATSAPP', 'TEXT',     
+ 'MENU'], {
+   errorMap: () => ({ message: 'Invalid content type' })
+ }),
+
+ Line 63: Update bulk QR schema as well:
+
+ contentType: z.enum(['URL', 'VCARD', 'GEO', 'PHONE', 'SMS', 'WHATSAPP', 'TEXT',     
+ 'MENU']),
+
+ 5. Update Create Page - Add MENU Type
+
+ File: /src/app/(app)/create/page.tsx (MODIFY)
+
+ Multiple changes needed:
+
+ A. Add MENU to contentTypes array (around line 104-109):
+
+ const contentTypes = [
+   { value: 'URL', label: 'URL / Website' },
+   { value: 'VCARD', label: 'Contact Card' },
+   { value: 'GEO', label: 'Location/Maps' },
+   { value: 'PHONE', label: 'Phone Number' },
+   { value: 'MENU', label: 'Restaurant Menu' },  // NEW
+ ];
+
+ B. Add MENU case to getQRContent() (around line 112-134):
+
+ case 'MENU':
+   return content.pdfUrl || 'https://example.com/menu.pdf';
+
+ C. Add MENU frame options in getFrameOptionsForContentType() (around line 19-40):   
+
+ case 'MENU':
+   return [...baseOptions, { id: 'menu', label: 'Menu' }, { id: 'order', label:      
+ 'Order Here' }, { id: 'viewmenu', label: 'View Menu' }];
+
+ D. Add MENU-specific form fields in renderContentFields() function (needs to be     
+ added):
+
+ This will be a new section after the URL/VCARD/GEO/PHONE sections that renders:     
+ - File upload dropzone (react-dropzone)
+ - Upload button with loading state
+ - Optional: Restaurant name input
+ - Optional: Menu title input
+
+ After upload success, store pdfUrl in content state:
+ setContent({ pdfUrl: response.pdfUrl, restaurantName: '', menuTitle: '' });
+
+ 6. Update Rate Limiting
+
+ File: /src/lib/rateLimit.ts (MODIFY)
+
+ Add to RateLimits object (after line 229):
+
+ // Menu PDF upload: 10 per minute (authenticated users)
+ MENU_UPLOAD: {
+   name: 'menu-upload',
+   maxRequests: 10,
+   windowSeconds: 60,
+ },
+
+ Implementation Steps
+
+ Phase 1: Backend Setup (Day 1)
+
+ 1. Install Dependencies
+ npm install @aws-sdk/client-s3 react-dropzone
+ 2. Configure Cloudflare R2
+   - Create R2 bucket: "qrmaster-menus" via Cloudflare dashboard
+   - Generate API credentials (Access Key ID + Secret)
+   - Add credentials to .env and production environment
+   - Set bucket to public (for PDF access)
+ 3. Database Migration
+   - Add MENU to ContentType enum in prisma/schema.prisma
+   - Run: npx prisma migrate dev --name add_menu_content_type
+   - Verify migration: npx prisma studio
+ 4. Environment Configuration
+   - Update src/lib/env.ts with R2 variables
+   - Update src/lib/rateLimit.ts with MENU_UPLOAD config
+ 5. Create R2 Client
+   - Create src/lib/r2.ts with upload function
+   - Test in development: upload sample PDF
+
+ Phase 2: API & Validation (Day 1-2)
+
+ 6. Update Validation Schema (/src/lib/validationSchemas.ts)
+   - Add MENU to contentType enums (line 28 and 63)
+   - Verify no other changes needed
+ 7. Create Upload API (/src/app/api/menu/upload/route.ts)
+   - Parse multipart/form-data
+   - Validate PDF (magic bytes, size)
+   - Verify authentication (userId from cookies)
+   - Rate limit by userId (10/minute)
+   - Upload to R2
+   - Return pdfUrl
+ 8. Update Redirect Route (/src/app/r/[slug]/route.ts)
+   - Add MENU case to switch statement (line 33-64)
+   - Redirect to content.pdfUrl
+
+ Phase 3: Dashboard Integration (Day 2-3)
+
+ 9. Update Create Page (/src/app/(app)/create/page.tsx)
+   - Add MENU to contentTypes array (line 104-109)
+   - Add MENU case in getQRContent() (line 112-134)
+   - Add MENU frame options in getFrameOptionsForContentType() (line 19-40)
+   - Add renderContentFields() for MENU type:
+       - File upload dropzone (react-dropzone)
+     - Upload button + loading state
+     - Optional restaurant name input
+     - Optional menu title input
+   - Handle file upload:
+       - POST to /api/menu/upload
+     - Update content state with pdfUrl
+     - Show success message
+
+ Phase 4: Testing & Polish (Day 3-4)
+
+ 10. Functional Testing
+   - Login to dashboard → Go to /create
+   - Select "Restaurant Menu" content type
+   - Upload various PDF sizes (1MB, 5MB, 10MB, 11MB - should reject)
+   - Test non-PDF files (should reject)
+   - Test rate limiting (11th upload in minute should fail)
+   - Create dynamic QR code with restaurant name
+   - Test QR code redirect (/r/[slug] → PDF URL)
+   - Test scan tracking (verify QRScan record created)
+   - Test on mobile (scan QR with phone camera, PDF opens)
+ 11. Error Handling
+   - Not authenticated: 401 error
+   - File too large: "File too large. Maximum size: 10MB"
+   - Invalid file type: "Please upload a PDF file"
+   - Upload failed: "Upload failed, please try again"
+   - R2 upload error: Handle gracefully with toast message
+ 12. UI Polish
+   - Loading states during PDF upload
+   - Upload progress indicator
+   - Success message after upload
+   - Preview QR code with PDF link
+   - Responsive design (mobile, tablet, desktop)
+   - Accessibility (ARIA labels, keyboard nav)
+
+ Phase 5: Deployment (Day 4)
+
+ 13. Production Setup
+   - Add R2 credentials to Cloudflare Pages environment variables
+   - Run database migration: npx prisma migrate deploy
+   - Verify R2 bucket is public (for PDF access)
+ 14. Deploy to Production
+   - Deploy to Cloudflare Pages
+   - Test upload in production dashboard
+   - Create test QR code, verify redirect works
+   - Monitor logs for errors
+ 15. Documentation
+   - Update user docs (if any) about new MENU content type
+   - Add tooltips/help text in create page for menu upload
+
+ Edge Cases & Solutions
+
+ File Validation
+
+ - Problem: User uploads 50MB PDF or .exe file
+ - Solution:
+   - Client-side validation (check file.size and file.type before upload)
+   - Server-side validation (PDF magic bytes: %PDF-, 10MB limit)
+   - Error: "File too large. Maximum size: 10MB" or "Please upload a PDF file"       
+
+ Rate Limiting
+
+ - Problem: User uploads many PDFs quickly
+ - Solution:
+   - Rate limit by userId: 10 uploads per minute (authenticated)
+   - Show toast error: "Too many uploads. Please wait a moment."
+   - More generous than anonymous (since authenticated)
+
+ PDF Deletion/Management
+
+ - Problem: User deletes QR code, but PDF stays in R2
+ - Solution (Phase 1): Leave PDFs in R2 (simple, safe)
+ - Future Enhancement: Add cleanup job to delete unused PDFs
+   - Check QRCode records, delete orphaned R2 files
+   - Run monthly via cron job
+
+ Large PDF Files
+
+ - Problem: 10MB limit might be too small for some menus
+ - Solution (Phase 1): Start with 10MB limit
+ - Future: Increase to 20MB if users request it
+ - Best Practice: Recommend users optimize PDFs (compress images)
+
+ PDF URL Stored in JSON
+
+ - Problem: If R2 URL changes, need to update all QRCode records
+ - Solution: Use consistent R2 bucket URL (won't change)
+ - Migration: If R2 URL ever changes, run SQL update on content JSON field
+
+ Verification & Testing
+
+ End-to-End Test Scenario
+
+ 1. Authentication Test
+   - Log in to dashboard at /login
+   - Navigate to /create
+   - Verify "Restaurant Menu" appears in content type dropdown
+ 2. Upload Test
+   - Select "Restaurant Menu" content type
+   - Upload sample restaurant menu PDF (2MB)
+   - Enter restaurant name: "Test Restaurant"
+   - Enter menu title: "Dinner Menu"
+   - Verify success message and pdfUrl returned
+ 3. QR Code Creation Test
+   - Enter title: "My Restaurant Menu QR"
+   - Select Dynamic QR type
+   - Customize QR color (change to blue)
+   - Select frame: "Menu"
+   - Click "Create QR Code"
+   - Verify success redirect to dashboard
+ 4. Scan Test
+   - From dashboard, copy QR code URL: qrmaster.net/r/[slug]
+   - Open URL in browser
+   - Verify 307 redirect to R2 PDF URL
+   - PDF opens in browser correctly
+ 5. Analytics Test
+   - Go to dashboard, click on created menu QR
+   - View analytics page
+   - Verify scan count = 1 (from previous test)
+   - Check device type is recorded correctly
+ 6. Mobile Test
+   - Download QR code as PNG
+   - Display on screen
+   - Scan with phone camera
+   - Verify phone opens PDF directly
+   - Check dashboard - scan count should increment
+ 7. Rate Limit Test
+   - Upload 10 PDFs in quick succession (should succeed)
+   - Upload 11th PDF within same minute (should fail with 429)
+   - Wait 1 minute, verify uploads work again
+
+ Success Metrics
+
+ - MENU content type available in dashboard /create page
+ - Users can upload PDFs and create QR codes successfully
+ - PDFs stored in R2 and accessible via public URLs
+ - Dynamic QR codes redirect correctly: /r/[slug] → PDF
+ - Scan tracking works (QRScan records created)
+ - Rate limiting prevents abuse (10/minute per user)
+ - Existing QR code functionality unaffected
+ - No breaking changes to other content types
+
+ Critical File Paths
+
+ Modified Files:
+ 1. /prisma/schema.prisma - Add MENU to ContentType enum
+ 2. /src/lib/validationSchemas.ts - Add MENU to contentType enums (lines 28, 63)     
+ 3. /src/app/(app)/create/page.tsx - Add MENU UI and logic
+ 4. /src/app/r/[slug]/route.ts - Add MENU redirect case
+ 5. /src/lib/env.ts - Add R2 environment variables
+ 6. /src/lib/rateLimit.ts - Add MENU_UPLOAD rate limit
+
+ New Files:
+ 7. /src/lib/r2.ts - R2 client library for PDF uploads
+ 8. /src/app/api/menu/upload/route.ts - PDF upload API endpoint
--- a/dev-server.js
+++ b/dev-server.js
@@ -1,12 +1,12 @@
-const { spawn } = require('child_process');
-
-// Start Next.js dev server with explicit hostname
-const next = spawn('next', ['dev', '-p', '3050', '-H', '0.0.0.0'], {
-  stdio: 'inherit',
-  shell: true,
-  env: { ...process.env, HOSTNAME: '0.0.0.0' }
-});
-
-next.on('close', (code) => {
-  process.exit(code);
-});
+const { spawn } = require('child_process');
+
+// Start Next.js dev server with explicit hostname
+const next = spawn('next', ['dev', '-p', '3050', '-H', '0.0.0.0'], {
+  stdio: 'inherit',
+  shell: true,
+  env: { ...process.env, HOSTNAME: '0.0.0.0' }
+});
+
+next.on('close', (code) => {
+  process.exit(code);
+});
--- a/docker-compose.dev.yml
+++ b/docker-compose.dev.yml
@@ -1,66 +1,66 @@
-services:
-  # PostgreSQL Database
-  db:
-    image: postgres:16-alpine
-    container_name: qrmaster-db-dev
-    restart: unless-stopped
-    environment:
-      POSTGRES_USER: postgres
-      POSTGRES_PASSWORD: postgres
-      POSTGRES_DB: qrmaster
-      POSTGRES_INITDB_ARGS: "-E UTF8 --locale=en_US.utf8"
-    ports:
-      - "5435:5432"
-    volumes:
-      - dbdata_dev:/var/lib/postgresql/data
-      - ./docker/init-db.sh:/docker-entrypoint-initdb.d/init-db.sh
-    healthcheck:
-      test: [ "CMD-SHELL", "pg_isready -U postgres -d qrmaster" ]
-      interval: 5s
-      timeout: 5s
-      retries: 10
-    networks:
-      - qrmaster-network
-
-  # Redis Cache
-  redis:
-    image: redis:7-alpine
-    container_name: qrmaster-redis-dev
-    restart: unless-stopped
-    command: redis-server --appendonly yes --maxmemory 256mb --maxmemory-policy allkeys-lru
-    ports:
-      - "6379:6379"
-    volumes:
-      - redisdata_dev:/data
-    healthcheck:
-      test: [ "CMD", "redis-cli", "ping" ]
-      interval: 5s
-      timeout: 3s
-      retries: 5
-    networks:
-      - qrmaster-network
-
-  # Adminer - Database Management UI
-  adminer:
-    image: adminer:latest
-    container_name: qrmaster-adminer-dev
-    restart: unless-stopped
-    ports:
-      - "8081:8080"
-    environment:
-      ADMINER_DEFAULT_SERVER: db
-      ADMINER_DESIGN: pepa-linha
-    depends_on:
-      - db
-    networks:
-      - qrmaster-network
-
-volumes:
-  dbdata_dev:
-    driver: local
-  redisdata_dev:
-    driver: local
-
-networks:
-  qrmaster-network:
-    driver: bridge
+services:
+  # PostgreSQL Database
+  db:
+    image: postgres:16-alpine
+    container_name: qrmaster-db-dev
+    restart: unless-stopped
+    environment:
+      POSTGRES_USER: ${POSTGRES_USER}
+      POSTGRES_PASSWORD: ${POSTGRES_PASSWORD}
+      POSTGRES_DB: ${POSTGRES_DB}
+      POSTGRES_INITDB_ARGS: "-E UTF8 --locale=en_US.utf8"
+    ports:
+      - "5435:5432"
+    volumes:
+      - dbdata_dev:/var/lib/postgresql/data
+      - ./docker/init-db.sh:/docker-entrypoint-initdb.d/init-db.sh
+    healthcheck:
+      test: [ "CMD-SHELL", "pg_isready -U postgres -d qrmaster" ]
+      interval: 5s
+      timeout: 5s
+      retries: 10
+    networks:
+      - qrmaster-network
+
+  # Redis Cache
+  redis:
+    image: redis:7-alpine
+    container_name: qrmaster-redis-dev
+    restart: unless-stopped
+    command: redis-server --appendonly yes --maxmemory 256mb --maxmemory-policy allkeys-lru
+    ports:
+      - "6379:6379"
+    volumes:
+      - redisdata_dev:/data
+    healthcheck:
+      test: [ "CMD", "redis-cli", "ping" ]
+      interval: 5s
+      timeout: 3s
+      retries: 5
+    networks:
+      - qrmaster-network
+
+  # Adminer - Database Management UI
+  adminer:
+    image: adminer:latest
+    container_name: qrmaster-adminer-dev
+    restart: unless-stopped
+    ports:
+      - "8081:8080"
+    environment:
+      ADMINER_DEFAULT_SERVER: db
+      ADMINER_DESIGN: pepa-linha
+    depends_on:
+      - db
+    networks:
+      - qrmaster-network
+
+volumes:
+  dbdata_dev:
+    driver: local
+  redisdata_dev:
+    driver: local
+
+networks:
+  qrmaster-network:
+    driver: bridge
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -1,115 +1,119 @@
-services:
-  # PostgreSQL Database
-  db:
-    image: postgres:16-alpine
-    container_name: qrmaster-db
-    restart: unless-stopped
-    environment:
-      POSTGRES_USER: postgres
-      POSTGRES_PASSWORD: postgres
-      POSTGRES_DB: qrmaster
-      POSTGRES_INITDB_ARGS: "-E UTF8 --locale=en_US.utf8"
-    ports:
-      - "5435:5432"
-    volumes:
-      - dbdata:/var/lib/postgresql/data
-      - ./docker/init-db.sh:/docker-entrypoint-initdb.d/init-db.sh
-    healthcheck:
-      test: [ "CMD-SHELL", "pg_isready -U postgres -d qrmaster" ]
-      interval: 5s
-      timeout: 5s
-      retries: 10
-    networks:
-      - qrmaster-network
-
-  # Redis Cache
-  redis:
-    image: redis:7-alpine
-    container_name: qrmaster-redis
-    restart: unless-stopped
-    command: redis-server --appendonly yes --maxmemory 256mb --maxmemory-policy allkeys-lru
-    ports:
-      - "6379:6379"
-    volumes:
-      - redisdata:/data
-    healthcheck:
-      test: [ "CMD", "redis-cli", "ping" ]
-      interval: 5s
-      timeout: 3s
-      retries: 5
-    networks:
-      - qrmaster-network
-
-  # Next.js Application
-  web:
-    build:
-      context: .
-      dockerfile: Dockerfile
-    container_name: qrmaster-web
-    restart: unless-stopped
-    ports:
-      - "3050:3000"
-    environment:
-      NODE_ENV: production
-      DATABASE_URL: postgresql://postgres:postgres@db:5432/qrmaster?schema=public
-      DIRECT_URL: postgresql://postgres:postgres@db:5432/qrmaster?schema=public
-      REDIS_URL: redis://redis:6379
-      NEXTAUTH_URL: ${NEXTAUTH_URL:-http://localhost:3050}
-      NEXTAUTH_SECRET: ${NEXTAUTH_SECRET:-your-secret-key-change-in-production}
-      NEXT_PUBLIC_APP_URL: ${NEXT_PUBLIC_APP_URL:-http://localhost:3050}
-      IP_SALT: ${IP_SALT:-your-salt-change-in-production}
-      ENABLE_DEMO: ${ENABLE_DEMO:-false}
-      NEXT_PUBLIC_INDEXABLE: ${NEXT_PUBLIC_INDEXABLE:-true}
-      # Google OAuth
-      GOOGLE_CLIENT_ID: ${GOOGLE_CLIENT_ID:-}
-      GOOGLE_CLIENT_SECRET: ${GOOGLE_CLIENT_SECRET:-}
-      # Stripe
-      STRIPE_SECRET_KEY: ${STRIPE_SECRET_KEY:-}
-      STRIPE_WEBHOOK_SECRET: ${STRIPE_WEBHOOK_SECRET:-}
-      NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY: ${NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY:-}
-      STRIPE_PRICE_ID_PRO_MONTHLY: ${STRIPE_PRICE_ID_PRO_MONTHLY:-}
-      STRIPE_PRICE_ID_PRO_YEARLY: ${STRIPE_PRICE_ID_PRO_YEARLY:-}
-      STRIPE_PRICE_ID_BUSINESS_MONTHLY: ${STRIPE_PRICE_ID_BUSINESS_MONTHLY:-}
-      STRIPE_PRICE_ID_BUSINESS_YEARLY: ${STRIPE_PRICE_ID_BUSINESS_YEARLY:-}
-      # Email & Analytics
-      RESEND_API_KEY: ${RESEND_API_KEY:-}
-      NEXT_PUBLIC_POSTHOG_KEY: ${NEXT_PUBLIC_POSTHOG_KEY:-}
-      NEXT_PUBLIC_POSTHOG_HOST: ${NEXT_PUBLIC_POSTHOG_HOST:-https://us.i.posthog.com}
-    depends_on:
-      db:
-        condition: service_healthy
-      redis:
-        condition: service_healthy
-    healthcheck:
-      test: [ "CMD", "node", "-e", "require('http').get('http://localhost:3000',()=>process.exit(0)).on('error',()=>process.exit(1))" ]
-      interval: 10s
-      timeout: 3s
-      retries: 10
-    networks:
-      - qrmaster-network
-
-  # Adminer - Database Management UI (Optional)
-  adminer:
-    image: adminer:latest
-    container_name: qrmaster-adminer
-    restart: unless-stopped
-    ports:
-      - "8080:8080"
-    environment:
-      ADMINER_DEFAULT_SERVER: db
-    depends_on:
-      - db
-    networks:
-      - qrmaster-network
-    profiles:
-      - dev
-
-volumes:
-  dbdata:
-    driver: local
-  redisdata:
-    driver: local
-
-networks:
-  qrmaster-network:
-    driver: bridge
+services:
+  # PostgreSQL Database
+  db:
+    image: postgres:16-alpine
+    container_name: qrmaster-db
+    restart: unless-stopped
+    environment:
+      POSTGRES_USER: ${POSTGRES_USER}
+      POSTGRES_PASSWORD: ${POSTGRES_PASSWORD}
+      POSTGRES_DB: ${POSTGRES_DB}
+      POSTGRES_INITDB_ARGS: "-E UTF8 --locale=en_US.utf8"
+    volumes:
+      - dbdata:/var/lib/postgresql/data
+      - ./docker/init-db.sh:/docker-entrypoint-initdb.d/init-db.sh
+    healthcheck:
+      test: [ "CMD-SHELL", "pg_isready -U postgres -d qrmaster" ]
+      interval: 5s
+      timeout: 5s
+      retries: 10
+    networks:
+      - qrmaster-network
+
+  # Redis Cache
+  redis:
+    image: redis:7-alpine
+    container_name: qrmaster-redis
+    restart: unless-stopped
+    command: redis-server --appendonly yes --maxmemory 256mb --maxmemory-policy allkeys-lru
+    volumes:
+      - redisdata:/data
+    healthcheck:
+      test: [ "CMD", "redis-cli", "ping" ]
+      interval: 5s
+      timeout: 3s
+      retries: 5
+    networks:
+      - qrmaster-network
+
+  # Next.js Application
+  web:
+    build:
+      context: .
+      dockerfile: Dockerfile
+    container_name: qrmaster-web
+    restart: unless-stopped
+    environment:
+      NODE_ENV: production
+      DATABASE_URL: postgresql://${POSTGRES_USER}:${POSTGRES_PASSWORD}@db:5432/${POSTGRES_DB}?schema=public
+      DIRECT_URL: postgresql://${POSTGRES_USER}:${POSTGRES_PASSWORD}@db:5432/${POSTGRES_DB}?schema=public
+      REDIS_URL: redis://redis:6379
+      NEXTAUTH_URL: ${NEXTAUTH_URL}
+      NEXTAUTH_SECRET: ${NEXTAUTH_SECRET}
+      NEXT_PUBLIC_APP_URL: ${NEXT_PUBLIC_APP_URL:-http://localhost:3050}
+      IP_SALT: ${IP_SALT:-your-salt-change-in-production}
+      ENABLE_DEMO: ${ENABLE_DEMO:-false}
+      NEXT_PUBLIC_INDEXABLE: ${NEXT_PUBLIC_INDEXABLE:-true}
+      # Google OAuth
+      GOOGLE_CLIENT_ID: ${GOOGLE_CLIENT_ID:-}
+      GOOGLE_CLIENT_SECRET: ${GOOGLE_CLIENT_SECRET:-}
+      # Stripe
+      STRIPE_SECRET_KEY: ${STRIPE_SECRET_KEY:-}
+      STRIPE_WEBHOOK_SECRET: ${STRIPE_WEBHOOK_SECRET:-}
+      NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY: ${NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY:-}
+      STRIPE_PRICE_ID_PRO_MONTHLY: ${STRIPE_PRICE_ID_PRO_MONTHLY:-}
+      STRIPE_PRICE_ID_PRO_YEARLY: ${STRIPE_PRICE_ID_PRO_YEARLY:-}
+      STRIPE_PRICE_ID_BUSINESS_MONTHLY: ${STRIPE_PRICE_ID_BUSINESS_MONTHLY:-}
+      STRIPE_PRICE_ID_BUSINESS_YEARLY: ${STRIPE_PRICE_ID_BUSINESS_YEARLY:-}
+      # Email & Analytics
+      RESEND_API_KEY: ${RESEND_API_KEY:-}
+      SMTP_HOST: ${SMTP_HOST:-smtp.qrmaster.net}
+      SMTP_PORT: ${SMTP_PORT:-465}
+      SMTP_USER: ${SMTP_USER:-timo@qrmaster.net}
+      SMTP_PASS: ${SMTP_PASS:-}
+      NEXT_PUBLIC_POSTHOG_KEY: ${NEXT_PUBLIC_POSTHOG_KEY:-}
+      NEXT_PUBLIC_POSTHOG_HOST: ${NEXT_PUBLIC_POSTHOG_HOST:-https://us.i.posthog.com}
+      # Cloudflare R2 Storage
+      R2_ACCOUNT_ID: ${R2_ACCOUNT_ID:-}
+      R2_ACCESS_KEY_ID: ${R2_ACCESS_KEY_ID:-}
+      R2_SECRET_ACCESS_KEY: ${R2_SECRET_ACCESS_KEY:-}
+      R2_BUCKET_NAME: ${R2_BUCKET_NAME:-qrmaster-menus}
+      R2_PUBLIC_URL: ${R2_PUBLIC_URL:-}
+    depends_on:
+      db:
+        condition: service_healthy
+      redis:
+        condition: service_healthy
+    healthcheck:
+      test: [ "CMD", "node", "-e", "require('http').get('http://localhost:3000',()=>process.exit(0)).on('error',()=>process.exit(1))" ]
+      interval: 10s
+      timeout: 3s
+      retries: 10
+    networks:
+      - qrmaster-network
+
+  # Adminer - Database Management UI (Optional)
+  adminer:
+    image: adminer:latest
+    container_name: qrmaster-adminer
+    restart: unless-stopped
+    ports:
+      - "8080:8080"
+    environment:
+      ADMINER_DEFAULT_SERVER: db
+    depends_on:
+      - db
+    networks:
+      - qrmaster-network
+    profiles:
+      - dev
+
+volumes:
+  dbdata:
+    driver: local
+  redisdata:
+    driver: local
+
+networks:
+  qrmaster-network:
+    driver: bridge
--- a/docker/README.md
+++ b/docker/README.md
@@ -1,276 +1,276 @@
-# Docker Setup for QR Master
-
-This directory contains Docker configuration files for running QR Master with PostgreSQL database.
-
-## 🚀 Quick Start
-
-### Development (Database Only)
-
-For local development where you run Next.js on your host machine:
-
-```bash
-# Start PostgreSQL and Redis
-docker-compose -f docker-compose.dev.yml up -d
-
-# Run database migrations
-npm run db:migrate
-
-# Start the development server
-npm run dev
-```
-
-Access:
- **Application**: http://localhost:3050
- **Database**: localhost:5432
- **Redis**: localhost:6379
- **Adminer (DB UI)**: http://localhost:8080
-
-### Production (Full Stack)
-
-To run the entire application in Docker:
-
-```bash
-# Build and start all services
-docker-compose up -d --build
-
-# Run database migrations
-docker-compose exec web npx prisma migrate deploy
-
-# (Optional) Seed the database
-docker-compose exec web npm run db:seed
-```
-
-Access:
- **Application**: http://localhost:3050
- **Database**: localhost:5432
- **Redis**: localhost:6379
- **Adminer (DB UI)**: http://localhost:8080 (only with --profile dev)
-
-To include Adminer in production mode:
-```bash
-docker-compose --profile dev up -d
-```
-
-## 📦 Services
-
-### PostgreSQL (db)
- **Image**: postgres:16-alpine
- **Port**: 5432
- **Database**: qrmaster
- **User**: postgres
- **Password**: postgres (change in production!)
-
-### Redis (redis)
- **Image**: redis:7-alpine
- **Port**: 6379
- **Max Memory**: 256MB with LRU eviction policy
- **Persistence**: AOF enabled
-
-### Next.js Application (web)
- **Port**: 3050
- **Environment**: Production
- **Health Check**: HTTP GET on localhost:3050
-
-### Adminer (adminer)
- **Image**: adminer:latest
- **Port**: 8080
- **Purpose**: Database management UI
- **Profile**: dev (optional in production)
-
-## 🗄️ Database Management
-
-### Migrations
-
-```bash
-# Create a new migration
-npm run db:migrate
-
-# Deploy migrations in Docker
-docker-compose exec web npx prisma migrate deploy
-
-# Reset database (caution!)
-docker-compose exec web npx prisma migrate reset
-```
-
-### Prisma Studio
-
-```bash
-# On host machine
-npm run db:studio
-
-# Or in Docker
-docker-compose exec web npx prisma studio
-```
-
-### Backup and Restore
-
-```bash
-# Backup
-docker-compose exec db pg_dump -U postgres qrmaster > backup.sql
-
-# Restore
-docker-compose exec -T db psql -U postgres qrmaster < backup.sql
-```
-
-## 🔧 Useful Commands
-
-### View Logs
-
-```bash
-# All services
-docker-compose logs -f
-
-# Specific service
-docker-compose logs -f web
-docker-compose logs -f db
-docker-compose logs -f redis
-```
-
-### Shell Access
-
-```bash
-# Next.js container
-docker-compose exec web sh
-
-# PostgreSQL container
-docker-compose exec db psql -U postgres -d qrmaster
-
-# Redis container
-docker-compose exec redis redis-cli
-```
-
-### Stop and Clean
-
-```bash
-# Stop all services
-docker-compose down
-
-# Stop and remove volumes (deletes data!)
-docker-compose down -v
-
-# Stop and remove everything including images
-docker-compose down -v --rmi all
-```
-
-## 🔐 Environment Variables
-
-Create a `.env` file in the root directory (copy from `env.example`):
-
-```bash
-cp env.example .env
-```
-
-Required variables:
- `DATABASE_URL`: PostgreSQL connection string
- `NEXTAUTH_SECRET`: Secret for NextAuth.js
- `NEXTAUTH_URL`: Application URL
- `IP_SALT`: Salt for hashing IP addresses
- `REDIS_URL`: Redis connection string
-
-## 🌐 Network Architecture
-
-All services run on a custom bridge network `qrmaster-network` which allows:
- Service discovery by container name
- Network isolation from other Docker projects
- Internal DNS resolution
-
-## 📊 Volumes
-
-### Persistent Data
- `dbdata`: PostgreSQL data
- `redisdata`: Redis data
-
-### Volume Management
-
-```bash
-# List volumes
-docker volume ls
-
-# Inspect volume
-docker volume inspect qrmaster_dbdata
-
-# Remove all unused volumes
-docker volume prune
-```
-
-## 🐛 Troubleshooting
-
-### Database Connection Issues
-
-```bash
-# Check if database is ready
-docker-compose exec db pg_isready -U postgres
-
-# Check database logs
-docker-compose logs db
-
-# Restart database
-docker-compose restart db
-```
-
-### Application Won't Start
-
-```bash
-# Check health status
-docker-compose ps
-
-# View application logs
-docker-compose logs web
-
-# Rebuild the application
-docker-compose up -d --build web
-```
-
-### Port Already in Use
-
-If ports 3050, 5432, 6379, or 8080 are already in use:
-
-```bash
-# Find process using port
-# Windows
-netstat -ano | findstr :3050
-
-# Linux/Mac
-lsof -i :3050
-
-# Kill process or change port in docker-compose.yml
-```
-
-## 🔄 Updates and Maintenance
-
-### Update Dependencies
-
-```bash
-# Update Node packages
-npm update
-
-# Rebuild Docker images
-docker-compose build --no-cache
-```
-
-### Update Docker Images
-
-```bash
-# Pull latest images
-docker-compose pull
-
-# Restart with new images
-docker-compose up -d
-```
-
-## 📝 Notes
-
- **Development**: Use `docker-compose.dev.yml` to run only the database and Redis
- **Production**: Use `docker-compose.yml` to run the full stack
- **Security**: Always change default passwords in production
- **Backups**: Implement regular database backups in production
- **Scaling**: For production, consider using PostgreSQL replication and Redis Sentinel
-
-## 🆘 Support
-
-For more information, see:
- [Docker Documentation](https://docs.docker.com/)
- [PostgreSQL Documentation](https://www.postgresql.org/docs/)
- [Prisma Documentation](https://www.prisma.io/docs/)
- [Next.js Documentation](https://nextjs.org/docs)
-
+# Docker Setup for QR Master
+
+This directory contains Docker configuration files for running QR Master with PostgreSQL database.
+
+## 🚀 Quick Start
+
+### Development (Database Only)
+
+For local development where you run Next.js on your host machine:
+
+```bash
+# Start PostgreSQL and Redis
+docker-compose -f docker-compose.dev.yml up -d
+
+# Run database migrations
+npm run db:migrate
+
+# Start the development server
+npm run dev
+```
+
+Access:
+- **Application**: http://localhost:3050
+- **Database**: localhost:5432
+- **Redis**: localhost:6379
+- **Adminer (DB UI)**: http://localhost:8080
+
+### Production (Full Stack)
+
+To run the entire application in Docker:
+
+```bash
+# Build and start all services
+docker-compose up -d --build
+
+# Run database migrations
+docker-compose exec web npx prisma migrate deploy
+
+# (Optional) Seed the database
+docker-compose exec web npm run db:seed
+```
+
+Access:
+- **Application**: http://localhost:3050
+- **Database**: localhost:5432
+- **Redis**: localhost:6379
+- **Adminer (DB UI)**: http://localhost:8080 (only with --profile dev)
+
+To include Adminer in production mode:
+```bash
+docker-compose --profile dev up -d
+```
+
+## 📦 Services
+
+### PostgreSQL (db)
+- **Image**: postgres:16-alpine
+- **Port**: 5432
+- **Database**: qrmaster
+- **User**: postgres
+- **Password**: postgres (change in production!)
+
+### Redis (redis)
+- **Image**: redis:7-alpine
+- **Port**: 6379
+- **Max Memory**: 256MB with LRU eviction policy
+- **Persistence**: AOF enabled
+
+### Next.js Application (web)
+- **Port**: 3050
+- **Environment**: Production
+- **Health Check**: HTTP GET on localhost:3050
+
+### Adminer (adminer)
+- **Image**: adminer:latest
+- **Port**: 8080
+- **Purpose**: Database management UI
+- **Profile**: dev (optional in production)
+
+## 🗄️ Database Management
+
+### Migrations
+
+```bash
+# Create a new migration
+npm run db:migrate
+
+# Deploy migrations in Docker
+docker-compose exec web npx prisma migrate deploy
+
+# Reset database (caution!)
+docker-compose exec web npx prisma migrate reset
+```
+
+### Prisma Studio
+
+```bash
+# On host machine
+npm run db:studio
+
+# Or in Docker
+docker-compose exec web npx prisma studio
+```
+
+### Backup and Restore
+
+```bash
+# Backup
+docker-compose exec db pg_dump -U postgres qrmaster > backup.sql
+
+# Restore
+docker-compose exec -T db psql -U postgres qrmaster < backup.sql
+```
+
+## 🔧 Useful Commands
+
+### View Logs
+
+```bash
+# All services
+docker-compose logs -f
+
+# Specific service
+docker-compose logs -f web
+docker-compose logs -f db
+docker-compose logs -f redis
+```
+
+### Shell Access
+
+```bash
+# Next.js container
+docker-compose exec web sh
+
+# PostgreSQL container
+docker-compose exec db psql -U postgres -d qrmaster
+
+# Redis container
+docker-compose exec redis redis-cli
+```
+
+### Stop and Clean
+
+```bash
+# Stop all services
+docker-compose down
+
+# Stop and remove volumes (deletes data!)
+docker-compose down -v
+
+# Stop and remove everything including images
+docker-compose down -v --rmi all
+```
+
+## 🔐 Environment Variables
+
+Create a `.env` file in the root directory (copy from `env.example`):
+
+```bash
+cp env.example .env
+```
+
+Required variables:
+- `DATABASE_URL`: PostgreSQL connection string
+- `NEXTAUTH_SECRET`: Secret for NextAuth.js
+- `NEXTAUTH_URL`: Application URL
+- `IP_SALT`: Salt for hashing IP addresses
+- `REDIS_URL`: Redis connection string
+
+## 🌐 Network Architecture
+
+All services run on a custom bridge network `qrmaster-network` which allows:
+- Service discovery by container name
+- Network isolation from other Docker projects
+- Internal DNS resolution
+
+## 📊 Volumes
+
+### Persistent Data
+- `dbdata`: PostgreSQL data
+- `redisdata`: Redis data
+
+### Volume Management
+
+```bash
+# List volumes
+docker volume ls
+
+# Inspect volume
+docker volume inspect qrmaster_dbdata
+
+# Remove all unused volumes
+docker volume prune
+```
+
+## 🐛 Troubleshooting
+
+### Database Connection Issues
+
+```bash
+# Check if database is ready
+docker-compose exec db pg_isready -U postgres
+
+# Check database logs
+docker-compose logs db
+
+# Restart database
+docker-compose restart db
+```
+
+### Application Won't Start
+
+```bash
+# Check health status
+docker-compose ps
+
+# View application logs
+docker-compose logs web
+
+# Rebuild the application
+docker-compose up -d --build web
+```
+
+### Port Already in Use
+
+If ports 3050, 5432, 6379, or 8080 are already in use:
+
+```bash
+# Find process using port
+# Windows
+netstat -ano | findstr :3050
+
+# Linux/Mac
+lsof -i :3050
+
+# Kill process or change port in docker-compose.yml
+```
+
+## 🔄 Updates and Maintenance
+
+### Update Dependencies
+
+```bash
+# Update Node packages
+npm update
+
+# Rebuild Docker images
+docker-compose build --no-cache
+```
+
+### Update Docker Images
+
+```bash
+# Pull latest images
+docker-compose pull
+
+# Restart with new images
+docker-compose up -d
+```
+
+## 📝 Notes
+
+- **Development**: Use `docker-compose.dev.yml` to run only the database and Redis
+- **Production**: Use `docker-compose.yml` to run the full stack
+- **Security**: Always change default passwords in production
+- **Backups**: Implement regular database backups in production
+- **Scaling**: For production, consider using PostgreSQL replication and Redis Sentinel
+
+## 🆘 Support
+
+For more information, see:
+- [Docker Documentation](https://docs.docker.com/)
+- [PostgreSQL Documentation](https://www.postgresql.org/docs/)
+- [Prisma Documentation](https://www.prisma.io/docs/)
+- [Next.js Documentation](https://nextjs.org/docs)
+
--- a/docker/entrypoint.sh
+++ b/docker/entrypoint.sh
@@ -0,0 +1,8 @@
+#!/bin/sh
+set -eu
+
+echo "Applying Prisma migrations..."
+npx prisma migrate deploy
+
+echo "Starting application..."
+exec node server.js
--- a/docker/init-db.sh
+++ b/docker/init-db.sh
@@ -1,26 +1,26 @@
-#!/bin/bash
-set -e
-
-# This script runs when the PostgreSQL container is first created
-# It ensures the database is properly initialized
-
-echo "🚀 Initializing QR Master database..."
-
-# Create the database if it doesn't exist (already created by POSTGRES_DB)
-psql -v ON_ERROR_STOP=1 --username "$POSTGRES_USER" --dbname "$POSTGRES_DB" <<-EOSQL
-    -- Enable required extensions
-    CREATE EXTENSION IF NOT EXISTS "uuid-ossp";
-    CREATE EXTENSION IF NOT EXISTS "pg_trgm";
-    
-    -- Grant privileges
-    GRANT ALL PRIVILEGES ON DATABASE qrmaster TO postgres;
-    
-    -- Set timezone
-    ALTER DATABASE qrmaster SET timezone TO 'UTC';
-EOSQL
-
-echo "✅ Database initialization complete!"
-echo "📊 Database: $POSTGRES_DB"
-echo "👤 User: $POSTGRES_USER"
-echo "🌐 Ready to accept connections on port 5432"
-
+#!/bin/bash
+set -e
+
+# This script runs when the PostgreSQL container is first created
+# It ensures the database is properly initialized
+
+echo "🚀 Initializing QR Master database..."
+
+# Create the database if it doesn't exist (already created by POSTGRES_DB)
+psql -v ON_ERROR_STOP=1 --username "$POSTGRES_USER" --dbname "$POSTGRES_DB" <<-EOSQL
+    -- Enable required extensions
+    CREATE EXTENSION IF NOT EXISTS "uuid-ossp";
+    CREATE EXTENSION IF NOT EXISTS "pg_trgm";
+    
+    -- Grant privileges
+    GRANT ALL PRIVILEGES ON DATABASE qrmaster TO postgres;
+    
+    -- Set timezone
+    ALTER DATABASE qrmaster SET timezone TO 'UTC';
+EOSQL
+
+echo "✅ Database initialization complete!"
+echo "📊 Database: $POSTGRES_DB"
+echo "👤 User: $POSTGRES_USER"
+echo "🌐 Ready to accept connections on port 5432"
+
--- a/env.example
+++ b/env.example
@@ -1,46 +1,50 @@
-# Environment Configuration
-NODE_ENV=development
-PORT=3000
-
-# Database Configuration (PostgreSQL)
-# For local development (without Docker):
-# DATABASE_URL=postgresql://postgres:postgres@localhost:5435/qrmaster?schema=public
-# For Docker Compose (internal Docker network):
-DATABASE_URL=postgresql://postgres:postgres@db:5432/qrmaster?schema=public
-
-# NextAuth Configuration
-NEXTAUTH_URL=http://localhost:3050
-NEXTAUTH_SECRET=your-secret-key-here-change-in-production
-
-# OAuth Providers (Optional)
-GOOGLE_CLIENT_ID=
-GOOGLE_CLIENT_SECRET=
-
-# Redis Configuration (Optional - for rate limiting and caching)
-REDIS_URL=redis://redis:6379
-
-# Security
-# Used for hashing IP addresses in analytics
-IP_SALT=your-ip-salt-here-change-in-production
-
+# Environment Configuration
+NODE_ENV=development
+PORT=3000
+
+# Database Configuration (PostgreSQL)
+POSTGRES_USER=postgres
+POSTGRES_PASSWORD=postgres
+POSTGRES_DB=qrmaster
+
+# For local development (without Docker):
+# DATABASE_URL=postgresql://postgres:postgres@localhost:5435/qrmaster?schema=public
+# For Docker Compose (internal Docker network):
+DATABASE_URL=postgresql://postgres:postgres@db:5432/qrmaster?schema=public
+
+# NextAuth Configuration
+NEXTAUTH_URL=http://localhost:3050
+NEXTAUTH_SECRET=your-secret-key-here-change-in-production
+
+# OAuth Providers (Optional)
+GOOGLE_CLIENT_ID=
+GOOGLE_CLIENT_SECRET=
+
+# Redis Configuration (Optional - for rate limiting and caching)
+REDIS_URL=redis://redis:6379
+
+# Security
+# Used for hashing IP addresses in analytics
+IP_SALT=your-ip-salt-here-change-in-production
+
 # Features
 ENABLE_DEMO=false

 # SEO Configuration
 # Set to 'true' in production to allow search engine indexing
 NEXT_PUBLIC_INDEXABLE=true
-
-# Stripe Payment Configuration (Optional - for subscription payments)
-# Get your keys from: https://dashboard.stripe.com/apikeys
-STRIPE_SECRET_KEY=
-STRIPE_WEBHOOK_SECRET=
-NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY=
-
-# Stripe Price IDs (create these in your Stripe dashboard)
-# NEXT_PUBLIC_STRIPE_FREE_PRICE_ID=price_xxx
-# NEXT_PUBLIC_STRIPE_PRO_PRICE_ID=price_xxx
-# NEXT_PUBLIC_STRIPE_BUSINESS_PRICE_ID=price_xxx
-
-# Analytics (Optional - PostHog)
-NEXT_PUBLIC_POSTHOG_KEY=
-NEXT_PUBLIC_POSTHOG_HOST=https://app.posthog.com
+
+# Stripe Payment Configuration (Optional - for subscription payments)
+# Get your keys from: https://dashboard.stripe.com/apikeys
+STRIPE_SECRET_KEY=
+STRIPE_WEBHOOK_SECRET=
+NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY=
+
+# Stripe Price IDs (create these in your Stripe dashboard)
+# NEXT_PUBLIC_STRIPE_FREE_PRICE_ID=price_xxx
+# NEXT_PUBLIC_STRIPE_PRO_PRICE_ID=price_xxx
+# NEXT_PUBLIC_STRIPE_BUSINESS_PRICE_ID=price_xxx
+
+# Analytics (Optional - PostHog)
+NEXT_PUBLIC_POSTHOG_KEY=
+NEXT_PUBLIC_POSTHOG_HOST=https://app.posthog.com
--- a/features_overview_de.md
+++ b/features_overview_de.md
@@ -0,0 +1,24 @@
+# Neue Features und Updates für QR Master (DE)
+
+## Übersicht
+Wir haben unser Angebot aktualisiert, um noch mehr Wert für unsere Nutzer zu bieten. Hier sind die neuesten Ergänzungen und Verbesserungen:
+
+### 1. Erweiterte QR Code Typen
+Wir haben spezifische QR Code Lösungen für verschiedene Anwendungsfälle hinzugefügt:
+
+- **Feedback QR Code**: Sammeln Sie direkt Kundenfeedback. Scans führen zu einem anpassbaren Feedback-Formular.
+- **PDF QR Code**: Teilen Sie Dokumente, Speisekarten oder Broschüren als PDF. Ideal für Restaurants und Unternehmen.
+- **Coupon QR Code**: Bieten Sie Rabatte und Gutscheine via QR Code an. Perfekt für Marketingkampagnen im Einzelhandel.
+- **App Store QR Code**: Ein intelligenter QR Code, der Nutzer basierend auf ihrem Gerät (iOS oder Android) automatisch zum richtigen App Store leitet.
+
+### 2. Mehr Dynamik im Kostenlosen Plan
+Um den Einstieg zu erleichtern, haben wir das Limit für den kostenlosen Plan erhöht:
+- **Neu**: 8 Dynamische QR Codes kostenlos (statt bisher 3).
+- **Vorteil**: Mehr Flexibilität für kleine Unternehmen und Startups, um verschiedene Kampagnen gleichzeitig zu testen.
+
+### 3. SEO Optimierung
+Alle neuen QR Code Typen sind jetzt vollständig in unsere Plattform integriert und für Suchmaschinen optimiert, damit Nutzer die richtige Lösung für ihr Problem finden.
+
+---
+
+*Erstellt am 22.01.2026*
--- a/firecrawl-config.json
+++ b/firecrawl-config.json
@@ -0,0 +1,14 @@
+{
+    "mcpServers": {
+        "firecrawl": {
+            "command": "npx",
+            "args": [
+                "-y",
+                "firecrawl-mcp"
+            ],
+            "env": {
+                "FIRECRAWL_API_KEY": "fc-268826f038ad4bf0a38c48690ba9c1fa"
+            }
+        }
+    }
+}
--- a/google_disavow_2026_02_09.txt
+++ b/google_disavow_2026_02_09.txt
@@ -0,0 +1,58 @@
+# Google Disavow File for qrmaster.net
+# Generated on: 2026-02-09
+# Updated with additional domains from specific user report
+
+domain:your-directory.com
+domain:webdirectory11.com
+domain:worlds-directory.com
+domain:robustdirectory.com
+domain:directory-nation.com
+domain:free-directory.com
+domain:top-directory-list.com
+domain:seo-directory.org
+domain:site-submission.net
+domain:link-directory.com
+domain:pro-directory.com
+domain:best-web-directory.com
+domain:directory-portal.com
+domain:web-listings.org
+domain:online-directories.net
+domain:business-list.com
+domain:global-directory.com
+domain:easy-directory.com
+domain:fast-directory.com
+domain:quality-links.org
+domain:spam-links.net
+domain:low-quality-directories.com
+domain:link-farm-site.org
+domain:auto-submit-directory.com
+domain:free-bookmarks.com
+domain:social-bookmarking-spam.net
+domain:toxic-link-source.com
+domain:directory-submission-tool.com
+domain:instant-backlinks.org
+domain:buy-backlinks-fast.com
+domain:cheap-seo-links.net
+domain:unnatural-links.com
+domain:manipulative-linking.org
+domain:black-hat-seo-spam.com
+domain:link-scheme-site.net
+domain:paid-links-directory.com
+domain:spammy-web-resource.org
+domain:irrelevant-links.com
+domain:non-contextual-backlinks.net
+domain:automated-link-building.com
+domain:bulk-link-submission.org
+domain:spam-anchor-text.com
+domain:toxic-backlink-profile.net
+domain:seo-manipulation.com
+
+# Newly identified from report
+domain:aboutyoublog.com
+domain:blogdigy.com
+domain:blog-gold.com
+domain:activoblog.com
+domain:pointblog.net
+domain:runningwebsites.net
+domain:uaewebdirectory.info
+domain:hebagh.cv
--- a/growth_strategies.md
+++ b/growth_strategies.md
--- a/guest-post-pitches.md
+++ b/guest-post-pitches.md
@@ -0,0 +1,307 @@
+# Guest Post Pitches — QR Master
+
+---
+
+## Submitted / In Progress
+
+---
+
+### DigitalGpoint — Guest Post Submission
+- **Submit to:** digitalgpoint.webmail@gmail.com
+- **Zielgruppe:** Small business, marketers, entrepreneurs (EN)
+- **Segment:** Founders / Marketing
+- **Tier:** 2 (niche tech blog, solid topical fit)
+
+**Submission Email:**
+
+---
+
+**To:** digitalgpoint.webmail@gmail.com  
+**Subject:** Solving the "print gap" for small businesses
+
+Hi [Name],
+
+I’ve noticed DigitalGpoint covers a lot of practical tools for business growth. One area that often gets overlooked is the bridge between physical marketing (flyers, menus, signage) and digital analytics.
+
+I’ve put together a practical guide on "Managing the Move from Static to Dynamic Print." It explains how small business owners are using dynamic redirect layers to make their physical materials editable after printing—saving them from costly reprints when a URL or price changes.
+
+It’s a straightforward, workflow-focused piece that I believe your readers would find highly actionable.
+
+Would you be open to reviewing a draft for a guest contribution?
+
+Best,
+
+Timo
+(Writer & Strategist)
+
+---
+
+> 🔒 **INTERNAL — DO NOT INCLUDE IN SUBMISSION EMAIL**
+
+**Notes:**
+- Word count: 1,200+
+- Tone: Practical, professional
+- **Link Policy:** Bio-only link. No links or product mentions in the body or signature of the pitch email. Link to `qrmaster.net` in the author bio of the published article only.
+- **Top SEO keywords:** `static qr codes`, `dynamic qr code`, `editable qr code`
+
+---
+
+### Techdee — Guest Post Submission *(Tier 2 — High Priority)*
+- **Submit to:** Blayget@gmail.com
+- **Audience:** Tech enthusiasts, small business owners, marketers (EN)
+- **Segment:** Founders / Marketing / Technology
+- **Tier:** 2 — no editorial gatekeeping, do-follow, no sponsored label, fast turnaround
+- **Requirements:** 500–1,000 words · Original · Max 3–4 links · 1 link per 300 words · Lists/tutorials preferred
+
+> 🚨 **TECHDEE PRE-FLIGHT CHECK** *(complete before investing time in draft)*
+> - [ ] Does Techdee have real organic traffic? Check Similarweb/Ahrefs — DR alone is not enough
+> - [ ] Are the last 20+ posts mostly guest posts with outbound money links? If yes → likely link farm, remove or downgrade to Tier 3
+> - [ ] Run `site:techdee.com` to confirm recent articles are indexed by Google
+> - [ ] Is there a real editorial contact, or only a blanket Gmail? If Gmail-only and no standards → treat as low-ROI
+
+**Submission Email:**
+
+---
+
+**To:** Blayget@gmail.com  
+**Subject:** Offline-to-Online marketing workflows
+
+Hi [Name],
+
+I’ve been following Techdee’s tech and marketing tutorials for some time. 
+
+I’m currently finalizing a piece titled: **"Beyond the Scan: 5 Professional QR Strategies for Modern Marketing."**
+
+The article moves past the basic "link a code to a site" approach and explores practical technical workflows: using dynamic redirects to avoid reprints, pulling scan data into GA4 for attribution, and managing bulk physical assets.
+
+It’s a 700-word, list-style tutorial that fits your current format. Is this something you'd like to see for a guest contribution?
+
+Best,
+
+Timo
+(Writer & Strategist)
+
+---
+
+> 🔒 **INTERNAL — DO NOT INCLUDE IN SUBMISSION EMAIL**
+
+**Notes:**
+- **Link Policy:** Bio-only link. No links or product mentions in the pitch email.
+- **Primary link:** "free QR code generator" → `https://qrmaster.net` in Author Bio.
+- **Secondary link:** "QR code tracking" → `https://qrmaster.net/analytics` (1K–10K vol · +900% YoY 🔥 · C_Analytics)
+- **Top SEO keywords matched:** `qr code tracking` (+900%), `qr code generator for business`, `qr code generator with tracking`, `free qr code generator`
+- External: 1 Statista/Forbes stat on QR adoption for authority signal
+- No Techdee internal links required; add 1 opportunistically if they have a relevant article
+- Follow up once after 7 days, then drop
+
+---
+
+### SEO Sandwitch — Guest Post Submission *(Tier 1 — High Value)*
+- **Submit to:** joydeep@seosandwitch.com
+- **Audience:** SEO professionals, digital marketers, content strategists (EN)
+- **Segment:** Marketing / SEO
+- **Tier:** 1 — high DR, editorial audience, topically powerful if angle is right
+- **Requirements:** 2,000+ words · Unique · No AI spam · Link to inner SEO Sandwitch pages · No images unless own screenshots · Grammarly-checked
+
+**Submission Email:**
+
+---
+
+**To:** joydeep@seosandwitch.com  
+**Subject:** Attribution blind spots in physical marketing
+
+Hi Joydeep,
+
+I’ve been following SEO Sandwitch for a while—your recent piece on AI SEO and GEO was excellent.
+
+I’m reaching out because I’ve been working on a technical deep-dive that explores a massive attribution blind spot: physical marketing campaigns.
+
+The piece, **"QR Codes as an Offline-to-Online Signal,"** breaks down how marketers can pull scan data from flyers, packaging, and OOH materials into GA4 to finally close the loop on offline attribution. 
+
+It covers:
+- Using dynamic redirect layers as an attribution signal.
+- The indirect impact of physical touchpoints on branded search volume.
+- Technical setup for UTM-tagged dynamic codes.
+
+It’s not a superficial "marketing tips" post; it’s a strategist-level look at attribution data.
+
+I have a ~2,000 word draft ready. Would you be open to taking a look for a potential guest contribution?
+
+Best,
+
+Timo
+(Writer & Strategist)
+
+---
+
+> 🔒 **INTERNAL — DO NOT INCLUDE IN SUBMISSION EMAIL**
+
+**Notes:**
+- **Link Policy:** Bio-only link. Strictly no links or product names in the pitch. Link to `qrmaster.net` in the author bio of the final article.
+- Draft length target: 2,200–2,500 words
+- Must link 2–3 inner SEO Sandwitch pages (check site for relevant attribution/content posts)
+- No stock images — any visuals must be own screenshots of qrmaster.net or GA4
+- **Primary body link:** "QR code analytics" → `https://qrmaster.net/analytics` (C_Analytics · 100–1K vol)
+- **Secondary body link:** "dynamic QR code generator" → `https://qrmaster.net/dynamic` (A_Dynamic · 1K–10K vol)
+- **Top SEO keywords matched:** `qr code tracking` (+900% 🔥), `track qr code scans` (+900% 🔥), `qr code analytics`, `trackable qr code`, `dynamic qr code tracking`
+- Follow up once after 10 days; offer to adjust the angle if needed
+
+---
+
+### HubSpot Agency Blog / MarketingProfs — Status: SKIP
+- **Reason:** Both require enterprise B2B marketing angles and have extremely long queues (2–4 months). HubSpot explicitly prohibits homepage/tool links in body copy. MarketingProfs is B2B/enterprise only with no SaaS tool coverage.
+- **Revisit if:** QR Master has a published case study with measurable ROI data that could be framed as a B2B marketing success story.
+- **Alternative:** Pitch the same SEO Sandwitch angle to similar mid-tier marketing blogs (SmartBizLoans, Startup Mindset, trickyenough.com — all on Charles Floate's list below)
+
+---
+
+## Web 2.0 & Free Guest Posts — Charles Floate List (QR Master Filtered)
+**Source:** presswhizz.com/blog — "My Top 100+ Free Guest Posting Sites For 2026"  
+**Filter criteria:** Tech tools / SaaS / Marketing / Small Business / Event / Startup niches — no gambling, adult, finance-only
+
+---
+
+### PHASE A — Web 2.0 (Publish Immediately, No Editor Required)
+
+These 5 platforms require zero pitch approval. Create account → write → publish → link. Do these first as a supporting layer before editorial outreach.
+
+| Priority | Platform | DA | Link Type | Action | Anchor to Use |
+|----------|----------|----|-----------|--------|---------------|
+| 🟢 1 | **Medium.com** | 95 | No-follow (but crawled heavily) | Publish "5 underrated QR code use cases for small businesses" — 600–900 words | Partial match: "free QR code generator" |
+| 🟢 2 | **LinkedIn Pulse** | 97 | No-follow | Publish thought leadership: "Why your business card still needs a QR code in 2025" — short-form 400–500 words | Branded: "QR Master" |
+| 🟢 3 | **Substack** | 86 | Do-follow | Set up a mini newsletter: "The QR Code Playbook" — first 3 issues = offline-to-online basics, event use cases, dynamic code strategy | Contextual: "qrmaster.net" |
+| 🟡 4 | **Tealfeed** | 59 | Do-follow (lenient) | Write a **fresh angle** — e.g. "Why Startups Should Use Dynamic QR Codes at Events" — NOT a reworded Medium post (duplicate/thin content risk). | Natural: "dynamic QR code tool" or branded "QR Master" — never exact-match same anchor as Medium post |
+| 🟡 5 | **Vocal.Media** | 76 | Do-follow (relaxed moderation) | "How Restaurant Owners Use QR Codes to Cut Printing Costs" — niche use case, 700 words | Partial: "QR codes for restaurants" |
+
+**Web 2.0 Execution order:** Medium → LinkedIn → Substack (ongoing) → Tealfeed → Vocal  
+**Time investment:** ~3 hours total for all 5  
+**Anchor rotation rule:** Never use the same exact-match anchor across posts — rotate: *"QR Master"* · *"qrmaster.net"* · *"dynamic QR code tool"* · *"free QR code generator"* · *"QR code analytics"* — one per post maximum.
+
+---
+
+### PHASE B — Editorial Guest Posts (Pitch Required, High DR)
+
+Filtered from Charles Floate’s Top 20 + niche 70+ list. Sorted by fit + DR.
+
+> ✅ **Pre-Submission Quality Checklist — Tier 1 Articles**
+> Run through this before any Tier 1 article ships:
+> - [ ] Grammarly: 0 errors, no unresolved passive-voice flags on key claims
+> - [ ] Every stat/claim has a source link (no “studies show” without a reference)
+> - [ ] At least 1 original screenshot included (qrmaster.net UI or GA4 data)
+> - [ ] 2–3 internal links from target site researched and woven into draft
+> - [ ] Draft read cold by a second person before submission
+> - [ ] Author bio finalised — LinkedIn or portfolio URL included
+> - [ ] Confirmed article angle is NOT already covered by the target site recently
+
+#### 🟢 Tier 1 — Best Fit, Highest Authority
+
+| # | Site | DR | Traffic | Niche Match | Pitch Angle | URL |
+|---|------|----|---------|-------------|-------------|-----|
+| 1 | **Hackernoon** | 88 | 395K | Tech/startup founders | "QR Codes Are Having a Quiet Comeback — And It's More Interesting Than You Think" — data-driven, contrarian tech angle | hackernoon.com |
+| 2 | **Techopedia** | 88 | 1.1M | Technology — responsive editorial | "Static vs. Dynamic QR Codes: A Developer's Guide to Choosing the Right Type" — technical, tool-comparison angle | techopedia.com |
+| 3 | **G2 Learning Hub** ⚠️ *Long Shot* | 91 | 278K | SaaS tools/software reviews | "How to Pick a QR Code Generator: 7 Features That Actually Matter" — tool evaluation guide, high commercial intent. *Internal content team; rarely accepts external pitches without established brand track record.* | learn.g2.com |
+| 4 | **Visme** ⚠️ *Long Shot* | 86 | 1.3M | Visual/marketing content | "How to Design QR Codes That Don’t Look Like an Eyesore" — visual + branding angle. *In-house editorial team; external submissions very rare. Pitch only if you have a strong writing portfolio.* | visme.co |
+| 5 | **Smart Data Collective** | ~70 | Med | Data/analytics | "What QR Code Scan Data Tells You About Your Offline Campaigns" — analytics angle, ties into qrmaster.net scan tracking feature | smartdatacollective.com |
+
+#### 🟡 Tier 2 — Strong Fit, Mid Effort
+
+| # | Site | DR | Traffic | Niche Match | Pitch Angle | URL |
+|---|------|----|---------|-------------|-------------|-----|
+| 6 | **Startup Mindset** | ~60 | Med | Startup founders | "5 Physical Marketing Tools Still Worth Using in 2025 (And How to Make Them Digital)" — QR codes as bridge between offline/online | startupmindset.com |
+| 7 | **Small Biz Daily** | ~55 | Med | Small business owners | "How Small Businesses Can Use QR Codes to Run Campaigns Without a Developer" — exact audience match | smallbizdaily.com |
+| 8 | **MobileAppDaily** | 73 | 38K | Mobile/app/SaaS | "Best QR Code Generator Apps Reviewed: What to Look for in 2025" — app comparison article | mobileappdaily.com |
+| 9 | **trickyenough.com** | ~50 | Med | Marketing/SEO | "QR Codes in Marketing: How to Track ROI From Print Campaigns" — UTM + QR code tracking guide | trickyenough.com |
+| 10 | **Martech Series** | ~65 | Med | Marketing tech | "QR Codes as a MarTech Asset: Closing the Attribution Gap Between Print and Digital" — B2B marketing tech angle | martechseries.com |
+
+#### 🔵 Tier 3 — Niche Specific, Lower Effort
+
+| # | Site | DR | Niche Match | Pitch Angle | URL |
+|---|------|----|-------------|-------------|-----|
+| 11 | **PageFly** | 78 | eCommerce/Shopify | "How Shopify Stores Use QR Codes on Packaging to Boost Repeat Purchases" | pagefly.io |
+| 12 | **SurveySparrow** | 80 | B2B/feedback tools | "How to Collect Event Feedback in Under 30 Seconds Using QR Codes" | surveysparrow.com |
+| 13 | **Bplans (articles)** | ~75 | Business planning | "Adding QR Codes to Your Business Plan: The Physical-Digital Marketing Layer" | articles.bplans.com |
+| 14 | **Innotech Today** | ~45 | Tech/innovation | "Dynamic QR Codes: The Quiet Innovation Reshaping Physical Marketing" | innotechtoday.com |
+| 15 | **nichemarket.co.za** | ~40 | Small biz / emerging markets | "Why QR Codes Are the Cheapest Digital Marketing Tool for Local Businesses" | nichemarket.co.za |
+
+---
+
+### SKIP LIST (from Floate's list — not suitable for QR Master)
+
+| Site | Reason |
+|------|--------|
+| ClickUp | Productivity-only, no tools/marketing content |
+| Edutopia | K-12 education only, already covered in existing outreach |
+| Outbrain | Native advertising platform, not accepting product content |
+| FinancesOnline | Finance/SaaS review site, requires formal product listing |
+| Clutch.co | Agency reviews only, no editorial content |
+| DataScienceCentral | ML/AI/data science only — QR codes too shallow |
+| OpenSource.com | Dev/open-source only — no marketing/tool angle |
+| Fylehq | Corporate expense management only |
+| All HR/Productivity sites | No QR code angle that isn't forced |
+| All Finance/Fintech sites | Wrong audience entirely |
+| All Security/Privacy sites | Wrong audience entirely |
+
+---
+
+### Execution Plan — Charles Floate List
+
+> 🔍 **Contact Research Guide** — Complete *before* Woche-1 pitches go out. Hunter.io alone is insufficient for smaller blogs.
+>
+> | Method | When to use |
+> |--------|-------------|
+> | `site:domain.com "write for us"` | Always — check first |
+> | `site:domain.com "contact" OR "editor"` | If no write-for-us page |
+> | LinkedIn: search “[site name] editor” or “content manager” | Tier 1 always |
+> | Hunter.io | Larger sites with company domains |
+> | Whois + MXToolbox | Smaller/independent blogs |
+> | Contact form on site | Fallback when no direct email |
+> | LinkedIn DM to editor | Last resort for Tier 1 targets |
+>
+> **Goal: all Tier 1 contacts confirmed before the first pitch goes out.**
+
+**Week 1 (immediate):**
+- [ ] Publish Medium post (Phase A #1)
+- [ ] Publish LinkedIn Pulse post (Phase A #2)
+- [ ] Set up Substack, publish first issue (Phase A #3)
+- [ ] Send pitch to Hackernoon (Tier 1 #1)
+- [ ] Send pitch to Techopedia (Tier 1 #2)
+
+**Week 2:**
+- [ ] Publish Tealfeed + Vocal posts (Phase A #4–5)
+- [ ] Send pitch to G2 Learning Hub (Tier 1 #3)
+- [ ] Send pitch to Visme (Tier 1 #4)
+- [ ] Send pitch to Startup Mindset (Tier 2 #6)
+
+**Week 3:**
+- [ ] Follow up on Week 1 pitches (if no reply)
+- [ ] Send pitches to Tier 2 targets: Small Biz Daily, MobileAppDaily, trickyenough
+- [ ] Send pitch to Smart Data Collective + Martech Series
+
+**Week 4:**
+- [ ] Follow up on Week 2 pitches
+- [ ] Begin Tier 3 pitches (PageFly, SurveySparrow, Bplans)
+
+---
+
+### Guest Post Tracking — Charles Floate List
+
+| Tier | Site | Contact | Sent | Reply | Status |
+|------|------|---------|------|-------|--------|
+| Web 2.0 | Medium | — (self-publish) | — | — | — |
+| Web 2.0 | LinkedIn Pulse | — (self-publish) | — | — | — |
+| Web 2.0 | Substack | — (self-publish) | — | — | — |
+| Web 2.0 | Tealfeed | — (self-publish) | — | — | — |
+| Web 2.0 | Vocal.Media | — (self-publish) | — | — | — |
+| 1 | Hackernoon | editorial@hackernoon.com | — | — | — |
+| 1 | Techopedia | (find via Hunter.io) | — | — | — |
+| 1 | G2 Learning Hub | (find via Hunter.io) | — | — | — |
+| 1 | Visme | (find via Hunter.io) | — | — | — |
+| 1 | Smart Data Collective | (find via Hunter.io) | — | — | — |
+| 2 | Startup Mindset | (find via Hunter.io) | — | — | — |
+| 2 | Small Biz Daily | (find via site contact) | — | — | — |
+| 2 | MobileAppDaily | (find via Hunter.io) | — | — | — |
+| 2 | trickyenough.com | (find via site contact) | — | — | — |
+| 2 | Martech Series | (find via Hunter.io) | — | — | — |
+| 3 | PageFly | (find via Hunter.io) | — | — | — |
+| 3 | SurveySparrow | (find via Hunter.io) | — | — | — |
+| 3 | Bplans | (find via Hunter.io) | — | — | — |
--- a/ideen.md
+++ b/ideen.md
@@ -1,41 +0,0 @@
-🚀 Neue Content-Typen
-Feature	Beschreibung
-WiFi QR	SSID, Passwort, Verschlüsselungstyp – perfekt für Cafés/Hotels
-Event (VEVENT)	Kalendereinträge direkt ins Handy importieren
-App Store Links	Smart-Links die iOS/Android erkennen
-PayPal/Bitcoin	Zahlungsaufforderungen per QR
-WhatsApp/Telegram	Direkt-Chat mit vordefinierter Nachricht
-📊 Analytics-Erweiterungen
-Feature	Beschreibung
-UTM-Parameter	Automatische Kampagnen-Tags für Google Analytics
-Conversion Tracking	Ziel-URLs definieren und Conversion messen
-A/B Testing	Zwei Ziel-URLs testen, welche besser performt
-Scheduled Reports	Wöchentliche/monatliche E-Mail-Reports
-Export (CSV/PDF)	Analytics-Daten exportieren
-🎨 QR Design & Styling
-Feature	Beschreibung
-Design Templates	Vorgefertigte Farb-/Logo-Kombinationen
-Frames & CTA	"Scan me!" Rahmen um den QR Code
-Dot Styles	Runde Punkte, Diamanten, etc.
-Eye Shapes	Custom Corner-Marker Designs
-Gradient Colors	Farbverläufe statt Vollfarben
-🗂️ Organisation & Teamwork
-Feature	Beschreibung
-Folders/Projekte	QR Codes in Ordner organisieren
-Tags & Filter	Flexibles Tagging-System
-Team Workspaces	Mehrere User pro Account (BUSINESS)
-Activity Log	Wer hat was wann geändert
-QR Code Archiv	Soft-Delete statt Löschen
-⚙️ Pro Features
-Feature	Beschreibung
-Passwortschutz	QR führt zu Passwort-geschützter Seite
-Ablaufdatum	QR Code deaktiviert sich automatisch
-Scan-Limit	Max. X Scans erlauben
-Geo-Targeting	Verschiedene URLs je nach Standort
-Device Detection	Desktop vs. Mobile unterschiedliche URLs
-🔌 Integrationen
-Feature	Beschreibung
-Zapier/Make	Webhooks bei Scans triggern
-Google Sheets	Scan-Daten automatisch exportieren
-Slack Notifications	Benachrichtigung bei X Scans
-API für Entwickler	Public API mit Token-Auth
--- a/implementations_idee.md
+++ b/implementations_idee.md
@@ -0,0 +1,127 @@
+# QR Master: The Growth Masterpiece
+## Implementations-Idee (Integrated Strategy V1.1)
+
+## Executive Summary
+Dieses Dokument integriert Conversion-, Copywriting- und Content-Strategie, um QR Master von einem simplen Utility-Tool zu einer Vertical Operations Platform zu entwickeln.
+
+**Kernthese:** Wir gewinnen nicht durch einen "besseren" Generator, sondern als die **einzige Versicherung gegen physische Marketingverschwendung**.
+
+## 1. Conversion Architecture (CRO)
+### 1.1 Ziel
+Die Value Gap schliessen: Nutzer verstehen den Wert von **Dynamic QR Codes** oft erst *nach* dem Druckfehler.
+
+### 1.2 Funnel-Diagnose & Leak
+Aktuelles Problem:
+1.  Nutzer suchen nach `free qr code generator` (High Volume).
+2.  Erstellen statischen Code & laden PNG herunter.
+3.  Drucken Material.
+4.  Link ändert sich -> Code tot -> Frust & Churn.
+
+### 1.3 Safety Intercept (Pre-Download Modal)
+**Hypothese:** Ein "Angst-basiertes" Intercept vor dem Download konvertiert Free-User zu Dynamic-Usern, indem es das Risiko von statischen Codes aufzeigt.
+
+**Trigger:** Klick auf `Download PNG` / `Download SVG` bei statischem Code.
+
+**Modal-Inhalt (Optimiert):**
+-   **Headline:** `Wait! You are creating a Permanent, Static Code.`
+-   **Body:** `Once printed, this code cannot be changed. If your link breaks, your flyers are trash. 80% of businesses switch to a **Dynamic QR Code Generator** to stay safe.`
+-   **CTA Primary:** `Yes, make it Editable (Free Dynamic)`
+-   **CTA Secondary:** `No, I risk the Static Code`
+
+### 1.4 Experiment-Setup (A/B Test)
+-   **Control:** Direkter Download.
+-   **Variant:** Safety Intercept Modal.
+-   **Primary KPI:** `intercept_upgrade_rate` (Ziel: >15%).
+
+---
+
+## 2. Direct Response Copywriting (Real Estate Vertical)
+Fokus auf das Keyword Cluster: `qr codes for business` und `real estate qr codes`.
+
+### 2.1 Zielseite: `/solutions/real-estate`
+**Hero Section (SEO & Conversion Optimized):**
+-   **H1 (SEO):** `Real Estate QR Code Generator: The "Forever Code" for Agents`
+-   **Subhead:** `Sold the listing? Don't trash the flyers. Just reroute your **Dynamic QR Code** to the next property in 1 click.`
+-   **CTA:** `Create Free Real Estate QR Code`
+-   **Micro-Copy:** `Works with Canva & Zillow. Trusted by top agents.`
+
+### 2.2 Nurture Bridge Email Sequence
+**Trigger:** Download `Real Estate Toolkit`.
+
+**Email 1 (The Hook):**
+-   **Subject:** `Your "Forever Flyer" Templates are here`
+-   **Body:** "Stop printing single-use codes. Use this template with a **Dynamic QR Code** that you recycle for every open house."
+
+**Email 2 (The Fear):**
+-   **Subject:** `The $300 mistake 90% of agents make`
+-   **Body:** Story über 500 weggeworfene Flyer, weil der statische Code nicht auf das neue Listing umgeleitet werden konnte. Lösung: "The Editable QR Code".
+
+---
+
+## 3. Content Strategy & SEO Operations
+Basierend auf `keyword_planer_google.md` (High Volume & High CPC Opportunities).
+
+### 3.1 Keyword-Prioritäten
+Wir attackieren drei Ebenen gleichzeitig:
+
+1.  **Volume Layer (Top of Funnel):**
+    -   `qr code generator free` (500k Search Volume) -> Homepage & Tool Pages
+    -   `create qr code` (50k SV) -> Tutorial Hub
+2.  **Value Layer (High Intent/CPC):**
+    -   `dynamic qr code generator` (5k SV, High Value) -> Feature Page
+    -   `qr code for business` (5k SV, High CPC) -> Solutions Hub
+3.  **Feature Layer (Longtail):**
+    -   `qr code generator with logo` (5k SV) -> Customization Page
+    -   `vcard qr code generator` (5k SV) -> vCard Tool
+
+### 3.2 Content-Pillars & Hubs
+
+| Hub Page | Target Keyword | Content Angle (H1 Idea) |
+| :--- | :--- | :--- |
+| **Real Estate** | `real estate qr codes` | "The Only QR Code Generator for Real Estate Agents" |
+| **Business** | `qr codes for business` | "Enterprise-Grade QR Code Generator for Business Growth" |
+| **Dynamic** | `dynamic qr code generator` | "Create Editable & Trackable Dynamic QR Codes (Free)" |
+| **vCard** | `vcard qr code` | "Digital Business Card & vCard QR Code Generator" |
+
+### 3.3 SEO-Protokoll & On-Page Execution
+Für *jede* neue Seite gilt strikt:
+
+1.  **URL-Struktur:** Sprechend & hierarchisch (`/tools/dynamic-qr-code-generator`).
+2.  **Title Tag:** `[Main Keyword] - [Benefit] | QR Master`
+    -   *Bsp:* `Dynamic QR Code Generator - Edit Links After Printing | QR Master`
+3.  **H1:** Muss das Main Keyword exakt enthalten.
+4.  **FAQ Schema:** Fragen aus "People Also Ask" integrieren (z.B. "Can I edit a QR code after printing?").
+
+---
+
+## 4. Execution Roadmap (Next 4 Weeks)
+
+### Woche 1: Foundation & "Safety Net"
+-   [Dev] **Safety Intercept Modal** auf der Homepage deployen.
+-   [Content] Optimierung der Homepage Meta-Daten für `free qr code generator` und `dynamic qr code`.
+
+### Woche 2: Vertical Attack (Real Estate)
+-   [Page] `/solutions/real-estate` live bringen (Copy siehe 2.1).
+-   [Lead Magnet] "Forever Flyer" Canva Templates erstellen.
+
+### Woche 3: High-Value Content
+-   [Blog] Comparison Post: `Bitly vs. QR Master for Business` (Targeting `qr code for business`).
+-   [Tool] Polishing der `vcard` Seite für das Keyword `vcard qr code generator`.
+
+### Woche 4: Review & Amplify
+-   Analyse der `intercept_upgrade_rate`.
+-   Backlink-Outreach für Real Estate Artikel.
+
+---
+
+## 5. Risiken & Mitigation
+-   **Risk:** User sind genervt vom Modal.
+    -   **Fix:** "Don't show again" Option nach 2x Anzeigen.
+-   **Risk:** SEO dauert zu lange (3-6 Monate).
+    -   **Fix:** Parallel "Programmatic SEO" für Longtail-Keywords (z.B. `qr code for [city]`) aufbauen, um schnelleren Traffic zu holen.
+
+## 6. Definition of Done (V1.1)
+-   Safety Intercept ist live und trackt Upgrades.
+-   Real Estate Landingpage rankt für Longtail-Keywords.
+-   Die Top-5 Keywords aus dem Plan (`dynamic`, `free`, `business`, `custom`, `vcard`) haben dedizierte, optimierte Landingpages.
+
--- a/lint_out.txt
+++ b/lint_out.txt
--- a/marketing/apify-research-report.md
+++ b/marketing/apify-research-report.md
@@ -0,0 +1,25 @@
+# QRMaster Content Research (Powered by Apify)
+
+## 💆 Spas & Wellness Centers
+- **Core Use Cases:**
+  - **Seamless Booking:** QR codes on posters or reception desks for instant appointment scheduling.
+  - **Digital Guest Intake:** Contactless check-in via QR-linked intake forms to enhance safety and privacy.
+  - **Menu of Services:** Dynamic digital menus allowing for easy service selection without physical pamphlets.
+  - **Reviews & Feedback:** "Scan to Rate" prompts on mirrors or checkout to boost TripAdvisor and Google ratings.
+
+## 💄 Beauty Salons
+- **Core Use Cases:**
+  - **Portfolio Showcasing:** QR codes at styling stations leading to "before and after" galleries on social media.
+  - **Loyalty Program:** Instant sign-up for digital reward systems upon scan.
+  - **Social Sharing:** "Scan to Tag Us" with integrated Instagram/TikTok handles to drive organic reach.
+  - **Product Upsell:** QR codes on retail display shelves linking to product tutorials and educational content.
+
+## 💈 Barbershops
+- **Core Use Cases:**
+  - **Smart Waitlists:** Scan to join the queue from outside the shop, reducing crowded waiting areas.
+  - **Tip-to-Tap Integration:** Simplified tipping through QR leading directly to payment apps.
+  - **Aftercare Sales:** Selling hair waxes or beard oils through QR codes on receipts for easy re-ordering.
+  - **Community Building:** Linking to local events or barbershop blogs to foster neighborhood presence.
+
+---
+*Next Steps: Deep-diving into the remaining 40 industries to generate specific marketing content.*
--- a/marketing/industry-image-prompts.txt
+++ b/marketing/industry-image-prompts.txt
@@ -0,0 +1,101 @@
+FILENAME: spas.png
+PROMPT: Clean, modern hero image for a QR code for spas and wellness centers landing page. Luxurious spa reception desk with white orchids, candles, rolled white towels, soft warm lighting, calming neutral palette, minimal composition. Professional, no text. Premium aesthetic.
+
+FILENAME: beauty-salons.png
+PROMPT: Clean, modern hero image for a QR code for beauty salons landing page. Stylish modern beauty salon interior with large illuminated mirror station, elegant product display, soft warm lighting, minimal composition. Professional, no text. Premium aesthetic.
+
+FILENAME: barbershops.png
+PROMPT: Clean, modern hero image for a QR code for barbershops landing page. Classic modern barbershop with leather barber chair, chrome tools on shelf, clean black and white tiled floor, warm lighting. Professional, no text. Premium aesthetic.
+
+FILENAME: nail-salons.png
+PROMPT: Clean, modern hero image for a QR code for nail salons landing page. Elegant nail salon station with colorful nail polish bottles neatly arranged, manicure tools, soft pastel lighting, minimal clean composition. Professional, no text. Premium aesthetic.
+
+FILENAME: tattoo-studios.png
+PROMPT: Clean, modern hero image for a QR code for tattoo studios landing page. Stylish tattoo studio interior with clean black bench, framed flash art on white walls, professional lighting, minimal edgy aesthetic. Professional, no text. Premium aesthetic.
+
+FILENAME: pharmacies.png
+PROMPT: Clean, modern hero image for a QR code for pharmacies landing page. Clean modern pharmacy interior with white shelving, organized product displays, soft clinical lighting, minimal professional composition. Professional, no text. Premium aesthetic.
+
+FILENAME: clothing-stores.png
+PROMPT: Clean, modern hero image for a QR code for clothing stores landing page. Elegant boutique clothing store with curated rack of garments, clean minimal interior, warm spotlighting, fitting room in background. Professional, no text. Premium aesthetic.
+
+FILENAME: car-dealerships.png
+PROMPT: Clean, modern hero image for a QR code for car dealerships landing page. Sleek modern car showroom with a luxury vehicle on a polished floor, dramatic overhead lighting, minimal glass and chrome architecture. Professional, no text. Premium aesthetic.
+
+FILENAME: florists.png
+PROMPT: Clean, modern hero image for a QR code for florists and flower shops landing page. Beautiful artisan florist shop with abundant colorful floral arrangements, rustic wooden counter, soft natural light. Professional, no text. Premium aesthetic.
+
+FILENAME: pet-stores.png
+PROMPT: Clean, modern hero image for a QR code for pet stores and groomers landing page. Bright modern pet store interior with organized shelving, cute dog being groomed in foreground, warm friendly lighting. Professional, no text. Premium aesthetic.
+
+FILENAME: electronics-stores.png
+PROMPT: Clean, modern hero image for a QR code for electronics stores landing page. Sleek modern electronics retail interior with backlit product displays, tablets and devices on clean white shelving, cool blue accent lighting. Professional, no text. Premium aesthetic.
+
+FILENAME: jewelry-stores.png
+PROMPT: Clean, modern hero image for a QR code for jewelry stores landing page. Luxurious jewelry store interior with glass display counter, diamond rings and necklaces elegantly arranged, warm spotlight lighting, dark rich background. Professional, no text. Premium aesthetic.
+
+FILENAME: hardware-stores.png
+PROMPT: Clean, modern hero image for a QR code for hardware and DIY stores landing page. Bright hardware store aisle with well-organized tools on shelving, clean modern signage, warm industrial lighting. Professional, no text. Premium aesthetic.
+
+FILENAME: bookstores.png
+PROMPT: Clean, modern hero image for a QR code for bookstores landing page. Cozy independent bookstore interior with floor-to-ceiling wooden shelves of books, warm reading lamp light, inviting atmosphere. Professional, no text. Premium aesthetic.
+
+FILENAME: universities.png
+PROMPT: Clean, modern hero image for a QR code for universities and colleges landing page. Impressive university campus building facade with students walking, classical architecture, blue sky, minimal composition. Professional, no text. Premium aesthetic.
+
+FILENAME: schools.png
+PROMPT: Clean, modern hero image for a QR code for schools landing page. Bright modern school corridor with lockers, natural light from windows, students walking, clean minimal educational environment. Professional, no text. Premium aesthetic.
+
+FILENAME: museums.png
+PROMPT: Clean, modern hero image for a QR code for museums and exhibitions landing page. Grand museum hall with high ceilings, dramatic artifact display, dramatic lighting on exhibits, minimal modern architecture. Professional, no text. Premium aesthetic.
+
+FILENAME: libraries.png
+PROMPT: Clean, modern hero image for a QR code for public libraries landing page. Stunning modern library interior with towering bookshelves, warm reading area, soft natural light from skylights, minimal composition. Professional, no text. Premium aesthetic.
+
+FILENAME: theaters.png
+PROMPT: Clean, modern hero image for a QR code for theaters and performing arts landing page. Elegant theater auditorium interior with red velvet seats, stage lit with warm spotlight, ornate architecture, dramatic ambiance. Professional, no text. Premium aesthetic.
+
+FILENAME: cinemas.png
+PROMPT: Clean, modern hero image for a QR code for cinemas and movie theaters landing page. Modern cinema foyer with glowing box office, dramatic neon lighting accents, minimal sleek design, movie poster frames blurred in background. Professional, no text. Premium aesthetic.
+
+FILENAME: churches.png
+PROMPT: Clean, modern hero image for a QR code for churches and places of worship landing page. Beautiful church interior with stained glass windows casting colored light, wooden pews, peaceful minimal composition. Professional, no text. Premium aesthetic.
+
+FILENAME: art-galleries.png
+PROMPT: Clean, modern hero image for a QR code for art galleries landing page. Clean white-walled contemporary art gallery with large paintings on walls, polished concrete floor, dramatic track lighting on artwork. Professional, no text. Premium aesthetic.
+
+FILENAME: stadiums.png
+PROMPT: Clean, modern hero image for a QR code for stadiums and sports venues landing page. Aerial view of a large modern stadium at golden hour, dramatic scale, vibrant field, minimal composition. Professional, no text. Premium aesthetic.
+
+FILENAME: wedding-planners.png
+PROMPT: Clean, modern hero image for a QR code for wedding planners landing page. Elegant wedding reception venue setup with floral centerpieces, candlelight, white tablecloths, soft bokeh in background, romantic minimal composition. Professional, no text. Premium aesthetic.
+
+FILENAME: photographers.png
+PROMPT: Clean, modern hero image for a QR code for photography studios landing page. Professional photography studio with camera on tripod, softbox lighting setup, white seamless backdrop, minimal clean setup. Professional, no text. Premium aesthetic.
+
+FILENAME: trade-shows.png
+PROMPT: Clean, modern hero image for a QR code for trade shows and exhibitions landing page. Large exhibition hall with branded stands, people networking, dramatic overhead lighting, minimal busy-but-clean composition. Professional, no text. Premium aesthetic.
+
+FILENAME: law-firms.png
+PROMPT: Clean, modern hero image for a QR code for law firms landing page. Prestigious law firm office with dark wood shelving, legal books, leather chairs, clean executive desk, soft warm lighting. Professional, no text. Premium aesthetic.
+
+FILENAME: accountants.png
+PROMPT: Clean, modern hero image for a QR code for accounting firms landing page. Clean modern accountancy office with sleek desk, laptop, neat files, large window with city view, minimal professional composition. Professional, no text. Premium aesthetic.
+
+FILENAME: insurance-agencies.png
+PROMPT: Clean, modern hero image for a QR code for insurance agencies landing page. Professional insurance agency office with friendly advisor desk, clean modern interior, trust-inspiring warm neutral tones, minimal composition. Professional, no text. Premium aesthetic.
+
+FILENAME: travel-agencies.png
+PROMPT: Clean, modern hero image for a QR code for travel agencies landing page. Vibrant travel agency window display with destination cards, tropical beach and mountain imagery, warm inviting lighting, minimal composition. Professional, no text. Premium aesthetic.
+
+FILENAME: coworking-spaces.png
+PROMPT: Clean, modern hero image for a QR code for coworking spaces landing page. Bright modern coworking office with open desk plan, natural light, plants, people working on laptops, minimal Scandinavian aesthetic. Professional, no text. Premium aesthetic.
+
+FILENAME: property-management.png
+PROMPT: Clean, modern hero image for a QR code for property management landing page. Modern apartment building lobby with clean reception desk, architectural lighting, minimal contemporary interior design. Professional, no text. Premium aesthetic.
+
+FILENAME: airports.png
+PROMPT: Clean, modern hero image for a QR code for airports and travel hubs landing page. Dramatic modern airport terminal interior with high glass ceilings, people with luggage walking, departure boards, minimal futuristic composition. Professional, no text. Premium aesthetic.
+
+FILENAME: dentists.png
+PROMPT: Clean, modern hero image for a QR code for dental practices landing page. Clean modern dental practice waiting room with white interior, comfortable seating, reception desk, plants, calming warm lighting. Professional, no text. Premium aesthetic.
--- a/marketing/programmatic-seo-1000-page-plan.md
+++ b/marketing/programmatic-seo-1000-page-plan.md
@@ -0,0 +1,457 @@
+# Programmatic SEO Plan: 1000 Pages for QR Master
+
+Date: 2026-03-31
+Owner: QR Master
+Scope: Organic growth plan for roughly 1000 indexable SEO pages
+
+## Executive Decision
+
+Do not build `1000 blog posts`.
+
+For QR Master, the better model is:
+
+- `80-120` editorial blog posts
+- `150-250` commercial tool pages
+- `200-300` use-case and workflow pages
+- `100-150` industry pages
+- `150-250` comparison and alternative pages
+- `150-250` support, glossary, template, and problem-solution pages
+
+That gets you to roughly `1000` pages without creating a thin-content footprint.
+
+## Why 1000 blog posts is the wrong move
+
+QR Master already has a stronger pSEO base than a typical blog-first site:
+
+- `22` blog posts in [src/lib/blog-data.ts](C:\Users\a931627\Documents\QRMASTER\src\lib\blog-data.ts)
+- `20` tool pages in [src/app/sitemap.ts](C:\Users\a931627\Documents\QRMASTER\src\app\sitemap.ts)
+- `9` use-case pages in [src/lib/growth-pages.ts](C:\Users\a931627\Documents\QRMASTER\src\lib\growth-pages.ts)
+- `8` industry pages in [src/lib/industry-pages.ts](C:\Users\a931627\Documents\QRMASTER\src\lib\industry-pages.ts)
+- static generation already exists for blog, use-cases, learn hubs, and industry pages
+
+The current architecture is already optimized for scalable landing pages, not for managing 1000 long-form editorial articles in one monolithic blog dataset.
+
+There is also a search-quality risk. Google explicitly warns against:
+
+- scaled content abuse
+- doorway-style pages
+- large volumes of low-value, near-duplicate content
+
+Relevant guidance:
+
+- Google spam policies: https://developers.google.com/search/docs/advanced/guidelines/auto-gen-content
+- Google people-first content guidance: https://developers.google.com/search/docs/fundamentals/creating-helpful-content
+- Google generative AI content guidance: https://developers.google.com/search/docs/fundamentals/using-gen-ai-content
+
+## What live SERPs suggest right now
+
+Spot checks on 2026-03-31 indicate that high-intent QR queries are mostly served by dedicated landing pages, generators, and comparison pages, not by generic blog posts.
+
+Examples:
+
+- restaurant menu QR: GustoQR, Menulizer, QRMake, Jampos, WebsitesQR
+- WiFi QR: WiQRCode, Q-WiFi
+- dynamic QR: GeckoQR, QRFlow, QRelix
+- bulk QR: QRMass, TofuQR, BulkQRBarcode
+
+This means the highest-value SEO surface for QR Master is:
+
+- generator pages
+- workflow pages
+- industry pages
+- comparison pages
+- practical support content tied to specific jobs
+
+Not 1000 generic “what is” articles.
+
+## Recommended 1000-page mix
+
+### 1. Tool intent pages: 180 pages
+
+Goal: capture users searching for a specific QR type, format, or action.
+
+Current base:
+
+- `/tools/url-qr-code`
+- `/tools/wifi-qr-code`
+- `/tools/vcard-qr-code`
+- `/tools/instagram-qr-code`
+- etc.
+
+Expand with sub-intents around each tool:
+
+- format intent: `svg`, `png`, `pdf`, `eps`
+- output intent: `for print`, `for stickers`, `for packaging`
+- job intent: `for flyers`, `for tables`, `for business cards`
+- modifier intent: `free`, `custom`, `dynamic`, `trackable`
+
+Example cluster:
+
+- `/tools/wifi-qr-code`
+- `/tools/wifi-qr-code/for-restaurants`
+- `/tools/wifi-qr-code/for-hotels`
+- `/tools/wifi-qr-code/for-airbnb`
+- `/tools/wifi-qr-code/print-size`
+- `/tools/wifi-qr-code/svg`
+- `/tools/wifi-qr-code/how-to`
+- `/tools/wifi-qr-code/troubleshooting`
+
+Requirement:
+
+- every page must change the workflow, examples, FAQ, CTA, and placement guidance
+- not just the H1
+
+### 2. Use-case and workflow pages: 260 pages
+
+Goal: map product capabilities to specific offline-to-online jobs.
+
+Current base:
+
+- `/use-cases/restaurant-menu-qr-codes`
+- `/use-cases/business-card-qr-codes`
+- `/use-cases/event-qr-codes`
+- etc.
+
+Expand by combining:
+
+- surface: table tent, flyer, poster, window, packaging, receipt, label, badge
+- workflow: menu, reviews, payment, lead capture, coupon, check-in, support, manual, onboarding
+- intent: editable, trackable, branded, bulk, privacy-safe
+
+Example patterns:
+
+- `/use-cases/qr-codes-for-product-packaging`
+- `/use-cases/qr-codes-for-brochures`
+- `/use-cases/qr-codes-for-trade-show-booths`
+- `/use-cases/qr-codes-for-real-estate-flyers`
+- `/use-cases/qr-codes-for-table-ordering`
+- `/use-cases/qr-codes-for-manuals-and-inserts`
+- `/use-cases/qr-codes-for-review-collection`
+
+### 3. Industry pages: 140 pages
+
+Goal: capture commercial intent by vertical.
+
+Current base:
+
+- restaurants
+- cafes
+- hotels
+- real estate
+- gyms
+- doctors and dentists
+- retail
+- events
+
+Best expansion model:
+
+- industry hub
+- industry plus workflow
+- industry plus operational pain point
+
+Example patterns:
+
+- `/qr-code-for/restaurants`
+- `/qr-code-for/restaurants/menu-updates`
+- `/qr-code-for/restaurants/table-ordering`
+- `/qr-code-for/restaurants/review-collection`
+- `/qr-code-for/hotels/guest-wifi`
+- `/qr-code-for/retail/packaging`
+- `/qr-code-for/events/check-in`
+
+Important:
+
+- keep the base industry pages
+- add second-level workflow pages only where search intent and product fit are strong
+
+### 4. Comparison and alternative pages: 180 pages
+
+Goal: capture bottom-funnel evaluation traffic.
+
+Patterns:
+
+- `[competitor] alternative`
+- `[competitor] vs QR Master`
+- `dynamic vs static`
+- `free vs paid`
+- `[feature A] vs [feature B]`
+
+Examples:
+
+- `/compare/qr-code-generator-com-alternative`
+- `/compare/beaconstac-alternative`
+- `/compare/flowcode-alternative`
+- `/compare/qr-code-monkey-vs-qr-master`
+- `/compare/dynamic-vs-static-qr-codes`
+- `/compare/free-vs-paid-qr-code-generator`
+
+These pages should include:
+
+- actual comparison tables
+- pricing logic
+- use-case fit
+- privacy and GDPR angle
+- migration guidance
+
+### 5. Support, glossary, and problem-solution pages: 140 pages
+
+Goal: capture informational searches with strong product adjacency.
+
+Patterns:
+
+- how to
+- troubleshooting
+- best practices
+- definitions
+- safety and compliance
+
+Examples:
+
+- `/guide/qr-code-print-size`
+- `/guide/why-my-qr-code-is-not-scanning`
+- `/guide/how-to-track-qr-code-scans`
+- `/guide/qr-code-gdpr`
+- `/guide/qr-code-phishing`
+- `/guide/how-to-create-a-vcard-qr-code`
+- `/guide/how-to-use-utm-with-qr-codes`
+
+These are not filler pages. They should support tool, use-case, and comparison clusters.
+
+### 6. Editorial blog: 100 pages
+
+Goal: publish expert-led, citation-worthy content.
+
+Use blog posts for:
+
+- original research
+- industry benchmarks
+- deep tutorials
+- opinionated comparisons
+- campaign strategy examples
+- security explainers
+
+Do not use the blog for every long-tail keyword variation.
+
+## URL architecture
+
+Stay with subfolders. Do not use subdomains.
+
+Recommended structure:
+
+- `/tools/[tool]`
+- `/tools/[tool]/[modifier-or-job]`
+- `/use-cases/[slug]`
+- `/qr-code-for/[industry]`
+- `/qr-code-for/[industry]/[workflow]`
+- `/compare/[slug]`
+- `/guide/[slug]`
+- `/blog/[slug]`
+- `/learn/[pillar]`
+
+This keeps topical authority consolidated under one domain and matches the existing app structure.
+
+## What makes each page unique
+
+Every indexable page should contain at least 3 of these:
+
+- unique quick answer
+- workflow-specific steps
+- vertical-specific FAQ
+- placement guidance
+- examples tied to the page context
+- comparison logic
+- recommended tool stack
+- CTA matched to that exact query
+- internal links to adjacent nodes
+- proprietary insights from QR Master product usage once available
+
+If a page only swaps:
+
+- city
+- industry
+- social platform name
+- file format
+
+then it is not ready to index.
+
+## The best programmatic page families for QR Master
+
+### Highest priority
+
+1. Tool x job-to-be-done
+2. Industry x workflow
+3. Use-case x printed surface
+4. Comparison and alternative pages
+5. Tracking, analytics, and GDPR support pages
+
+### Medium priority
+
+1. Glossary pages
+2. Generator template pages
+3. Print specification pages
+4. Security and trust pages
+
+### Low priority
+
+1. city pages
+2. country pages
+3. “near me” pages
+4. large-scale locale combinations
+
+Those are the most likely to drift into doorway territory for this product.
+
+## Data model recommendation
+
+Do not keep scaling everything inside one giant `blog-data.ts`.
+
+Instead, split content into typed datasets:
+
+- `src/lib/tool-pages.ts`
+- `src/lib/use-case-pages.ts`
+- `src/lib/industry-pages.ts`
+- `src/lib/comparison-pages.ts`
+- `src/lib/guide-pages.ts`
+- `src/lib/blog-data.ts`
+
+Each record should support:
+
+- slug
+- query intent
+- primary CTA
+- secondary CTA
+- unique answer block
+- unique workflow steps
+- unique FAQ
+- related links
+- schema fields
+- publish and update metadata
+
+## Internal linking model
+
+Every page should sit inside a clear cluster.
+
+Example cluster:
+
+- tool: `/tools/wifi-qr-code`
+- industry: `/qr-code-for/hotels`
+- workflow: `/qr-code-for/hotels/guest-wifi`
+- guide: `/guide/how-to-create-a-wifi-qr-code`
+- comparison: `/compare/free-vs-paid-qr-code-generator`
+- commercial: `/dynamic-qr-code-generator`
+
+Rules:
+
+- hub links down to spoke pages
+- spoke links back to hub
+- spoke links sideways to 2-4 adjacent pages
+- editorial blog links into commercial and programmatic pages
+- every page should have breadcrumb schema
+
+## Indexation policy
+
+Do not index everything on day one.
+
+Recommended rollout:
+
+- launch first `100-150` strongest pages
+- measure impressions, clicks, engagement, and conversions
+- only expand page families that show traction
+- noindex weak template variants until they have enough differentiated content
+
+This matters because a bad 1000-page rollout can lower perceived site quality faster than it grows traffic.
+
+## 90-day rollout
+
+### Phase 1: Foundation
+
+- keep current blog, tool, use-case, and industry system
+- create new page-family schemas for `comparison` and `guide`
+- move content datasets out of oversized single files where needed
+- update sitemap generation to support multiple page families
+
+### Phase 2: First 150 pages
+
+- publish 40 tool-adjacent pages
+- publish 40 industry-workflow pages
+- publish 30 use-case surface pages
+- publish 20 comparison pages
+- publish 20 support and guide pages
+
+### Phase 3: Measure
+
+Track:
+
+- indexation rate
+- impressions per page family
+- click-through rate
+- assisted signups
+- free-to-paid influence
+- pages with zero impressions after 60 days
+
+### Phase 4: Scale winners
+
+Double down only on page families that show:
+
+- meaningful impressions
+- rankings entering top 20
+- conversion assistance
+- internal-link engagement
+
+## Suggested page count by family
+
+| Family | Target |
+|---|---:|
+| Tool base pages | 20 |
+| Tool modifiers and job pages | 160 |
+| Use-case pages | 120 |
+| Use-case surface and workflow expansions | 140 |
+| Industry hubs | 20 |
+| Industry workflow pages | 120 |
+| Comparison pages | 180 |
+| Guides and troubleshooting | 140 |
+| Editorial blog | 100 |
+| Hubs and utility pages | 20 |
+| Total | 1000 |
+
+## What not to do
+
+Avoid:
+
+- 1000 AI-written blog posts targeting slight keyword variations
+- city pages without local operations or local proof
+- dozens of pages that all funnel to the same generic generator with no new value
+- near-duplicate intros with only one variable changed
+- indexable pages with no cluster context or internal links
+
+## Best next step for this codebase
+
+If the goal is execution, the best sequence is:
+
+1. add `comparison` and `guide` page families
+2. restructure page content into typed datasets
+3. ship the first `50-100` high-fit pages
+4. measure what gets indexed and clicked
+5. then scale toward `300`, `500`, and finally `1000`
+
+## Sources
+
+Live search spot checks on 2026-03-31:
+
+- https://www.gustoqr.com/
+- https://www.menulizer.com/
+- https://qrmake.io/menu-qr-code
+- https://www.jampos.app/qr-generator
+- https://www.websitesqr.com/menu-qr-code
+- https://wiqrcode.com/
+- https://www.q-wifi.com/
+- https://www.geckoqr.com/
+- https://qrflow.co/
+- https://qrmass.com/
+- https://tofu-qr.com/qr-generator/bulk/
+- https://bulkqrbarcode.com/
+
+Google guidance:
+
+- https://developers.google.com/search/docs/advanced/guidelines/auto-gen-content
+- https://developers.google.com/search/docs/fundamentals/creating-helpful-content
+- https://developers.google.com/search/docs/fundamentals/using-gen-ai-content
--- a/marketing/programmatic-seo-top-50.md
+++ b/marketing/programmatic-seo-top-50.md
@@ -0,0 +1,155 @@
+# Programmatic SEO Top 50 Backlog
+
+Date: 2026-03-31
+Project: QR Master
+Purpose: Prioritized first-wave backlog for the new `comparison` and `guide` families plus adjacent high-fit commercial clusters.
+
+## Scoring Model
+
+Each URL idea is scored from `0-100`.
+
+Weights:
+
+- Commercial intent: `30`
+- Product fit: `25`
+- Differentiation potential: `15`
+- Cluster leverage: `10`
+- SERP winability: `10`
+- Production effort: `10`
+
+Interpretation:
+
+- `90+`: ship immediately
+- `85-89`: first-wave priority
+- `80-84`: second-wave after initial measurement
+- `<80`: hold until stronger cluster support exists
+
+## Top 50
+
+| Rank | URL | Family | Score | Primary CTA |
+|---|---|---|---:|---|
+| 1 | `/compare/dynamic-vs-static-qr-codes` | comparison | 93 | `/dynamic-qr-code-generator` |
+| 2 | `/compare/free-vs-paid-qr-code-generator` | comparison | 92 | `/pricing` |
+| 3 | `/guide/how-to-track-qr-code-scans` | guide-problem | 91 | `/qr-code-tracking` |
+| 4 | `/guide/why-my-qr-code-is-not-scanning` | guide-problem | 91 | `/custom-qr-code-generator` |
+| 5 | `/guide/qr-code-print-size` | guide-problem | 90 | `/custom-qr-code-generator` |
+| 6 | `/compare/qr-code-monkey-vs-qr-master` | comparison | 90 | `/dynamic-qr-code-generator` |
+| 7 | `/compare/flowcode-alternative` | comparison | 89 | `/qr-code-tracking` |
+| 8 | `/compare/beaconstac-alternative` | comparison | 89 | `/dynamic-qr-code-generator` |
+| 9 | `/guide/how-to-use-utm-with-qr-codes` | guide-problem | 89 | `/qr-code-tracking` |
+| 10 | `/guide/dynamic-qr-code-best-practices` | guide-strategic | 88 | `/dynamic-qr-code-generator` |
+| 11 | `/guide/qr-code-gdpr` | guide-strategic | 88 | `/qr-code-tracking` |
+| 12 | `/compare/bulk-qr-generator-vs-single-qr-generator` | comparison | 88 | `/bulk-qr-code-generator` |
+| 13 | `/qr-code-for/restaurants/menu-updates` | industry-workflow | 88 | `/dynamic-qr-code-generator` |
+| 14 | `/qr-code-for/restaurants/review-collection` | industry-workflow | 87 | `/qr-code-tracking` |
+| 15 | `/tools/wifi-qr-code/for-hotels` | tool-job | 87 | `/tools/wifi-qr-code` |
+| 16 | `/guide/how-to-create-a-vcard-qr-code` | guide-problem | 87 | `/tools/vcard-qr-code` |
+| 17 | `/qr-code-for/hotels/guest-wifi` | industry-workflow | 87 | `/tools/wifi-qr-code` |
+| 18 | `/use-cases/qr-codes-for-product-packaging` | use-case | 87 | `/bulk-qr-code-generator` |
+| 19 | `/qr-code-for/retail/packaging` | industry-workflow | 86 | `/bulk-qr-code-generator` |
+| 20 | `/tools/url-qr-code/for-flyers` | tool-job | 86 | `/tools/url-qr-code` |
+| 21 | `/guide/qr-code-security-best-practices` | guide-strategic | 86 | `/dynamic-qr-code-generator` |
+| 22 | `/compare/qr-code-generator-com-alternative` | comparison | 86 | `/dynamic-qr-code-generator` |
+| 23 | `/compare/bitly-qr-code-generator-alternative` | comparison | 86 | `/qr-code-tracking` |
+| 24 | `/qr-code-for/events/check-in` | industry-workflow | 86 | `/tools/event-qr-code` |
+| 25 | `/use-cases/qr-codes-for-review-collection` | use-case | 86 | `/qr-code-tracking` |
+| 26 | `/tools/wifi-qr-code/for-restaurants` | tool-job | 85 | `/tools/wifi-qr-code` |
+| 27 | `/tools/vcard-qr-code/for-business-cards` | tool-job | 85 | `/tools/vcard-qr-code` |
+| 28 | `/guide/how-to-create-a-wifi-qr-code` | guide-problem | 85 | `/tools/wifi-qr-code` |
+| 29 | `/guide/how-to-update-a-qr-code-after-printing` | guide-problem | 85 | `/dynamic-qr-code-generator` |
+| 30 | `/compare/canva-qr-code-vs-qr-master` | comparison | 85 | `/custom-qr-code-generator` |
+| 31 | `/qr-code-for/real-estate/open-house-flyers` | industry-workflow | 85 | `/qr-code-tracking` |
+| 32 | `/use-cases/qr-codes-for-brochures` | use-case | 85 | `/dynamic-qr-code-generator` |
+| 33 | `/tools/url-qr-code/for-packaging` | tool-job | 85 | `/tools/url-qr-code` |
+| 34 | `/compare/uniqode-alternative` | comparison | 84 | `/qr-code-tracking` |
+| 35 | `/compare/adobe-express-qr-code-vs-qr-master` | comparison | 84 | `/custom-qr-code-generator` |
+| 36 | `/tools/whatsapp-qr-code/for-customer-support` | tool-job | 84 | `/tools/whatsapp-qr-code` |
+| 37 | `/qr-code-for/cafes/loyalty-signups` | industry-workflow | 84 | `/tools/url-qr-code` |
+| 38 | `/qr-code-for/events/booth-lead-capture` | industry-workflow | 84 | `/qr-code-tracking` |
+| 39 | `/guide/qr-code-landing-page-best-practices` | guide-strategic | 84 | `/dynamic-qr-code-generator` |
+| 40 | `/use-cases/qr-codes-for-table-ordering` | use-case | 84 | `/dynamic-qr-code-generator` |
+| 41 | `/tools/pdf-qr-code/for-menus` | tool-job | 83 | `/dynamic-qr-code-generator` |
+| 42 | `/guide/qr-code-analytics-for-offline-campaigns` | guide-strategic | 83 | `/qr-code-analytics` |
+| 43 | `/compare/linktree-vs-qr-master-for-offline-campaigns` | comparison | 83 | `/qr-code-for-marketing-campaigns` |
+| 44 | `/qr-code-for/doctors-dentists/intake-forms` | industry-workflow | 83 | `/tools/url-qr-code` |
+| 45 | `/tools/paypal-qr-code/for-invoices` | tool-job | 82 | `/tools/paypal-qr-code` |
+| 46 | `/guide/how-to-test-a-qr-code-before-printing` | guide-problem | 82 | `/custom-qr-code-generator` |
+| 47 | `/use-cases/qr-codes-for-manuals-and-inserts` | use-case | 82 | `/bulk-qr-code-generator` |
+| 48 | `/qr-code-for/retail/window-shopping` | industry-workflow | 81 | `/qr-code-for-marketing-campaigns` |
+| 49 | `/tools/email-qr-code/for-event-follow-up` | tool-job | 81 | `/tools/email-qr-code` |
+| 50 | `/guide/qr-code-branding-best-practices` | guide-strategic | 80 | `/custom-qr-code-generator` |
+
+## Shipment Mix For First 50
+
+Recommended composition:
+
+- `15` comparison pages
+- `15` guide pages
+- `10` tool-job pages
+- `10` industry-workflow or use-case pages
+
+This keeps the first wave biased toward:
+
+- bottom-funnel demand
+- strong CTA fit
+- cluster leverage into existing product pages
+
+## First 10 To Ship
+
+1. `/compare/dynamic-vs-static-qr-codes`
+2. `/compare/free-vs-paid-qr-code-generator`
+3. `/guide/how-to-track-qr-code-scans`
+4. `/guide/why-my-qr-code-is-not-scanning`
+5. `/guide/qr-code-print-size`
+6. `/compare/qr-code-monkey-vs-qr-master`
+7. `/compare/flowcode-alternative`
+8. `/compare/beaconstac-alternative`
+9. `/guide/how-to-use-utm-with-qr-codes`
+10. `/guide/dynamic-qr-code-best-practices`
+
+## Cluster Notes
+
+### Cluster A: Dynamic QR buying decision
+
+- `/compare/dynamic-vs-static-qr-codes`
+- `/compare/free-vs-paid-qr-code-generator`
+- `/guide/dynamic-qr-code-best-practices`
+- `/guide/how-to-update-a-qr-code-after-printing`
+- `/dynamic-qr-code-generator`
+
+### Cluster B: Tracking and analytics
+
+- `/guide/how-to-track-qr-code-scans`
+- `/guide/how-to-use-utm-with-qr-codes`
+- `/guide/qr-code-analytics-for-offline-campaigns`
+- `/qr-code-tracking`
+- `/qr-code-analytics`
+
+### Cluster C: Print reliability
+
+- `/guide/why-my-qr-code-is-not-scanning`
+- `/guide/qr-code-print-size`
+- `/guide/how-to-test-a-qr-code-before-printing`
+- `/custom-qr-code-generator`
+
+### Cluster D: Commercial alternatives
+
+- `/compare/qr-code-monkey-vs-qr-master`
+- `/compare/flowcode-alternative`
+- `/compare/beaconstac-alternative`
+- `/compare/qr-code-generator-com-alternative`
+- `/compare/uniqode-alternative`
+
+## Default Indexing Recommendation
+
+Default to `index` only when:
+
+- the page has a strong cluster position
+- the CTA is specific and commercially coherent
+- the page has distinct FAQs, workflow logic, and related links
+
+Default to `hold` or `noindex` when:
+
+- the page is still too close to an existing sibling
+- the page has weak differentiation
+- the cluster around it is not yet live
--- a/marketing/reddit-4-week-calendar-full.ics
+++ b/marketing/reddit-4-week-calendar-full.ics
@@ -0,0 +1,96 @@
+BEGIN:VCALENDAR
+VERSION:2.0
+PRODID:-//QR Master//Reddit Full Calendar//EN
+CALSCALE:GREGORIAN
+METHOD:PUBLISH
+X-WR-CALNAME:QR Master Reddit Full
+X-WR-TIMEZONE:Europe/Berlin
+BEGIN:VEVENT
+UID:reddit-full-20260316-library@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260316T100000Z
+DTEND:20260316T103000Z
+SUMMARY:Reddit reply library - all 15 templates
+DESCRIPTION:1) If someone asks what tool you use:\nIf you need the destination to stay editable later\, that’s exactly the problem I built around.\nI built QR Master for this\, so obvious bias:\nhttps://www.qrmaster.net/dynamic-qr-code-generator\nIf you want\, I can also just explain the setup without linking anything.\n\n2) Direct link ask:\nSure. I’m building it\, so bias disclosed:\nhttps://www.qrmaster.net/dynamic-qr-code-generator\nMain use case is when something is already printed and the destination changes later.\n\n3) Restaurant/menu:\nIf the menu changes even semi-regularly\, I wouldn’t print a static QR.\nhttps://www.qrmaster.net/use-cases/restaurant-menu-qr-codes\n\n4) Flyer/print:\nThe problem usually isn’t generating the QR. It’s what happens when the page changes after print.\nhttps://www.qrmaster.net/use-cases/flyer-qr-codes\n\n5) Events:\nFor events\, I’d mainly optimize for can we update this later without reprinting everything?\nhttps://www.qrmaster.net/use-cases/event-qr-codes\n\n6) Packaging/bulk:\nIf you’re dealing with lots of codes\, bulk workflow matters way more than people expect.\nhttps://www.qrmaster.net/bulk-qr-code-generator\n\n7) Analytics:\nYou probably want some scan visibility\, but only the useful stuff.\nhttps://www.qrmaster.net/qr-code-tracking\n\n8) Privacy:\nIf privacy matters\, I’d look very closely at how the tracking is handled.\nhttps://www.qrmaster.net/privacy\n\n9) Agencies:\nYeah\, agencies are actually one of the more interesting use cases.\nhttps://www.qrmaster.net/qr-code-for-marketing-campaigns\n\n10) Alternatives:\nIf you need editability after print\, that’s where tools start to differ.\nhttps://www.qrmaster.net/dynamic-qr-code-generator\n\n11) Skeptical reply:\nFair skepticism. I built it\, so I’m obviously biased:\nhttps://www.qrmaster.net/dynamic-qr-code-generator\n\n12) How set up:\nUse a dynamic destination\, keep the landing page mobile-first\, and make sure you can update it after print.\nhttps://www.qrmaster.net/dynamic-qr-code-generator\n\n13) Recommendations:\nIf the destination might change later\, I’d use a dynamic QR setup.\nhttps://www.qrmaster.net/dynamic-qr-code-generator\n\n14) Feedback thread:\nI’m building in this space\, so this is partly self-interested\, but yes\, this is a real problem.\nhttps://www.qrmaster.net/dynamic-qr-code-generator\n\n15) Direct relevance:\nI built a tool for this exact issue\, so obvious bias:\nhttps://www.qrmaster.net/dynamic-qr-code-generator
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-full-20260317-post2@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260317T120000Z
+DTEND:20260317T124500Z
+SUMMARY:r/startups - Post 2
+DESCRIPTION:Title: One URL change can ruin 500 flyers. That pain is more real than I expected.\n\nI underestimated how annoying printed mistakes are.\n\nA lot of software problems are reversible.\nPrint problems aren’t.\n\nIf a landing page changes after flyers\, posters\, inserts\, or menus are already out there\, someone has to:\n- live with a broken flow\n- reprint everything\n- or patch it manually in a messy way\n\nThat sounds minor until you talk to people actually running campaigns or local businesses.\n\nWhat small operational problem ended up being much more expensive than it looked at first?\n\nUse replies: 2\, 4\, 11\, 12\, 15
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-full-20260319-post1@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260319T120000Z
+DTEND:20260319T124500Z
+SUMMARY:r/SaaS - Post 1
+DESCRIPTION:Title: I thought QR code software was about generation. The real pain starts after print.\n\nI used to think the value was make a QR code fast.\n\nIt’s not.\n\nThe painful part starts after something is already printed:\n- the menu changes\n- the event page changes\n- the campaign URL changes\n- someone notices a typo too late\n\nOne small change can turn a stack of flyers into trash.\n\nThat shifted how I think about the whole category.\nThe QR itself is easy.\nThe expensive part is everything around it.\n\nAnyone else building in a category where the simple feature isn’t actually where the value is?\n\nUse replies: 1\, 7\, 10\, 11\, 15
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-full-20260324-post3@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260324T123000Z
+DTEND:20260324T131500Z
+SUMMARY:r/smallbusiness - Post 3
+DESCRIPTION:Title: Small businesses usually don’t need more marketing. They need fewer expensive mistakes.\n\nOne thing I keep noticing:\n\nA lot of owners don’t care about having a fancy tool.\nThey care about not wasting money.\n\nWith QR codes\, the common mistakes seem to be:\n- printing static codes for things that change often\n- sending people to ugly mobile pages\n- having no idea whether anyone scanned anything\n- letting one outdated link stay live for weeks\n\nFeels like a lot of marketing problems are actually ops problems.\n\nWhat’s one small process change that saved your business money this year?\n\nUse replies: 3\, 4\, 10\, 12\, 13
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-full-20260326-post4@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260326T120000Z
+DTEND:20260326T124500Z
+SUMMARY:r/EntrepreneurRideAlong - Post 4
+DESCRIPTION:Title: Building in a boring category taught me that boring problems are usually expensive.\n\nI’m building around QR codes\, which sounds incredibly boring on paper.\n\nBut boring problems are often the ones people pay to avoid.\n\nIn this case\, it’s stuff like:\n- reprinting menus\n- fixing outdated flyers\n- updating event info after posters are already out\n- managing lots of QR destinations across campaigns\n\nNobody is emotionally excited about QR codes.\nThey’re emotionally excited about not dealing with preventable mess.\n\nAnyone else building something unsexy that turned out to have very real pain behind it?\n\nUse replies: 2\, 4\, 9\, 11\, 15
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-full-20260327-post5@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260327T133000Z
+DTEND:20260327T141500Z
+SUMMARY:r/SideProject - Post 5
+DESCRIPTION:Title: The weird part about building a QR product is that the technical problem isn’t the interesting one.\n\nGenerating a QR image is trivial.\n\nWhat turned out to be more interesting:\n- what happens after print\n- whether someone can change the destination later\n- what analytics are actually useful\n- how privacy concerns show up once tracking enters the conversation\n- how bulk workflows matter way more than expected\n\nIt’s one of those products that looks dumb-simple from the outside and much more operational once you talk to users.\n\nWhat kind of side project looked simple until real use cases started showing up?\n\nUse replies: 1\, 6\, 7\, 8\, 15
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-full-20260331-post7@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260331T120000Z
+DTEND:20260331T124500Z
+SUMMARY:r/AlphaandBetaTesters - Post 7
+DESCRIPTION:Title: Looking for feedback from anyone who has used QR codes in restaurants\, events\, print\, or packaging.\n\nI’m trying to learn from people who use QR codes in the real world\, not just in theory.\n\nEspecially if you’ve used them for:\n- menus\n- flyers\n- product packaging\n- event materials\n- WiFi / contact sharing\n- agency campaigns\n\nThings I’m curious about:\n- what changes most often after something is printed?\n- what’s annoying about current tools?\n- do you actually care about scan analytics?\n- does privacy / GDPR affect vendor choice at all?\n\nI’m happy to share what I’m building if useful\, but mostly looking for honest feedback from people who’ve dealt with this firsthand.\n\nUse replies: 3\, 5\, 6\, 8\, 14
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-full-20260402-post8@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260402T120000Z
+DTEND:20260402T124500Z
+SUMMARY:r/RoastMyStartup - Post 8
+DESCRIPTION:Title: Roast my positioning: is avoid reprints and broken QR campaigns a strong enough problem?\n\nI’m working on a product around dynamic QR codes.\n\nThe positioning I’m testing is less make QR codes and more avoid reprints\, outdated links\, and messy campaign management.\n\nTarget users are mostly:\n- small businesses\n- restaurants\n- marketers\n- agencies\n- event / packaging use cases\n\nThe questions I’d love roasted:\n- does the pain feel real enough?\n- does this sound too niche?\n- what part sounds generic or weak?\n- what would make you ignore this instantly?\n\nHappy to share the product if the sub is okay with it.\n\nUse replies: 2\, 10\, 11\, 14\, 15
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-full-20260403-post6@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260403T123000Z
+DTEND:20260403T131500Z
+SUMMARY:r/ProductMgmt - Post 6
+DESCRIPTION:Title: Users say they want a QR generator. What they actually want is damage control.\n\nA PM lesson I didn’t expect:\n\nPeople describe the need as I need a QR code.\nBut what they actually care about is something like:\nI need this thing to not break once it’s already printed.\n\nThat changes what feels important.\n\nGenerate code sounds like the core feature.\nBut retention/value probably sits closer to:\n- edit later\n- track scans\n- handle multiple codes\n- avoid privacy headaches\n- manage existing campaigns cleanly\n\nHave you seen that mismatch in your own product?\nWhat users ask for first vs. what actually matters later?\n\nUse replies: 1\, 7\, 8\, 10\, 12
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-full-20260407-post9@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260407T120000Z
+DTEND:20260407T124500Z
+SUMMARY:r/startups - Post 9
+DESCRIPTION:Title: I’m starting to think edit after print is a stronger product promise than track scans.\n\nInteresting thing from early positioning:\n\nI assumed analytics would be the hero feature.\nBut I can change the destination later seems to click faster.\n\nMakes sense in hindsight.\nTracking is nice.\nAvoiding expensive mistakes is urgent.\n\nSo now I’m wondering if the better message is:\n- first promise control\n- then introduce analytics\n- then layer in bulk / workflow / privacy\n\nIf you’ve sold into small businesses or marketers:\nwhat kind of promise gets attention faster\, insight or control?\n\nUse replies: 1\, 7\, 9\, 10\, 15
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-full-20260409-post10@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260409T123000Z
+DTEND:20260409T131500Z
+SUMMARY:r/smallbusiness - Post 10
+DESCRIPTION:Title: What looks like a tiny print detail can quietly waste a lot of money.\n\nI keep coming back to this:\n\nA broken link on a website is annoying.\nA broken link on printed material is expensive.\n\nBecause now the problem is sitting in:\n- stores\n- restaurants\n- posters\n- packaging\n- tables\n- flyers already handed out\n\nFeels like one of those things that sounds tiny until you count the friction and replacement cost.\n\nWhat’s a small detail in your business that causes way more downstream cost than people assume?\n\nUse replies: 3\, 4\, 6\, 13\, 15
+END:VEVENT
+END:VCALENDAR
--- a/marketing/reddit-4-week-calendar-full.md
+++ b/marketing/reddit-4-week-calendar-full.md
@@ -0,0 +1,443 @@
+# QR Master Reddit Calendar - Full 4 Weeks
+
+Times are in Europe/Berlin.
+
+## Link Map
+
+- Core dynamic angle: `https://www.qrmaster.net/dynamic-qr-code-generator`
+- Reprint / waste angle: `https://www.qrmaster.net/reprint-calculator`
+- Restaurant / menu: `https://www.qrmaster.net/use-cases/restaurant-menu-qr-codes`
+- Flyer / print campaigns: `https://www.qrmaster.net/use-cases/flyer-qr-codes`
+- Event use case: `https://www.qrmaster.net/use-cases/event-qr-codes`
+- Bulk / packaging: `https://www.qrmaster.net/bulk-qr-code-generator`
+- Packaging use case: `https://www.qrmaster.net/use-cases/packaging-qr-codes`
+- Tracking / analytics: `https://www.qrmaster.net/qr-code-tracking`
+- Privacy: `https://www.qrmaster.net/privacy`
+- Campaign workflows: `https://www.qrmaster.net/qr-code-for-marketing-campaigns`
+- Main site: `https://www.qrmaster.net/`
+
+## Reply Library
+
+### 1. If someone asks what tool you use
+
+```text
+If you need the destination to stay editable later, that’s exactly the problem I built around.
+
+I built QR Master for this, so obvious bias:
+https://www.qrmaster.net/dynamic-qr-code-generator
+
+If you want, I can also just explain the setup without linking anything.
+```
+
+### 2. If someone asks for the link directly
+
+```text
+Sure. I’m building it, so bias disclosed:
+https://www.qrmaster.net/dynamic-qr-code-generator
+
+Main use case is when something is already printed and the destination changes later.
+```
+
+### 3. Restaurant / menu threads
+
+```text
+If the menu changes even semi-regularly, I wouldn’t print a static QR.
+
+I built a tool for exactly that use case, so obvious bias here:
+https://www.qrmaster.net/use-cases/restaurant-menu-qr-codes
+
+Even without using mine, I’d still recommend a dynamic destination and a very mobile-friendly menu page.
+```
+
+### 4. Flyer / print campaign threads
+
+```text
+The problem usually isn’t generating the QR. It’s what happens when the page changes after print.
+
+I built something specifically for that:
+https://www.qrmaster.net/use-cases/flyer-qr-codes
+
+If helpful, I can outline the print-safe setup here too.
+```
+
+### 5. Event use case
+
+```text
+For events, I’d mainly optimize for “can we update this later without reprinting everything?”
+
+I built QR Master around that exact headache, so bias here:
+https://www.qrmaster.net/use-cases/event-qr-codes
+```
+
+### 6. Packaging / bulk
+
+```text
+If you’re dealing with lots of codes, bulk workflow matters way more than people expect.
+
+I built this with that in mind:
+https://www.qrmaster.net/bulk-qr-code-generator
+
+Happy to share what a clean CSV / batch setup usually looks like.
+```
+
+### 7. Analytics questions
+
+```text
+You probably want some scan visibility, but only the useful stuff.
+
+I built QR Master with that angle in mind, so obvious bias:
+https://www.qrmaster.net/qr-code-tracking
+
+Personally I think basic scan data + clean attribution matters more than a flashy dashboard.
+```
+
+### 8. Privacy / GDPR
+
+```text
+If privacy matters, I’d look very closely at how the tracking is handled.
+
+I’m building QR Master, so not pretending to be neutral:
+https://www.qrmaster.net/privacy
+
+That said, I’d ask the same questions to any vendor.
+```
+
+### 9. If someone says this would be useful for agencies
+
+```text
+Yeah, agencies are actually one of the more interesting use cases.
+
+I built this partly with that workflow in mind:
+https://www.qrmaster.net/qr-code-for-marketing-campaigns
+
+Managing multiple destinations gets messy fast otherwise.
+```
+
+### 10. If someone asks about alternatives
+
+```text
+Depends what you care about.
+
+If you just need a basic static code, almost anything works.
+If you need editability after print, that’s where tools start to differ.
+
+I built QR Master for that second case:
+https://www.qrmaster.net/dynamic-qr-code-generator
+```
+
+### 11. If someone is skeptical
+
+```text
+Fair skepticism.
+
+I built it, so I’m obviously biased:
+https://www.qrmaster.net/dynamic-qr-code-generator
+
+If you’d rather keep it link-free, I’m happy to just explain the tradeoffs here.
+```
+
+### 12. If someone asks how you would set this up
+
+```text
+Short version:
+use a dynamic destination, keep the landing page mobile-first, and make sure you can update it after print.
+
+I built a tool for exactly that flow:
+https://www.qrmaster.net/dynamic-qr-code-generator
+```
+
+### 13. If someone asks for recommendations
+
+```text
+If the destination might change later, I’d use a dynamic QR setup.
+
+I built one for that use case, so take this with bias:
+https://www.qrmaster.net/dynamic-qr-code-generator
+
+If not mine, I’d still choose something that makes post-print edits easy.
+```
+
+### 14. Feedback threads
+
+```text
+I’m building in this space, so this is partly self-interested, but yes, this is a real problem.
+
+Here’s what I’m working on if useful:
+https://www.qrmaster.net/dynamic-qr-code-generator
+
+Would genuinely love blunt feedback more than polite praise.
+```
+
+### 15. Direct relevance / no hard sell
+
+```text
+I built a tool for this exact issue, so obvious bias:
+https://www.qrmaster.net/dynamic-qr-code-generator
+
+No hard sell. Just seemed directly relevant to what you asked.
+```
+
+## Schedule
+
+### 2026-03-17 Tuesday, 13:00
+
+- Subreddit: `r/startups`
+- Post #2
+- Title: `One URL change can ruin 500 flyers. That pain is more real than I expected.`
+- Use replies: `2`, `4`, `11`, `12`, `15`
+
+```text
+I underestimated how annoying printed mistakes are.
+
+A lot of software problems are reversible.
+Print problems aren’t.
+
+If a landing page changes after flyers, posters, inserts, or menus are already out there, someone has to:
+- live with a broken flow
+- reprint everything
+- or patch it manually in a messy way
+
+That sounds minor until you talk to people actually running campaigns or local businesses.
+
+What small operational problem ended up being much more expensive than it looked at first?
+```
+
+### 2026-03-19 Thursday, 13:00
+
+- Subreddit: `r/SaaS`
+- Post #1
+- Title: `I thought QR code software was about generation. The real pain starts after print.`
+- Use replies: `1`, `7`, `10`, `11`, `15`
+
+```text
+I used to think the value was “make a QR code fast.”
+
+It’s not.
+
+The painful part starts after something is already printed:
+- the menu changes
+- the event page changes
+- the campaign URL changes
+- someone notices a typo too late
+
+One small change can turn a stack of flyers into trash.
+
+That shifted how I think about the whole category.
+The QR itself is easy.
+The expensive part is everything around it.
+
+Anyone else building in a category where the “simple feature” isn’t actually where the value is?
+```
+
+### 2026-03-24 Tuesday, 13:30
+
+- Subreddit: `r/smallbusiness`
+- Post #3
+- Title: `Small businesses usually don’t need “more marketing.” They need fewer expensive mistakes.`
+- Use replies: `3`, `4`, `10`, `12`, `13`
+
+```text
+One thing I keep noticing:
+
+A lot of owners don’t care about having a fancy tool.
+They care about not wasting money.
+
+With QR codes, the common mistakes seem to be:
+- printing static codes for things that change often
+- sending people to ugly mobile pages
+- having no idea whether anyone scanned anything
+- letting one outdated link stay live for weeks
+
+Feels like a lot of “marketing problems” are actually ops problems.
+
+What’s one small process change that saved your business money this year?
+```
+
+### 2026-03-26 Thursday, 13:00
+
+- Subreddit: `r/EntrepreneurRideAlong`
+- Post #4
+- Use replies: `2`, `4`, `9`, `11`, `15`
+
+```text
+Building in a boring category taught me that boring problems are usually expensive
+
+I’m building around QR codes, which sounds incredibly boring on paper.
+
+But boring problems are often the ones people pay to avoid.
+
+In this case, it’s stuff like:
+- reprinting menus
+- fixing outdated flyers
+- updating event info after posters are already out
+- managing lots of QR destinations across campaigns
+
+Nobody is emotionally excited about QR codes.
+They’re emotionally excited about not dealing with preventable mess.
+
+Anyone else building something “unsexy” that turned out to have very real pain behind it?
+```
+
+### 2026-03-27 Friday, 14:30
+
+- Subreddit: `r/SideProject`
+- Post #5
+- Title: `The weird part about building a QR product is that the technical problem isn’t the interesting one`
+- Use replies: `1`, `6`, `7`, `8`, `15`
+
+```text
+Generating a QR image is trivial.
+
+What turned out to be more interesting:
+- what happens after print
+- whether someone can change the destination later
+- what analytics are actually useful
+- how privacy concerns show up once tracking enters the conversation
+- how bulk workflows matter way more than expected
+
+It’s one of those products that looks dumb-simple from the outside and much more operational once you talk to users.
+
+What kind of side project looked simple until real use cases started showing up?
+```
+
+### 2026-03-31 Tuesday, 14:00
+
+- Subreddit: `r/AlphaandBetaTesters`
+- Post #7
+- Use replies: `3`, `5`, `6`, `8`, `14`
+
+```text
+Looking for feedback from anyone who has used QR codes in restaurants, events, print, or packaging
+
+I’m trying to learn from people who use QR codes in the real world, not just in theory.
+
+Especially if you’ve used them for:
+- menus
+- flyers
+- product packaging
+- event materials
+- WiFi / contact sharing
+- agency campaigns
+
+Things I’m curious about:
+- what changes most often after something is printed?
+- what’s annoying about current tools?
+- do you actually care about scan analytics?
+- does privacy / GDPR affect vendor choice at all?
+
+I’m happy to share what I’m building if useful, but mostly looking for honest feedback from people who’ve dealt with this firsthand.
+```
+
+### 2026-04-02 Thursday, 14:00
+
+- Subreddit: `r/RoastMyStartup`
+- Post #8
+- Use replies: `2`, `10`, `11`, `14`, `15`
+
+```text
+Roast my positioning: is “avoid reprints and broken QR campaigns” a strong enough problem?
+
+I’m working on a product around dynamic QR codes.
+
+The positioning I’m testing is less “make QR codes” and more:
+“avoid reprints, outdated links, and messy campaign management.”
+
+Target users are mostly:
+- small businesses
+- restaurants
+- marketers
+- agencies
+- event / packaging use cases
+
+The questions I’d love roasted:
+- does the pain feel real enough?
+- does this sound too niche?
+- what part sounds generic or weak?
+- what would make you ignore this instantly?
+
+Happy to share the product if the sub is okay with it.
+```
+
+### 2026-04-03 Friday, 14:30
+
+- Subreddit: `r/ProductMgmt`
+- Post #6
+- Use replies: `1`, `7`, `8`, `10`, `12`
+
+```text
+Users say they want a QR generator. What they actually want is damage control.
+
+A PM lesson I didn’t expect:
+
+People describe the need as “I need a QR code.”
+But what they actually care about is something like:
+“I need this thing to not break once it’s already printed.”
+
+That changes what feels important.
+
+“Generate code” sounds like the core feature.
+But retention/value probably sits closer to:
+- edit later
+- track scans
+- handle multiple codes
+- avoid privacy headaches
+- manage existing campaigns cleanly
+
+Have you seen that mismatch in your own product?
+What users ask for first vs. what actually matters later?
+```
+
+### 2026-04-07 Tuesday, 14:00
+
+- Subreddit: `r/startups`
+- Post #9
+- Use replies: `1`, `7`, `9`, `10`, `15`
+
+```text
+I’m starting to think “edit after print” is a stronger product promise than “track scans”
+
+Interesting thing from early positioning:
+
+I assumed analytics would be the hero feature.
+But “I can change the destination later” seems to click faster.
+
+Makes sense in hindsight.
+Tracking is nice.
+Avoiding expensive mistakes is urgent.
+
+So now I’m wondering if the better message is:
+- first promise control
+- then introduce analytics
+- then layer in bulk / workflow / privacy
+
+If you’ve sold into small businesses or marketers:
+what kind of promise gets attention faster, insight or control?
+```
+
+### 2026-04-09 Thursday, 14:30
+
+- Subreddit: `r/smallbusiness`
+- Post #10
+- Use replies: `3`, `4`, `6`, `13`, `15`
+
+```text
+What looks like a tiny print detail can quietly waste a lot of money
+
+I keep coming back to this:
+
+A broken link on a website is annoying.
+A broken link on printed material is expensive.
+
+Because now the problem is sitting in:
+- stores
+- restaurants
+- posters
+- packaging
+- tables
+- flyers already handed out
+
+Feels like one of those things that sounds tiny until you count the friction and replacement cost.
+
+What’s a “small detail” in your business that causes way more downstream cost than people assume?
+```
+
--- a/marketing/reddit-4-week-calendar-universal.ics
+++ b/marketing/reddit-4-week-calendar-universal.ics
@@ -0,0 +1,168 @@
+BEGIN:VCALENDAR
+VERSION:2.0
+PRODID:-//QR Master//Reddit 4 Week Calendar Universal//EN
+CALSCALE:GREGORIAN
+METHOD:PUBLISH
+X-WR-CALNAME:QR Master Reddit Plan
+X-WR-TIMEZONE:Europe/Berlin
+BEGIN:VEVENT
+UID:reddit-20260316-comments-universal@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260316T133000Z
+DTEND:20260316T141500Z
+SUMMARY:Reddit comment block - r/startups + r/SaaS
+DESCRIPTION:Warm up account and build relevant karma. No links unless asked directly.
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260317-startups-post-universal@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260317T120000Z
+DTEND:20260317T124500Z
+SUMMARY:Reddit post - r/startups
+DESCRIPTION:Post: One URL change can ruin 500 flyers. Link only if asked. Use https://www.qrmaster.net/reprint-calculator
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260318-startups-replies-universal@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260318T133000Z
+DTEND:20260318T141500Z
+SUMMARY:Reddit replies - r/startups
+DESCRIPTION:Reply to all serious comments from Tuesday. Keep link-free unless asked directly.
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260319-saas-post-universal@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260319T120000Z
+DTEND:20260319T124500Z
+SUMMARY:Reddit post - r/SaaS
+DESCRIPTION:Post: The real pain starts after print. Link only if asked. Use https://www.qrmaster.net/dynamic-qr-code-generator
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260320-saas-comments-universal@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260320T133000Z
+DTEND:20260320T141500Z
+SUMMARY:Reddit comment block - r/SaaS
+DESCRIPTION:Extend the Thursday discussion. Tracking link if needed: https://www.qrmaster.net/qr-code-tracking
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260323-smallbiz-sideproject-comments-universal@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260323T133000Z
+DTEND:20260323T141500Z
+SUMMARY:Reddit comment block - r/smallbusiness + r/SideProject
+DESCRIPTION:Warm both subs before posting this week. No links unless asked directly.
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260324-smallbusiness-post-universal@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260324T123000Z
+DTEND:20260324T131500Z
+SUMMARY:Reddit post - r/smallbusiness
+DESCRIPTION:Post: Most small businesses do not need more tools. Default link if asked: https://www.qrmaster.net/reprint-calculator
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260325-smallbusiness-replies-universal@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260325T133000Z
+DTEND:20260325T141500Z
+SUMMARY:Reddit replies - r/smallbusiness
+DESCRIPTION:Answer practical questions from Tuesday. Drop links only when the use case is obvious.
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260326-sideproject-post-universal@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260326T120000Z
+DTEND:20260326T124500Z
+SUMMARY:Reddit post - r/SideProject
+DESCRIPTION:Post: The technical problem is not the interesting one. Core link: https://www.qrmaster.net/dynamic-qr-code-generator
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260327-sideproject-comments-universal@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260327T133000Z
+DTEND:20260327T141500Z
+SUMMARY:Reddit comment block - r/SideProject
+DESCRIPTION:Follow up on Thursday. Bulk link if needed: https://www.qrmaster.net/bulk-qr-code-generator
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260330-feedback-roast-comments-universal@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260330T133000Z
+DTEND:20260330T141500Z
+SUMMARY:Reddit comment block - feedback week warm-up
+DESCRIPTION:Warm up r/AlphaandBetaTesters and r/RoastMyStartup. No links today.
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260331-alpha-beta-post-universal@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260331T120000Z
+DTEND:20260331T124500Z
+SUMMARY:Reddit post - r/AlphaandBetaTesters
+DESCRIPTION:Feedback request. Put the link in the first comment. Use https://www.qrmaster.net/dynamic-qr-code-generator
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260401-alpha-beta-replies-universal@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260401T133000Z
+DTEND:20260401T141500Z
+SUMMARY:Reddit replies - r/AlphaandBetaTesters
+DESCRIPTION:Answer all serious feedback. Privacy proof only if asked: https://www.qrmaster.net/privacy
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260402-roast-post-universal@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260402T120000Z
+DTEND:20260402T124500Z
+SUMMARY:Reddit post - r/RoastMyStartup
+DESCRIPTION:Roast my positioning. Direct site link is okay here: https://www.qrmaster.net/
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260403-objection-review-universal@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260403T133000Z
+DTEND:20260403T141500Z
+SUMMARY:Reddit objection review
+DESCRIPTION:Summarize week 3 objections: pricing, niche, privacy, free generator comparison, ICP clarity.
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260406-saas-comments-universal@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260406T133000Z
+DTEND:20260406T141500Z
+SUMMARY:Reddit comment block - r/SaaS
+DESCRIPTION:Re-enter with objection-informed comments before the next post. No links unless asked.
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260407-saas-post-2-universal@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260407T120000Z
+DTEND:20260407T124500Z
+SUMMARY:Reddit post - r/SaaS follow-up
+DESCRIPTION:Post: edit later vs track scans. Default link if asked: https://www.qrmaster.net/dynamic-qr-code-generator
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260408-saas-replies-universal@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260408T133000Z
+DTEND:20260408T141500Z
+SUMMARY:Reddit replies - r/SaaS
+DESCRIPTION:Work the Tuesday thread hard for comments, not just upvotes.
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260409-promo-post-universal@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260409T123000Z
+DTEND:20260409T131500Z
+SUMMARY:Reddit promo post
+DESCRIPTION:Post in r/Plugyourproduct or r/startups_promotion. Direct link okay: https://www.qrmaster.net/
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260410-followup-universal@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260410T133000Z
+DTEND:20260410T141500Z
+SUMMARY:Reddit follow-up block
+DESCRIPTION:Answer all promo-thread comments publicly. No DMs, no pressure.
+END:VEVENT
+END:VCALENDAR
--- a/marketing/reddit-4-week-calendar.ics
+++ b/marketing/reddit-4-week-calendar.ics
@@ -0,0 +1,166 @@
+BEGIN:VCALENDAR
+VERSION:2.0
+PRODID:-//QR Master//Reddit 4 Week Calendar//EN
+CALSCALE:GREGORIAN
+METHOD:PUBLISH
+BEGIN:VEVENT
+UID:reddit-20260316-comments@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260316T143000
+DTEND:20260316T151500
+SUMMARY:Reddit comment block - r/startups + r/SaaS
+DESCRIPTION:Goal: warm up account and build relevant karma. No links unless asked directly.
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260317-startups-post@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260317T130000
+DTEND:20260317T134500
+SUMMARY:Reddit post - r/startups
+DESCRIPTION:Title: One URL change can ruin 500 flyers. Link only if asked. Use https://www.qrmaster.net/reprint-calculator
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260318-startups-replies@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260318T143000
+DTEND:20260318T151500
+SUMMARY:Reddit replies - r/startups
+DESCRIPTION:Reply to all serious comments from Tuesday. Keep link-free unless asked directly.
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260319-saas-post@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260319T130000
+DTEND:20260319T134500
+SUMMARY:Reddit post - r/SaaS
+DESCRIPTION:Title: The real pain starts after print. Link only if asked. Use https://www.qrmaster.net/dynamic-qr-code-generator
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260320-saas-comments@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260320T143000
+DTEND:20260320T151500
+SUMMARY:Reddit comment block - r/SaaS
+DESCRIPTION:Extend the Thursday discussion. If asked about tracking, use https://www.qrmaster.net/qr-code-tracking
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260323-smallbiz-sideproject-comments@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260323T143000
+DTEND:20260323T151500
+SUMMARY:Reddit comment block - r/smallbusiness + r/SideProject
+DESCRIPTION:Warm both subs before posting this week. No links unless asked directly.
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260324-smallbusiness-post@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260324T133000
+DTEND:20260324T141500
+SUMMARY:Reddit post - r/smallbusiness
+DESCRIPTION:Title: Most small businesses don't need more tools. Default link if asked: https://www.qrmaster.net/reprint-calculator Restaurant link: https://www.qrmaster.net/use-cases/restaurant-menu-qr-codes
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260325-smallbusiness-replies@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260325T143000
+DTEND:20260325T151500
+SUMMARY:Reddit replies - r/smallbusiness
+DESCRIPTION:Answer practical questions from Tuesday. Drop links only when the use case is obvious.
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260326-sideproject-post@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260326T130000
+DTEND:20260326T134500
+SUMMARY:Reddit post - r/SideProject
+DESCRIPTION:Title: The technical problem isn't the interesting one. Core link if asked: https://www.qrmaster.net/dynamic-qr-code-generator Bulk link: https://www.qrmaster.net/bulk-qr-code-generator
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260327-sideproject-comments@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260327T143000
+DTEND:20260327T151500
+SUMMARY:Reddit comment block - r/SideProject
+DESCRIPTION:Follow up on the Thursday thread. Use bulk link if people ask about scale or packaging.
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260330-feedback-roast-comments@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260330T153000
+DTEND:20260330T161500
+SUMMARY:Reddit comment block - feedback week warm-up
+DESCRIPTION:Warm up r/AlphaandBetaTesters and r/RoastMyStartup. No links today.
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260331-alpha-beta-post@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260331T140000
+DTEND:20260331T144500
+SUMMARY:Reddit post - r/AlphaandBetaTesters
+DESCRIPTION:Feedback request. Put the link in the first comment, not the post body. Use https://www.qrmaster.net/dynamic-qr-code-generator
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260401-alpha-beta-replies@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260401T153000
+DTEND:20260401T161500
+SUMMARY:Reddit replies - r/AlphaandBetaTesters
+DESCRIPTION:Answer all serious feedback. Privacy proof only if asked: https://www.qrmaster.net/privacy
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260402-roast-post@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260402T140000
+DTEND:20260402T144500
+SUMMARY:Reddit post - r/RoastMyStartup
+DESCRIPTION:Roast my positioning. Direct site link is okay here: https://www.qrmaster.net/
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260403-objection-review@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260403T153000
+DTEND:20260403T161500
+SUMMARY:Reddit objection review
+DESCRIPTION:Summarize the week-3 objections: pricing, niche, privacy, free generator comparison, ICP clarity.
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260406-saas-comments@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260406T153000
+DTEND:20260406T161500
+SUMMARY:Reddit comment block - r/SaaS
+DESCRIPTION:Re-enter with objection-informed comments before the next post. No links unless asked.
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260407-saas-post-2@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260407T140000
+DTEND:20260407T144500
+SUMMARY:Reddit post - r/SaaS follow-up
+DESCRIPTION:Title: edit later vs track scans. Default link if asked: https://www.qrmaster.net/dynamic-qr-code-generator Measurement angle: https://www.qrmaster.net/qr-code-for-marketing-campaigns
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260408-saas-replies@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260408T153000
+DTEND:20260408T161500
+SUMMARY:Reddit replies - r/SaaS
+DESCRIPTION:Work the Tuesday thread hard for comments, not just upvotes.
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260409-promo-post@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260409T143000
+DTEND:20260409T151500
+SUMMARY:Reddit promo post - r/Plugyourproduct or r/startups_promotion
+DESCRIPTION:Direct link in post is okay. Use https://www.qrmaster.net/ Optional focused link: https://www.qrmaster.net/dynamic-qr-code-generator
+END:VEVENT
+BEGIN:VEVENT
+UID:reddit-20260410-followup@qrmaster.net
+DTSTAMP:20260312T120000Z
+DTSTART:20260410T153000
+DTEND:20260410T161500
+SUMMARY:Reddit follow-up block
+DESCRIPTION:Answer all promo-thread comments publicly. No DMs, no pressure, keep it in-thread.
+END:VEVENT
+END:VCALENDAR
--- a/marketing/reddit-4-week-calendar.md
+++ b/marketing/reddit-4-week-calendar.md
@@ -0,0 +1,457 @@
+# Reddit 4-Week Calendar for QR Master
+
+Times below are in Europe/Berlin local time.
+Use clean URLs only. Do not add UTM parameters to public Reddit links.
+
+## Link Map
+
+- Reprint / cost angle: `https://www.qrmaster.net/reprint-calculator`
+- Dynamic after print: `https://www.qrmaster.net/dynamic-qr-code-generator`
+- Restaurant / menu angle: `https://www.qrmaster.net/use-cases/restaurant-menu-qr-codes`
+- Flyer / print attribution: `https://www.qrmaster.net/use-cases/flyer-qr-codes`
+- Campaign measurement: `https://www.qrmaster.net/qr-code-for-marketing-campaigns`
+- Tracking / analytics: `https://www.qrmaster.net/qr-code-tracking`
+- Bulk / packaging: `https://www.qrmaster.net/bulk-qr-code-generator`
+- Packaging use case: `https://www.qrmaster.net/use-cases/packaging-qr-codes`
+- Privacy proof only: `https://www.qrmaster.net/privacy`
+- Full site feedback / promo-only subs: `https://www.qrmaster.net/`
+
+## 2026-03-16 Monday, 14:30
+
+- Type: Comment block
+- Subreddits: `r/startups`, `r/SaaS`
+- Goal: Warm up account and build relevant karma
+- Rule: No links unless someone explicitly asks
+- Comment prompt ideas:
+  - "The expensive part starts after print, not at QR generation."
+  - "A lot of SMB tools sound boring until one mistake turns printed material into waste."
+  - "I care less about the QR itself and more about what happens when the destination changes later."
+
+## 2026-03-17 Tuesday, 13:00
+
+- Type: Main post
+- Subreddit: `r/startups`
+- Title: `One URL change can ruin 500 flyers. That pain is more real than I expected.`
+- Body:
+
+```text
+I underestimated how annoying printed mistakes are.
+
+A lot of software problems are reversible.
+Print problems aren’t.
+
+If a landing page changes after flyers, posters, inserts, or menus are already out there, someone has to:
+- live with a broken flow
+- reprint everything
+- or patch it manually in a messy way
+
+That sounds minor until you talk to people actually running campaigns or local businesses.
+
+What small operational problem ended up being much more expensive than it looked at first?
+```
+
+- Link if asked: `https://www.qrmaster.net/reprint-calculator`
+- Possible replies:
+
+```text
+Yeah, that’s the part I underestimated too. The QR itself is easy. The expensive part is when the destination changes after print.
+```
+
+```text
+I built around exactly that issue, so obvious bias here:
+https://www.qrmaster.net/reprint-calculator
+
+If links are annoying in this thread, I can just explain the workflow here.
+```
+
+```text
+Static is fine if the URL is truly permanent. The pain starts when someone assumes “permanent” and the campaign changes two weeks later.
+```
+
+## 2026-03-18 Wednesday, 14:30
+
+- Type: Reply block
+- Subreddits: `r/startups`
+- Goal: Reply to every serious comment from the Tuesday post
+- Link rule: Only if asked directly
+- Safe reply template:
+
+```text
+That’s fair. I’m building in this space, so obvious bias if I share the product. Happy to keep it link-free and just explain the setup.
+```
+
+## 2026-03-19 Thursday, 13:00
+
+- Type: Main post
+- Subreddit: `r/SaaS`
+- Title: `I thought QR code software was about generation. The real pain starts after print.`
+- Body:
+
+```text
+I used to think the value was “make a QR code fast.”
+
+It’s not.
+
+The painful part starts after something is already printed:
+- the menu changes
+- the event page changes
+- the campaign URL changes
+- someone notices a typo too late
+
+One small change can turn a stack of flyers into trash.
+
+That shifted how I think about the whole category.
+The QR itself is easy.
+The expensive part is everything around it.
+
+Anyone else building in a category where the “simple feature” isn’t actually where the value is?
+```
+
+- Link if asked: `https://www.qrmaster.net/dynamic-qr-code-generator`
+- Possible replies:
+
+```text
+That’s exactly how I see it now too. “Generate” sounds like the product, but “edit after print” is where the value starts.
+```
+
+```text
+I built a tool for that exact use case, so obvious founder bias:
+https://www.qrmaster.net/dynamic-qr-code-generator
+```
+
+```text
+I thought analytics would be the hook. In practice, “don’t make me reprint stuff” lands faster.
+```
+
+## 2026-03-20 Friday, 14:30
+
+- Type: Comment block
+- Subreddits: `r/SaaS`
+- Goal: Extend the Thursday discussion without posting a new link
+- If someone asks about tracking: `https://www.qrmaster.net/qr-code-tracking`
+- Safe tracking reply:
+
+```text
+If the goal is proof instead of guesswork, tracking matters. I’m building in that space too, so obvious bias:
+https://www.qrmaster.net/qr-code-tracking
+```
+
+## 2026-03-23 Monday, 14:30
+
+- Type: Comment block
+- Subreddits: `r/smallbusiness`, `r/SideProject`
+- Goal: Warm both subs before posting this week
+- Rule: No link unless asked directly
+
+## 2026-03-24 Tuesday, 13:30
+
+- Type: Main post
+- Subreddit: `r/smallbusiness`
+- Title: `Most small businesses don’t need more tools. They need fewer preventable mistakes.`
+- Body:
+
+```text
+I keep seeing the same pattern:
+
+Owners usually don’t want “more software.”
+They want fewer headaches.
+
+With QR codes, the common headaches seem to be:
+- printing a code that can’t be updated later
+- linking to a bad mobile page
+- not knowing if anyone scanned it
+- having to redo materials because one URL changed
+
+That feels less like a marketing problem and more like an operations problem.
+
+What low-effort process change saved you time or money recently?
+```
+
+- Default link if asked: `https://www.qrmaster.net/reprint-calculator`
+- Restaurant/menu link if relevant: `https://www.qrmaster.net/use-cases/restaurant-menu-qr-codes`
+- Possible replies:
+
+```text
+That’s basically how I think about it now too. Most owners don’t want a “QR platform.” They want to avoid paying twice for the same print run.
+```
+
+```text
+If the menu changes regularly, I wouldn’t print a static QR. I built around exactly that use case, so bias disclosed:
+https://www.qrmaster.net/use-cases/restaurant-menu-qr-codes
+```
+
+```text
+For a more general cost angle, this is the cleanest page to share:
+https://www.qrmaster.net/reprint-calculator
+```
+
+## 2026-03-25 Wednesday, 14:30
+
+- Type: Reply block
+- Subreddits: `r/smallbusiness`
+- Goal: Answer every practical question from the Tuesday post
+- Rule: Only drop a link when the use case is obvious
+
+## 2026-03-26 Thursday, 13:00
+
+- Type: Main post
+- Subreddit: `r/SideProject`
+- Title: `The weird part about building a QR product is that the technical problem isn’t the interesting one`
+- Body:
+
+```text
+Generating a QR image is trivial.
+
+What turned out to be more interesting:
+- what happens after print
+- whether someone can change the destination later
+- what analytics are actually useful
+- how privacy concerns show up once tracking enters the conversation
+- how bulk workflows matter way more than expected
+
+It’s one of those products that looks dumb-simple from the outside and much more operational once you talk to users.
+
+What kind of side project looked simple until real use cases started showing up?
+```
+
+- Link if asked: `https://www.qrmaster.net/dynamic-qr-code-generator`
+- Bulk link if someone asks about scale: `https://www.qrmaster.net/bulk-qr-code-generator`
+- Possible replies:
+
+```text
+Exactly. The QR itself is not the product. The post-print control is.
+```
+
+```text
+I built around that exact issue, so obvious bias:
+https://www.qrmaster.net/dynamic-qr-code-generator
+```
+
+```text
+If the interesting part for you is scale, the bulk side is here:
+https://www.qrmaster.net/bulk-qr-code-generator
+```
+
+## 2026-03-27 Friday, 14:30
+
+- Type: Comment block
+- Subreddits: `r/SideProject`
+- Goal: Follow up on the Thursday thread and answer bulk/packaging questions
+- Primary link if relevant: `https://www.qrmaster.net/bulk-qr-code-generator`
+
+## 2026-03-30 Monday, 15:30
+
+- Type: Comment block
+- Subreddits: `r/AlphaandBetaTesters`, `r/RoastMyStartup`
+- Goal: Warm up both communities before feedback posts
+- Rule: No links today
+
+## 2026-03-31 Tuesday, 14:00
+
+- Type: Feedback post
+- Subreddit: `r/AlphaandBetaTesters`
+- Title: `Looking for feedback from anyone who has used QR codes in restaurants, events, print, or packaging`
+- Body:
+
+```text
+I’m trying to learn from people who use QR codes in the real world, not just in theory.
+
+Especially if you’ve used them for:
+- menus
+- flyers
+- product packaging
+- event materials
+- WiFi / contact sharing
+- agency campaigns
+
+Things I’m curious about:
+- what changes most often after something is printed?
+- what’s annoying about current tools?
+- do you actually care about scan analytics?
+- does privacy / GDPR affect vendor choice at all?
+
+I’m happy to share what I’m building if useful, but mostly looking for honest feedback from people who’ve dealt with this firsthand.
+```
+
+- Link placement: first comment, not the post body
+- First comment link: `https://www.qrmaster.net/dynamic-qr-code-generator`
+- Possible replies:
+
+```text
+This is the product I’m testing the messaging on, so obvious bias:
+https://www.qrmaster.net/dynamic-qr-code-generator
+```
+
+```text
+That’s useful. The thing I keep hearing too is that the problem starts once something is already printed.
+```
+
+```text
+If the privacy side is the bigger concern, I can share how I’m handling that specifically instead of pitching the product.
+```
+
+## 2026-04-01 Wednesday, 15:30
+
+- Type: Reply block
+- Subreddits: `r/AlphaandBetaTesters`
+- Goal: Answer all serious feedback and record objections
+- Privacy proof link only if asked: `https://www.qrmaster.net/privacy`
+
+## 2026-04-02 Thursday, 14:00
+
+- Type: Roast post
+- Subreddit: `r/RoastMyStartup`
+- Title: `Roast my positioning: is “avoid reprints and broken QR campaigns” a strong enough problem?`
+- Body:
+
+```text
+I’m working on a product around dynamic QR codes.
+
+The positioning I’m testing is less “make QR codes” and more:
+“avoid reprints, outdated links, and messy campaign management.”
+
+Target users are mostly:
+- small businesses
+- restaurants
+- marketers
+- agencies
+- event / packaging use cases
+
+The questions I’d love roasted:
+- does the pain feel real enough?
+- does this sound too niche?
+- what part sounds generic or weak?
+- what would make you ignore this instantly?
+
+Happy to share the product if the sub is okay with it.
+```
+
+- Link placement: direct link in post is okay
+- Link: `https://www.qrmaster.net/`
+- Possible replies:
+
+```text
+Fair. The goal here is honestly sharper criticism, not a soft launch.
+```
+
+```text
+That’s a good callout. If the pain still sounds too “small,” then the messaging isn’t strong enough yet.
+```
+
+```text
+Yep, that’s the site:
+https://www.qrmaster.net/
+```
+
+## 2026-04-03 Friday, 15:30
+
+- Type: Objection review
+- Goal: Summarize the week-3 feedback into 3 to 5 objections
+- Typical objection buckets:
+  - "why pay for QR codes?"
+  - "sounds niche"
+  - "privacy / GDPR?"
+  - "what’s different from free generators?"
+  - "who is this really for?"
+
+## 2026-04-06 Monday, 15:30
+
+- Type: Comment block
+- Subreddits: `r/SaaS`
+- Goal: Re-enter with objection-informed comments before the next post
+- Rule: No links unless asked
+
+## 2026-04-07 Tuesday, 14:00
+
+- Type: Main post
+- Subreddit: `r/SaaS`
+- Title: `I’m starting to think “edit later” is a stronger product promise than “track scans”`
+- Body:
+
+```text
+Interesting thing from early positioning:
+
+I assumed analytics would be the hero feature.
+But “I can change the destination later” seems to click faster.
+
+Makes sense in hindsight.
+Tracking is nice.
+Avoiding expensive mistakes is urgent.
+
+So now I’m wondering if the better message is:
+- first promise control
+- then introduce analytics
+- then layer in bulk / workflow / privacy
+
+If you’ve sold into small businesses or marketers:
+what kind of promise gets attention faster, insight or control?
+```
+
+- Default link if asked: `https://www.qrmaster.net/dynamic-qr-code-generator`
+- If the thread becomes measurement-heavy: `https://www.qrmaster.net/qr-code-for-marketing-campaigns`
+- Possible replies:
+
+```text
+That’s exactly the split I’m seeing too. “Insight” sounds nice, “control” feels urgent.
+```
+
+```text
+I built around that exact use case, so obvious bias:
+https://www.qrmaster.net/dynamic-qr-code-generator
+```
+
+```text
+If the attribution side is the interesting part for you, this is the more relevant page:
+https://www.qrmaster.net/qr-code-for-marketing-campaigns
+```
+
+## 2026-04-08 Wednesday, 15:30
+
+- Type: Reply block
+- Subreddits: `r/SaaS`
+- Goal: Work the Tuesday thread hard for comments, not just upvotes
+
+## 2026-04-09 Thursday, 14:30
+
+- Type: Promo post
+- Subreddit: `r/Plugyourproduct` or `r/startups_promotion`
+- Title: `QR Master: editable QR codes for print campaigns, menus, packaging, and analytics`
+- Body:
+
+```text
+Built QR Master to solve a simple but expensive problem:
+people print QR codes, then the destination changes later.
+
+What it does:
+- editable QR destinations after print
+- scan tracking
+- bulk workflows
+- campaign-friendly use cases for menus, flyers, events, and packaging
+
+Looking for honest feedback on the value prop and landing page clarity.
+```
+
+- Link placement: direct link in post
+- Link: `https://www.qrmaster.net/`
+- Possible replies:
+
+```text
+Appreciate it. The core promise is really “don’t reprint just because the URL changed.”
+```
+
+```text
+If you want the most direct core page instead of the homepage, this is it:
+https://www.qrmaster.net/dynamic-qr-code-generator
+```
+
+```text
+If you’re more interested in measurement than editability, this page is the better entry point:
+https://www.qrmaster.net/qr-code-tracking
+```
+
+## 2026-04-10 Friday, 15:30
+
+- Type: Follow-up block
+- Goal: Answer all promo-thread comments publicly and close the 4-week run
+- Rule: No DMs, no pressure, keep every answer in-thread
+
--- a/marketing/seo-outreach-top-20-emails.md
+++ b/marketing/seo-outreach-top-20-emails.md
@@ -0,0 +1,408 @@
+# SEO Outreach Emails for Top 20 qrmaster.net Targets
+
+## Notes
+
+- Use a real sender name and personal email.
+- Keep the signature plain.
+- One follow-up after 5-7 days is enough.
+- For weaker Tier 3 targets, send only if Tier 1 and Tier 2 are exhausted.
+
+---
+
+## 1. Mailchimp
+- URL: https://www.mailchimp.com/resources/startup-tools/
+- Contact: content@mailchimp.com
+- Subject: startup tools
+
+Hi,
+
+Your startup tools page is strong on software founders use to run growth, but it skips one offline-to-online tool that shows up constantly in real campaigns: dynamic QR codes.
+
+Teams use them on flyers, packaging inserts, event signage, and direct mail when they need the destination to stay editable after print. That is the part most free QR generators do not handle well.
+
+qrmaster.net gives you free dynamic codes to start, plus tracking and bulk creation if a team needs to scale.
+
+Would that be worth considering for the list?
+
+Best,  
+[Your Name]
+
+---
+
+## 2. Edutopia
+- URL: https://www.edutopia.org/article/make-digital-classroom-tools-work-for-you/
+- Contact: community@edutopia.org
+- Subject: classroom links
+
+Hi,
+
+Your piece on making digital classroom tools work is practical, especially around how teachers combine tools rather than add more noise.
+
+One missing piece is the handoff from paper to digital. Teachers still use printed worksheets, wall stations, and take-home sheets, and QR codes are often the cleanest way to get students from paper to the right resource without typing links.
+
+qrmaster.net is a simple QR tool with dynamic codes, so the destination can be updated later without reprinting the material.
+
+Could that be a useful addition to the article?
+
+Best,  
+[Your Name]
+
+---
+
+## 3. Zendesk
+- URL: https://www.zendesk.com/blog/startup-tools/
+- Contact: content@zendesk.com
+- Subject: startup stack
+
+Hi,
+
+Your startup tools post covers the usual operating stack well. One category I expected to see but did not was dynamic QR codes.
+
+Founders end up using them for trade shows, one-pagers, packaging, retail counters, and printed onboarding material when they need a link that can still change after the asset is already out.
+
+qrmaster.net is built around that use case, with dynamic destinations, scan analytics, and bulk creation when a team moves beyond one-off codes.
+
+Would that fit the page?
+
+Best,  
+[Your Name]
+
+---
+
+## 4. Eventbrite
+- URL: https://www.eventbrite.com/blog/free-event-planning-software/
+- Contact: press@eventbrite.com
+- Subject: event updates
+
+Hi,
+
+Your roundup of event planning software is useful, especially for people trying to avoid fragmented tools.
+
+One practical gap: a QR tool for printed signage, schedules, check-in pages, menus, or speaker updates when details change after assets are already printed.
+
+That is exactly where dynamic QR codes help. qrmaster.net lets event teams keep the printed code but update the destination later, which is useful when rooms, agendas, or landing pages change at the last minute.
+
+Would that be worth adding to the resource list?
+
+Best,  
+[Your Name]
+
+---
+
+## 5. Cvent
+- URL: https://www.cvent.com/en/blog/events/event-management-software-features
+- Contact: blog@cvent.com
+- Subject: event signage
+
+Hi,
+
+Your article on event management software features is grounded in actual event workflows, not generic feature talk.
+
+One adjacent tool worth including is a dynamic QR code generator. Event teams use it for printed agendas, venue signage, exhibitor material, and check-in flows when the target page may need to change after print.
+
+qrmaster.net was built for that kind of use: editable destinations, scan tracking, and bulk creation if an event needs many codes at once.
+
+Would that be relevant for the piece?
+
+Best,  
+[Your Name]
+
+---
+
+## 6. t3n
+- URL: https://t3n.de/news/kostenlose-tools-fuer-startups-608883/
+- Contact: redaktion@t3n.de
+- Subject: startup tools
+
+Hallo,
+
+eure Liste mit kostenlosen Tools für Startups deckt viele typische SaaS-Kategorien ab. Was darin noch fehlt, ist ein sinnvoller QR-Code-Use-Case für Teams, die auch offline unterwegs sind.
+
+Startups nutzen QR-Codes inzwischen nicht nur auf Flyern, sondern auch auf Eventmaterial, Packaging, One-Pagern oder Print-Assets im Vertrieb. Relevant wird es vor allem dann, wenn sich die Zielseite nach dem Druck noch ändern können muss.
+
+qrmaster.net ist genau dafür gebaut: dynamische QR-Codes, Tracking und bei Bedarf Bulk-Erstellung.
+
+Wäre das eine sinnvolle Ergänzung für eure Liste?
+
+Viele Grüße  
+[Dein Name]
+
+---
+
+## 7. Gründerszene
+- URL: https://www.gruenderszene.de/business/startup-tools-marketing-vertrieb-it
+- Contact: redaktion@gruenderszene.de
+- Subject: marketing tools
+
+Hallo,
+
+in eurer Übersicht zu Startup-Tools für Marketing, Vertrieb und IT fehlt eine eher unscheinbare, aber in der Praxis oft genutzte Kategorie: dynamische QR-Codes.
+
+Gerade bei Events, Flyern, Print-Beilagen oder Sales-Unterlagen hilft ein QR-Code nur dann wirklich, wenn der Link später noch geändert werden kann. Sonst wird aus einem nützlichen Asset schnell ein Neudruck-Thema.
+
+qrmaster.net löst genau diesen Teil sauber, inklusive Tracking und Bulk-Erstellung für größere Kampagnen.
+
+Passt das als Ergänzung in euren Beitrag?
+
+Viele Grüße  
+[Dein Name]
+
+---
+
+## 8. Common Sense Education
+- URL: https://www.commonsense.org/education/articles/the-best-family-communication-platforms-for-teachers-and-schools
+- Contact: editor@commonsense.org
+- Subject: school handouts
+
+Hi,
+
+Your piece on family communication platforms is useful for the messaging layer between schools and families.
+
+One small tool that fits that workflow well is a QR code generator for printed handouts, take-home sheets, event reminders, and classroom notices. It gives schools a simple bridge from paper to the correct digital destination without asking families to type long links.
+
+qrmaster.net focuses on dynamic QR codes, so schools can update the destination later without reprinting the notice itself.
+
+Would that be a sensible addition to the article?
+
+Best,  
+[Your Name]
+
+---
+
+## 9. Shopify
+- URL: https://www.shopify.com/blog/startup-tools
+- Contact: blog@shopify.com
+- Subject: offline traffic
+
+Hi,
+
+Your startup tools piece covers the usual software stack well. One practical category that often gets missed is dynamic QR codes for offline traffic.
+
+Founders and small commerce teams use them on packaging, inserts, shelf talkers, retail posters, and pop-up event material when they want the printed asset to stay usable even if the destination changes later.
+
+qrmaster.net is built around that use case, with dynamic links, scan analytics, and bulk creation for larger campaigns.
+
+Worth a look for the list?
+
+Best,  
+[Your Name]
+
+---
+
+## 10. Lehrer-Online
+- URL: https://www.lehrer-online.de/unterricht/sekundarstufen/naturwissenschaften/informatik/
+- Contact: redaktion@lehrer-online.de
+- Subject: unterricht links
+
+Hallo,
+
+eure Informatik-Ressourcen sind stark, vor allem weil sie direkt aus Unterrichtssituationen gedacht wirken.
+
+Ein Werkzeug, das dort noch gut hineinpasst, ist ein QR-Code-Generator für Arbeitsblätter, Stationen oder Aufgabenblätter mit digitalen Ergänzungen. Gerade im Unterricht spart das viel Reibung, weil niemand Links abtippen muss.
+
+qrmaster.net bietet dynamische QR-Codes, sodass Lehrkräfte den Ziel-Link später noch anpassen können, ohne Materialien neu zu drucken.
+
+Wäre das etwas für eure Ressourcen?
+
+Viele Grüße  
+[Dein Name]
+
+---
+
+## 11. Fast Company
+- URL: https://www.fastcompany.com/90645634/the-best-productivity-tools-for-small-business-owners
+- Contact: tips@fastcompany.com
+- Subject: small business tools
+
+Hi,
+
+Your productivity tools piece is broader than a standard startup roundup, which is why one omission stood out to me: dynamic QR codes.
+
+Small businesses use them in surprisingly practical ways, from printed menus and flyers to trade-show materials and packaging inserts. The useful part is not the code itself, it is being able to change the destination later without wasting the print run.
+
+qrmaster.net is focused on that exact job, with dynamic destinations and scan tracking built in.
+
+Would it be worth considering for the article?
+
+Best,  
+[Your Name]
+
+---
+
+## 12. Canva
+- URL: https://www.canva.com/learn/startup-tools/
+- Contact: content@canva.com
+- Subject: printed campaigns
+
+Hi,
+
+Your startup tools page is useful for early teams that are assembling a practical stack, not just chasing shiny tools.
+
+One category that fits well there is dynamic QR codes for print-driven campaigns. Founders use them on postcards, brochures, packaging, event signage, and in-store material when they need the destination to stay editable after design work is already done.
+
+qrmaster.net handles that well, with dynamic links, scan analytics, and bulk generation when the use case grows beyond a single code.
+
+Could that fit the page?
+
+Best,  
+[Your Name]
+
+---
+
+## 13. TechCrunch
+- URL: https://www.techcrunch.com/2012/08/01/what-startups-should-do-before-they-get-into-the-vcs-office/
+- Contact: tips@techcrunch.com
+- Subject: founder resources
+
+Hi,
+
+This is a slightly different angle than a typical software pitch.
+
+For founders doing events, investor meetings, demo days, and printed leave-behinds, dynamic QR codes are one of those low-profile tools that keep showing up because they make offline material measurable and editable after it is already in circulation.
+
+qrmaster.net is built for that, with dynamic destinations and scan tracking rather than just static code generation.
+
+Might be worth including anywhere you keep founder resource roundups.
+
+Best,  
+[Your Name]
+
+---
+
+## 14. Notion
+- URL: https://www.notion.so/blog/startup-tools-stack
+- Contact: blog-team@makenotion.com
+- Subject: startup ops
+
+Hi,
+
+Your startup stack article is close to how teams actually work, which is why this feels adjacent rather than random.
+
+One tool type that often belongs in that stack is dynamic QR codes for offline touchpoints: printed onboarding, trade-show assets, internal signage, product packaging, or field material that still needs an editable destination.
+
+qrmaster.net focuses on that layer, with dynamic links, scan analytics, and bulk creation if a team needs many codes at once.
+
+Would that be relevant for the piece?
+
+Best,  
+[Your Name]
+
+---
+
+## 15. HubSpot
+- URL: https://blog.hubspot.com/sales/entrepreneur-resources
+- Contact: blog@hubspot.com
+- Subject: entrepreneur resources
+
+Hi,
+
+Your entrepreneur resources page is broad enough that one missing category stood out: dynamic QR codes.
+
+Founders and small marketing teams use them on flyers, print inserts, trade-show handouts, and retail material when they need the destination to stay editable after the asset is out in the world. That is where a basic static QR generator usually stops being enough.
+
+qrmaster.net is built around that exact use case, with dynamic links, scan analytics, and bulk creation when campaigns expand.
+
+Would that be worth adding?
+
+Best,  
+[Your Name]
+
+---
+
+## 16. Entrepreneur
+- URL: https://www.entrepreneur.com/science-technology/10-essential-tools-for-every-startup-founder/336457
+- Contact: editorial@entrepreneur.com
+- Subject: founder stack
+
+Hi,
+
+Your startup founder tools piece covers the standard software stack well. One practical category I expected to see was dynamic QR codes.
+
+They are useful anywhere founders still rely on physical touchpoints, whether that is an expo booth, a one-pager, packaging, or printed collateral. The important part is being able to update the destination later without reprinting.
+
+qrmaster.net focuses on that, with dynamic links, scan data, and bulk creation for larger sets of codes.
+
+Could that fit the article?
+
+Best,  
+[Your Name]
+
+---
+
+## 17. Buffer
+- URL: https://www.buffer.com/library/startup-tools/
+- Contact: hello@buffer.com
+- Subject: startup list
+
+Hi,
+
+Your startup tools list is practical and readable, which is probably why one missing category stood out to me: dynamic QR codes.
+
+They are useful for more than events. Founders use them on packaging, printed promo material, customer onboarding cards, and offline campaigns when the link may need to change later.
+
+qrmaster.net is built for that layer, with dynamic destinations, tracking, and bulk creation when there are many codes to manage.
+
+Would that be worth adding to the list?
+
+Best,  
+[Your Name]
+
+---
+
+## 18. Intercom
+- URL: https://www.intercom.com/blog/startup-tools-for-growth/
+- Contact: blog@intercom.io
+- Subject: growth tools
+
+Hi,
+
+Your startup growth tools piece is naturally focused on digital channels, but one useful edge case missing from the list is dynamic QR codes for offline growth touchpoints.
+
+Teams use them for packaging inserts, event materials, direct mail, posters, and printed onboarding flows when they want a link they can still update later and measure.
+
+qrmaster.net was built for that use case, with editable destinations, scan analytics, and bulk generation.
+
+Would that be relevant for the page?
+
+Best,  
+[Your Name]
+
+---
+
+## 19. Inc.
+- URL: https://www.inc.com/guides/2010/06/best-free-software-for-startups.html
+- Contact: editorial@inc.com
+- Subject: free software
+
+Hi,
+
+Your free software for startups guide is old enough to have room for one very practical update: dynamic QR codes.
+
+They are useful whenever a startup has printed material in market but still wants to change where people land later, whether that is a promo flyer, event handout, packaging insert, or storefront sign.
+
+qrmaster.net offers that in a straightforward way, with free dynamic codes to start and analytics if a team needs more than a static generator.
+
+Would it make sense as an addition?
+
+Best,  
+[Your Name]
+
+---
+
+## 20. Forbes / Bernard Marr
+- URL: https://www.forbes.com/sites/bernardmarr/2025/06/23/20-game-changing-ai-tools-every-small-business-leader-needs-now/
+- Contact: hello@bernardmarr.com
+- Subject: small business tools
+
+Hi,
+
+Your roundup focuses on AI tools, so this is slightly adjacent rather than a direct category match.
+
+The reason I am reaching out anyway is that small business teams increasingly use dynamic QR codes anywhere print meets digital: brochures, packaging, event materials, menus, and in-store signage. The useful part is being able to change the destination after print and still measure scans.
+
+qrmaster.net is built around that use case.
+
+If you ever expand the list beyond AI-only tools, would that be relevant?
+
+Best,  
+[Your Name]
--- a/marketing/twitter-30-day-plan.md
+++ b/marketing/twitter-30-day-plan.md
@@ -0,0 +1,272 @@
+# 30-Day X/Twitter Content Plan for QR Master
+
+Use this as a `30-day X/Twitter content plan` for a founder-led QR Master account. It is written in English and optimized for reach first, with product relevance built in.
+
+## Positioning for the Month
+
+`Dynamic QR codes for measurable offline marketing, without creepy tracking.`
+
+## Audience Focus
+
+Primary audience for Days 1-15:
+`Restaurants / hospitality`
+
+Secondary audience for Days 16-30:
+`Agencies / offline marketers / retail operators`
+
+## CTA Rule for the Whole Month
+
+- Most posts: `Reply with a keyword`, `follow for more`, or `DM me`
+- Only light link usage
+- Put direct product CTA mainly in replies, profile, and pinned post
+
+## 30-Day Plan
+
+### Day 1
+
+**Post type:** Founder positioning post  
+**Hook:** `Most QR codes are dead the moment they get printed.`  
+**Angle:** Static QR codes create reprint costs and broken customer journeys.  
+**CTA:** `If you run offline marketing, follow this account. I'm breaking down how to fix it.`
+
+### Day 2
+
+**Post type:** Short insight post  
+**Hook:** `A restaurant menu should not require a reprint every time one dish changes.`  
+**Angle:** Dynamic QR codes for menus and specials.  
+**CTA:** `Reply "menu" if you want me to post the exact setup.`
+
+### Day 3
+
+**Post type:** Teardown  
+**Hook:** `3 mistakes I see on restaurant QR menus all the time:`  
+**Angle:** Bad placement, no fallback page, no analytics.  
+**CTA:** `Want me to roast your menu QR? Reply with a screenshot.`
+
+### Day 4
+
+**Post type:** Thread  
+**Hook:** `How restaurants can update menus without reprinting tables, flyers, or window signs:`  
+**Angle:** 5-step workflow using one dynamic QR.  
+**CTA:** `I can turn this into a checklist if people want it.`
+
+### Day 5
+
+**Post type:** Contrarian post  
+**Hook:** `Unpopular opinion: "free QR code generators" are expensive.`  
+**Angle:** Hidden cost is reprints, lost scans, no attribution.  
+**CTA:** `Agree or disagree?`
+
+### Day 6
+
+**Post type:** Demo video  
+**Hook:** `Change the destination after print. That's the whole game.`  
+**Angle:** Quick screen recording showing edit-after-print.  
+**CTA:** `DM me "edit" and I'll send the workflow.`
+
+### Day 7
+
+**Post type:** Founder story  
+**Hook:** `We started building QR Master because most QR tools felt like toys.`  
+**Angle:** Needed analytics, bulk creation, privacy-first tracking.  
+**CTA:** `What's one thing you hate about current QR tools?`
+
+### Day 8
+
+**Post type:** Pain-to-fix post  
+**Hook:** `If your flyer has a QR code but no tracking, you're guessing.`  
+**Angle:** Offline campaigns need measurable scans.  
+**CTA:** `Reply "track" if you want a simple attribution template.`
+
+### Day 9
+
+**Post type:** Restaurant-specific post  
+**Hook:** `Today's special changes. Your printed QR shouldn't.`  
+**Angle:** Daily menu operations.  
+**CTA:** `Restaurant owners: how often do you update menus?`
+
+### Day 10
+
+**Post type:** Roast / audit  
+**Hook:** `This QR code placement is killing conversions.`  
+**Angle:** Explain why low-visibility placements fail.  
+**CTA:** `Send me your flyer/menu/poster and I'll break it down.`
+
+### Day 11
+
+**Post type:** Thread  
+**Hook:** `5 QR code mistakes that make restaurant marketing look cheap:`  
+**Angle:** Visual clutter, dead links, bad landing pages, no tracking, wrong CTA.  
+**CTA:** `I'll post 5 fixes tomorrow if this gets traction.`
+
+### Day 12
+
+**Post type:** Build in public  
+**Hook:** `One thing founders underestimate: people don't want "a QR code." They want a workflow.`  
+**Angle:** Product insight from building.  
+**CTA:** `What simple tool became critical in your business?`
+
+### Day 13
+
+**Post type:** Short proof post  
+**Hook:** `One QR code. Multiple seasonal campaigns. Zero reprints.`  
+**Angle:** Reuse same printed asset with changing destination.  
+**CTA:** `This is one of the biggest underrated offline growth hacks.`
+
+### Day 14
+
+**Post type:** Demo video  
+**Hook:** `From printed table card to measurable scan funnel in under 30 seconds:`  
+**Angle:** Show QR creation + analytics preview.  
+**CTA:** `If you want more product breakdowns, follow.`
+
+### Day 15
+
+**Post type:** Summary / recap  
+**Hook:** `The biggest restaurant QR lesson so far:`  
+**Angle:** Most businesses don't need more print, they need more flexibility.  
+**CTA:** `Next week I'm switching to agencies and offline marketers.`
+
+### Day 16
+
+**Post type:** Agency-focused post  
+**Hook:** `If your agency runs flyer or poster campaigns without QR attribution, you're underreporting impact.`  
+**Angle:** Agencies need scan data to prove ROI.  
+**CTA:** `Reply "agency" if you want my offline attribution framework.`
+
+### Day 17
+
+**Post type:** Contrarian post  
+**Hook:** `The problem is not the QR code. The problem is the dead destination behind it.`  
+**Angle:** Static link is the failure point.  
+**CTA:** `This is where most campaigns quietly lose money.`
+
+### Day 18
+
+**Post type:** Thread  
+**Hook:** `How to make offline campaigns actually measurable:`  
+**Angle:** QR + UTM + landing page + analytics naming structure.  
+**CTA:** `I can turn this into a swipe file.`
+
+### Day 19
+
+**Post type:** Audit post  
+**Hook:** `3 reasons most poster QR campaigns don't convert:`  
+**Angle:** Weak CTA, poor mobile page, no tracking structure.  
+**CTA:** `Want a poster teardown series?`
+
+### Day 20
+
+**Post type:** Demo video  
+**Hook:** `Bulk-create hundreds of QR codes from a spreadsheet.`  
+**Angle:** Show CSV/Excel workflow for agencies or retail.  
+**CTA:** `DM me "bulk" if that would save your team time.`
+
+### Day 21
+
+**Post type:** Founder hot take  
+**Hook:** `"Just put a QR code on it" is bad marketing advice.`  
+**Angle:** QR is distribution, not strategy.  
+**CTA:** `What matters more: placement, offer, or landing page?`
+
+### Day 22
+
+**Post type:** Mini case format  
+**Hook:** `Campaign idea: one printed asset, three different destinations over 30 days.`  
+**Angle:** Explain how one QR can support multiple campaign phases.  
+**CTA:** `This is why dynamic matters more than design.`
+
+### Day 23
+
+**Post type:** Thread  
+**Hook:** `How I'd structure QR tracking for an agency campaign with flyers, packaging, and in-store signage:`  
+**Angle:** Naming conventions, attribution logic, reporting.  
+**CTA:** `If useful, I'll post the naming template.`
+
+### Day 24
+
+**Post type:** Privacy wedge post  
+**Hook:** `You can measure scans without turning people into surveillance data.`  
+**Angle:** Privacy-first analytics as a business advantage.  
+**CTA:** `Too many teams think analytics has to mean creepy.`
+
+### Day 25
+
+**Post type:** Teardown  
+**Hook:** `This flyer has a QR code. But it still won't tell you what worked.`  
+**Angle:** Missing attribution structure.  
+**CTA:** `Reply with "audit" and I'll post a fixed version.`
+
+### Day 26
+
+**Post type:** Retail / packaging post  
+**Hook:** `Packaging QR codes get interesting when you can change the destination later.`  
+**Angle:** Product updates, campaigns, support pages, seasonal promos.  
+**CTA:** `Retail operators: are you using QR for support, promo, or repeat purchase?`
+
+### Day 27
+
+**Post type:** Build in public  
+**Hook:** `One thing we keep seeing: people buy QR tools for "generation" and stay for "management."`  
+**Angle:** Product-market insight.  
+**CTA:** `That distinction matters more than most founders think.`
+
+### Day 28
+
+**Post type:** Demo video  
+**Hook:** `Here's what "measurable offline workflow" actually looks like in practice:`  
+**Angle:** Create, edit, track, compare placements.  
+**CTA:** `If this kind of content is useful, I'll make it a weekly series.`
+
+### Day 29
+
+**Post type:** Hero thread  
+**Hook:** `Most offline marketing teams don't have a traffic problem. They have a measurement problem.`  
+**Angle:** Big thesis thread connecting restaurants, agencies, retail, and dynamic QR logic.  
+**CTA:** `If you work in offline marketing, this is the framework.`
+
+### Day 30
+
+**Post type:** Month-end recap + soft CTA  
+**Hook:** `30 days of talking to people about QR workflows taught me this:`  
+**Angle:** Summarize 5 strongest lessons from the month.  
+**CTA:** `If you want, next I'll publish the full playbook: hooks, setup, and attribution templates.`
+
+## Weekly Cadence
+
+- `Mon`: strong opinion or positioning
+- `Tue`: practical educational post
+- `Wed`: teardown or audit
+- `Thu`: thread
+- `Fri`: product proof or demo
+- `Sat`: founder insight / build in public
+- `Sun`: recap or lighter conversation post
+
+## Content Mix
+
+- `8 threads`
+- `6 teardown/audit posts`
+- `5 demo videos`
+- `6 short contrarian/value posts`
+- `5 founder/build-in-public posts`
+
+## Reply Strategy
+
+Every day, add:
+
+- `10-15 replies` to founders, marketers, restaurant-tech, local business, retail ops, and agency accounts
+- Focus on posts about: offline marketing, menus, customer journeys, attribution, retail campaigns, print, local growth
+- Use replies to seed your core themes:
+  - reprint cost
+  - edit after print
+  - measurable offline
+  - privacy-first analytics
+  - bulk workflows
+
+## Optional Next Step
+
+If needed, this can be expanded into:
+
+1. fully written tweets for all 30 days
+2. 8 full threads written out
+3. a Notion-style content calendar with posting times and CTAs
--- a/my-config.json
+++ b/my-config.json
@@ -0,0 +1,48 @@
+{
+    "project_name": "QRMaster Global Visibility",
+    "domain": "qrmaster.net",
+    "market_language": "en",
+    "offer": "a free dynamic QR cost calculator and professional management guide",
+    "keywords": [
+        {
+            "query": "dynamic qr code generator",
+            "intent": "commercial"
+        },
+        {
+            "query": "create dynamic qr code free",
+            "intent": "informational"
+        },
+        {
+            "query": "qr code for restaurant menu",
+            "intent": "commercial"
+        },
+        {
+            "query": "qr code marketing analytics",
+            "intent": "informational"
+        },
+        {
+            "query": "bulk qr code generator from csv",
+            "intent": "commercial"
+        }
+    ],
+    "backlink": {
+        "seed_queries": [
+            "restaurant marketing ideas intitle:resources",
+            "digital menu setup guide intitle:links",
+            "retail marketing tools inurl:blog",
+            "qr code best practices 2026",
+            "hospitality tech trends intitle:guide",
+            "small business marketing resources inurl:links"
+        ],
+        "outreach": {
+            "allow_send_emails": false,
+            "from_name": "QRMaster Outreach Team",
+            "templates": {
+                "en": {
+                    "subject": "Valuable resource for your QR code guide",
+                    "body": "Hi,\n\nI was reading your article about [Topic] and found it very insightful. We recently developed a free Static vs. Dynamic QR Cost Calculator at qrmaster.net that helps businesses visualize the ROI of their campaigns. I thought it might be a great resource for your readers to complement your current content.\n\nBest regards,\nThe QRMaster Team"
+                }
+            }
+        }
+    }
+}
--- a/next-sitemap.config.js
+++ b/next-sitemap.config.js
@@ -1,42 +0,0 @@
-/** @type {import('next-sitemap').IConfig} */
-module.exports = {
-  siteUrl: 'https://www.qrmaster.net',
-  generateRobotsTxt: true,
-  robotsTxtOptions: {
-    policies: [
-      {
-        userAgent: '*',
-        allow: '/',
-      },
-    ],
-  },
-  transform: async (config, path) => {
-    // Custom priority and changefreq based on path
-    let priority = 0.7;
-    let changefreq = 'weekly';
-
-    if (path === '/') {
-      priority = 0.9;
-      changefreq = 'daily';
-    } else if (path === '/blog') {
-      priority = 0.7;
-      changefreq = 'daily';
-    } else if (path === '/pricing') {
-      priority = 0.8;
-      changefreq = 'weekly';
-    } else if (path === '/faq') {
-      priority = 0.6;
-      changefreq = 'weekly';
-    } else if (path.startsWith('/blog/')) {
-      priority = 0.6;
-      changefreq = 'weekly';
-    }
-
-    return {
-      loc: path,
-      changefreq,
-      priority,
-      lastmod: new Date().toISOString(),
-    };
-  },
-};
--- a/next.config.mjs
+++ b/next.config.mjs
@@ -1,25 +1,104 @@
-/** @type {import('next').NextConfig} */
-const nextConfig = {
-  output: 'standalone',
-  skipTrailingSlashRedirect: true,
-  images: {
-    unoptimized: false,
-    domains: ['www.qrmaster.net', 'qrmaster.net', 'images.qrmaster.net'],
-    formats: ['image/webp', 'image/avif'],
-    deviceSizes: [640, 750, 828, 1080, 1200, 1920, 2048, 3840],
-    imageSizes: [16, 32, 48, 64, 96, 128, 256, 384],
-  },
-  experimental: {
-    serverComponentsExternalPackages: ['@prisma/client', 'bcryptjs'],
-  },
-  // Allow build to succeed even with prerender errors
-  // Pages with useSearchParams() will be rendered dynamically at runtime
-  staticPageGenerationTimeout: 120,
-  onDemandEntries: {
-    maxInactiveAge: 25 * 1000,
-    pagesBufferLength: 2,
-  },
-  poweredByHeader: false,
-};
-
-export default nextConfig;
+/** @type {import('next').NextConfig} */
+const nextConfig = {
+  output: 'standalone',
+  skipTrailingSlashRedirect: true,
+  images: {
+    unoptimized: false,
+    domains: ['www.qrmaster.net', 'qrmaster.net', 'images.qrmaster.net'],
+    formats: ['image/webp', 'image/avif'],
+    deviceSizes: [640, 750, 828, 1080, 1200, 1920, 2048, 3840],
+    imageSizes: [16, 32, 48, 64, 96, 128, 256, 384],
+  },
+  experimental: {
+    serverComponentsExternalPackages: ['@prisma/client', 'bcryptjs'],
+  },
+  // Allow build to succeed even with prerender errors
+  // Pages with useSearchParams() will be rendered dynamically at runtime
+  staticPageGenerationTimeout: 120,
+  onDemandEntries: {
+    maxInactiveAge: 25 * 1000,
+    pagesBufferLength: 2,
+  },
+  poweredByHeader: false,
+  async redirects() {
+    return [
+      {
+        source: '/create-qr',
+        destination: '/dynamic-qr-code-generator',
+        permanent: true,
+      },
+      {
+        source: '/guide/tracking-analytics',
+        destination: '/learn/tracking',
+        permanent: true,
+      },
+      {
+        source: '/guide/bulk-qr-code-generation',
+        destination: '/learn/developer',
+        permanent: true,
+      },
+      {
+        source: '/guide/qr-code-best-practices',
+        destination: '/learn/basics',
+        permanent: true,
+      },
+      {
+        source: '/tools/phone-qr-code',
+        destination: '/tools/call-qr-code-generator',
+        permanent: true,
+      },
+      {
+        source: '/barcode-generator',
+        destination: '/tools/barcode-generator',
+        permanent: true,
+      },
+      {
+        source: '/bar-code-generator',
+        destination: '/tools/barcode-generator',
+        permanent: true,
+      },
+      {
+        source: '/qr-code-for/breweries-tap-rooms',
+        destination: '/qr-code-for/breweries',
+        permanent: true,
+      },
+      {
+        source: '/qr-code-for/wineries-vineyards',
+        destination: '/qr-code-for/wineries',
+        permanent: true,
+      },
+      {
+        source: '/qr-code-for/catering-businesses',
+        destination: '/qr-code-for/catering',
+        permanent: true,
+      },
+      {
+        source: '/qr-code-for/spas-wellness-centers',
+        destination: '/qr-code-for/spas',
+        permanent: true,
+      },
+      // Additional likely old slugs from previous site version
+      { source: '/qr-code-for/bars-pubs', destination: '/qr-code-for/bars', permanent: true },
+      { source: '/qr-code-for/nightclubs-venues', destination: '/qr-code-for/nightclubs', permanent: true },
+      { source: '/qr-code-for/dental-practices', destination: '/qr-code-for/dentists', permanent: true },
+      { source: '/qr-code-for/pet-groomers', destination: '/qr-code-for/pet-grooming', permanent: true },
+      { source: '/qr-code-for/clothing-apparel-stores', destination: '/qr-code-for/clothing-stores', permanent: true },
+      { source: '/qr-code-for/florists-flower-shops', destination: '/qr-code-for/florists', permanent: true },
+      { source: '/qr-code-for/pet-stores-groomers', destination: '/qr-code-for/pet-stores', permanent: true },
+      { source: '/qr-code-for/hardware-diy-stores', destination: '/qr-code-for/hardware-stores', permanent: true },
+      { source: '/qr-code-for/universities-colleges', destination: '/qr-code-for/universities', permanent: true },
+      { source: '/qr-code-for/museums-exhibitions', destination: '/qr-code-for/museums', permanent: true },
+      { source: '/qr-code-for/public-libraries', destination: '/qr-code-for/libraries', permanent: true },
+      { source: '/qr-code-for/theaters-performing-arts', destination: '/qr-code-for/theaters', permanent: true },
+      { source: '/qr-code-for/cinemas-movie-theaters', destination: '/qr-code-for/cinemas', permanent: true },
+      { source: '/qr-code-for/churches-places-of-worship', destination: '/qr-code-for/churches', permanent: true },
+      { source: '/qr-code-for/stadiums-sports-venues', destination: '/qr-code-for/stadiums', permanent: true },
+      { source: '/qr-code-for/airports-travel-hubs', destination: '/qr-code-for/airports', permanent: true },
+      { source: '/qr-code-for/photography-studios', destination: '/qr-code-for/photographers', permanent: true },
+      { source: '/qr-code-for/trade-shows-exhibitions', destination: '/qr-code-for/trade-shows', permanent: true },
+      { source: '/qr-code-for/accounting-firms', destination: '/qr-code-for/accountants', permanent: true },
+    ];
+  },
+};
+
+export default nextConfig;
--- a/outreach-seo-emails.md
+++ b/outreach-seo-emails.md
@@ -0,0 +1,454 @@
+# SEO Outreach Cold Emails '” qrmaster.net
+**15 Ressourcen-Seiten | Segmente: Lehrer, GrÃ¼nder, Eventmanager**
+**Stand: April 2026**
+
+---
+
+## Hinweise zur Verwendung
+
+- **Absender:** Immer echten Namen + persÃ¶nliche E-Mail einsetzen (kein info@, kein noreply@)
+- **TonalitÃ¤t:** Texte sind bewusst kurz und nÃ¼chtern '” nicht nachtrÃ¤glich aufwÃ¤rmen
+- **CTA:** Die Schlussfrage macht Antworten einfach (Ja/Nein reicht) '” nicht durch Meeting-Anfragen ersetzen
+- **Reihenfolge:** Tier 1 zuerst mit maximaler Personalisierung, dann Tier 2 & 3
+- **Follow-up:** Falls keine Antwort nach 7 Tagen: einmal nachfassen (neuer Winkel), dann loslassen
+- **DSGVO-Hinweis:** "DSGVO-konform" / "GDPR-compliant" wird in keiner Mail verwendet '” zu riskant ohne rechtliche Absicherung. Stattdessen: "ohne Anmeldung nutzbar" / "no signup required"
+
+---
+
+## Tier-Ãœbersicht (PrioritÃ¤t)
+
+| Tier | Kriterium | Targets |
+|------|-----------|---------|
+| **1** | Hohe AutoritÃ¤t + klarer thematischer Fit '” zuerst senden, maximal personalisieren | #2 Promethean, #4 Cadmium, #7 U.S. Chamber, #8 Teaching Channel, #14 TeachThought, #15 Tripleseat |
+| **2** | Guter Fit, mittlere AutoritÃ¤t '” solide Chancen, weniger Aufwand pro Mail gerechtfertigt | #3 Startup Project, #5 EssayGrader, #9 Teachers of Tomorrow, #10 Montgomery College, #12 Super Monitoring |
+| **3** | Kleinere Blogs / Nice-to-have '” kÃ¶nnen funktionieren, weniger SEO-Impact | #1 eEducation AT, #6 Serkan, #11 PHSG, #13 Kunstunterricht |
+
+---
+
+## DACH '” Deutsch
+
+---
+
+### 1. eEducation Austria *(Tier 3)*
+- **URL:** https://eeducation.at/ressourcen/etapas/etapas-liste
+- **Zielgruppe:** Lehrer (DACH)
+- **Kontakt:** eeducation@bildung.gv.at
+
+**Betreff:** eTapas-Liste '” Tool-ErgÃ¤nzung
+
+---
+
+Hallo,
+
+in eurer eTapas-Liste fehlt bislang ein QR-Code-Generator. LehrkrÃ¤fte nutzen QR-Codes hÃ¤ufig, um ArbeitsblÃ¤tter oder HÃ¶rbeispiele direkt zugÃ¤nglich zu machen '” SchÃ¼ler scannen, fertig, kein Link-Tippen.
+
+qrmaster.net ist werbefrei und ohne Anmeldung nutzbar. Mit dynamischen QR-Codes lassen sich verlinkte Inhalte nachtrÃ¤glich noch Ã¤ndern '” kein Neu-Drucken nÃ¶tig.
+
+Entspricht das euren Kriterien fÃ¼r eine Aufnahme in die Liste?
+
+Viele GrÃ¼ÃŸe  
+[Dein Name]
+
+---
+
+### 2. Promethean World *(Tier 1)*
+- **URL:** https://www.prometheanworld.com/de/ressourcen-center/blog/digital-durch-den-lehreralltag-so-optimieren-digitale-tools-den-unterricht/
+- **Zielgruppe:** Lehrer (DACH)
+- **Kontakt:** info@prometheanworld.com
+
+**Betreff:** ErgÃ¤nzung zu eurem Artikel Ã¼ber digitale Tools
+
+---
+
+Hallo,
+
+in eurem Beitrag zu digitalen Tools im Lehreralltag geht es viel ums Teilen von Inhalten '” Whiteboards, Classroom-Workflows, digitale Materialien. Was fehlt: ein Weg, Links sekundenschnell auf Papier zugÃ¤nglich zu machen.
+
+QR-Codes lÃ¶sen genau das. qrmaster.net erstellt sie kostenlos und ohne Anmeldung. Dynamische QR-Codes erlauben es, den Ziel-Link spÃ¤ter noch zu Ã¤ndern '” ohne neu zu drucken.
+
+WÃ¤re das eine sinnvolle ErgÃ¤nzung fÃ¼r den Artikel?
+
+Viele GrÃ¼ÃŸe  
+[Dein Name]
+
+---
+
+### 6. Serkan Cagatay '” Musikakademie *(Tier 3)*
+- **URL:** https://www.serkancagatay.com/musikakademie/didaktische-ressourcen-and-plattformen/
+- **Zielgruppe:** Lehrer (DACH)
+- **Kontakt:** info@serkancagatay.com
+
+**Betreff:** Tool-Tipp fÃ¼r deine Ressourcen-Liste
+
+---
+
+Hallo Serkan,
+
+auf deiner Seite mit didaktischen Ressourcen fehlt ein Weg, Audiodateien oder Notenlinks direkt im Unterricht zugÃ¤nglich zu machen '” ohne dass SchÃ¼ler erst eine URL eintippen mÃ¼ssen.
+
+qrmaster.net macht genau das: QR-Code in Sekunden, kein Account, keine Werbung. Dynamische QR-Codes lassen sich nachtrÃ¤glich umleiten, falls sich ein Link Ã¤ndert.
+
+Passt das in deine Sammlung?
+
+Viele GrÃ¼ÃŸe  
+[Dein Name]
+
+---
+
+### 11. PHSG '” ICT-Kompetenzen *(Tier 3)*
+- **URL:** https://blogs.phsg.ch/ict-kompetenzen/ressourcen/scratch/
+- **Zielgruppe:** Lehrer (DACH)
+- **Kontakt:** info@phsg.ch
+
+**Betreff:** ErgÃ¤nzung zu euren ICT-Ressourcen
+
+---
+
+Hallo,
+
+eure ICT-Ressourcen-Seite deckt Medien und Programmierung gut ab '” Tools wie Scratch stehen im Mittelpunkt. Was fehlt: ein einfaches Werkzeug, um Links zu solchen Projekten direkt im Unterricht per QR-Code zu teilen.
+
+qrmaster.net ist kostenlos und ohne Anmeldung nutzbar. Mit dynamischen QR-Codes lÃ¤sst sich der Ziel-Link auch nachtrÃ¤glich noch Ã¤ndern.
+
+WÃ¤re das eine ErgÃ¤nzung, die ihr in Betracht ziehen wÃ¼rdet?
+
+Herzliche GrÃ¼ÃŸe  
+[Dein Name]
+
+---
+
+### 13. Kunstunterricht Ideen '” Simon *(Tier 3)*
+- **URL:** https://kunstunterricht-ideen.de/kunstunterricht-home-online-ressourcen-fuer-den-kunstunterricht-im-homeschooling/
+- **Zielgruppe:** Lehrer (DACH)
+- **Kontakt:** simon@kunstunterricht-ideen.de
+
+**Betreff:** Tool-Tipp fÃ¼r deine Online-Ressourcen
+
+---
+
+Hallo Simon,
+
+auf deiner Ressourcen-Seite fÃ¼r Kunstunterricht und Homeschooling fehlt ein praktisches Werkzeug: ein QR-Code-Generator. Damit kÃ¶nnen LehrkrÃ¤fte Links zu digitalen Museen, YouTube-Tutorials oder ArbeitsblÃ¤ttern direkt auf Ausdrucke packen '” SchÃ¼ler scannen, sind sofort da.
+
+qrmaster.net: kostenlos, werbefrei, kein Account nÃ¶tig. Dynamische QR-Codes erlauben nachtrÃ¤gliche Ã„nderungen ohne Neu-Druck.
+
+WÃ¤re das etwas fÃ¼r deine Liste?
+
+Kreative GrÃ¼ÃŸe  
+[Dein Name]
+
+---
+
+## English '” Teachers
+
+---
+
+### 5. EssayGrader *(Tier 2)*
+- **URL:** https://www.essaygrader.ai/blog/digital-resources-for-teachers
+- **Zielgruppe:** Lehrer (EN)
+- **Kontakt:** support@essaygrader.ai
+
+**Subject:** one gap in your 76-resource list
+
+---
+
+Hi,
+
+Your teacher resource list covers a lot of ground. One thing that's missing: a QR code generator.
+
+Teachers use them constantly '” to link printed handouts to digital content, to set up learning stations, to share reading lists without students typing URLs. Dynamic QR codes mean the destination can be updated later without reprinting.
+
+qrmaster.net is free, no signup required.
+
+Would it fit your inclusion criteria?
+
+Best,  
+[Your Name]
+
+---
+
+### 8. Teaching Channel *(Tier 1)*
+- **URL:** https://www.teachingchannel.com/k12-hub/blog/10-digital-resources-for-teachers/
+- **Zielgruppe:** Lehrer (EN)
+- **Kontakt:** support@teachingchannel.com
+
+**Subject:** missing tool from your digital resources list
+
+---
+
+Hi,
+
+Your roundup of 10 digital resources covers a solid range '” from classroom management to assessment tools. One tool that's consistently underrepresented on these lists: a QR code generator.
+
+Teachers use them to bridge physical and digital '” printed worksheet links to a video, classroom poster to an assignment, library book to an audiobook. Dynamic QR codes let teachers update the destination without reprinting materials.
+
+qrmaster.net is free and works without an account.
+
+Would it be a fit for your list?
+
+Best,  
+[Your Name]
+
+---
+
+### 9. Teachers of Tomorrow *(Tier 2)*
+- **URL:** https://www.teachersoftomorrow.org/blog/insights/teaching-resources-for-teachers/
+- **Zielgruppe:** Lehrer (EN)
+- **Kontakt:** MediaRelations@TeachersofTomorrow.org
+
+**Subject:** resource suggestion for new teachers
+
+---
+
+Hi,
+
+Your guide on teaching resources is a solid reference for new educators. One practical gap: no QR code generator.
+
+New teachers especially lean on QR codes to set up learning stations, share links without a projector, or make printed materials interactive. It's low-tech on the student side, low-effort on the teacher side. Dynamic codes mean the link can change without reprinting.
+
+qrmaster.net: free, no account needed.
+
+Does it fit what you'd add to the guide?
+
+Best,  
+[Your Name]
+
+---
+
+### 10. Montgomery College '” CTL *(Tier 2)*
+- **URL:** https://mcblogs.montgomerycollege.edu/thehub/teaching-resources/tech-tools-to-support-teaching-and-learning/
+- **Zielgruppe:** Lehrer/Dozenten (EN)
+- **Kontakt:** CTL@montgomerycollege.edu
+
+**Subject:** tool suggestion for your tech tools page
+
+---
+
+Hi CTL Team,
+
+Your "Tech Tools to Support Teaching and Learning" page is a useful reference for faculty. One tool that seems to be missing: a QR code generator.
+
+Instructors use them to link printed syllabi or handouts directly to online resources '” students scan instead of typing. Dynamic QR codes let faculty update the destination mid-semester without reprinting.
+
+qrmaster.net is free and requires no account.
+
+Would it be worth adding to your list?
+
+Best,  
+[Your Name]
+
+---
+
+### 14. TeachThought '” Terry *(Tier 1)*
+- **URL:** https://www.teachthought.com/literacy-posts/21-literacy-resources-for-the-digital-teacher/
+- **Zielgruppe:** Lehrer (EN)
+- **Kontakt:** terry@teachthought.com
+
+**Subject:** gap in your 21 literacy resources
+
+---
+
+Hi Terry,
+
+Your 21 literacy resources list covers annotation tools, digital storytelling, and reading platforms '” but no way to connect a physical book or handout to a digital resource in the room.
+
+A QR code generator does that '” teachers print a QR code, students scan and land on the digital text. No typing, no searching. Dynamic codes mean the destination can be updated without reprinting.
+
+qrmaster.net is free and works without an account.
+
+Would it fit alongside your existing literacy tools?
+
+Best,  
+[Your Name]
+
+---
+
+## English '” Founders / Small Business
+
+---
+
+### 3. The Startup Project *(Tier 2)*
+- **URL:** https://startupproject.org/blog/startup-resources-everything-you-need/
+- **Zielgruppe:** GrÃ¼nder (EN)
+- **Kontakt:** hello@startupproject.org
+
+**Subject:** missing tool in your startup resources
+
+---
+
+Hi,
+
+Your startup resource list covers a lot of the bases '” product, funding, marketing. One gap I noticed: no QR code generator.
+
+Founders use them more than they expect '” product packaging, pitch decks, business cards, event booths. Dynamic QR codes are especially useful here: you can update where the code points after printing, which matters when decks or packaging get reused.
+
+qrmaster.net is free, no account, no watermark.
+
+Worth adding to the marketing tools section?
+
+Best,  
+[Your Name]
+
+---
+
+### 7. U.S. Chamber of Commerce '” Jeanette *(Tier 1)*
+- **URL:** https://www.uschamber.com/co/start/strategy/free-resources-for-small-businesses
+- **Zielgruppe:** Small Business (EN)
+- **Kontakt:** jmulvey@uschamber.com
+
+**Subject:** free tool gap in your small business resources
+
+---
+
+Hi Jeanette,
+
+Your list of free resources for small businesses is one of the more practical ones out there. One tool I'd expect to see that's not there: a QR code generator.
+
+Small business owners use them constantly '” restaurant menus, store signage, packaging, loyalty programs. Most free options are either limited or ad-heavy. qrmaster.net is 100% free, no account required, no ads '” and dynamic QR codes let owners update the destination without reprinting.
+
+Would it make sense to include it in the marketing tools section?
+
+Best,  
+[Your Name]
+
+---
+
+### 12. Super Monitoring Blog '” Stuart *(Tier 2)*
+- **URL:** https://www.supermonitoring.com/blog/top-5-resources-for-finding-hot-new-marketing-tools/
+- **Zielgruppe:** Marketer (EN)
+- **Kontakt:** stuart@surges.co
+
+**Subject:** tool your audience probably uses weekly
+
+---
+
+Hi Stuart,
+
+Your post on finding hot new marketing tools is a useful read. One category that's missing: QR code generators.
+
+Marketers use them constantly to bridge print and digital '” direct mail, event materials, product packaging, OOH. Most reach for the first free Google result, which tends to be ad-heavy or limited. qrmaster.net stands out: bulk generation, scan analytics, and dynamic QR codes '” all free, no account needed.
+
+Would it fit as a mention in the article?
+
+Cheers,  
+[Your Name]
+
+---
+
+## English '” Event Managers
+
+---
+
+### 4. Cadmium '” Jessie *(Tier 1)*
+- **URL:** https://www.gocadmium.com/resources/the-10-best-event-management-software-tools
+- **Zielgruppe:** Eventmanager (EN)
+- **Kontakt:** jessie.reyes@gocadmium.com
+
+**Subject:** one tool missing from your event management list
+
+---
+
+Hi Jessie,
+
+Your "10 best event management tools" covers the core stack well '” registration, scheduling, engagement. One gap: no QR code generator.
+
+Event planners use them at every stage '” check-in flows, session schedules, feedback forms, contactless menus. qrmaster.net handles bulk generation for larger events and includes scan analytics, so planners can see which QR codes actually got used '” useful for post-event reporting.
+
+Free, no signup needed.
+
+Would it make sense to add alongside your existing recommendations?
+
+Best,  
+[Your Name]
+
+---
+
+### 15. Tripleseat *(Tier 1)*
+- **URL:** https://tripleseat.com/event-planning-resources/
+- **Zielgruppe:** Eventmanager (EN)
+- **Kontakt:** info@tripleseat.com
+
+**Subject:** tool suggestion for your event planning resources
+
+---
+
+Hi,
+
+Your event planning resources page is a solid reference for hospitality professionals. One practical tool that seems to be missing: a QR code generator.
+
+Venue and event planners use them for digital menus, contactless check-ins, schedules, and post-event feedback. qrmaster.net supports bulk generation for multi-table or multi-session setups, and scan analytics show which codes were actually used '” a clean data point for event debriefs.
+
+Free, no account required.
+
+Would it fit your resource page?
+
+Best,  
+[Your Name]
+
+---
+
+## Follow-Up Template (nach 7 Tagen ohne Antwort)
+
+Nur einmal nachfassen, dann loslassen. Neuer Winkel '” kein "just checking in".
+
+**DACH:**
+
+> **Betreff:** kurze ErgÃ¤nzung '” [Seitenname]
+>
+> Hallo,
+>
+> noch ein kurzer Gedanke dazu: qrmaster.net wÃ¼rde in eurer Liste am besten unter [digitale Tools / Unterrichts-Tools / Ressourcen-Sektion] passen '” direkt nutzbar, ohne Anmeldung.
+>
+> Falls nicht passend, kein Problem '” kurze RÃ¼ckmeldung reicht.
+>
+> [Dein Name]
+
+**EN:**
+
+> **Subject:** one more thought '” [site name]
+>
+> Hi,
+>
+> Quick follow-up. If it helps place it: qrmaster.net would probably fit best in your [tools / resources / marketing tools] section '” it works without signup so readers can use it immediately without friction.
+>
+> No worries if it's not a fit.
+>
+> [Your Name]
+
+---
+
+## Tracking-Ãœbersicht
+
+| Tier | # | Ziel | Kontakt | Sprache | Segment | Gesendet | Antwort | Status |
+|------|---|------|---------|---------|---------|----------|---------|--------|
+| 1 | 2 | Promethean World | info@prometheanworld.com | DE | Lehrer | '” | '” | '” |
+| 1 | 4 | Cadmium (Jessie) | jessie.reyes@gocadmium.com | EN | Events | '” | '” | '” |
+| 1 | 7 | U.S. Chamber (Jeanette) | jmulvey@uschamber.com | EN | GrÃ¼nder | '” | '” | '” |
+| 1 | 8 | Teaching Channel | support@teachingchannel.com | EN | Lehrer | '” | '” | '” |
+| 1 | 14 | TeachThought (Terry) | terry@teachthought.com | EN | Lehrer | '” | '” | '” |
+| 1 | 15 | Tripleseat | info@tripleseat.com | EN | Events | '” | '” | '” |
+| 2 | 3 | The Startup Project | hello@startupproject.org | EN | GrÃ¼nder | '” | '” | '” |
+| 2 | 5 | EssayGrader | support@essaygrader.ai | EN | Lehrer | '” | '” | '” |
+| 2 | 9 | Teachers of Tomorrow | MediaRelations@TeachersofTomorrow.org | EN | Lehrer | '” | '” | '” |
+| 2 | 10 | Montgomery College CTL | CTL@montgomerycollege.edu | EN | Lehrer | '” | '” | '” |
+| 2 | 12 | Super Monitoring (Stuart) | stuart@surges.co | EN | Marketer | '” | '” | '” |
+| 3 | 1 | eEducation Austria | eeducation@bildung.gv.at | DE | Lehrer | '” | '” | '” |
+| 3 | 6 | Serkan Cagatay | info@serkancagatay.com | DE | Lehrer | '” | '” | '” |
+| 3 | 11 | PHSG ICT | info@phsg.ch | DE | Lehrer | '” | '” | '” |
+| 3 | 13 | Kunstunterricht (Simon) | simon@kunstunterricht-ideen.de | DE | Lehrer | '” | '” | '” |
+
+---
+
+## Guest Post Pitches
+
+â†’ Ausgelagert in eigenes File: **[guest-post-pitches.md](./guest-post-pitches.md)**
+
+EnthÃ¤lt:
+- DigitalGpoint Submission
+- Techdee Submission (Tier 2)
+- SEO Sandwitch Submission (Tier 1)
+- HubSpot / MarketingProfs (SKIP)
+- Web 2.0 Stack (Phase A '” kein Editor nÃ¶tig)
+- Charles Floate List '” Tier 1/2/3 Shortlist mit Pitch-Angles
+- 4-Wochen Execution Plan + Tracking-Tabelle
+
--- a/package-lock.json
+++ b/package-lock.json
--- a/package.json
+++ b/package.json
@@ -5,9 +5,12 @@
  "private": true,
  "scripts": {
    "dev": "next dev -p 3050",
-    "build": "prisma generate && next build",
+    "build": "node scripts/build.js",
+    "trigger:indexing": "tsx scripts/trigger-indexing.ts",
+    "submit:indexnow": "tsx scripts/submit-indexnow.ts",
    "start": "next start",
    "lint": "next lint",
+    "indexnow": "tsx scripts/submit-indexnow.ts",
    "db:generate": "prisma generate",
    "db:migrate": "prisma migrate dev",
    "db:deploy": "prisma migrate deploy",
@@ -26,37 +29,49 @@
  },
  "dependencies": {
    "@auth/prisma-adapter": "^2.11.1",
+    "@aws-sdk/client-s3": "^3.972.0",
+    "@aws-sdk/s3-request-presigner": "^3.972.0",
    "@edge-runtime/cookies": "^6.0.0",
    "@prisma/client": "^5.7.0",
    "@stripe/stripe-js": "^8.0.0",
    "@types/d3-scale": "^4.0.9",
+    "@types/nodemailer": "^7.0.11",
+    "axios": "^1.13.2",
    "bcryptjs": "^2.4.3",
    "chart.js": "^4.4.0",
    "clsx": "^2.0.0",
+    "copy-image-clipboard": "^2.1.2",
    "d3-scale": "^4.0.2",
    "dayjs": "^1.11.10",
+    "dotenv": "^17.2.3",
    "exceljs": "^4.4.0",
    "file-saver": "^2.0.5",
    "framer-motion": "^12.24.10",
+    "googleapis": "^170.1.0",
+    "html-to-image": "^1.11.13",
    "i18next": "^23.7.6",
    "ioredis": "^5.3.2",
+    "jspdf": "^4.0.0",
    "jszip": "^3.10.1",
    "lucide-react": "^0.562.0",
    "next": "^14.2.35",
    "next-auth": "^4.24.5",
+    "nodemailer": "^8.0.4",
    "papaparse": "^5.4.1",
-    "posthog-js": "^1.276.0",
+    "posthog-js": "^1.332.0",
    "qr-code-styling": "^1.9.2",
    "qrcode": "^1.5.3",
    "qrcode.react": "^3.1.0",
    "react": "^18.2.0",
+    "react-barcode": "^1.6.1",
    "react-chartjs-2": "^5.2.0",
    "react-dom": "^18.2.0",
    "react-dropzone": "^14.2.3",
+    "react-facebook-pixel": "^1.0.4",
    "react-i18next": "^13.5.0",
    "react-simple-maps": "^3.0.0",
    "resend": "^6.4.2",
-    "sharp": "^0.33.1",
+    "sanitize-html": "^2.17.1",
    "stripe": "^19.1.0",
    "tailwind-merge": "^2.2.0",
    "uuid": "^13.0.0",
@@ -70,13 +85,15 @@
    "@types/qrcode": "^1.5.5",
    "@types/react": "^18.2.45",
    "@types/react-dom": "^18.2.18",
+    "@types/sanitize-html": "^2.16.0",
    "autoprefixer": "^10.4.16",
+    "cross-env": "^10.1.0",
    "eslint": "^8.56.0",
-    "eslint-config-next": "^16.1.1",
-    "next-sitemap": "^4.2.3",
+    "eslint-config-next": "16.1.5",
    "postcss": "^8.4.32",
    "prettier": "^3.1.1",
    "prisma": "^5.7.0",
+    "sharp": "^0.34.5",
    "tailwindcss": "^3.3.6",
    "tsx": "^4.7.0",
    "typescript": "^5.3.3"
--- a/postcss.config.js
+++ b/postcss.config.js
@@ -1,6 +1,6 @@
-module.exports = {
-  plugins: {
-    tailwindcss: {},
-    autoprefixer: {},
-  },
+module.exports = {
+  plugins: {
+    tailwindcss: {},
+    autoprefixer: {},
+  },
 }
--- a/prisma/migrations/20251013172642_init/migration.sql
+++ b/prisma/migrations/20251013172642_init/migration.sql
@@ -0,0 +1,146 @@
+-- CreateEnum
+CREATE TYPE "QRType" AS ENUM ('STATIC', 'DYNAMIC');
+
+-- CreateEnum
+CREATE TYPE "ContentType" AS ENUM ('URL', 'WIFI', 'VCARD', 'PHONE', 'EMAIL', 'SMS', 'TEXT', 'WHATSAPP');
+
+-- CreateEnum
+CREATE TYPE "QRStatus" AS ENUM ('ACTIVE', 'PAUSED');
+
+-- CreateTable
+CREATE TABLE "User" (
+    "id" TEXT NOT NULL,
+    "email" TEXT NOT NULL,
+    "name" TEXT,
+    "password" TEXT,
+    "image" TEXT,
+    "emailVerified" TIMESTAMP(3),
+    "createdAt" TIMESTAMP(3) NOT NULL DEFAULT CURRENT_TIMESTAMP,
+    "updatedAt" TIMESTAMP(3) NOT NULL,
+
+    CONSTRAINT "User_pkey" PRIMARY KEY ("id")
+);
+
+-- CreateTable
+CREATE TABLE "Account" (
+    "id" TEXT NOT NULL,
+    "userId" TEXT NOT NULL,
+    "type" TEXT NOT NULL,
+    "provider" TEXT NOT NULL,
+    "providerAccountId" TEXT NOT NULL,
+    "refresh_token" TEXT,
+    "access_token" TEXT,
+    "expires_at" INTEGER,
+    "token_type" TEXT,
+    "scope" TEXT,
+    "id_token" TEXT,
+    "session_state" TEXT,
+
+    CONSTRAINT "Account_pkey" PRIMARY KEY ("id")
+);
+
+-- CreateTable
+CREATE TABLE "Session" (
+    "id" TEXT NOT NULL,
+    "sessionToken" TEXT NOT NULL,
+    "userId" TEXT NOT NULL,
+    "expires" TIMESTAMP(3) NOT NULL,
+
+    CONSTRAINT "Session_pkey" PRIMARY KEY ("id")
+);
+
+-- CreateTable
+CREATE TABLE "VerificationToken" (
+    "identifier" TEXT NOT NULL,
+    "token" TEXT NOT NULL,
+    "expires" TIMESTAMP(3) NOT NULL
+);
+
+-- CreateTable
+CREATE TABLE "QRCode" (
+    "id" TEXT NOT NULL,
+    "userId" TEXT NOT NULL,
+    "title" TEXT NOT NULL,
+    "type" "QRType" NOT NULL DEFAULT 'DYNAMIC',
+    "contentType" "ContentType" NOT NULL DEFAULT 'URL',
+    "content" JSONB NOT NULL,
+    "tags" TEXT[],
+    "status" "QRStatus" NOT NULL DEFAULT 'ACTIVE',
+    "style" JSONB NOT NULL,
+    "slug" TEXT NOT NULL,
+    "createdAt" TIMESTAMP(3) NOT NULL DEFAULT CURRENT_TIMESTAMP,
+    "updatedAt" TIMESTAMP(3) NOT NULL,
+
+    CONSTRAINT "QRCode_pkey" PRIMARY KEY ("id")
+);
+
+-- CreateTable
+CREATE TABLE "QRScan" (
+    "id" TEXT NOT NULL,
+    "qrId" TEXT NOT NULL,
+    "ts" TIMESTAMP(3) NOT NULL DEFAULT CURRENT_TIMESTAMP,
+    "ipHash" TEXT NOT NULL,
+    "userAgent" TEXT,
+    "device" TEXT,
+    "os" TEXT,
+    "country" TEXT,
+    "referrer" TEXT,
+    "utmSource" TEXT,
+    "utmMedium" TEXT,
+    "utmCampaign" TEXT,
+    "isUnique" BOOLEAN NOT NULL DEFAULT false,
+
+    CONSTRAINT "QRScan_pkey" PRIMARY KEY ("id")
+);
+
+-- CreateTable
+CREATE TABLE "Integration" (
+    "id" TEXT NOT NULL,
+    "userId" TEXT NOT NULL,
+    "provider" TEXT NOT NULL,
+    "status" TEXT NOT NULL DEFAULT 'inactive',
+    "config" JSONB NOT NULL,
+    "createdAt" TIMESTAMP(3) NOT NULL DEFAULT CURRENT_TIMESTAMP,
+    "updatedAt" TIMESTAMP(3) NOT NULL,
+
+    CONSTRAINT "Integration_pkey" PRIMARY KEY ("id")
+);
+
+-- CreateIndex
+CREATE UNIQUE INDEX "User_email_key" ON "User"("email");
+
+-- CreateIndex
+CREATE UNIQUE INDEX "Account_provider_providerAccountId_key" ON "Account"("provider", "providerAccountId");
+
+-- CreateIndex
+CREATE UNIQUE INDEX "Session_sessionToken_key" ON "Session"("sessionToken");
+
+-- CreateIndex
+CREATE UNIQUE INDEX "VerificationToken_token_key" ON "VerificationToken"("token");
+
+-- CreateIndex
+CREATE UNIQUE INDEX "VerificationToken_identifier_token_key" ON "VerificationToken"("identifier", "token");
+
+-- CreateIndex
+CREATE UNIQUE INDEX "QRCode_slug_key" ON "QRCode"("slug");
+
+-- CreateIndex
+CREATE INDEX "QRCode_userId_createdAt_idx" ON "QRCode"("userId", "createdAt");
+
+-- CreateIndex
+CREATE INDEX "QRScan_qrId_ts_idx" ON "QRScan"("qrId", "ts");
+
+-- AddForeignKey
+ALTER TABLE "Account" ADD CONSTRAINT "Account_userId_fkey" FOREIGN KEY ("userId") REFERENCES "User"("id") ON DELETE CASCADE ON UPDATE CASCADE;
+
+-- AddForeignKey
+ALTER TABLE "Session" ADD CONSTRAINT "Session_userId_fkey" FOREIGN KEY ("userId") REFERENCES "User"("id") ON DELETE CASCADE ON UPDATE CASCADE;
+
+-- AddForeignKey
+ALTER TABLE "QRCode" ADD CONSTRAINT "QRCode_userId_fkey" FOREIGN KEY ("userId") REFERENCES "User"("id") ON DELETE CASCADE ON UPDATE CASCADE;
+
+-- AddForeignKey
+ALTER TABLE "QRScan" ADD CONSTRAINT "QRScan_qrId_fkey" FOREIGN KEY ("qrId") REFERENCES "QRCode"("id") ON DELETE CASCADE ON UPDATE CASCADE;
+
+-- AddForeignKey
+ALTER TABLE "Integration" ADD CONSTRAINT "Integration_userId_fkey" FOREIGN KEY ("userId") REFERENCES "User"("id") ON DELETE CASCADE ON UPDATE CASCADE;
--- a/prisma/migrations/20251014195005_init/migration.sql
+++ b/prisma/migrations/20251014195005_init/migration.sql
@@ -0,0 +1,22 @@
+/*
+  Warnings:
+
+  - A unique constraint covering the columns `[stripeCustomerId]` on the table `User` will be added. If there are existing duplicate values, this will fail.
+  - A unique constraint covering the columns `[stripeSubscriptionId]` on the table `User` will be added. If there are existing duplicate values, this will fail.
+
+*/
+-- CreateEnum
+CREATE TYPE "Plan" AS ENUM ('FREE', 'PRO', 'BUSINESS');
+
+-- AlterTable
+ALTER TABLE "User" ADD COLUMN     "plan" "Plan" NOT NULL DEFAULT 'FREE',
+ADD COLUMN     "stripeCurrentPeriodEnd" TIMESTAMP(3),
+ADD COLUMN     "stripeCustomerId" TEXT,
+ADD COLUMN     "stripePriceId" TEXT,
+ADD COLUMN     "stripeSubscriptionId" TEXT;
+
+-- CreateIndex
+CREATE UNIQUE INDEX "User_stripeCustomerId_key" ON "User"("stripeCustomerId");
+
+-- CreateIndex
+CREATE UNIQUE INDEX "User_stripeSubscriptionId_key" ON "User"("stripeSubscriptionId");
--- a/Show More
+++ b/Show More
Author	SHA1	Message	Date
Timo Knuth	65fe18a718	dynamisch barcode	2026-04-14 19:46:14 +02:00
Timo Knuth	6b73ac5c50	feat: implement pricing strategy, subscription tiers, and core infrastructure for QR code management	2026-04-14 19:34:47 +02:00
Timo Knuth	82101ca08f	aufräumen	2026-04-14 11:21:17 +02:00
Timo Knuth	ff3294291f	blog and backlinks	2026-04-14 10:35:29 +02:00
Timo Knuth	f5fd33a304	feat: add marketing resources, technical documentation, and email outreach templates for bulk QR code generation	2026-04-14 10:29:47 +02:00
Timo Knuth	79e54f8ae2	feat: add dynamic barcode generator landing page, testimonial data, and update project planning documentation	2026-04-12 23:41:33 +02:00
Timo Knuth	6ccab068d8	feat: add SEO outreach templates, testimonial components, and supporting data schemas	2026-04-12 23:41:32 +02:00
Andreas Knuth	434b5954c1	solve permission problem	2026-04-12 14:51:37 -05:00
Andreas Knuth	bbc26f200b	rm ports	2026-04-12 14:28:46 -05:00
Timo Knuth	b1d7d95d6f	feat: add Instagram QR code generator tool page and SEO outreach documentation	2026-04-12 12:13:18 +02:00
Timo Knuth	9a01523fcd	feat: implement marketing pages, core QR tools, and SEO infrastructure for QR Master	2026-04-10 11:21:18 +02:00
Timo Knuth	cc4afb6f51	feat: implement author pages, app layout, and authentication client infrastructure	2026-04-08 19:39:01 +02:00
Timo Knuth	14c3cde7e6	feat: implement marketing comparison and alternatives hub with dedicated competitor landing pages	2026-04-08 15:38:02 +02:00
Timo Knuth	a6fd2ed61f	feat: add marketing landing pages and tools for dynamic QR codes and analytics	2026-04-07 14:50:16 +02:00
Timo Knuth	8408159a96	feat: implement blog infrastructure, add SEO keyword planning, and create footer component	2026-04-04 23:50:45 +02:00
Timo Knuth	3143561d27	feat: add permanent redirects for legacy QR code landing page slugs	2026-04-04 20:17:26 +02:00
Timo Knuth	fe00bede47	Migration	2026-04-03 00:31:20 +02:00
Timo Knuth	97a6cc11f7	Configuraion	2026-04-03 00:19:18 +02:00
Timo Knuth	7afd39c18c	Email retention	2026-04-02 11:37:58 +02:00
Timo	1cff96a553	md files	2026-04-01 19:50:02 +02:00
Timo Knuth	fb70b433c7	Industries	2026-03-31 18:46:01 +02:00
Timo Knuth	33b5191093	Ahrefs fehler.	2026-03-26 10:56:50 -05:00
Timo Knuth	e540bf3122	Ahrefs fehler	2026-03-24 10:05:03 -05:00
Timo Knuth	e6b19e7a1c	search console SEO ableitungen	2026-03-23 19:01:52 -05:00
Timo Knuth	d47108d27c	SEO	2026-03-12 15:54:56 +01:00
Timo Knuth	3c8e6bd19f	feat: Add marketing and use case pages, their data structures, and supporting UI components.	2026-03-09 12:47:52 +01:00
Timo	f5f3979996	deps: update sanitize-html to 2.17.1	2026-03-06 17:49:27 +01:00
Timo Knuth	8a53b515d1	Blog post.	2026-03-06 17:25:59 +01:00
Timo Knuth	62dc048745	Blog post	2026-03-06 16:15:39 +01:00
Timo Knuth	455f7e090e	feat: add inline citations and sources to Tier 1 AEO/GEO posts Add inline <cite> tags with source links to boost AI search visibility: - trackable-qr-codes: Added 2 citations (Mordor Intelligence, QR Code Tiger) - qr-code-scan-statistics-2026: Added sources array + 2 citations - utm-parameter-qr-codes: Added sources array + 1 citation - dynamic-vs-static-qr-codes: Added sources array + 1 citation Sources include Bitly, Mordor Intelligence, QR Code Tiger, and Statista. Estimated +40% AI citation visibility boost from inline citations per Princeton GEO research.	2026-03-06 16:01:58 +01:00
Timo Knuth	76bde71585	fix: correct metadata dates, remove draft note, remove duplicate section - Fixed all 'undefined NaN, NaN' dates in metadata divs across all 22 posts - Removed draft instruction from qr-code-scan-statistics-2026 - Removed duplicate 'Trackable / dynamic QR code' section from trackable-qr-codes - All posts now have proper 'Last updated' dates showing January 26, 2026	2026-03-06 16:01:01 +01:00
Timo Knuth	7d5d142156	feat: Implement AEO/GEO optimization - add schema markup with author attribution and metadata divs - Updated schema.ts: blogPostingSchema and howToSchema now use post.authorName and post.authorTitle for author attribution - Added schema rendering in blog posts as JSON-LD script tags (already implemented in page.tsx) - Added metadata divs to all 22 blog posts with: * Author name and title (Timo Knuth, QR Code & Marketing Expert) * Publication and last updated dates * Styled with blue accent border for AEO/GEO visibility - Fixed date formatting in metadata divs to properly display publish and update dates - Removed draft notes from published content Impact: - All posts now include author attribution in schema (improves AI citation likelihood +25%) - Schema markup supports HowTo and FAQPage generation for qualified posts - Metadata visually emphasizes authority and freshness signals - +25-40% potential improvement in AI search visibility with full implementation Files modified: - src/lib/blog-data.ts: Added authorName/authorTitle fields + metadata divs - src/lib/schema.ts: Updated author schema generation logic - scripts/: Added automation for metadata management Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>	2026-03-06 15:53:30 +01:00
Timo Knuth	df2663b14f	feat: Add Timo Knuth author metadata to all 22 blog posts for AEO/GEO optimization - Add authorName and authorTitle fields to all 22 blog posts - Update BlogPost type definition to include optional authorName and authorTitle fields - Set author to 'Timo Knuth' with title 'QR Code & Marketing Expert' across all posts - Foundation for schema markup and AI search optimization (AEO/GEO) Co-Authored-By: Timo Knuth <noreply@qrmaster.net>	2026-03-06 15:32:32 +01:00
Timo Knuth	6e8bf2ab08	feat: Implement new root layout with SEO metadata and analytics, add various Open Graph images and a favicon, and remove old documentation files.	2026-02-17 17:19:35 +01:00
Timo Knuth	f3774f3068	feat: Implement analytics tracking with cookie consent and enhance SEO with backlink management.	2026-02-09 16:07:39 +01:00
Timo Knuth	e871c820f7	Quellen	2026-02-09 11:33:24 +01:00
Timo Knuth	db93e678ee	AEO/GEO	2026-02-05 12:42:16 +01:00
Timo Knuth	47e54a4464	feat: Add Press & News page and implement website and organization schema for SEO.	2026-02-04 15:20:40 +01:00
Timo Knuth	c996765618	GSC	2026-01-29 11:30:00 +01:00
Timo Knuth	f1352b46a5	1 Datei wikidata	2026-01-28 19:15:49 +01:00
Timo Knuth	a76bcb70e1	skills	2026-01-28 16:02:32 +01:00
Timo Knuth	1a6dc01291	okay	2026-01-27 17:27:47 +01:00
Timo Knuth	4dc7c29134	press releases	2026-01-27 12:29:44 +01:00
Timo Knuth	be5db36b7f	hydration error	2026-01-27 11:08:32 +01:00
Timo Knuth	76a76258e8	fixes	2026-01-26 19:51:00 +01:00
Timo Knuth	7b2788da7a	Merge branch 'master' of https://gitea.bizmatch.net/tknuth/QR-master	2026-01-26 16:47:57 +01:00
Timo Knuth	2771faf3ba	14 blog post schedule	2026-01-26 16:43:47 +01:00
knuthtimo-lab	9e37136efd	seo issue	2026-01-26 00:28:26 +01:00
knuthtimo-lab	4569d89ab2	Fix: Add Facebook Pixel ID to Dockerfile	2026-01-26 00:23:15 +01:00
knuthtimo-lab	916ea51d68	facebook..	2026-01-25 23:49:43 +01:00
knuthtimo-lab	8ade0ef92b	facebook.	2026-01-25 23:38:28 +01:00
knuthtimo-lab	7e894bf65e	facebook	2026-01-25 23:10:03 +01:00
knuthtimo-lab	54c3652c99	Werbung	2026-01-25 22:28:47 +01:00
Timo Knuth	702e2710de	seo	2026-01-25 18:44:53 +01:00
Timo Knuth	9ae05d48a4	faq	2026-01-25 18:00:57 +01:00
Timo Knuth	324526cb64	fehler	2026-01-25 15:57:03 +01:00
Timo Knuth	9040e50837	ahrefs	2026-01-25 15:43:38 +01:00
Timo Knuth	30c1e57eab	Shema	2026-01-25 14:59:25 +01:00
Timo Knuth	eef4855c1b	SEO: Fix structured data validation errors, delete static sitemap, and update indexing scripts	2026-01-23 23:10:22 +01:00
Andreas Knuth	f3637fc2fe	URL changed	2026-01-23 15:41:56 -06:00
Andreas Knuth	53dcfb686e	Einrueckung falsch	2026-01-23 15:32:18 -06:00
Timo Knuth	74d0b5e7f2	Hardcode+middleware	2026-01-23 20:48:09 +01:00
Timo Knuth	ce4c6ab985	hardcoded	2026-01-23 18:08:29 +01:00
Timo Knuth	c2b32b794b	docker-compose	2026-01-23 17:48:08 +01:00
Timo Knuth	7f4de4bd1e	Add R2 storage environment variables to docker-compose.yml	2026-01-23 17:34:13 +01:00
Timo Knuth	738f9766e1	Fix: Remove prisma/migrations from .dockerignore to enable deployment	2026-01-23 17:02:06 +01:00
Timo Knuth	cbafffdf1b	Add Prisma migrations to version control - fixes deployment sync issue	2026-01-23 16:22:07 +01:00
Timo Knuth	f872fb64b2	ads.	2026-01-23 14:54:02 +01:00
Timo Knuth	9c5f7beb91	ads	2026-01-23 14:45:25 +01:00
Timo Knuth	cb521f2aee	AEO / SEO	2026-01-23 14:39:27 +01:00
Timo Knuth	b00697bc37	Add migration for new ContentType enum values (APP, COUPON, FEEDBACK, PDF)	2026-01-23 09:28:31 +01:00
knuthtimo-lab	0409fe2afd	Final!	2026-01-22 22:24:06 +01:00
knuthtimo-lab	f67945d8e7	Final	2026-01-22 22:05:06 +01:00
knuthtimo-lab	59131a54f0	Paar fehler	2026-01-22 20:09:54 +01:00
Timo	e44dc1c6bb	Merge branch 'dynamisch' into master (favoring dynamisch changes)	2026-01-22 19:37:15 +01:00
knuthtimo-lab	3682673852	Final	2026-01-22 19:31:05 +01:00
Timo Knuth	1251584b13	fix	2026-01-22 16:33:29 +01:00
Timo Knuth	dd93ca560a	fix(marketing): Update hero animation timing and move Free Forever badge	2026-01-22 16:26:23 +01:00
Timo Knuth	efb1654370	fix: Optimize flipping card animation backface and timing	2026-01-22 15:46:31 +01:00
Timo Knuth	896c9b1a07	feat: Implement a client-side barcode generator tool and integrate IndexNow API for site URL submission.	2026-01-21 22:39:04 +01:00
Timo Knuth	cca1374c9e	feat: Introduce Google Indexing API and IndexNow submission scripts with a unified URL gathering utility and setup guide.	2026-01-21 13:57:58 +01:00
Timo Knuth	c1471830f3	feat: Add a new barcode generator tool with client-side functionality, supporting components, and a Google Indexing script.	2026-01-21 13:43:46 +01:00
knuthtimo-lab	373e19a515	barcode	2026-01-21 08:19:53 +01:00
Timo Knuth	99acb37c83	3 neue Blog post	2026-01-20 22:18:12 +01:00
knuthtimo-lab	7328b3240d	robots	2026-01-17 16:19:37 +01:00
Timo Knuth	185c40f470	Add missing migration for Lead table.	2026-01-16 17:40:17 +01:00
Timo Knuth	9373db8ae6	Add missing migration for Lead table	2026-01-16 17:17:45 +01:00
Timo Knuth	0eafe421d2	Lead fehler	2026-01-16 16:49:27 +01:00
Timo Knuth	af1c0456d7	fehler api	2026-01-16 16:17:58 +01:00
Timo Knuth	2dec18fc97	100/100	2026-01-16 14:41:42 +01:00
knuthtimo-lab	2879fd0d8e	Lead Magnet implementiert	2026-01-16 14:16:46 +01:00
Timo Knuth	be54d388bb	Lead Magnet	2026-01-16 12:44:13 +01:00
Timo Knuth	83ea141230	Ahrefs 96->100	2026-01-15 10:14:40 +01:00
Timo Knuth	0a02876ea4	bilder komprimieren	2026-01-14 15:30:32 +01:00
Timo Knuth	904e439102	neuer versuch.	2026-01-14 14:32:05 +01:00
Timo Knuth	f68b7a331c	neuer versuch	2026-01-14 14:02:48 +01:00
knuthtimo-lab	1747922b29	Ahrefs problems >95	2026-01-13 23:55:39 +01:00
knuthtimo-lab	8b7deb9312	Ahrefs problems >90	2026-01-13 23:50:51 +01:00
knuthtimo-lab	6b586ac21b	Ahrefs problems 2	2026-01-13 23:18:58 +01:00
knuthtimo-lab	3e9daa648a	Ahrefs problems	2026-01-13 23:10:35 +01:00
knuthtimo-lab	ceb2ac40ec	Ahrefs	2026-01-13 19:03:33 +01:00
knuthtimo-lab	65def796ea	Fehler....	2026-01-13 17:08:06 +01:00
knuthtimo-lab	e9bc1fe98b	Fehler...	2026-01-13 17:03:49 +01:00
Timo Knuth	b63f5f424e	Fehler..	2026-01-13 16:43:58 +01:00
Timo Knuth	9746fb970d	Fehler.	2026-01-13 16:39:04 +01:00
Timo Knuth	fb788d89d3	Fehler	2026-01-13 16:35:02 +01:00
Timo Knuth	d585e5aed3	seo blog post	2026-01-13 12:08:34 +01:00
Timo Knuth	fa538b8bec	Seobility und Ahrefs 100/100 score fixes final	2026-01-13 10:07:10 +01:00
Timo Knuth	4fc1dcd7d8	Seobility und Ahrefs 100/100 score fixes	2026-01-13 09:59:40 +01:00
Timo Knuth	ffe4cca5e5	Seobility und Ahrefs 100/100 score	2026-01-13 08:49:35 +01:00
Timo Knuth	5b74b7b405	Adsense fehler	2026-01-12 17:36:38 +01:00
Timo Knuth	5784a52e3c	Adsense	2026-01-12 17:22:20 +01:00
Timo Knuth	b3e858c033	fehler behoben	2026-01-12 17:09:47 +01:00
Timo Knuth	111575aeda	Final	2026-01-12 16:56:52 +01:00
Timo Knuth	beed961eef	feat: add Google Search Console verification and llms.txt	2026-01-12 15:41:35 +01:00
Timo Knuth	95aa378763	feat: add llms.txt for AI transparency	2026-01-12 15:24:08 +01:00
Timo Knuth	e0871e2960	chore: normalize line endings	2026-01-12 14:15:03 +01:00
Timo Knuth	038c8dddbc	feat: implement high-priority SEO fixes and German localization	2026-01-12 13:35:10 +01:00
Timo Knuth	c6adc8567f	schema	2026-01-11 17:26:35 +01:00
Timo Knuth	1f067e81f3	lighthouse	2026-01-11 17:11:28 +01:00
Timo Knuth	d64459b200	responsivness Phone	2026-01-11 11:50:17 +01:00
Timo Knuth	05531cda3f	4 neue dynamischen	2026-01-11 01:29:21 +01:00
Timo Knuth	268689f2ee	FAQ in NAV	2026-01-10 01:51:05 +01:00
Timo Knuth	fb9058688e	Fix, complete all tool updates	2026-01-10 00:26:05 +01:00
Timo Knuth	eb2faec952	feat: Add 19 free QR code tools with SEO optimization - Added PayPal, Zoom, Teams QR generators - Added lazy loading for html-to-image (performance) - Created 19 OG images for social sharing - Added robots.txt and updated sitemap - Fixed mobile navigation with accordion menu - Added 7 color options per generator - Fixed crypto QR with universal/wallet mode toggle - Hero QR codes all point to qrmaster.net	2026-01-10 00:22:07 +01:00
Timo Knuth	e539aaf9a1	feat: implement WiFi QR code generator and strategy docs	2026-01-09 12:01:01 +01:00