Use SEOmatic in Nanoclaw
Updated
Before you start
A running nanoclaw install with OneCLI, and a free SEOmatic account with an API key from Settings, AI Agents, API Keys.
Connect Nanoclaw#
- Create an API key. In SEOmatic (a free account works), open Settings, then AI Agents, then API Keys, and create a key.
- Store it in the vault. Run onecli secrets create with the name SEOmatic, type generic, your key as the value, the host pattern app.seomatic.ai, header name Authorization and value format Bearer {value}, so the vault sends it as a Bearer header.
- Grant it to the group. Find the group's OneCLI agent id with onecli agents list (its identifier matches the group id), then run onecli agents grants attach-secret with that id and the new secret id. On an older OneCLI without grants, onecli agents set-secrets still works but replaces the whole list, so include the secrets it already has.
- Add the server to the group. Run ncl groups config add-mcp-server --id
--name seomatic --url https://app.seomatic.ai/api/mcp, then ncl groups restart --id . - Ask in the group. Message the group: “@Andy how is our site doing on Google this month?” (use your agent's name). Connect Search Console in SEOmatic first for click and ranking data.
nanoclaw setup
# 1. Store your SEOmatic key in the OneCLI Agent Vault
onecli secrets create --name SEOmatic --type generic \
--value "smk_live_..." --host-pattern app.seomatic.ai \
--header-name Authorization --value-format "Bearer {value}"
# 2. Attach it to the group's OneCLI agent
onecli agents list # the agent whose identifier is your group id
onecli agents grants attach-secret --id <agent-id> --secret-id <seomatic-secret-id>
# older OneCLI without grants (set-secrets replaces the whole list):
# onecli agents set-secrets --id <agent-id> --secret-ids <existing-ids>,<seomatic-secret-id>
# 3. Add SEOmatic to the group and restart it
ncl groups config add-mcp-server --id <group-id> \
--name seomatic --url https://app.seomatic.ai/api/mcp
ncl groups restart --id <group-id>Note
Never put the key in --headers on the ncl command; nanoclaw writes headers into the group's config, and the vault exists to keep secrets out of it. If the agent says it has no SEOmatic tools or gets a 401, check the secret's host pattern is app.seomatic.ai, its header name is Authorization with value format Bearer {value}, it is attached to this group's agent, and the group was restarted.
MCP Server per Group, or the Skill in the Container?
| Route | Best for | How |
|---|---|---|
| MCP server for a group | Most setups: one agent group handles your site and gets SEOmatic's tools | Store the key with onecli secrets create, attach it to the group's OneCLI agent with onecli agents grants attach-secret, then ncl groups config add-mcp-server --id and ncl groups restart --id . |
| SEOmatic skill and CLI | Groups that should run SEO checks as shell commands inside their container | Add the skill to your nanoclaw fork with npx skills add Minh42/seomatic-mcp. The skill runs npx -y seomatic, which reads SEOMATIC_API_KEY from the container. |
Pick the MCP server for a group. The vault injects your key in flight, so the container never sees it, and only the groups you choose get SEO tools.
Try Asking#
- “How did our site do on Google last week compared with the week before?”
- “Check every page in our sitemap and tell me which ones Google has not indexed.”
- “We relaunch the site on Friday. Audit it and list anything that could hurt rankings.”
- “Which searches bring us impressions but almost no clicks?”
- “Every Monday at 9, post a short Search Console recap in this group.”
- “Stage fixes for the two worst problems you found and post the approval link.”
What It Costs#
Connecting is free. Reading your own data never uses credits: Search Console performance and insights, index status, rankings, site audits, AI citations, traffic and your tasks. Only live market lookups (keyword metrics, search results, backlinks), AI visibility scans and the fixes you approve use AI credits; every tool is labelled free or billed. On the Free plan, market lookups count against 5 free questions a month. The workspace Owner sees every credit spent, by feature, in Settings > Usage. nanoclaw itself is billed by its maker, not by SEOmatic: nothing on our side counts tokens.
Nothing Changes on Your Site Without Your Approval#
In a group chat, anyone can type a request, so nanoclaw's agent is never the one who approves. A staged change is a proposal: it says what will change and why, and nothing touches your site until you approve it. The assistant records your decision, and it is told never to approve anything on its own judgment. Approved fixes start within seconds, the page's previous state is stored, and any applied change can be rolled back. Changes that could take a page out of Google, like a noindex, need an extra explicit confirmation. The agent can stage a fix when asked; the change waits until a signed-in SEOmatic user approves it. Revoke the key in SEOmatic or remove the vault secret to cut access at once.
- nanoclaw says SEOmatic is connected but answers without my data.
- Start a new chat and check that SEOmatic is enabled for that conversation in the tools menu. This is the step most people miss.
- The SEOmatic page says "This connection request expired".
- Start the connection again from nanoclaw, or paste the setup prompt again.
- The Authorize page shows the wrong email or no workspace.
- Click Switch account on that page and sign in with the SEOmatic account that owns the site.
- Why does nanoclaw say it cannot change my site?
- Fixes need a live paid plan or trial. On the Free plan, or when billing is paused or failed, your assistant can read and answer only.
- How do I disconnect?
- Open Settings > AI Agents, scroll to API Keys and delete the row named OAuth: nanoclaw. See disconnect an assistant.
Was This Article Helpful?
Still need help?Email contact@seomatic.ai with your site address and a screenshot. A person replies, usually within one business day.