What a short link actually does

A short link does not host the page you are sending people to. The browser asks this service for a short path such as /go/k7Qm3pLx. The service looks up that code and answers with the long address. The browser then requests the long address on its own.

Why the redirect is temporary

Linkora answers with HTTP 302, not 301. A 301 means “this moved permanently,” and browsers and intermediate caches are allowed to remember it. That is the wrong default for a link you may disable, expire, or block after a report. A 302 plus Cache-Control: no-store tells the browser to ask again next time.

HTTP/1.1 302 Found
Cache-Control: no-store
Referrer-Policy: no-referrer
Location: https://example.com/pricing

What the destination site can see

The redirect response sets Referrer-Policy: no-referrer. The destination site does not receive the short code or the custom slug as the referring URL. If you need campaign attribution, put it on the destination itself, for example as UTM parameters, before you shorten it. Those parameters are part of the stored URL. They are not added later.

What is fixed at creation

The destination cannot be edited after the code is issued. That stops a link that was shared as a product page from being switched to a different site. If the page moves, create a new short link. Deleting the old one retires the code; it is not offered to another account.

Fragments (the part after #) are removed before the link is stored. Browsers do not send fragments to servers, and two URLs that differ only by a fragment are the same destination for a redirect.