The PlayKovo Review Checklist: Six Lines to Check Before You Submit

The developer portal has a six-line review checklist. It is short, but each line stands for a decision you can get wrong. This post goes through the six items one by one, says what a reviewer is likely to look at and gives you a ten-minute test you can run before you press submit.

1. Game opens quickly in a modern browser.
2. Thumbnail and cover image clearly show the game.
3. Description explains gameplay without keyword stuffing.
4. Categories are broad and tags are focused.
5. Ads are age-appropriate and do not interrupt basic play unfairly.
6. No popups, forced redirects, fake download buttons, malware or phishing.

The portal places a "Submit a checked game" button directly under the list. The intent is that you go through it first.

A reviewer opens your game once, probably on a normal computer. If the first screen takes a long time, they wait, and so will players. Check:

• The size of your ZIP and your largest files. See what goes in a PlayKovo ZIP for limits.
• That a loading screen appears quickly, and that you tell the SDK about it; see loadingStart and loadingFinished.
• That nothing waits for a network request that does not exist, such as a missing font host or analytics script.

Pictures are what people see before they play. The test is simple: show the thumbnail to someone who has never seen the game and ask what it is. If they cannot say, redo it. Use a real screenshot, a clear character and readable text. Details are in the exact specs.

Write what happens in the game: what the player does, how to win, what makes it different. Keyword stuffing is a string of search terms in a row ("car game racing game free car racing online"). Read your description aloud. If you would not say it to a friend, rewrite it. Two honest paragraphs beat a long list.

Categories are the shelves your game sits on, such as racing, puzzle or action. Choose a small number that really fit. Tags are narrow descriptors of what is inside: "drifting", "physics", "one-tap". Look at how the live catalog does it; it uses a short list of categories and a larger set of specific tags for the same game, and the tags describe features rather than repeat the category. Do not add a tag for a feature the game lacks to appear in more searches.

Two parts: age-appropriate, and not unfair. The first connects to the family-safe rule; see family-safe means all ages. The second means no ad at first paint, none on every death or click, and none in a loop. The SDK guidelines say to use no more than one ad request for a single player action. Placements and timing are covered in ad behavior that gets a game rejected.

This is the hard stop. No popups, forced redirects, fake download buttons, malware or phishing. Look at your own code for window.open, location.href changes you did not intend and any third-party script you copied from another project. A single leftover tracking snippet can look like a problem; see trackers and network calls.

Minute	Do this
0–2	Open the game in a private window, with the network panel visible. Note the time to the first playable screen and any failed requests.
2–4	Play two minutes as a stranger. Do not use your knowledge of the game.
4–5	Trigger every ad placement. Check that the game continues after each one, including when no ad appears.
5–7	Try a phone-sized window and the orientation you declared.
7–8	Read your title, description, categories and tags once more.
8–10	Look at the thumbnail at its smallest size.

Then press submit. If the result is a rejection, our post on resubmitting gives you an order of work. The checklist itself is in the developer portal.