# Map of Content — Automating Social Media & SEO with Claude Code

> Source: [How To Fully Automate Social Media & SEO w/ Claude Code](https://www.youtube.com/watch?v=qvnHOc35ngQ) (14:08, single speaker)
> Read [[_AGENT_PRIMER]] first if you want the distilled expert briefing in one document.

---

## 🎯 One-Sentence Thesis

A solo creator using [[tool-claude-code]] inside [[tool-vs-code]] — orchestrating [[tool-arvow]] for SEO blog generation and [[tool-blotato]] for social scheduling — can build a content engine that produces, publishes, and repurposes content end-to-end with minimal human input.

---

## 🏗️ Master Architecture

The pipeline is documented in [[framework-autonomous-content-engine]]. The local setup that hosts it is in [[framework-claude-code-setup]].

Three layers:

1. **Substrate** — [[tool-vs-code]] + a local desktop folder
2. **Orchestrator** — [[tool-claude-code]] holding [[concept-claude-code-skills]]
3. **Executors** — [[tool-arvow]] (writes/publishes) and [[tool-blotato]] (distributes)

Plus [[tool-ahrefs]] as the external scoreboard, and [[entity-org-anthropic]] as the vendor of the orchestrator.

---

## 🧠 Concepts (`concepts/`)

| Note | Role |
|------|------|
| [[concept-claude-code-skills]] | Persistent local "skills" = the AI's long-term memory of your brand. |
| [[concept-rss-to-social-pipeline]] | RSS-feed-triggered repurposing automation. |
| [[concept-ai-technical-seo]] | Tool-handled meta descriptions, alt text, H-tags, internal links. |
| [[contrarian-one-person-content-team]] | The contrarian frame: solo architect beats a traditional team. |

---

## 📢 Claims (`claims/`)

| Note | Speaker Confidence | Independent Assessment |
|------|--------------------|--------------------------|
| [[claim-replace-content-team]] | High | **Partially supported, overstated.** Replaces production, not strategy. |
| [[claim-arvow-seo-optimization]] | High | **Largely supported with nuance.** Specialized tooling improves reliability, not capability. |

---

## 🔧 Frameworks (`frameworks/`)

| Note | What It Covers |
|------|----------------|
| [[framework-claude-code-setup]] | 6 steps to install VS Code, install Claude Code, and open a workspace. |
| [[framework-autonomous-content-engine]] | 7-step master pipeline: research → write → publish → RSS → repurpose → schedule. |

---

## 🧩 Entities (`entities/`)

### Tools
- [[tool-claude-code]] — Anthropic's orchestrator. Lives in VS Code.
- [[tool-vs-code]] — Microsoft's editor; the host environment.
- [[tool-arvow]] — AI SEO blog generator + CMS publisher.
- [[tool-blotato]] — Social media scheduler + visual generator.
- [[tool-ahrefs]] — SEO analytics suite (used as evidence, not in pipeline).

### Organizations
- [[entity-org-anthropic]] — Vendor of Claude Code.

### People
- [[entity-speaker-1]] — Anonymous presenter (sole narrator).

---

## 💬 Quotes (`quotes/`)

- [[quote-claude-code-urgency]] — The urgency hook.
- [[quote-clarifying-questions]] — The 95%-confidence prompt directive (most operationally valuable line in the source).

---

## ✅ Action Items (`action-items/`)

| Note | What You Do |
|------|-------------|
| [[action-setup-local-skill-folder]] | Create a desktop folder; open it in VS Code; *then* prompt Claude. |
| [[action-use-clarifying-questions-prompt]] | Append "ask clarifying questions, one at a time, until 95% confident" to master prompts. |
| [[action-rss-repurposing]] | Point Claude at your RSS feed → auto-generate per-platform social copy → send to Blotato. |

---

## 📋 Prerequisites (`prerequisites/`)

- [[prereq-api-knowledge]] — You must know how to handle API keys.
- [[prereq-brand-assets]] — You must have brand voice + audience + assets ready.

---

## ❓ Open Questions

None recorded in the source. The enrichment overlay raises several validation questions worth tracking:

- Is Claude Code's "skills" terminology a named product feature, or user-managed instruction files? (Verify with [[entity-org-anthropic]] docs.)
- Does Arvow demonstrably outperform a strong human SEO workflow in controlled tests?
- Does Blotato's API reliably schedule at production scale?
- Is the organic traffic growth shown via [[tool-ahrefs]] screenshots attributable to the stack — or to underlying content strategy / brand momentum?

---

## 🗺️ Recommended Reading Order

For a new agent priming on this vault:

1. **[[_AGENT_PRIMER]]** — single-doc distillation.
2. **[[framework-autonomous-content-engine]]** — the master architecture.
3. **[[framework-claude-code-setup]]** — how to actually start.
4. **[[concept-claude-code-skills]]** — the abstraction that makes it scale.
5. **[[claim-replace-content-team]]** — the headline claim with validation.
6. **[[action-use-clarifying-questions-prompt]]** — the highest-leverage technique.
7. Everything else as needed.