# OMR Reviews Verification Guide

**Last Updated:** 2026-04-02

## Expected public marketing counts (on-site copy)

After verifying against **OMR** and **Google Business / Maps**, keep these aligned with the single source of truth in `v2/data/social-proof-trust-section.php` (trust card + homepage v3 hero + pricing/paid review lines):

- **Google Reviews:** 4,8 Sterne, 40 Bewertungen (as displayed on the site).
- **OMR Reviews:** 4,9 Sterne, 55 Bewertungen (OMR JSON-LD on the product page listed `reviewCount` 55 and `ratingValue` 4.91 as of 2026-04-02).

Comparison pages use **OMR-style** 4.9 for Ordio in the hero card and matching `aggregateRating` / review distribution; update those when OMR totals change.

## Purpose

This guide helps you manually verify review data extracted from OMR Reviews by comparing it with the actual OMR website.

## Prerequisites

- Access to OMR Reviews: https://omr.com/de/reviews/product/ordio/all
- The generated review data table: `docs/testimonials/omr-reviews-data-table.md`
- Notion account (optional, for easier table viewing)

## Verification Process

### Step 1: Open OMR Reviews Page

1. Navigate to: https://omr.com/de/reviews/product/ordio/all
2. If needed, navigate to page 2: https://omr.com/de/reviews/product/ordio/all/2
3. Wait for the page to fully load

### Step 2: Load Review Data Table

1. Open `docs/testimonials/omr-reviews-data-table.md`
2. Copy the table (starting from the header row)
3. Paste into Notion (optional but recommended for better viewing)
4. Or view directly in your markdown viewer

### Step 3: Compare Reviews

For each review in the table:

1. **Find the review on OMR** by:

   - Searching for the reviewer name
   - Searching for the company name
   - Using the review ID to locate it

2. **Verify each field:**

   - ✅ **Reviewer Name**: Should match exactly
   - ✅ **Job Title**: Check if job title is visible on OMR (e.g., "CEO", "Geschäftsführer", "Manager")
   - ✅ **Company Name**: Should match exactly
   - ✅ **Company Size**: Should match (e.g., "1-50 Mitarbeiter", "51-1000 Mitarbeiter")
   - ✅ **Industry**: Should match
   - ✅ **Rating**: Should match (numeric and stars)
   - ✅ **Date**: Should be approximately correct (OMR shows relative dates like "Vor mehr als 12 Monaten")
   - ✅ **Headline**: Should match (may have slight formatting differences)
   - ✅ **Pros**: Should match content
   - ✅ **Cons**: Should match content
   - ✅ **Problems Solved**: Should match content
   - ✅ **Use Cases**: Should match (order may differ)

### Step 4: Document Issues

When you find discrepancies:

1. **Note the Review ID** (e.g., "omr-001")
2. **Document the issue**:

   - Missing job title (if visible on OMR)
   - Incorrect company name
   - Missing or incorrect content
   - Other data quality issues

3. **Take a screenshot** (optional but helpful)

## Common Issues to Look For

### Missing Job Titles

**Symptom**: Job Title column shows "❌ Missing" but OMR shows a job title

**Example**:

- Table shows: "Jens" with no job title
- OMR shows: "Jens Verifizierter Reviewer Geschäftsführer bei Verdie GmbH"

**Action**: Note the review ID and the actual job title from OMR

### Incorrect Company Names

**Symptom**: Company name doesn't match OMR

**Example**:

- Table shows: "Company A"
- OMR shows: "Company A GmbH"

**Action**: Note the review ID and correct company name

### Missing Content

**Symptom**: Pros/Cons/Problems Solved fields are empty but OMR shows content

**Action**: Note the review ID and missing content

### HTML Entities

**Symptom**: Text shows "&amp;" instead of "&"

**Action**: This is a display issue, but note if it appears in the table

## Verification Checklist

Use this checklist for each review:

- [ ] Review found on OMR website
- [ ] Reviewer name matches
- [ ] Job title matches (or correctly marked as missing)
- [ ] Company name matches
- [ ] Company size matches
- [ ] Industry matches
- [ ] Rating matches
- [ ] Date is approximately correct
- [ ] Headline matches
- [ ] Pros content matches
- [ ] Cons content matches
- [ ] Problems solved content matches
- [ ] Use cases match (order may differ)

## Reporting Issues

When reporting issues, include:

1. **Review ID** (e.g., "omr-001")
2. **Field with issue** (e.g., "Job Title")
3. **What's in the table** (e.g., "❌ Missing")
4. **What's on OMR** (e.g., "Geschäftsführer")
5. **OMR URL** (if possible, direct link to review)
6. **Screenshot** (optional but helpful)

## Tips

- **Use browser search** (Ctrl+F / Cmd+F) to quickly find reviews on OMR
- **Check both pages** - reviews are split across multiple pages
- **Focus on missing job titles first** - this is the primary issue to fix
- **Batch verification** - verify 10-20 reviews at a time to avoid fatigue
- **Use Notion** - copying the table to Notion makes it easier to sort and filter

## After Verification

Once you've verified reviews and identified issues:

1. **Create a list** of reviews with missing job titles
2. **Note any other data quality issues**
3. **Share findings** with the team
4. **Update scraping logic** based on findings
5. **Re-scrape reviews** with improved logic
6. **Re-verify** to confirm fixes

## Quick Reference

- **OMR Page 1**: https://omr.com/de/reviews/product/ordio/all
- **OMR Page 2**: https://omr.com/de/reviews/product/ordio/all/2
- **Data Table**: `docs/testimonials/omr-reviews-data-table.md`
- **Database**: `v2/data/testimonials/testimonials-database.json`
