If you're a developer building a presence on LinkedIn and your impressions suddenly dropped to near-zero, this post might save you weeks of frustration. Here's exactly what happened to me, what didn't work, and the one thing that did.
The Timeline
Week 1: First LinkedIn post ever. Opinionated take on developer skills in the AI era. ~10k impressions, 30+ comments. Solid for a brand new account with barely any connections.
Same week: Published a second post with two external links. Deleted it after a week because it wasn't performing. From the moment I posted those links, every subsequent post got fewer than 50 impressions. Total. Not per hour. Total.
Weeks 2-3: Posted consistently. Tried different topics, formats, times. Paused activity for 48-72 hours multiple times. Switched to comment-only engagement. Nothing changed. Under 50 impressions per post, every time.
Week 3: Contacted support. Got three rounds of copy-paste responses about how the algorithm works. Nobody confirmed or denied whether my account had any flags.
Week 3.5: Filed a formal GDPR Article 15 data access request in the same support thread.
20+ hours later (previous replies had been 30-60 minutes apart): got a response containing this sentence:
"If you experienced any temporary issues previously, they may have been related to normal system checks or short-term technical behavior, which have since been resolved."
Next day: Posted again. 2,000+ impressions on 1,200+ unique members in 9 hours. Normal distribution restored.
What I Ruled Out
- No automation tools, ever
- No policy warnings or content removals from LinkedIn
- No engagement pods
- Comments on other people's posts were visible and received replies
- Could log in, message, connect. Everything worked except post distribution
- LinkedIn Premium (activated during this period) had no effect either way
This wasn't "the algorithm not liking my content." A 99.5% drop that persists for three weeks across all content types, formats, and posting times is a flag on the account, not a content quality issue.
What Support Actually Did
Round 1: Generic template about duplicate accounts and identity verification. Completely unrelated to my question.
Round 2: "Forwarded to another group." Then a full copy-paste about how the LinkedIn algorithm works. Said they "didn't find any technical inconsistencies" but never confirmed whether my account had any restrictions.
Note: "no technical inconsistencies" and "no restrictions" are very different statements. Read support responses carefully for what they don't say.
Round 3: After I filed a GDPR request citing Article 15, Article 22, and LinkedIn Ireland as data controller: 20+ hours of silence, then the "short-term technical behavior which has since been resolved" response.
The funny part? We were both crafting rough replies to each other, mediated by the kindness of each other's LLM.
The GDPR Angle (EU Residents)
If you're in the EU, this is your strongest tool. Here's why it works:
Article 15 of the GDPR gives you the right to access all personal data a company holds on you. This includes automated profiling data.
Article 22 specifically covers automated decision-making that significantly affects you. An algorithm deciding whether to show your content to 10,000 people or 10 people qualifies.
Article 12(3) requires a response within 30 days.
LinkedIn Ireland Unlimited Company is the data controller for all EEA users. Not LinkedIn Corporation in California. LinkedIn Ireland.
Here's the short version for your initial request:
I am an EU resident. Under Article 15 of the GDPR, I request
disclosure of the following personal data:
a) Any flags, restrictions, or classifications applied to my account
b) Any content moderation actions taken on my posts
c) Any automated profiling scores or signals associated with my
account that affect content distribution (including trust scores,
spam scores, content quality scores, or distribution throttling)
d) Meaningful information about the logic involved in automated
decision-making that affects my content's reach, per Article 15(1)(h)
LinkedIn Ireland Unlimited Company, as data controller for EEA users,
is required to respond within 30 days (Article 12(3)).
When they inevitably ignore it (mine was ignored twice), here's the full escalation template that actually worked:
Hi [contact name],
Thank you for your reply. I appreciate the additional detail,
but I need to point out two issues:
1. You did not confirm or deny whether my account has any flags,
restrictions, trust scores, spam classifications, or content
moderation actions applied to it. I'm asking for a direct answer:
does my account have any flags or distribution restrictions,
yes or no?
2. More importantly, my previous message included a formal data
access request under Article 15 of the GDPR. This was not
acknowledged in your response. I will restate it clearly:
FORMAL GDPR DATA ACCESS REQUEST
Article 15, Regulation (EU) 2016/679
I, [your name], EU resident ([your country]), hereby exercise my
right of access under Article 15 of the General Data Protection
Regulation. I also invoke my rights under Article 22 regarding
automated decision-making and profiling.
I request that LinkedIn Ireland Unlimited Company, as the data
controller for EEA users, provide me with the following personal data:
a) Any flags, restrictions, classifications, or labels applied to
my account or profile
b) Any content moderation actions or decisions taken regarding my posts
c) Any automated profiling scores or signals associated with my
account that affect the distribution or visibility of my content
(including but not limited to: trust scores, spam scores, content
quality scores, shadow ban status, or distribution throttling
indicators)
d) Meaningful information about the logic involved in any automated
decision-making that significantly affects my content's reach,
as required by Article 15(1)(h)
LinkedIn is required to respond to this request without undue delay
and no later than 30 days from receipt (Article 12(3)).
If this support channel is not the appropriate place to process GDPR
requests, please direct me to the correct team or data protection
officer immediately. Do not close this case until the GDPR request
has been properly addressed or redirected.
Thank you,
[your name]
This turns a customer service complaint into a legal obligation. First-tier support agents cannot close a ticket with a copy-paste when a formal data access request is sitting in it. It has to go to legal or privacy teams, which is where people with actual access to account-level data sit.
If they don't respond within 30 days: file a complaint with your national data protection authority. In Italy it's the Garante per la protezione dei dati personali. Every EU country has one.
What I Think Happened
Educated guess, not confirmed:
- Post with external links triggered an automated flag. LinkedIn's system classified the account as potentially spammy
- Deleting the post didn't clear the flag. The signal was already recorded (perhaps it even reinforced it)
- The flag suppressed post distribution but left all other features working (comments, messages, profile). This is a "content distribution restriction," not a full shadow ban
- Three weeks of normal behavior didn't auto-clear it
- Multiple 48-72 hour pauses didn't clear it
- Support agents either couldn't see the flag or weren't authorized to discuss it
- GDPR request forced escalation to someone with backend access
- That person found something, cleared it, and the template response called it "short-term technical behavior"
Practical Takeaways
For new LinkedIn accounts:
- Don't post external links until your account has established a posting history. LinkedIn officially says links aren't penalized. Independent research consistently shows 25-60% reach reduction. My experience suggests it can be much worse on new accounts
- If impressions drop 90%+ overnight and stay there, it's probably not your content. It's a flag
- Common workarounds for sharing links: link in the first comment (still risky according to some sources), asking people to DM you or comment a specific word, or using the Premium custom button (paid only)
For EU-based developers:
- GDPR Article 15 is a real tool with real teeth. Use it when support stonewalls you
- Cite LinkedIn Ireland specifically, not LinkedIn Corporation
- Include the 30-day deadline. It changes the urgency
- If they ignore it, restate it in formal legal language. Mine was ignored twice before it worked
For everyone:
- LinkedIn support will copy-paste algorithm explainers at you until you either give up or escalate legally. The system is designed to exhaust you into acceptance
- "No technical inconsistencies" is not the same as "no restrictions." Read support responses carefully for what they don't say
- If your comments are visible but your posts get zero reach, you have a content distribution restriction, not a full account restriction. Support will tell you "your account is fine" because technically it is. Your posts just aren't being shown to anyone
- Don't give up on support replies. Responses in the one-hour range are a waste of tokens. Briefly parse them with AI and craft a reiteration requesting a human review of your account, no matter what they say
The Part That Bothers Me
I'm a senior engineer with 10+ years of experience. I know how to debug systems, read legal documentation, and write formal escalation requests. It still took me three weeks and a GDPR citation to get this resolved.
What happens to someone earlier in their career who doesn't know any of this? They post, get zero engagement, assume their content is bad, and quit. LinkedIn never tells them what happened. Support never investigates. The platform just silently decides they don't exist.
That's a systemic problem, not a content strategy problem.
Has anyone else experienced a similar sudden drop and recovery? Especially interested in hearing from anyone who has filed a GDPR or equivalent data access request with LinkedIn and received a substantive response about automated profiling data.
I wrote a more detailed version of this story on my blog with the full support conversation breakdown.
Drop a comment or reach me directly.
Top comments (0)