ChatSEO alternative: Serpkin vs ChatSEO for coded sites

ChatSEO and Serpkin both use your Search Console data to tell you what to fix next, but they put the work in different places. ChatSEO is a chat web app that writes content and publishes it to WordPress, Shopify or Webflow. Serpkin hands one mission to the coding agent that edits your repository (Claude Code, Codex or Cursor), checks the preview before you merge and measures the result. If your site lives in a CMS and you don't write code, ChatSEO is the closer fit. If your site lives in a Git repository and an agent ships your changes, look at Serpkin or another developer tool.

We make Serpkin, so weigh that. Everything about ChatSEO below comes from its own pages (home, pricing, features, MCP, about, security and llms.txt), checked on November 4, 2026 and listed under sources. We don't rate the quality of its advice or content, because we can't source that.

#What ChatSEO is

ChatSEO describes itself as "an AI SEO employee available 24/7. It audits your site, finds quick wins, writes and publishes content for you." Its about page names the audience: "founders, marketers and agencies who want Google traffic without becoming SEO experts." It was founded in 2025 by three co-founders, and the dashboard is in English and French (you can chat in any language).

What it works with, according to its own pages:

• Your data. Google Search Console with the read-only webmasters.readonly scope. Its security page says Search Console data is fetched live and never stored. Google Analytics is included from the Pro plan. Keyword volumes, SERPs and backlinks come from a third-party data provider.
• The model. Anthropic Claude (its security page lists Sonnet 4 and Haiku) for analysis and conversation.
• Agents. 12 specialized agents: strategy, keyword research, performance, competitors, on-page, internal linking, backlinks, indexation, structured data, local SEO, GEO and NinjaLinking.
• Actions. It writes briefs, articles and meta tags, and publishes to WordPress, Shopify or Webflow once a CMS is connected. Its FAQ says it changes your site "only if you ask it to." Every plan also lists Google Business Profile management and weekly SEO reports.

Its pages don't mention GitHub, repositories, code edits, pull requests or preview deployments. ChatSEO says it is "used by 20,000+ website owners"; we can't verify that number.

#The core difference: where the change lands

Most of the gap between the two tools follows from one question: what happens after the tool decides a page needs a new title or a new section?

With ChatSEO, the answer is a chat reply or an artifact (an article, a brief, a rewritten meta tag). If your CMS is connected and you ask, it publishes there. That is a short path for a WordPress blog or a Shopify store, where content is data in the CMS and nobody opens a code editor.

On a coded site (Next.js, Astro, SvelteKit, a React app), titles, canonicals, structured data and page copy live in source files. A change there means an edit, a commit, a preview deploy and a merge. A tool that publishes to a CMS can't take that path. You or your coding agent have to turn its advice into a diff.

Serpkin is built for that second case. Each mission names the pages to change, the source files where your routes are mapped, ordered steps for the agent and the acceptance checks that prove it shipped. Then npx serpkin check <preview-url> compares the preview with production and fails on regressions (a lost title, a new noindex, a broken canonical) before you merge.

#ChatSEO vs Serpkin side by side

#Pricing compared

ChatSEO prices in euros excluding VAT (its pricing page says the same amounts apply in USD), and each plan has six credit tiers. Annual billing takes 20% off.

A credit is one message, "however complex": an audit that runs five tools costs the same as a quick question, and failed or empty replies aren't counted. Unused credits on monthly plans roll over, up to one month's worth. The trial gives 7 days and 30 credits on the plan you pick, with a card on file and a reminder 3 days before the first charge. ChatSEO refunds in full within 7 days of the first charge, and you can pause a subscription for 1 to 3 months. Onboarding and your first message are free, but there are no free credits after that.

Serpkin has two plans. Builder is $29 a month or $290 a year (3 sites, 150 pages per scan, 30 missions a month). Pro is $79 a month or $790 a year (15 sites, 500 pages per scan, 150 missions a month). Both start with a 7-day free trial, card required, with research capped at 150 credits during the trial. Research credits pay for keyword research and similar calls. Getting the next mission over MCP is free and doesn't use credits.

