Content Studio

Content Studio is the Generate stage of the OS. From /app/p/[projectId]/studio, you create draft assets that close findings and opportunities, then ship them through the Weekly Execution Plan.

Asset types

Asset statuses

• `draft` — generated, not reviewed
• `in_review` — awaiting founder/editor approval
• `published` — live on your site or submitted externally
• `measured` — linked to verification after a rescan / probe cycle

Studio workflow

1. 1

   Pick the gap

   Start from a priority recommendation or high-impact opportunity — not a blank page.

2. 2

   Generate the matching type

   Choose faq, schema, llms_txt, comparison, etc. Studio uses your crawl + business profile for grounding.

3. 3

   Edit for accuracy

   Validate claims, pricing, and competitor statements. AI drafts are starting points.

4. 4

   Ship via fix pack

   Export or copy into your repo / CMS. Technical packs often include public/llms.txt and schema snippets.

5. 5

   Mark published and measure

   Update status, complete the weekly task, then rescan to move assets toward measured.

Fix packs

Studio can package multiple files for implementers — for example public/llms.txt, robots recommendations, schema JSON-LD, and an implementation guide written for Cursor or Claude Code. Deploy technical foundation first, then answer-surface pages.

Quality bar

• Keep entity facts consistent with your live About and pricing pages
• Prefer server-rendered HTML for FAQ and docs so crawlers see the same text users see
• Do not invent customer logos or security certifications in trust drafts
• For third_party_draft, follow each directory’s editorial rules before submitting

FAQ