A solo marketer with fifty short links can keep them in their head. A five-person team producing links for email, social, paid, events, and three product lines cannot — and the failure mode is predictable. Six months in, the account holds nine hundred links named things like test2, final-FINAL, and sarah-campaign, nobody knows which ones are still live in the wild, and a link printed on last year's conference banner redirects to a landing page that was deleted in a website migration.

None of that is a tooling problem. It's a process problem, and the process is not complicated — it just has to exist before the mess does. This article lays out the pieces: naming conventions, shared workspace structure, campaign taxonomy, pre-launch QA, periodic audits, and a governance checklist you can adopt as-is.

Naming conventions: the foundation everything sits on

Every link in a shared account needs a name that answers three questions at a glance: what campaign is this, where is it placed, and who would know more? A convention that works for most teams:

{campaign}-{channel}-{placement}

So a spring product launch produces spring26-email-header, spring26-li-post1, spring26-podcast-shownotes. Rules that make it stick:

Lowercase and hyphens only. Mixed case and underscores breed duplicates (Spring26_Email vs. spring26-email), and hyphenated slugs read better if the alias is ever public-facing.
Fixed vocabulary for channels. Publish a short list — email, li, ig, tt, x, paid, qr, pr — and reject inventions. The vocabulary going stale is fine; two words for the same channel is not.
Campaign token defined at kickoff. The campaign brief names the token (spring26) before any links exist, so nobody improvises.
No names, no dates in the slug unless the date is the campaign (the owner lives in the link's notes field or your tracker, and dates are in the metadata already).

The payoff is compounding: dashboards sort into campaign groups automatically, searches work, and the naming carries straight into your UTM values so shortener data and site analytics line up. Keep the two aligned — the slug's channel token should match utm_source/utm_medium per the conventions in our UTM parameters guide.

Shared workspaces and access

Links created under personal accounts are the original sin of team link management. The person leaves, the account lapses, and every link they made — some printed, some in evergreen video descriptions — dies with it. The rules:

One team workspace owns all links. Personal accounts are for personal links. If the tool supports roles, most members need create-and-edit; deletion and domain settings stay with one or two admins.
A custom domain the company controls, registered under company infrastructure, not an employee's registrar login. The domain is the migration insurance policy — as covered in our comparison of URL shorteners, links on your own domain can survive a provider switch; links on a shared generic domain cannot.
Agencies get scoped access, not credentials. If you work with external partners, use separate workspaces or client-scoped setups — the agency white label arrangement exists for exactly this — so offboarding a vendor doesn't require an account migration.
Every link gets an owner recorded in its notes or your campaign tracker, because "whose link is this?" is the first question in every incident.

Campaign taxonomy: how links map to work

Naming tells you what a link is; taxonomy tells you how links relate. The useful mental model is a three-level hierarchy:

Level	Example	Lifespan	Review cadence
Evergreen	`docs`, `pricing`, `careers`	Years	Annual audit
Campaign	`spring26-*` links	Weeks to months	At campaign close
Experiment	`spring26-email-cta-a` / `-b`	Days to weeks	At test close

The distinction matters because the levels have different rules. Evergreen links deserve short, speakable aliases and extreme caution around edits — they're in printed material and old videos. Campaign links follow the naming convention and get formally closed (see auditing below). Experiment links are disposable by design, paired with the test log described in our A/B testing framework, and archived the moment the test concludes so they don't pollute dashboards.

Tag or group links by level if your tool supports it. When someone asks "can I change where this points?", the level answers the question: experiment links, freely; campaign links, during the campaign; evergreen links, only with a change record.

QA before launch: the five-minute check

Most link incidents ship at launch, and almost all are catchable in five minutes. Before any campaign goes out, someone other than the link's creator runs this on every link:

Click it. Not "look at it" — click it, and confirm it lands on the intended page, not a staging URL, a redirect chain, or a 404.
Click it on a phone, ideally inside the app where it will live (Instagram's in-app browser, a mail client), since that's where most real clicks happen.
Check the UTM values survive. Confirm the parameters appear in the destination address bar and match the campaign's naming sheet — a typo in utm_campaign writes garbage into your analytics for the campaign's whole life.
Verify the alias against the convention so the dashboard stays sorted.
For printed or broadcast links: test the QR code from the actual artwork at print size using a real phone camera, and say the URL out loud once — if it's ambiguous spoken (0 vs O), fix it now. Codes from the QR code generator wrap a short link, which means the destination stays editable after printing; that's your safety net, but it shouldn't be your plan.

Put this checklist in the campaign template so it's a launch gate, not a favor.

Auditing old links and fighting link rot

Links rot from the destination side: the short link works forever, but the page it points to gets moved, reworked, or deleted — most catastrophically during website migrations, when hundreds of destinations change at once. A team that has never audited its links has rot; the only question is how much.

The audit routine, quarterly for most teams:

Export all links from your workspace (documentation covers exports) and check destination URLs for non-200 responses. A spreadsheet and a simple checker script suffice; at a few hundred links this is an hour of work.
Fix by editing the redirect, not by making a new link. This is the superpower of managed short links — the printed QR code and the three-year-old YouTube description keep working because the short URL never changed, only its destination. Do the same triage after every site migration, immediately, without waiting for the quarter.
Close finished campaigns: archive or tag their links as closed, record final click counts in the campaign retro, and stop watching them. Clicks trickling into a closed campaign's links are a signal worth glancing at — they mean the content is still circulating somewhere.
Flag zombie links: links still receiving traffic whose destination no longer serves the visitor's likely intent (an ended promotion, a sunset product). Repoint them to the nearest useful page rather than letting them 404 or, worse, mislead.

Reading the click patterns that surface during audits — which old links still pull traffic, from where — is its own skill; the link analytics guide covers interpretation in depth.

The governance checklist

Everything above, condensed into the one-page policy to adopt at your next team meeting:

All links live in the shared UrlShorter workspace; personal accounts are prohibited for work links.
Permanent and printed links use the company custom domain.
Aliases follow {campaign}-{channel}-{placement}, lowercase, hyphenated, channel vocabulary fixed.
Campaign tokens are assigned in the campaign brief, before link creation.
UTM values mirror the link naming convention.
Every link has a recorded owner.
No link ships without the five-step QA check by a second person.
Evergreen link edits require a change record; experiment links are archived at test close.
Quarterly rot audit; immediate audit after any website migration.
Campaign closeout includes final click numbers and link archival.

Ten rules, none of which require budget — only agreement.

Frequently asked questions

How do we migrate hundreds of existing messy links to a convention?

Don't rename what's already published — a live link's alias is load-bearing. Instead, apply the convention to all new links from a cutover date, tag legacy links as legacy so they're visually separate, and clean up destinations (not names) during your first audit. The mess stops growing immediately, which is the actual goal.

Should each team or region have its own workspace?

Default to one workspace with naming-level separation (emea-spring26-*) until you have a hard boundary — separate client billing, legal separation, or an agency relationship. Multiple workspaces multiply admin overhead and break cross-team reporting; the FAQ covers workspace and access options.

What happens to our links if someone leaves the team?

If you followed rule one, nothing — the workspace owns the links, and you reassign the owner field during offboarding. If links live in a personal account, migrate them before the person's last day: recreate the redirects in the workspace and update the published URLs you still control. This is painful exactly once, which is why the rule exists.

How many links is too many for one campaign?

There's no ceiling, but there is a smell test: every link should map to a placement you'll actually evaluate separately. Twelve links for twelve real placements is discipline; twelve links for one Instagram post is noise. When in doubt, one link per channel-placement pair — the granularity used in how to track link clicks — is the right resolution.

Closing: process beats cleanup

Every team eventually manages its links; the only choice is whether that happens by design at fifty links or by archaeology at a thousand. The convention, the shared workspace, the QA gate, and the quarterly audit together cost perhaps two hours a month — roughly what a single broken printed link costs in Slack threads alone. Write the ten rules into your campaign template this week, and the mess simply never accumulates.