Guide
Last verified: 2026-08-08
Version: Site ops research snapshot 2026-08-08 — not a game patch

GSC Click Decline Diagnosis (2026-08-08)

This is a site-ops research note for monsterlabsimulator.wiki. It uses only the Search Console comparison numbers supplied on action cards for this worktree and the site’s existing content map. It is not a player walkthrough and it does not invent query-level breakdowns that were not provided.

Snapshot metrics (provided comparison window)

MetricCurrentPreviousAbsolute changeRelative change
Clicks120193-73-37.82% (changePct: -37.82)
Impressions32743376-102-3.02% (changePct: -3.02)
CTR0.0367 (3.67%)0.0572 (5.72%)-0.0205-35.89% (changePct: -35.8868)
Average position10.126.64+3.48+52.42% worse (changePct: 52.42)

Source status: action-card GSC aggregate for this research pass (2026-08-07). No additional proprietary query tables were attached to this card.

Raw comparison object (unchanged from the action card):

{"clicks":{"current":120,"previous":193,"change":-73,"changePct":-37.82},"impressions":{"current":3274,"previous":3376,"change":-102,"changePct":-3.02},"ctr":{"current":0.0367,"previous":0.0572,"change":-0.0205,"changePct":-35.8868},"position":{"current":10.12,"previous":6.64,"change":3.48,"changePct":52.42}}

What kind of problem is this?

HypothesisSupported by these numbers?Why
Demand disappeared overnightNoImpressions only −3.02% — visibility volume is almost flat
Pure “site offline / indexing wipe”NoThousands of impressions still register (3,274)
Ranking deteriorationYesAverage position moved from 6.64 → 10.12 (+3.48)
CTR / SERP package failureYesCTR −35.89% tracks the click drop almost 1:1
Clicks fall mainly because of fewer showsNoClick loss (−37.82%) is far larger than impression loss (−3.02%)

One-line root cause

Search demand is still roughly present; the site is ranking worse on average and converting those impressions into clicks at a much lower rate. That is a position + CTR / page-matching problem, not a traffic-pool extinction event.

Arithmetic check (no new data)

If impressions had stayed exactly at 3,376 and CTR stayed at 5.72%, expected clicks ≈ 193.
At current impressions (3,274) with the old CTR (5.72%), expected clicks ≈ 187.
Observed clicks = 120.
So most of the missing ~67–73 clicks come from lower CTR and weaker average rank, not from the −102 impression delta alone.

Secondary signals already logged on this pass (context only)

These are not extra GSC tables; they are research notes already used by content cards in this worktree:

  • Recipes intent is split across multiple pages (list tool vs workflow vs index) — multi-page competition risk for monster lab simulator recipes.
  • Breeding-tool click pressure has been called out in prior ops notes (action cards cite large click losses on the breeding surface).
  • all monsters intent shows strong CTR when a clean list exists — content answers: All Monsters + All Fulus.
  • Mid-game rarity shifted after Empower Your Fulus (2026-03-02); missing executable pages hurt “what do I do after recipes?” sessions.
  • Parallel GA4 pass: site sessions −46.77%; among provided channels Direct −74.59% dominates absolute loss vs Organic −28.8% — see GA4 diagnosis.

Do not treat secondary notes as substitute query exports.

Page-level add-on: /monsters (action card 2026-08-08)

Supplied Search Console comparison for https://monsterlabsimulator.wiki/monsters only:

MetricCurrentPreviousAbsolute changeRelative change
Clicks4159-18−30.51%
Impressions621634-13−2.05%
CTR0.066 (6.60%)0.0931 (9.31%)-0.027−29.05%
Average position12.056.42+5.63+87.75% worse

Raw comparison object (unchanged from the action card):

{"clicks":{"current":41,"previous":59,"change":-18,"changePct":-30.51,"change_pct":-30.51},"impressions":{"current":621,"previous":634,"change":-13,"changePct":-2.05,"change_pct":-2.05},"ctr":{"current":0.066,"previous":0.0931,"change":-0.027,"changePct":-29.0537,"change_pct":-29.0537},"position":{"current":12.05,"previous":6.42,"change":5.63,"changePct":87.75,"change_pct":87.75}}

