SEO data that powers your tools.

One API for search and AI visibility data — rankings, keywords, backlinks, and citations. 100TBs of data at your disposal.

Get your API key Browse the endpoints ↓

No credit card required · Start with 1,500 free credits.

$ curl api.seofetch.com/v1/search -d '{"query": "best running shoes"}'

← response200 · 1 credit

{
  "object": "search",
  "credits": { "charged": 1, "balance": 9857 },
  "data": {
    "query": "best running shoes",
    "total_results": 84900000,
    "items": [
      {
        "rank": 1,
        "title": "The 12 Best Running Shoes",
        "url": "https://example.com/best-running-shoes",
        "site_name": "Example Running Co.",
        "rating": { "value": 4.6, "votes": 1284, "max": 5 },
        "sitelinks": [ { "title": "Best Trail Running Shoes" } ]
      }
    ]
  }
}

+9 more results ranks · titles · ratings · sitelinks 1 credit

how it works

Three commands to first data.

Get a key

$ export SEOFETCH_KEY=sof_live_…

Send a request

Every metered endpoint is one POST. Same envelope, same rules.

$ curl api.seofetch.com/v1/search -H "Authorization: Bearer $SEOFETCH_KEY"

Get normalized JSON

The same envelope on every endpoint: object, credits, data. One integration, all data types.

"credits": { "charged": 1, "balance": 9857 }

for agents

Give your coding agent the whole picture.

A short Markdown brief, built for pasting straight into an agent's context — what the API does, every endpoint and what it costs, a quickstart it can run, and one worked example. The preview below shows the shape; copy the full document into your agent and skip the docs crawl.

preview

# seofetch — SEO data API

seofetch is a REST API for SEO data — search results, keyword volume and difficulty, backlinks, domain overviews, site audits, Lighthouse performance, and more. All 19 endpoints return the same JSON envelope, so learning that shape once gets you every endpoint.

Base URL: `https://api.seofetch.com`. Authenticate every request with `Authorization: Bearer <your key>`. Get a key at `https://seofetch.com/accounts/signup/` — 1,500 free credits, no card required.

## Quick start

```bash
curl https://api.seofetch.com/v1/search \
  -H "Authorization: Bearer sof_live_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{"query": "best running shoes"}'
```

→ copyoverview.md →

show the full document

# seofetch — SEO data API

seofetch is a REST API for SEO data — search results, keyword volume and difficulty, backlinks, domain overviews, site audits, Lighthouse performance, and more. All 19 endpoints return the same JSON envelope, so learning that shape once gets you every endpoint.

Base URL: `https://api.seofetch.com`. Authenticate every request with `Authorization: Bearer <your key>`. Get a key at `https://seofetch.com/accounts/signup/` — 1,500 free credits, no card required.

## Quick start

```bash
curl https://api.seofetch.com/v1/search \
  -H "Authorization: Bearer sof_live_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{"query": "best running shoes"}'
```

```json
{
  "id": "srch_tnq5objwpmflh2poczbwxnfr",
  "request_id": "req_c7leybmgtzholcwoyhozbqsqkq",
  "object": "search",
  "created_at": "2026-08-08T16:50:38Z",
  "elapsed_ms": 142,
  "cache": "miss",
  "credits": {
    "charged": 1,
    "balance": 9857
  },
  "data": {
    "query": "best running shoes",
    "engine": "google",
    "location": 2840,
    "language": "en",
    "device": "desktop",
    "total_results": 84900000,
    "serp_url": "https://www.google.com/search?q=best+running+shoes",
    "result_types": [
      "organic"
    ],
    "results_count": 10,
    "items": [
      {
        "type": "organic",
        "rank": 1,
        "page": 1,
        "domain": "example.com",
        "title": "The 12 Best Running Shoes",
        "url": "https://example.com/best-running-shoes",
        "description": "Our team tested 40 pairs...",
        "displayed_link": "example.com › reviews › shoes",
        "date": null,
        "site_name": "Example Running Co.",
        "rating": {
          "value": 4.6,
          "votes": 1284,
          "max": 5
        },
        "sitelinks": [
          {
            "type": "sitelink",
            "title": "Best Trail Running Shoes",
            "description": null,
            "url": "https://example.com/best-running-shoes/trail"
          },
          {
            "type": "sitelink",
            "title": "Best Budget Running Shoes",
            "description": null,
            "url": "https://example.com/best-running-shoes/budget"
          }
        ],
        "price": null
      }
    ]
  }
}
```

## What's possible

- `POST /v1/search` — Run one search query and get the parsed SERP back — ranked items, not raw HTML. — 1 credit at the default depth (10 results), 10 credits at depth=100.
- `POST /v1/keywords/volume` — Historical Google keyword search volume and competition metrics. — 20 credits per call.
- `POST /v1/keywords/difficulty` — Keyword difficulty (0-100) per keyword; unscored keywords return pending and are scored for a later call. — 110 credits per call.
- `POST /v1/backlinks/summary` — Backlink profile summary metrics for a domain or URL. — 20 credits per call.
- `POST /v1/backlinks/list` — Individual backlinks pointing at a domain or URL. — 50 credits per call.
- `POST /v1/backlinks/domains` — Domains that link to a target, with per-domain metrics. — 50 credits per call.
- `POST /v1/backlinks/anchors` — Anchor-text distribution of backlinks to a target. — 50 credits per call.
- `POST /v1/domains/overview` — Return a domain's organic and paid search overview for one market. — 10 credits per call.
- `POST /v1/page/lighthouse` — Lighthouse scores and core web vitals for a single page. — 2 credits per call.
- `POST /v1/page/crawl` — Render a single page and return a slim page-SEO snapshot. — 2 credits per call.
- `POST /v1/page/accessibility` — Axe accessibility scan of a single page — violations, keyboard-navigation checks, honest scan status. — 2 credits per call.
- `POST /v1/site/audit` — Crawl and audit a whole site; billed per delivered page (sum of enabled checks x pages delivered). — 2 credits per check per delivered page.
- `POST /v1/serp/history` — Position history for a (domain, keyword) pair from our SERP archive. — 5 credits per call.
- `POST /v1/domains/card` — Company card — identity, contacts, socials, technology from our crawl. — 10 credits per call.
- `POST /v1/keywords/questions` — People-Also-Ask questions observed for a topic, deduplicated. — 20 credits per call.
- `POST /v1/ai/visibility` — How often AI assistants mention a domain, per provider, over time. — 10 credits per call.
- `GET /v1/locations` — Look up Google Ads geotarget IDs by name — country, state/region, city, or neighborhood. — free, unmetered (`?q=` required).
- `POST /v1/domains/competitors` — Competitor discovery from the SERP archive: domains that rank for the same keywords, ranked by overlap. — 30 credits per call.
- `POST /v1/domains/gap` — Keyword gap between two domains: opportunity, shared, or unique rankings, volume-enriched. — 15 credits per call.

