SEO DataForSEO

## Quick judgment Strong, specialized SEO research skill built on the DataForSEO API. Well-suited for agents that need structured keyword, YouTube, SERP, and competitor insights, and can manage an external paid API key. Less ideal where no external credentials are available or where API cost/quotas are a concern. --- ### What this skill does well - **Comprehensive SEO workflows**: High-level functions like `keyword_research`, `youtube_keyword_research`, `full_keyword_analysis`, `landing_page_keyword_research`, `competitor_analysis`, and `trending_topics` cover most practical SEO research needs. - **Automatic structured output**: All research runs auto-save JSON to `results/` (subfolders for keywords, labs, SERP, trends) with timestamped filenames, making it easy for downstream tools or agents to re-use data. - **Post-processing support**: Utility helpers (`list_results`, `load_result`, `get_latest_result`, `get_recent_results`, `load_latest`) make it straightforward to fetch the latest or relevant datasets for summarization or reporting. - **Supports strategic planning**: Functions combine difficulty, intent, historical volume, and trend data to help prioritize topics, not just generate raw keyword lists. --- ### Key risks and limitations 1. **External API dependency** - Requires a **DataForSEO account and valid credentials** in `.env`. Without this, the skill cannot function. - Subject to DataForSEO **availability, rate limits, and pricing**; heavy use may incur cost. 2. **Operational reliability considerations** - Network or authentication issues can cause failures; robustness (retries, graceful degradation) is not detailed in the description. - If API quotas are hit or credentials expire, agents will need to handle errors explicitly. 3. **Local file system assumptions** - Persists results under a fixed `results/` directory. In certain execution environments (read-only FS, ephemeral storage, or sandboxed runtimes), this may not behave as expected. 4. **Manual summary creation step** - The recommended workflow is: run research → then create a markdown summary manually using the stored JSON data. - For agents, this means additional logic is needed to read saved results and generate user-facing summaries. 5. **Privacy and data exposure** - All search terms, domains, and topics are sent to DataForSEO; sensitive or confidential topics may have privacy implications depending on the user’s policies. --- ### Recommended scenarios This skill is a good fit when: - An agent needs **data-driven SEO decisions**: selecting topics, prioritizing content, choosing YouTube video ideas, or optimizing landing pages based on volume, difficulty, and SERP landscape. - The environment can provide and securely store **DataForSEO credentials** and tolerate outbound HTTP calls and API cost. - You want **repeatable research runs** where results are logged as JSON and can be re-used or audited later. Use it specifically when users ask to: - "Research keywords" or "find keyword ideas" for SEO or YouTube. - "Check search volume/CPC/competition" or "check keyword difficulty". - "Analyze competitor [domain.com]" or "see what ranks for these keywords". - "Find trending topics" in a region. - "Optimize landing page keywords" or plan content around a set of keywords. It is less appropriate where no external API keys are allowed, strict data-privacy rules forbid third-party SEO APIs, or where a fully self-contained, offline SEO capability is required.