HeadlinesBriefing favicon HeadlinesBriefing.com

Google Jail Blocks New Wikis

Hacker News •
×

Big week! We just finished moving the Overwatch and Fortnite wikis off of Fandom. It’s still my favorite thing in the world to help wiki editors grab control of their projects and make them awesome (and not covered with a dozen auto-playing video ads!) Unlike most of the other wikis we host (runescape.wiki, minecraft.wiki, gta.wiki…), both Overwatch and Fortnite are launching at subdomains of weirdgloop.org instead of on their own root domain, like (say) overwatch.wiki. There is an unusually good reason for this, and the rest of this post will be going into excruciating detail about: a frustrating change that Google made in early 2024 to how it treats brand-new-domains, the wide-ranging effects of these changes on the entire independent wiki ecosystem, and how I’m trying to work around this new “Google Jail” for the wikis that we host.

If you have a new domain, only the main page shows up on Google search results. These March 2024 changes have a specific “failure mode” on Google Search which has made it even more difficult for a certain class of new wikis (and most likely, new websites in general) to show up in search results. For the last two years, with very few exceptions, wikis on brand new domains will not show up on Google Search for anything other than the main page.

Since ~85% of video game wiki traffic comes from Google, and wikis (obviously) have many popular pages other than the main page, this is a pretty catastrophic outcome. Hollow Knight wiki: into Google Jail in March 2024, back out 9 months later. Here’s what we think we know: This has happened to about 90% of wikis I’m aware of that have launched on brand new domains since the March 2024 Google core update.

This includes gta.wiki and hytalewiki.org that we host, hollowknight.wiki, the official Path of Exile 2 wiki, and a couple dozen smaller wikis. This happens regardless of whether the content is brand-new, or derived from something else (like Fandom) that Google is already indexing. It’s not the conventional “duplicate content” issue that wikis have had to deal with for the last decade.

It doesn’t seem to have much to do with the actual “ranking” of the domain - there’s quite a few examples where the main page is actually beating Fandom’s main page on Google, and yet that’s the only page that shows up at all for the entire domain. This “Google Jail” lasts for an unclear period of time, sometimes up to a year, and is also sometimes “defeated” by big game updates that cause significant new traffic/content to come to the wiki. Undertale and Vampire Survivors are examples of wikis that defeated the Google Jail by waiting it out and having a big game update.

It can intermittently start and stop, sometimes getting out of Google Jail for a few months and then going back in again. It seems to always eventually stop. Most of the time, but not always, articles besides the main page are still getting indexed and crawled, and show up with a site: search.

The relevant factor seems to be not the actual “age” of the registration of the domain, but roughly when Google first indexed it. I can’t find any evidence of this happening before March 2024, in any context even outside of wikis. #1 for the most popular search, and it's the only page on the entire domain that shows up. My best guess (and to be clear, this is a guess): Google decided they could no longer effectively identify and swat away SEO slop, and figured that just massively nerfing brand new domains was their next best option.

Subdomains of existing domains are totally fine. Since this Google issue started, we’ve also launched a number of wikis on subdomains of an existing, established domain (wiki.leagueoflegends.com, wiki.warframe.com, hypixelskyblock.minecraft.wiki). Every single one of these has been immediately successful for getting articles other than the main page indexed on Google.

It doesn’t even need to be a popular domain! overwatch.weirdgloop.org, which launched just 7 days ago, is already doing better on page-indexing t...