Discord’s Discovery activity requirements are measured as proportions of the people who join your server, so your total member count and your daily message volume never enter the calculation. A server with 90,000 members can fail on a weak retention proportion. A much smaller community of 1,200 passes comfortably, because a bigger share of its joiners stay and talk. That is why the support threads on this are full of owners running 12k, 70k and 147k servers who cannot work out what they did wrong. You are looking at a ratio problem, and growing faster is usually what caused it.
Table of Contents
Discord Publishes Most of the Thresholds and Hides One
The official requirements list for enabling Server Discovery has six items on it, and five of them come with a number or a setting you can check in under a minute.
- Your server must have at least 1,000 members.
- Your server must be at least 8 weeks old.
- The Community safety requirements must be switched on.
- The 2FA Requirement For Moderation setting must be enabled.
- Your server name, description and channel names must read cleanly.
- Your server must meet certain activity requirements.
That last line is the whole article. Discord describes the activity requirement without publishing what it is, anywhere in its help centre. The figures your server is currently measured against appear inside the Discovery tab in Server Settings, and most owners have never opened it after the initial setup. Go and look before you change anything, because the panel tells you which requirement you are failing and everything below assumes you know that.
Ratios Are the Reason Getting Bigger Makes This Worse
The obvious response to a failed requirement is to grow. Run a giveaway, get listed on every server directory going, and push the number up until Discord has to notice you. You were expecting me to say the requirement is a size gate, right? Every person who joins and never speaks lands in the bottom half of the fraction.
Think about what a retention measure and a communicator measure actually count. Retention asks how many of the people who joined recently are still around. The weekly communicator figure works differently, counting the members who sent at least one message inside a seven day window. Both compare a small active number against a large total number. A community of 90,000 where 3,000 people talk in a given week has a worse communicator share than a community of 2,000 where 400 do, even though the bigger server generates more than seven times the chat.
Which means every growth tactic that brings in browsers rather than participants moves you further from qualifying. The giveaway that added 8,000 members in a weekend did real damage that will show up two weeks later.
Discovery Itself Feeds the Loop That Removes You
This is the part that reads like a bug and is really just arithmetic. People who find your server through the Discover tab arrive with almost no intent. They were browsing a category, your card looked interesting, they clicked join. Compare that with somebody who followed an invite link from a friend who told them what the server was for.
The browsers join in volume, sit silently, and a large share of them leave within a fortnight. Every one of them lowers the retention proportion and the communicator proportion at the same time. So qualifying for Discovery starts a process that can disqualify you from Discovery. Owners in the support threads describe exactly this sequence, getting listed, watching their numbers sag, then receiving the warning within a month or two.
You cannot switch off the traffic, but you can change what happens to it. That is where the actual fix lives.
Several Gates Fail You Silently and Look Nothing Like Activity
Before you spend a month on engagement work, rule out the checks that have no relationship to activity at all. Any one of these can be what is really wrong.
- Your server name and description must accurately describe the server and be free of profanity. Vague or joke descriptions are a real failure mode here, and so are channel names that made sense to your regulars in 2023.
- Discovery Guidelines exclude servers built around controlled substances or drugs, servers dedicated to regulated goods such as alcohol, and graphic violence or sexual content in public spaces. Servers whose primary purpose is sexually explicit content are not eligible for Discovery at all.
- Community verification requires members to have a verified email on their Discord account before they can send messages or DM anyone in the server.
- The media content filter has to be set to scan media content from all members, so that potentially explicit content is caught and deleted.
- A rules channel and a moderator updates channel both have to exist and be assigned.
- Recent enforcement action against your server for a Community Guidelines violation removes you from Discovery regardless of how healthy your numbers are. Discord’s Trust and Safety team may temporarily join a server to investigate reports.
None of these produce a message saying which one you failed. They produce a server that is not in Discovery.
Where Your Real Numbers Live
Server Insights is available to servers above 500 members and holds data going back as far as 120 days for communities that are not Partnered or Verified. It is the only place you can see the shape of the problem rather than the verdict.
The invite source breakdown is the single most useful screen in it. Insights groups any referrer with fewer than 50 joiners into an “Other” bucket, so what you get is a clean view of your genuinely large traffic sources and how they compare on retention. Almost every failing server has one or two sources bringing in enormous numbers of people who never come back. Find them, then stop feeding them.
The Four Week Clock You Are Already On
The warning message is precise about what happens next. It reads: “This server has failed Discovery activity requirements for 1 week. If this server fails for 4 weeks in a row, it will be automatically removed from Discovery.”
Take that literally. The removal is automatic, there is no human reviewing your case, and appealing it is not a thing that exists. Four consecutive failing weeks and the listing goes. You get back in by meeting the requirement again, which means the work has to start in the week you receive the first notice rather than in the week you receive the fourth.
What to Change Before the Next Check
- Open the Discovery tab and write down which specific requirement is showing as unmet. Everything else is guesswork until you have done this.
- Turn off your worst invite sources. Directory listings and giveaway campaigns that deliver silent joiners are actively costing you the listing.
- Build one easy first message. An onboarding question works, or an introductions channel with a prompt short enough to answer in three words. People who send one message during their first week are far more likely to send another.
- Use the welcome screen to point new arrivals at one channel. A wall of forty channels is how a curious visitor becomes a silent member.
- Fix the safety settings and the 2FA requirement in one sitting, then assign the rules channel and the moderator updates channel. That is five minutes of work removing several possible causes at once.
- Read your server name, description and channel names as a stranger would, then rewrite anything that does not say plainly what the community is for.
One tempting move is worth arguing against. Mass-kicking inactive members to improve your percentages is a guess, and owners have already filed requests asking Discord to stop counting kicks and bans against retention figures, which suggests the purge does not do what people hope. You would be removing members who might come back in order to fix a number you cannot see. Fix the arrival experience instead, and let the ratio recover from the top.