# Ratgeber Post Creation Workflow **Last Updated:** 2026-03-16 **Purpose:** Step-by-step workflow for creating ratgeber posts with cluster alignment and resource connections. Adapted from [LEXIKON_POST_CREATION_WORKFLOW.md](lexikon-inventory/LEXIKON_POST_CREATION_WORKFLOW.md). **Quality bar:** Ratgeber must match lexikon depth, formatting, and data-driven rigor. See [RATGEBER_IMPROVEMENT_PLAN_2026.md](RATGEBER_IMPROVEMENT_PLAN_2026.md). --- ## Differences from Lexikon - **Topic source:** From CLUSTER_EXPANSION, content gaps, or SERP research – no lexikon inventory - **Structure:** Comparison/how-to focus (tables, pros/cons, software criteria) vs definition-first - **Intro:** Human-first hook, not definition-first - **Year in title:** Ratgeber often include year (e.g. 2026) – requires annual update per [blog-evergreen-annual.mdc](../../.cursor/rules/blog-evergreen-annual.mdc) - **Same validation sequence:** validate-section-depth, validate-content-completeness, validate-faq-quality, validate-new-post - **Same quality standards:** Answer capsules, 100% competitive-depth target, format patterns (blog-note, formula-block), E-E-A-T signals --- ## Pre-Creation Research ### 1. Cluster Alignment Verification - [ ] Identify primary cluster (Zeiterfassung/Dienstplan/Both/Supporting) - [ ] Verify cluster assignment using cluster keywords - [ ] Check related posts in same cluster - [ ] Identify pillar page(s) to link to ### 2. Resource Connection Mapping - [ ] Identify relevant tools (existing and planned) - [ ] Identify relevant templates (existing and planned) - [ ] Identify relevant ratgeber posts (existing and planned) - [ ] Identify relevant lexikon posts (existing and planned) - [ ] Verify resource connections are logical ### 3. Keyword Research - [ ] Primary keyword identified (Serper + Web Search) - [ ] Secondary keywords identified (5-10) - [ ] Search intent verified (informational/commercial) - [ ] Competitor coverage analyzed - [ ] Featured snippet opportunities identified --- ## Content Creation ### 4. Content Structure (Ratgeber-Specific) - [ ] H1 headline (includes primary keyword; year if applicable) - [ ] Introduction (human-first hook, not definition-first) - [ ] Main content sections (H2s, H3s) - [ ] **Comparison table** (software features, pricing, pros/cons) where applicable – per [BLOG_TABLE_FORMAT.md](BLOG_TABLE_FORMAT.md) - [ ] **Answer capsules:** 120–150 character direct answer after **question-style H2s** (AEO/GEO; featured snippet) - [ ] Fazit section - [ ] FAQ section (10-15 FAQs) ### 5. Content Depth - [ ] Word count target: **100% of competitive-depth recommended** (not minimum). Aim for 1,800–2,500 for main comparison topics. - [ ] Comprehensive coverage of topic - [ ] Comparison criteria clearly defined - [ ] **H3 planning:** Target-group sections (Gastronomie, Pflege, Kleinbetriebe) → H3 per group when 2+ sentences each - [ ] Examples provided where relevant - [ ] Related concepts explained - [ ] **Format patterns:** Use `blog-note--important` for pricing/legal callouts; `formula-block` for cost formulas when applicable ### 6. Keyword Integration - [ ] Primary keyword in title, H1, first paragraph - [ ] Secondary keywords naturally integrated - [ ] Keyword density appropriate (not over-optimized) - [ ] Semantic variations used --- ## Resource Linking ### 7. Internal Links to Resources - [ ] Links to relevant tools (2-5 links; match lexikon standard) - [ ] Links to relevant ratgeber posts (2-3 links) - [ ] Links to relevant lexikon posts (1-2 links) - [ ] Links contextual and logical - [ ] Anchor text variety maintained ### 8. Cluster Linking - [ ] Links to pillar page(s) (3-5 links) - [ ] Links to related ratgeber posts (2-3 links) - [ ] Total internal links: 10-15 per post - [ ] Cluster authority strengthened --- ## SEO Optimization ### 9. Meta Tags - [ ] Meta title optimized (50-60 characters, includes primary keyword) - [ ] Meta description optimized (150-160 characters, includes primary keyword) - [ ] Canonical URL correct ### 10. Schema Markup - [ ] Article schema included - [ ] FAQPage schema included (for FAQ section) - [ ] BreadcrumbList schema included - [ ] All schema validated with Google Rich Results Test --- ## Quality Review ### 11. Content Quality - [ ] Comparison table format per [BLOG_TABLE_FORMAT.md](BLOG_TABLE_FORMAT.md) (table-breakout-wrapper, no Tailwind on tables) - [ ] **Answer capsules** present for question-style H2s (120–150 chars) - [ ] **blog-note--important** callouts for pricing/legal caveats where applicable - [ ] Legal/compliance accuracy verified (if applicable) - [ ] Statistics and data accurate - [ ] Links functional and correct - [ ] Tone consistent (du tone, Ordio mentions contextual) - [ ] **E-E-A-T:** Examples, case studies, or concrete data points where relevant ### 12. Technical Quality - [ ] Images optimized (WebP format, alt text = {Title} | Ordio) - [ ] Mobile responsive - [ ] No broken links - [ ] URL structure correct --- ## Pre-Publication Checklist - [ ] All validators pass (section-depth, content-completeness, faq-quality, new-post) - [ ] compare-content-to-competitors run and gaps addressed - [ ] Schema markup validated - [ ] Mobile preview checked - [ ] CREATION_NOTES.md created --- ## Related Documentation - [RATGEBER_IMPROVEMENT_PLAN_2026.md](RATGEBER_IMPROVEMENT_PLAN_2026.md) - Gap analysis and improvement pillars - [RATGEBER_NEW_POST_CHECKLIST.md](RATGEBER_NEW_POST_CHECKLIST.md) - Quick reference checklist - [LEXIKON_POST_CREATION_WORKFLOW.md](lexikon-inventory/LEXIKON_POST_CREATION_WORKFLOW.md) - Lexikon workflow (source) - [SEO_GEO_AEO_CHECKLIST.md](SEO_GEO_AEO_CHECKLIST.md) - Answer capsules, E-E-A-T, schema - [CONTENT_FORMAT_PATTERNS.md](CONTENT_FORMAT_PATTERNS.md) – formula-block, breakout tables, blog-note; **when/how much:** § *Visual format decision guide* - [.cursor/rules/blog-new-post-creation.mdc](../../.cursor/rules/blog-new-post-creation.mdc) - Cursor rule