# CV Parsing – Next Steps

**Post:** lexikon/cv-parsing  
**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,174 words, 127.9% 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 (DESK scene type), WebP variants (640w, 1024w, 1280w), post JSON updated
- [x] Related posts (14) + carousel updates (8 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: No product mapping (BMS/Recruiting cluster - no Ordio product)
- [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/cv-parsing/
- **Check:**
  - Links (internal links to lexikon posts, BMS/Recruiting cluster)
  - Tables (comparison table H2 2, extracted fields 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/cv-parsing/`
- **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/cv-parsing/`
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:

- [ ] **bewerbermanagementsystem**: Add link to cv-parsing in CV Parsing/BMS integration section
- [ ] **multiposting**: Add link to cv-parsing in BMS features section
- [ ] **e-recruiting**: Add link to cv-parsing in E-Recruiting technology section
- [ ] **candidate-experience**: Add link to cv-parsing in application processing section
- [ ] **recruiting**: Add link to cv-parsing in Recruiting technology section

### Monitoring

Follow MONITORING_SETUP.md for:
- GA4 tracking verification
- GSC indexing and rankings
- Performance targets (Top 10 for "CV Parsing" in 3-6 months)
- Competitor monitoring (personio.de, textkernel.com, klippa.com)

### Content Optimization (if needed)

Based on performance data:
- Expand implementation guide with more examples
- Add industry-specific use cases (Gastronomie, Einzelhandel)
- Update GDPR compliance section with latest DSGVO guidance
- Add more extracted fields to table if competitors expand

## Notes

- **PAA Override:** Manual override required due to 100% off-topic SISTRIX questions (Lebenslauf erstellen, Lebenslauf-Vorlagen)
- **No Product Mapping:** BMS/Recruiting cluster - documented in PRODUCT_MAPPING.md
- **Scene Type:** DESK (technology-focused) distinct from bewerbermanagementsystem CAFE, recruiting DESK
- **Differentiation Critical:** Comparison table (H2 2) is critical ranking factor
- **GDPR Emphasis:** H2 7 must emphasize DSGVO compliance - important for German HR context
- **BMS Integration:** H2 8 explains how CV Parsing fits into Bewerbermanagementsystem workflow - unique angle