seo-apilisted

DataForSEO API integration architect for developers. Covers the entire DataForSEO surface — DataForSEO Labs (ranked keywords, keyword ideas/suggestions/related, domain rank overview, competitors, domain/page intersection, subdomains, relevant pages, bulk keyword difficulty, bulk traffic estimation, search intent, historical rank/keyword/SERP data, top searches), SERP (Google + YouTube organic live advanced), Keywords Data (Google Ads search volume, Google Trends, DFS Trends), Backlinks (summary, backlinks, anchors, referring domains/networks, competitors, intersections, bulk metrics, time series), On-Page (instant pages, Lighthouse, content parsing), AI Optimization (LLM mention metrics, ChatGPT scraper, live LLM response, AI keyword data), and Merchant/Business data. For any "how do I…" question about endpoints, parameters, JSON bodies, per-call cost, rate limits, or authentication. Produces ready-to-paste cURL / Python / TypeScript / MCP-tool-call recipes against `https://api.dataforseo.com/v3/*` (HTTP Basi
amirjahfar1/automate-seo-with-claude · ★ 0 · AI & Automation · score 72

Install: claude install-skill amirjahfar1/automate-seo-with-claude

> Built on the DataForSEO MCP server (`mcp__dataforseo__*` tools) and the REST API at `https://api.dataforseo.com/v3/*`. Tool names are cross-checked against the connected server so reference data is never stale. # DataForSEO API Integration Architect Help developers ship real integrations against the DataForSEO API. The deliverable is a **code recipe** — a ready-to-paste cURL / Python / TypeScript / MCP-tool-call sequence — for the goal the user describes. The skill knows the whole DataForSEO surface (Labs / SERP / Keywords Data / Backlinks / On-Page / AI Optimization / Merchant & Business Data), the pay-per-call cost model, the Basic-auth setup, and which `mcp__dataforseo__*` tool maps to which REST endpoint. DataForSEO is **stateless** — it stores nothing on the user's behalf. There are no saved projects, no stored rank tracking, no project-attached audits. Anything that needs to persist between runs is built on a first-party companion (GSC for the own verified site, GA4 for own traffic) or the user's own local storage — never on DataForSEO. There is therefore no "create project / confirm mutation" flow in this skill: DataForSEO calls are read-shaped requests that change no account state. ## Prerequisites - **DataForSEO MCP server connected.** The skill calls `mcp__dataforseo__*` tools. The server authenticates with **HTTP Basic auth** using `DATAFORSEO_USERNAME` / `DATAFORSEO_PASSWORD` env vars (no OAuth, no shared key). If `/mcp` doesn't list `dataforseo`, emit the