For game devs

What eight weeks of Crit Pick data actually show

An early Crit Pick checkpoint: cumulative search figures, uneven page results and the conclusions those observations cannot support.

Layered translucent panels casting blue shadows beside a magnifier — SeeIndie

At the eight-week checkpoint, Crit Pick had recorded 44 clicks and 5,050 impressions in Search Console. The earlier saved checkpoint showed 18 clicks and 1,650 impressions. These are cumulative snapshots, not two separate months. What interests me is which pages were being found and which were not, while I was still finding the shape of a magazine I wanted to make.

Crit Pick is my gaming magazine and a project I care about. I use it to examine publishing decisions in public. This second checkpoint records early observations; it cannot establish an SEO method or tell an indie developer what their game will sell.

Data through · Google Search Console

The short version
  • The cumulative totals increased. Average position changed from 11.1 to 12.1 and CTR from 1.1% to 0.9%. A different mix of pages and queries may explain some of that change; the aggregate report cannot tell me how much.
  • One guide gained clicks. The RimWorld animal tier list changed from 1 to 16 cumulative clicks and from 174 to 992 impressions. That makes it useful to investigate, but it does not isolate the effect of internal links or time.
  • The big utility bet missed, so far. The GW2 event timer, the high-volume front door I singled out in month two, has 62 impressions, zero clicks, with a reported average position of 17.8 in this snapshot.
  • The title problem I flagged is still open. The RimWorld lore page now gets seen 956 times and clicked 3. A 0.3% click-through. I said I would fix it. Real life got in the way.
  • Still a data point, not a result. 44 clicks. Treat it as a small observation, not a verdict.

Compare the same reporting windows

A second snapshot gives me more observations, but cumulative totals normally rise as the measurement window gets longer. To test growth, I need equal periods with the same pages, query filters and definitions.

The saved four-week checkpoint contains 1,650 impressions and 18 clicks; the later cumulative checkpoint contains 5,050 impressions and 44 clicks. I am keeping both as historical records, without treating their ratio as a measured monthly growth rate.

5,050
search impressions across eight weeks, up from 1,650 at the last checkpoint
Google Search Console
44
clicks so far, up from 18, and more than half of them in the last month
Google Search Console
12.1
average position, one slot lower than the 11.1 last time, cause not established
Google Search Console
0.9%
click-through, down from 1.1%, the contribution of page and query mix is unresolved
Google Search Console

A separate last-28-days export contains 3,541 impressions and 27 clicks. That is a different reporting window from the cumulative eight-week total. Without aligned start and end dates for both periods, I cannot use it to establish acceleration.

The first four weeks1,650
The most recent 28 days3,541

Average position and CTR changed at the same time as the site gained pages. New Palworld pages may have changed the mix, but older pages may also have moved. I need a page-and-query comparison across matching periods to separate those explanations.

I chose to build individual Palworld creature pages because a player may be looking for one creature. That is a product and information-structure decision. It is not evidence that every entity needs its own URL, or that a new page will eventually rank if I wait long enough.

For what it is worth: I am proud of how those Pal pages turned out. Google does not rank you for design, so it buys me nothing on the scoreboard, but I built them myself and I love how they look.

One evergreen guide gained clicks

The RimWorld animal tier list is worth a closer look: its saved cumulative figures changed from 174 impressions and 1 click to 992 impressions and 16 clicks. Its reported average position was 9.6, an aggregate across impressions rather than a fixed place on page one.

Clicks by page, eight weeks (one page carries it)
Google Search Console
animal tier list
16
demo review
7
which race (GW2)
6
lore explained
3
Scrapper build
3
I had not deliberately rewritten that guide between the checkpoints. More related pages and links appeared around it, but other things changed too. Internal linking is a plausible contributor, not a measured cause. The GW2 race guide also gained impressions in these saved views.

What faded: the timely posts

The demo review had 7 cumulative clicks at both checkpoints. This snapshot does not establish why it stopped gaining clicks.

In this small sample, the demo review stopped gaining clicks while the evergreen guide gained some. That is a useful contrast to investigate, not a rule that guides beat news. For an indie developer, a timely demo announcement and a lasting explanation can serve different player needs.

The bet that has not landed

Here is the one that stings. In month two I made a point of the GW2 event timer as the cluster's front door, the one high-volume utility page worth fighting for at roughly 12,100 searches a month. The idea: a useful tool page pulls in traffic that a niche guide never could, and funnels it into the rest of the cluster.

Eight weeks later that page has 62 impressions, zero clicks, and an average position of 17.8. Page two. It only started showing up in search at all around 20 July, the first recorded impressions do not establish its crawl date, and it has a long way to climb before anyone sees it.

The guide · average position 9.6
RimWorld animal tier list

16 clicks, 992 impressions, position 9.6. The guide gained cumulative clicks without a deliberate rewrite; the cause is unresolved.

The tool · average position 17.8
GW2 event timer

