For years, Discord has been the place communities go to talk, and the place good answers go to disappear.
If you’ve run a server, you know the pattern. Someone asks a question in #help, a moderator or a helpful regular answers it, and three weeks later someone asks the exact same thing. The answer exists. It’s just buried somewhere nobody outside your server, and honestly most people inside it, will ever find.
That’s about to change. On October 27, Discord announced that public channels in its Discoverable Servers will start showing up on the open web, and eventually in search results. If you run one of those servers, your community is about to become part of what Google, and the AI tools built on top of search, say about your product.
We spend most of our days inside Discord servers with game studios and software teams, so we’ve been thinking a lot about what this means. Below is what’s actually changing, which channels we think are worth keeping public, and a few honest risks to plan for. If you’re an admin, the date to remember is November 16.
Here’s what Discord is actually changing.
First, this only applies to Discoverable Servers, the ones anyone can join without an invite. To qualify, a server needs at least 1,000 members, has to be at least eight weeks old, and has to meet Discord’s activity and safety requirements. Discord says there are more than 63,000 of them. Private servers, DMs, group DMs and role-restricted channels are never included.
If your server qualifies, two things are rolling out:
- November 16: Server Web Pages and Channel Summaries. Every Discoverable Server gets a public web page that anyone can view without a Discord account, and that search engines can index. Those pages can include Channel Summaries, which Discord writes with AI from recent conversations in your public channels.
- Mid-December: Channel Messages. Individual messages from public channels start appearing on those pages and in search results, in the member’s own words, without usernames or avatars. Discord says the rollout is gradual, so the first messages may take a few weeks to show up.
The part worth paying attention to is that all of this is on by default. If you don’t change anything, your public channels are included. Admins can choose which channels take part under Server Settings > Community > Web Presence, with separate controls for summaries and messages. You can also turn discoverability off entirely, which takes the page down.
Members get their own setting under User Settings > Data & Privacy that keeps their messages off the web. It only works going forward: messages sent while it was on can still appear unless they’re deleted. It’s on by default in most regions, but off by default in the EU/EEA, UK, Canada, Brazil, Australia and South Korea, and teen accounts are excluded entirely. That setting only covers messages, though. Summaries stay up unless an admin turns them off.
Two more details matter for planning. Only new conversations count. Summaries draw on conversations from November 16 onward, and messages sent before mid-December aren’t included, so your existing history isn’t going public. And deleting a message removes it from Discord’s page, but search engines may hold onto cached copies for a while.
Small shift, big impact.
Discord says it plainly in its own announcement: before Discord, message boards were everywhere, from community-run forums to official ones run by game studios. A lot of those conversations moved into Discord servers, and when they did, they left the open web. Years of patch discussions, troubleshooting threads and “how do I do X” answers ended up somewhere search engines couldn’t see.
This change brings some of that back. But search looks very different now than it did when forums were the norm. People don’t just type keywords and click a link anymore. They ask Google and get an AI Overview, or they ask ChatGPT, Perplexity or an agent, and those tools build an answer from whatever they can find on the web.
Community conversations are some of the most useful material those tools can find, because they’re specific and recent. A product page tells you what a feature is supposed to do. A community thread tells you it broke after last Tuesday’s update and how people got around it.
So here’s the practical question for every team with a public server. When someone asks an AI tool about your product, do you want the answer built from your patch notes and your team’s verified answers, or from an old Reddit thread and a wiki nobody has updated since launch? Until now, Discord wasn’t part of that answer at all. Starting this month, it can be.
One note on AI specifically. Discord’s announcement doesn’t mention AI crawlers or model training, and Discord has said it doesn’t sell messages to AI companies. We’d still treat a public page as readable by any tool that reads the web, because that’s how public pages work.
Not every channel should be public. Here’s how we’d think about it.
The question isn’t really whether to make channels public. If you run a Discoverable Server, your public channels are already in. The real decision is which ones to leave in, and that comes down to what each channel is for.
Patch notes and announcements: keep them in.
This is the easiest call, and probably the most valuable one. Patch notes and announcements are written by your team, they’re accurate, and they’re exactly what you want an AI tool to repeat when someone asks “did they fix the crash on launch?” or “what changed in 1.4?”
Because your staff writes them, they also don’t depend on member settings, so they’ll show up consistently. That’s how Discord ran its own pilot: on servers like NBA 2K, Rust and Dead by Daylight, every published post came from admins and moderators.
FAQ, help and support: keep them in, but tidy up first.
This is where people are searching for answers, so it has a lot of value. But it’s messier than it looks. If the person who answered a question has turned off the member setting (which is the default for everyone in Europe), the page might show the question without the answer. And an AI summary of a long back-and-forth won’t always land on the right conclusion.
If support matters to you, have your team post the confirmed answer in its own message, or move common questions into a forum channel with a pinned staff answer.
Guides, builds and tutorials: keep them in.
This is the content Discord clearly has in mind, like builds, strategies and boss guides. For software teams, it’s config examples, workarounds and setup tips. It’s the stuff people already search for and currently can’t find.
Bug reports and feedback: decide on purpose.
There’s a good case either way. Being open about known issues builds trust, and it means an AI tool can tell someone “yes, that’s a known bug, here’s the workaround” instead of guessing. On the other hand, an AI-written summary of your bug channel could become one of the first things people see about your product, and it won’t include any of the context your team has.
If you keep it in, pair it with a known-issues post your team keeps up to date.
General chat and off-topic: we’d leave these out.
There’s very little search value here, and it’s where people talk the most casually. Even without usernames, most members didn’t join your server expecting their small talk to end up on Google.
Beta, NDA, playtest and mod channels: make them private.
You can exclude these in Web Presence, but role-restricting them is the safer move. Private channels are never included, no matter what the other settings say.
| Channel | Our take | Why |
|---|---|---|
| Patch notes, announcements | Keep in | Staff-written, accurate, and what you want AI tools to repeat |
| FAQ, help, support | Keep in, after cleanup | High search value, but member answers may be missing |
| Guides, builds, tutorials | Keep in | Exactly what people are searching for |
| Bug reports, feedback | Decide on purpose | Transparency vs. an AI summary of complaints |
| General, off-topic | Leave out | Low value, and members expect it to stay casual |
| Beta, NDA, playtest, mod | Role-restrict | The only guaranteed way to keep them off the web |
If a channel is public, make it worth finding.
A public channel only helps if what’s in it holds up when someone reads it out of context, months later, through a search result or an AI answer. A few habits go a long way:
- Name the version. “Fixed in 1.4.2” is useful forever. “Fixed in the latest patch” turns wrong the moment you ship the next one.
- Put the answer in one message. An answer spread across fifteen replies is hard for people to follow and hard for AI to summarize correctly.
- Use real names. Call features and products what your users and your docs call them, not internal nicknames.
- Correct wrong answers where they live. If a wrong answer is sitting in a public channel, reply to it in the channel. Otherwise it may be the version that gets quoted.
- Update your server profile. If you haven’t set up a Server Web Page, Discord builds a default one from your server profile, so make sure it describes your community accurately.
- Post a “current state” message in December. Older messages aren’t included, so a short, up-to-date summary in your key channels after mid-December gives search something accurate to work with from day one.
There are real tradeoffs, and your members deserve a heads-up.
We think this change is a net positive for most communities, but it’s worth going in with eyes open.
Summaries can be wrong. Discord’s own help page says Channel Summaries may not always be accurate. They’re on by default, and members can’t opt out of them, so if a summary of a channel would misrepresent your community, the fix is on the admin side.
Your members joined a chat, not a forum. Usernames and avatars are stripped, but people’s words show up as they wrote them. Discord will mark participating channels and show members a notice, but it’s better if they hear it from you first. Tell them which channels are included and why, and point them to the setting in Data & Privacy if they’d rather opt out.
Removal isn’t instant. Turning a channel off stops new content from being added, but anything already published stays until the original message is deleted, and search engines may keep cached copies even after that. Make your channel decisions before content goes out, not after.
Expect fragmented threads. Between regional defaults and individual opt-outs, some conversations will show up with pieces missing. That’s one more reason to have your team post complete answers in the channels that matter most.
What we’d do before November 16.
If you run a Discoverable Server, here’s a short list to get through before summaries go live:
- Check whether your server is Discoverable under Server Settings > Access > Discoverable. If it isn’t, none of this applies yet.
- Open Server Settings > Community > Web Presence and go through your channels one at a time, for both summaries and messages.
- Role-restrict anything under NDA, in testing, or meant for moderators only.
- Update your server profile so your default web page describes your community accurately.
- Post an announcement telling members what’s changing, which channels are included, and where to find the opt-out setting.
- Put a reminder on the calendar for mid-December to post “current state” messages in your most important channels.
We’ll be watching how this rolls out across the communities we work with, and we’ll share what we see once messages start appearing in December.
And if you’d like a clear picture of what’s already being said in your public channels before it’s on Google, that’s a big part of what we built Kinn to do. It connects to Discord and all of your community spaces, letting you ask questions about your community in plain language, with every answer linked back to the original messages.
