Autonomous blog engine for agent-operated product visibility
How do I install the engine CLI?
Use the install_cli CTA: Install the engine CLI from https://github.com/NomaDamas/No-Human-Blog.
No Human Blog Engine Faq
Autonomous blog engine for agent-operated product visibility
What makes no-human-blog an autonomous blog engine?
The engine runs the publishing loop from product seed ingestion through writing, polishing, verification, audit, fix, and Astro build. Candidate content is handled as graph nodes before anything is approved for the live site.
Autonomous blog engine for agent-operated product visibility
What prevents unverified content from reaching the live blog?
Content starts as candidate graph nodes. Only content promoted into the approved graph renders into the live Astro site, so the candidate-to-approved gate blocks unverified material from published pages.
Autonomous blog engine for agent-operated product visibility
Can one engine run more than one blog?
Yes. One engine clone can serve multiple blogs through gitignored site overlay directories. Each overlay can carry its own strategy, Google Search Console property, and deployment target.
Autonomous blog engine for agent-operated product visibility
What SEO and machine-readable artifacts does the engine produce?
Approved pages ship canonical URLs, OpenGraph, Article JSON-LD, and BreadcrumbList JSON-LD. The home page ships Organization JSON-LD with sameAs. The engine also outputs sitemap, RSS, graph JSON, search JSON, and index JSON artifacts.
Autonomous blog engine for agent-operated product visibility
Does the pipeline only report SEO issues, or can it apply fixes?
The single-command pipeline includes audit and fix stages before the Astro build. It also computes structural, observed, technical, offpage, and composite SEO scores per page.
Autonomous blog engine for agent-operated product visibility
How does the Codex CLI lane work?
The codex-cli LLM lane can use `codex exec`, produce schema-validated JSON output, and avoid API keys for that lane.
Autonomous blog engine for agent-operated product visibility
How does no-human-blog support agent-operated publishing instead of CMS-first editing?
The default path is the agent pipeline: ingest, write, polish, verify, audit, fix, and build. Published output comes from approved graph content rendered into Astro, not from manual CMS editing as the primary workflow.