Broken SEO should break your build.
Add one line to your pipeline. Every deploy gets audited. Regressions fail the build.
Guard every deploy
SEO errors block deployment. Warnings are flagged. Clean builds ship clean metadata.
Diff between deploys
Compare scores between deploys. Catch regressions before they hit production.
Zero config
Works with Vercel, GitHub Actions, and any CI. One command, zero config.
One line. Any pipeline.
Vercel build command
GitHub Actions
How CI/CD SEO validation works
SEO regressions are the silent killer of organic traffic. A developer removes a meta description while refactoring, another deploy adds a noindex directive left from staging, and an og:image path breaks during a URL restructure. None of these trigger test failures. None cause build errors. They ship to production undetected.
Indxel's CI/CD guard treats SEO like type safety. Add npx indxel check --ci to your build command. On every deploy, Indxel validates 15 SEO rules across every page: title length, meta description presence, og:image status, canonical URLs, JSON-LD validity, robots directives, and more. Each page gets a 0-100 score. If any page drops below your threshold, the build fails with a clear error message pointing to the exact issue.
The --diff flag compares the current state against the previous check, showing exactly what changed between deploys. New errors, fixed issues, and score changes are surfaced in your terminal or CI logs. Pair it with Slack or Discord webhooks to get notified of regressions instantly.
Works with any CI system that respects exit codes: Vercel, GitHub Actions, GitLab CI, CircleCI, Bitbucket Pipelines, Jenkins, and more. The check runs in seconds and requires zero configuration beyond the single command.
Frequently asked questions
Does this slow down my builds?
No. The static check runs in 2-5 seconds for most sites. It analyzes your source code without needing a running server. The crawl mode (for live URL validation) takes longer but runs as a separate CI job.
What happens when the check fails?
The process exits with code 1, which fails the build in any CI system. The output shows exactly which pages failed, which rules were violated, and the current score. Fix the issues, push again, and the check passes.
Can I set a custom score threshold?
Yes. By default, pages below 90/100 fail the build. Configure your threshold in seo.config.ts or pass --threshold 80 to the CLI. Set it lower during migration, higher for production.
Does it work with monorepos?
Yes. Indxel works with Turborepo, Nx, and any monorepo setup. Run the check from the app directory or configure it as a pipeline task. Each app gets its own SEO validation.