원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
linkedin-growth
The LinkedIn personal-profile growth engine — the profile as a landing page, what to post and how often, strategic commenting on target accounts, the golden hour, newsletters/video, and connections vs followers. The agent drafts posts + comment copy and designs the system; a human does the live commenting/connecting; scheduling-and-queue → WoopSocial publishes the posts. Complements linkedin-post-writer (the single-post craft) and linkedin-company-pages (the page).
The POV: dwell + comments, on a personal profile
LinkedIn's algorithm rewards dwell time (people actually reading) and early, meaningful comments — likes barely move distribution, and engagement bait is down-ranked. The feed is structurally tilted to people, not logos (personal profiles get ~65% of feed allocation; pages ~1–5%), external links in the body suppress reach (put them in the first comment), and posts now have a long shelf life via suggested feeds — a good post travels for days or weeks. The cheapest growth lever isn't posting more: it's thoughtful comments on bigger accounts in your niche, which put your name in front of their audience daily. And in a feed where ~half the long posts are AI-written, a specific, lived, first-person POV is the differentiator — not volume.
Read these first
- brand-profile — positioning, audience, non-negotiables.
- voice-builder — so posts and comments sound like one credible human.
The framework: LADDER
(Depth: references/the-ladder-framework.md.)
- L — Landing-page profile: headline = value proposition (not job title); About opens with the
3 visible lines; Featured = the CTA; Follow-primary once inbound outpaces outbound. Every post's job ends at a profile visit — the profile converts it. → profile-optimization.
- A — Author for dwell: win the "…see more" tap, format for the read, mix text / document
carousel / native video / newsletter; link in the first comment. → linkedin-post-writer.
- D — Deploy strategic comments: 5–10 substantive comments/day on target accounts in the niche —
the afterburner. A comment is content, not a courtesy. → reply-and-comment-writer.
- D — Drive the golden hour: first 60–90 min decides reach; post in the audience window, reply
to every comment, comment around your own post time. Max 1 post/day, 3–5/week.
- E — Expand with native surfaces: newsletter (notification + email push), native video (the
2026 push), audio events; SSI as a directional health check, never the goal.
- R — Relationships & network hygiene: connections (capped, ~100 invites/week) vs followers
(unlimited); no-pitch invites; DMs warm, not pitch-slaps. → social-selling-and-dm.
The reality (verify-quarterly)
Feed allocation and reach decline, dwell + comment weighting, the golden hour, link suppression, format hierarchy (carousels/video/text), the see-more cutoff, creator mode's retirement, connection caps, newsletters, SSI, the AI-content flood, cadence: references/linkedin-2026-reality.md. Post types + the commenting playbook + worked examples: references/comment-and-post-recipes.md.
Honest scope (never violate)
- The engagement core is human — the agent drafts posts, comment copy, invite notes, and DM
openers; a human posts the live comments, sends invites, and holds the conversations. No auto-commenting, no auto-connect tooling (a restriction risk on LinkedIn specifically).
- WoopSocial schedules the posts (text + media + optional link; native document carousels,
polls, newsletters, and audio events are posted/run natively). No update → delete + recreate. For link-in-first-comment, the agent supplies post + comment; the pair is posted by tool/human.
- No analytics in WoopSocial → read native LinkedIn analytics (impressions, members reached,
profile viewers, followers) and SSI as a directional check. Never fabricate metrics.
- No engagement bait, pods, mass-tagging, bought followers, or broetry theatre — down-ranked by
the algorithm and quietly judged by the exact professionals you're trying to reach. (Scope, distinctions + connections: references/scope-and-connections.md.)
Distinct from its siblings (route correctly)
linkedin-growth (this) = the PERSONAL-profile growth system (profile, cadence, commenting, golden hour, features, network) · linkedin-post-writer = how to write one post well · linkedin-company-pages = the page strategy + employee advocacy (advocates' personal posting routes back here) · reply-and-comment-writer = drafting the comments/replies themselves · engagement-routine = the recurring daily engagement block · social-strategy = the cross-platform plan.
Where this connects
Reads first: brand-profile, voice-builder. Post craft: linkedin-post-writer, hook-writer, carousel-writer (document-carousel slides), talking-head-and-piece-to-camera (native video). Profile: profile-optimization. Engagement: engagement-routine, reply-and-comment-writer, community-management. Discovery: social-seo (headline/About keywords), ai-search-optimization (LinkedIn is a B2B AI-answer source), trend-jacking. Pipeline: social-selling-and-dm, lead-magnets-and-funnels; long-form owned channel: email-and-newsletter. Plan/measure: social-strategy, goals-and-kpis, analytics-and-reporting (native LinkedIn analytics). Publish: scheduling-and-queue → WoopSocial (posts; live comments/invites/DMs are human).
Definition of done
A profile audited as a landing page (headline = value prop, Featured = CTA, Follow-primary decision made); a 3–5 posts/week plan, max 1/day, with links in the first comment and format mix mapped to dwell; a named list of 10–20 target accounts with a 5–10 comments/day playbook (drafted by the agent, posted by a human); a golden-hour routine (audience window, reply-to-every-comment); native surfaces decided deliberately (newsletter yes/no, video cadence); connection-request hygiene with no-pitch invite copy; posts routed to scheduling-and-queue → WoopSocial with live engagement flagged human; metrics from native LinkedIn analytics + SSI directionally; no bait/pods/bought followers/ broetry; correctly distinguished from linkedin-post-writer and linkedin-company-pages.
