Register a .wiki domain

Fan wikis for games, shows and franchises are often the single most-visited resource a community has, yet many still live on a third-party hosting platform's subdomain, subject to that platform's ads, layout and rules. Moving a community wiki to its own brand.wiki gives the maintainers full control over design, moderation and monetisation, while the ending itself tells new visitors exactly what kind of resource they have found before they read a word of content. It also gives the project a stable, memorable address that survives a change of hosting platform or wiki software, which matters for a resource that a community may maintain for a decade or more. Search engines and other community sites can link to a clean brand.wiki with confidence that the address will still resolve years later, and the extension quietly reinforces the collaborative, always-current nature of the content on every backlink and citation.

Every growing company eventually accumulates onboarding guides, runbooks, glossaries and process notes that outlive the tool they started in — a shared drive folder, a chat pinned message, a wiki page buried inside another SaaS product. Standing up an internal knowledge base on its own brand.wiki, even if access is restricted to staff, gives that material a stable and unmistakable address that new hires can be pointed to on day one. It also decouples the knowledge base from any single vendor: if the underlying wiki software is ever swapped, the domain, links and muscle memory of "check the wiki" stay the same. For companies that want a searchable single source of truth for how things actually work, rather than tribal knowledge scattered across chat history, a dedicated .wiki gives that source of truth a permanent front door.

Search engines treat .wiki like any other generic top-level domain: there is no automatic ranking boost simply for using the extension, and Google has said as much about new gTLDs generally. What .wiki does influence is behaviour once a link or search result is in front of a visitor. An address ending in .wiki sets an accurate expectation — structured, collaboratively maintained reference content — which tends to improve click-through and reduce bounce for exactly the kind of pages that live there, because visitors are not surprised by what they find.

For branding, the extension does useful narrative work on its own. brand.wiki tells a new visitor, a journalist, or a search engine result skimmer that this is a living reference rather than a marketing page, without needing a tagline to explain it. That framing also matters for trust: readers are generally more forgiving of gaps or in-progress sections on something explicitly labelled a wiki than they would be on a page presented as finished, polished content. Combine that with genuinely well-organised articles, clear internal linking between related entries, and a stable domain that does not change hosts every year, and a .wiki site can build the kind of durable topical authority search engines reward over time — the extension frames the content correctly; consistent maintenance earns the ranking.

Against .com, the trade-off is precision versus universal familiarity. .com is the address most people type from habit and assumes nothing about content format; .wiki tells a visitor immediately that they are looking at reference material meant to be edited, which a generic .com cannot communicate on its own. For a community knowledge base or documentation project, that clarity is often worth more than the extra familiarity of .com, though many teams still register the matching .com defensively and redirect it.

Against .org, both endings carry a sense of community and non-commercial purpose, but .org is broader — it fits nonprofits, associations and open projects generally — while .wiki is specific to the collaborative-reference format itself. A project that is both a nonprofit and a wiki sometimes registers both and lets .wiki carry the actual content while .org anchors the organisation's identity.

Against .info, which was built as a catch-all for informational content, .wiki is the sharper choice whenever the content is genuinely collaborative and ongoing rather than a static set of informational pages. .info reads as "information about"; .wiki reads as "edited and maintained by us, together" — a meaningfully different promise to the reader.