# Discord App Directory verify and enable discovery before promo

> Finish Discord app verification and discovery opt-in before you push traffic, because the App Directory and App Launcher only start working after approval and can take up to 24 hours to populate.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/discord-app-directory-verify-and-enable-discovery-before-promo/
- Source: [docs.discord.com](https://docs.discord.com/developers/discovery/enabling-discovery)
- GrowthDex source hub: [Discord Docs: Enabling Discovery](/sources/discord-docs-enabling-discovery-docs-discord-com/)
- Last checked: 2026-06-05T05:15:00Z
- Rarity: rare
- Budget: free
- Channels: Communities, Marketplaces, Launches
- Stages: discord, app directory, launch timing, verification
- Key metric: Discovery can take up to 24 hours before the app appears in the App Directory and App Launcher.

## Why this can grow

A lot of Discord app launches start with social posts, creator seeding, or community announcements before the app can actually be found inside Discord. Discord is explicit that an app needs verification, discovery qualification, and discovery opt-in before it can appear in the App Directory and App Launcher, and even then it can take up to 24 hours to show up. That means discovery status is part of launch timing, not an admin chore. If you send people early, they cannot search, inspect, or install through the native surfaces you are claiming to have live.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. I would treat this as earning the right to be in the room, not dropping a campaign into a room. In community-led growth, the first job is to notice what people already care about, then bring a useful proof, tool, teardown, or question that makes the conversation better. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where discord app directory verify and enable discovery before promo can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Communities and Marketplaces channel.
3. Use the evidence from docs.discord.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Discord's Enabling Discovery guide says apps must complete verification and discovery qualification, then enable Discovery, and that it may take up to 24 hours for the app to appear in the App Directory and App Launcher.

## Adjacent tactics in the same lane

- [Salesforce AppExchange security review parallel with listing design](/growth-ideas/salesforce-appexchange-security-review-parallel-with-listing-design/) - 2 shared channels, 1 shared stage
- [Chrome Web Store deferred publish window after review](/growth-ideas/chrome-web-store-deferred-publish-window-after-review/) - 2 shared channels, 1 shared stage
- [Discord App Directory install link before page polish](/growth-ideas/discord-app-directory-install-link-before-page-polish/) - 1 shared channel, 2 shared stages
- [Discord App Directory summary names the server job](/growth-ideas/discord-app-directory-summary-names-the-server-job/) - 1 shared channel, 2 shared stages

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The Discord app page should finish the Add App click](/blog/the-discord-app-page-should-finish-the-add-app-click/) - community-led growth, brand trust, onboarding

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.