---
title: Rich Results Validation CI
category: product
entity_type: skill
price: $15
canonical: https://forgehouse.ai/skills/rich-results-validation-ci/
lang: en
hreflang_alt: https://forgehouse.ai/tr/skiller/rich-results-validation-ci/
last_updated: 2026-06-20
---

# Rich Results Validation CI

> Google Rich Results Test API entegrasyonu ile CI/CD deploy gate kurulumu.

A build-time gate that validates your Schema.org structured data against Google's Rich Results Test API inside your CI/CD pipeline, before invalid schema ever reaches production. Broken markup that would silently kill your rich snippets (review stars, FAQ accordions, product cards) becomes a failed build with a clear fix, not a ranking loss you discover weeks later. It is the live-validation layer of a defense-in-depth schema chain.

## Use cases
- Gating production deploys so schema-invalid pages cannot ship
- Validating new schema types (Product, Article, FAQ, LocalBusiness, Recipe, HowTo)
- Batch-validating thousands of pages on large pSEO builds within API quota
- Catching rich-result blockers like missing offers or missing itemReviewed
- Auto-commenting on pull requests with the exact file, issue, and fix snippet
- Re-testing retroactively when a CMS edit or merge breaks previously valid schema

## Benefits
- Catches schema regressions at PR time, when fixes are far cheaper than in production
- Protects rich-snippet eligibility and the click-through it drives
- Keeps developers unblocked with severity tiers: critical fails, minor only warns
- Stays within free API quota through idempotent content-hash caching

## What’s included
- Async Python validator with concurrency, retry, and exponential backoff
- Four-tier severity classification (critical fail, high warn, medium comment, low info)
- Ready-to-use GitHub Actions workflow with path filters and concurrency control
- SARIF report generation for the GitHub Security tab
- PR comment template with file, line, issue, and copy-paste remediation
- Per-project severity tuning so each site fails on the rules that matter to it

## Who it’s for
SEO-focused engineering teams running schema-rich sites who want invalid structured data blocked at build time, not discovered in lost rankings.

## How it runs
The skill wires Google's Rich Results Test API into CI as a deploy gate, the third layer of a schema defense in depth: invalid schema fails the build before it ever reaches production, instead of being discovered in Search Console weeks later.
1. Runs the cheap layers first: the offline spec validator and the @graph integrity check; if those fail, the Google API is never called, which saves quota and time.
2. Extracts rendered HTML straight from the Next.js build output and posts it inline to the Rich Results API, so changed pages get tested without waiting for a staging deploy.
3. Validates in parallel (10 concurrent calls with exponential backoff on rate limits) and caches responses by SHA256 of the HTML for 24 hours, pushing cache hit rates above 70 percent on large sites and keeping quota inside the free tier.
4. Classifies every issue by severity from real eligibility rules: CRITICAL means the rich result is lost entirely (Product without offers, Article without headline, AggregateRating without itemReviewed), HIGH limits the result, MEDIUM and LOW are best practice notes.
5. Enforces the gate: any CRITICAL exits with code 2 and blocks the merge, the full issue list uploads as a SARIF report to the GitHub Security tab, and a PR comment shows the top 10 issues each with a concrete fix snippet and a Google docs link.
6. Tunes severity per customer through a YAML policy file, so one site can promote a specific issue class to build-fail while another treats the same class as a warning.

## FAQ
### We deploy through GitHub Actions: does it slot in, and what about other CI systems?
A ready workflow with path filters and concurrency control ships for GitHub Actions, including SARIF output for the Security tab. The validator itself is an async Python script, so GitLab, Jenkins, or any other runner invokes it the same way, only the workflow wrapper is GitHub-specific.

### I already paste URLs into the Rich Results Test before big releases, what changes when the same check runs at PR time?
Same Google API, but automated at PR time with four severity tiers: critical fails the build, minor only warns, and the PR gets a comment naming the exact file, issue, and fix snippet. Content-hash caching keeps repeat runs inside the free API quota, something manual testing never tracks.

### Will it fix my schema or guarantee rich snippets show up?
No. It blocks invalid markup and tells you the remediation, but displaying rich results remains Google's decision. Valid schema earns eligibility, not a guarantee, and writing the schema itself is upstream of this gate.

## Price
$15, one-time, no subscription. VAT included.

Related guide: [How to automate SEO and AEO with Claude](https://forgehouse.ai/guides/automate-seo-claude/)