0 clicks, 62 impressions, position 17.8. The biggest-volume bet on the site, and so far it has produced nothing.

The timer and quiz are different pages answering different searches. Existing competitors, the age of the pages, demand and how well each result fits the query are possible explanations. I have not isolated any of them, so this comparison cannot establish a required order of building authority and launching a tool.

The title problem is still a title problem

The RimWorld lore page had 538 impressions and 2 clicks at the earlier checkpoint. Its title and snippet are worth checking, but low CTR can also reflect query mix, position or the search results around it. A title change would be a test, not a confirmed diagnosis.

It now has 956 impressions and 3 clicks. A 0.3% click-through rate, which is worse than it was. More people are seeing it, almost none are clicking, and I did not fix the title the way I said I would. The honest reason is not strategic: I was in the middle of a house move, and a title rewrite on a page that already ranks kept losing to real life. That is the unglamorous truth of running a project like this alongside everything else, and pretending the gap was some clever wait-and-see would be exactly the kind of tidy story this whole experiment is meant to avoid. The job did not get done, the data noticed, and now it is on the record until it is fixed.

Internal linking: the deep dives lead, the hubs lag

The individual guides have lower average-position values than the broader hubs in this snapshot. They answer different queries, so this is a comparison to investigate rather than evidence of link equity passing between them.

Average position: deep dives vs their hubs (shorter is better)
Google Search Console
class quiz
8.8
animal tier list
9.6
Scrapper build
9.7
RimWorld hub
18.3
GW2 guides hub
30.4
homepage
31.4
The individual guides had better average positions than the broader hubs in this snapshot. They answer different searches, so that does not measure link value passing between them. I would track the same hub and guide queries over equal periods before judging the structure.

So the next checkpoint has a clear thing to watch: do the hubs finally start climbing, or does the theory need a rethink?

The honest verdict, so far

The cumulative totals increased and some pages attracted more clicks. That is encouraging for a small publication, but it does not prove that the method works, that internal links caused compounding, or that these results transfer to a studio website.

½
An unresolved comparison
“The event timer will be the cluster's front door.”

Established competitors are one possible explanation. The snapshot does not establish why this page performed differently from the others. 62 impressions, 0 clicks, page two.

×
Did not happen
“I will fix the lore page's title next.”

A house move ate the time. The page still pulls 956 impressions at a 0.3% click-through. On the record until it is fixed.

×
Not in the short term
“More pages should lift the average.”

New pages may have changed the average. That remains a hypothesis until the same pages and queries are compared.

None of that is failure at eight weeks, but all of it is the kind of thing a case study is supposed to say out loud instead of cropping out of the screenshot. Forty-four clicks is still nothing. This is an early observation, not a proven result. The reason to keep reading is that you get to watch it either keep bending up or flatten out, with the method laid bare enough that you can judge it for yourself.

One last honest thing, because it colours all of the above. Crit Pick is a games project I actually care about, not just a test rig for SeeIndie, so not every page here is an optimization play. Some exist purely because I wanted them to, and a page made out of real interest is never fully optimized. That is almost what makes it real. I think that is a feature, not a leak. A site that only ever ships the keyword-perfect page reads like one, and its numbers are the easy kind to stage. This one has pages that are just mine, made because they mattered to me and not because a tool told me to.

I would rather hand you honest data off a project I love than clean data off a machine.

What is next

Three questions for a later measurement.

01
Fix the title
Actually rewrite the RimWorld lore title and snippet, and watch whether those 956 impressions finally start converting.
02
Investigate the timer
Give the event timer internal links and time, and decide by the next pull whether the front-door idea survives contact with reality.
03
Watch the hubs
If the deep dives keep climbing but the hubs stay on page two, the cluster model needs a harder look.

A later update needs matching measurement windows and a clear record of what changed. There is no fixed publication schedule for this experiment.

Common questions

Is eight weeks long enough to conclude anything?

It gives me observations to investigate, not a proven method. These cumulative checkpoints cannot establish a growth slope. Comparing matching periods and the same pages and queries is the next measurement task.

Why did the average position get worse if the site grew?

New pages may have changed the mix of impressions. Without comparing the same pages and queries across matching periods, I cannot separate that effect from changes to existing rankings.

What was the single biggest surprise?
That the high-volume tool page I was most excited about produced zero clicks, while an evergreen tier list I barely thought about became a third of the site's traffic. The unglamorous page won.
Can I check these numbers?
That is the whole idea. Crit Pick is live at critpick.me, every page mentioned here is public, and the totals come straight from Google Search Console. If a claim here does not match what you can see, I want to know.
Does this method work for my game's site?

This is a publisher case, not a developer sales test. Clear pages, useful links and careful measurement are ideas to examine on your own site. These data do not establish that copying the structure will increase wishlists or sales.

Sources: Google Search Console (clicks, impressions, CTR, position) for critpick.me, eight-week view and the last-28-days export; the earlier checkpoint post for the four-week comparison; own keyword research for the event-timer search volume.