HTML5 game publishing

Building an Arrow Puzzle Collection Page from the PlayKovo Feed

Define the collection, shortlist with feed fields and a text rule, read every candidate, write what the feed cannot give you and keep the page accurate as the catalog changes.

PlayKovo Team4 min read
Games currently available on PlayKovo. Open a title to see its current listing.

"Arrow puzzle games" is the kind of query a collection page was made for. It has a clear meaning, a defined set of games and a searcher who wants to see them side by side. This post is a practical walkthrough of building that page from the PlayKovo feed: how to pick games, how to filter them in code, what to write around them and how to keep the page accurate as the catalog changes. The same recipe works for any mechanic-based collection, like sorting puzzles, pin-pull puzzles or drawing games.

Define the collection first

Write a one-line rule for what belongs on the page before you touch the feed. For arrows: "puzzles where you tap or click arrows to send them off a board, and the order matters". That rule keeps out games with arrows in the title that are not the same thing, such as archery games. Searchers who type "arrow puzzle" and land on a bow-and-arrow shooter leave instantly.

Find the games in the feed

The game feed gives you, for each game, a title, short description, full description, controls, thumbnail, device support, screen orientation, language, categories and tags, and an embed URL. Tags are the coarse tool and text is the precise one. No tag is guaranteed to match your collection exactly, so combine them:

const res = await fetch('https://playkovo.com/api/embed-games?format=json');
const { games } = await res.json();

const rule = /\barrows?\b/i;
const candidates = games.filter(g =>
  rule.test(g.title) || rule.test(g.shortDescription)
);

Then read every candidate. A text match is a shortlist, not a decision. In the PlayKovo catalog, a title search for "arrow" returns arrow-removal puzzles and also archery games and a game where you steer an arrow through spinning rings. A human step of reading the descriptions is what keeps the page honest. Store your approved list by game slug in a small file, so the page does not change by accident when a title changes.

Use the right fields to organise the page

Different fields help different visitors:

  • Orientation. Puzzle games like this are mostly portrait. A grid of landscape and portrait thumbnails looks messy, so group by orientation, or show portrait games in a taller card. See portrait games in an embed for the embed side.
  • Device support. If you want to say "works on phones", check deviceSupport for each game rather than assuming. Choosing games by device support covers it.
  • Controls. Show the controls line next to each game. It is useful and original content that the visitor cannot find in a thumbnail. See showing controls and instructions from the feed.

Write the part the feed cannot give you

A page that is only a list from a feed is thin. What makes the page worth ranking is the writing around it:

  1. A short explanation of the genre. What the mechanic is and why it is satisfying.
  2. How the games differ. One that has lives and a timer, one with no timer, one on a rotating cube, one that unlocks furniture. Visitors choose by those differences.
  3. A beginner's tip or two. For example, working backwards from the most trapped arrow.
  4. Which to start with and why. A clear recommendation is the part no feed provides.

Games on PlayKovo have their own pages with fuller descriptions. Do not copy them. Write in your own words and link to your own game pages, as explained in writing your own page for each game. The same applies to titles and descriptions of the page itself.

A collection page with ten embedded games loads ten iframes, and that will hurt your speed. Use thumbnails on the collection page and link to a separate page for each game that holds the embed. See inline embeds versus dedicated pages, and if you do embed several games, lazy loading many embeds.

Keep it accurate over time

  • Games leave the catalog. Check your approved slugs against the feed each time the page builds. If a slug is gone, drop it from the page and from your internal links. See what visitors see when a game goes away.
  • New games appear. Run your text rule against the feed weekly and read new candidates. A review queue for new feed games describes a routine.
  • Facts change. If you write "the game has 850 levels", that number is stated by the game and may change. Prefer ranges or leave numbers out unless you recheck them.

What success looks like

After a few weeks, check whether the page receives impressions for the queries that prompted it. If it appears but gets few clicks, improve the title and the introduction. If it does not appear at all, check that it is linked from your hub page and submitted with IndexNow. To pick the next collection, go back to your list of opportunity queries and look for a mechanic you have not covered.

We use optional cookies for site analytics and site advertising. You can change your choice later. Privacy policy.