## What people use it for

- **Let an LLM pick what to optimize next** — An agent ranks your pages by winnable upside — positions, volume, difficulty, on-page gaps. (`/v1/search`, `/v1/keywords/volume`, `/v1/keywords/difficulty`, `/v1/page/crawl`)
- **Find backlink donors** — Mine competitors' referring domains into a ranked candidate list for vetting. (`/v1/backlinks/domains`, `/v1/backlinks/anchors`, `/v1/domains/overview`)
- **A rank tracker in a cron job** — Daily positions, diffed and alerted, for 1 credit per keyword per day. (`/v1/search`)
- **Fail the build when the site regresses** — Lighthouse + on-page checks on every deploy. (`/v1/page/lighthouse`, `/v1/page/crawl`, `/v1/site/audit`)
- **Find out who you're actually up against** — Competitors ranked by real keyword overlap from the SERP archive — not who you assume they are. (`/v1/domains/competitors`, `/v1/domains/overview`, `/v1/domains/gap`)
- **Find the content you're missing** — Keywords a competitor ranks for that you don't — volume-enriched, with the questions people actually ask. (`/v1/domains/gap`, `/v1/keywords/questions`, `/v1/keywords/difficulty`)
- **Vet a backlink donor before you pitch** — Spam score, authority, and the link-mix breakdown for any domain — 30 credits to skip a bad neighborhood. (`/v1/backlinks/summary`, `/v1/domains/overview`)
- **Track page performance over time** — Lighthouse scores and lab vitals in a CSV, with rank history sitting next to them. (`/v1/page/lighthouse`, `/v1/serp/history`)

## A worked example — A rank tracker in a cron job

Daily positions, diffed and alerted, for 1 credit per keyword per day.

```bash
#!/usr/bin/env bash
# tracker.sh -- daily rank tracker, cron-ready. keywords.txt: one keyword per line.
# cron: 15 6 * * *  cd /path/to/tracker && ./tracker.sh
set -euo pipefail
: "${SEOFETCH_KEY:?export SEOFETCH_KEY first}"
DOMAIN="${TRACK_DOMAIN:-yourdomain.com}"
TODAY=$(date -u +%F)
mkdir -p snapshots
OUT="snapshots/$TODAY.csv"
: > "$OUT"

while IFS= read -r kw; do
  [ -z "$kw" ] && continue
  # -w tacks the status code onto the last line.
  resp=$(curl -sS https://api.seofetch.com/v1/search \
    -H "Authorization: Bearer $SEOFETCH_KEY" \
    -H "Content-Type: application/json" \
    -d "$(jq -cn --arg q "$kw" '{query: $q}')" \
    -w $'\n%{http_code}')
  code=${resp##*$'\n'}
  body=${resp%$'\n'*}
  if [ "$code" != "200" ]; then
    # a 504 means the job kept running server-side past your connection --
    # the charge stands either way. Any non-2xx (401/429/504/500/...) is
    # never a "miss" -- skip it rather than parse the error body as data.
    echo "warning: $kw returned HTTP $code, skipping" >&2
    continue
  fi
  # "miss" = not in the returned results (top 10 at the default depth) --
  # the row survives so the diff below can see you drop out entirely
  rank=$(printf '%s' "$body" | jq -r --arg d "$DOMAIN" \
    '[.data.items[]? | select(.domain == $d) | .rank][0] // "miss"')
  printf '%s,%s\n' "$kw" "$rank" >> "$OUT"
done < keywords.txt

# diff against yesterday, alert on drops (macOS date -v / GNU date -d both handled)
PREV="snapshots/$(date -u -v-1d +%F 2>/dev/null || date -u -d yesterday +%F).csv"
if [ -f "$PREV" ]; then
  awk -F, 'NR==FNR { prev[$1]=$2; next }
    ($1 in prev) && prev[$1] != "miss" && $2 != "miss" && ($2+0) > (prev[$1]+0) \
      { print $1 ": " prev[$1] " -> " $2 }
    ($1 in prev) && prev[$1] != "miss" && $2 == "miss" \
      { print $1 ": " prev[$1] " -> miss (dropped out)" }' "$PREV" "$OUT" |
    sh -c "${ALERT_CMD:-cat}"   # e.g. ALERT_CMD="mail -s 'rank drops' you@example.com"
fi
```

## Going deeper

This overview is deliberately short. Every endpoint's exact request parameters (required fields, defaults, enums) and response fields are published as OpenAPI: https://api.seofetch.com/v1/openapi.json. For the whole docs corpus in one fetch — every page, the idempotency/retry contract, and a reference page per endpoint — see https://docs.seofetch.com/llms-full.txt.

endpoints

All the SEO data your tools need. Predictable credit costs.

Click any endpoint — the response shown is the real envelope, built from the live catalog.

