OpenClaw + Sightkick: SEO and GEO from your chat apps

Updated November 7, 2026

OpenClaw, the open-source assistant that runs on your own computer, connects to Sightkick's MCP server with openclaw mcp add and an OAuth sign-in, no API key. From WhatsApp, Telegram, Slack or iMessage, OpenClaw can then tell you how AI answers and Google treat your site, and do the work in Sightkick.

Sightkick makes this page. The setup below was run on 5 November 2026 against sightkick.so's own workspace.

Key takeaways

• Four lines. Stop the Gateway, add the server, sign in, start the Gateway again.
• Tested. On 5 November 2026, OpenClaw 2026.11.1 signed in and openclaw mcp probe listed Sightkick's 37 tools.
• From your phone. Once signed in, any chat app connected to OpenClaw can reach Sightkick.
• Your gates. Sightkick asks for no confirm. Limit OpenClaw to the get_ tools if you want it read-only.

How do you connect OpenClaw to Sightkick?

Run four lines in a terminal on the machine where OpenClaw runs. OpenClaw adds a server and signs in only while its Gateway is stopped, so the first line stops it and the last starts it again. The same lines are in Sightkick's OpenClaw setup.

openclaw gateway stop --force
openclaw mcp add sightkick --url https://app.sightkick.so/mcp --transport streamable-http --auth oauth
openclaw mcp login sightkick
openclaw gateway start

The stop needs --force from a shell nobody types in, such as an agent's. If you ask OpenClaw itself to connect, it can't stop the Gateway it runs inside: run the lines in a terminal yourself, or add the server in OpenClaw's Control UI, where an admin adds it under Settings → MCP (Add server) and signs in with Sign in, with the Gateway running.

Open the link the login line prints. Sign in to Sightkick and pick the workspace for your site. If the browser can't get back to OpenClaw, rerun the login line with --code and the code from the address:

openclaw mcp login sightkick --code <code>

Then check that OpenClaw sees Sightkick's tools, before the Gateway starts again:

openclaw mcp probe sightkick

This is the run on 5 November 2026, OpenClaw 2026.11.1, against sightkick.so's workspace (the sign-in link shortened):

$ openclaw mcp add sightkick --url https://app.sightkick.so/mcp --transport streamable-http --auth oauth
Saved MCP server "sightkick" to ~/.openclaw/openclaw.json.
Run openclaw mcp login sightkick to authorize this MCP server.

$ openclaw mcp login sightkick
Open this URL to authorize "sightkick":
https://clerk.sightkick.so/oauth/authorize?…
Waiting for the browser to return to OpenClaw...
MCP OAuth credentials saved for "sightkick".

$ openclaw mcp probe sightkick
MCP check (~/.openclaw/openclaw.json):
- sightkick: 37 tools

Last, ask OpenClaw to call get_workspace. It returns the workspace, the plan's amounts and what's left this month, Sightkick's jobs, what setup still lacks and what's new. The "Connect your agent" popup in Sightkick ticks off when that first call arrives.

Starting without an account

OpenClaw can do the account setup for you. Send it:

Read https://sightkick.so/llms.txt and set up Sightkick for example.com.

OpenClaw sends your website, brand, rivals and the questions your buyers ask AI as a draft. Nothing is charged and nothing runs. You sign up from the link it gives you, with Google or an email code, and start the 7-day trial. OpenClaw waits in the background, collects a key once the trial starts, and is connected. For a first look with no card, there's the free AI visibility report.

What is OpenClaw?

OpenClaw is an open-source AI assistant that runs on your own computer. Peter Steinberger created it, and the OpenClaw Foundation, an independent US 501(c)(3), now employs the core team and signs every release. It is MIT-licensed. Its GitHub repository dates from November 24, 2025. The project's lore traces it from a WhatsApp gateway called Warelay through Clawdbot and Moltbot (January 27, 2026) to the name OpenClaw on January 30, 2026.

You talk to OpenClaw through chat apps: WhatsApp, Telegram, Discord, Slack, Signal, iMessage and more, 29 channels in all per openclaw.ai. It has desktop apps for macOS, Windows and Linux, and apps for iOS and Android. A local Gateway is the control plane for sessions, tools and channels. There's no subscription and no hosted tier: state lives on your machine.

