Editing a destination updates every copy of the short URL already printed, posted or embedded in a QR code.
The short URL is a stable name; the destination is a value attached to it. Edit the destination and the next click goes to the new place. Nothing about the short URL changes, so posters, packaging and QR codes already in the world keep working.
1
Open the link
From the Links table, or from its detail page if you came in from analytics.
2
Replace the destination URL
The new destination is screened the same way the original was.
3
Save
The cached resolution for this link is invalidated on save, so the change takes effect on the next click rather than at the end of a cache window.
A 301 may be cached by the visitor
If the link uses a 301 or 308, browsers and intermediaries are entitled to remember the old destination and may not ask us again. For anything you expect to re-point later, use 302 or 307.
When to use 301, 302, 307 or 308, and why the default is 302.
Status
Meaning
Method preserved
Use it when
301
Moved permanently
No — POST becomes GET
The destination will never change and you want search engines to pass authority to it.
302
Found (temporary)
No — POST becomes GET
The default. You may re-point this link later.
307
Temporary redirect
Yes
A temporary redirect that must keep the request method and body.
308
Permanent redirect
Yes
A permanent redirect that must keep the request method and body.
The redirect engine is a route handler rather than a page precisely so it can emit any of these four. A redirect from a Server Component is always 307, and a permanent one always 308 — which would make 301 and 302 unreachable.
Permanent means permanent to a cache
Once a browser has cached a 301 it may go straight to the old destination for months without asking us. Choosing 301 for a campaign link you later re-point is the most common cause of "my edit did nothing" reports.
Three independent controls over when a link resolves, and what a visitor sees when it does not.
These are Pro and Business features. Each is independent — a link can require a password, expire on a date and stop after a number of clicks all at once.
Password protection
Set a password of at least four characters. Visitors get a form before the redirect; a correct answer sets a cookie scoped to that link so they are not asked again on the next click. The password is stored as a bcrypt hash, so nobody — including us — can read it back. Attempts are rate limited.
Expiry
Pick a date and time, then choose what happens after it passes:
Not found — a plain 404, as if the link never existed.
Message — a page showing text you write, which is the right choice when people will keep arriving from printed material.
Redirect — send them to a different URL, for example last season’s campaign to the current one.
Click limits
Cap the total number of clicks. When the cap is reached the link is disabled and behaves like a disabled link: it returns 410 Gone with an explanation rather than silently 404ing.
A spent link is not deleted
Expired, capped and disabled links stay in your account with their analytics intact. Clearing the expiry or raising the cap brings the same short URL back to life.
Targeting rules route by country, device, operating system, language, referrer or time window. First match wins.
A link can carry an ordered list of rules. On each click the rules are evaluated top to bottom and the first one that matches supplies the destination. If none match, the link’s own destination is used — so the fallback is never undefined.
Rule type
Matches on
Country
The two-letter country resolved from the request. Select one or more.
Device
desktop, mobile or tablet.
OS
iOS, Android, Windows, macOS, Linux or Chrome OS.
Language
The visitor’s Accept-Language preference.
Referrer
The referring host, matched by contains or equals.
Time window
A start and end timestamp in a timezone you choose.
Order is the whole configuration
A broad rule above a narrow one makes the narrow one unreachable. Put "iOS" above "mobile", not below it, or every iPhone takes the mobile branch.
Rules can be disabled individually without deleting them, which is how you park a seasonal branch until next year.
Attach campaign parameters once and have them merged into the destination at redirect time.
Set utm_source, utm_medium, utm_campaign, utm_term and utm_content on the link. They are merged into the destination’s query string when the redirect is issued, which means the short URL you hand out stays short and the destination still receives complete campaign attribution.
What the visitor’s browser ends up requesting
Short link paddek.com/summer-sale
Destination https://shop.example.com/collections/summer?ref=newsletter
UTM source=newsletter medium=email campaign=summer-2026
Resolved https://shop.example.com/collections/summer
?ref=newsletter
&utm_source=newsletter
&utm_medium=email
&utm_campaign=summer-2026
Parameters already present on the destination are preserved. A UTM value you set on the link replaces a UTM key of the same name on the destination, so the link is the single source of truth for campaign tagging.
You still see the click
UTM parameters are for the destination’s analytics. Ours are recorded independently on our side, so a link with no UTM tags is still fully measured.
Generate a QR for any link, restyle it, download PNG or SVG, and read scans separately from clicks.
A QR code encodes the short URL, not the destination. That is the point: you can reprint nothing and still change where the code leads.
Setting
Range
Notes
Foreground / background
Any hex colour
Keep strong contrast — scanners need it more than eyes do.
Size
128–2048 px
Only affects the PNG. The SVG is resolution-independent.
Margin
0–10 modules
The quiet zone. Below 2 some scanners struggle.
Error correction
L, M, Q, H
Higher levels survive scuffing and partial damage, at the cost of a denser code.
Styling is a Pro and Business feature; the plain black-on-white code is available on every plan. Scans arrive tagged as QR traffic, so the analytics separate "scanned the poster" from "clicked the tweet" without you setting anything up.
What makes a scan countable
A scan and a tap are otherwise identical requests, so the code we generate encodes your short link with a marker on the end of it. The redirect engine reads the marker, counts the visit as a QR scan, and drops it — the page your visitor lands on never sees it. A code generated somewhere else from the bare short URL still works, but it arrives as an ordinary click, because there is nothing in the request that says otherwise.
Test the printed size, not the screen
A code that scans on a monitor can fail at 15 mm on a matte label. Print a proof at final size and scan it with an average phone before the run.