Forgiven 
This article lists only ranking-related factors Valve documents or makes directly controllable in Steamworks. It does not assign secret weights or promise placement.
Store metadata
Accurate tags, categories, features and languages help describe the game. Use the official tag wizard and store configuration.
Search and presentation
Title, store text and compliant assets affect how players find and understand the product. Do not stuff descriptions with repeated terms.
Wishlists
Valve documents notifications and reporting, but not a universal wishlist threshold for ranking. Treat the count as audience evidence.
Release and update opportunities
Steam documents release visibility and Update Visibility Rounds, each with conditions. A qualifying action is not a guarantee of a specific homepage position.
Events and discounts
Participation and pricing must follow their current rules. They can create store contexts without proving a permanent algorithm effect.
Player outcomes
Sales, play, refunds and reviews matter to the business, but do not invent a public formula for their ranking weight.
Evidence boundary
Start with Valve’s documentation. Use game-specific tests for presentation and traffic, and state “not published” where the platform is silent.
