Skill: x-rayluan/geo-content-ops (version 0.1.0)

--- name: openclaw-geo-content-ops description: Use when Ray asks to design, operate, audit, or improve OpenClaw GEO content operations beyond single-article writing: knowledge sources, topic clusters, content tasks, publish targets, llms.txt, schema, multi-site distribution, receipts, AI crawler visibility, or GEO analytics. version: "0.1.0" license: MIT tags: - openclaw - geo - ai-search-visibility - content-ops - distribution - analytics --- # OpenClaw GEO Content Ops This skill turns GEO from "write more posts" into an operating system for trusted source material, content production, publication targets, LLM-friendly artifacts, receipts, and visibility analytics. It is inspired by GEOFlow's content-engineering architecture, but it does not require adopting GEOFlow's Laravel CMS. Use it to extend the existing OpenClaw SEO/GEO workflow, not to replace `openclaw-seo-geo-workflow` or [REDACTED_SECRET]. ## Use Boundaries Use this skill for: - GEO operating model design. - Content asset inventory and source-of-truth planning. - Topic cluster, keyword, FAQ, and question map organization. - Daily/weekly content ops planning. - Multi-site or multi-channel publication design. - `llms.txt`, sitemap, TXT map, Schema, Open Graph, and AI-summary artifact planning. - Receipt design for publish, crawl, citation, and analytics evidence. - GEO dashboard/KPI design. - Deciding what to borrow from GEOFlow. Do not use this skill as the writing layer for a single article. Use [REDACTED_SECRET] for that. Do not claim live publish, indexing, ranking, crawler visits, or AI citations without receipts. ## Core Object Model Use these nouns consistently: | Object | Purpose | Example Artifact | | --- | --- | --- | | `knowledge_sources` | Trusted facts, docs, product pages, customer proof, FAQs, competitor notes | `catalogs/sources.jsonl`, source briefs, uploaded docs | | `topic_clusters` | Search/AI questions grouped by intent and entity | keyword master, topic cluster markdown | | `content_tasks` | Planned work units with owner, date, source, status, target query, and publish scope | daily manifest, task JSON | | `draft_assets` | Generated article, metadata, schema, social/X derivative, images | `delivery/seo-geo/YYYY-MM-DD/` | | `publication_targets` | Where content can go | ClawLite blog, WordPress, static GEO site, X, Feishu doc | | `geo_artifacts` | LLM/search-readable outputs around content | `llms.txt`, sitemap, Schema, TXT map, FAQ blocks | | `receipts` | Durable proof of state transitions | generation, audit, publish, deploy, live QA, patrol | | `visibility_signals` | Evidence content is discoverable or useful | crawl logs, GA4, indexing, AI crawler, citation checks | Canonical source catalog: ```text clawlite-brain/catalogs/sources.jsonl ``` Relationship to ClawLite wiki: - `knowledge_sources` is the evidence/source index. It points to raw docs, canonical files, receipts, URLs, and selected compiled wiki pages. - `clawlite-brain/wiki/` is the durable compiled knowledge layer for project memory and retrieval. - `synthadoc/wiki/` is a readable/generated wiki layer for brand, SEO, Hunter topics, and agent navigation. - Prefer raw/canonical sources for factual claims; use wiki pages for fast orientation and retrieval. - When daily findings become durable, promote them from receipts into `sources.jsonl` and then into topic/entity/synthesis wiki pages when warranted. ## Operating Loop 1. **Collect sources.** Confirm the facts are real, owned, current, and citeable. 2. **Build clusters.** Convert sources into user questions, entity maps, keywords, comparison angles, and FAQs. 3. **Create tasks.** For each task, define target reader, core query, primary answer, required sources, publish target, and success signal. 4. **Generate and audit.** Use the writing layer for drafts; require source grounding, direct answer, extractable structure, metadata, and schema hints. 5. **Publish by target.** Treat source publish, site deploy, social post, and remote distribution as separate state transitions. 6. **Emit GEO artifacts.** Keep `llms.txt`, sitemap, TXT map, Schema, Open Graph, and canonical data aligned with published content. 7. **Write receipts.** Store what happened, what was skipped, what failed, and which evidence supports the claim. 8. **Measure signals.** Monitor AI crawler hits, search index state, page views, citations, top content, failures, and stale content. 9. **Feed learning back.** Promote useful daily findings into `keywords-master.json`, topic clusters, source catalog, or rescue tasks. ## Required Task Brief Every GEO content task should include: ```json { "taskId": "geo-YYYY-MM-DD-slug", "status": "planned", "targetReader": "specific reader", "coreQuery": "question this page answers", "primaryAnswer": "short answer the page must give", "requiredSources": ["source-id-or-url"], "entities": ["OpenClaw", "ClawLite"], "topicCluster": "cluster-name", "publishScope": ["clawlite_blog"], "geoArtifacts": ["schema", "sitemap", "llms_txt"], "successSignals": ["live_url", "index_check", "ai_crawler_log"] } ``` If any field is missing, make the smallest honest assumption and mark it in the receipt. Do not silently invent sources. ## Publication Target Rules - `clawlite_blog`: requires source apply/build evidence and, for production claims, deploy plus live QA. - `wordpress_rest`: requires remote ID/URL, media sync result, and API response receipt. - `static_geo_site`: requires generated HTML/Markdown, sitemap/TXT map update, and reachable URL check. - `x_post`: requires a derivative artifact tied to the article's narrative spine; do not treat social posting as blog publication. - `feishu_doc`: useful for internal review; not a public GEO signal unless explicitly published externally. Remote distribution failure must not rewrite history. Mark the target as `FAILED` or `NEEDS_RETRY`; keep local publish status separate. ## GEO Artifact Checklist For public web targets, check whether each published page or batch has: - canonical URL and stable slug - title and meta description - Open Graph/Twitter metadata where relevant - Article/FAQ/HowTo/Organization schema where appropriate - sitemap inclusion - `llms.txt` or site-level AI-readable map inclusion - TXT map or Markdown index for important content hubs - internal links to and from related cluster pages - source/evidence block where claims need grounding - clear update timestamp for evergreen pages ## Receipts Recommended receipt shape: ```json { "date": "YYYY-MM-DD", "taskId": "geo-YYYY-MM-DD-slug", "stage": "publish|artifact|patrol|analytics", "target": "clawlite_blog", "status": "PASS|FAIL|SKIPPED|NEEDS_DATA|PASS_WITH_WARNINGS", "evidence": { "localPath": "path/to/file", "liveUrl": "https://example.com/page", "deployId": "optional", "checkedAt": "ISO timestamp" }, "warnings": [], "nextActions": [] } ``` Status vocabulary must match `openclaw-seo-geo-workflow` where possible. ## Analytics Questions When designing or auditing GEO analytics, answer: - What was created, audited, published, deployed, skipped, or failed? - Which sources and clusters produced publishable work? - Which targets received the content? - Which pages are included in sitemap/`llms.txt`/TXT maps? - Which content received crawler traffic or AI crawler hits? - Which pages need refresh, consolidation, internal links, or rescue? - Which daily findings should be promoted into durable source/keyword/topic files? ## When Borrowing From GEOFlow Borrow patterns, not the whole stack: - structured source library before generation - task queue state machine - local publish separate from remote distribution - target-site Agent / WordPress provider abstraction - `llms.txt`, sitemap, TXT map, Schema output - access-log and AI-crawler analytics Read `references/geoflow-patterns.md` when designing implementation details or mapping this to code.

