Skip to main content
Agent skill

SEMrush Automation

Automate SEO analysis with SEMrush -- research keywords, analyze domain organic rankings, audit backlinks, assess keyword difficulty, and discover related terms through the Composio SEMrush integration.

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use SEMrush Automation when an AI agent needs a reusable SKILL.md workflow for this job: Automate SEO analysis with SEMrush -- research keywords, analyze domain organic rankings, audit backlinks, assess keyword difficulty, and discover related terms through the Composio SEMrush integration.

When not to use it

Skip SEMrush Automation when the task is outside the analysis category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/semrush-automation
# Save SKILL.md to ~/.claude/skills/semrush-automation/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/semrush-automation/SKILL.md. For a shared project, commit the folder at .claude/skills/semrush-automation/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the SEMrush Automation skill for this task: Use SEMrush Automation when this documented workflow matches the task. Confirm any required inputs or files before making changes.

What supports this recommendation?

63/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
67/100
Practical detail
50/100
Source evidence
63/100
Source signals
80/100
Model compatibility evidence
  • claudeinferred

    The skill text mentions Claude or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# SEMrush Automation

Run **SEMrush** SEO analytics directly from Claude Code. Analyze domain keywords, audit backlink profiles, research keyword difficulty, discover related terms, and track organic page performance without leaving your terminal.