OpenClaw starts from a message: you text it where you already chat. Hermes Agent, the other open-source agent people run themselves, is built to run anywhere, a VPS or a serverless host included. OpenClaw is built around the computer you already use.

What can OpenClaw do with Sightkick?

OpenClaw can answer questions about your AI visibility, rivals, next pages and Google results from any chat app, and act on them in Sightkick. These are questions you can send from your phone, each with what came back on sightkick.so, Sightkick's own site. That site tracks 100 prompts in all four AI models, beyond what a plan includes, through add-ons.

1. "Are AI answers naming us more?"

Check Sightkick: in the last 14 days, how often did each AI model mention us, against the 14 days before? How many answers recommended us or cited our pages, and what was the tone?

On sightkick.so, mentions rose in every AI model: ChatGPT 14 (from 2), Google AI Mode 7 (from 6), Gemini 1 (from 0), Google AI Overviews 1 (from 0). Sightkick was recommended 13 times and cited 24 times. Sentiment: 13 positive, 7 neutral, 3 mixed, none negative.

2. "Who gets named instead of us?"

From Sightkick, which competitors do AI answers name most for our prompts? Give me the top five with counts, and the prompts where they win and we don't.

On sightkick.so the rivals named most were Profound (2,043 answers), Peec AI (1,988), Otterly (1,875), Scrunch AI (766) and Rankscale AI (517), then Promptwatch (243), Semrush (152) and SE Ranking (54), per Sightkick's get_visibility competitors view for sightkick.so, 14 days to 2026-11-04. The prompts they win and you don't are get_visibility's gaps view. Sightkick also runs that gap analysis every week.

3. "What kind of page should we write next?"

Look at the pages AI answers cite for our prompts in Sightkick. Which page types get cited most? Suggest the type and topic of our next page, and create it in Sightkick as an unscheduled page.

On sightkick.so, cited pages split into product pages (3,076 citations), list articles (1,292), guides (412), discussions (165) and videos (72). Sightkick publishes blog posts and comparison, alternatives, integration and use-case pages, so the next page can match what AI already cites.

4. "What does Google show for this keyword?"

Before we write about "claude seo", pull Google's results page for it through Sightkick and tell me who ranks and what the AI Overview says.

For "claude seo" (Google US, 2026-11-04), Sightkick's check_web serp returned infranodus.com/skills/seo, the AgriciDaniel/claude-seo GitHub repo, claude-seo.md and SE Ranking's "Claude SEO Skills" page. The AI Overview described claude-seo, an open-source skill for Claude Code. A page on that keyword has to beat a repo and a skill page, not only blogs.

5. "Where do we rank for our own name?"

In Sightkick's Search Console data for the last 28 days, how did the search for our brand name do? Impressions, clicks and position.

On sightkick.so, the query "sightkick" had 173 impressions, 1 click and an average position of 17.9 in the 28 days to 2026-11-03. An average position of 17.9 is page two of Google for the brand's own name.

What if OpenClaw can't reach Sightkick?

Most problems are a running Gateway, a browser that can't get back to OpenClaw, or a missing sign-in. Each fix is below.

The OpenClaw CLI refuses while the Gateway runs

OpenClaw's commands that write config or sign-in state (add, login, probe and others) need the local Gateway stopped, and the CLI says so. Run openclaw gateway stop --force, then the commands, then openclaw gateway start. Without --force, the stop exits with an error in a shell nobody types in.

The browser can't get back to OpenClaw

That happens when OpenClaw runs on another machine than your browser. Copy the code from the address the browser landed on and run openclaw mcp login sightkick --code with it.

Every tool says the connection isn't tied to a Sightkick workspace

The sign-in finished before the new account's workspace existed. Finish the setup at app.sightkick.so/start (sign in, confirm the site, start the trial or plan), then run openclaw mcp login sightkick again. Or remove the server with openclaw mcp unset sightkick and add it back.

OpenClaw answers without Sightkick's tools