path: README.md
content: # OpenClaw GEO Content Ops

> Languages: [简体中文](README.md) | [English](docs/readme/README_en.md) | [日本語](docs/readme/README_ja.md) | [Español](docs/readme/README_es.md) | [Русский](docs/readme/README_ru.md) | [Português (BR)](docs/readme/README_pt_BR.md)

> OpenClaw GEO Content Ops 是一个面向 GEO（生成式引擎优化）的轻量级 Skill 与内容运营模型。它把可信知识源、topic clusters、内容任务、AI Search 写作、SEO/GEO 工作流 receipts、发布目标、LLM 友好 artifacts 和可见度 analytics 串成一条可审计的内容资产链路。

[![Skill](https://img.shields.io/badge/OpenClaw-Skill-0F766E)](#快速开始)
[![GEO](https://img.shields.io/badge/GEO-Content%20Ops-blue)](#你可以用它做什么)
[![License](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)

OpenClaw GEO Content Ops 以 [MIT License](LICENSE) 开源发布。你可以自由使用、复制、修改和分发本项目，包括商业使用；请保留版权声明和许可证文本。

---

## 你可以用它做什么

| 层级 | 说明 |
| --- | --- |
| 知识源目录 | 管理品牌文档、产品事实、receipts、URL、客户问题、竞品记录和 wiki 页面 |
| Topic clusters | 沉淀问题、关键词、实体、对比角度和 FAQ 地图 |
| 内容任务 | 把读者、核心问题、source evidence、发布范围和成功信号串成任务 brief |
| 写作协同 | 与 AI Search writer 分工，保证单篇内容 answer-first、可引用、可抽取 |
| SEO/GEO 工作流 | 与 Hunter/Tony/Peter daily workflow、发布门禁和 receipts 分工 |
| 发布目标 | 支持 ClawLite blog、WordPress REST、静态 GEO site、X posts、Feishu docs 和后续 provider |
| GEO artifacts | 管理 `llms.txt`、sitemap、TXT map、Schema、Open Graph、canonical URL 和证据块 |
| Receipts | 保存生成、审核、发布、部署、live QA、patrol、analytics 的 durable evidence |
| 可见度分析 | 追踪 AI crawler hits、indexing、sitemap coverage、AI citation checks、top content 和 rescue tasks |

---

## 为什么需要它

很多 SEO/GEO 系统把三件事混在一起：找资料、写内容、证明发布。结果就是“多写文章”，但没有可信来源、没有发布证据，也没有反馈回流。

OpenClaw GEO Content Ops 把三层分开：

1. **内容运营层**：决定 sources、topics、tasks、targets、artifacts、receipts 和 analytics。
2. **每日执行层**：由 `openclaw-seo-geo-workflow` 执行 Hunter/Tony/Peter 生产、发布、QA 和 patrol。
3. **单篇写作层**：由 `ai-search-visibility-content-writing` 保证内容清晰、可抽取、可引用。

这个 repo 是运营层，不替代写作 skill，也不替代发布 workflow。

---

## 运行结构

```text
knowledge_sources
    ↓
topic_clusters
    ↓
content_tasks
    ↓
AI-search content writing
    ↓
SEO/GEO workflow receipts
    ↓
publication_targets
    ↓
GEO artifacts
    ↓
visibility analytics
    ↓
source/wiki promotion
```

---

## 系统架构

| 组件 | 作用 | 示例 |
| --- | --- | --- |
| `knowledge_sources` | 证据与来源索引 | `catalogs/sources.jsonl` |
| `clawlite-brain/wiki` | 长期项目知识层 | topic/entity/synthesis pages |
| `synthadoc/wiki` | 可读的生成式导航与 topic 页面 | brand hub、keyword map、Hunter pages |
| `topic_clusters` | 内容战略层 | keywords、questions、comparison pages |
| `content_tasks` | 执行 brief 层 | reader、query、answer、source IDs |
| `openclaw-seo-geo-workflow` | 每日交付控制器 | Hunter/Tony/Peter receipts |
| `ai-search-visibility-content-writing` | 单篇写作层 | answer-first body、metadata、schema hints |
| `publication_targets` | 分发层 | ClawLite blog、WordPress、static site、X |
| `geo_artifacts` | LLM/search 可读输出 | `llms.txt`、sitemap、Schema、TXT map |
| `visibility_signals` | 监控层 | crawler logs、indexing、AI citations |

---

## 与现有 Skill 如何协同

| Skill | 负责 | 不负责 |
| --- | --- | --- |
| `openclaw-geo-content-ops` | sources、topics、tasks、targets、artifacts、receipts、analytics | 单篇正文写作或无证据的 live publish claim |
| `openclaw-seo-geo-workflow` | Hunter/Tony/Peter daily execution、publish gates、receipts、patrol | 长期 source catalog governance |
| `ai-search-visibility-content-writing` | 单篇内容质量、直接答案、实体清晰、可引用结构 | 选题发现、部署、analytics |
| `claw-wiki` | 从 canonical source 生成可读 wiki 页面 | 原始来源注册和发布状态判断 |

推荐顺序：

1. 用 `openclaw-geo-content-ops` 选择 sources、clusters、tasks、targets 和 success signals。
2. 用 `openclaw-seo-geo-workflow` 跑或审查 daily production 与 publish evidence。
3. 用 `ai-search-visibility-content-writing` 写或改单篇内容。
4. 再用 `openclaw-geo-content-ops` 把 validated findings 回流到 source catalog、wiki、rescue tasks 和 analytics。

---

## 快速开始

### 安装为 Codex Skill

```bash
mkdir -p ~/.codex/skills
git clone https://github.com/X-RayLuan/openclaw-geo-content-ops.git ~/.codex/skills/openclaw-geo-content-ops
```

### 安装为 OpenClaw Workspace Skill

```bash
mkdir -p ~/.openclaw/workspace/skills
git clone https://github.com/X-RayLuan/openclaw-geo-content-ops.git ~/.openclaw/workspace/skills/openclaw-geo-content-ops
```

### 使用方式

```text
Use openclaw-geo-content-ops to design this week's GEO content operating plan.
```

```text
Use openclaw-geo-content-ops to audit whether today's SEO/GEO workflow promoted the right findings back into sources and wiki.
```

---

## Source Catalog

Source catalog 是 JSONL 证据索引。每一行是一个 source：

```json
{
  "id": "clawlite-positioning",
  "type": "brand_doc",
  "title": "ClawLite Positioning",
  "path": "references/clawlite-brand/positioning.md",
  "trustLevel": "owned",
  "capturedAt": "2026-05-24T00:00:00+08:00",
  "summary": "Canonical positioning source for ClawLite.",
  "entities": ["ClawLite", "OpenClaw"],
  "usableFor": ["brand-positioning", "comparison-pages"]
}
```

参考：`examples/sources.example.jsonl`

---

## Task Brief

每个 GEO content task 都应该把 source evidence 和 publish target 连起来：

```json
{
  "taskId": "geo-2026-05-24-openclaw-routing-cost-control",
  "status": "planned",
  "targetReader": "AI team operator",
  "coreQuery": "How can teams control OpenClaw routing cost without losing reliability?",
  "primaryAnswer": "Use a verified routing policy, receipts, and rollback gates instead of manual model switching.",
  "requiredSources": ["clawlite-positioning", "clawlite-topic-clusters"],
  "entities": ["OpenClaw", "ClawLite"],
  "topicCluster": "routing-cost-control",
  "publishScope": ["clawlite_blog", "x_post"],
  "geoArtifacts": ["schema", "sitemap", "llms_txt"],
  "successSignals": ["live_url", "index_check", "ai_crawler_log"]
}
```

参考：`examples/task.example.json`

---

## Receipt Contract

没有 evidence，就不要声明生产发布、索引、AI crawler visits、排名或 AI citation。

```json
{
  "date": "2026-05-24",
  "taskId": "geo-2026-05-24-openclaw-routing-cost-control",
  "stage": "publish",
  "target": "clawlite_blog",
  "status": "PASS",
  "evidence": {
    "localPath": "delivery/seo-geo/2026-05-24/manifest.json",
    "liveUrl": "https://clawlite.ai/blog/openclaw-routing-cost-control",
    "checkedAt": "2026-05-24T10:00:00+08:00"
  },
  "warnings": [],
  "nextActions": []
}
```

参考：`examples/receipt.example.json`

---

## GEO Artifact Checklist

公开 web target 应检查：

- canonical URL 和稳定 slug
- title 和 meta description
- Open Graph / Twitter metadata
- Article、FAQ、HowTo 或 Organization Schema
- sitemap inclusion
- `llms.txt` 或 AI-readable site map inclusion
- TXT map 或 Markdown hub index
- 相关 cluster 页面的 internal links
- 需要 grounding 的 source/evidence block
- evergreen 页面更新时间

---

## 从 GEOFlow 借鉴了什么

这个 repo 参考了 GEOFlow 的架构思想，但没有引入它的 Laravel CMS stack。

借鉴点：

- generation 之前先建设 source/material library
- task queue state machine
- local publish 与 remote distribution 分离
- target-site Agent / WordPress provider abstraction
- `llms.txt`、sitemap、TXT map、Schema 输出
- access-log 和 AI-crawler analytics

---

## 仓库结构

```text
.
├── SKILL.md
├── README.md
├── LICENSE
├── agents/
│   └── openai.yaml
├── docs/readme/
│   ├── README_en.md
│   ├── README_ja.md
│   ├── README_es.md
│   ├── README_ru.md
│   └── README_pt_BR.md
├── examples/
│   ├── receipt.example.json
│   ├── sources.example.jsonl
│   └── task.example.json
└── references/
    ├── geoflow-patterns.md
    └── openclaw-integration.md
```

---

## 推荐运营节奏

Daily:

1. 先读 workflow receipts，再判断状态。
2. 只把 validated findings 推进 source catalog 或 topic clusters。
3. 对 publish、live QA、patrol 失败项创建 rescue tasks。

Weekly:

1. Review source catalog quality。
2. 把重复问题合并进 topic clusters。
3. 刷新 wiki pages。
4. 检查 visibility analytics。
5. 决定哪些强内容要派生 X posts 或 internal links。


path: agents/openai.yaml
content: interface:
  display_name: "OpenClaw GEO Content Ops"
  short_description: "Operate GEO content assets, targets, artifacts, receipts, and analytics"
  brand_color: "#0F766E"
  default_prompt: "Use $openclaw-geo-content-ops to design or audit our GEO content operations pipeline, including sources, tasks, publish targets, LLM-friendly artifacts, receipts, and analytics."


path: docs/readme/README_en.md
content: # OpenClaw GEO Content Ops

> Languages: [简体中文](../../README.md) | [English](README_en.md) | [日本語](README_ja.md) | [Español](README_es.md) | [Русский](README_ru.md) | [Português (BR)](README_pt_BR.md)

> OpenClaw GEO Content Ops is a lightweight skill and operating model for GEO (Generative Engine Optimization). It connects trusted knowledge sources, topic clusters, content tasks, AI-search writing, SEO/GEO workflow receipts, publication targets, LLM-friendly artifacts, and visibility analytics into one auditable content-asset loop.

[![Skill](https://img.shields.io/badge/OpenClaw-Skill-0F766E)](#quick-start)
[![GEO](https://img.shields.io/badge/GEO-Content%20Ops-blue)](#what-it-does)
[![License](https://img.shields.io/badge/License-MIT-blue.svg)](../../LICENSE)

Released under the [MIT License](../../LICENSE).

---

## What It Does

| Layer | What it manages |
| --- | --- |
| Knowledge sources | Brand docs, product facts, receipts, URLs, customer notes, competitor notes, and wiki pages |
| Topic clusters | Durable question, keyword, entity, comparison, and FAQ maps |
| Content tasks | Briefs that connect reader, core query, source evidence, publish scope, and success signals |
| Writing handoff | Boundary with AI-search writing so each article is answer-first, citeable, and extractable |
| SEO/GEO workflow | Boundary with Hunter/Tony/Peter delivery, publish gates, and receipts |
| Publication targets | ClawLite blog, WordPress REST, static GEO sites, X posts, Feishu docs, and future providers |
| GEO artifacts | `llms.txt`, sitemap, TXT maps, Schema, Open Graph, canonical URLs, and evidence blocks |
| Receipts | Evidence for generation, audit, publish, deploy, live QA, patrol, and analytics |
| Visibility analytics | AI crawler hits, indexing state, sitemap coverage, citation checks, top content, stale pages, and rescue tasks |

---

## Running Structure

```text
knowledge_sources
    ↓
topic_clusters
    ↓
content_tasks
    ↓
AI-search content writing
    ↓
SEO/GEO workflow receipts
    ↓
publication_targets
    ↓
GEO artifacts
    ↓
visibility analytics
    ↓
source/wiki promotion
```

---

## How It Coordinates Skills

| Skill | Owns |
| --- | --- |
| `openclaw-geo-content-ops` | Sources, topics, tasks, targets, artifacts, receipts, analytics |
| `openclaw-seo-geo-workflow` | Daily Hunter/Tony/Peter execution, publish gates, receipts, patrol |
| `ai-search-visibility-content-writing` | Single-page quality, direct answer, entity clarity, citeable structure |
| `claw-wiki` | Readable wiki pages generated from canonical sources |

---

## Quick Start

```bash
mkdir -p ~/.codex/skills
git clone https://github.com/X-RayLuan/openclaw-geo-content-ops.git ~/.codex/skills/openclaw-geo-content-ops
```

```bash
mkdir -p ~/.openclaw/workspace/skills
git clone https://github.com/X-RayLuan/openclaw-geo-content-ops.git ~/.openclaw/workspace/skills/openclaw-geo-content-ops
```

Use:

```text
Use openclaw-geo-content-ops to design this week's GEO content operating plan.
```

---

## Core Contracts

- Source catalog: `examples/sources.example.jsonl`
- Task brief: `examples/task.example.json`
- Receipt contract: `examples/receipt.example.json`
- Integration notes: `references/openclaw-integration.md`
- GEOFlow patterns: `references/geoflow-patterns.md`

Do not claim production publish, indexing, AI crawler visits, rankings, or AI citations without receipts.

---

## License

MIT


path: docs/readme/README_es.md
content: # OpenClaw GEO Content Ops

> Languages: [简体中文](../../README.md) | [English](README_en.md) | [日本語](README_ja.md) | [Español](README_es.md) | [Русский](README_ru.md) | [Português (BR)](README_pt_BR.md)

> OpenClaw GEO Content Ops es una skill ligera y un modelo operativo para GEO (Generative Engine Optimization). Conecta fuentes confiables, topic clusters, tareas de contenido, escritura para AI Search, receipts del workflow SEO/GEO, destinos de publicación, artifacts compatibles con LLM y analytics de visibilidad en un ciclo auditable.

[![Skill](https://img.shields.io/badge/OpenClaw-Skill-0F766E)](#quick-start)
[![GEO](https://img.shields.io/badge/GEO-Content%20Ops-blue)](#what-it-does)
[![License](https://img.shields.io/badge/License-MIT-blue.svg)](../../LICENSE)

Publicado bajo la [MIT License](../../LICENSE).

---

## What It Does

| Layer | Qué gestiona |
| --- | --- |
| Knowledge sources | Documentos de marca, hechos de producto, receipts, URLs, notas de clientes, competidores y wiki |
| Topic clusters | Mapas duraderos de preguntas, keywords, entidades, comparaciones y FAQ |
| Content tasks | Briefs que conectan lector, pregunta, evidencia, alcance de publicación y señales de éxito |
| Writing handoff | Límite con escritura para AI Search: respuesta directa, entidades claras y estructura citable |
| SEO/GEO workflow | Límite con Hunter/Tony/Peter, publish gates, receipts y patrol |
| Publication targets | ClawLite blog, WordPress REST, static GEO sites, X posts, Feishu docs |
| GEO artifacts | `llms.txt`, sitemap, TXT maps, Schema, Open Graph y canonical URLs |
| Receipts | Evidencia de generación, auditoría, publicación, deploy, live QA, patrol y analytics |
| Visibility analytics | AI crawler hits, indexing, citation checks, top content y rescue tasks |

---

## Running Structure

```text
knowledge_sources
    ↓
topic_clusters
    ↓
content_tasks
    ↓
AI-search content writing
    ↓
SEO/GEO workflow receipts
    ↓
publication_targets
    ↓
GEO artifacts
    ↓
visibility analytics
    ↓
source/wiki promotion
```

---

## Quick Start

```bash
mkdir -p ~/.codex/skills
git clone https://github.com/X-RayLuan/openclaw-geo-content-ops.git ~/.codex/skills/openclaw-geo-content-ops
```

```text
Use openclaw-geo-content-ops to design this week's GEO content operating plan.
```

---

## Core Contracts

- Source catalog: `examples/sources.example.jsonl`
- Task brief: `examples/task.example.json`
- Receipt contract: `examples/receipt.example.json`
- Integration notes: `references/openclaw-integration.md`
- GEOFlow patterns: `references/geoflow-patterns.md`

No declares publicación en producción, indexing, AI crawler visits, rankings o AI citations sin receipts.

---

## License

MIT


path: docs/readme/README_ja.md
content: # OpenClaw GEO Content Ops

> Languages: [简体中文](../../README.md) | [English](README_en.md) | [日本語](README_ja.md) | [Español](README_es.md) | [Русский](README_ru.md) | [Português (BR)](README_pt_BR.md)

> OpenClaw GEO Content Ops は、GEO（Generative Engine Optimization）を継続的なコンテンツ資産運用として扱うための軽量 Skill と運用モデルです。信頼できる知識ソース、topic clusters、content tasks、AI Search 向け執筆、SEO/GEO workflow receipts、公開先、LLM-friendly artifacts、visibility analytics をひとつの監査可能なループに接続します。

[![Skill](https://img.shields.io/badge/OpenClaw-Skill-0F766E)](#quick-start)
[![GEO](https://img.shields.io/badge/GEO-Content%20Ops-blue)](#what-it-does)
[![License](https://img.shields.io/badge/License-MIT-blue.svg)](../../LICENSE)

MIT License で公開されています。

---

## What It Does

| Layer | 管理するもの |
| --- | --- |
| Knowledge sources | ブランド文書、製品事実、receipts、URL、顧客メモ、競合メモ、wiki ページ |
| Topic clusters | 質問、キーワード、エンティティ、比較軸、FAQ の長期マップ |
| Content tasks | 読者、核心クエリ、source evidence、公開範囲、成功指標をつなぐ brief |
| Writing handoff | AI Search 向け執筆との境界を明確にし、引用しやすい記事にする |
| SEO/GEO workflow | Hunter/Tony/Peter の実行、publish gates、receipts との境界 |
| Publication targets | ClawLite blog、WordPress REST、static GEO site、X posts、Feishu docs |
| GEO artifacts | `llms.txt`、sitemap、TXT maps、Schema、Open Graph、canonical URLs |
| Receipts | 生成、監査、公開、deploy、live QA、patrol、analytics の証拠 |
| Visibility analytics | AI crawler hits、indexing、citation checks、top content、rescue tasks |

---

## Running Structure

```text
knowledge_sources
    ↓
topic_clusters
    ↓
content_tasks
    ↓
AI-search content writing
    ↓
SEO/GEO workflow receipts
    ↓
publication_targets
    ↓
GEO artifacts
    ↓
visibility analytics
    ↓
source/wiki promotion
```

---

## Quick Start

```bash
mkdir -p ~/.codex/skills
git clone https://github.com/X-RayLuan/openclaw-geo-content-ops.git ~/.codex/skills/openclaw-geo-content-ops
```

```text
Use openclaw-geo-content-ops to design this week's GEO content operating plan.
```

---

## Core Contracts

- Source catalog: `examples/sources.example.jsonl`
- Task brief: `examples/task.example.json`
- Receipt contract: `examples/receipt.example.json`
- Integration notes: `references/openclaw-integration.md`
- GEOFlow patterns: `references/geoflow-patterns.md`

本番公開、indexing、AI crawler visits、ranking、AI citation は receipt なしで主張しないでください。

---

## License

MIT


path: docs/readme/README_pt_BR.md
content: # OpenClaw GEO Content Ops

> Languages: [简体中文](../../README.md) | [English](README_en.md) | [日本語](README_ja.md) | [Español](README_es.md) | [Русский](README_ru.md) | [Português (BR)](README_pt_BR.md)

> OpenClaw GEO Content Ops é uma skill leve e um modelo operacional para GEO (Generative Engine Optimization). Ela conecta fontes confiáveis, topic clusters, tarefas de conteúdo, escrita para AI Search, receipts do workflow SEO/GEO, destinos de publicação, artifacts compatíveis com LLM e analytics de visibilidade em um ciclo auditável.

[![Skill](https://img.shields.io/badge/OpenClaw-Skill-0F766E)](#quick-start)
[![GEO](https://img.shields.io/badge/GEO-Content%20Ops-blue)](#what-it-does)
[![License](https://img.shields.io/badge/License-MIT-blue.svg)](../../LICENSE)

Publicado sob a [MIT License](../../LICENSE).

---

## What It Does

| Layer | O que gerencia |
| --- | --- |
| Knowledge sources | Docs de marca, fatos do produto, receipts, URLs, notas de clientes, concorrentes e wiki |
| Topic clusters | Mapas duráveis de perguntas, keywords, entidades, comparações e FAQ |
| Content tasks | Briefs que conectam leitor, pergunta central, evidência, escopo de publicação e sinais de sucesso |
| Writing handoff | Fronteira com escrita para AI Search: resposta direta, entidades claras e estrutura citável |
| SEO/GEO workflow | Fronteira com Hunter/Tony/Peter, publish gates, receipts e patrol |
| Publication targets | ClawLite blog, WordPress REST, static GEO sites, X posts, Feishu docs |
| GEO artifacts | `llms.txt`, sitemap, TXT maps, Schema, Open Graph e canonical URLs |
| Receipts | Evidência para geração, auditoria, publicação, deploy, live QA, patrol e analytics |
| Visibility analytics | AI crawler hits, indexing, citation checks, top content e rescue tasks |

---

## Running Structure

```text
knowledge_sources
    ↓
topic_clusters
    ↓
content_tasks
    ↓
AI-search content writing
    ↓
SEO/GEO workflow receipts
    ↓
publication_targets
    ↓
GEO artifacts
    ↓
visibility analytics
    ↓
source/wiki promotion
```

---

## Quick Start

```bash
mkdir -p ~/.codex/skills
git clone https://github.com/X-RayLuan/openclaw-geo-content-ops.git ~/.codex/skills/openclaw-geo-content-ops
```

```text
Use openclaw-geo-content-ops to design this week's GEO content operating plan.
```

---

## Core Contracts

- Source catalog: `examples/sources.example.jsonl`
- Task brief: `examples/task.example.json`
- Receipt contract: `examples/receipt.example.json`
- Integration notes: `references/openclaw-integration.md`
- GEOFlow patterns: `references/geoflow-patterns.md`

Não declare publicação em produção, indexing, AI crawler visits, rankings ou AI citations sem receipts.

---

## License

MIT


path: docs/readme/README_ru.md
content: # OpenClaw GEO Content Ops

> Languages: [简体中文](../../README.md) | [English](README_en.md) | [日本語](README_ja.md) | [Español](README_es.md) | [Русский](README_ru.md) | [Português (BR)](README_pt_BR.md)

> OpenClaw GEO Content Ops — это легкий skill и операционная модель для GEO (Generative Engine Optimization). Он связывает надежные источники знаний, topic clusters, задачи контента, AI Search writing, receipts SEO/GEO workflow, цели публикации, LLM-friendly artifacts и visibility analytics в один проверяемый цикл.

[![Skill](https://img.shields.io/badge/OpenClaw-Skill-0F766E)](#quick-start)
[![GEO](https://img.shields.io/badge/GEO-Content%20Ops-blue)](#what-it-does)
[![License](https://img.shields.io/badge/License-MIT-blue.svg)](../../LICENSE)

Проект распространяется по лицензии [MIT](../../LICENSE).

---

## What It Does

| Layer | Что управляет |
| --- | --- |
| Knowledge sources | Документы бренда, факты продукта, receipts, URL, заметки клиентов, конкуренты и wiki |
| Topic clusters | Устойчивые карты вопросов, keywords, entities, сравнений и FAQ |
| Content tasks | Briefs, связывающие читателя, запрос, evidence, publish scope и success signals |
| Writing handoff | Граница с AI Search writing: прямой ответ, ясные entities, цитируемая структура |
| SEO/GEO workflow | Граница с Hunter/Tony/Peter, publish gates, receipts и patrol |
| Publication targets | ClawLite blog, WordPress REST, static GEO sites, X posts, Feishu docs |
| GEO artifacts | `llms.txt`, sitemap, TXT maps, Schema, Open Graph и canonical URLs |
| Receipts | Evidence для generation, audit, publish, deploy, live QA, patrol и analytics |
| Visibility analytics | AI crawler hits, indexing, citation checks, top content и rescue tasks |

---

## Running Structure

```text
knowledge_sources
    ↓
topic_clusters
    ↓
content_tasks
    ↓
AI-search content writing
    ↓
SEO/GEO workflow receipts
    ↓
publication_targets
    ↓
GEO artifacts
    ↓
visibility analytics
    ↓
source/wiki promotion
```

---

## Quick Start

```bash
mkdir -p ~/.codex/skills
git clone https://github.com/X-RayLuan/openclaw-geo-content-ops.git ~/.codex/skills/openclaw-geo-content-ops
```

```text
Use openclaw-geo-content-ops to design this week's GEO content operating plan.
```

---

## Core Contracts

- Source catalog: `examples/sources.example.jsonl`
- Task brief: `examples/task.example.json`
- Receipt contract: `examples/receipt.example.json`
- Integration notes: `references/openclaw-integration.md`
- GEOFlow patterns: `references/geoflow-patterns.md`

Не заявляйте production publish, indexing, AI crawler visits, rankings или AI citations без receipts.

---

## License

MIT


path: examples/receipt.example.json
content: {
  "date": "2026-05-24",
  "taskId": "geo-2026-05-24-openclaw-routing-cost-control",
  "stage": "publish",
  "target": "clawlite_blog",
  "status": "PASS",
  "evidence": {
    "localPath": "delivery/seo-geo/2026-05-24/manifest.json",
    "liveUrl": "https://clawlite.ai/blog/openclaw-routing-cost-control",
    "checkedAt": "2026-05-24T10:00:00+08:00"
  },
  "warnings": [],
  "nextActions": []
}


path: examples/task.example.json
content: {
  "taskId": "geo-2026-05-24-openclaw-routing-cost-control",
  "status": "planned",
  "targetReader": "AI team operator",
  "coreQuery": "How can teams control OpenClaw routing cost without losing reliability?",
  "primaryAnswer": "Use a verified routing policy, receipts, and rollback gates instead of manual model switching.",
  "requiredSources": [
    "clawlite-positioning",
    "keyword-map-wiki"
  ],
  "entities": [
    "OpenClaw",
    "ClawLite"
  ],
  "topicCluster": "routing-cost-control",
  "publishScope": [
    "clawlite_blog",
    "x_post"
  ],
  "geoArtifacts": [
    "schema",
    "sitemap",
    "llms_txt"
  ],
  "successSignals": [
    "live_url",
    "index_check",
    "ai_crawler_log"
  ]
}


path: references/geoflow-patterns.md
content: # GEOFlow Patterns For OpenClaw

Use this reference when translating GEOFlow's architecture into OpenClaw without adopting GEOFlow as a CMS.

## What To Borrow

### 1. Content Engineering Pipeline

GEOFlow's useful pipeline:

```text
knowledge base / materials / prompts
  -> task configuration
  -> queue generation
  -> draft / review / publish
  -> distribution queue
  -> target site artifacts
  -> analytics
```

OpenClaw mapping:

```text
catalogs/sources + topic clusters
  -> Hunter/Tony/factory task manifest
  -> draft + audit receipts
  -> Peter source apply / deploy
  -> target-specific distribution receipts
  -> patrol + visibility analytics
```

### 2. Knowledge Source First

Do not start from keyword volume alone. Require source material that can support a useful answer.

Minimum source fields:

```json
{
  "id": "source-stable-id",
  "type": "product_doc|case_study|faq|competitor|customer_note|web_url",
  "title": "Human readable title",
  "url": "optional URL",
  "owner": "optional owner",
  "capturedAt": "ISO timestamp",
  "trustLevel": "owned|verified|third_party|unverified",
  "summary": "What this source proves",
  "entities": ["OpenClaw"],
  "usableFor": ["cluster-name"]
}
```

### 3. Task State Machine

Keep local generation and public distribution separate:

```text
planned
  -> sourced
  -> drafted
  -> audited
  -> source_published
  -> built
  -> deployed
  -> live_checked
  -> monitored
```

Target-level states:

```text
queued -> sending -> synced
queued -> sending -> failed -> retry_scheduled
skipped
```

This prevents one failed remote target from making the whole article look unpublished.

### 4. Publication Provider Abstraction

Each target should implement the same conceptual interface:

```text
health()
publishArticle(payload)
updateArticle(payload)
deleteOrUnpublish(payload)
syncAssets(payload)
return remoteId, remoteUrl, status, logs
```

Start with:

- `clawlite_blog`
- `wordpress_rest`
- `static_geo_site`
- `x_post`
- `feishu_doc`

Do not mix provider-specific credentials or response bodies into generic task records. Store them under provider metadata and redact secrets in logs.

### 5. GEO Artifact Layer

For each public web target, maintain a target artifact record:

```json
{
  "target": "clawlite_blog",
  "liveUrl": "https://clawlite.ai/blog/slug",
  "canonical": "https://clawlite.ai/blog/slug",
  "sitemapIncluded": true,
  "llmsTxtIncluded": true,
  "txtMapIncluded": true,
  "schemaTypes": ["Article", "FAQPage"],
  "openGraph": true,
  "lastVerifiedAt": "ISO timestamp"
}
```

### 6. Analytics Model

Separate production analytics from visibility analytics:

Production:

- created tasks
- completed drafts
- failed audits
- publish queue count
- deployed pages
- failed targets

Visibility:

- indexed pages
- sitemap/`llms.txt` coverage
- AI crawler hits
- search impressions/clicks when available
- AI citation checks
- top pages by views or mentions
- stale pages and missing internal links

### 7. Daily To Weekly Promotion

Daily findings should land in receipts first. Promote only validated patterns to durable assets:

- daily keyword candidate -> `keywords-master.json`
- recurring question -> `topic-clusters.md`
- verified source -> `catalogs/sources.jsonl`
- failed page -> rescue task
- strong article -> social/X derivative and internal link expansion

## What Not To Borrow

- Full Laravel/PHP CMS unless OpenClaw intentionally wants a second content backend.
- Admin UI assumptions that duplicate existing OpenClaw dashboard work.
- Blind batch generation without source grounding.
- A single "published" boolean for multi-target content.
- SEO/GEO claims without evidence receipts.


path: references/openclaw-integration.md
content: # OpenClaw Integration

This reference explains how `openclaw-geo-content-ops` coordinates existing OpenClaw SEO/GEO assets.

## Skill Boundaries

| Skill | Use it for | Hand off when |
| --- | --- | --- |
| `openclaw-geo-content-ops` | Source catalog, content tasks, publish targets, GEO artifacts, receipts, analytics | A single article needs drafting or today's publish status needs deterministic receipt inspection |
| `openclaw-seo-geo-workflow` | Hunter/Tony/Peter daily workflow, blog factory status, publish/build/live QA, patrol | Durable source catalog or weekly content ops planning is needed |
| `ai-search-visibility-content-writing` | Article or landing page writing/rewrite, answer-first structure, citeable sections, schema hints | The task is source ingestion, distribution, live QA, or analytics |
| `claw-wiki` | Regenerating readable ClawLite wiki pages from canonical source files | Raw sources or receipts need registration first |

## Recommended Local Paths

These paths are workspace conventions, not public repo requirements:

```text
clawlite-brain/catalogs/sources.jsonl
clawlite-brain/wiki/
synthadoc/wiki/
references/clawlite-brand/
references/clawlite-seo/
mission-control/data/
delivery/seo-geo/YYYY-MM-DD/
```

## Daily Loop

1. Read yesterday and today receipts before claiming state.
2. Register valuable new evidence in `clawlite-brain/catalogs/sources.jsonl`.
3. Create or update content tasks with source IDs.
4. Use the writing skill for each article body.
5. Use the SEO/GEO workflow for publish and live QA.
6. Add GEO artifact checks to receipts.
7. Promote durable learning into topic clusters or wiki pages.

## Weekly Loop

1. Review source catalog quality.
2. Consolidate repeated questions into topic clusters.
3. Refresh wiki pages.
4. Inspect visibility analytics.
5. Create rescue tasks for failed or stale pages.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)