Send a query to Google — or Bing, YouTube, Google Maps, and more — and get the parsed SERP back as clean JSON. Skip building and maintaining your own scraper.

→ requestPOST /v1/search

POST /v1/search HTTP/1.1
Authorization: Bearer sof_live_your_key_here
Content-Type: application/json

{
  "query": "best running shoes"
}

← response200 scrolls ↕

{
  "id": "srch_tnq5objwpmflh2poczbwxnfr",
  "request_id": "req_c7leybmgtzholcwoyhozbqsqkq",
  "object": "search",
  "created_at": "2026-08-08T16:50:38Z",
  "elapsed_ms": 142,
  "cache": "miss",
  "credits": {
    "charged": 1,
    "balance": 9857
  },
  "data": {
    "query": "best running shoes",
    "engine": "google",
    "location": 2840,
    "language": "en",
    "device": "desktop",
    "total_results": 84900000,
    "serp_url": "https://www.google.com/search?q=best+running+shoes",
    "result_types": [
      "organic"
    ],
    "results_count": 10,
    "items": [
      {
        "type": "organic",
        "rank": 1,
        "page": 1,
        "domain": "example.com",
        "title": "The 12 Best Running Shoes",
        "url": "https://example.com/best-running-shoes",
        "description": "Our team tested 40 pairs...",
        "displayed_link": "example.com › reviews › shoes",
        "date": null,
        "site_name": "Example Running Co.",
        "rating": {
          "value": 4.6,
          "votes": 1284,
          "max": 5
        },
        "sitelinks": [
          {
            "type": "sitelink",
            "title": "Best Trail Running Shoes",
            "description": null,
            "url": "https://example.com/best-running-shoes/trail"
          },
          {
            "type": "sitelink",
            "title": "Best Budget Running Shoes",
            "description": null,
            "url": "https://example.com/best-running-shoes/budget"
          }
        ],
        "price": null
      }
    ]
  }
}

200 OK1 credit

$ man search — full parameter reference in the docs →

See how many people search for a keyword each month, plus competition and cost-per-click, so you know which terms are actually worth targeting.

→ requestPOST /v1/keywords/volume

POST /v1/keywords/volume HTTP/1.1
Authorization: Bearer sof_live_your_key_here
Content-Type: application/json

{
  "keywords": [
    "running shoes",
    "trail running shoes"
  ],
  "location": "US",
  "language": "en"
}

← response200 scrolls ↕

{
  "id": "keyw_pp5fbbqcjo7vb4equba4fuxj",
  "request_id": "req_6cjg6ezmbvaunop2yxba5e3xj4",
  "object": "keyword_volume",
  "created_at": "2026-08-09T06:04:02Z",
  "elapsed_ms": 180,
  "cache": "miss",
  "credits": {
    "charged": 20,
    "balance": 9857
  },
  "data": {
    "location": {
      "code": 2840,
      "name": "United States"
    },
    "language": {
      "code": "en",
      "name": "English"
    },
    "network": "google_search",
    "items_count": 2,
    "items": [
      {
        "keyword": "running shoes",
        "avg_monthly_searches": 90500,
        "competition": "HIGH",
        "competition_index": 88,
        "cpc": 1.24,
        "low_bid": 0.42,
        "high_bid": 2.1,
        "monthly": [
          {
            "month": "2026-06",
            "search_volume": 91000
          },
          "…"
        ]
      },
      {
        "keyword": "trail running shoes",
        "avg_monthly_searches": 8100,
        "competition": "MEDIUM",
        "competition_index": 54,
        "cpc": 0.87,
        "low_bid": 0.31,
        "high_bid": 1.55,
        "monthly": [
          {
            "month": "2026-06",
            "search_volume": 8300
          },
          "…"
        ]
      }
    ]
  }
}

200 OK20 credits

$ man volume — full parameter reference in the docs →

Score how hard a keyword is to rank for on a 0-100 scale, so you can pick winnable terms instead of guessing. An unscored keyword comes back pending — retry it on a later call to get the score.

→ requestPOST /v1/keywords/difficulty

POST /v1/keywords/difficulty HTTP/1.1
Authorization: Bearer sof_live_your_key_here
Content-Type: application/json

{
  "keywords": [
    "buy running shoes",
    "cold keyword"
  ],
  "location": 2840,
  "language": "en"
}

← response200 scrolls ↕

{
  "id": "keyw_rgzbcawvyegkzrxewmrtq2dy",
  "request_id": "req_yqknvk5fdrc7xk7c26xfyo2xyi",
  "object": "keyword_difficulty",
  "created_at": "2026-08-09T06:04:02Z",
  "elapsed_ms": 180,
  "cache": "miss",
  "credits": {
    "charged": 110,
    "balance": 9857
  },
  "data": {
    "items_count": 2,
    "items": [
      {
        "keyword": "buy running shoes",
        "difficulty": 42,
        "status": "available"
      },
      {
        "keyword": "cold keyword",
        "difficulty": null,
        "status": "pending"
      }
    ]
  }
}

200 OK110 credits

$ man difficulty — full parameter reference in the docs →

Get the headline backlink numbers for any domain — authority, referring domains, spam score — in one call, before you dig into the full link list.

→ requestPOST /v1/backlinks/summary

POST /v1/backlinks/summary HTTP/1.1
Authorization: Bearer sof_live_your_key_here
Content-Type: application/json

{
  "target": "example.com"
}

← response200 scrolls ↕

