Skip to main content
When a post contains a link, PostQueen can replace it with a short link from a link shortener, which counts the clicks. The option exists only when a shortener is configured. Without one, links go out as written, PostQueen never asks, and the app hides the Shortlink Settings card and each post’s Short Links Statistics table. Four services are supported. You choose one by setting its key.
Set only one. PostQueen picks the first configured service in this order, reads it once at start, and ignores the rest without a warning: DUB_TOKEN, then SHORT_IO_SECRET_KEY, then KUTT_API_KEY, then LINK_DRIP_API_KEY.

​
Set it up

1

Set the service's variables

Only the token is required; the other two show their defaults. Set DUB_SHORT_LINK_DOMAIN to a domain you added in Dub to get links on your own name.
2

Recreate the container

Recreate the app container so it reads the new values. A plain docker restart or docker compose restart keeps the old container and its old environment.In the folder that holds docker-compose.yaml, recreate only the postqueen service:
The database, Redis and Temporal keep running. Avoid docker compose down for a settings change: on a host that runs other Compose services in the same project, it stops them too. On Kubernetes, see Kubernetes with Helm.
3

Try it

Write a post with a link and schedule it. PostQueen asks “Do you want to shortlink the URLs? it will let you get statistics over clicks”. Choose Yes, shortlink it! and the published post carries the short domain.
A workspace admin chooses how links are handled in Settings > Global Settings > Shortlink Settings: Ask every time, Always shortlink or Never shortlink. With STRIP_LINKS_FROM_X_POSTS set, X posts lose their links anyway, so their text is not checked for links to shorten. If PostQueen never asks, the key is not reaching the backend: check the variable name, and that the container was recreated rather than restarted.
Last modified on September 23, 2026