Editorial standards
A good pick needs a good reason.
Community submissions can be discovered before review, with clear labels and submitter-provided descriptions. They are not recommendations and stay out of search indexing. An editorial release must meet every standard below before it is published as a reviewed pick.
Play it before publishing it.
A release needs a hands-on browser playtest. We record the browsers tested and review date. Mobile support is claimed only after a mobile test.
Write something only a playtest can tell you.
Explain the experience, who might enjoy it, and its limitations. Generic descriptions, rewritten provider feeds, and unverified claims do not qualify.
Credit the person who made it.
The creator must be identified, with a verified destination link. Confirm permission for the listing and any supplied screenshots. Linking does not imply permission to host or embed a game.
Put the useful details up front.
State pricing, sign-in requirements, compatibility, typical session length, and meaningful content warnings. AI use is disclosed when it is relevant to the player.
Keep editorial selection independent.
Community submissions are free and visibly separate from editorial picks. We do not offer paid editorial ranking, automatic editorial approval, traffic guarantees, or a promise of search visibility.
Maintain the shelf.
Review a release when the playable build changes or a problem is reported. Correct the notes, or withdraw the listing if it is no longer usable or authorized.