Developers

SEO in your pipeline

Run a RankForge audit from your terminal or CI and fail the build when the score drops — so an SEO regression never ships. Generate an API key in Settings(Pro & Agency), then:

CLI

No install — run the hosted script with Node 18+.

export RANKFORGE_API_KEY=rf_your_key
curl -fsSL https://rankforge.oodac.com/rankforge.mjs -o rankforge.mjs
node rankforge.mjs audit https://your-site.com --min-score 80 --max-pages 15

Exits 0 on pass, 1 when the score is below --min-score.

GitHub Action

Add your key as a repo secret (RANKFORGE_API_KEY), then drop this in .github/workflows/:

name: SEO audit
on: [pull_request, workflow_dispatch]
jobs:
  rankforge:
    runs-on: ubuntu-latest
    steps:
      - env:
          RANKFORGE_API_KEY: ${{ secrets.RANKFORGE_API_KEY }}
        run: |
          curl -fsSL https://rankforge.oodac.com/rankforge.mjs -o rankforge.mjs
          node rankforge.mjs audit "https://your-site.com" --min-score 80

REST API

Prefer to call it directly? One request, synchronous result.

curl -X POST https://rankforge.oodac.com/api/v1/audit \
  -H "Authorization: Bearer rf_your_key" \
  -H "content-type: application/json" \
  -d '{"url":"https://your-site.com","maxPages":15,"minScore":80}'

Response

{
  "url": "https://your-site.com",
  "score": 84,
  "pass": true,
  "minScore": 80,
  "categories": [{ "category": "technical", "score": 78 }, ...],
  "issueCounts": { "critical": 0, "warning": 3, "notice": 5 },
  "issues": [{ "severity": "warning", "impact": "crawlability", "title": "...", "recommendation": "..." }]
}

The CI endpoint runs an HTML crawl audit (no render/AI) for speed — a RankForge model score, not a Google score. Each call counts toward your monthly audit quota.