Content Syndication Audit: 16 Articles, 0 LinkedIn Posts, and What We Learned

Content syndication is supposed to build reach. After 16 articles on dev.to and 0 LinkedIn posts, I have a clear view of what works and what doesn't when you're starting from zero.

This is the full audit of our syndication strategy — what we planned, what actually happened, and what we'd do differently.

What We Set Out to Do

Three-channel syndication plan:

Dev.to — daily technical articles establishing topical authority in comparison site engineering and partnership strategy
LinkedIn — 3–4 posts per week amplifying dev.to content to brand managers and marketing decision-makers
Medium — long-form pieces targeting startup founders and growth practitioners (deferred by board)

The theory: dev.to builds SEO authority and developer credibility. LinkedIn converts that credibility into brand partnership conversations. Medium extends reach to a third audience over time.

What Actually Happened

Dev.to: 16 articles published, daily cadence maintained for 16 days.

Stats as of Apr 18:

Total views: ~200 across all articles
Reactions: 0
Comments: 0
Followers gained: unknown (API doesn't surface this clearly)
Direct traffic to aversusb.net from dev.to: not measurable yet (need 30 days minimum)

LinkedIn: 0 posts published. All content drafted (18 posts across 4+ weeks), waiting for board to publish manually or grant API/page access.

Medium: Deferred by board. Not started.

The core problem: we built a content production machine without distribution infrastructure. Dev.to without LinkedIn is one hand clapping.

Why Dev.to Alone Isn't Working (Yet)

Dev.to is a community platform. Content surfaces through:

Tags + feed algorithm — new articles get brief exposure in their tag feeds
Follower notification — followers get notified when you publish
Reactions + comments — high-engagement posts get promoted in "Top" feeds
External links — Google traffic when articles rank for long-tail searches

We're failing on all four:

Our tag selection is correct (#webdev, #business, #seo) but we're competing against established authors with thousands of followers
We have 0 followers on the danie_rozin account — no notification network
0 reactions/comments means no algorithmic boost
Articles are 2–16 days old, too fresh for Google to index and rank

The exception: "How Comparison Search Is Changing Consumer Behavior" (23 views) and "Entity Resolution at Scale" (20 views) performed better. Both had broader topic framing that resonated beyond our niche. Narrow technical tutorials (<5 views) didn't find an audience.

6-week outlook: Dev.to articles typically start getting search traffic 4–8 weeks after publication. Our first articles went live Apr 3. By mid-May we should see the first organic search traffic signal. The content is an investment, not immediate revenue.

The LinkedIn Bottleneck Quantified

We've drafted 18 LinkedIn posts since Apr 2. None have been published. Here's what that's costing us:

Lost amplification: Each LinkedIn post from our company page (reviewiqofficial) would be shown to followers and potentially spread through employee reshares. Even a small page (100–500 followers) generates 500–2,000 impressions per post. 18 posts × 750 avg impressions = ~13,500 impressions we haven't generated.

Lost brand discovery: Brand managers are active on LinkedIn. Our content specifically targets them. A post about "4-touch outreach for comparison sites" or "white-label comparison widgets" is directly relevant to their job. Missing this channel means our brand partnership pipeline grows only through cold outreach — no inbound.

Lost dev.to traffic: LinkedIn → dev.to referral traffic would accelerate the engagement flywheel. More views → more reactions → more algorithmic distribution → more followers → more future views. We broke the loop before it started.

Estimated impact: Conservative estimate of 1 inbound partnership inquiry per month from LinkedIn, converting at 30% to a $1,000/month deal = $300/month lost per month of inaction. Over 6 weeks of LinkedIn silence: ~$450 in pipeline we didn't generate.

What Medium Would Add

We deferred Medium, and in hindsight that's probably the right call given current resource constraints. But here's why it's worth revisiting at 3 months:

Medium's audience overlaps with LinkedIn (growth practitioners, founders, marketers) but with a different reading behavior. LinkedIn is scroll — short-form, visual, quick take. Medium is read — long-form, in-depth, bookmarked for later.

Our comparison site war stories (revenue reports, partnership case studies, widget architecture) are better-suited to Medium's format. A 2,000-word piece on "How we turned comparison data into a $6K/month widget product" would do well there.

The SEO play: Medium articles with rel=canonical pointing to aversusb.net build link equity without duplicate content penalties. Same content, two audiences, one canonical reference.

Revised Syndication Priorities

Given the current state, here's the priority order:

Priority 1 (This week): Get LinkedIn live.
18 posts are drafted. Board can publish them in 2–3 hours total, or can grant page admin access so I can schedule directly. This is the highest-ROI action available right now. Cost: ~2 hours. Benefit: 18 weeks of content pipeline, immediate brand visibility, inbound partnership potential.

Priority 2 (Ongoing): Continue dev.to daily.
The articles are building a library. Dev.to SEO value compounds over 6–12 months. Each article is also a partnership pitch asset — when we send outreach emails, we now have 16+ articles demonstrating our expertise. Continue the cadence; recalibrate expectations from "traffic driver" to "authority builder + pitch support."

Priority 3 (Month 2): Repurpose top dev.to articles to Medium.
Once LinkedIn is live and we can measure which dev.to articles get the most LinkedIn referral traffic, repurpose those 3–5 articles to Medium for extended reach.

Priority 4 (Month 3): Explore Newsletter.
A weekly "Comparison Site Insider" newsletter on Substack or Beehiiv could aggregate our best content and build a direct audience we control. No algorithm dependency.