HTML5 game publishing
Write Your Own Page for Each Game Instead of a Thin Copy
Why a frame plus the feed description is a weak page, what the Partner Terms let you reuse, what you can add from your own play, and a page structure that works.
The feed gives you a title, a short description and a long description for each game. The easy path is to publish exactly those words on a page with an iframe. The result is a page that looks like every other site's page for that game, with little that is yours. This post explains why that matters, what the Partner Terms allow you to reuse, and how to build a page worth visiting.
Why copied text is a weak page
The description of a game in the feed is the same for every partner who reads it. If ten sites paste the same paragraph, none of them gives a reader or a search engine a reason to prefer one over the others. A page made only of a game frame and borrowed text is thin: nothing on it comes from you. Visitors can tell, and bounce.
The aim is not to hide the source. It is to add the parts that only you can add.
What the terms say about feed text
Section 4 of the Partner Terms lets you use feed data, including descriptions and images, to list, promote and link to games you embed or plan to embed. Section 7 forbids copying or rehosting feed images or descriptions in a way that is not needed to list the games you embed, and forbids reselling or offering the catalog or feed data to others as your own product. So using the description on the page of the game it belongs to is the intended use. Building a separate site of descriptions, or a dataset you give to others, is not.
Section 5 also applies: you may not describe a game as your own creation. Your own text should be about your site's view of the game, not a claim of authorship.
What you can add
| Addition | Example |
|---|---|
| Why it is on your site | "A good fit for a coffee break between lessons." |
| Who it suits | "One-finger controls, so it works on a phone held in one hand." |
| A tip from playing it | "The first few levels are about timing; save your upgrades for the third." |
| Related games on your site | A short list linking to other pages of yours |
| Your audience's context | A note on the theme of your site |
| A short FAQ | "Does it work on mobile? Do I need an account?" answered from the feed's device field and your own testing |
Everything on the table is true because you checked it. Play each game before you write about it; the checklist in the first 20 games guide includes what to look for.
A page structure that works
- A title that names the game and what kind of game it is. Keep the real game name.
- The embed, as copied, above the fold, with the aspect-ratio wrapper.
- Two or three sentences of your own that say why a visitor would want this game.
- Controls and how to play from the feed; see showing controls and instructions.
- Related games from your own site.
- A credit line such as "Games from PlayKovo", as described in using the PlayKovo name.
Page titles and meta descriptions
Write the title of the page and the short description that appears in search results yourself, in a way that fits your site. Do not claim that you made the game, and do not use the PlayKovo name as part of your own site's name. A clear title is the game's name plus a plain description, for example "Rainbow Run: a free unicorn runner in your browser".
What not to do
- Do not rewrite a description to make the game sound like something else. Misdescribing a game is unfair to the visitor and to the developer.
- Do not stuff keywords. A paragraph of search phrases helps nobody.
- Do not generate hundreds of near-identical pages by swapping the game name in a template. Fewer pages with real content are better.
- Do not invent facts such as ratings, player counts or awards.
For the wording that keeps you inside the terms, read how to describe games without claiming them. The feed fields are listed in the JSON feed field by field.


