A programmatic SEO checker you can wire into CI/CD. Fail the build when a page regresses below your SEO score threshold. GitHub Action, Python and Node SDKs, plain REST. Free tier.
SEO regressions don't show up in your test suite. They show up six weeks later in Search Console, after a deploy quietly dropped a meta tag or renamed an H1. The SEO Checker API turns an SEO audit into a pass/fail gate you run on every pull request — same place you run unit tests.
curl -H "X-API-Key: YOUR_KEY" \
"https://seoscoreapi.com/audit?url=https://example.com"Or with the Python SDK (pip install seoscoreapi):
from seoscoreapi import audit
result = audit("https://example.com", api_key="YOUR_KEY")
print(result["score"], result["grade"])Every audit returns a 0–100 score and a letter grade. Pick a floor (say 85), assert on it in CI, and block the merge if a change drags the page below it. The official GitHub Action does this in three lines of YAML; for GitLab, CircleCI, or anything else, call the REST endpoint with curl or the SDKs.
Run the checker against a preview/staging URL on every PR. The diff shows exactly which checks flipped from pass to fail, so the person who introduced the regression fixes it before it ever ships.
Prevent SEO regressions by adding automated audits to your CI/CD pipeline. GitHub Actions, GitLab CI, and curl examples — fail builds that break SEO.
A GitHub Actions workflow that audits SEO on every PR, posts results as comments, and fails merges when scores drop below your threshold.
Install our Claude Code custom skill and run SEO audits, batch checks, and score comparisons directly from your coding sessions. Free to start.
Install one MCP server and your AI assistant can audit URLs, look up observed backlinks, and read score history without any custom plumbing.
The seoscoreapi Python package now ships compare(), full historical timeseries, and webhook alerts on score drops. Worked examples for every new function.
Yes — that's the primary use case. There's an official GitHub Action, and the REST API works in any CI that can run curl or Python/Node.
Read the `score` field from the audit response and exit non-zero when it's below your threshold. The GitHub Action exposes a threshold input so you don't have to script it.
Yes. Any publicly reachable URL works, including Vercel/Netlify preview deployments and password-free staging environments.
Yes — `seoscoreapi` on PyPI and npm, both at v1.1.0, plus an n8n community node for low-code pipelines.
Add an SEO Gate to Your Pipeline