---
name: citestat-seo-audit
description: Audit a web page's SEO and AI-search readiness with the CiteStat API: score, graded findings with fixes, and how AI search engines would cite the page. Use when the user asks to check, audit or compare a website's SEO, GEO or agent readiness.
---

# CiteStat SEO audit

CiteStat (https://citestat.com/) checks one URL against more than 300 rules (on-page, technical, schema, performance,
content, GEO / AI visibility, agent readiness) and returns a 0-100 score with findings and fixes.

## Before you call

- An API key is required: `Authorization: Bearer <key>`. The user creates one on the dashboard
  (https://citestat.com/en/dashboard/api-keys). Never invent or reuse a key you were not given.
- Each scan costs 1 credit. The free plan has 10 credits a day; plans: https://citestat.com/pricing.
- Scan only URLs the user asked about.

## Scan one URL

```bash
curl -X POST https://citestat.com/api/scan \
  -H "Authorization: Bearer $CITESTAT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://example.com/page", "skipPerf": true}'
```

`skipPerf: true` skips PageSpeed (faster); leave it out when the user asks about speed or Core Web Vitals.

## Read the result

- `totalScore` (0-100) and `grade` — the headline. `headline` shows how it was derived.
- `scores[]` — one entry per category with its score; `findings[]` — every finding.
- A finding has `severity` (critical, high, medium, low, pass), `title`, `detail`, `fix`, and often
  `wikiSlug`: explain it with https://citestat.com/wiki/<wikiSlug>.
- Report the critical and high findings first, each with its fix. Do not list passes unless asked.
- HTTP 429 with `"code":"credit_limit"` means the day's credits are used up — tell the user; do not retry.

## More

- Full API reference: https://citestat.com/docs/api.md
- MCP server tools: https://citestat.com/docs/mcp.md