Most game portals treat the page around a game as packaging: a title, a thumbnail, a sentence copied from the developer and a wall of other thumbnails. We think the page is part of the product. This article explains what goes into a Diemakora game page, where the information comes from, what is written by us and what is not, and how we decide which pages are good enough to show to search engines.
Where the raw material comes from
Every game arrives with a small bundle from its distributor: a title, a short description written by the developer, a line of instructions, a category, a handful of tags, a thumbnail and a flag saying whether the game supports touch. The description is typically thirty to sixty words and is identical on every site that carries the game. Used on its own, it produces exactly the kind of page nobody wants to read — which is why we do not use it on its own.
What we add
A finished page has a fixed structure, and each section has a job.
- Lead. One paragraph that says what kind of game this is, what the tags imply and what to expect, written in our own words. It is the part a hurried reader sees, so it earns its place by being specific.
- About. The developer's description, cleaned of promotional filler and links to other sites, followed by our assessment of how the game fits its genre.
- How to play. Numbered steps: how to start, what the developer says about controls, a genre-specific piece of advice for the first minutes, and how to use full screen and save progress.
- Controls. A table built by reading the developer's instructions and identifying each input — arrow keys, space, mouse, tap, swipe — with the action it performs. When the instructions are vague, we say so instead of inventing detail.
- Tips. Four to six practical tips drawn from genre knowledge and from the tags. A racing game gets braking advice; a match-3 game gets advice about working from the bottom of the board.
- Who will enjoy it. Audience, session length, difficulty and device in three sentences.
- Details. A table of facts: category, tags, platform, control type, technology, frame size, date added, play count and, where votes exist, the player rating.
- FAQ. The questions people actually ask — is it free, does it work on a phone, what are the controls, does it save, how do I go full screen, what to do if it will not load — answered for this specific game.
- Similar games. Chosen by shared tags first and shared category second, ranked by how much players on this site actually play them.
How the writing is produced
We are a small team and there are many thousands of games. Writing every page by hand from a blank sheet is not possible, and we would rather be honest about that than pretend. Our approach has two layers.
The first layer is an editorial engine we built ourselves. It holds a large body of hand-written material — genre profiles, tag explanations, tips, phrasing — and combines it with the facts of each specific game: its name, category, tags, published instructions, dimensions, device support and player statistics. The combination is deterministic, so a page reads the same on every visit, and it is different for every game, because the inputs are different. It does not call any external artificial-intelligence service and it does not scrape other websites. Every sentence it can produce was written by a person on this team.
The second layer is hand-written content. For the games players return to most, we replace the engine's overview, how-to-play, tips and FAQ with sections written from actual play. These pages are marked in our system and take priority. The list grows every week, starting from the top of the most-played chart.
What we deliberately leave out
We do not publish walkthrough videos we did not make. We do not claim a game trains your brain, improves your reflexes or does anything beyond being fun. We do not use the names of other game websites, and we remove them when they appear in a developer's description. We do not write about a game's content in ways we cannot verify from its tags and instructions; if a game's description is thin, the page says less, not more.
Which pages search engines see
A page has to earn indexing. Each game is scored on the quality of its inputs — the length of the developer's description, whether instructions exist, whether the game has been played and liked on this site — and pages below the threshold carry a noindex instruction. They remain playable and linked, but we do not ask search engines to rank them. The same rule applies to tag pages with only a few games, to search results and to personal pages such as your recently played list. We would rather have a smaller number of pages we are proud of than a large number that all say the same thing.
Corrections
If a control is wrong, a game no longer loads, or a description misrepresents what a game is, the flag button under the game frame reaches a person, and so does the contact page. We fix pages when we are told they are wrong, and we log the change. The goal is simple: when you arrive on a Diemakora game page, you should leave knowing more than the thumbnail told you.