{
  "id": "back_v2gpcxzdgylckjjeupxlvloo",
  "request_id": "req_xlzrdsbin5bqlb3wgnpzvhtw5y",
  "object": "backlink_summary",
  "created_at": "2026-08-09T06:04:02Z",
  "elapsed_ms": 180,
  "cache": "miss",
  "credits": {
    "charged": 20,
    "balance": 9857
  },
  "data": {
    "target": "example.com",
    "authority": 33,
    "backlinks": 617091,
    "spam_score": 9,
    "referring_domains": 3582,
    "referring_root_domains": 3160,
    "referring_pages": 210044,
    "link_breakdown": {
      "tlds": {
        "com": 2891,
        "net": 412,
        "org": 279
      },
      "types": {
        "anchor": 17226,
        "image": 421,
        "redirect": 12
      },
      "attributes": {
        "nofollow": 1769,
        "ugc": 340,
        "external": 88,
        "sponsored": 26
      },
      "platforms": {
        "blogs": 3021,
        "cms": 1104,
        "news": 214
      },
      "page_sections": {
        "article": 12904,
        "footer": 2200,
        "section": 1122
      },
      "countries": {
        "US": 9821,
        "GB": 2011,
        "DE": 1502
      }
    }
  }
}

200 OK20 credits

$ man summary — full parameter reference in the docs →

Pull the individual links pointing at a domain, with source page, anchor text, and follow status — the raw data behind a link-building audit.

→ requestPOST /v1/backlinks/list

POST /v1/backlinks/list HTTP/1.1
Authorization: Bearer sof_live_your_key_here
Content-Type: application/json

{
  "target": "example.com",
  "limit": 100,
  "offset": 0
}

← response200 scrolls ↕

{
  "id": "back_ehr5wf2qnowojpfktdruon56",
  "request_id": "req_b7wiuzceavgfnojyt23l7tevoe",
  "object": "backlink_list",
  "created_at": "2026-08-09T06:04:02Z",
  "elapsed_ms": 180,
  "cache": "miss",
  "credits": {
    "charged": 50,
    "balance": 9857
  },
  "data": {
    "target": "example.com",
    "total_count": 355648,
    "limit": 100,
    "offset": 0,
    "items": [
      {
        "source_url": "https://blog.example.net/best-shoes",
        "target_url": "https://example.com/",
        "source_domain": "blog.example.net",
        "target_domain": "example.com",
        "anchor": "running shoes guide",
        "dofollow": true,
        "first_seen": "2024-03-11",
        "last_seen": "2026-06-02",
        "authority": 54,
        "spam_score": 0
      },
      "…"
    ]
  }
}

200 OK50 credits

$ man list — full parameter reference in the docs →

See which domains link to a target, with backlink counts and authority per domain, and whether each domain's link to you is still live or has been lost.

→ requestPOST /v1/backlinks/domains

POST /v1/backlinks/domains HTTP/1.1
Authorization: Bearer sof_live_your_key_here
Content-Type: application/json

{
  "target": "example.com",
  "limit": 100,
  "offset": 0
}

← response200 scrolls ↕

{
  "id": "refe_l3b7jswihfkyz6kqfvlcsr4q",
  "request_id": "req_76owuof2fzavzfij2jxba6tcya",
  "object": "referring_domains",
  "created_at": "2026-08-09T06:04:02Z",
  "elapsed_ms": 180,
  "cache": "miss",
  "credits": {
    "charged": 50,
    "balance": 9857
  },
  "data": {
    "target": "example.com",
    "total_count": 3160,
    "limit": 100,
    "offset": 0,
    "items": [
      {
        "domain": "caglrc.cc",
        "backlinks": 526,
        "first_seen": "2023-11-02",
        "lost_at": null,
        "authority": 27,
        "spam_score": 0
      },
      "…"
    ]
  }
}

200 OK50 credits

$ man domains — full parameter reference in the docs →

Break down the anchor text used across every backlink pointing at a domain, so you can catch over-optimization before Google does.

→ requestPOST /v1/backlinks/anchors

POST /v1/backlinks/anchors HTTP/1.1
Authorization: Bearer sof_live_your_key_here
Content-Type: application/json

{
  "target": "example.com",
  "limit": 100,
  "offset": 0
}

← response200 scrolls ↕

{
  "id": "back_v3wa5og57rr4igbndah4qvki",
  "request_id": "req_ik6bagpqrrccfnysb6azzpiscu",
  "object": "backlink_anchors",
  "created_at": "2026-08-09T06:04:02Z",
  "elapsed_ms": 180,
  "cache": "miss",
  "credits": {
    "charged": 50,
    "balance": 9857
  },
  "data": {
    "target": "example.com",
    "total_count": 3316,
    "limit": 100,
    "offset": 0,
    "items": [
      {
        "anchor": "running shoes",
        "backlinks": 597726,
        "referring_domains": 247,
        "first_seen": "2023-05-14"
      },
      {
        "anchor": null,
        "backlinks": 1201,
        "referring_domains": 88,
        "first_seen": "2024-01-09"
      },
      "…"
    ]
  }
}

200 OK50 credits

$ man anchors — full parameter reference in the docs →

Get organic and paid search visibility for a domain in one market, in a single call — keyword count, traffic estimate, and ranking distribution.

→ requestPOST /v1/domains/overview

POST /v1/domains/overview HTTP/1.1
Authorization: Bearer sof_live_your_key_here
Content-Type: application/json

{
  "domain": "example.com",
  "location": 2840,
  "language": "en"
}

← response200 scrolls ↕

{
  "id": "doma_x24ytvn424pu2fbflvozwrjv",
  "request_id": "req_igsmmqqwezcalatqz2rfdgb7ti",
  "object": "domain_overview",
  "created_at": "2026-08-09T06:04:02Z",
  "elapsed_ms": 180,
  "cache": "miss",
  "credits": {
    "charged": 10,
    "balance": 9857
  },
  "data": {
    "organic": {
      "keywords_count": 101,
      "traffic_estimate": 70.17,
      "traffic_value": 704.38,
      "positions": {
        "top_3": 0,
        "top_10": 3,
        "top_20": 11,
        "top_100": 101
      }
    },
    "paid": {
      "keywords_count": 0,
      "traffic_estimate": 0,
      "traffic_value": 0,
      "positions": {
        "top_3": 0,
        "top_10": 0,
        "top_20": 0,
        "top_100": 0
      }
    }
  }
}