**Toolkit docs:** [composio.dev/toolkits/semrush](https://composio.dev/toolkits/semrush)

---

## Setup

1. Add the Composio MCP server to your configuration: ``` https://rube.app/mcp ``` 2. Connect your SEMrush account when prompted. The agent will provide an authentication link. 3. All SEMrush tools require a `database` parameter specifying the regional database (e.g., `us`, `uk`, `de`). Choose the correct region for your target audience.

---

## Core Workflows

### 1. Domain Organic Keywords Analysis

Retrieve all organic search keywords for a domain, including positions, traffic estimates, CPC, and keyword difficulty.

**Tool:** `SEMRUSH_DOMAIN_ORGANIC_SEARCH_KEYWORDS`

Key parameters: - `domain` (required) -- e.g., `example.com` - `database` (required) -- regional database code (e.g., `us`, `uk`, `de`) - `display_limit` (default 10000) and `display_offset` (default 0) -- pagination - `display_sort` -- sort by position, traffic, volume, etc. (e.g., `tr_desc` for traffic descending) - `display_date` -- historical data in `YYYYMM15` format (monthly) or `YYYYMMDD` (daily) - `export_columns` -- specify columns like `Ph` (phrase), `Po` (position), `Nq` (volume), `Tr` (traffic), `Kd` (difficulty) - `display_filter` -- filter by specific columns

Example prompt: *"Get the top 100 organic keywords for example.com in the US database, sorted by traffic"*

---

### 2. Keyword Overview and Batch Analysis

Get detailed metrics for individual keywords or analyze up to 100 keywords at once.

**Tools:** `SEMRUSH_KEYWORD_OVERVIEW_ONE_DATABASE`, `SEMRUSH_BATCH_KEYWORD_OVERVIEW`

For single keyword: - `phrase` (required) -- keyword to investigate - `database` (required) -- regional database

For batch (up to 100 keywords): - `phrase` (required) -- semicolon-separated keywords (max 255 chars total) - `database` (required) -- regional database - `export_columns` -- `Ph` (phrase), `Nq` (volume), `Cp` (CPC), `Co` (competition), `Kd` (difficulty), `In` (intent)

Example prompt: *"Get keyword metrics for 'seo services;content marketing;link building' in the US database"*

---

### 3. Domain Organic Pages Report

Discover which URLs on a domain drive the most organic traffic and visibility.

**Tool:** `SEMRUSH_DOMAIN_ORGANIC_PAGES`

Key parameters: - `domain` (required) -- target domain - `database` (required) -- regional database - `display_sort` -- e.g., `pc_desc` for traffic share descending - `display_limit` and `display_offset` -- pagination - `export_columns` -- `Ur` (URL), `Pc` (traffic %), `Tg` (traffic), `Tr` (traffic cost)

Example prompt: *"Show the top 50 organic pages for example.com ranked by traffic share"*

---

### 4. Backlink Profile Overview

Get a summary of backlinks for a domain including Authority Score, link types, and referring domain counts.

**Tool:** `SEMRUSH_BACKLINKS_OVERVIEW`

Key parameters: - `target` (required) -- domain, subdomain, or full URL - `target_type` (required) -- `root_domain`, `domain`, or `url` - `export_columns` -- `ascore` (Authority Score), `total` (total backlinks), `domains_num` (referring domains), `follows_num`, `nofollows_num`, etc.

Example prompt: *"Get the backlink overview for example.com including Authority Score and referring domain count"*

---

### 5. Keyword Difficulty Assessment

Score how hard it is to rank in the top 10 for specific keywords (0-100 scale).

**Tool:** `SEMRUSH_KEYWORD_DIFFICULTY`

Key parameters: - `phrase` (required) -- keyword to analyze - `database` (required) -- regional database - `export_columns` -- `Ph` (phrase), `Kd` (difficulty score)

Example prompt: *"What is the keyword difficulty for 'best project management software' in the US?"*

---

### 6. Discover Related Keywords

Find synonyms, variations, and related terms for a seed keyword to expand your content strategy.

**Tool:** `SEMRUSH_RELATED_KEYWORDS`

Key parameters: - `phrase` (required) -- seed keyword - `database` (required) -- regional database - `display_limit` (default 10000) -- max results - `display_sort` -- e.g., `nq_desc` for volume descending, `kd_asc` for easiest first - `export_columns` -- `Ph`, `Nq`, `Kd`, `Cp`, `Co`, `Rr` (relatedness score)

Example prompt: *"Find related keywords for 'project management' in the US, sorted by search volume"*

---

## Known Pitfalls

- **Pagination is essential:** `SEMRUSH_DOMAIN_ORGANIC_SEARCH_KEYWORDS` and `SEMRUSH_DOMAIN_ORGANIC_PAGES` can return very large datasets. Always use `display_limit` and `display_offset` instead of assuming a single page is complete. - **CSV-style responses:** Many SEMrush tools return data as CSV-style text in a single field (e.g., `data/keyword_data`). You must parse rows and columns before analysis or joining reports. - **"ERROR 50 :: NOTHING FOUND":** This literal string means the domain or keyword has no data in that database. Treat it as a valid zero-result response, not a transport error. - **Batch keyword limits:** `SEMRUSH_BATCH_KEYWORD_OVERVIEW` may return HTTP 400 for problematic or oversized batches (max 255 chars total for the `phrase` field). Shrink batches or fall back to `SEMRUSH_KEYWORD_OVERVIEW_ONE_DATABASE` for individual lookups. - **Date format:** Historical dates must use `YYYYMM15` format for monthly data (e.g., `20231015`). Using an incorrect format will return unexpected results. - **Regional database matters:** Always use the correct regional database for your target audience. Results for `us` vs `uk` can differ dramatically in volume, CPC, and rankings. - **Column codes:** Export columns use short codes (`Ph`, `Nq`, `Kd`, etc.). Avoid over-narrowing `export_columns` so key metrics like traffic, CPC, position, and difficulty are retained.

---

## Quick Reference

| Tool Slug | Description | |---|---| | `SEMRUSH_DOMAIN_ORGANIC_SEARCH_KEYWORDS` | Organic keywords for a domain with positions and traffic | | `SEMRUSH_KEYWORD_OVERVIEW_ONE_DATABASE` | Single keyword metrics (volume, CPC, difficulty) | | `SEMRUSH_BATCH_KEYWORD_OVERVIEW` | Batch metrics for up to 100 keywords | | `SEMRUSH_DOMAIN_ORGANIC_PAGES` | Top organic pages for a domain by traffic | | `SEMRUSH_BACKLINKS_OVERVIEW` | Backlink profile summary with Authority Score | | `SEMRUSH_BACKLINKS` | Detailed backlinks list for a target | | `SEMRUSH_KEYWORD_DIFFICULTY` | Keyword difficulty score (0-100) | | `SEMRUSH_RELATED_KEYWORDS` | Related/similar keywords for a seed phrase | | `SEMRUSH_CATEGORIES` | Domain categories with confidence ratings | | `SEMRUSH_DOMAIN_ORGANIC_SUBDOMAINS` | Subdomain-level organic rankings breakdown |

---

*Powered by [Composio](https://composio.dev)*

Intended uses

  • Use SEMrush Automation when this documented workflow matches the task.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.