SEO-Forge
SEO-Forge is Erebros’s search-visibility app at /seo-forge (formerly SEO). It covers audits, keywords and content, with Claude-SEO now on any model (not just Claude) and reports organised into projects that respect the interface language. The old /seo URL redirects here, so pinned links keep working.
Research
Section titled “Research”Keyword data from Google Search Console. The research helper ~/.erebros/gsc-research.py ships with Erebros (provisioned by scripts/install-autostart.sh; it self-installs an isolated venv on first run).
To connect, do the one-time Google OAuth:
- Drop a Desktop-app
~/.erebros/client_secret.jsonfrom Google Cloud. - Run
python3 ~/.erebros/gsc-auth.pyonce — it writes~/.erebros/gsc-token.jsonand the tab goes live.
Generate
Section titled “Generate”Writes a full SEO blog post via Claude into ~/.erebros/seo-posts.
History
Section titled “History”The saved reports for the selected project, newest first (up to 50). Each entry shows
its id, the skill that produced it, the url audited, the createdAt
timestamp and the file path — read from each report’s front-matter. Reports are
stored as Markdown under <vault>/SEO-Forge/<project>/, and can be opened or deleted
from here.
OpenSEO
Section titled “OpenSEO”Embeds the self-hosted every-app/open-seo console on :3001. OpenSEO runs natively (no Docker) from ~/openseo via the openseo.service user unit, so it autostarts on every reboot.
Setup and dependencies
Section titled “Setup and dependencies”- Python 3 — required for keyword research (and shared with P-Forge for
.pptxassembly). - GSC OAuth — a Desktop OAuth
~/.erebros/client_secret.json, thenpython3 ~/.erebros/gsc-auth.pyto write~/.erebros/gsc-token.json. - OpenSEO host — runs natively from
~/openseovia theopenseo.serviceuser unit on:3001. For live data, add a DataForSEO key to~/openseo/.envand restart the service:printf 'you@example.com:YOUR_API_PASSWORD' | base64and paste the result intoDATAFORSEO_API_KEY=. See the OpenSEO setup block inDEPENDENCIES.md.
Where output goes
Section titled “Where output goes”Generated blog posts land in ~/.erebros/seo-posts. Reports are organised into projects that follow the interface language.
- Claude-SEO is no longer Claude-only — point it at any model you have configured.
- OpenSEO works without a key, but wire a DataForSEO key into
~/openseo/.envfor live SERP and keyword data.