BlogGrowth

How the X algorithm actually works: the voice-first reading of the weights

The X algorithm filters 500M daily posts to 1,500 ranked candidates using a weighted engagement score. The standard advice is to game the weights. The voice-first reading is that the weights amplify whatever voice you bring. Here's what the published weights mean for voice-first creators.

· 8 min read

The X algorithm is documented and unsealed. It filters roughly 500 million daily posts down to a personalized 1,500 per user, ranks them with a weighted engagement-probability score, and serves the top results. The published weights are specific. Replies count 13.5x. Author-engaged replies count 75x. Reposts count 20x. Likes and bookmarks count around 30x. Verification adds a 4x follower multiplier and 2x general multiplier. Reports cost 369x. Negative feedback costs 74x. Hashtag-heavy posts get a 1.7x deboost. The decay half-life is 360 minutes.

Standard advice reads these weights as a checklist to game. Get verified, reply to your own comments to trigger the 75x author-reply weight, avoid hashtags, post during peak hours, push for the 2-minute engagement window. All technically correct. All voice-blind. The algorithm amplifies whatever's underneath. If what's underneath is a voice that gets people back to your profile, the weights produce compounding reach. If what's underneath is category-default content, the weights produce marginal incremental impressions on posts that don't convert. The math is the same; the underlying asset isn't.

What the weights actually reward, voice-first

The replies multiplier is the largest non-penalty weight in the published table. 13.5x for replies, 75x if the author engages back. The implication for voice-first creators is that voice-rich replies on bigger accounts are the single highest-leverage move on the platform. A 100-word substantive reply to a 1M-follower account that gets author-engaged is worth more in the ranking score than 5 of your own original posts at average distribution. The voice-first reply strategy is the playbook for what that actually looks like in practice: 5 to 10 voice-rich replies a day, not 30.

The likes/bookmarks weight rewards content that prompts saving for later. Bookmarks are the strongest privacy-respecting signal that your content has reference value, and the algorithm reads them at ~30x. Voice-rich evergreen posts pick up bookmarks for weeks; viral hot takes don't. Twitter bookmarks as voice-research infrastructure covers the inverse half of this (what to bookmark from others). What matters for distribution is the inbound: bookmarks-per-impression is a cleaner voice-fit signal than likes-per-impression.

The penalties are bigger than the boosts. Voice protects you here.

Read the published weights again with the negatives in mind. Reports cost 369x. Negative feedback costs 74x. Offensive-language detection costs 10x. Unknown language costs 20x. The single largest factor in the ranking is what triggers a report, and reports are largely a function of writing register. Drama-bait, contrarian-for-its-own-sake, and category-default outrage take ride the same algorithm but accumulate negative-feedback signal as they scale. Voice-first creators in their actual register rarely trigger reports because they're not performing on top of their voice; the natural-register content sits inside the writer's category-norms and doesn't read as inflammatory to in-category readers.

The hashtag deboost (1.7x) and the offensive-language deboost (10x) are both surface-level pattern matches. Voice-first creators almost never hit these because the patterns that trigger them are pattern-match content (hashtag spam, ALL-CAPS rage-tweeting) that the writing voice would naturally avoid. The penalties are bigger threats to template-driven accounts than to voice-first accounts.

The 360-minute decay and why voice-rich evergreen is the cheat code

Every post loses ~50% of its ranking weight every 6 hours. After 24 hours, the post is functionally dead in the timeline algorithm. The exception is content that keeps picking up engagement (replies, bookmarks, quote-tweets) past the initial window. Voice-rich evergreen posts get re-surfaced for weeks via inbound interactions that the algorithm reads as continued relevance. Hot-take posts get a 6-hour spike and then disappear. The decay function structurally rewards content that has more than 24 hours of useful life, and voice-rich evergreen is what produces it.

The implication for posting cadence: 3 voice-rich posts a week that get re-surfaced over weeks outperform 21 hot-take posts a week that each die in 6 hours. The ranking math says so. What compounds versus what looks like it does covers the broader version of this argument.

Verification (4x followers, 2x general) as a small modifier, not the lever

Premium gives a 4x multiplier to follower distribution and 2x to general. Real but modest. The 10 to 15% visibility lift that creators measure in practice is the rough output of this weight after it's combined with everything else. Premium amplifies what's already in your voice. It doesn't manufacture audience. The voice-first take on X Premium covers when the math works and when it doesn't.

The 2-minute engagement window and long-form

The algorithm rewards content that holds attention for ~2 minutes (the published threshold for the 'time spent' factor). Long-form posts and threads can clear this threshold. So can voice-rich shorter posts that prompt re-reads or replies that pull the reader back to the post. The 'just write longer posts' advice is shape-correct and voice-blind: a long category-default post bores readers off in 20 seconds; a short voice-rich post can hold attention for 90 seconds while readers re-read the closing.

Voice-rich content tends to clear the 2-minute window naturally because the writer's specific framings and specific observations don't compress well; the reader has to slow down to actually take in what's being said. Category-default content compresses to skimming because the reader has seen the same shape 50 times already.

