AI content farms already swamped a game's search results — a case study in the other direction

Alternate headlines:

• What an honest fan guide looks like in the AI-slop era (Phantom Blade Zero case study)
• Invented weapon stats, wrong dates: inside the AI wiki farms racing game launches

Phantom Blade Zero — a wuxia action RPG from S-GAME that launches October 28/29 — has been one of the most wishlisted unreleased games on Steam for months. Which means its search results are already a case study in AI content farming. Within days of every keyword spike, more than a dozen near-identical multilingual "wiki" domains appear: same layout family, same article skeleton, thinly reworded text in English, Chinese, Japanese, Spanish, German.

As people who work with LLMs, we can recognize the production line instantly. A few things I found while researching one launch:

• Plausible fabricated data. One wiki listed full weapon stat tables — named weapons with ATK values — weeks before release. No official source publishes those numbers. They don't exist yet. They were invented, in the specific way confident LLM filler gets invented.
• Stale claims copied between farms. Several still said "system requirements unannounced" weeks after the developer published four official hardware tiers (GTX 1660 minimum, SSD mandatory, up to RTX 5080/4K60 with path tracing).
• Date errors that compound. The Steam page shows October 28; the director's letter says October 29. Farms pick one at random, so half the results contradict the other half.

The interesting part is what the counter-example looks like. A fan-built guide — Phantom Blade Zero Guide — takes the opposite approach, and its discipline is basically the checklist we'd want from any AI-assisted publishing workflow:

1. Every claim carries a source and a date. Facts read "checked on 2026-10-09", not "reportedly". The release date page shows both the Steam date and the director's letter date side by side, says the exact unlock time is unconfirmed, and resists picking the convenient one.
2. Unknowns are labeled as unknowns. Whether the game has Soulslike death penalties is nowhere in official sources, so the page says exactly that instead of generating an answer. That single behavior separates a reference from a content farm more reliably than any writing style.
3. A public methodology page. The sources and editorial policy describes the evidence hierarchy — official API/store data over press, press over wikis, wikis over nothing — and what happens when a question has no verified answer yet.
4. Corrections are logged, not silently overwritten. An updates page records each dated change, so you can see the record improve instead of trusting a page that never admits it was wrong.

None of this is technically hard. It's the same discipline prompt engineering rewards: verifiable outputs, hedged uncertainty, no confident fabrication. The farms fail not because their models are weak but because their pipeline has no incentive to check anything.

Launch week is a live experiment: on October 28/29 the unlock time, day-one patch and first reviews will land, and we get to watch which results correct within hours and which quietly keep the wrong date forever. I know which kind I'll be bookmarking.

Phantom Blade Zero Guide is an unofficial, fan-made resource, not affiliated with S-GAME. This post describes its editorial approach; I have no stake in it beyond finding the methods worth copying.

Word count: ~560. Link inventory: 4 links — 1 homepage (brand anchor), 3 deep (release-date, sources-and-methodology, updates). Deliberately fewer than the standard placement article: Discourse flags first posts from new accounts carrying many external links, and a community post reads better with fewer references. All target URLs verified live 2026-10-16 (HTTP 200, distinct shells).