fix(linkedin-studio): N21 — scaffold-bånd-redesign + ferskhet-rester (newsletter-guide, first-comment) [skip-docs]
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
This commit is contained in:
parent
e7276cf8bb
commit
885526738c
9 changed files with 100 additions and 38 deletions
|
|
@ -62,6 +62,23 @@ The defensible spine is the **order**, not the multiplier:
|
|||
> The personal-profile **per-post baseline** (~2.0–2.6%) is a *different denominator* from
|
||||
> a format benchmark — never present an account baseline as a carousel rate.
|
||||
|
||||
## Post length (text posts)
|
||||
|
||||
| Claim | Statement | Source | Confidence |
|
||||
|-------|-----------|--------|------------|
|
||||
| Engagement optimum | Median engagement peaks in the **1,301–2,500 character** band (2.61–2.67%, against 2.10% below 400 chars); 2,501–3,000 falls back slightly. **Single vendor, personal profiles, one six-month window** — the defensible part is the direction (substance beats soundbite), not the boundaries. | AuthoredUp (372,126 posts, Sep 2025–Feb 2026) | medium |
|
||||
|
||||
> **On the plugin's own 1,200–1,800 standard band:** it overlaps the measured optimum from
|
||||
> 1,301 up, with its bottom ~100 characters below it, and its ceiling 700 short. Read
|
||||
> 1,301–2,500 as evidence that the shipped ceiling is **conservative, not wrong** — one
|
||||
> vendor's medians over one window is not enough to move an SSOT that every gate enforces
|
||||
> (`hooks/prompts/content-quality-gate.md`). Test a longer post against your own baseline
|
||||
> before concluding anything.
|
||||
>
|
||||
> **Two AuthoredUp sample sizes appear in this file** — 621K (NLP-quality-scored engagement
|
||||
> study) and 372K (this length study). Different studies, different windows; not a
|
||||
> transcription error.
|
||||
|
||||
## External links (in post body)
|
||||
|
||||
| Claim | Statement | Source | Confidence |
|
||||
|
|
@ -188,7 +205,7 @@ source.)
|
|||
|
||||
---
|
||||
|
||||
*Last updated: 2026-07-17 (GR-model correction). Maintained as the single canonical
|
||||
*Last updated: 2026-07-31 (post-length section added). Maintained as the single canonical
|
||||
algorithm statement; cite, do not restate.*
|
||||
|
||||
*Sources (per-claim quality/confidence noted inline): LinkedIn Engineering — "Engineering
|
||||
|
|
@ -197,6 +214,7 @@ research paper, withdrawn 2025-08-23); LinkedIn Engineering — "Leveraging Dwel
|
|||
AI (2025-08-11); Laura Lorenzetti, VP & Exec Editor (2026-05-19); Gyanda Sachdeva, VP
|
||||
Product (2026-02-16); Matt Navarra relaying LinkedIn Sr. Director Product (Aug 2025);
|
||||
Ordinal link-penalty study (900K, p<0.001); Socialinsider (1.3M); Buffer (2M+); Metricool
|
||||
(673K); AuthoredUp (621K, NLP-quality-scored); van der Blom Algorithm Insights 2025 (1.8M);
|
||||
(673K); AuthoredUp (621K, NLP-quality-scored); AuthoredUp post-length study (372,126 posts,
|
||||
Sep 2025–Feb 2026); van der Blom Algorithm Insights 2025 (1.8M);
|
||||
Originality.ai (8,795 posts); Inc. (buzzword editorial). Full provenance: research brief
|
||||
`docs/remediation/research/01-linkedin-algorithm-signals.md`.*
|
||||
|
|
|
|||
|
|
@ -139,17 +139,17 @@ This structure creates positive response by opposing forces and compels the "see
|
|||
**Hook (110-140 chars)**
|
||||
→ Grab attention, create curiosity
|
||||
|
||||
**Context (200-300 chars)**
|
||||
**Context (250-350 chars)**
|
||||
→ Set up the situation/problem/observation
|
||||
→ Why should they care?
|
||||
→ What's at stake?
|
||||
|
||||
**Insight/Argument (400-800 chars)**
|
||||
**Insight/Argument (550-850 chars)**
|
||||
→ Your main point
|
||||
→ Supporting evidence or logic
|
||||
→ This is the "meat" of the post
|
||||
|
||||
**Implication (200-300 chars)**
|
||||
**Implication (250-350 chars)**
|
||||
→ What does this mean?
|
||||
→ Why does it matter?
|
||||
→ Connect to bigger picture
|
||||
|
|
@ -158,6 +158,10 @@ This structure creates positive response by opposing forces and compels the "see
|
|||
→ What should the reader do/think?
|
||||
→ Engagement prompt
|
||||
|
||||
*The five components sum to 1,210-1,790 characters — inside the 1,200-1,800 standard
|
||||
band, so a draft that respects each component band passes the length gate by
|
||||
construction.*
|
||||
|
||||
### The Narrative Arc (For Story-Based Posts)
|
||||
|
||||
**Setup (200 chars)**
|
||||
|
|
@ -183,48 +187,54 @@ This structure creates positive response by opposing forces and compels the "see
|
|||
**CTA (50-100 chars)**
|
||||
→ Engagement prompt
|
||||
|
||||
*Sum: 1,350-1,500 characters — inside the 1,200-1,800 standard band.*
|
||||
|
||||
### The Data-Driven Post (For Research/Statistics)
|
||||
|
||||
**Stat Hook (100 chars)**
|
||||
**Stat Hook (110-140 chars)**
|
||||
→ Lead with the surprising number
|
||||
|
||||
**Context (200 chars)**
|
||||
**Context (250-350 chars)**
|
||||
→ Where this data comes from
|
||||
→ Why it matters
|
||||
|
||||
**Breakdown (500-700 chars)**
|
||||
**Breakdown (550-850 chars)**
|
||||
→ What the data actually means
|
||||
→ Deeper analysis
|
||||
→ Connect to reader's reality
|
||||
|
||||
**Action (200-300 chars)**
|
||||
**Action (250-350 chars)**
|
||||
→ What to do with this information
|
||||
→ Practical takeaways
|
||||
|
||||
**CTA (50-100 chars)**
|
||||
→ Engagement prompt
|
||||
|
||||
*Sum: 1,210-1,790 characters — inside the 1,200-1,800 standard band.*
|
||||
|
||||
### The Contrarian Post (For Challenging Norms)
|
||||
|
||||
**Bold Claim Hook (110 chars)**
|
||||
**Bold Claim Hook (110-140 chars)**
|
||||
→ State the contrarian position clearly
|
||||
|
||||
**Common Wisdom (200 chars)**
|
||||
**Common Wisdom (250-350 chars)**
|
||||
→ Acknowledge what "everyone" thinks
|
||||
→ Show you understand the conventional view
|
||||
|
||||
**The Challenge (400-600 chars)**
|
||||
**The Challenge (550-850 chars)**
|
||||
→ Why the common wisdom fails
|
||||
→ Evidence or logic for your position
|
||||
→ Personal experience or data
|
||||
|
||||
**Alternative View (300-400 chars)**
|
||||
**Alternative View (250-350 chars)**
|
||||
→ What we should do instead
|
||||
→ The better approach
|
||||
|
||||
**CTA (50-100 chars)**
|
||||
→ Invite discussion/disagreement
|
||||
|
||||
*Sum: 1,210-1,790 characters — inside the 1,200-1,800 standard band.*
|
||||
|
||||
## Call-to-Action Frameworks
|
||||
|
||||
CTAs should encourage engagement while feeling natural, not forced.
|
||||
|
|
|
|||
|
|
@ -13,11 +13,26 @@ External links in the post body correlate with lower reach (correlational, ~38%
|
|||
- 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:** Ensures the comment appears at the top before others comment. LinkedIn treats author comments as pinned by default when posted first.
|
||||
**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
|
||||
|
|
|
|||
|
|
@ -6,18 +6,26 @@ LinkedIn Newsletters are a powerful tool for building an owned audience within L
|
|||
|
||||
## When to Launch Your Newsletter
|
||||
|
||||
### Minimum Thresholds
|
||||
### Not a platform gate — a readiness judgment
|
||||
|
||||
- **5,000+ followers** (ensures viable initial subscriber base)
|
||||
**LinkedIn imposes no follower minimum on individual members:** "All LinkedIn members have
|
||||
access to create a newsletter on LinkedIn" (LinkedIn Help, *Newsletters on LinkedIn FAQ*,
|
||||
a517914; company pages have separate access criteria). Everything below is an editorial
|
||||
readiness bar, not a requirement — you *can* launch at any size, the question is whether
|
||||
you should.
|
||||
|
||||
### Readiness signals
|
||||
|
||||
- **An audience large enough that a launch issue lands somewhere** — a few thousand
|
||||
followers is a common working floor, but it is a heuristic, not a threshold
|
||||
- **3+ months of consistent posting** (proven content discipline)
|
||||
- **Clear topical authority** (algorithm recognizes your expertise)
|
||||
- **Reliable content generation system** (can sustain weekly/biweekly publishing)
|
||||
|
||||
### Why Wait Until 5,000+
|
||||
### Why size matters at all
|
||||
|
||||
- Newsletter notifications go to all subscribers (empty newsletters damage credibility)
|
||||
- Every issue notifies every subscriber — thin editions damage credibility at any scale
|
||||
- Lower subscriber counts reduce perceived authority
|
||||
- Algorithm favors newsletters from established creators
|
||||
- Need sufficient content library to repurpose effectively
|
||||
|
||||
### Red Flags You're Not Ready
|
||||
|
|
@ -40,7 +48,11 @@ LinkedIn Newsletters are a powerful tool for building an owned audience within L
|
|||
|
||||
### LinkedIn Newsletters
|
||||
|
||||
- Direct notification to ALL subscribers (inbox + email notification)
|
||||
- Direct notification to ALL subscribers — but **not necessarily by email**: LinkedIn
|
||||
de-duplicates across channels, and "if you receive an in-app or push notification, you
|
||||
should not expect to also receive an email for the same notification" (LinkedIn Help,
|
||||
a517914). Treat the notification as the reliable channel and email as a bonus; do not
|
||||
plan an edition around inbox delivery
|
||||
- Owned audience (subscribers chose to be notified)
|
||||
- **Ideal for:** Deeper dives, comprehensive frameworks, email list building, monetization
|
||||
- Higher commitment from subscribers (they opted in)
|
||||
|
|
@ -278,7 +290,7 @@ When someone engages deeply on a topic:
|
|||
|
||||
| Mistake | Fix |
|
||||
|---------|-----|
|
||||
| Launching too early | Wait until 5,000+ followers and consistent posting habit |
|
||||
| Launching too early | Nothing on the platform stops you — wait for a consistent posting habit and an audience worth notifying |
|
||||
| Inconsistent publishing | Choose sustainable frequency and never skip |
|
||||
| Newsletter as dumping ground for post leftovers | Provide genuine additional value, not reposts |
|
||||
| Over-promoting newsletter in every post | Subtle mentions, maximum 1 per 5-7 posts |
|
||||
|
|
@ -289,4 +301,4 @@ When someone engages deeply on a topic:
|
|||
|
||||
## Bottom Line
|
||||
|
||||
Newsletters are powerful for building owned audience and deepening relationships, but only after establishing consistent posting and reaching 5,000+ followers. Quality and consistency matter more than frequency.
|
||||
Newsletters are powerful for building owned audience and deepening relationships. LinkedIn lets any member start one — the real gate is editorial: a consistent posting habit, a clear topic, and enough content capacity to sustain the cadence. Quality and consistency matter more than frequency.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue