Open Source AI SEO Tools, Compared by What They Publish

Most listicles about open source AI SEO tools compare features nobody checks. This one compares the thing that decides whether the software is useful on a Tuesday afternoon: whether it can put a finished article on your site without you copying and pasting. Eight projects, every repository figure verified against the GitHub API on 2 October 2026, licences and maintenance status included. One of the eight is archived, three of them share the OpenSEO name and are unrelated, and four have code that puts an article into a named CMS, three of them into WordPress only.

Updated 2 October 2026. The first version of this post, checked on 3 September, compared five projects and said only AltoRank published to a named CMS. That was wrong: it left out SEOMachine, DispatchSEO and clawnify’s OpenSEO, all of which reach WordPress. They are in the table now, and every figure has been read again.

This guide is not for you if you want a hosted tool with a support contract, or if you are looking for an open-source replacement for Semrush’s data. The data underneath all of these comes from the same paid APIs; open source changes who holds the margin, not whether the data costs money.

How this was verified. Capability claims come from each project’s own repository README and product page, and for OpenSEO, AltoRank, SEOMachine and TuxSEO from their source code as well. Stars, forks, licence and last-commit dates come from the GitHub REST API, read on 2 October 2026, not from the projects’ marketing pages. The last-commit date is the newest commit on each default branch, which is not always the date GitHub shows as the last push. Figures are stamped with that date because star counts move.

Disclosure. I maintain AltoRank, one of the eight projects below. There are no affiliate links on this page. Where a competing project is better at something, the table says so, and the section headed “What AltoRank does not have” is there because a comparison written by a participant is worth nothing without it.

TL;DR

• Four of the eight have code that publishes into a named CMS, and three of those reach WordPress only. The others export files, post JSON to a webhook you have to build, or do not publish at all.
• Three of the eight are called OpenSEO, and they are unrelated. One is a research platform, two are content generators, and dozens more repositories on GitHub use the same name.
• Approval before publishing is not a differentiator. Most of the content projects here put a person before the publish, and the mainstream commercial tools do too.
• TuxSEO is archived. Its repository has had no commit since 26 May 2026.
• One project’s licence does not resolve. GitHub reports NOASSERTION for Juliusolsson05’s openSEO, so check the terms yourself before commercial use.
• Adoption is wildly lopsided: 22,120 stars for the leader, 7,469 for SEOMachine, under 100 for the other six, and one star for AltoRank.

The eight projects, verified

Project	Licence	Stars	Last commit	Research data	Generates articles	Publishes to a CMS
OpenSEO (every-app)	MIT	22,120	1 Oct 2026	Yes — keywords, ranks, backlinks, audits	No	No
SEOMachine (TheCraigHewitt)	MIT	7,469	5 Aug 2026	Yes — DataForSEO, Search Console, GA4	Yes — inside Claude Code	WordPress, as a draft post
openSEO (Juliusolsson05)	unresolved (see below)	4	8 Apr 2026	No	Yes — structured, block-based	Webhook only
OpenSEO (clawnify)	MIT	4	17 Sep 2026	Partial — live SERP via SerpAPI	Yes	WordPress, scheduled
DispatchSEO (NeoZi12)	AGPL-3.0	80	1 Oct 2026	Yes — Search Console, Autocomplete, optional DataForSEO	Yes — written by your coding agent	Self-hosted WordPress, or a git pull request
BlogPilot	MIT	25	15 Aug 2026	Partial — research modules	Yes	No — file export only
TuxSEO	MIT	59	26 May 2026 (archived)	Keywords, site and market analysis	Yes	Webhook only
AltoRank	AGPL-3.0	1	2 Oct 2026	Yes — via DataForSEO	Yes	Adapters for WordPress, Shopify and other CMSs, plus git and webhook; none yet verified end to end on a live site

Stars, forks, licence and commit dates read from the GitHub REST API on 2 October 2026.

Three projects called OpenSEO, none of them the same project

The shared name is an easy trap, and it will waste an afternoon if you install the wrong one. Three of the projects compared here use it and are unrelated, and they are not the only ones: a GitHub search for repositories with openseo in the name returned 68 on 2 October 2026, forks excluded.

OpenSEO by every-app, which runs the hosted product at openseo.so, is a research and analytics platform. It covers keyword research, rank tracking, backlink analysis, competitor insight and technical audits, plus AI-visibility lookups you run on demand (a brand check across ChatGPT and Google AI Overviews, and a prompt explorer); scheduled prompt tracking is on its roadmap, not in the product. It exposes an MCP server so agents like Claude Code can query the data directly. Self-hosting it requires your own DataForSEO key; the hosted plan, $10 a month including $10 of usage, runs on OpenSEO’s own DataForSEO account and, per its README, charges 28% on top of every request. It does not publish anything, and it does not write articles: asked “Does OpenSEO write content?”, its own FAQ answers “No.” That boundary has a date on it, because the public roadmap, checked on 2 October 2026, lists “Content writing workflows for Agents” under Soon. It is MIT licensed, and at 22,120 stars and 2,851 forks it is by a wide margin the most adopted project in this comparison, created in February 2026 and committed to on 1 October 2026.

openSEO by Juliusolsson05 is a content engine. It generates blog posts as structured elements rather than a markdown blob, across 28-plus element types including FAQs, comparison tables and checklists, and it offers a block-by-block editor. It sits at 4 stars and one fork, and its 27 open pull requests are all from Dependabot. The newest commit on its main branch is from 8 April 2026. Its README is unusually straight about scope: publishing to an outside CMS is by webhook only, alongside its own built-in public pages, and the agent and MCP integration is documented but not yet working code.

Its licence needs care. GitHub’s licence detection returns no recognised identifier for the repository — the API reports NOASSERTION — even though the project presents itself as GPL-3.0. That is not an accusation of anything; detection fails for ordinary reasons like a modified or non-standard licence file. It does mean that if you are putting this into a commercial workflow, read the licence terms in the repository directly rather than trusting a badge.

OpenSEO by clawnify is the third, also a content engine. It plans topic clusters, writes articles through OpenRouter, and publishes them to WordPress over the REST API, at once or at a scheduled time through Clawnify’s managed queue. Keyword research uses live Google results through SerpAPI, with labelled AI estimates when SerpAPI is not connected. It is MIT licensed, created in July 2026, at 4 stars with its latest commit on 17 September 2026.

If you are choosing between them you are not really choosing. One is a research tool, the other two are writing tools, and of those only clawnify’s puts the post on your site itself.

Which of them can actually publish

Publishing is where the category quietly splits, and it is the difference between software that saves you an hour and software that saves you a step.

Direct CMS publishing means the tool holds a credential for your site and creates the post itself. Four of the eight have code for it, and three of them reach WordPress only. SEOMachine creates a WordPress draft over the REST API with Yoast SEO fields filled in, so the final publish is still a click inside WordPress. clawnify’s OpenSEO publishes live to WordPress, now or at a scheduled time. DispatchSEO posts to a self-hosted WordPress with an application password or, for a site kept in a GitHub repository, opens a pull request; its README says Wix, Squarespace, Shopify, Webflow and Ghost will not work.

AltoRank’s code has publishing adapters for WordPress, Shopify, Webflow, Ghost, HubSpot, Magento, Notion, Wix, WooCommerce and Framer, plus git and webhook, which are publishing targets rather than content management systems. Said plainly: as of 2 October 2026 none of those connectors has been verified end to end against a live site, so the self-serve Connect buttons are withdrawn and a connection is set up on request. Adapters in the code are not the same as a connector you have watched publish.

Webhook publishing, which is Juliusolsson05’s openSEO, sends structured JSON to an endpoint. That is genuinely CMS-agnostic and it is also work: somebody has to write and host the receiver that turns that JSON into a post. Archived TuxSEO worked the same way, posting articles to an endpoint you configured.

Export publishing, which is BlogPilot, produces files — Markdown, HTML, JSON, WordPress WXR, Ghost JSON, Webflow CSV, Hugo TOML — that you then import. Broad format coverage, but the last step is still a human at a keyboard.

None of these three is wrong. They are different amounts of remaining work, and the listicles that put a green tick in a “publishing” column for all of them are hiding that difference.

Where each project is the better choice

Choose OpenSEO by every-app if what you actually need is data. It is the only project here whose whole product is research data, it is the most adopted by an enormous margin, and its MCP server makes it the natural data layer behind an agent workflow. If you already have a writing process, this is the piece you are missing. It is also the one project on this list I would recommend running alongside AltoRank rather than instead of it.

Choose SEOMachine if you already work in Claude Code and want a writing workspace rather than an app. It is the most adopted content project here, it pulls DataForSEO, Search Console and GA4 data into its research, and it sends finished articles to WordPress as drafts. It needs Claude Code and an Anthropic account, and its README’s licence section is still a placeholder, although GitHub detects an MIT licence file.

Choose DispatchSEO if your site lives in a git repository or a self-hosted WordPress and you want your own coding agent to do the writing. It queues ideas for you to approve and builds the oldest approved one each morning, posting it to WordPress or opening a pull request. Self-hosted, it runs in Docker, and its schedules only run while that machine is awake.

Choose BlogPilot if you want breadth in one self-hosted install and do not mind importing. Twelve-plus model providers including a free Gemini tier, deterministic non-AI generators for scoring, schema and internal linking, and export formats covering most static site generators.

Choose Juliusolsson05’s openSEO if structured, block-level control over the draft matters more than delivery, and you are comfortable building a webhook receiver. Two caveats: the newest commit on its main branch is from 8 April 2026, and the licence does not resolve.

Choose clawnify’s OpenSEO if you want a small WordPress autopilot to read and fork. At 4 stars, and built around Clawnify’s own deploy platform and queue, treat it as a starting point rather than a dependency.

Do not choose TuxSEO for new work. MIT, Python and Django, 59 stars, and a repository that is archived with no commit since 26 May 2026; its own archive note says AI agents now do this work better directly. It is worth reading if you want the approach; it is not worth depending on.

Approval before publishing is not a differentiator

AltoRank’s positioning leans on an approval gate, so it is worth stating plainly that this is not a unique property, and anyone claiming otherwise in this category is drawing the comparison set to flatter themselves.

Juliusolsson05’s openSEO says it directly in its README: not fully autonomous, humans review and publish. Its block editor exists for exactly that. SEOMachine stops at a WordPress draft, and DispatchSEO asks you to approve each idea before it builds one, with an auto mode for anyone who wants to skip the queue. Outside open source, the mainstream commercial tools — Jasper, Frase, Writesonic — all hand you a draft and expect you to publish it. Draft-then-review is the category default. The tools that publish unreviewed by default are a specific subcategory, and comparing only against those makes an ordinary property look like an achievement.

What is unusual about AltoRank’s version is narrower and more boring. The gate is enforced in one place in the publish path, and every live article records the person who approved it, either by clicking or by switching on an auto-approve rule that publishes after a hold window. The MCP server has no tool that approves an article or publishes it for the first time, only one that retries a publish that was already approved, so an agent cannot route around the gate. That is a design choice you can verify by reading the source, which is the only reason it is worth mentioning at all.

What AltoRank does not have

A comparison written by a participant needs this section to be worth reading.

It has one GitHub star, against 22,120 for OpenSEO and 7,469 for SEOMachine. It has no paying customers and no case studies, and nothing on the site carries a growth figure. None of its CMS connectors has been verified end to end on a live site yet, which is why connecting one is by request. Its command-line tool is not on npm yet; it runs from a checkout, next to the MCP server. It does no rank tracking or backlink analysis of the depth OpenSEO offers, and it depends on DataForSEO for the keyword data it does have, so the research layer skips rather than fails when that key is absent. It is AGPL-3.0, which is more restrictive than the MIT of most projects here: fine for self-hosting, deliberately awkward for anyone wanting to fork it into a closed hosted competitor.

If your decision rests on maturity or community, the honest answer is that OpenSEO wins on data, SEOMachine wins on content, and neither race is close.

Which one, for which situation

Your situation	Project	Why
Need keyword, rank and backlink data without a Semrush bill	OpenSEO (every-app)	The only one built for it, and by far the most adopted
Already work in Claude Code and want a writing workspace	SEOMachine	The most-starred content project here; sends WordPress drafts
Need an article to appear on WordPress with no manual step	OpenSEO (clawnify) or DispatchSEO	Both publish to WordPress themselves
Need Shopify, Webflow, Ghost or another non-WordPress CMS	AltoRank	The only one here with adapters for CMSs other than WordPress, set up on request until one is verified live
Running a static site and happy to import files	BlogPilot	Widest export coverage, free model tier available
Want block-level control and will build a receiver	openSEO (Juliusolsson05)	Structured generation, webhook delivery
Want a research layer plus a publishing layer	OpenSEO + a content engine	They are complements, not alternatives
Want a hosted product with support	None of these	Open source is the wrong aisle; these rankingCoach alternatives are the hosted do-it-yourself tools, priced

---

AltoRank is the AGPL-3.0 project in the table: keyword research, drafting, scoring and fact-checking, publishing adapters for WordPress, Shopify and other CMSs plus git and webhook, in 35 locales, with the approval gate enforced in the publish path. Self-hosting is free and ungated — the repository is the whole product, not a trimmed community edition. Hosted plans are on the pricing page if you would rather not hold the API keys.

Sources: GitHub REST API (stars, forks, licence, commit dates, read 2 October 2026) · every-app/open-seo · TheCraigHewitt/seomachine · Juliusolsson05/openSEO · clawnify/OpenSEO · NeoZi12/dispatchseo · BlogPilot · LVTD-LLC/TuxSEO · openseo.so · openseo.so/pricing · openseo.so/roadmap