Redirects (URL shortener)
A redirect is a route on your domain that sends visitors to another address. For
example, yourdomain.com/promo → a campaign page on another website. They are created from the
Redirects section in the dashboard and each tracks its own click metrics.
Available on the Basic, Pro, and Enterprise plans, with limits increasing per tier.
Static and dynamic redirects
| Route | What it captures |
|---|---|
/promo |
Only that exact address. |
/ |
The root of your domain. |
/producto/:id |
Any /producto/something (one segment). |
/blog/* |
Anything starting with /blog/, across any number of segments. |
/* |
Your entire site. |
A :name captures a single segment, and a trailing * captures everything that follows.
Landings have priority
A dynamic redirect (:name or *) never overrides one of your pages: if a published
landing responds at that address, the landing is shown. That is why /* means
"everything that is not a page on my site". This is useful, for example, to redirect all
obsolete URLs that no longer exist to another site.
A static redirect cannot use the path of one of your landings: it is rejected upon saving.
If two dynamic redirects match the same address, the most specific wins:
/blog/:nota before /blog/*, and /blog/* before /*.
Destination variables
In the destination of a dynamic redirect you can use:
{{PATH}}: the requested path, without the leading/.{{REST}}: what the*captured.{{NAME}}: what each:namecaptured (in uppercase).
For example, /* → https://new-site.com/{{PATH}} redirects
yourdomain.com/pricing to new-site.com/pricing.
Traffic origin (UTM)
When a redirect sends someone to another site, that site cannot naturally tell that the visitor passed through your domain: the browser reports the page preceding the redirect. Therefore each redirect can add UTM parameters to the destination, and this is enabled by default:
utm_source: the domain the visitor entered through (e.g.yourdomain.com).utm_medium:redirect.utm_campaign: the redirect route (e.g.promo).
This allows the destination's Google Analytics to record those visits as coming from your domain.
-
If the visit already carries its own UTMs (for example, arriving from an Instagram ad
with
utm_source=instagram), its original parameters are preserved entirely. They are never mixed: combining halves would attribute traffic to a nonexistent campaign source. -
The rest of the query string travels through: if someone enters
yourdomain.com/promo?ref=qr,ref=qrreaches the destination. If the destination already includes that parameter, the destination's value takes precedence. - You can disable this per redirect with "Report traffic origin".
Metrics
Each redirect tracks clicks (total and unique), broken down by country, device, and source. The
source is the incoming utm_source or, if none, the referring site.
Clicks for a dynamic redirect are aggregated on that redirect, rather than per individual path.
Between Landinker sites: if the destination is another landing built with Landinker, its
metrics will also register the utm_source, showing the referring domain in the traffic source report.