Auto-Blogger App
Blogging and backlinks from one client profile.
The problem
Agency SEO work kept client identity, keywords, WordPress credentials, blog generation and backlink planning in separate tools. A second client also exposed that the report page was not truly multi-client: it showed Ethos data under whichever client's name was open.
What it does
One app doing both blogging and backlinks off a single client record that holds the business profile, WordPress credentials, and an auto-publish toggle. From there it generates keyword-targeted posts and a full backlink task list.
Built for agency delivery, so the details matter: prompts pipe through STDIN rather than shell args because multi-line prompts get mangled on Windows, and generation runs from a temp directory so the app’s own config never leaks into client output.
Why it is built this way
I unified blogging and backlink planning behind one isolated client record, with WordPress draft-first by default and live publishing only behind a per-client toggle. The model prompt goes over stdin because Windows mangles multi-line shell arguments, and it runs from a neutral temp directory so this app's own instructions cannot leak into client copy; the local CLI and local image renderer keep marginal cost at zero.
What was hard
The full audit found a hardcoded Ethos report, database pages frozen at build time by static prerendering, a dead Settings link and a deprecated spawn form. The same codebase records two Windows-specific boundaries: shell arguments damaged prompts, while scheduled-task registration was deliberately left unrun because it would create standing system state and could collide with a developer server on port 3000.
Outcomes
- ~79 backlink tasks generated
- 10 task categories
- Drafts by default, never auto-publish