You drop a link in your Discord server. Maybe it's a YouTube video you want your community to discuss, a tool you've been testing, or an article that's directly relevant to a channel topic. For a second nothing happens. Then the embed appears: a generic site logo, a title that reads like a filing system label, and a description that's clearly a legal disclaimer or an SEO meta tag. Your members scroll past it.
This happens constantly in Discord, and it's not random. Discord's embed system has specific rules about what it reads and how it displays it — rules that most websites weren't designed with in mind. Understanding those rules is what separates a community that shares links professionally from one that looks like it was assembled with zero curation.
How Discord Embeds Actually Work
When you paste a URL into Discord, Discord's crawler (called Discordbot) fetches the page and reads its Open Graph metadata: the og:title, og:description, og:image, and og:site_name tags embedded in the page's HTML. It then renders these as an embed card — a contained block with a colored accent bar on the left side, the site name in small text above the title, and the image displayed either as a large banner below the description or as a smaller thumbnail to the right.
Discord also reads Twitter Card tags, specifically the twitter:card value. A value of "summary_large_image" tells Discord to display the image as a full-width banner. Without it, Discord may render the image as a compact thumbnail or skip it entirely, depending on how the og:image dimensions are interpreted.
The embed is cached. Discord stores what it finds the first time a URL is shared and reuses that data for subsequent shares. If you share a URL, then the source page updates its metadata, later shares in other servers or channels may still show the old version until the cache expires.
Why Most Links Look Bad in Discord
Most web pages were built for search engines and for Facebook's original Open Graph implementation. Their og:title is optimised for keyword ranking, not for a conversational platform where someone is about to decide in two seconds whether your recommendation is worth their time. Their og:image is a product hero shot sized for a news feed, not a Discord embed window. And their og:description is a legal notice, a boilerplate brand statement, or a truncated excerpt from the first paragraph.
Redirect URLs are a specific failure case. If you're sharing a referral link, a link shortener, a tool's affiliate URL, or any link that bounces through a redirect layer, that redirect page almost never has OG metadata. Discord's crawler follows the redirect, arrives at the destination, and either renders the destination's generic tags or produces a blank embed with nothing but the domain name. Either result misrepresents what you're sharing.
YouTube and Twitter links are the exception, not the rule. Those platforms have invested in making their embeds look good everywhere because it benefits them. Most other sites haven't made that investment, and it shows.
Why This Matters More in Discord Than Elsewhere
Discord communities operate on trust. Your members follow you into a server because they believe you'll surface things worth their attention. Every link you share is an implicit endorsement — and the embed is the first signal they use to evaluate whether to click.
A broken or generic embed creates a moment of friction. The member can't quickly tell what they're about to click into. They slow down, they question it, and often they keep scrolling. The same link with a clear image, a headline written for context, and a description that explains why it's relevant would have earned the click without that hesitation.
For content creators who run Discord communities alongside YouTube channels, newsletters, or podcasts, this friction compounds. You've already done the work of building an audience and directing them to a server. Every low-quality link embed quietly chips away at the signal-to-noise ratio that makes your community worth staying in.
What You Can and Can't Control
If you own the destination, you can fix the OG tags directly, update the title to something that lands in context, swap the image for one that works at Discord's embed dimensions, and write a description that speaks to your specific audience rather than to a search engine. For pages you control, this is the right approach.
But most of the time, you're sharing content you don't own: someone else's article, a SaaS tool you're recommending, a product from a brand you work with, a resource you found useful. You have no access to the page's HTML. You're at the mercy of whatever metadata the site's developers set, however long ago, for whatever purpose they had in mind.
Controlling the Embed Without Controlling the Page
The solution is to put a preview layer between your link and the destination. Instead of sharing the raw URL, you create a hosted page that carries your custom OG metadata and then transparently redirects real visitors to the original destination. Discord's crawler reads your title, your description, your image. Your members click and land exactly where they expected. Nothing about the experience changes for them.
This is what Prelinq is built for. You paste the destination URL, write the title that gives your members the context they need, add a description that frames why you're sharing it, and pick an image that signals the content clearly. Prelinq generates a link at prelinq.com that carries your metadata. When Discord's crawler visits it, it finds exactly what you configured. When your members click, they reach the original page.
Because each Prelinq URL is distinct, you can share the same source article in different channels with different framing. The same tool review shared in a beginner-focused channel and in an advanced-users channel can have different titles and descriptions, each written for the people in that specific channel. The destination is identical. The first impression is tailored.
A Concrete Example
Say you run a design community and you want to share a color palette generator tool. The raw URL embeds with the site's default title ("Coolors — The Super Fast Color Palettes Generator!"), a generic description, and a marketing hero image designed for a landing page. Useful enough, but generic.
With a Prelinq, you share the same tool with the title "Free color palette generator — great for finding accessible combinations", a description that speaks to why your community specifically would find it useful, and a screenshot of the tool in use rather than the marketing image. That embed tells your members something. It earns the click.
Start With Your Next Share
You don't need to go back and fix every link you've ever shared. Start with the next one. Before you paste a URL into Discord, ask whether the default embed is going to give your members the context they need to click with confidence. If it will, share it as-is. If it won't, spend sixty seconds creating a Prelinq that does.
The communities that feel curated aren't the ones where the admin posts more often. They're the ones where every shared link feels intentional — like someone read it, understood it, and decided it was worth the community's time. The embed is how you signal that before anyone clicks.