GEOFlow

GEOFlow is an open-source GEO (generative engine optimization) operations system for company sites. The repo yaojingang/GEOFlow is AGPL-3.0, created 2026-04-13, language PHP (Laravel). On 2026-09-14 GitHub listed 3,627 stars and 820 forks. version.json on main is 3.1.0. The product site is geoflow.me. It showed up on X For You when the author posted that GEOFlow 3.0 was ready to deploy, with AI knowledge, content production, quality inspection, and multi-site distribution in one admin.

Compare OpenSEO if you wanted keyword and backlink data instead of a CMS, Claude SEO if you wanted a local audit skill, or n8n if you only needed workflow glue.

Key Features

• One pipeline: trusted knowledge and assets, AI article production, AI quality gates, human review, then company site, hosted channel sites, WordPress REST, HTTP API, or a Chrome-assisted manual publish desk.
• Quality gate: checks knowledge evidence, citations, ad rules, and publish context. Scores, source spans, suggested edits, and history stay on the draft until a human releases it.
• Admin UI V3: six languages, PWA, illustrated help (15 topics, 24 screenshots, 72 fixed evals). Data center covers content, distribution, visits, top pages, and AI crawlers.
• Signed updater: independent GEOFlow Updater does signed packages, full backup, environment checks, and rollback. High-risk steps need admin password plus a 6-digit authenticator code.
• Built-in skill: .agents/skills/geoflow for Laravel, admin, frontend, themes, and channel sites. Codex can call $geoflow.

Limitation: 3,627 stars is a heat signal, not an audit. Current license is AGPL-3.0 (older Apache-2.0 releases stay on that license). Self-host needs PHP 8.3+, PostgreSQL (pgvector recommended), Redis, and Node 22 for frontend builds. Knowledge quality still depends on the corpus and reviewers. Chrome helper uses device pairing and scoped tokens; it does not store external passwords, cookies, or OAuth.

Use Cases

• Brand and content teams who need GEO pages, FAQs, and industry source sites with an audit trail.
• Agencies shipping content ops for clients under AGPL (service fees are allowed; network-modified copies still need corresponding source).
• People who should use OpenSEO instead if they needed rank and backlink tables, not a writing CMS.

Pricing

Getting Started

1. git clone https://github.com/yaojingang/GEOFlow.git && cp .env.example .env
2. docker compose build && docker compose up -d --remove-orphans
3. Open http://localhost:18080 and /geo_admin/login. First boot runs migrations via the init service.
4. Production: use docker-compose.prod.yml and DEPLOYMENT.md. Do not git pull into a live 2.x box.

First-party resource: the README and the 3.0 upgrade guide.

Frequently Asked Questions

Can a company run it internally for free?

Yes. README says internal use, customer ops, and SaaS are allowed under AGPL. If you modify it and staff or customers use it over a network, AGPL section 13 still requires a way to get the corresponding source.

Is this Semrush?

No. GEOFlow authors and publishes site content for AI and search visibility. OpenSEO is the SEO data platform.

Does it phone home?

Anonymous telemetry is off by default. When enabled it sends a random instance id, an irreversible admin digest, version, and event type. No domain, article, cookie, or APP_KEY.

Alternatives

• OpenSEO: keyword, backlink, and GSC data with MCP.
• Claude SEO: a local Claude Code SEO audit skill.
• n8n: generic automation, not a GEO CMS.

Tips

1. Quote AGPL-3.0, 3.1.0, PHP 8.3+, and 3,627 stars from pages checked 2026-09-14.
2. Pin a GitHub Release for production; main can be ahead of tagged builds.
3. Keep knowledge slices and human release as the gate. The AI QC log is evidence, not a substitute for a reviewer.

Conclusion

GEOFlow is the self-hosted GEO CMS that showed up on For You: knowledge in, quality-gated articles out, multi-site and Chrome-assisted publish. Start at github.com/yaojingang/GEOFlow. If you only needed SEO tables, open OpenSEO instead.