What this page card means

Hypothesis for /monstersSupported?Why
Demand for monster-list queries disappearedNoImpressions only −2.05%
Ranking deteriorated on this URLYesAverage position 6.42 → 12.05
CTR / SERP package weaker on this URLYesCTR −29.05% tracks the click drop
Content ops can fully repair the React UINoTitle/H1/filters live in app code outside content/

Content recovery surfaces for the same intent cluster: All Monsters Database / Complete Fulu List (first-screen verified 20), All Fulus catalog (depth + phantom blocklist), Families index (5×4 roll-up). Engineering still owns verified-default filters + draft purge on /monsters itself.

Likely page-level failure modes (ranked by fit)

  1. Weaker average position (site 6.64 → 10.12; /monsters 6.42 → 12.05)
    Titles/snippets compete lower on the SERP; fewer top-box slots → structural CTR drop even when titles are unchanged.

  2. Intent mismatch / cannibalization on recipes
    If two or more site URLs both claim “the recipes list,” Google splits ranking signals and players land on the weaker table. Content split now:

    IntentCanonical content surface
    Interactive list / filtersBreeding Calculator
    Discovery / verify workflowRecipe workflow
    All monsters + essence trios scanAll Fulus catalog
    Contribution / verification rulesRecipe index
    Mid-game rarity (not recipes)Empower guide
  3. Phantom draft data in merged DB/calculator views
    Unverified draft names (e.g. Zephyros / Terrak / Voltix class drafts) and Air/Earth/Electric essence rows dilute trust when players compare against complete verified-20 tables. Content-side clean catalog: All Fulus. JSON purge remains an engineering task outside content/.

  4. Missing mid-game Empower path
    After species unlock, players need Extract → Powder → Empower. Executable page: Empower / Extraction / Powder.

  5. Title/meta package lag on non-content routes
    App routes such as /tools/breeding and /monsters store titles in application code, not in content/. Content ops can only fix MDX surfaces and link architecture until an engineering pass updates those templates. The /monsters card above is the concrete example: rank + CTR collapsed while impressions stayed almost flat.

What this diagnosis does not claim

  • No claim about exact top losing queries beyond what other action cards already named (recipes multi-page, all monsters CTR strength, breeding click pressure).
  • No claim that Direct / branded traffic outside GSC is measured here (GSC is search only).
  • No invented percentage splits by device, country, or page without exports.
  • No assertion that fixing one page restores the full −73 clicks.

Action map (content already targeted this worktree)

PriorityActionContent surface
P1Keep verified 20 as the public all-monsters / all-recipes teaching setAll Monsters, All Fulus, Families, Recipe index, Verified policy
P1Split recipes list vs workflow so only one surface owns list intentBreeding Calculator + Workflow
P1Do not blame SEO for the full GA4 crash — Direct leads absolute lossGA4, Direct, Organic
P2Refresh monster database / all monsters content answer after /monsters CTR −30.5%All Monsters (2026-08-08 refresh) + All Fulus + Families
P2Ship executable mid-game rarity loopEmpower guide ← linked from Economy
P2Document phantom distrust list so unfiltered merges do not re-teach draftsAll Fulus phantom section
Eng (out of content scope)Breeding/monsters template title + verified-default filters + JSON draft purge/tools/breeding, /monsters, src/lib/data

Re-measure checklist (next GSC pull)

  1. Re-export the same comparison window length.
  2. Compare clicks / impressions / CTR / position again — look for position recovery first, then CTR.
  3. Pull page report for /tools/breeding, /monster-lab-simulator-recipes, /fulus, /all-monsters, /empower-fulus, /monsters.
  4. Pull query report for: monster lab simulator recipes, all monsters, monster database, fulus, and Empower-related strings if volume appears.
  5. For /monsters specifically, compare against the 41/621 / 6.60% / 12.05 baseline above — do not declare recovery from impressions alone while CTR stays depressed.
  6. Do not declare recovery from impressions alone while CTR stays depressed.

Related links