{
  "generated_at": "2026-06-17T08:53:46.702Z",
  "state": "approved",
  "strategy": {
    "product_name": "no-human-blog",
    "primary_audience": "developers and growth operators who want an agent-operated blog that raises a product's search and AI-answer visibility without manual publishing",
    "north_star_goal": "compound qualified engine installs and operator-guide reads driven by machine-readable, proof-first campaign content",
    "allowed_cta_families": [
      "install_cli",
      "download_guide",
      "book_demo"
    ],
    "geo_targets": [
      "global",
      "us",
      "kr"
    ],
    "campaign_ids": [
      "launch-no-human-blog",
      "geo-methodology",
      "codex-automation"
    ]
  },
  "nodes": [
    {
      "slug": "autonomous-blog-engine-for-product-visibility",
      "content_type": "post",
      "title": "Autonomous blog engine for agent-operated product visibility",
      "summary": "no-human-blog is a self-hosted autonomous blog engine for agent-operated publishing. It turns product seeds into candidate graph nodes, verifies content before approval, promotes only approved graph content into the live Astro site, and emits SEO-ready pages plus sitemap, RSS, graph, search, and index artifacts from one pipeline.",
      "source_refs": [
        {
          "label": "Engine README (capability inventory)",
          "url": "https://github.com/NomaDamas/No-Human-Blog/blob/main/README.md"
        },
        {
          "label": "Pipeline scripts (seed→build, single command)",
          "url": "https://github.com/NomaDamas/No-Human-Blog/blob/main/scripts/run-pipeline.mjs"
        },
        {
          "label": "JSON-LD / sitemap / RSS render layer",
          "url": "https://github.com/NomaDamas/No-Human-Blog/blob/main/src/lib/render.mjs"
        },
        {
          "label": "systemd timers for hands-off operation",
          "url": "https://github.com/NomaDamas/No-Human-Blog/blob/main/ops/README.md"
        }
      ],
      "seed_type": "release-note",
      "product_or_offer": "no-human-blog",
      "campaign_id": "launch-no-human-blog",
      "campaign_title": "Launch the no-human-blog autonomous publishing engine",
      "target_query_cluster": [
        "autonomous blog engine",
        "agent-operated publishing",
        "automated seo blog",
        "product visibility automation"
      ],
      "entity_mentions": [
        "no-human-blog",
        "Astro",
        "approved graph",
        "site overlay"
      ],
      "proof_points": [
        "Candidate-to-approved graph gate keeps unverified content off the live Astro site.",
        "Product seeds become candidate graph nodes before publication.",
        "Only approved graph content is promoted to the live Astro site.",
        "Every approved page ships canonical URL, OpenGraph, Article JSON-LD, and BreadcrumbList JSON-LD.",
        "The home page ships Organization JSON-LD with sameAs.",
        "The engine outputs sitemap, RSS, graph JSON, search JSON, and index JSON artifacts.",
        "One engine clone serves multiple blogs via gitignored site overlays.",
        "Each site overlay can carry its own strategy, Google Search Console property, and deployment target.",
        "Single command runs ingest, write, polish, verify, audit, fix, and Astro build.",
        "Audit and fix stages run before Astro build.",
        "systemd timers support hands-off operation.",
        "Structural, observed, technical, offpage, and composite SEO scores are computed per page.",
        "codex-cli LLM lane supports `codex exec`, schema-validated JSON output, and no API keys.",
        "IndexNow submission for Bing freshness is opt-in."
      ],
      "faq": [
        {
          "question": "How do I install the engine CLI?",
          "answer": "Use the install_cli CTA: Install the engine CLI from https://github.com/NomaDamas/No-Human-Blog."
        },
        {
          "question": "What makes no-human-blog an autonomous blog engine?",
          "answer": "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."
        },
        {
          "question": "What prevents unverified content from reaching the live blog?",
          "answer": "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."
        },
        {
          "question": "Can one engine run more than one blog?",
          "answer": "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."
        },
        {
          "question": "What SEO and machine-readable artifacts does the engine produce?",
          "answer": "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."
        },
        {
          "question": "Does the pipeline only report SEO issues, or can it apply fixes?",
          "answer": "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."
        },
        {
          "question": "How does the Codex CLI lane work?",
          "answer": "The codex-cli LLM lane can use `codex exec`, produce schema-validated JSON output, and avoid API keys for that lane."
        },
        {
          "question": "How does no-human-blog support agent-operated publishing instead of CMS-first editing?",
          "answer": "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."
        }
      ],
      "cta_type": "install_cli",
      "cta_label": "Install the engine CLI",
      "cta_url": "https://github.com/NomaDamas/No-Human-Blog",
      "cta_goal_metric": "engine-clones",
      "cta_measurement_mode": "repo-traffic",
      "north_star_alignment": "Matches north-star CTA family install_cli for campaign launch-no-human-blog.",
      "geo_targets": [
        "global",
        "us",
        "kr"
      ],
      "last_reviewed_at": "2026-06-11T05:28:19.515Z",
      "structured_data_type": "Article",
      "agent_actions": [
        "search",
        "quote",
        "act"
      ],
      "topic_slug": "autonomous-publishing",
      "comparison_slug": "no-human-blog-vs-managed-seo-tools",
      "use_case_slug": "product-visibility-automation",
      "faq_slug": "no-human-blog-engine-faq",
      "related_slugs": [
        "geo-is-foundational-seo-encoded-as-software",
        "one-engine-many-blogs-with-site-overlays"
      ],
      "body": "## Positioning\nno-human-blog is for operators who want an automated SEO blog where the agent pipeline is the publishing path. The engine ingests product seeds, writes candidate content, polishes it, verifies it, audits it, applies fixes, and builds the Astro site through a single command.\n\n## Publish Gate\n- Product seeds become candidate graph nodes before publication.\n- Candidate content is verified before promotion.\n- Only approved graph content renders into the live Astro site.\n- The candidate-to-approved graph gate keeps unverified content off published pages.\n\n## SEO And Structured Output\n- Approved pages ship canonical URLs, OpenGraph, Article JSON-LD, and BreadcrumbList JSON-LD.\n- The home page ships Organization JSON-LD with sameAs.\n- The engine also outputs sitemap, RSS, graph JSON, search JSON, and index JSON artifacts.\n- Structural, observed, technical, offpage, and composite SEO scores are computed per page.\n- IndexNow submission for Bing freshness is available as an opt-in workflow.\n\n## Operator Workflow\n- One command runs ingest, write, polish, verify, audit, fix, and Astro build.\n- The audit and fix stages run before build, so the pipeline can apply corrections instead of only reporting issues.\n- systemd timers support hands-off operation.\n- The codex-cli LLM lane can run through `codex exec` with schema-validated JSON output and no API keys.\n\n## Multi-Blog Operation\n- One engine clone can serve multiple blogs through gitignored site overlay directories.\n- Each overlay can carry its own strategy, Google Search Console property, and deployment target.\n- Site overlays keep the engine reusable while allowing each blog to maintain its own publishing constraints.\n\n## Query Coverage\n- autonomous blog engine: self-hosted engine that moves seeds through graph, verification, approval, and Astro build steps.\n- agent-operated publishing: agents run ingest, writing, polish, verification, audit, fix, and build without making a CMS the default path.\n- automated seo blog: approved pages ship canonical URLs, structured data, sitemap, RSS, and audit outputs.\n- product visibility automation: one pipeline produces web pages plus machine-readable graph, search, and index artifacts.\n- codex cli automation: the LLM lane can use `codex exec` with schema-validated JSON output.\n\n## Operator CTA\nInstall the engine CLI from the GitHub repository: https://github.com/NomaDamas/No-Human-Blog\n\n## Internal Link Targets\n- Link operator-loop pages to migration and publishing-system pages.\n- Link publishing-system pages to operational playbooks and migration decisions.\n- Link migration pages to platform comparison, audit, and implementation guides.",
      "routes": {
        "post": "/posts/autonomous-blog-engine-for-product-visibility/",
        "topic": "/topics/autonomous-publishing/",
        "compare": "/compare/no-human-blog-vs-managed-seo-tools/",
        "use_case": "/use-cases/product-visibility-automation/",
        "faq": "/faq/no-human-blog-engine-faq/"
      }
    },
    {
      "slug": "geo-is-foundational-seo-encoded-as-software",
      "content_type": "post",
      "title": "Generative engine optimization done honestly: verified fundamentals, no tricks",
      "summary": "no-human-blog treats generative engine optimization as a documented SEO methodology, not an AI-search shortcut layer. The guide maps each GEO-facing feature to `docs/seo-ssot.md`, keeps verified fundamentals, removes unsupported AI-search mechanisms, and documents the allowed behavior for Google AI Overviews, IndexNow, Bing freshness, JSON-LD, and crawler access.",
      "source_refs": [
        {
          "label": "SEO single source of truth (feature contract)",
          "url": "https://github.com/NomaDamas/No-Human-Blog/blob/main/docs/seo-ssot.md"
        },
        {
          "label": "JSON-LD / sitemap / RSS render layer",
          "url": "https://github.com/NomaDamas/No-Human-Blog/blob/main/src/lib/render.mjs"
        },
        {
          "label": "IndexNow submission lane",
          "url": "https://github.com/NomaDamas/No-Human-Blog/blob/main/src/lib/indexnow.mjs"
        },
        {
          "label": "Engine README (capability inventory)",
          "url": "https://github.com/NomaDamas/No-Human-Blog/blob/main/README.md"
        }
      ],
      "seed_type": "doc-excerpt",
      "product_or_offer": "no-human-blog",
      "campaign_id": "geo-methodology",
      "campaign_title": "GEO is foundational SEO, encoded as software",
      "target_query_cluster": [
        "generative engine optimization",
        "geo vs seo",
        "ai search visibility",
        "llms.txt google"
      ],
      "entity_mentions": [
        "no-human-blog",
        "GEO",
        "Google AI Overviews",
        "IndexNow",
        "Bing"
      ],
      "proof_points": [
        "`docs/seo-ssot.md` classifies every engine-facing feature as keep, remove, or add against the documented methodology.",
        "`llms.txt` and agent-manifest endpoints were removed and return 404 by design.",
        "JSON-LD scope is limited to Article, BreadcrumbList, and home-page Organization/WebSite.",
        "IndexNow key file is emitted on build, with submission available as one command after deploy.",
        "`robots.txt` allows all crawlers uniformly as the documented safe cross-engine default."
      ],
      "faq": [
        {
          "question": "What is the no-human-blog approach to generative engine optimization?",
          "answer": "no-human-blog treats GEO as documented SEO methodology. `docs/seo-ssot.md` classifies engine-facing features as keep, remove, or add instead of adding unsupported AI-search tricks."
        },
        {
          "question": "How does the methodology define GEO vs SEO?",
          "answer": "The methodology keeps GEO tied to durable SEO fundamentals: indexable content, metadata, canonical URLs, eligible structured data, crawler access, and auditable publishing behavior."
        },
        {
          "question": "Does no-human-blog use `llms.txt` for Google visibility?",
          "answer": "No. The methodology removes `llms.txt` and agent-manifest endpoints, and those routes return 404 by design."
        },
        {
          "question": "What structured data is allowed?",
          "answer": "JSON-LD is limited to Article, BreadcrumbList, and home-page Organization/WebSite. The methodology does not add unsupported schema just for AI-search visibility."
        },
        {
          "question": "How does the workflow handle Bing freshness?",
          "answer": "IndexNow is kept as an opt-in Bing freshness mechanism. The build emits the IndexNow key file, and submission is available as one command after deploy."
        },
        {
          "question": "How are crawlers handled?",
          "answer": "`robots.txt` allows all crawlers uniformly, which the methodology documents as the safe cross-engine default."
        },
        {
          "question": "Where can operators get the methodology guide?",
          "answer": "Get the SEO methodology guide at https://github.com/NomaDamas/No-Human-Blog/blob/main/docs/seo-ssot.md."
        }
      ],
      "cta_type": "download_guide",
      "cta_label": "Get the SEO methodology guide",
      "cta_url": "https://github.com/NomaDamas/No-Human-Blog/blob/main/docs/seo-ssot.md",
      "cta_goal_metric": "guide-reads",
      "cta_measurement_mode": "doc-traffic",
      "north_star_alignment": "Matches north-star CTA family download_guide for campaign geo-methodology.",
      "geo_targets": [
        "global",
        "us",
        "kr"
      ],
      "last_reviewed_at": "2026-06-11T04:49:04.573Z",
      "structured_data_type": "Article",
      "agent_actions": [
        "search",
        "quote",
        "act"
      ],
      "topic_slug": "geo-methodology",
      "comparison_slug": "verified-seo-vs-geo-tricks",
      "use_case_slug": "ai-answer-visibility",
      "faq_slug": "geo-methodology-faq",
      "related_slugs": [
        "autonomous-blog-engine-for-product-visibility",
        "one-engine-many-blogs-with-site-overlays"
      ],
      "body": "## Position\n\nGenerative engine optimization should be handled through the same durable constraints as search optimization: indexable content, clear metadata, canonical URLs, eligible structured data, and auditable publishing behavior.\n\nno-human-blog implements GEO as a documented feature contract. `docs/seo-ssot.md` is the single source of truth for what ships, what is removed, and what remains opt-in.\n\n## Methodology\n\n- Keep foundational SEO behavior documented in `docs/seo-ssot.md`.\n- Classify each engine-facing feature as keep, remove, or add against the documented methodology.\n- Remove unsupported AI-only mechanisms such as `llms.txt` and agent-manifest endpoints.\n- Return 404 for removed `llms.txt` and agent-manifest routes by design.\n- Limit JSON-LD to Article, BreadcrumbList, and home-page Organization/WebSite.\n- Keep IndexNow as an opt-in freshness mechanism for Bing.\n- Emit the IndexNow key file during build and run submission as one post-deploy command.\n- Keep `robots.txt` uniformly open as the documented safe cross-engine default.\n\n## Operator Outcome\n\nThe workflow gives operators a verifiable way to handle GEO, SEO, and AI search visibility without shipping unsupported AI-search myths. Every engine-facing behavior is either documented in the SEO SSOT, constrained to known structured-data scope, or removed from the build surface.\n\n## Proof Map\n\n- Source of truth: `docs/seo-ssot.md` defines the methodology and feature status.\n- Removed mechanisms: `llms.txt` and agent-manifest endpoints return 404 by design.\n- Structured data scope: JSON-LD is limited to Article, BreadcrumbList, and home-page Organization/WebSite.\n- Bing freshness: IndexNow key output is produced at build time and submitted after deploy.\n- Crawler access: `robots.txt` allows all crawlers uniformly.\n\n## Internal Link Targets\n\n- publishing-system pages: explain the agent-native publishing workflow and verification gates.\n- operational playbooks: show IndexNow submission and build-time SEO checks.\n- migration decisions: compare durable SEO fundamentals against AI-search shortcut claims.\n\n## CTA\n\nGet the SEO methodology guide: https://github.com/NomaDamas/No-Human-Blog/blob/main/docs/seo-ssot.md",
      "routes": {
        "post": "/posts/geo-is-foundational-seo-encoded-as-software/",
        "topic": "/topics/geo-methodology/",
        "compare": "/compare/verified-seo-vs-geo-tricks/",
        "use_case": "/use-cases/ai-answer-visibility/",
        "faq": "/faq/geo-methodology-faq/"
      }
    },
    {
      "slug": "one-engine-many-blogs-with-site-overlays",
      "content_type": "post",
      "title": "Operate multiple blogs from one no-human-blog engine clone with gitignored site overlays",
      "summary": "no-human-blog is an autonomous blog engine for agent-operated publishing: operators clone the engine once, keep each site's configuration in gitignored overlays, and run a single-command pipeline that ingests seeds, writes drafts, polishes content, verifies claims, audits output, fixes issues, and builds deployable static site artifacts.",
      "source_refs": [
        {
          "label": "Fork-to-operate guide (overlay model)",
          "url": "https://github.com/NomaDamas/No-Human-Blog/blob/main/docs/fork-to-operate.md"
        },
        {
          "label": "Engine README (capability inventory)",
          "url": "https://github.com/NomaDamas/No-Human-Blog/blob/main/README.md"
        },
        {
          "label": "Runtime + Codex CLI provider docs",
          "url": "https://github.com/NomaDamas/No-Human-Blog/blob/main/docs/runtime.md"
        },
        {
          "label": "Pipeline scripts (seed→build, single command)",
          "url": "https://github.com/NomaDamas/No-Human-Blog/blob/main/scripts/run-pipeline.mjs"
        }
      ],
      "seed_type": "campaign-brief",
      "product_or_offer": "no-human-blog",
      "campaign_id": "launch-no-human-blog",
      "campaign_title": "Launch the no-human-blog autonomous publishing engine",
      "target_query_cluster": [
        "autonomous blog engine",
        "agent-operated publishing",
        "automated seo blog",
        "multi-site publishing engine"
      ],
      "entity_mentions": [
        "no-human-blog",
        "systemd",
        "GitHub"
      ],
      "proof_points": [
        "One engine clone can support many blogs through gitignored per-site overlays.",
        "The pipeline covers ingest, write, polish, verify, audit, fix, and build as one operator workflow.",
        "Candidate-to-approved graph gating prevents unverified content from becoming approved output.",
        "Static site output keeps publishing artifacts machine-readable and deployable.",
        "systemd timers support hands-off operation after the engine is configured.",
        "The CTA points directly to the engine CLI installation guide: https://github.com/NomaDamas/No-Human-Blog/blob/main/docs/runtime.md"
      ],
      "faq": [
        {
          "question": "How do I install the no-human-blog engine CLI?",
          "answer": "Use the Install the engine CLI guide at https://github.com/NomaDamas/No-Human-Blog/blob/main/docs/runtime.md. The CTA is install_cli, so the next step is to install the engine CLI before configuring site overlays or timers."
        },
        {
          "question": "Can one no-human-blog engine clone operate more than one blog?",
          "answer": "Yes. The documented operating model is one reusable engine clone with each site's configuration kept in gitignored overlays."
        },
        {
          "question": "What prevents unverified content from shipping?",
          "answer": "The candidate-to-approved graph gate blocks unverified candidate content from becoming approved publishing output."
        },
        {
          "question": "What does the no-human-blog pipeline do?",
          "answer": "The single-command operator workflow covers ingest, write, polish, verify, audit, fix, and build."
        },
        {
          "question": "How does no-human-blog support hands-off operation?",
          "answer": "After the engine is configured, systemd timers can run the pipeline hands-off while preserving the same ingest-to-build workflow."
        },
        {
          "question": "Why is no-human-blog relevant to automated SEO blog operations?",
          "answer": "It connects seed ingestion, drafting, polishing, claim verification, output auditing, issue fixing, and static site building in one repeatable operator workflow instead of relying on disconnected manual CMS steps."
        }
      ],
      "cta_type": "install_cli",
      "cta_label": "Install the engine CLI",
      "cta_url": "https://github.com/NomaDamas/No-Human-Blog/blob/main/docs/runtime.md",
      "cta_goal_metric": "engine-installs",
      "cta_measurement_mode": "cli-install-intent",
      "north_star_alignment": "Matches north-star CTA family install_cli for campaign launch-no-human-blog.",
      "geo_targets": [
        "global",
        "us",
        "kr"
      ],
      "last_reviewed_at": "2026-06-11T05:28:39.513Z",
      "structured_data_type": "Article",
      "agent_actions": [
        "search",
        "quote",
        "act"
      ],
      "topic_slug": "multi-site-agent-publishing",
      "comparison_slug": "engine-clone-vs-cms-editing",
      "use_case_slug": "multi-site-product-visibility",
      "faq_slug": "site-overlays-faq",
      "related_slugs": [
        "autonomous-blog-engine-for-product-visibility",
        "geo-is-foundational-seo-encoded-as-software"
      ],
      "body": "## Operational Model\n\nno-human-blog is a reusable publishing engine for running multiple blogs from one engine boundary.\n\n- Clone the engine once.\n- Keep each site's configuration in gitignored overlays.\n- Operate many blogs without creating a separate CMS project per site.\n- Build static site output that remains machine-readable and deployable.\n\n## Pipeline Proof\n\nThe operator workflow is one pipeline, not a loose set of manual publishing tasks.\n\n- ingest seeds\n- write drafts\n- polish content\n- verify claims\n- audit output\n- fix issues\n- build the static site\n\nThis supports autonomous blog engine, agent-operated publishing, automated seo blog, and multi-site publishing engine intent because the workflow is explicit, repeatable, and artifact-oriented.\n\n## Verification Gate\n\nno-human-blog uses a candidate-to-approved graph gate.\n\n- Candidate content starts outside the approved publishing path.\n- Verification is required before candidate content can become approved output.\n- Unverified content does not ship.\n\n## Machine-Readable Publishing Output\n\nThe pipeline builds static site artifacts instead of depending on human CMS editing as the default publishing path.\n\n- Publishing output is generated from the engine workflow.\n- Static artifacts are deployable after the build step.\n- Structured publishing assets can stay aligned with the same operator pipeline.\n\n## Hands-Off Operation\n\nAfter configuration, systemd timers can run the pipeline hands-off.\n\n- Operators configure the engine and site overlays.\n- The timer runs the publishing workflow on schedule.\n- The same ingest-to-build path is used for unattended operation.\n\n## Next Step\n\nInstall the engine CLI from the runtime guide: https://github.com/NomaDamas/No-Human-Blog/blob/main/docs/runtime.md",
      "routes": {
        "post": "/posts/one-engine-many-blogs-with-site-overlays/",
        "topic": "/topics/multi-site-agent-publishing/",
        "compare": "/compare/engine-clone-vs-cms-editing/",
        "use_case": "/use-cases/multi-site-product-visibility/",
        "faq": "/faq/site-overlays-faq/"
      }
    }
  ],
  "topics": [
    {
      "slug": "autonomous-publishing",
      "title": "Autonomous Publishing",
      "route": "/topics/autonomous-publishing/",
      "posts": [
        {
          "slug": "autonomous-blog-engine-for-product-visibility",
          "title": "Autonomous blog engine for agent-operated product visibility",
          "summary": "no-human-blog is a self-hosted autonomous blog engine for agent-operated publishing. It turns product seeds into candidate graph nodes, verifies content before approval, promotes only approved graph content into the live Astro site, and emits SEO-ready pages plus sitemap, RSS, graph, search, and index artifacts from one pipeline.",
          "cta_label": "Install the engine CLI"
        }
      ]
    },
    {
      "slug": "geo-methodology",
      "title": "Geo Methodology",
      "route": "/topics/geo-methodology/",
      "posts": [
        {
          "slug": "geo-is-foundational-seo-encoded-as-software",
          "title": "Generative engine optimization done honestly: verified fundamentals, no tricks",
          "summary": "no-human-blog treats generative engine optimization as a documented SEO methodology, not an AI-search shortcut layer. The guide maps each GEO-facing feature to `docs/seo-ssot.md`, keeps verified fundamentals, removes unsupported AI-search mechanisms, and documents the allowed behavior for Google AI Overviews, IndexNow, Bing freshness, JSON-LD, and crawler access.",
          "cta_label": "Get the SEO methodology guide"
        }
      ]
    },
    {
      "slug": "multi-site-agent-publishing",
      "title": "Multi Site Agent Publishing",
      "route": "/topics/multi-site-agent-publishing/",
      "posts": [
        {
          "slug": "one-engine-many-blogs-with-site-overlays",
          "title": "Operate multiple blogs from one no-human-blog engine clone with gitignored site overlays",
          "summary": "no-human-blog is an autonomous blog engine for agent-operated publishing: operators clone the engine once, keep each site's configuration in gitignored overlays, and run a single-command pipeline that ingests seeds, writes drafts, polishes content, verifies claims, audits output, fixes issues, and builds deployable static site artifacts.",
          "cta_label": "Install the engine CLI"
        }
      ]
    }
  ],
  "compares": [
    {
      "slug": "engine-clone-vs-cms-editing",
      "title": "Engine Clone Vs Cms Editing",
      "route": "/compare/engine-clone-vs-cms-editing/",
      "posts": [
        {
          "slug": "one-engine-many-blogs-with-site-overlays",
          "title": "Operate multiple blogs from one no-human-blog engine clone with gitignored site overlays",
          "summary": "no-human-blog is an autonomous blog engine for agent-operated publishing: operators clone the engine once, keep each site's configuration in gitignored overlays, and run a single-command pipeline that ingests seeds, writes drafts, polishes content, verifies claims, audits output, fixes issues, and builds deployable static site artifacts.",
          "cta_label": "Install the engine CLI"
        }
      ]
    },
    {
      "slug": "no-human-blog-vs-managed-seo-tools",
      "title": "No Human Blog Vs Managed Seo Tools",
      "route": "/compare/no-human-blog-vs-managed-seo-tools/",
      "posts": [
        {
          "slug": "autonomous-blog-engine-for-product-visibility",
          "title": "Autonomous blog engine for agent-operated product visibility",
          "summary": "no-human-blog is a self-hosted autonomous blog engine for agent-operated publishing. It turns product seeds into candidate graph nodes, verifies content before approval, promotes only approved graph content into the live Astro site, and emits SEO-ready pages plus sitemap, RSS, graph, search, and index artifacts from one pipeline.",
          "cta_label": "Install the engine CLI"
        }
      ]
    },
    {
      "slug": "verified-seo-vs-geo-tricks",
      "title": "Verified Seo Vs Geo Tricks",
      "route": "/compare/verified-seo-vs-geo-tricks/",
      "posts": [
        {
          "slug": "geo-is-foundational-seo-encoded-as-software",
          "title": "Generative engine optimization done honestly: verified fundamentals, no tricks",
          "summary": "no-human-blog treats generative engine optimization as a documented SEO methodology, not an AI-search shortcut layer. The guide maps each GEO-facing feature to `docs/seo-ssot.md`, keeps verified fundamentals, removes unsupported AI-search mechanisms, and documents the allowed behavior for Google AI Overviews, IndexNow, Bing freshness, JSON-LD, and crawler access.",
          "cta_label": "Get the SEO methodology guide"
        }
      ]
    }
  ],
  "useCases": [
    {
      "slug": "ai-answer-visibility",
      "title": "Ai Answer Visibility",
      "route": "/use-cases/ai-answer-visibility/",
      "posts": [
        {
          "slug": "geo-is-foundational-seo-encoded-as-software",
          "title": "Generative engine optimization done honestly: verified fundamentals, no tricks",
          "summary": "no-human-blog treats generative engine optimization as a documented SEO methodology, not an AI-search shortcut layer. The guide maps each GEO-facing feature to `docs/seo-ssot.md`, keeps verified fundamentals, removes unsupported AI-search mechanisms, and documents the allowed behavior for Google AI Overviews, IndexNow, Bing freshness, JSON-LD, and crawler access.",
          "cta_label": "Get the SEO methodology guide"
        }
      ]
    },
    {
      "slug": "multi-site-product-visibility",
      "title": "Multi Site Product Visibility",
      "route": "/use-cases/multi-site-product-visibility/",
      "posts": [
        {
          "slug": "one-engine-many-blogs-with-site-overlays",
          "title": "Operate multiple blogs from one no-human-blog engine clone with gitignored site overlays",
          "summary": "no-human-blog is an autonomous blog engine for agent-operated publishing: operators clone the engine once, keep each site's configuration in gitignored overlays, and run a single-command pipeline that ingests seeds, writes drafts, polishes content, verifies claims, audits output, fixes issues, and builds deployable static site artifacts.",
          "cta_label": "Install the engine CLI"
        }
      ]
    },
    {
      "slug": "product-visibility-automation",
      "title": "Product Visibility Automation",
      "route": "/use-cases/product-visibility-automation/",
      "posts": [
        {
          "slug": "autonomous-blog-engine-for-product-visibility",
          "title": "Autonomous blog engine for agent-operated product visibility",
          "summary": "no-human-blog is a self-hosted autonomous blog engine for agent-operated publishing. It turns product seeds into candidate graph nodes, verifies content before approval, promotes only approved graph content into the live Astro site, and emits SEO-ready pages plus sitemap, RSS, graph, search, and index artifacts from one pipeline.",
          "cta_label": "Install the engine CLI"
        }
      ]
    }
  ],
  "faqs": [
    {
      "slug": "geo-methodology-faq",
      "title": "Geo Methodology Faq",
      "route": "/faq/geo-methodology-faq/",
      "items": [
        {
          "question": "What is the no-human-blog approach to generative engine optimization?",
          "answer": "no-human-blog treats GEO as documented SEO methodology. `docs/seo-ssot.md` classifies engine-facing features as keep, remove, or add instead of adding unsupported AI-search tricks.",
          "source_slug": "geo-is-foundational-seo-encoded-as-software",
          "source_title": "Generative engine optimization done honestly: verified fundamentals, no tricks"
        },
        {
          "question": "How does the methodology define GEO vs SEO?",
          "answer": "The methodology keeps GEO tied to durable SEO fundamentals: indexable content, metadata, canonical URLs, eligible structured data, crawler access, and auditable publishing behavior.",
          "source_slug": "geo-is-foundational-seo-encoded-as-software",
          "source_title": "Generative engine optimization done honestly: verified fundamentals, no tricks"
        },
        {
          "question": "Does no-human-blog use `llms.txt` for Google visibility?",
          "answer": "No. The methodology removes `llms.txt` and agent-manifest endpoints, and those routes return 404 by design.",
          "source_slug": "geo-is-foundational-seo-encoded-as-software",
          "source_title": "Generative engine optimization done honestly: verified fundamentals, no tricks"
        },
        {
          "question": "What structured data is allowed?",
          "answer": "JSON-LD is limited to Article, BreadcrumbList, and home-page Organization/WebSite. The methodology does not add unsupported schema just for AI-search visibility.",
          "source_slug": "geo-is-foundational-seo-encoded-as-software",
          "source_title": "Generative engine optimization done honestly: verified fundamentals, no tricks"
        },
        {
          "question": "How does the workflow handle Bing freshness?",
          "answer": "IndexNow is kept as an opt-in Bing freshness mechanism. The build emits the IndexNow key file, and submission is available as one command after deploy.",
          "source_slug": "geo-is-foundational-seo-encoded-as-software",
          "source_title": "Generative engine optimization done honestly: verified fundamentals, no tricks"
        },
        {
          "question": "How are crawlers handled?",
          "answer": "`robots.txt` allows all crawlers uniformly, which the methodology documents as the safe cross-engine default.",
          "source_slug": "geo-is-foundational-seo-encoded-as-software",
          "source_title": "Generative engine optimization done honestly: verified fundamentals, no tricks"
        },
        {
          "question": "Where can operators get the methodology guide?",
          "answer": "Get the SEO methodology guide at https://github.com/NomaDamas/No-Human-Blog/blob/main/docs/seo-ssot.md.",
          "source_slug": "geo-is-foundational-seo-encoded-as-software",
          "source_title": "Generative engine optimization done honestly: verified fundamentals, no tricks"
        }
      ]
    },
    {
      "slug": "no-human-blog-engine-faq",
      "title": "No Human Blog Engine Faq",
      "route": "/faq/no-human-blog-engine-faq/",
      "items": [
        {
          "question": "How do I install the engine CLI?",
          "answer": "Use the install_cli CTA: Install the engine CLI from https://github.com/NomaDamas/No-Human-Blog.",
          "source_slug": "autonomous-blog-engine-for-product-visibility",
          "source_title": "Autonomous blog engine for agent-operated product visibility"
        },
        {
          "question": "What makes no-human-blog an autonomous blog engine?",
          "answer": "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.",
          "source_slug": "autonomous-blog-engine-for-product-visibility",
          "source_title": "Autonomous blog engine for agent-operated product visibility"
        },
        {
          "question": "What prevents unverified content from reaching the live blog?",
          "answer": "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.",
          "source_slug": "autonomous-blog-engine-for-product-visibility",
          "source_title": "Autonomous blog engine for agent-operated product visibility"
        },
        {
          "question": "Can one engine run more than one blog?",
          "answer": "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.",
          "source_slug": "autonomous-blog-engine-for-product-visibility",
          "source_title": "Autonomous blog engine for agent-operated product visibility"
        },
        {
          "question": "What SEO and machine-readable artifacts does the engine produce?",
          "answer": "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.",
          "source_slug": "autonomous-blog-engine-for-product-visibility",
          "source_title": "Autonomous blog engine for agent-operated product visibility"
        },
        {
          "question": "Does the pipeline only report SEO issues, or can it apply fixes?",
          "answer": "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.",
          "source_slug": "autonomous-blog-engine-for-product-visibility",
          "source_title": "Autonomous blog engine for agent-operated product visibility"
        },
        {
          "question": "How does the Codex CLI lane work?",
          "answer": "The codex-cli LLM lane can use `codex exec`, produce schema-validated JSON output, and avoid API keys for that lane.",
          "source_slug": "autonomous-blog-engine-for-product-visibility",
          "source_title": "Autonomous blog engine for agent-operated product visibility"
        },
        {
          "question": "How does no-human-blog support agent-operated publishing instead of CMS-first editing?",
          "answer": "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.",
          "source_slug": "autonomous-blog-engine-for-product-visibility",
          "source_title": "Autonomous blog engine for agent-operated product visibility"
        }
      ]
    },
    {
      "slug": "site-overlays-faq",
      "title": "Site Overlays Faq",
      "route": "/faq/site-overlays-faq/",
      "items": [
        {
          "question": "How do I install the no-human-blog engine CLI?",
          "answer": "Use the Install the engine CLI guide at https://github.com/NomaDamas/No-Human-Blog/blob/main/docs/runtime.md. The CTA is install_cli, so the next step is to install the engine CLI before configuring site overlays or timers.",
          "source_slug": "one-engine-many-blogs-with-site-overlays",
          "source_title": "Operate multiple blogs from one no-human-blog engine clone with gitignored site overlays"
        },
        {
          "question": "Can one no-human-blog engine clone operate more than one blog?",
          "answer": "Yes. The documented operating model is one reusable engine clone with each site's configuration kept in gitignored overlays.",
          "source_slug": "one-engine-many-blogs-with-site-overlays",
          "source_title": "Operate multiple blogs from one no-human-blog engine clone with gitignored site overlays"
        },
        {
          "question": "What prevents unverified content from shipping?",
          "answer": "The candidate-to-approved graph gate blocks unverified candidate content from becoming approved publishing output.",
          "source_slug": "one-engine-many-blogs-with-site-overlays",
          "source_title": "Operate multiple blogs from one no-human-blog engine clone with gitignored site overlays"
        },
        {
          "question": "What does the no-human-blog pipeline do?",
          "answer": "The single-command operator workflow covers ingest, write, polish, verify, audit, fix, and build.",
          "source_slug": "one-engine-many-blogs-with-site-overlays",
          "source_title": "Operate multiple blogs from one no-human-blog engine clone with gitignored site overlays"
        },
        {
          "question": "How does no-human-blog support hands-off operation?",
          "answer": "After the engine is configured, systemd timers can run the pipeline hands-off while preserving the same ingest-to-build workflow.",
          "source_slug": "one-engine-many-blogs-with-site-overlays",
          "source_title": "Operate multiple blogs from one no-human-blog engine clone with gitignored site overlays"
        },
        {
          "question": "Why is no-human-blog relevant to automated SEO blog operations?",
          "answer": "It connects seed ingestion, drafting, polishing, claim verification, output auditing, issue fixing, and static site building in one repeatable operator workflow instead of relying on disconnected manual CMS steps.",
          "source_slug": "one-engine-many-blogs-with-site-overlays",
          "source_title": "Operate multiple blogs from one no-human-blog engine clone with gitignored site overlays"
        }
      ]
    }
  ]
}