# Employee Experience – Next Steps

**Post:** lexikon/employee-experience  
**Status:** Content complete, ready for preview + publish  
**Created:** 2026-03-03

## Completed ✅

- [x] Backup, scaffold, pipeline
- [x] SERP_ANALYSIS, CONTENT_OUTLINE (10 H2s, PAA coverage matrix)
- [x] Content (2,341 words, 83.6% of target) via update-post-content.php
- [x] FAQs (15, quality score 100/100) via generate-faq-questions.php, generate-faq-answers-optimized.php, add-faqs-to-post.php
- [x] Featured image (CAFE scene type), WebP variants (640w, 1024w, 1280w), post JSON updated
- [x] Related posts (14) + carousel updates (9 posts) via suggest-related-posts.php, add-new-post-to-related-carousels.php
- [x] SEO meta (title: 55 chars, description: 151 chars) in seo-meta.json
- [x] Product mapping: employee-experience → /arbeitszeiterfassung, /schichtplan, /abwesenheiten, /digitale-personalakte
- [x] Lead capture copy manually added to JSON
- [x] LLM sync: sync-blog-posts-to-llms.php --add
- [x] Lexikon inventory: normalize-and-match-terms.py, generate-lexikon-inventory-report.py
- [x] All validations passing (section depth, content completeness, FAQ quality/schema/uniqueness, content flow, new post)
- [x] Schema structure validated programmatically (FAQPage with 15 FAQs)

## Pending (Manual)

### 1. Browser Preview

Preview locally (Docker/server must be running):

- **URL:** http://localhost:8003/insights/lexikon/employee-experience/
- **Check:**
  - Links (internal links to lexikon posts, product features)
  - Tables (comparison table H2 2, Employee Life Cycle table H2 4)
  - FAQ accordion (15 FAQs rendering correctly)
  - Meta tags (title, description)
  - Featured image (WebP variants loading correctly)
  - Mobile responsiveness
  - Console errors (none expected)

### 2. Schema Validation (after publish)

Run [Google Rich Results Test](https://search.google.com/test/rich-results) with production URL:

- `https://www.ordio.com/insights/lexikon/employee-experience/`
- **Verify:**
  - Article schema (with publicationDate, modifiedDate)
  - FAQPage schema (15 FAQs)
  - No schema errors or warnings

### 3. GSC Indexing (after publish)

1. Submit URL to Google Search Console: `/insights/lexikon/employee-experience/`
2. Request indexing via GSC URL Inspection tool
3. Monitor indexing status (typically 1-7 days)

## Next Steps (Optional)

### Reciprocal Linking

Consider adding bidirectional links from related posts:

- [ ] **employee-engagement**: Add link to employee-experience in differentiation section
- [ ] **mitarbeiterbindung**: Add link to employee-experience in differentiation section
- [ ] **candidate-experience**: Add link to employee-experience (Employee Life Cycle section)
- [ ] **onboarding**: Add link to employee-experience (Employee Life Cycle section)
- [ ] **unternehmenskultur**: Add link to employee-experience (three dimensions section)

### Monitoring

Follow MONITORING_SETUP.md for:
- GA4 tracking verification
- GSC indexing and rankings
- Performance targets (Top 10 for "Employee Experience" in 3-6 months)
- Competitor monitoring (hr-heute.com, qualtrics.com, greatplacetowork.at)

### Content Optimization (if needed)

Based on performance data:
- Expand measurement methods section with more KPIs
- Add industry-specific examples (Gastronomie, Einzelhandel)
- Update ROI statistics annually
- Add more specific examples for three dimensions

## Key Differentiators

- **Comparison table** (H2 2): Critical ranking factor - Employee Experience vs Employee Engagement vs Mitarbeiterbindung
- **Three dimensions** (H2 3): Comprehensive coverage with H3 subsections (Cultural, Technological, Physical)
- **Employee Life Cycle** (H2 4): Detailed phase coverage with touchpoints table
- **HR process integration** (H2 9): Unique angle on Zeiterfassung/Schichtplanung integration
- **FAQs**: 15 FAQs vs competitors' 0-10 FAQs

## Notes

- **Manual PAA override**: Created `paa-questions-manual.json` due to 92% off-topic SISTRIX questions (employer branding, customer experience, Yammer)
- **Word count**: 2,341/2,800 (83.6%) - comprehensive coverage, above 80% minimum
- **Content depth**: Above average (1,776 words) vs competitors
- **Schema**: FAQPage schema validated programmatically (15 FAQs in @graph)