# Product Updates LLMS Process

**Last Updated:** 2026-04-08

Manual review workflow for adding product update pages to LLM files (`llms.txt` and `llms-full.txt`). Product update pages use a **manual review process**—do NOT use automated generation for content quality.

## Overview

When new product update pages are published, follow this process to add them to the appropriate LLM file(s). The process ensures ACAO compliance, semantic richness, and correct placement.

## Inclusion Criteria

### llms.txt (Essentials, ~80 URLs)

Include:
- **Main page** (`/produkt-updates`) – always
- **Month pages** – current month + last 2 months only
- **Feature posts** – top 3 from current month + last 2 months (by relevance/impact)

### llms-full.txt (Comprehensive, ~200+ URLs)

Include:
- **Main page** – always
- **Month pages** – all months
- **Feature posts** – all posts with `read_more_link` (standalone feature pages)

### Exclusion

- Feature posts **without** `read_more_link` – exclude (no dedicated page)

## Decision Tree

```
Main page? → Include in both files ✅

Month page?
├─ Current month or within last 2 months? → llms.txt ✅
└─ All months → llms-full.txt ✅

Feature post?
├─ Has read_more_link? → llms-full.txt ✅
├─ Top 3 from current + last 2 months? → llms.txt ✅
└─ No read_more_link? → Exclude ❌
```

## ACAO Checklist

Every entry **MUST** include all four ACAO components:

| Component | Purpose | Example |
|-----------|---------|---------|
| **(Action)** | What the user does / benefit | "Entdecke neueste Features" |
| **(Context)** | Background/conditions | "für Januar 2026", "von Ordio" |
| **(Advantage)** | Benefits/value | "mit 1 neuen Features", "mit Verbesserungen" |
| **(Outcome)** | Measurable results | "und 2 Verbesserungen", "für bessere Produktivität" |

## Step-by-Step: Adding a Product Update Page

### 1. Verify Page Exists

- [ ] Page loads (HTTP 200) at the exact path (follow redirects: URLs that end on `/produkt-updates` are **not** valid feature/month pages — remove them from LLMS)
- [ ] Canonical URL is correct
- [ ] Page is in production `sitemap-produkt-updates.xml` (or confirm intentional omission)
- [ ] **Diff check:** `curl -s https://www.ordio.com/sitemap-produkt-updates.xml | grep -o '<loc>[^<]*</loc>'` vs `grep produkt-updates/ html/llms-full.txt` — every **new** public URL should appear in `llms-full.txt`; `llms.txt` stays curated (current month + two prior months + top features per [Inclusion Criteria](#inclusion-criteria))

### 2. Review Page Quality

- [ ] Title tag: 50–60 characters
- [ ] Meta description: 155–160 characters
- [ ] Schema type correct (CollectionPage for months, BlogPosting for features)

### 3. Create Entry

Use the appropriate template below. Ensure all ACAO components are present.

### 4. Insert in Correct Section

- **Section:** "Produkt-Updates (Product Updates)"
- **Location:** After "Unternehmen", before "Kontakt & Support"
- **Order:** Main page first, then months (newest first), then feature posts (newest first)

### 5. Update Dates (if needed)

- Update "Last Updated" in file header to current date
- Run `date +%Y-%m-%d` for current date

### 6. Validate

- Run `python3 v2/scripts/llms/validate-llms-content.py --file both --sample 15`
- Verify no duplicate URLs
- Check section ordering

## Entry Format Templates

**Note:** Blog entries (Lexikon, Ratgeber, Inside Ordio) use a different tag format: `[TYPE: YYYY-MM-DD | CategoryLabel]`. See `docs/seo-strategy-2026/LLM_FILES_GUIDE.md` for the full tag format specification.

### Main Page

```
> [UPDATES: Monat | Features] Produkt-Updates - Entdecke neueste Features (Action) von Ordio (Context) mit monatlichen Updates (Advantage) und bleibe informiert (Outcome)
https://www.ordio.com/produkt-updates
```

### Month Page

```
> [UPDATE: {Month Title} | {Feature Count} Features | {Platforms}] {Month Name} Updates - {Intro Text} (Action) für {Month Name} (Context) mit {Feature Count} neuen Features (Advantage) und {Improvement Count} Verbesserungen (Outcome)
https://www.ordio.com/produkt-updates/{month-slug}
```

**Example:**
```
> [UPDATE: Januar 2026 | 1 Features | Desktop & Mobile] Januar 2026 Updates - Dieser Monat: Ordio Updates im Januar 2026 (Action) für Januar 2026 (Context) mit 1 neuen Features (Advantage) und 2 Verbesserungen (Outcome)
https://www.ordio.com/produkt-updates/januar-2026
```

### Feature Post

```
> [FEATURE: {Title} | {Tag} | {Platforms}] {Title} - {Description} (Action) von Ordio (Context) mit {Tag-specific Advantage} (Advantage) für bessere Produktivität (Outcome)
https://www.ordio.com/produkt-updates/{feature-slug}
```

**Example:**
```
> [FEATURE: Payroll Plus Update: Weniger Setup | Verbesserung | Desktop & Mobile] Payroll Plus Update: Weniger Setup, mehr Klarheit für alle - Wir haben Payroll Plus an mehreren Stellen weiter verbessert (Action) von Ordio (Context) mit Verbesserungen (Advantage) für bessere Produktivität (Outcome)
https://www.ordio.com/produkt-updates/payroll-plus-verbesserungen
```

## Tag Labels

| Tag Key | Label |
|---------|-------|
| neues-feature | Neues Feature |
| verbesserung | Verbesserung |
| bugfix | Bugfix |
| update | Update |
| sicherheit | Sicherheit |
| performance | Performance |

## Related Documentation

- `PRODUCT_UPDATES_LLMS_QUICK_REFERENCE.md` – One-page quick reference
- `NEXT_STEPS_LLMS.md` – Monthly maintenance checklist
- `.cursor/rules/llm-files.mdc` – Cursor AI rules for LLM files
- `docs/seo-strategy-2026/LLM_FILES_GUIDE.md` – Format specification
- `docs/seo-strategy-2026/LLM_FILES_MAINTENANCE.md` – Maintenance procedures

## Automation Note

The script `v2/api/generate-llms.php` can inject the product updates section into LLM files. It uses data from the product updates API. For **manual control** and **ACAO-optimized entries**, prefer editing the files directly and using this process. The script is useful for bulk regeneration when the section structure changes.