# Semrush MCP

Use for **per-database organic visibility** across markets — Semrush's database-per-market model is well-suited to international SEO comparison.

Call pattern: discovery → `get_report_schema` → `execute_report`.

## Per-market comparison pattern

```
# Pull organic positions per database (one call per target market)
mcp__semrush__organic_research(query="<domain>", database="us")
mcp__semrush__organic_research(query="<domain>", database="kr")
mcp__semrush__organic_research(query="<domain>", database="jp")
mcp__semrush__organic_research(query="<domain>", database="cn")
mcp__semrush__organic_research(query="<domain>", database="de")

# Cross-market visibility deltas surface content-parity gaps from a ranking perspective
```

## Key reports

- `organic_research` — keywords/positions per `database`
- `overview_research` — domain traffic per market
- `siteaudit_research` — site-wide audit (catches hreflang issues with limitations)
- `keyword_research` — per-market keyword expansion

## Strengths for this skill

- Quickest "where am I ranking in market X vs market Y" comparison.
- Easy cross-database competitor pulls.

## Not for this skill when

- **Hreflang validation / parity audit / fix** — OurSEO is the default; only it owns the fix engine.
- **Forced-redirect / Accept-Language audit** — WebFetch with explicit headers.
- **Naver / regional engines** — Semrush is Google-only.