The last de-niche slice: recast the 10 sites where the vendor/sector beat (Microsoft|Azure|Copilot|public sector) sat as the PRIVILEGED/default example, varying each to a concrete cross-domain example instead of sterilizing (plugin-is-domain-general — domain comes from user config, never hardcoded). Recast (10): url-processing-templates (news worked-example Copilot->Figma), opportunity-generation (3 headline examples + About block -> varied/ops persona), profile (3 "good example" headlines/impact -> healthcare/e-commerce/support), first-comment-strategy (drop "Microsoft" from research-paper example), poll-strategy-guide (Copilot option -> generic AI assistants), engagement-frameworks (1 of 3 direct-address audiences -> RevOps/SaaS), setup (audience e.g. -> two varied examples), post (invocation e.g. -> SaaS pricing), network-builder (tagline example -> ops/manufacturing), video-scripter (2 filename slugs -> neutral topics). Kept as false positives (would sterilize): content-angles.md (Public Sector is 1 of 6 balanced industry tables + Industry-Agnostic section), outreach.md (Microsoft Build/Ignite/Azure UG = 3 of ~20 varied real conferences), linkedin-growth-playbook (biographical fact in a real case study), the Gemini/Tavily/Perplexity MCP tool-name examples, and the algorithm-signals "Gemini provenance" SSOT citation. AI-as-topic kept (not a niche token; the de-AI/AI-slop mechanic is the plugin's legit subject). Gate scripts/test-runner.sh 87/0/0 (no lint touches these files yet; §17-guard extension to content-planner is the deferred next step). 10 files, 26/26. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RBMKqPSVbvSZHtQ4heM1UY
181 lines
6.5 KiB
Markdown
181 lines
6.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
|
|
|
|
## 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.
|
|
|
|
### 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
|