200 OK10 credits

$ man overview — full parameter reference in the docs →

Run a real Lighthouse audit on any page and get back Core Web Vitals and category scores — performance, accessibility, best practices, and SEO, all in one call.

→ requestPOST /v1/page/lighthouse

POST /v1/page/lighthouse HTTP/1.1
Authorization: Bearer sof_live_your_key_here
Content-Type: application/json

{
  "url": "https://example.com/",
  "device": "mobile"
}

← response200 scrolls ↕

{
  "id": "ligh_zev6tf2fhs4jrfwmwajb3fbv",
  "request_id": "req_nwuuoqwgs5bl7jkuodbnaacqoi",
  "object": "lighthouse",
  "created_at": "2026-08-09T06:04:02Z",
  "elapsed_ms": 180,
  "cache": "miss",
  "credits": {
    "charged": 2,
    "balance": 9857
  },
  "data": {
    "url": "https://example.com/",
    "device": "mobile",
    "scores": {
      "performance": 100,
      "accessibility": 96,
      "best_practices": 96,
      "seo": 80
    },
    "metrics": {
      "lcp_ms": 762,
      "fcp_ms": 611,
      "cls": 0.02,
      "tbt_ms": 40,
      "si_ms": 900,
      "tti_ms": 1100
    },
    "fetched_at": "2026-07-26T10:15:00Z",
    "audits": {
      "largest-contentful-paint": {
        "id": "largest-contentful-paint",
        "title": "Largest Contentful Paint",
        "description": "Largest Contentful Paint marks the time at which the largest text or image is painted.",
        "score": 1,
        "scoreDisplayMode": "numeric",
        "numericValue": 762.4,
        "numericUnit": "millisecond",
        "displayValue": "0.8 s",
        "scoringOptions": {
          "p10": 2500,
          "median": 4000
        }
      },
      "…": "…"
    },
    "screenshots": {
      "full_page": {
        "data": "data:image/webp;base64,…",
        "width": 412,
        "height": 6200
      },
      "final": {
        "data": "data:image/webp;base64,…"
      },
      "thumbnails": [
        {
          "data": "data:image/webp;base64,…",
          "timing": 375
        },
        "…"
      ]
    }
  }
}

200 OK2 credits

$ man lighthouse — full parameter reference in the docs →

Render a page and pull its on-page SEO signals — title, meta description, headings, links, images — without writing your own crawler.

→ requestPOST /v1/page/crawl

POST /v1/page/crawl HTTP/1.1
Authorization: Bearer sof_live_your_key_here
Content-Type: application/json

{
  "url": "https://example.com/"
}

← response200 scrolls ↕

{
  "id": "craw_2qkmc2gx6dpqtvtllpp6ipgy",
  "request_id": "req_nlniyys65fd6zi776yuubzbgdu",
  "object": "crawl",
  "created_at": "2026-08-09T06:04:02Z",
  "elapsed_ms": 180,
  "cache": "miss",
  "credits": {
    "charged": 2,
    "balance": 9857
  },
  "data": {
    "url": "https://example.com/",
    "final_url": "https://example.com/",
    "http_status": 200,
    "title": "Example Domain",
    "meta_description": "An example page used for documentation.",
    "canonical": "https://example.com/",
    "headings": {
      "h1_count": 1,
      "h2_count": 2
    },
    "links": {
      "internal": 2,
      "external": 1
    },
    "images": {
      "total": 2,
      "missing_alt": 1
    },
    "is_html": true,
    "load_ms": 812
  }
}

200 OK2 credits

$ man crawl — full parameter reference in the docs →

Run an axe accessibility scan on any page and get real violations, keyboard-navigation checks, and honest scan status back, not just a pass/fail badge.

→ requestPOST /v1/page/accessibility

POST /v1/page/accessibility HTTP/1.1
Authorization: Bearer sof_live_your_key_here
Content-Type: application/json

{
  "url": "https://seojuice.io/"
}

← response200 scrolls ↕

{
  "id": "acce_tfocgcs4fuuws4pewk5gxhrn",
  "request_id": "req_jny75urfnndr7hp4daujwi674q",
  "object": "accessibility",
  "created_at": "2026-08-09T06:04:02Z",
  "elapsed_ms": 180,
  "cache": "miss",
  "credits": {
    "charged": 2,
    "balance": 9857
  },
  "data": {
    "url": "https://seojuice.io/",
    "status": "complete",
    "violations": [
      {
        "id": "color-contrast",
        "impact": "serious",
        "help": "Elements must meet minimum color contrast ratio thresholds",
        "help_url": "https://dequeuniversity.com/rules/axe/4.10/color-contrast?application=axeAPI",
        "nodes_count": 77
      }
    ],
    "passes_count": 23,
    "incomplete_count": 1,
    "keyboard": {
      "interactive_total": 100,
      "reached": 95,
      "focus_trap": false,
      "has_skip_link": false
    },
    "engine": {
      "axe_version": "4.10.3"
    }
  }
}

200 OK2 credits

$ man accessibility — full parameter reference in the docs →

Crawl a whole site and run the checks you choose — crawl, Lighthouse, accessibility — across every page in one job, billed only for pages actually delivered, not pages requested.

→ requestPOST /v1/site/audit

POST /v1/site/audit HTTP/1.1
Authorization: Bearer sof_live_your_key_here
Content-Type: application/json

{
  "domain": "example.com",
  "max_pages": 5,
  "checks": [
    "crawl",
    "lighthouse"
  ],
  "device": "mobile"
}

← response200 scrolls ↕

