Back to the journal

Community

A Discord invite that does not die inside Instagram

Invites expire. Bios get screenshotted. Put a never-expire invite on a hub you control, label it like a room with rules, and keep the Instagram Website field on that hub.

September 26, 20265 minLinkForge Editorial

Discord invites expire, hit member caps, or get revoked after a raid. Instagram bios are screenshotted, saved in notes apps, and tapped months later by someone who finally has time. If the Website field is a raw discord.gg/abc123 and that code dies, every old screenshot is a dead end you cannot edit. You will not find all the screenshots. You can only change what the official profile points at — unless the official profile points at a page you control, and Discord is a button on that page.

When the Reel is “join us for the watch party,” Discord can be the hero button this week. It should almost never be the only URL in the Website field for the life of the account. You will sell a PDF, a ticket, or a calendar later. The hub absorbs that without a new bio.

Create the invite you mean to keep

  1. In the server, open the invite dialog. Set expiration to never, unless you have a reason to rotate (a raid, a leaked code, a cohort that should close). Set a member cap only if you can actually moderate the cap.
  2. If Discord has granted a vanity URL (discord.gg/yourname), use that on the button. Vanity is memorable. It is still a single destination. Put it on the hub, not as the Instagram field, because the day you add a shop you will want two buttons.
  3. Write the button label as a room, not a brand: “Join the server — rules are in #welcome,” or “Watch-party chat (starts 20:00 CET).” “Discord” alone does not say whether they are joining a class, a fandom, or a support line.
  4. Publish the hub and set Instagram → Website to the hub. Create the hub. Free covers five links and per-link analytics. Pro at 7€/month is the domain you can print on merch without sending people through a tool name, with SSL.
  5. Pin a welcome message that matches the button. If the Instagram caption says “introduce yourself in #welcome,” the channel must exist and must be readable by new members. A mismatch is how people join and leave in a minute, convinced the server is abandoned.
  6. Test the invite while logged out, on a phone that does not already have the server. Some invites bounce into an app-store loop. If that loop is the first experience, fix it before you spend a Reel on it.

When Discord is the wrong first button

  • The content was a product drop. The hero is the product. Discord can be “questions and restocks” underneath.
  • You cannot moderate. A public never-expire invite with no mods is a spam magnet, and the spam will wear your name.
  • The server is adult and the Instagram audience is mixed-age. Do not hero it. A warning page still sends minors one tap away. If you cannot separate the audiences, do not use the bio as the funnel.
  • The server is for paying members. A public invite that lands in a locked channel feels like a bait. Either explain “you’ll see the lobby; the class is for patrons” on the hub, or keep the invite off the public page and send it after payment.

Telegram is a different crowd and a different rot pattern (private t.me/+ links). Some pages need both, with one hero. The parallel setup is a Telegram channel in the bio. Email is the asset you own if the server disappears; signup from the bio is how you collect it without making the server the only roll call.

If the bio is already a dead invite

You are in a hole until old screenshots age out, but you can stop digging.

  1. Create a fresh never-expire invite.
  2. If Instagram’s Website field is the dead code, replace it with the hub today. New visitors recover immediately.
  3. Put the new invite on the hub as the first button, with one line: “If an old code failed, you are in the right place.”
  4. In the next three posts, say “the server link is the first button on my site,” not “Discord is in the bio,” so people look at the website row.
  5. If you still control the dead code, point it at a server you own only if Discord allows that edit. Often you cannot. Do not buy a “redirect the invite” service from a stranger.

Vanity URLs that you lose because of a badge change should be treated as a migration: hub stays, button updates, posts explain it once.

Moderation and the promise you make in public

The hub should state the tone of the room in one sentence: “Work-in-progress critique, no client poaching,” or “Match-day chat, memes allowed, hate speech removed.” People self-select. You still need mods for the ones who do not.

Do not promise “I’ll answer everyone in Discord” unless you will. A label like “community chat, I read it on Sundays” is calmer and true. Support for paying customers belongs on a form or email with an order number, not in a public channel where refund details become entertainment. The open-source maintainer version of this boundary — security reports never go to a public Discord — is the strict case. A creator server can be warmer and should still keep private data out.

What to measure

Per-link analytics tell you whether the Discord button is the thing people came for. If a product Reel sends everyone to Discord and nobody to the shop, either the spoken ask was “join the chat” or the shop button is unclear. Fix the label or the video. Do not add a second invite “to see if it converts.” One door, one server, unless you truly run two communities with two purposes.

Once a month, tap the button from a logged-out phone. Confirm it still resolves, the welcome channel matches the label, and you would be willing to greet the person who joins. Renew that willingness or close the invite. An open door you resent becomes a server you do not moderate.

Keep Instagram pointed at the hub. Let the invite live on a button you can replace in one edit the day the code leaks, the cohort ends, or the shop becomes the point of the Reel.

Create my page — Pro is 7€/month (~$7)

Free to start. Pro is 7€/month (~$7 depending on exchange) for a custom domain and full SEO controls.