Steam Store Algorithm: How Steam Decides What Gets Seen

There is no single Steam ranking to climb. The store assembles a different front page for every customer, and Valve's own partner documentation names what feeds that assembly: purchases and playtime, the languages your game supports, and accurate tags. It names, just as explicitly, what does not feed it: wishlist counts, store page traffic, conversion rate, and review score above 40 percent. Most folklore about the algorithm contradicts the documentation Valve publishes in the open, which is the unusual part: this is a black box with a manual.

The questions that brought this article into existence came from developer communities in September. One developer watched an algorithmic sale widget, rather than any curated slot, deliver about a thousand visits during a seasonal sale, and asked whether the store had quietly replaced daily deals with personalization. Another asked whether reviews given through keys count less than purchased ones. A third was self-hosting a market analyzer because they could not afford the commercial one. All three questions have documented answers, and the answers are more boring, and more useful, than the theories.

Quick answer#

Steam decides visibility per customer, not per game. The store weights what players actually own, play and spend money on, then assembles a front page unique to each person; Valve describes the main capsule as driven by what players spend time and money on, rather than Valve curation. Every new release is guaranteed a baseline of real impressions through the New Releases Queue, which prioritizes titles that have received the fewest views since release. Everything beyond that baseline is earned the same way: players buying and playing your game is the signal that makes the store show it to more people. And placement cannot be bought; Valve's FAQ answer to whether you can pay for more visibility is a single word.

The rest of this article walks the surfaces, the signals, and the levers, with the documentation linked at the end.

What the store is actually optimizing#

Valve frames front page placement as "a careful balancing act": show products customers are interested in buying and will be happy with, while giving new games a chance to find their audience. The stated objective is happy customers, which sounds soft until you unpack what it implies mechanically. A placement that shows a player something they regret buying has failed twice, so the store leans on the most honest predictors it has: what this player already owns, what they keep playing, what their friends play, what language they read.

This is why the mental model of "ranking on page one" misleads. There is no page one; there are millions of them, one per customer, recomputed continuously. Two players browsing at the same moment see different main capsules, different recommendation shelves, often a different order of the same Top Sellers list. When a third-party analytics site tells you your game is position 8 for a tag, that is an average over a population of personalized pages, not a fact about any page a human saw.

It also explains a frustration the community keeps voicing: you cannot easily see where your game appears. Valve's answer to that is built into Steamworks, under Marketing and Visibility, a Traffic Breakdown report showing the specific placements your game appeared in, how many impressions each earned, and how many clicks followed. Any developer with a live store page has this data free, and it is more precise than any external tracker, because it is the store reporting itself.

Where visibility actually comes from#

The surfaces divide into a guaranteed launch window and everything after.

The guaranteed part. At full release your game enters a pool of just-released titles. Each time a logged-in player opens the New Releases Queue, the system builds a queue from that pool, prioritizing the titles that have received the fewest views since release. Queues are tailored to each player, and titles can be filtered out based on tags or product type, but within whatever pool applies, unviewed games go first. This is the one part of Steam visibility nobody earns: a floor of real impressions, counted per click-through, from which the store measures interest.

The earned part at launch. Beyond the queue, a new release can land in several places, all conditional. It appears on the New Releases page and the All New Releases list by default. If it is doing well it can reach the New and Trending section, which Valve explicitly warns is volatile: a title "may be bumped off this list quickly if many other popular products are releasing at the same time." If it achieves sales rank it can enter the Top Sellers lists on the store home page and on relevant genre and tag pages. And everyone who wishlisted it gets an email.

The surfaces after launch.

Two of these deserve a special note. The friends' activity feed is the only surface where social proof does the placement work for you: every purchase, screenshot, achievement and discussion by a player surfaces the game to their friends, which is why games that give players something to share keep compounding long after launch week. And Recently Updated is not automatic luck; it is a mechanism you operate, covered below in the levers section.

The three inputs the ranking actually uses#

Valve's visibility documentation lists the key elements, and it is a short list.

Purchases and playtime. "Are people buying and playing your game? This is a strong signal to Steam that there is interest in your game and that Steam should try showing it to more players." Note the pairing: buying and playing. A game that sells a burst of copies and gets refunded or abandoned tells the store less than one whose buyers are still in it a week later. This is the mechanical reason launch-week playtime matters beyond reviews: it is a ranking input.

Languages. Players prefer games they can understand, so the store is more likely to show your game to players who speak a language it supports. The uncomfortable implication for English-only solo devs is that localization is a visibility lever, not just a courtesy: each supported language widens the population the algorithm is allowed to match you with. The wording stops short of promising placement, but the direction is unambiguous.

Tags. Steam requires at least five tags before launch and recommends up to twenty; only the top twenty are visible and used to influence store visibility. Tags decide where your game is allowed to surface: genre and category pages, tag search, tag-driven recommendations, dynamic library collections. Two details of the tag system trip developers up. First, order matters: the Tag Wizard, in the store page editor, lets you sequence tags for weighting, so the most specific descriptor should lead. Second, tags are not purely yours: players and moderators apply tags too, and their weight can drift over time as the community votes with tags of its own. You can remove tags that misdescribe the game, and you should, because a wrong tag does not just mislabel you; it filters you into queues of players who did not want your kind of game. The documentation's own example of good practice is Super Meat Boy: not "Action", not even "Platformer", but "Precision Platformer", the most specific true thing.