When the saved sign-in is missing, OpenClaw drops that one server from the turn instead of failing it. Run openclaw mcp status: authorization-required means log in again. If the tokens look stuck, run openclaw mcp logout sightkick, then the login. Also check a tool filter (openclaw mcp tools) or a minimal tool profile, which hides MCP tools.

Nobody can open a browser

On a headless box, ask for an API key: in Sightkick, Settings → Agents, then New key. Keep it in SIGHTKICK_API_KEY, never in code or a commit. The CLI runs the same tools on it:

npx -y sightkick status

To keep MCP, send the key as an Authorization: Bearer header instead. OpenClaw ignores static Authorization headers while auth is oauth, so add the server without --auth oauth. Use an environment reference for the key: openclaw mcp doctor warns about literal secrets.

Is it safe to give OpenClaw access?

Yes, if you set the limits you want, because OpenClaw acts as a user of the workspace, the same as you. It can read, write, spend the plan's allowances and publish whenever it likes, and Sightkick asks for no confirm. Sightkick's Auto, Manual and Off settings only cover what Sightkick does by itself.

• Bound to one site. The grant covers the workspace you picked at sign-in, and nothing else.
• Logged under its name. Every call shows in Sightkick's activity feed, attributed to OpenClaw's connection.
• Kept for you. Signing in, the first card, ending a trial early (Start my plan now), who gets access, and signing in to Google or a mailbox.
• Marked when it can't be taken back. Deleting, taking a page down and sending an email are destructive actions. Edits to live pages are kept and can be undone.
• Read as data. OpenClaw reads your messages from many channels. Sightkick marks text from other sites, AI answers and emails as untrusted, never as instructions.

To keep a person in the loop, set Sightkick's jobs to Manual and ask OpenClaw for drafts only: a page with no day waits in Unscheduled. On OpenClaw's side, limit the server to Sightkick's reads, which all start with get_ (stop the Gateway first):

openclaw mcp tools sightkick --include 'get_*'

How does OpenClaw compare with other agents on Sightkick?

OpenClaw and Hermes Agent are the open-source agents you run yourself. Codex and Claude Code are coding agents in a terminal. All four can run without a person at the keyboard.

Sources: OpenClaw MCP docs, Hermes Agent MCP docs, Sightkick's connect guide, read 7 November 2026.

FAQ

What does it cost to use OpenClaw with Sightkick?

OpenClaw is free and MIT-licensed, with no subscription. Sightkick's MCP server comes with every plan: Standard at $39 a month ($31 billed yearly), where your agent writes the pages, or Pro at $99 a month ($79 billed yearly), with 30 articles a month by Sightkick. Each starts with a 7-day trial that takes a card and charges nothing for 7 days.

Do I need an API key?

Not for MCP. OpenClaw signs in with OAuth 2.1 and stores the session itself. A key from Settings → Agents is the fallback where no browser can reach the sign-in.

Can I ask OpenClaw about Sightkick from my phone?

Yes. Once openclaw mcp login has run, the saved sign-in serves OpenClaw's agent turns, so you can ask from any channel you've connected to OpenClaw, or its iOS and Android apps.

Does OpenClaw publish without asking?

It can, because Sightkick never asks for a confirm. A written page on the schedule goes live on its day. Keep pages in Unscheduled, or allow only get_ tools, if you want to approve each one.

Can OpenClaw run Sightkick checks on a schedule?

Yes. OpenClaw has a built-in scheduler, Automations (openclaw cron is an alias), and a job can announce its result to a channel. Sightkick's own jobs run without any agent, too.

Do I need to install an SEO skill in OpenClaw?

No extra install is needed for Sightkick's method. Its playbook reaches OpenClaw in the MCP server's instructions on connect, and get_guidance returns it by topic.

Is Sightkick an agent?

No. Sightkick is the platform OpenClaw works in. OpenClaw is the agent, and Sightkick can also do each job by itself.

Next

• The Sightkick MCP server, with every client's setup
• Claude Code + Sightkick
• Pricing and the 7-day trial
• Free AI visibility report, no card
• Hermes Agent + Sightkick
• Codex + Sightkick
• Google Search Console + Sightkick