twimco.Let’s talk ↗︎
Menu
Field notes / AI in practice

Your Discord help channel is about to become a search result. Use the two dates to decide what it says

If your product's community lives on a public Discord server, the answers your members give each other in #help will start turning up in web search from mid-December. That's free reach and a new support risk at the same time. Here's what to do before November 16, and what to do before December.

Editorial engraving of a sunny board-game café where a community manager sorts channels into public and private while a moderator shows a pinned answer on his phone.

Discord will give every Discoverable Server (public, 1,000+ members) a Server Web Page on November 16, 2026, with automated channel summaries, and from mid-December messages from public channels can appear on that page and in web search, without usernames or avatars. Admins choose channels in Server Settings > Community > Web Presence; everything public stays on by default. Before November 16, pick which channels should be public answers. Before December, make sure the answers people will find there are right.

What Discord announced

On October 27 Discord announced that conversations in its most public communities will become findable on the open web. It affects Discoverable Servers only: servers with at least 1,000 members, at least eight weeks old, that meet Discord's activity and safety rules and that chose to be listed so anyone can join. Discord says there are more than 63,000 of them. Private servers, DMs and group DMs aren't included.

There are two dates.

November 16, 2026. Every Discoverable Server gets a Server Web Page, a public page describing the community. If your team hasn't set one up, Discord publishes a default page using your server profile. The page can also show Channel Summaries: automated summaries of active conversations from November 16 onward, without usernames or avatars.

Mid-December 2026. Messages from public channels can start appearing on that page and in web search, in members' own words, again without usernames or avatars. Messages sent before then won't be shown, and channels that may appear on the web will be labeled. The rollout is gradual, so it may take a few weeks for the first messages to show up.

Admins control which channels take part in Server Settings > Community > Web Presence, on desktop or in the browser. If you change nothing, public channels stay on. Members can turn their own messages off in User Settings > Data and Privacy, one switch for every Discoverable Server they're in.

Sequence of work

Two dates, two jobs

  1. Now

    Controls live in Server Settings > Web Presence.

  2. Nov 16

    Server Web Pages and Channel Summaries go live.

  3. Mid-December

    Public channel messages start appearing in search.

  4. After

    Best answers move into maintained help content.

Dates from Discord's Oct 27, 2026 announcement; the jobs are the studio's suggestion.

Why a product team should care

Discord pitches this at fandoms and indie game developers, and it'll help them. But plenty of software companies, hardware brands and developer tools run their community and much of their support on a public Discord server. For them, #help, #troubleshooting and #feature-requests are about to become public documents.

That cuts two ways. The good side: answers your community has written for years become findable by people who'd never have joined the server. Search engines, and the AI assistants that read search results, get a new source of real answers about your product.

The risky side: a lot of those answers are wrong, outdated or written for a version you retired. A member's workaround from last spring, a moderator's guess about a release date, an argument about pricing. None of it shows usernames, but all of it appears under your community's name. The question isn't whether people will find your community's answers. It's whether the answers they find are still true.

The question isn't whether people will find your community's answers. It's whether the answers they find are still true.

Before November 16: decide which channels speak for you

The first job is sorting channels. Open Web Presence with your moderators and go through the list.

  • Keep on: channels where the answers are good and stable, like a curated FAQ channel, a forum channel for how-to questions with resolved threads, or an announcements channel.
  • Turn off: channels for bug reports, billing, account problems, beta testers, off-topic chat and anything where people paste logs or screenshots. Even without usernames, a pasted error log can contain more than you'd want indexed.
  • Think hard about: general help channels. They're the most useful and the messiest. If you keep them on, plan to moderate them as if they were public pages, because they will be.

Check the default Server Web Page too. If Discord builds it from your server profile, make sure the description, links and rules there are current. And review Channel Summaries: admins can choose which channels they draw from, curate what's shown or turn them off.

If the honest answer is that you don't want any of this, Discord's route out is to stop being a Discoverable Server and switch back to a Community Server. That keeps the community but gives up being listed in Server Discovery.

Decision guide

Which channels to leave public

ConsiderationLeave onTurn off
AnswersCurated FAQ and resolved how-to threads.Unmoderated guesses and old workarounds.
NewsAnnouncements and changelog posts.Release-date speculation.
SupportGeneral help, if moderated as public.Billing, accounts and pasted logs.
TestingPublic feature discussion.Beta and private testing channels.
Decision framework for sorting channels; illustrative.

Before mid-December: make the public answers good

Messages sent before mid-December won't appear, so you have about six weeks to set habits for what comes after.

  • Pin and close. In forum channels, mark the accepted answer and close resolved threads, so the best reply is the one people see.
  • Correct in the channel. When a moderator spots a wrong answer, reply with the right one and a link to your docs, rather than deleting quietly.
  • Point at the source of truth. Encourage moderators to answer with a link to your help center or changelog. The public answer then carries people to the page you maintain.
  • Tell members. Post a short note explaining what's changing, which channels are on and how members can opt out. Discord labels channels that may appear on the web, but your own words will land better. Some members will opt out, and that's fine; respect it and don't ask them to explain why.

Where your own assistant fits

If your community is a big source of answers about your product, it's worth asking where those answers should live long-term. A public Discord channel is good for conversation and poor at being correct over time.

The durable fix is to turn the best community answers into maintained help content, and to have your own support assistant answer from that, with links back to the conversation where it helps. An assistant that answers from your docs and reviewed community answers, and says when it doesn't know, beats a search result that quotes a stranger's guess from last March.

The community still matters in that setup. It's where new questions show up first, often weeks before they reach a support ticket. Treat the public channels as an early signal: when the same question appears three times in a week, that's a help article missing. When a member's answer is better than yours, ask if you can use it. Over time the community writes the first draft and your team keeps it right, which is a better division of work than hoping search engines pick the correct reply.

The plan on one page

This week: open Web Presence, sort channels, check the default page. By November 16: channels set, summaries reviewed, members told. By mid-December: moderators pinning, correcting and linking. After that: move the best answers into your help center.

If you'd like help building an assistant that answers from your own content and keeps up with your community, our AI applications and agents team does that work. Talk to us.

Related work: Spin Market.

twimco.

We build alongside the people doing the work.
Bring us the problem you’re thinking about.

Related work

Spin:Market ↗︎