The Government Figured Out Permalinks Before Your Startup Did
Photo: John Robert McPherson, CC BY-SA 4.0, via Wikimedia Commons
Somewhere in a federal agency's public affairs office is a spreadsheet of short links created before you had a job, and those links still resolve today. Not because the team behind them was unusually clever, but because someone wrote down a rule and then a compliance officer occasionally checked.
That is the entire trick. Permanence at scale is a policy artifact, not an engineering achievement.
How the government ended up here
The U.S. government got into link shortening the way it gets into most things: through a consolidation effort. Early agency shorteners — the memorable 1.usa.gov among them — were eventually folded into a single shared service so that public links would have one accountable operator instead of a dozen orphaned subdomains. The lesson from that consolidation still holds: a short-link program with one owner and one policy outlives a short-link program with good intentions.
Today the pattern repeats at every level. Federal agencies, state transportation departments, public university systems, and municipal governments all run shortened link services, and the good ones share a recognizable shape.
What durable programs actually enforce
A naming convention with a human gate. Slugs are reviewed before publication, usually against a style guide for the words that appear in public-facing URLs. No self-serve free-for-all. The review is annoying, and that is the point.
Retention tied to records, not to campaigns. This is the piece startups consistently miss. A marketing team decommissions a campaign, so the links die with it. A records retention schedule says a public communication is preserved for a defined period regardless of whether anyone in marketing still cares. The link's lifespan is derived from the document it points to, not from the enthusiasm of the team that created it.
A published abuse channel. Government shorteners typically list an address for reporting malicious redirects and have a process for suspending them. That matters because a .gov domain carries institutional trust and therefore attracts impersonation. The trust is defended with a process, not a disclaimer.
Explicit ownership. Every short domain has a named operator, a support contact, and a page explaining what the service is and is not for. When the service is retired, there is an announcement.
Optics as a constraint. A redirected .gov link heading to a commercial page is a problem, because someone will notice and write about it. Restricting destinations to agency-controlled properties is a governance rule that doubles as a security rule.
None of this is technically sophisticated. All of it is written down.
Where commercial shorteners structurally differ
Free and low-cost shorteners are businesses, and their incentives are not your permanence. Terms of service change. Tiers get restructured. Acquisitions happen. The most common failure mode is not a dramatic shutdown — it is a quiet policy update that makes bulk export harder, or a pricing change that makes a legacy account uneconomic to maintain.
Even paid service does not purchase permanence unless the contract says so. A monthly subscription buys availability this month. It does not buy the redirect in 2039.
The governance checklist for anyone who is not the federal government
You do not need an agency to adopt agency discipline. You need a document and a person willing to enforce it.
- Name a single owner, plus a backup. A shared inbox is not an owner. Write both names into the policy with a review date.
- Set a retention floor. Pick a number of years tied to the content the link points to — a tax document, a published report, a legal notice — and make deletion an exception requiring sign-off, not a default.
- Control the domain. Register a short domain you own. Custom paths on someone else's domain are borrowed, not owned.
- Reserve the namespace. Document a prefix scheme by team or program. Undocumented slugs collide eventually, and renaming a live link is a small crisis every time.
- Require review for public-facing links. A four-eyes check on destination and wording catches typos, phishing lookalikes, and accidentally internal URLs.
- Publish an abuse contact. Even if you are a 40-person nonprofit. A page with a monitored address is the difference between a quick takedown and a week of escalating complaints.
- Document the sunset behavior. Retired links should return
410 Gonewith a page explaining the retirement and, where possible, the current equivalent. Do not let them silently 404. - Export monthly. Redirect maps, creation dates, owners, destinations. Store them somewhere the shortener cannot delete.
- Negotiate exit terms before you need them. Bulk export in a documented format, redirect continuity if the vendor is acquired or shuts down, and a notice period long enough to migrate.
- Review annually, in writing. A short-link program with no scheduled review is a program that has already started decaying.
The uncomfortable comparison
A commercial shortener will give you slick analytics, a chrome extension, and a dashboard that renders beautifully on a keynote screen. It will not give you a records schedule. It will not give you an owner who is accountable to anyone but a support queue. It will not give you a reason to keep a link alive when the campaign team has moved on to a new initiative.
Those things have to come from inside your organization. The government figured that out because public records law forced it to. The rest of us get to figure it out voluntarily, which is cheaper.
Fiscal years end. Budgets get cut. Teams get reorganized. The link should outlast all of it. That is not an engineering problem — it is a memo waiting to be written.