Skip to content

0xTrey/customer-owned-content-engine

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

1 Commit
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Customer-Owned Content Engine

A forkable starter kit for building an AI-assisted blog content engine that supports SEO, AEO, and GEO.

This repo is intentionally generic. It is designed for teams who want to point Claude Code, Codex, Cursor, or another coding agent at a clean starter and adapt it to their own brand, topics, publishing stack, and approval workflow.

What this starter does

  • Stores brand rules in brand.yaml
  • Stores planned blog topics in content/topics.yaml
  • Generates an answer-first blog article
  • Adds TL;DR, FAQ, and Article JSON-LD structure
  • Runs a simple quality gate for required structure and forbidden terms
  • Writes generated articles to site/published/
  • Builds a static index in site/dist/
  • Includes tests using Python's built-in unittest

Why it exists

Search is becoming fragmented. Buyers ask Google, AI assistants, sales teams, communities, and peers before talking to a vendor. A content engine gives your team a repeatable way to become the clearest trusted answer across those channels.

AEO means Answer Engine Optimization. GEO means Generative Engine Optimization. SEO means Search Engine Optimization.

Quick start

git clone https://github.com/0xTrey/customer-owned-content-engine.git
cd customer-owned-content-engine
python3 -m unittest discover -v
python3 -m engine.pipeline
open site/dist/index.html

Customize for your company

  1. Edit brand.yaml
  2. Edit content/topics.yaml
  3. Run python3 -m engine.pipeline
  4. Review the article in site/published/
  5. Extend the generator, quality gate, and publishing steps for your stack

How to use with Claude Code or Codex

Open this repo in your coding agent and use the prompt in CODEX_PROMPT.md.

Recommended first task:

Read AGENTS.md and CODEX_PROMPT.md. Then adapt this starter into a content engine for our company using brand.yaml and content/topics.yaml as the source of truth. Keep tests passing and do not add secrets to the repo.

Suggested next extensions

  • Replace the deterministic article generator with your preferred LLM API
  • Add source-backed research collection
  • Add internal link recommendations
  • Add a stronger quality score for citations, extractable summaries, schema, and FAQ depth
  • Add markdown output in addition to HTML
  • Add a CMS exporter for Webflow, WordPress, HubSpot, Contentful, or a static site
  • Add analytics import for rankings, citations, traffic, engagement, and pipeline

Repository principles

  • Brand-owned: your claims, voice, and approvals stay under your control
  • Agent-assisted: agents help with repeatable research, drafting, QA, and monitoring
  • Answer-first: every article should quickly answer the buyer's question
  • Citable: definitions, TL;DRs, FAQs, tables, and short declarative passages should be easy to extract
  • Safe by default: no API keys, no secrets, no customer data, and no proprietary brand references

License

MIT

About

Forkable starter kit for an AI-assisted AEO/GEO/SEO blog content engine

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors