Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

When you publish your game for the first time, it usually has a chance to appear in the "Recent" section. However, if you wait 33 days and release a major update, even after meeting all the requirements to be featured again, your game may still not appear there. What's even more frustrating is that there is often no clear explanation as to why it didn't qualify.

Because of this, it seems that releasing your game in episodes may be a reasonable strategy, especially if you're a developer trying to grow your audience. Instead of updating the existing page, creating a new page for each major release could help your project regain visibility.

Of course, this approach comes with trade-offs. By creating a new page, you may lose your existing collections, comments, and some of the social proof that has accumulated around your project.

At the moment, this is the conclusion I've come to regarding the issue. That said, to avoid abusing the system, I believe this approach should only be used for genuinely substantial updates that can justify being treated as a new release.

(+1)

It happen to me too, after 2 weeks has your game been up to most recent or do we really need to depend on other ways to advertise too?

(+1)

Unfortunately, it never showed up, even after waiting.

Because of that, we changed our publishing strategy on itch.io. We used to keep updating the same game page with new versions. Instead, we decided to split the game into chapters. For each new chapter, we publish a new itch.io page and remove the old one. We also redesigned the game to fit this release model.

Some people underestimate the exposure that itch.io provides, but in our experience, it's far more valuable than many think. We didn't want to lose that visibility, so we had to change our publishing strategy.

Yes, this means we're willing to lose our collections, ratings, and user feedback after every major update. It was a bit disappointing, but we realized we didn't have any other practical choice.

We only do this for our public version.