#Using ChatSEO and Serpkin from Claude Code

Both tools have a remote MCP server, so both work inside Claude Code. What the agent gets back is different.

ChatSEO MCP

ChatSEO's server is at https://api.chatseo.app/mcp (Streamable HTTP, OAuth 2.1) and needs the Pro plan or higher. Its MCP page lists 18 tools. Most manage the account, sites, actions, conversations, projects and artifacts. send_message is described as "the main entry point": it hands an SEO question or task to the ChatSEO agent, and get_conversation_messages reads the reply. Two tools connect WordPress and publish an artifact to it.

claude mcp add --transport http chatseo https://api.chatseo.app/mcp
# then run /mcp in Claude Code and sign in with OAuth

So from Claude Code you are mostly chatting with ChatSEO's agent through your own agent. ChatSEO's pages don't say whether a send_message call over MCP uses a credit the way a chat message does; check your credit balance (get_credits) after a few calls if that matters to you.

Serpkin MCP

Serpkin's server is available on every plan and the trial. serpkin_next_mission returns one ranked fix with an implementation block: ordered steps, each with a file from your route map and an action, code snippets where Serpkin can generate them (a metadata export, app/sitemap.ts, a JSON-LD component), verify commands and a done_when list that mirrors the acceptance checks. The agent edits the files itself. Setup is one command in the repository:

npx serpkin          # connects Claude Code, Codex or Cursor and registers the site
npx serpkin check https://my-branch.vercel.app   # compare a preview with production
npx serpkin weekly   # add the Monday mission PR and the preview check to .github/workflows/

#If you keep ChatSEO for a coded site

You can still use ChatSEO's recommendations on a Next.js or Astro site. The publishing step is yours. This is the workflow we'd use with any chat-based SEO tool:

1. Ask for page-level output

   Ask for the exact URL, the new title, the new meta description and any copy change, one page per answer. Vague advice ("improve your titles") is hard to turn into a diff.

2. Paste it into your coding agent as a task

   Give Claude Code, Codex or Cursor the URL and the target values, and ask it to find the route file. In the Next.js App Router, page metadata lives in the route's page.tsx or layout.tsx:

   import type { Metadata } from "next";
   
   export const metadata: Metadata = {
     title: "Pricing: plans for small teams",
     description: "Compare plans, limits and what each one includes. Start with a 7-day trial.",
     alternates: { canonical: "/pricing" },
   };

3. Check the preview, not just the diff

   Open the preview URL and view the server HTML (curl -sL <url> | grep -i "<title"), or run the free SEO checker on it. Template changes can break other pages, so check a few routes that share the layout.

4. Note the date you shipped

   Write down the deploy date and compare the page in Search Console 28 days before and after. Without that, you won't know whether the change helped.

#How to choose

#Using both

Plenty of teams have two kinds of site: a product or marketing site in a repository, and a blog or store in a CMS. The tools don't overlap much in that setup. ChatSEO can write and publish the WordPress or Shopify content, and Serpkin can handle the coded site: technical fixes, metadata, structured data, internal links and new pages your agent builds.

Two things to keep tidy if you run both. First, register each site in only the tool that changes it, so two tools aren't rewriting the same titles. Second, if both connect to the same Search Console property, that is fine (both use read-only access), but measure each change in one place so you don't double-count a win.

#Where Serpkin fits

Serpkin is the ChatSEO alternative for people who ship code. It reads your site and your Search Console data, picks one fix worth doing, hands it to your coding agent with the files to change, checks the preview and measures the result after 14 and 28 days. It doesn't publish to a CMS, merge, deploy or promise rankings. Builder is $29 a month (3 sites) and Pro $79 (15 sites), each with a 7-day free trial. See getting started, compare other agent tools in SEO MCP servers compared, or start a 7-day free trial.