What the algorithm explicitly ignores#

The documentation is unusually direct about the non-factors, and each one overturns a piece of community folklore.

Wishlists, mostly. "With a few exceptions like the Popular Upcoming tab, wishlists are not a factor in your game's algorithmic visibility on Steam." Before launch they do matter, since upcoming lists sort by popularity filters, and the wishlist FAQ notes a wishlisted game can resurface in featured sections with a visual reminder for that player. But as a ranking input after release, the count you agonized over is not being scored. What wishlists actually are is a distribution list with triggers attached: launch and Early Access exit emails, discount emails at 20 percent or more, and one demo notification. The discount trigger has fine print worth knowing: the discount must include your lowest-priced package, run over eight hours, and each app ID is limited to roughly one email per two weeks, with the cooldown extending during seasonal sales. If you have been optimizing wishlist counts as if they were SEO, our guide to getting your first 100 Steam wishlists is written around what they really do, and our wishlist conversion benchmarks cover what the list pays back after launch.

Store page traffic. "The traffic landing on your store page is not a factor in your Steam store visibility." More visitors may produce more sales, which do matter, but traffic alone is not scored. This is the documented reason buying store-page traffic is worthless for visibility: the store discounts visitors who do not become players.

Conversion rate. Also not a factor. A page that converts 12 percent of 500 visitors earns nothing extra over one that converts 3 percent, all else equal; only the purchases and playtime that result are read. Conversion still matters to your revenue, obviously, and to whether paid external traffic pays for itself, but it is not a ranking input.

Review score, above the floor. As long as reviews are Mixed or above, roughly 40 percent positive, the score is not a factor in algorithmic visibility. Drop below that into Mostly Negative and the game becomes less likely to be featured. The score is a floor, not a ladder; the difference between 70 and 90 percent is for humans, not the algorithm.

Do key-given reviews count less?#

This question circulated in developer communities again in September, and the documented answer is yes, in a narrower way than people fear. The review score shown on your store page includes only purchases made by the reviewing account; key activations are excluded. Reviews written from keys, press copies and pre-release builds are displayed, and marked as free or pre-release, but they do not move the aggregate.

The practical effect on visibility rounds to zero, because, as above, the score above 40 percent is not a visibility input. What key campaigns actually touch is the number browsing humans see next to your capsule, and the emotional weight early reviews carry. One caution from the same documentation: soliciting reviews in exchange for games, DLC, money or other rewards is against the usage rules, with press copies the stated exception; the same rules ask you not to prompt for reviews from inside the game.

Daily deals, sale widgets, and the personalized storefront#

The September observation that a sale widget delivered about a thousand visits deserves its own reconciliation with the docs, because both halves are true.

Daily Deals still exist as a curated promotion, featured on the home page and tag pages, but they sit behind earned criteria: demonstrated customer interest and trending revenue over recent months, typically sustained revenue in the tens of thousands of dollars per month. A game released within the last two or three months is explicitly too new to evaluate; first discounts tend not to qualify for lack of performance data; and curated promotions are capped at roughly once a year per game. Deals run seven to fourteen days, and even among active deals, which ones a given player sees first is personalized by play history and language. For a first-game developer, this surface is irrelevant, and that is fine; it is the endgame, not the opening.

Meanwhile the volume of sale-period discovery flows through the algorithmic shelves: Specials, recommendation rows, the personalized capsule. That is what the community thread actually noticed, and it is the same mechanism as every other week, merely amplified: per-player placement, earned by the buy-and-play signal. If you want the deeper treatment of how crowded the launch environment has become and what a human-made indie still does about it, our piece on AI-generated games flooding Steam covers the visibility fight; this article is the machinery underneath it.

The levers you actually control#

Nothing above is purchasable, but nearly all of it is steerable. The list, roughly in the order a pre-launch developer meets them:

