# How to connect Semrush to OpenClaw (paste one key, 37 tools) > Connect Semrush to OpenClaw with ClawLink: paste your Semrush key once and 37 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/semrush The usual route to Semrush access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Semrush setup: install one ClawHub skill, connect Semrush in the browser, and OpenClaw can call real Semrush actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/semrush ## Setup It takes three steps to connect OpenClaw to Semrush. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Semrush** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect semrush # connect Semrush (browser OAuth) npx -y @useclawlink/cli actions semrush # list available actions npx -y @useclawlink/cli run semrush --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Semrush in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Semrush API key once. Verify the connection by asking OpenClaw: > Use Semrush to account units balance and walk me through the result in plain English. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Semrush is connected in the dashboard, that agent calls the same 37 Semrush tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Semrush MCP for OpenClaw Looking for a Semrush MCP server for OpenClaw? ClawLink connects Semrush to OpenClaw and exposes 37 Semrush tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Semrush integration](https://claw-link.dev/hermes/semrush) works the same way. ## What the OpenClaw Semrush integration can do 37 Semrush tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 37. ### 30 of 37 Semrush tools for OpenClaw | Tool | What it does | |---|---| | **Account units balance** `semrush_account_units_balance` | Check Semrush account units balance | | **Authority score profile** `semrush_authority_score_profile` | Get authority score for a domain | | **Backlinks** `semrush_backlinks` | List backlinks for a domain | | **Backlinks overview** `semrush_backlinks_overview` | Get backlink overview for a domain | | **Batch keyword overview** `semrush_batch_keyword_overview` | Get keyword overview for multiple keywords | | **Broad match keyword** `semrush_broad_match_keyword` | Find broad match keywords | | **Competitors in organic search** `semrush_competitors_in_organic_search` | Find organic search competitors | | **Domain organic pages** `semrush_domain_organic_pages` | List organic pages for a domain | | **Domain organic search keywords** `semrush_domain_organic_search_keywords` | List organic search keywords for a domain | | **Domain vs domain** `semrush_domain_vs_domain` | Compare two domains in Semrush | | **Historical data** `semrush_historical_data` | Get historical keyword data from Semrush | | **Keyword difficulty** `semrush_keyword_difficulty` | Check keyword difficulty in Semrush | | **Keyword overview one database** `semrush_keyword_overview_one_database` | Get keyword overview for a specific database | | **Organic results** `semrush_organic_results` | Get organic search results for a keyword | | **Phrase questions** `semrush_phrase_questions` | Find questions related to a keyword | | **Ads copies** `semrush_ads_copies` | Retrieves unique ad copies Semrush has observed for a specified domain from a regional | | **Anchors** `semrush_anchors` | Use this action to get a CSV report of anchor texts for backlinks pointing to a specified | | **Batch comparison** `semrush_batch_comparison` | Compares backlink profiles for multiple specified targets (domains, subdomains, or URLs) to | | **Categories** `semrush_categories` | Retrieves categories and their 0-1 confidence ratings for a specified domain, subdomain, or | | **Categories profile** `semrush_categories_profile` | Retrieves a profile of content categories from referring domains for a specified target | | **Competitors** `semrush_competitors` | Retrieves a CSV-formatted report of competitors for a specified target (root domain, domain, or | | **Competitors in paid search** `semrush_competitors_in_paid_search` | Retrieves a list of a domain's competitors in paid search results from a specified regional | | **Domain ad history** `semrush_domain_ad_history` | Retrieves a domain's 12-month advertising history from Semrush (keywords bid on, ad positions | | **Domain organic subdomains** `semrush_domain_organic_subdomains` | Retrieves a report on subdomains of a given domain that rank in Google's top 100 organic search | | **Domain paid search keywords** `semrush_domain_paid_search_keywords` | Fetches keywords driving paid search traffic to a specified, existing domain using a supported | | **Domain pla search keywords** `semrush_domain_pla_search_keywords` | Retrieves Product Listing Ad (PLA) search keywords for a specified domain from a Semrush | | **Indexed pages** `semrush_indexed_pages` | Retrieves a list of indexed pages from Semrush for a specified `target` (root domain, domain | | **Keyword overview all databases** `semrush_keyword_overview_all_databases` | Fetches a keyword overview from Semrush for a specified phrase, including metrics like search | | **Keywords ads history** `semrush_keywords_ads_history` | Fetches a historical report (last 12 months) of domains advertising on a specified keyword in | | **Paid results** `semrush_paid_results` | Fetches domains ranking in Google's paid search results (AdWords) for a specified keyword and | ## Example prompts **Account Units Balance** > Use Semrush to account units balance and walk me through the result in plain English. **Authority Score Profile** > Use Semrush to authority score profile and walk me through the result in plain English. **Backlinks** > Use Semrush to backlinks and walk me through the result in plain English. **Backlinks Overview** > Use Semrush to backlinks overview and walk me through the result in plain English. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Semrush working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Semrush API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Semrush account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Semrush. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Semrush actions to the runtime in a format your agent can reliably use. | 37 tools for Semrush are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Semrush to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Semrush in the browser, and the 37 tools above work from chat. There is no SDK and no config file, and the Semrush key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Semrush skill but can't call the tools The ClawHub skill teaches OpenClaw about Semrush, but the calls run through the ClawLink plugin and your connected account. Make sure Semrush is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Semrush from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Semrush tools Semrush tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Semrush call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Semrush returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for Semrush has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Semrush integration? Yes. ClawLink is the fastest way to connect OpenClaw to Semrush: link your Semrush account once in the browser and OpenClaw can call the Semrush API through 37 ready-made tools — no custom code or token handling. ### How do I add Semrush to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Semrush skill from ClawHub, then you click Connect in the dashboard to authorize Semrush. OpenClaw calls the tools from the next message — no config files, and the Semrush key you paste is stored server-side instead of in your environment. ### How long does it take to connect Semrush to OpenClaw? About two minutes. Sign in, click Connect next to Semrush in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Semrush up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Semrush working from chat. ### OpenClaw installed the Semrush skill but can't call the tools The ClawHub skill teaches OpenClaw about Semrush, but the calls run through the ClawLink plugin and your connected account. Make sure Semrush is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [PostHog](https://claw-link.dev/openclaw/posthog) — Track user behavior and feature flags - [OpenClaw DataforSEO integration](https://claw-link.dev/openclaw/dataforseo) — SEO data APIs for keywords, SERP, and site audits - [Metabase](https://claw-link.dev/openclaw/metabase) — Metabase is an open-source business intelligence tool that lets you ask questions about your data and visualize answers as charts, graphs, and dashboards.