What the algorithm doesn't measure (and what voice protects against)

  • Audience quality. The weights treat a like from a bot the same as a like from a niche peer. Voice-rich content tends to attract niche peers because it doesn't perform like engagement-farming content; the inbound is structurally higher-quality.
  • Re-circulation. The published weights don't directly include 'this person comes back to read your timeline.' But the indirect signals (replies-per-impression, profile-clicks-per-impression) capture some of it. Voice produces re-circulation; templates don't.
  • Off-platform compounds. The algorithm doesn't see your newsletter signups, your DMs that become consulting calls, your products that sell. Voice-first creators optimize for these; the algorithm scores their content the same as everyone else's, but the off-platform math is what actually pays.
  • Voice consistency over time. A timeline that reads as one writer's voice over 12 months compounds via readers attaching to the writer, not via any single post's algorithmic boost. The algorithm sees each post independently; the audience doesn't.

The voice-first algorithm playbook

  1. Replies as the primary distribution surface. 5 to 10 voice-rich replies a day on bigger accounts. The 13.5x to 75x weight does most of the work. Skip reply-bot automation; the patterns get caught and the negative feedback compounds. The case against reply-bot automation at scale covers why.
  2. Voice-rich evergreen, 2 to 4 a week. Each post designed to be readable in 6 months. The 360-minute decay rewards content that keeps getting picked up across the days that follow.
  3. Bookmarks-per-impression as the cleanest distribution proxy. Track it. If it's flat, the audience isn't finding reference value; usually a voice-flatness symptom.
  4. Verification at audience-tier where the 4x multiplier produces measurable lift (typically 3K+ followers). Below that, the lift is below noise.
  5. Avoid the penalty triggers structurally, not tactically. Don't write the content that earns reports; the voice register that earns reports is the same register that suppresses long-term audience attachment.
  6. Don't use the algorithm as a learning signal for voice. The weights reward engagement; engagement is downstream of voice. Use the algorithm as a publishing constraint, not as a voice editor.

Where Auden fits

Auden trains on a creator's full profile (100 to 200 posts, replies, threads, and images across 9 signals of voice) and produces drafts that match the writer's register. The algorithm rewards what voice produces. The role of Auden in this picture is not to game the weights; it's to keep voice consistent across the cadence the weights reward. A timeline that reads as one writer's voice over 90 days picks up the algorithm's small boosts on every post; a timeline that drifts off-voice picks them up half the time and loses the readers who came for a specific writer.

The algorithm is mechanical. Voice is the asset it amplifies. The voice-first playbook treats the weights as a small modifier on a much larger system: who you're recognized as, who comes back, and what they do off-platform. The published weights confirm the playbook; they don't replace it. For the writer-facing playbook that operationalizes this mechanical-amplification-of-voice reading into a refusal of the four shortcuts the standard growth guides still recommend (bought followers, engagement pods, AI-template hook patterns, sycophantic reply-spraying) plus the five disciplines that produce real organic growth on the 90-to-180-day timeline the weights and the audience-side filtering combined actually permit, see how to grow on X in 2026 without buying followers or running engagement pods.

Want content that actually sounds like you?

VoiceMoat trains an AI on your full profile (posts, replies, threads, and images) and refuses to draft anything off-voice. Free for 7 days.

Related posts

Growth

The reply guy playbook: how to use AI for Twitter replies (without sounding like a bot) in 2026

Reply automation at scale is voice-corrosive at the structural level; the audience pattern-matches automated reply patterns within scrolling distance and the writer's reputational capital collapses faster than any other content failure mode. The conviction-led playbook for AI-assisted Twitter replies in 2026 that does not sound like a bot: the voice-corrosive-versus-voice-rich split in reply tooling, the inline Chrome extension workflow that keeps the writer in the loop, three illustrative reply examples clearly labeled constructed, and the operational discipline that compounds reputational capital instead of collapsing it.

Growth

How to repurpose tweets into LinkedIn posts (without sounding generic) in 2026

Cross-platform repurposing fails most often when the writer optimizes for LinkedIn's surface conventions and loses the voice that made the X content land. The tactical, example-rich playbook for repurposing tweets into LinkedIn posts in 2026: three structural moves (format conversion 280-char to 3000-char native, tone calibration without LinkedInfluencer cliches, audience-context adjustment from feed-scrolling to professional reading), illustrative before/after transformations clearly labeled constructed, and the voice-fidelity discipline that holds across both platforms.

Growth

The 10 best Chrome extensions for Twitter/X creators in 2026

Chrome extensions sit inside x.com itself, which removes the tab-switching friction that kills sustained content cadence. Ten Chrome extensions serious Twitter/X creators run in 2026: voice-trained reply drafting, AI growth platforms, scheduler-from-feed, two-platform parity for LinkedIn-and-X, viral-metrics overlay, multi-channel publisher, reply automation at the voice-corrosive edge, and the utility extensions that round out the stack. VoiceMoat's Chrome extension is in the list at position two with the placement-discipline reasoning on page; pricing is verified where publicly surfaced as of May 2026.