{
  "id": "site_m3uxi7ke66nd56tgfzx4tm6c",
  "request_id": "req_3xkt6mrleve25jfdf2nb4gr6l4",
  "object": "site_audit",
  "created_at": "2026-08-09T06:04:02Z",
  "elapsed_ms": 180,
  "cache": "miss",
  "credits": {
    "charged": 12,
    "balance": 9857
  },
  "data": {
    "domain": "example.com",
    "pages_requested": 5,
    "pages_crawled": 4,
    "pages_delivered": 3,
    "credits_charged": 12,
    "pages": [
      {
        "url": "https://example.com/",
        "status": "ok",
        "crawl": {
          "http_status": 200,
          "links": {
            "internal": 2,
            "external": 0
          }
        },
        "lighthouse": {
          "device": "mobile",
          "scores": {
            "performance": 90,
            "accessibility": 91,
            "best_practices": 93,
            "seo": 80
          }
        }
      },
      "…"
    ],
    "summary": {
      "score": {
        "value": 82,
        "band": "excellent",
        "grade": "A"
      },
      "axes": [
        {
          "key": "speed",
          "score": 73,
          "band": "good"
        }
      ],
      "issues": {
        "critical": 2,
        "major": 1,
        "minor": 1
      },
      "broken_links": 1,
      "pages_with_errors": 1
    }
  }
}

200 OK12 credits

$ man audit — full parameter reference in the docs →

Track how a domain has ranked for a keyword over time — the days we have an archived observation for, plus the best rank reached — pulled from our own SERP archive instead of running your own rank checks.

→ requestPOST /v1/serp/history

POST /v1/serp/history HTTP/1.1
Authorization: Bearer sof_live_your_key_here
Content-Type: application/json

{
  "domain": "example.com",
  "keyword": "best running shoes",
  "engine": "google",
  "location": 2840,
  "language": "en",
  "device": "desktop",
  "date_from": "2026-05-20",
  "date_to": "2026-07-28"
}

← response200 scrolls ↕

{
  "id": "serp_z4py5vqdaq5nd4zchcbuwtt3",
  "request_id": "req_n46nrygbznhj5pxwqmbzxuxvwm",
  "object": "serp_history",
  "created_at": "2026-08-09T06:04:02Z",
  "elapsed_ms": 180,
  "cache": "miss",
  "credits": {
    "charged": 5,
    "balance": 9857
  },
  "data": {
    "domain": "example.com",
    "keyword": "best running shoes",
    "engine": "google",
    "location": 2840,
    "language": "en",
    "device": "desktop",
    "points": [
      {
        "date": "2026-06-03",
        "rank": 9,
        "url": "https://example.com/best-running-shoes",
        "type": "organic"
      },
      {
        "date": "2026-06-17",
        "rank": 6,
        "url": "https://example.com/best-running-shoes",
        "type": "organic"
      }
    ],
    "first_seen": "2026-06-03",
    "best_rank": 6,
    "coverage": {
      "from": "2026-05-20",
      "observations": 14
    }
  }
}

200 OK5 credits

$ man history — full parameter reference in the docs →

Get a company's identity in one call — name, description, contacts, socials, and tech stack — built from our own crawl of the domain; any field we couldn't identify comes back null.

→ requestPOST /v1/domains/card

POST /v1/domains/card HTTP/1.1
Authorization: Bearer sof_live_your_key_here
Content-Type: application/json

{
  "domain": "example.com"
}

← response200 scrolls ↕

{
  "id": "doma_bwrwrvj2cc6wg2adjt6i4cqi",
  "request_id": "req_ej32qsj6evepreeu66rkhoipgy",
  "object": "domain_card",
  "created_at": "2026-08-09T06:04:02Z",
  "elapsed_ms": 180,
  "cache": "miss",
  "credits": {
    "charged": 10,
    "balance": 9857
  },
  "data": {
    "domain": "example.com",
    "site_name": "Example Inc.",
    "description": "Compression socks for trail runners.",
    "logo_url": "https://example.com/logo.svg",
    "emails": [
      "hello@example.com"
    ],
    "phones": [
      "+1 415 555 0100"
    ],
    "postal_address": "548 Market St, San Francisco, CA",
    "social_profiles": {
      "linkedin": "https://linkedin.com/company/example",
      "x": "https://x.com/example"
    },
    "technology": {
      "cms": "wordpress",
      "framework": null,
      "server": "nginx",
      "hosting": "cloudflare"
    },
    "country": "US",
    "language": "en",
    "as_of": "2026-07-21"
  }
}

200 OK10 credits

$ man card — full parameter reference in the docs →

Pull the real questions people ask about a topic, deduplicated and ready to seed FAQ pages or content briefs.

→ requestPOST /v1/keywords/questions

POST /v1/keywords/questions HTTP/1.1
Authorization: Bearer sof_live_your_key_here
Content-Type: application/json

{
  "keyword": "running shoes",
  "location": 2840,
  "language": "en",
  "limit": 50
}

← response200 scrolls ↕

{
  "id": "keyw_5hcavbzbjerrwt46ptj4zvfl",
  "request_id": "req_d2y2ruhapjg3zeo7iucb5dbgce",
  "object": "keyword_questions",
  "created_at": "2026-08-09T06:04:02Z",
  "elapsed_ms": 180,
  "cache": "miss",
  "credits": {
    "charged": 20,
    "balance": 9857
  },
  "data": {
    "keyword": "running shoes",
    "items": [
      {
        "question": "How often should you replace running shoes?",
        "first_seen": "2026-06-11",
        "last_seen": "2026-07-25",
        "times_seen": 18
      },
      {
        "question": "Are carbon plate shoes worth it?",
        "first_seen": "2026-07-02",
        "last_seen": "2026-07-27",
        "times_seen": 7
      },
      "…"
    ],
    "count": 42,
    "coverage": {
      "from": "2026-07-01",
      "observations": 130
    }
  }
}

