Discord Bot Verification: The Complete Verified Bot Guide

Your bot is growing, the invite link is being passed around, and one day you notice it can no longer join new servers. This is exactly where Discord bot verification comes into play. Discord requires an official verification from every application that crosses the 100-server threshold; without completing this step your bot cannot join servers beyond 100. In this guide I explain exactly what happens at the threshold, how the verification application works, how privileged intent approval fits in, and the practical ways to get through the process smoothly.

Why does the 100-server threshold exist?

Discord's reasoning is simple: a small bot is experimental, but a bot reaching hundreds of thousands of users is a serious responsibility. Before reaching 100 servers you can develop and test freely; no approval is needed. The moment your bot joins its 100th server nothing self-destructs, but from that point on it must reach verified status to keep joining new servers. So verification is really a milestone you should plan for while the bot is still small; preparing the application at server 50 is far more comfortable than panicking at server 99.

Preparing before you apply

The verification application asks you to clearly describe what your bot does and how it uses data. Before opening the application, have the following ready:

• A clear bot description: Explain the core function, which commands it offers, and which data it touches, in plain language.
• Privileged intent justifications: If you use the GUILD_MEMBERS, PRESENCE or MESSAGE_CONTENT intents, explain why each is needed with a concrete example.
• Privacy policy and terms of service: For a bot that processes data these are now an expected standard. Have them ready, even as a simple page.
• Team / identity details: Verification may require the application owner to confirm their identity; you'll need a valid ID document for this step.

Privileged intents: the real crux of verification

Most developers think verification is only about "unlocking the server limit", when the genuinely demanding part is privileged intent approval. Discord sets apart three privacy-sensitive gateway intents:

• GUILD_MEMBERS — the member list, join/leave events, role changes.
• GUILD_PRESENCES — users' online status and activities.
• MESSAGE_CONTENT — the text content of messages (privileged since 2022).

While under 100 servers you can toggle these from the Developer Portal with a single click. But for a verified bot you must obtain separate approval for each privileged intent. The most common mistake here is requesting MESSAGE_CONTENT when you don't actually need it. If your bot works purely through slash commands, you usually don't need access to message content, and not requesting this intent speeds up your application.

In code, enable only the intents you genuinely use. A typical minimal setup with discord.js looks like this:

const { Client, GatewayIntentBits } = require('discord.js');

const client = new Client({
  intents: [
    GatewayIntentBits.Guilds,
    GatewayIntentBits.GuildMessages,
    // MessageContent only if you need prefix commands / reading text:
    GatewayIntentBits.MessageContent,
  ],
});

client.once('clientReady', () => {
  console.log(`Logged in as: ${client.user.tag}`);
});

client.login(process.env.DISCORD_TOKEN);

The golden rule here: the intent you request must match the intent in your code. If you say "I listen to member events for moderation" in the application but the GuildMembers intent isn't enabled in your code, or vice versa, the review takes longer.

The application process, step by step

1. Open your application in the Developer Portal and check, under the Bot tab, which privileged intents are enabled.
2. If possible, move your bot under a Team; this is healthier for both security and organizational visibility.
3. Fill out the verification application form: bot description, intent justifications, privacy policy link.
4. Complete the identity verification step if requested.
5. Submit the application and wait for the review period. This can range from a few days to several weeks, depending on volume.

Practical tips to avoid rejection

• Make justifications concrete. Instead of "I need member data", write "I listen to the GuildMemberAdd event to assign a welcome role when new members join".
• Don't request extra intents. Every privileged intent you enable means a separate justification and a separate review burden.
• Clarify your data retention policy. Do you store message content, and for how long? A clear answer builds trust.
• Keep your bot running. A bot that's unreachable or erroring during the review leaves a poor impression.
• Apply early. Start before you hit 100 servers so your growth momentum isn't interrupted.

What changes after verification?

Once approved, a Verified badge appears on your bot's profile and it can freely join servers beyond 100. That badge also reassures users; when adding an unfamiliar bot, being verified is a serious plus. Approved privileged intents are permanent, but if you significantly change the bot's behavior (for example, start collecting new data) you're expected to stay faithful to your privacy commitments. Verification isn't an end, it's the start of running a responsible bot.

Frequently Asked Questions

Do I need verification if my bot is under 100 servers?

No. Verification isn't mandatory under 100 servers, and you can enable privileged intents yourself from the Developer Portal. Still, if you're planning to grow, it pays to learn the process early.

Can I build a bot without the MESSAGE_CONTENT intent?

Yes. Most modern bots work with slash commands, buttons and menus; these interactions don't require access to message content. This approach is both privacy-friendly and makes verification easier.

How long does verification take?

There's no fixed duration; it usually ranges from a few days to several weeks. Having a clear application, concrete justifications, and requested intents consistent with your code noticeably speeds things up.

Want to get your bot ready for verification? Whether you want a clean intent architecture from scratch or you'd like me to prepare your existing bot for the verification application — for a solid, sustainable Discord bot, get in touch with me.