Overview

Most validators only check if properties exist. Value Quality Scoring goes deeper, assessing whether property values are actually useful — are descriptions long enough? Are images high resolution? Are dates in the future for upcoming events?

How It Works

1. After validation, each property value is assessed for quality
2. Quality checks include:
– Text length and substance (not just “lorem ipsum”)
– Image URL accessibility and dimensions
– Date validity and temporal relevance
– URL validity and accessibility
– Numeric value reasonableness
3. Each property gets a quality grade
4. Overall value quality score supplements the completeness score

Tier Availability

| Tier | Available |
|——|———–|
| Enterprise | Yes |

Related Features

– Schema Completeness Score: Measures property presence (this measures value quality)
– Entity Consistency Checker: Related quality dimension
– AI Discoverability Score: Value quality improves AI readiness

Mini-Tutorial

Assessing and Improving Value Quality

1. Analyze quality for a URL:

   POST /validgraph/v1/analyze-quality

   {
     "url": "https://example.com/products/widget-x"
   }
   

2. Review the quality report showing each property with ratings:
– Description: “Lorem ipsum dolor…” → Poor (placeholder text)
– Image: “small.jpg” (120x80px) → Warning (too small)
– Phone: “555-0123” → Poor (not E.164 format)
– Price: “99.99” → Good

3. Identify improvement priorities:
– Replace placeholder descriptions with real content (>100 chars)
– Use high-quality images (>300x300px, .jpg/.png/.webp/.avif)
– Standardize phone numbers to E.164 format
– Use ISO 8601 dates for temporal data

4. Update your schemas with quality content:

   {
     "@context": "https://schema.org",
     "@type": "Product",
     "name": "Widget X",
     "description": "A high-quality widget designed for professional applications...",
     "image": "https://cdn.example.com/widget-x-800x600.jpg",
     "offers": {
       "@type": "Offer",
       "price": "99.99",
       "priceCurrency": "USD"
     },
     "telephone": "+1-555-0123"
   }
   

5. Re-validate to measure quality improvement.

Technical Details

Quality Assessment Checks

1. Text Fields (description, name, etc.):
– Placeholder detection: “test”, “example”, “lorem”, “undefined”, “null”, “todo” (case-insensitive)
– All-caps detection: flagged as potentially automated/low-quality
– Length validation: descriptions must be >50 chars for “good” rating
– Name fields minimum 3 characters

2. Image Properties:
– URL format validation (must be valid URL with scheme)
– Accessibility check (not localhost, properly hosted)
– Format validation (.jpg, .png, .webp, .gif, .avif only)
– Dimension recommendations: minimum 300x300px

3. URL Properties:
– Format validation (proper URL with scheme)
– HTTPS requirement (http URLs = warning)
– Localhost detection (localhost URLs = poor for production)

4. Phone Numbers:
– E.164 format validation: +[country][number]
– Invalid formats = poor rating

5. Dates:
– ISO 8601 format validation (YYYY-MM-DD or YYYY-MM-DDTHH:MM:SSZ)
– Temporal relevance (future dates for events, past dates for published content)

6. Quality Grades:
– Good: All checks pass, quality standards met
– Warning: Minor issues that should be addressed
– Poor: Significant quality problems affecting AI readiness

REST API Example

Request:

POST /validgraph/v1/analyze-quality

Request body:

{
  "url": "https://example.com/products/widget"
}

Response:

{
  "url": "https://example.com/products/widget",
  "schemas": [
    {
      "@type": "Product",
      "properties": [
        {
          "name": "description",
          "value": "A professional-grade widget...",
          "quality_score": 0.95,
          "grade": "good",
          "checks": {
            "no_placeholder": true,
            "no_all_caps": true,
            "min_length_met": true
          }
        },
        {
          "name": "image",
          "value": "https://example.com/widget.jpg",
          "quality_score": 0.88,
          "grade": "good",
          "checks": {
            "valid_url": true,
            "valid_format": true,
            "accessible": true,
            "minimum_dimensions": true
          }
        },
        {
          "name": "telephone",
          "value": "555-0123",
          "quality_score": 0.2,
          "grade": "poor",
          "checks": {
            "e164_format": false,
            "valid_format": true
          }
        }
      ]
    }
  ],
  "overall_quality_score": 0.67
}

References

– Schema.org Property Definitions
– Image SEO Best Practices
– ISO 8601 Date Format
– E.164 Phone Format Standard