200 OK20 credits

$ man questions — full parameter reference in the docs →

Track how often ChatGPT, Perplexity, Gemini, Copilot, and Le Chat mention a domain — mentions and rank trending over time, plus an overall sentiment score per provider — visibility data search rankings alone cannot show you.

→ requestPOST /v1/ai/visibility

POST /v1/ai/visibility HTTP/1.1
Authorization: Bearer sof_live_your_key_here
Content-Type: application/json

{
  "domain": "example.com",
  "providers": [
    "chatgpt",
    "perplexity"
  ],
  "date_from": "2026-06-01",
  "date_to": "2026-07-28",
  "granularity": "week"
}

← response200 scrolls ↕

{
  "id": "ai_v_5swck5dwqohp4vl63bqbqvbg",
  "request_id": "req_evkoh5updnbq3oorqmuwzivnpu",
  "object": "ai_visibility",
  "created_at": "2026-08-09T06:04:02Z",
  "elapsed_ms": 180,
  "cache": "miss",
  "credits": {
    "charged": 10,
    "balance": 9857
  },
  "data": {
    "domain": "example.com",
    "providers": {
      "chatgpt": {
        "mentions": 41,
        "prompts_seen": 380,
        "avg_rank": 2.6,
        "avg_sentiment": 0.31,
        "series": [
          {
            "period": "2026-07-14",
            "mentions": 6,
            "prompts_seen": 55,
            "avg_rank": 2.2
          },
          {
            "period": "2026-07-21",
            "mentions": 9,
            "prompts_seen": 61,
            "avg_rank": 2.9
          }
        ]
      },
      "perplexity": {
        "mentions": 12,
        "prompts_seen": 140,
        "avg_rank": 3.4,
        "avg_sentiment": 0.12,
        "series": []
      }
    },
    "coverage": {
      "from": "2026-06-01",
      "observations": 520,
      "note": "mentions are drawn from prompts run through this API; not a census of all AI traffic"
    }
  }
}

200 OK10 credits

$ man visibility — full parameter reference in the docs →

Look up the exact geotarget ID for any country, state, city, or neighborhood — the geotarget ID other endpoints take for their location parameter, and it costs nothing.

→ requestGET /v1/locations

GET /v1/locations?q=austin+texas HTTP/1.1
Authorization: Bearer sof_live_your_key_here

← response200 scrolls ↕

{
  "id": "loca_5p6wuqir5dqnqlcgxduaskl3",
  "request_id": "req_4btuqf76argufiuohh3rnh6pye",
  "object": "location_list",
  "created_at": "2026-08-09T06:04:02Z",
  "elapsed_ms": 180,
  "cache": "miss",
  "credits": {
    "charged": 0,
    "balance": 9857
  },
  "data": {
    "locations": [
      {
        "id": 1026201,
        "name": "Austin,Texas,United States",
        "type": "city",
        "country": "US",
        "parent_id": 21176
      },
      {
        "id": 9198393,
        "name": "Central Austin,Texas,United States",
        "type": "neighborhood",
        "country": "US",
        "parent_id": 21176
      },
      {
        "id": 9060225,
        "name": "Downtown Austin,Texas,United States",
        "type": "neighborhood",
        "country": "US",
        "parent_id": 21176
      },
      {
        "id": 9198961,
        "name": "East Austin,Texas,United States",
        "type": "neighborhood",
        "country": "US",
        "parent_id": 21176
      },
      {
        "id": 9194496,
        "name": "Old West Austin,Texas,United States",
        "type": "neighborhood",
        "country": "US",
        "parent_id": 21176
      },
      {
        "id": 9197266,
        "name": "South Austin,Texas,United States",
        "type": "neighborhood",
        "country": "US",
        "parent_id": 21176
      }
    ]
  }
}

200 OKfree

$ man locations — full parameter reference in the docs →

Find the domains actually competing with a domain in search, ranked by keyword overlap instead of who you assume the competitors are.

→ requestPOST /v1/domains/competitors

POST /v1/domains/competitors HTTP/1.1
Authorization: Bearer sof_live_your_key_here
Content-Type: application/json

{
  "domain": "semrush.com",
  "engine": "google",
  "location": 2840,
  "language": "en",
  "device": "desktop",
  "limit": 25
}

← response200 scrolls ↕

{
  "id": "doma_b6nvdov2zejxapnuhgga5qbj",
  "request_id": "req_vg2u5y5ebnf3hpu7wwlwvgxds4",
  "object": "domain_competitors",
  "created_at": "2026-08-09T06:04:02Z",
  "elapsed_ms": 180,
  "cache": "miss",
  "credits": {
    "charged": 30,
    "balance": 9857
  },
  "data": {
    "domain": "semrush.com",
    "keywords_total": 2834,
    "keywords_considered": 200,
    "total_competitors": 1743,
    "competitors": [
      {
        "domain": "reddit.com",
        "shared_keywords": 106,
        "keywords_total": 114768,
        "avg_rank": 3.9,
        "target_avg_rank": 1,
        "overlap": 0.53,
        "shared_volume": 370910,
        "sample_keywords": [
          {
            "keyword": "google search console",
            "volume": 368000
          },
          "…"
        ]
      },
      "…"
    ],
    "coverage": {
      "from": "2026-05-20",
      "observations": 200
    }
  }
}

200 OK30 credits

$ man competitors — full parameter reference in the docs →

Compare rankings for two domains side by side — gap, shared, or unique keywords — with search volume attached, so you know exactly which keywords are worth chasing.

→ requestPOST /v1/domains/gap

POST /v1/domains/gap HTTP/1.1
Authorization: Bearer sof_live_your_key_here
Content-Type: application/json

{
  "domains": [
    "semrush.com",
    "ahrefs.com"
  ],
  "mode": "gap",
  "engine": "google",
  "location": 2840,
  "language": "en",
  "device": "desktop",
  "limit": 100,
  "offset": 0
}

