Editorial guidelines

Why this page exists

Almost every article about URL shorteners on the open web exists to sell a URL shortener. It is written fast, often by someone who has never inspected a redirect chain, then trimmed until it ranks for "best link shortener 2026". The result recommends whichever product pays the highest affiliate rate and never mentions that the redirect itself is a tracking event.

We are not going to pretend we have no commercial interest. Forwrd is a product, and this blog exists partly because the problems we write about are the problems we built the product around. What we can do is publish the rules we hold ourselves to, before the traffic arrives, so you can hold us to them later.

Who writes it

Articles are written by the people who run Forwrd. There is no freelance content team, no agency feeding us keyword briefs, no guest posts. We publish under "the Forwrd team" rather than personal bylines because the same small group drafts, reviews, and ships everything. If an outside expert reviews a piece, we credit them in that piece.

Everything is written in American English. Forwrd's interface is translated into seven languages; the blog is not, because a machine-translated technical article is worse than an honest English one, and we would rather you read the version we can actually verify.

Standards of proof

Every claim falls into one of four categories, and each has its own bar.

1. How a protocol or format works (for example, "a 301 is cacheable by default and a 302 is not"). Verified against the primary specification - the relevant IETF RFC, W3C or WHATWG document, ISO standard, or the vendor's own reference - and, where possible, by running the request and reading the response headers.
2. What a specific product or platform does (for example, "this chat app fetches the destination server-side when it unfurls a link"). Verified by testing on current versions, on more than one device where behavior could differ, and dated in the article. "We tested this in May 2026" is honest; "Service X does Y" is not, because Service X changes.
3. Historical and news claims (for example, Google's shutdown of goo.gl). Cited from the primary source: the vendor announcement, the agency advisory, the court filing, or contemporaneous reporting from a named outlet. Never from a blog summarizing another blog.
4. Opinion and judgment (for example, "shorteners are the wrong default for anything meant to be durable"). Labeled as opinion in the prose, with the strongest counter-argument stated before we reject it.

Sources we use

• Specifications: IETF, W3C, WHATWG, ISO, ITU-T, and the ISO/IEC 18004 QR code standard.
• Government and regulator material: NIST publications, FBI, CISA, NCSC and ENISA advisories, EDPB and ICO opinions, FTC actions, court filings.
• Peer-reviewed work: USENIX Security, ACM CCS, IEEE S&P, PETS, NDSS.
• Vendor documentation, changelogs, and status pages, with the date we read them.
• The service, header, or code path being discussed, opened and inspected.

We do not cite content farms, undated listicles, "top 10" affiliate pages, or a language model's summary of any of the above. If a claim has no primary source we drop it, or we label it as widely reported and unverified.

How we use AI

We do not generate articles with a language model and publish them. Each piece is written by a person, sentence by sentence, including this page.

We do use AI tools the way writers already use a search engine: to recall the number of a standard, to draft a terminal command, to check whether a sentence has run too long. A human verifies and owns every factual claim afterward. "The model said so" is not a citation.

Model output has a recognizable shape: fluent, relentlessly upbeat, five-item lists where each item starts with a gerund, no dates, no named products, no opinion that could inconvenience anyone. If something here reads like that, tell us and we will rewrite it.

Conflicts of interest and how we make money

• No paid placements. We do not take money, credits, or product in exchange for coverage, links, or reviews.
• No affiliate links in editorial content. If a recommended tool has an affiliate program, we link the plain URL anyway.
• No link sales, no guest posts, no "write for us". If you email asking, the answer is no.
• We criticize our own product where it deserves it. Forwrd cannot make a redirect invisible to our hosting layer, cannot guarantee a destination stays honest after you shorten it, and is the wrong tool when the full URL would have worked fine. Articles here say so.
• Where the money comes from is stated plainly: display advertising, which visitors can turn off, and paid plans that are currently free while we grow. If that changes, this page changes and the next article says so.

Our privacy stance, applied to ourselves

It would be embarrassing to write about click tracking from a site that quietly profiled its readers. The blog runs on the same infrastructure as the rest of Forwrd and follows the same privacy policy. Specifically: no account is needed to read anything, advertising only loads after you allow it, and we do not embed third-party scripts whose business is following you across the web. The one exception is the forwarding page itself, where an ad is shown during the wait; that is documented in the privacy policy rather than hidden.

Corrections

• Substantive corrections get a dated note at the bottom of the article saying what was wrong and what changed.
• Light edits - typos, dead links, clearer phrasing - are made silently and reflected in the last-updated date.
• Stale articles get a note at the top when the landscape has moved, with a pointer to the newer piece if one exists.
• Articles we no longer stand behind are updated or retracted with an explanation. They are never quietly deleted.

What we will not write

• Anything that helps someone use short links for phishing, malware delivery, or cloaked deception. Our service guidelines ban those uses and the blog is not a workaround.
• Speculation about individuals based on anything other than the public record.
• A takedown of a competitor built on one second-hand complaint.
• Anything we have not done the work for. If it needs expertise we lack, we get it or skip it.

Tell us when we slip

The fastest way to make this page real instead of decorative is for readers to hold us to it. If a fact is wrong, a source is thin, a recommendation has aged badly, or a paragraph reads like a model wrote it, email us. We would rather hear it from you than from a search ranking.

Back to the blog index.