Use case

SEO checks in your CI/CD pipeline.

You gate deploys on tests, types, and linting. SEO should be no different — but most teams have zero automated checks for metadata quality. A developer accidentally removes a meta description, marketing pushes a PR with a 120-character title, and a template change breaks structured data across 50 pages. Indxel adds a validation step to your pipeline that catches these issues before they reach production. One command, exit code 1 on failures, JSON output for pipeline integration.

Common pain points

•SEO issues bypass CI/CD and reach production undetected
•No automated way to validate metadata in the build pipeline
•Marketing files PRs with SEO changes that break structured data
•Rollbacks happen because of SEO regressions that were preventable

How Indxel helps

Pipeline integration

indxel check --ci exits with code 1 on failures. Drop it into any CI system — GitHub Actions, GitLab CI, CircleCI.

Diff-mode for PRs

indxel check --diff validates only changed files. Fast, focused, no wasted compute on unchanged pages.

Exit codes and JSON output

Machine-readable output for pipeline integration. Parse results, set thresholds, post comments on PRs.

Vercel integration

Add to your Vercel build command. Preview deployments fail if SEO is broken — before it hits production.

GitHub Actions workflow

yaml

# .github/workflows/seo-guard.yml
name: SEO Guard
on: [pull_request]
jobs:
  seo-check:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: npm ci
      - run: npx indxel check --ci --diff
        env:
          INDXEL_API_KEY: ${{ secrets.INDXEL_API_KEY }}

Add SEO validation to your CI/CD pipeline.

View pricing