Discordbot user agent
Discordbot is the crawler Discord uses to fetch a URL shared in a channel so it can render the embed preview from Open Graph and oEmbed metadata. It is a link-unfurling bot, not a human visit, and identifies itself with a documented Discordbot user-agent token plus a self-identifying URL.
What this means
When a link is posted in Discord, Discord fetches the URL to build the embed — the inline card with title, description, and image. Discord reads Open Graph and standard meta tags, and supports oEmbed for some providers.
The embed reflects the metadata Discordbot read, not a human reading the page. Discord respects robots.txt for these fetches, so disallowing the Discordbot token suppresses the embed.
How Discordbot identifies itself
Discord's crawler uses the user-agent token Discordbot, and its user agent includes a self-identifying URL. Match on the stable Discordbot token rather than a version suffix.
The user agent is a claim and can be copied. Discordbot reads server-rendered tags; it does not execute client-side JavaScript to assemble the embed.
- User-agent token: Discordbot
- User agent includes a self-identifying Discord URL
- Reads Open Graph / meta tags; supports oEmbed for some providers
Debugging a missing embed
If a Discord link shows no embed, confirm the page returns 200 with valid Open Graph tags in the initial HTML, and that robots.txt does not disallow the Discordbot token. Redirects and login walls can also block the fetch.
Seeing the Discordbot token in your logs for the shared URL confirms the embed fetch reached your server.
How it appears in analytics and logs
A request carrying the Discordbot token means Discord fetched a URL to build an embed. It is triggered by a message and is bot traffic; a short burst when a link is posted is normal, not audience growth.
Diagnostic use case
Confirm whether Discordbot fetched a shared page, debug a missing or wrong Discord embed, and keep its requests out of human analytics.
What WebmasterID can help detect
WebmasterID classifies Discordbot server-side as a social-preview bot and surfaces its fetches on the bot-intelligence view, so embed crawls do not inflate human page views or look like referrals.
Common mistakes
- Disallowing Discordbot in robots.txt and then expecting embeds to render.
- Counting Discordbot embed fetches as human visits.
- Relying on JavaScript-injected meta tags Discordbot does not execute.
Privacy and accuracy notes
Discordbot detection uses only the user agent. No human identity is associated with the embed fetch. WebmasterID records it as a social-preview bot event, separate from human analytics.
Frequently asked questions
- Why does my Discord link not show an embed?
- Discordbot could not read valid Open Graph metadata, or robots.txt disallows the Discordbot token. Confirm a 200 response with og: tags in the initial HTML and an unrestricted robots.txt.
Related pages
- Slackbot user agent
Slackbot is the crawler Slack uses to fetch a URL shared in a channel or DM so it can build the message unfurl from Open Graph (and where supported oEmbed) metadata. It is a link-unfurling bot, not a human visit, and identifies itself with a documented Slackbot user-agent token plus a self-identifying URL.
- TelegramBot user agent
TelegramBot is the crawler Telegram uses to fetch a URL shared in a chat so it can render the link preview from Open Graph and standard page metadata. It is a preview-generation bot, not a human visit, and identifies itself with a documented TelegramBot user-agent token.
- Social preview bot user agents
When someone pastes your link into a social or messaging app, a preview bot fetches the page to build a card from your Open Graph and Twitter Card tags. Bots like facebookexternalhit, Twitterbot, Slackbot, Discordbot, and LinkedInBot identify themselves by token. This page covers what they are and why they hit you.
- Bot intelligence
Server-side classification of embed and preview crawlers.
Sources and verification notes
- Discord — Embeds (developer docs)Discord builds embeds from page metadata fetched by Discordbot.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.