Skip to main content
Biqli short links use direct redirects. When an eligible visitor opens the short URL, Biqli evaluates the link state, password, schedule, expiration, safety, and targeting rules before sending the visitor to the selected destination. The public Workspace API also treats links as direct redirects. Link pages, overlays, and frontend widget data are not accepted as link API fields. If a link does not redirect as expected, check:
  1. The link is active.
  2. Its activation date has passed and its expiration has not.
  3. Its click limit has not been reached.
  4. The destination is not blocked by a safety check.
  5. The visitor completed password verification when required.
Targeting and expiration rules can intentionally send the visitor to a URL that differs from the main destination.

​
What visitors experience

The browser first requests the short URL. Biqli finds the link within the hostname’s workspace context, checks whether the request is eligible, records supported analytics, and responds with the destination redirect. The destination website then loads normally in the visitor’s browser. Biqli does not frame the destination and does not insert a splash or overlay into standard links. This avoids depending on whether the destination permits embedding and keeps the destination responsible for its own content and security.

​
Redirect chains

The destination itself can redirect again, but long chains add delay and make campaigns harder to debug. Point a Biqli link as close as possible to the final page. Do not use another public URL shortener as the destination. To inspect an unexpected result, test the short URL in a clean browser session, then check its main destination, targeting URLs, click-expiration fallback, and the redirect behavior of the destination website.