Content Distribution

content-distribution

Publishing isn't distribution. The map decides what to write; this makes sure each piece is seen while organic traffic is still compounding. It reads the same workspace, respects the tier, and points its plays at the brand's actual personas — not a generic channel list.

Read first: ../../framework/content-distribution.md (atoms, channel fit, cadence, the honesty rule).

Preconditions

• entity-profile.json (audience + personas drive channel fit) + topical-map.json

(statuses tell published from planned).

• Naming the specific communities/newsletters needs web_search: true (T1). At T0 the

plan proposes channel types + atoms + cadence but not named venues — say so; don't invent subreddits or metrics.

Workflow

1. Build the plan (T0, offline).

`` python ../../scripts/distribution_plan.py --map brands//topical-map.json \ --entity-profile brands//entity-profile.json --brand "" \ --out brands//outreach/distribution-plan.md ` Per node (published first, then core→outer): fitting channels, the repurposing atoms, and a cadence. Priorities/channel fit are derived; the atoms are asserted` formats.

1. Find the real venues (T1, web_search). For the top personas, discover the specific

subreddits, Slack/Discord communities, newsletters, and creators the ICP actually uses. Record each measured + dated with why-relevant. Never assert a community exists without checking; never attach a reach/engagement estimate.

1. Write the distribution plan → brands//outreach/distribution-plan.md:

• Priority-ordered pieces with channels, atoms, cadence.
• The named venues per persona (measured), or an explicit note they weren't looked up

(T0).

• For a product that can demo itself (e.g. an AI video tool), flag the dogfood atom — generate

the short-form asset with the product; the promo and the demo are one.

1. Feed the loop.

• Community questions worth answering → query-network additions via

topical-map-builder.

• A link or citation earned while promoting → hand to link-opportunities /

answer-engine-optimizer.

• Once GSC has data, seo-performance-tracker shows which distributed pieces

actually converted attention to rankings.

Definition of done

• distribution-plan.md written: priority-ordered, channels + atoms + cadence per piece.
• Channels tied to the brand's real personas; venues measured (T1) or explicitly not

looked up (T0). No invented reach numbers, no invented communities.

Grounding ladder

• T0: offline channel types, repurposing atoms, cadence. Useful alone.
• T1 (web_search): + named communities/newsletters/creators for the ICP, measured.
• T2: no paid dependency.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: siddiqss
• Source: siddiqss/semantic-seo-suite
• License: MIT

Install and usage instructions live in the source repository linked above.