Del 1 — scaffold-bånd (KTG-beslutning: behold målbåndet, utvid komponentene). Komponentsummen var 960–1 640 mot målbåndet 1 200–1 800: en skjelett-konform draft kunne lande under gulvet og nådde aldri taket. Nye bånd — Context 250–350, Insight 550–850, Implication 250–350 (Hook 110–140 og CTA 50–100 uendret) — summerer til 1 210–1 790, altså INNI 1 200–1 800. Skjelett-konform er nå gate-konform per konstruksjon. Målbåndet 1 200–1 800 er uendret overalt; hooks/prompts/content-quality-gate.md (den kanoniske gaten) er ikke rørt. Alternativet — å heve taket per AuthoredUp D-4 — ville krevd 25 filer / 40 linjer inkl. gate-prompten, begge skills, quality-scorecard, config-malen og brain-fiksturen. Skjelettet fantes i seks kopier, alle rettet på KTG-go: commands/post.md, commands/batch.md, commands/pipeline.md, references/engagement-frameworks.md, agents/content-optimizer.md, skills/linkedin-content-creation/SKILL.md. De tre siste lå utenfor planens scope, men to av dem var internt selvmotsigende på én linje (overskrift 1 200–1 800 over komponenter som summerte til 960–1 640), og engagement-frameworks.md er nettopp fila post.md/pipeline.md instruerer modellen om å LESE for strukturen. Nabofunn tatt med på KTG-go: post.md:95 ga «Personal stories → 1 000–1 400», som motsa post.md:136s egen gate. Kald-review R2a MAJOR — nå 1 200–1 800. D-4 inn i kanonfila: ny «Post length»-seksjon i references/algorithm-signals-reference.md med AuthoredUp-optimumet 1 301–2 500 (372 126 poster, sep 2025–feb 2026), merket single-vendor/ett vindu, med eksplisitt note om at datapunktet gjør det shippede taket konservativt — ikke feil — og at de to AuthoredUp-N-ene i fila (621K vs 372K) er ulike studier. Kilde verifisert mot primærkilden, ikke overført fra planen. Del 2 — ferskhet-rester (begge påstander verifisert mot LinkedIn Help): - D-6 newsletter-strategy-guide.md: «5 000+ følgere» framstilt som terskel er feil — «All LinkedIn members have access to create a newsletter on LinkedIn» (a517914). Omskrevet til redaksjonell modenhetsvurdering (også i Mistakes-tabellen og Bottom Line). E-post er ikke garantert: LinkedIn de-dupliserer på tvers av kanaler — «if you receive an in-app or push notification, you should not expect to also receive an email for the same notification» (a517914). Bringer referansefila i tråd med newsletter.md:2384. Fjernet samtidig den ukildede «Algorithm favors newsletters from established creators» i den omskrevne blokka. - D-7 first-comment-strategy.md: «pinned by default» er uverifisert og feil — pinning er en eksplisitt forfatterhandling (a524166), og standard kommentarsortering er algoritmisk. Lagt til «What this file does not claim»- avsnitt som speiler kanonfilas «contested»/low-confidence-epistemikk. Scope 3 (KTG-go, amend): references/engagement-frameworks.md har FIRE skjeletter, ikke ett. To til brot gulvet i malbandet — Data-Driven Post (1 050-1 400) og Contrarian Post (1 060-1 410) — og er lagt om til samme komponentprofil som Standard, sum 1 210-1 790. Narrative Arc (1 350-1 500) la allerede inni og star urort; alle tre har na en eksplisitt sum-linje. Fila er den post.md:104 sender modellen til for «story structures», sa a sertifisere den som fikset med to odelagte skjeletter igjen ville vaert usant. SUPERSEDED og ikke gjeninnført: gammel B §S6 Del 2 pkt 1 (first-comment −5/−10 %-tall, pods-eskalering, 360Brew-fotnote). Verifisering: bånd-summen ligger inni målbåndet i alle seks kopier av standard-skjelettet og i alle fire skjelettene i engagement-frameworks.md (grep-bevis, 0 gjenværende 200-300/400-800) · D-6/D-7 omformulert (0 treff på «5,000+ followers» / «pinned by default» / «inbox + email») · alle ti suiter grønne, alle floors uendret: test-runner 270/0 (269 assertions >= floor 251) · trends 300/0 · analytics 202/0 · hooks 191/0 · brain 134/0 · editions 72/0 · render 63/0 · specifics-bank 45/0 · tests 35/0 · contract-gate 33/0. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LhF1H7ctT5Fk8KkoCQpe5n
196 lines
7.5 KiB
Markdown
196 lines
7.5 KiB
Markdown
# First Comment Strategy
|
|
|
|
Your first comment is a strategic tool, not an afterthought. Used correctly, it extends your post's value without the lower-reach correlation of body links. Used poorly, it looks like spam.
|
|
|
|
## Why First Comments Matter
|
|
|
|
External links in the post body correlate with lower reach (correlational, ~38% in 2026; LinkedIn denies an intentional penalty — see `references/algorithm-signals-reference.md`). A first comment is a common hedge — but lead with standalone value either way; it's much more than a link dump.
|
|
|
|
**First comment benefits:**
|
|
- Avoids the body-link reach correlation while still providing resources
|
|
- Adds a second engagement surface (people reply to comments)
|
|
- Signals to the algorithm that the post is generating conversation
|
|
- Lets you add context that didn't fit the post's character limit
|
|
- Creates a natural CTA without cluttering the main post
|
|
|
|
### What this file does *not* claim
|
|
|
|
The canonical reference rates the first-comment tactic **"neither a magic fix nor a
|
|
confirmed penalty — contested"**, at *low* confidence — practitioner heuristic, no large-N
|
|
primary source (`references/algorithm-signals-reference.md`). Nothing below upgrades that.
|
|
Specifically, this plugin does **not** assert:
|
|
|
|
- that a link in a comment carries a measured reach cost (no primary source either way)
|
|
- that author comments are auto-pinned or auto-promoted (they are not — pinning is manual)
|
|
- any percentage figure for what a first comment gains or costs you
|
|
|
|
Treat every timing and placement rule here as a hypothesis to test against your own
|
|
baseline, not a mechanic to optimize against. The one durable claim is the body-link
|
|
correlation itself, and even that is a correlation.
|
|
|
|
## Timing Strategy
|
|
|
|
### Immediate (within 60 seconds)
|
|
**Best for:** Link-sharing, resource lists, CTA
|
|
**Why:** Being first gives the comment the best odds of sitting at the top before others arrive. **There is no automatic pinning** — LinkedIn documents pinning as an explicit action the post author takes from the comment's three-dot menu (LinkedIn Help, a524166), and default comment ordering is algorithmic ("Most relevant"), not chronological. If the comment must stay on top, pin it yourself.
|
|
|
|
### Delayed (15-30 minutes)
|
|
**Best for:** Engagement boost, conversation starter, hot take
|
|
**Why:** Adds a new engagement signal during the critical first-hour window. The algorithm re-evaluates distribution when new activity appears.
|
|
|
|
### Strategic Delay (1-2 hours)
|
|
**Best for:** Follow-up data, poll results teaser, additional perspective
|
|
**Why:** Gives the post time to gain organic engagement first, then re-ignites distribution with fresh activity.
|
|
|
|
**Rule of thumb:** If the comment contains a link or resource, post immediately. If it's a conversation starter or additional perspective, delay 15-30 minutes.
|
|
|
|
## First Comment Templates
|
|
|
|
### 1. Link Sharing
|
|
**When:** You reference an article, tool, or resource in the post
|
|
**Template:**
|
|
```
|
|
Here's the [resource type] I mentioned:
|
|
[URL]
|
|
|
|
Key takeaway: [1-sentence summary of why it's worth clicking]
|
|
```
|
|
|
|
**Example:**
|
|
```
|
|
Here's the research paper I mentioned:
|
|
[URL]
|
|
|
|
Key takeaway: They found that AI assistants improve developer productivity by 26% — but only when the developer already understands the fundamentals.
|
|
```
|
|
|
|
### 2. Extra Context
|
|
**When:** Your post makes a bold claim that needs nuance
|
|
**Template:**
|
|
```
|
|
Some context that didn't fit the post:
|
|
|
|
[2-3 bullet points with additional detail, data, or caveats]
|
|
|
|
What's your experience with this?
|
|
```
|
|
|
|
**Example:**
|
|
```
|
|
Some context that didn't fit the post:
|
|
|
|
- This pattern works best for teams of 5-15 people
|
|
- We tested it over 6 months with 3 different departments
|
|
- The 40% improvement was measured in deployment frequency, not lines of code
|
|
|
|
What's your experience with this?
|
|
```
|
|
|
|
### 3. Resource List
|
|
**When:** You want to provide multiple references without cluttering the post
|
|
**Template:**
|
|
```
|
|
Resources if you want to go deeper:
|
|
|
|
1. [Resource name] — [1-line description]
|
|
2. [Resource name] — [1-line description]
|
|
3. [Resource name] — [1-line description]
|
|
|
|
Which of these resonates most? I can elaborate.
|
|
```
|
|
|
|
### 4. Call to Action
|
|
**When:** Your post is educational and you want to drive a specific action
|
|
**Template:**
|
|
```
|
|
If this resonated, here's what I'd suggest:
|
|
|
|
1. [Specific first step]
|
|
2. [Follow-up action]
|
|
3. [Where to learn more or connect]
|
|
|
|
DM me if you want [specific offer — template, checklist, conversation].
|
|
```
|
|
|
|
### 5. Contrarian Addition
|
|
**When:** You want to add a nuanced take that would weaken the post's hook
|
|
**Template:**
|
|
```
|
|
One thing I deliberately left out of the post:
|
|
|
|
[Counterpoint or caveat that adds depth]
|
|
|
|
This doesn't invalidate the main point, but it's worth knowing if you're [specific context].
|
|
```
|
|
|
|
### 6. Behind-the-Scenes
|
|
**When:** You share a lesson or result and want to add the messy reality
|
|
**Template:**
|
|
```
|
|
What I didn't mention in the post:
|
|
|
|
[The failure, struggle, or unexpected twist that preceded the lesson]
|
|
|
|
The polished version makes it sound easy. It wasn't.
|
|
```
|
|
|
|
### 7. Question Redirect
|
|
**When:** You want to steer the conversation toward a specific topic
|
|
**Template:**
|
|
```
|
|
Curious about something:
|
|
|
|
[Specific question that narrows the discussion to your expertise area]
|
|
|
|
I'll share my take once I've heard a few perspectives.
|
|
```
|
|
|
|
## Self-Comment as Engagement Boost
|
|
|
|
Commenting on your own post is not just for adding links. Strategic self-comments can:
|
|
|
|
1. **Re-ignite distribution** — A new comment triggers the algorithm to re-evaluate the post
|
|
2. **Model the conversation** — Your comment style sets the tone for how others respond
|
|
3. **Add social proof** — Responding to early commenters shows you're present and engaged
|
|
4. **Extend reach window** — Comments in the 2-4 hour window can extend the post's active distribution
|
|
|
|
### Self-Comment Timing Sequence
|
|
|
|
| Time | Action | Purpose |
|
|
|------|--------|---------|
|
|
| 0 min | Post goes live | — |
|
|
| 0-1 min | First comment (if link/resource) | Avoid body-link reach hit |
|
|
| 15-30 min | Reply to first 3-5 commenters | Build early engagement momentum |
|
|
| 1-2 hours | Add additional perspective or data | Re-ignite algorithm distribution |
|
|
| 4-6 hours | Respond to remaining comments | Maintain conversation signal |
|
|
|
|
## What NOT to Put in First Comments
|
|
|
|
- **"Link in comments"** in the post body — LinkedIn recognizes this phrase and may still suppress reach
|
|
- **Multiple links** — One link per comment. More looks like spam
|
|
- **Self-promotional CTAs on every post** — Reserve for 1 in 5 posts maximum (90/10 rule)
|
|
- **Generic comments** — "Thanks for reading!" adds no value
|
|
- **Hashtags** — Put these in the post body, not the comment
|
|
|
|
## First Comment for Different Post Types
|
|
|
|
| Post Type | First Comment Strategy | Timing |
|
|
|-----------|----------------------|--------|
|
|
| Educational | Resource link or deeper context | Immediate |
|
|
| Story/Personal | Behind-the-scenes addition | 15-30 min delay |
|
|
| Opinion/Hot take | Nuanced caveat or data | Immediate |
|
|
| Question post | Your own answer to model responses | 30 min delay |
|
|
| Carousel | Summary or "which slide resonated?" | Immediate |
|
|
| Poll | "Here's why I'm asking..." context | Immediate |
|
|
| Quick post | Skip first comment (keep it pure) | N/A |
|
|
|
|
## Quality Checklist
|
|
|
|
Before posting your first comment, verify:
|
|
|
|
- [ ] It adds genuine value (not just "link below")
|
|
- [ ] It's 2-5 lines maximum (comments aren't posts)
|
|
- [ ] It has a conversational element (question or invitation)
|
|
- [ ] It doesn't repeat what's already in the post
|
|
- [ ] It doesn't contain "link in comments" phrasing
|
|
- [ ] Links are relevant, not self-promotional spam
|