Scanner Signals 4 min read August 2026

Do links in posts kill reach?

Direct Answer

There is no explicit link penalty in the open-source code. However, outbound links reduce reach indirectly: users who click external links leave the X app immediately, crushing continuous dwell time, while reducing in-app replies and copy-link shares. Furthermore, unverified or suspicious URLs trigger safety screens that drop posts entirely.

What People Get Wrong

Myth: "Putting the link in the main post triggers an automatic hidden blacklist penalty."
Reality: The open-source code includes positive terms for link clicks. The reach drop is behavioral (users bounce instead of engaging on X).
Myth: "Putting the link in the first reply always gives 10x more reach."
Reality: If the main post doesn’t generate strong standalone dwell and conversation, the reply will never be seen anyway.

What the Code & Rules Actually Say

visibility-filtering/rules/registry.rs
Referenced Rules & Signals:
• URL Safety Filtering Gate
• Continuous Dwell Time Scoring Parameter
• Share via Copy Link Weight

An external link post that causes users to leave the app forfeits massive dwell and sharing bonuses, while risking safety filter drops if URLs redirect.

Surgical Action Plan

1 Write comprehensive, standalone value in the main post so users dwell for 15+ seconds.
2 Only include links when they are genuinely essential to the post context.
3 Avoid URL shorteners (bit.ly, tinyurl) that trigger security screeners; use clean canonical domains.
4 Purge old broken link tweets from your archive using XPurge.
Where this shows up in XPurge

XPurge flags tweets with multiple URLs, external affiliate redirects, or dead links across your entire archive. Note: Excessive Links is an XPurge scanner heuristic.

Clean Link Posts →
Interactive System Blueprint Gamified Course

Want the visual mental model? Explore the full 15-module interactive architecture in Algo Map to earn XP and master how this rule operates in production.

Open Algo Map →

Related Questions