← response200 scrolls ↕

{
  "id": "doma_fwctm7f4g3rb3ls75f7k3mlb",
  "request_id": "req_o4lrprfcejh3pknjx4chktvzie",
  "object": "domain_gap",
  "created_at": "2026-08-09T06:04:02Z",
  "elapsed_ms": 180,
  "cache": "miss",
  "credits": {
    "charged": 15,
    "balance": 9857
  },
  "data": {
    "mode": "gap",
    "domains": [
      "semrush.com",
      "ahrefs.com"
    ],
    "items": [
      {
        "keyword": "search engine optimization",
        "volume": 18100,
        "ranks": [
          null,
          {
            "rank": 27,
            "url": "https://ahrefs.com/blog/what-is-seo/",
            "date": "2026-06-28"
          }
        ]
      },
      "…"
    ],
    "totals": [
      2834,
      1315
    ],
    "matched_count": 409,
    "coverage": {
      "from": "2026-06-28",
      "observations": 409
    },
    "limit": 100,
    "offset": 0
  }
}

200 OK15 credits

$ man gap — full parameter reference in the docs →

examples

What people build with it.

Let an LLM pick what to optimize next

An agent ranks your pages by winnable upside — positions, volume, difficulty, on-page gaps.

/v1/search/v1/keywords/volume/v1/keywords/difficulty/v1/page/crawl

$ read example →

Find backlink donors

Mine competitors' referring domains into a ranked candidate list for vetting.

/v1/backlinks/domains/v1/backlinks/anchors/v1/domains/overview

$ read example →

A rank tracker in a cron job

Daily positions, diffed and alerted, for 1 credit per keyword per day.

/v1/search

$ read example →

Fail the build when the site regresses

Lighthouse + on-page checks on every deploy.

/v1/page/lighthouse/v1/page/crawl/v1/site/audit

$ read example →

Find out who you're actually up against

Competitors ranked by real keyword overlap from the SERP archive — not who you assume they are.

/v1/domains/competitors/v1/domains/overview/v1/domains/gap

$ read example →

Find the content you're missing

Keywords a competitor ranks for that you don't — volume-enriched, with the questions people actually ask.

/v1/domains/gap/v1/keywords/questions/v1/keywords/difficulty

$ read example →

Vet a backlink donor before you pitch

Spam score, authority, and the link-mix breakdown for any domain — 30 credits to skip a bad neighborhood.

/v1/backlinks/summary/v1/domains/overview

$ read example →

Track page performance over time

Lighthouse scores and lab vitals in a CSV, with rank history sitting next to them.

/v1/page/lighthouse/v1/serp/history

$ read example →

pricing

Prepaid credits. No subscription.

$49

10,000 credits

$0.0049 / credit

Get started

Infrastructure-grade, by design.

The playbook that made payments programmable — one consistent API, idempotency everywhere, metered pricing, failures that make themselves right — applied to SEO data.

usage feedbalance 10,000

/v1/search138 ms−1200

/v1/backlinks/summary612 ms−20200

/v1/page/lighthouse5.9 s−2200

usage metering

Metered like a utility

Per-request pricing, timed and logged. Your usage feed is the invoice — no seats, no tiers to outgrow.

{ envelope — never changes
  "id", "request_id", "object", 🔒
  "created_at", "elapsed_ms", "cache", "credits", 🔒
  "data": { "query", "items[rank, title, domain]" }
}

same envelope since v1every endpoint

one envelope

One API to learn

The envelope never changes — learn it once and every endpoint behaves identically.

idempotency-key: kd-001attempt 1

POST /v1/keywords/difficulty

job running…charged 110 cr

retries are free

Idempotent by default

Same key, same result, one charge. Crashed cron, flaky network, long job — retries are always free.

POST /v1/keywords/volume — one request

"trail running shoes"#1

"running shoes for flat feet"#2

"carbon plate shoes"#3

keywords 3 / 500price 20 cr — flat

batch scale

Built for bulk

One keyword or five hundred in a single call — same envelope, one flat price.

rank · "best running shoes"#6

1 credit / keyword / daysame request_id = free re-read

daily data

Dependable enough to build on

Fresh daily, stable ids, replayable results — treat it as an input, not a report.

agent: find pages worth optimizing

○/v1/searchrank 7

○/v1/keywords/volume135k/mo

○/v1/keywords/difficultyKD 41 — winnable

○/v1/page/crawlmeta missing

→ verdict: rewrite /blog/shoes — upside 135k/mo · 133 cr spent

composable

Primitives, not features

JSON in, JSON out, fixed costs — compose them into trackers, audit gates, agents.

faq

Questions.

What is a credit?

A unit of API usage. Most endpoints cost a flat number of credits per request. /v1/search is depth-tiered (1 or 10), /v1/site/audit is billed per delivered page, /v1/locations is free. Credits don't expire.

What are the rate limits?

100 requests per second per organization.

What happens if I run out of credits?

Requests return 402 Payment Required until you top up.

Do failed requests cost credits?

Upstream failures are refunded automatically. A 504 covers two different situations — check the error's code, not just the status. connection_timeout means the job is still running and the charge stands, nothing to refund yet: reconnect with the same key you sent — or, if you called keyless, with the request_id from that response — to collect the result once it's ready. upstream_timeout means the upstream itself gave up: that's a definite failure, refunded automatically like any other.

Are requests synchronous?

Yes — you get the result on the same connection, up to each endpoint's ceiling (60s for most; /v1/search runs to 180s, /v1/site/audit to 600s — see the per-endpoint ceilings in the docs). If it's still running you get a 504; reconnect with the same key you sent — or, if you called keyless, with the request_id from that response.

$ seofetch signup — 1,500 credits granted

Start with 1,500 free credits.

No credit card required.

Get your API key