Why your Steam game isn't selling: a diagnostic checklist

The build works. The page is live. A few people said kind things. And the sales graph is a flat line that never really started. The first explanation most developers reach for is that the game must not be good enough — sometimes that is the answer, but far more often the game is fine and something upstream of it failed. Nobody who would have loved it ever found out it existed.

Selling a game is a chain. There has to be demand for the thing you made, people have to be able to find it, the page has to convince them in seconds, the price and the moment have to make sense, and the people who could buy it have to be able to read it. Break any single link and the result on your dashboard looks identical: a flat line. That is why 'my game is not selling' is almost never one problem, and why guessing which link broke usually wastes a month.

What follows is a diagnostic, in roughly the order the links tend to break. Go through it honestly. One or two items will be uncomfortable to read, and those are the ones worth your next month of effort.

Was there demand before you started building?

This is the least pleasant question, so it goes first. A game can be well made, technically clean, and personally meaningful, and still be aimed at an audience that does not exist in useful numbers. Craft and demand are separate variables, and no amount of the first compensates for a total absence of the second.

You can check this after the fact, and it costs you nothing but an afternoon. Find five to ten games a player would realistically consider instead of yours — same genre, similar scope, similar price band. Look at how many reviews each has accumulated, how long it took them to get there, and whether they still appear in store listings a year after release. Review counts are public and are a rough proxy for units sold, so comparing several of them tells you whether the shelf you are standing on has any traffic at all.

If comparable games clearly found an audience and yours did not reach it, your problem is discovery or presentation, and the rest of this article applies directly. If the entire shelf is quiet, no amount of marketing effort will rescue this release — the useful moves are repositioning (asking which shelf you are actually on) or accepting the result and carrying the lesson into the next project. Both are legitimate. Continuing to promote a game into a market that is not there is not.

Does your store page do its job in the first few seconds?

Traffic that arrives and leaves looks exactly like no traffic at all in your revenue numbers, but it is a completely different problem with a completely different fix. Your store page is the conversion step, and pages that underperform almost always fail in the first few seconds: the header image, the opening line of the description, and the first moments of the trailer.

The common failure modes are specific and fixable. A trailer that opens with engine and studio logos instead of the game. Screenshots that show menus, dialogue boxes, or empty scenery rather than the moment your game is actually about. A description that opens with the setting and backstory instead of what the player does. A header capsule with a title so stylized or so small that it is unreadable at the size it is really displayed at, in a grid, next to a hundred others.

A useful test: show the page to somebody who has never heard of your game, take it away after five seconds, and ask them what the game is. If they cannot tell you what you do in it, the page is your bottleneck — and rewriting a page is the cheapest item on this entire list.

Can anyone find you at all?

Store discovery runs largely on classification. Tags and genre decide which lists you appear in, which games recommend you in their 'more like this' section, and which browsing filters include you. Tags that describe how you feel about your game rather than what it mechanically is will file you on a shelf where the wrong people are looking, and no amount of page polish fixes being on the wrong shelf.

Compare your tag set against the comparable games you listed earlier. If there is little overlap between your tags and the tags of the games you would want to be recommended next to, that is a structural problem you can fix this week. The order of tags matters as well as their presence, so put the ones that define the shelf first.

Outside the store itself, the routes to a small game are creators and streamers, communities built around your genre, and platform events such as seasonal sales and festivals. For most indie titles these are not extras on top of store traffic — they are the entire top of the funnel. A game released with no launch beat, no festival participation, and no creator coverage is relying on the store to promote it, and stores mostly promote what is already moving.

Price, timing, and the first reviews

Price is a message about scope before it is a transaction. Priced far below comparable games, it can read as a warning rather than a bargain — players infer length and polish from the number. Priced above them without visible production value to justify the gap, it stalls at exactly the moment the player compares you to something else. The reference set is, again, those comparable titles you already pulled up.

Timing matters in two directions. Launching in the shadow of a major release in your genre costs you attention you cannot win back later. And launching immediately into a store-wide discount season means competing for a click against a wall of established games at reduced prices. Neither is fatal on its own, but both are decisions worth making deliberately rather than by calendar accident.

Then there are reviews. A store page does not display a summarized review score until it has accumulated enough reviews to produce one, and a page without that visible score converts worse, because buyers hesitate when there is no social proof. Early reviews come from your earliest buyers, and your earliest buyers come mostly from wishlists that were built before launch day. This is why so many launch-week problems actually trace back to the months before launch — and why the fix is often not for this game but for the way you run the next one.

Are you quietly excluding most of your possible buyers?

Here is the link almost nobody checks, because it does not feel like part of selling: what language your game is in. Every store page carries a supported-languages table, and players read it. Steam also lets players filter out titles that do not support the languages they have set, which means a game with a single supported language can be invisible to a large group of people before any judgement about the game itself is ever made.

It is worth looking at the actual distribution rather than assuming. Steam publishes a monthly Hardware & Software Survey that includes a breakdown of the languages users have their clients set to, and reading it once tends to change how a developer frames the whole question. English-language users are a large group but nowhere close to a majority, and Chinese-language users are consistently among the largest groups on the platform. If you released in one language, that survey shows you roughly the size of the room you were never in.

Then look at your own numbers rather than the platform average. Steamworks reports wishlists, traffic, and sales by country. Traffic arriving from countries whose language you do not support, and converting far below your home market, is the clearest possible evidence of a leak: people are finding you and bouncing off a page they cannot read. That is a marketing problem you already paid for and did not collect on.

Making a game readable in another language is what the industry calls localization — translating the text and adapting anything that assumes the player's context. The thing to understand for this checklist is that it comes in sizes. Translating the store page alone is a few hundred words, and it works as an experiment rather than a commitment: if a translated page starts moving wishlists in that region, you have bought the information you need to decide whether the game itself is worth translating. If it moves nothing, you spent very little finding that out.

The order to fix things in

Do not fix everything at once. If you change the page, the tags, the price, and the languages in the same week, whatever happens next teaches you nothing, because you will not know which change caused it. Change one link, wait for a readable amount of traffic, then decide on the next one.

None of these steps is fast, and none of them is guaranteed to move a game that has already launched quietly. Some releases do not recover, and the honest version of this advice includes that possibility. But 'my game is not selling' is a symptom rather than a diagnosis, and every item below is something you can test instead of agonising over. Working through them in order is how you replace a demoralising mystery with a short list of concrete things to do — and how you find out which link in the chain you need to build differently next time.

• The store page first — copy, capsule, screenshots, and the opening seconds of the trailer. Cheapest to change and it affects every other channel you will use afterwards.
• Tags and positioning next — they decide which audience even reaches the page you just improved.
• The store page in the languages your own traffic data already points at — small word count, measurable outcome, reversible.
• A discount and event cadence — seasonal sales and festivals are recurring free traffic you already qualify for and may simply not be using.
• Full game localization, but only after a translated page has shown you the demand is real.
• Everything you learn here becomes an input to the next game, which starts being marketed before it is built rather than after it ships.