Farever Guide Hub

Farever is still in Early Access, so this guide cluster avoids pretending that every route, reward, item name, or companion behavior is final. Confirmed rows use database strings, readable UI, or strong source agreement. Reported rows can still help players, but the page shows where a screenshot, tooltip, quest log, or patch note is missing.

This hub is built for players who do not want a vague article. Each guide answers a specific question, then separates what is confirmed from what is only reported. That means a player can still act on useful leads, while editors and contributors can see exactly which screenshot, tooltip, quest log, or patch note would make the page stronger.

The first group of pages focuses on systems with the strongest evidence: H. Catchum, Gotta Catch One, Large Butterfly Net, companions, mounts, gliders, and the Crystal Mall hidden reward route. Pages for first dungeon, max level, performance fixes, and boss routes should wait until the wiki has stronger UI proof.

Use the hub as a two-click path from the homepage to a player answer. The homepage should send players to Guides, the guide hub should send them to one specific page, and each page should send them sideways to the next related guide. That crawl path keeps the site structure clean while helping players stay inside the wiki.

If you are new, start with the Farever Beginner Guide. It gives the safest first-session path without pretending that every Early Access route is solved. After that, move to Gotta Catch One if you are working with H. Catchum, or move to the Mounts Guide if your immediate goal is faster travel.

If you are collecting creatures, read the Companion Guide before looking for a pet tier list. The current evidence supports companions, capture nets, and Collections, but it does not yet prove combat bonuses or final rankings. That is why the hub points players to companion fundamentals before any ranking page.

If you are chasing hidden rewards, use the Crystal Mall page as a route lead, not as a final loot table. The route evidence is useful, but the exact reward names still need tooltip proof. This is the kind of distinction that makes the guide hub more trustworthy than a thin page that simply repeats a video title.

Some competitor pages cover first dungeon, max level, Crabgantua, performance fixes, and detailed quest chains. Those topics may be useful later, but they are not ready for this proof-first guide hub unless we have stronger in-game evidence. A guide page should not publish exact dungeon names, level caps, boss drops, or spawn timers from weak sources.

The next pages to build should come from the same rule: if the page can answer a player decision with confirmed facts and clear verification labels, it is safe to publish. If the page only has rumors, keep it in research until a database row, screenshot, video timestamp, patch note, or official post can support it.

This does not slow the site down. It creates a better content pipeline. Thin pages can rank briefly, but verified guide pages can keep players longer because they help them decide what to do and what not to trust.

The guide hub should be one click from the homepage and should link down to every major guide page. Each content page links back up to this hub through visible breadcrumbs, then links sideways to related pages. That gives Google a clear hub-and-spoke structure and gives players a natural path through the wiki.

The anchor text should stay descriptive. Use names like Farever Companion Guide, Farever Mounts Guide, and Farever Gotta Catch One Quest instead of vague text. This helps the site avoid orphan pages and keeps each page focused on one core keyword, especially when players land on the Farever Guide Hub from search.

Over time, this hub can expand into dungeons, bosses, crafting, and route guides. The stable rule is that `/guide/` remains the category hub, while individual pages carry the exact long-tail query.