1. Put the Coming Soon page up early. Valve's own best practice list starts here: a live page gives interested players somewhere to act, wishlists barely decay (a player who wishlisted two years out buys about as readily as one from two weeks), and the release email needs a list to land on. The page must be public at least two weeks before release, and store review needs a buffer of at least seven business days; treat both as floors. Our Steam Direct walkthrough covers the setup end to end.
2. Run the tag pass like it matters, because it does. Sequence for weight, most specific first, aim for the full twenty, steal honestly from the tags of the three most similar games to yours, and delete tags that misdescribe you. Tags decide which queues you are even eligible for.
3. Support one more language than feels convenient. Each language is a population the algorithm may match you with. Even partial localization widens the door.
4. Choose a launch week you can win. New and Trending bumps titles off quickly when many popular products release at once. Scan the release calendar; a quiet week buys your nascent signal more time to register.
5. Use the demo notification deliberately. When your demo goes public you can send wishlisters one notification, manually triggered, any time in the following two weeks. Pair the timing with your demo and festival strategy rather than firing it on day one by reflex.
6. Budget the five Update Visibility Rounds. Every product gets five rounds, shared between Early Access and full release; spend them all in Early Access and there are none left for launch. A round shows your update to players who own or wishlisted the game, on a dedicated front page shelf, for up to thirty days or one million impressions. It requires a community announcement posted within the last thirty days, starts only after initial launch visibility concludes, does not display during the four seasonal sales (though those days still count against the thirty), and additional rounds are granted to games that are selling well. There is no forced cooldown between rounds; the constraint is your own roadmap.
7. Remember what a discount triggers. Any discount of 20 percent or more, on the lowest-priced package, running over eight hours, sends the wishlist email. Small symbolic discounts below 20 percent save nothing and announce nothing.
8. Read your own Traffic Breakdown weekly. Impressions by placement, clicks by placement, free, authoritative. It answers the question the would-be analyzer builder was trying to answer, and it should shape where you spend effort: a shelf that shows you often but earns no clicks is a page problem; a shelf you never appear on is a signal problem.
9. Bring demand from outside. The store amplifies interest; it does not manufacture the first spark. The external-channel work is unchanged by any of this machinery, and our guide to marketing an indie game with no budget is the companion piece: it fills the top of the funnel this article's levers then multiply.

Common mistakes#

• Hoarding wishlists as a ranking currency. The count is a distribution list, and the docs say so; optimize it for the email it sends, not for a score that is not being kept.
• Buying store page traffic. Traffic is a stated non-factor; only the purchases it produces matter, and cold purchased traffic rarely produces them.
• Launching into a stacked week. The New and Trending bump-off is documented behavior; it turns a winnable week into a lottery.
• Tagging broad instead of specific. "Action" tells the store almost nothing; the community re-weights your tags anyway, and wrong tags place you in front of players who filter you out.
• Paying for analytics before opening the free ones. Traffic Breakdown and the wishlist reports in Steamworks answer most placement questions with first-party data.
• Burning all five Update Rounds during Early Access, leaving nothing for the 1.0 launch, which is treated as a fresh visibility event you will want ammunition for.
• Chasing the review score upward. Above 40 percent the algorithm does not read it; the marginal weekend spent farming positivity buys nothing that an hour of playtime engineering would not.

How Egmatic fits#

Egmatic, the no-code 2D editor this blog belongs to, is being built around a simple observation about everything above: the levers are post-export work. The store page, the tags, the demo notification, the Update Round, the discount that trips the wishlist email, the Traffic Breakdown read; none of them are about making the game, all of them are about shipping it, and they arrive exactly when a solo developer is most exhausted. The ship layer is where we are wiring those steps, next to publishing and analytics, so that releasing a build and acting on its visibility data become one motion instead of two disciplines. The AI inside the editor plays the role we believe AI should always play here, a craft amplifier under your direction: you decide what the update is and which shelf it targets, it drafts the announcement and the page changes, and every file stays yours. We will state the stage plainly: Egmatic is pre-alpha, we announce no dates we cannot keep, and the waitlist at egmatic.com is where you can reply with the visibility lever you would want wired first, because requests that arrive during pre-alpha are the ones that steer the build.

Visibility levers that live next to the Publish button.

Egmatic is a no-code 2D editor and engine with a ship layer under construction: store page steps, update announcements, discounts and traffic analytics wired beside publishing. Reply on the waitlist with the visibility lever you would want first: requests sent during pre-alpha are the ones that steer the build.

you@example.comGet Build News

No spam. Unsubscribe anytime.

Conclusion#

The Steam store algorithm is not a slot machine and not a bribe economy; it is a matchmaker with published tastes. It shows each player a store built from that player's behavior, it reads three inputs about your game with real weight, purchases and playtime, languages, and tags, and it says plainly that the numbers most developers obsess over, wishlists, traffic, conversion, review percentage, are not inputs at all. The discipline that follows is almost anticlimactic: make a game people keep playing, describe it in the store's own vocabulary of specific tags and supported languages, claim the guaranteed baseline by launching into a week you can win, and then work the mechanisms you control, the Coming Soon page, the demo ping, five Update Rounds, discounts deep enough to notify anyone. Valve's own last word in the documentation is the part nobody wants to hear and every launched game confirms: some customers need to see your game dozens of times before it catches their attention. The algorithm's job is to give it those dozens of chances; yours is to give the algorithm something worth repeating.

Sources#

• Visibility on Steam, Steamworks Documentation, Valve
• Update Visibility Rounds, Steamworks Documentation, Valve
• Steam Tags, Steamworks Documentation, Valve
• Wishlists, Steamworks Documentation, Valve
• User Reviews, Steamworks Documentation, Valve
• Daily Deals, Steamworks Documentation, Valve
• Community reads, r/gamedev, September 2026: sale-widget visit counts during a seasonal sale, the key-given reviews question, and the self-hosted market analyzer thread; flagged as community observations, not Valve statements