Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/org-quicko/linq/llms.txt

Use this file to discover all available pages before exploring further.

A link tree is a link of kind tree that serves a hosted HTML page instead of issuing a redirect. When a visitor lands on its short URL, linq renders the page directly — displaying a title, description, optional image, and an ordered list of items, each pointing to another link on the same domain. Link trees are the linq equivalent of social-media profile link pages (like Linktree or Carrd), but self-hosted on your own domain with no third-party dependency. The short URL format is identical for both kinds: https://<domain>/<slug>. Only what happens on arrival differs.

​
Items

Each item on a tree page is an ordered entry with:
  • A label — the visible text shown to the visitor.
  • A target link — another link that lives on the same domain as the tree. The target can be any active redirect link on that domain. Clicking the item follows the target link’s own redirect, including any rules.
Target links must belong to the same domain as the tree link. You cannot mix links from different domains on a single tree page.
Items are managed as a sub-resource of the tree link. The order of items in the response is the order they appear on the rendered page.

​
QR Codes

Tree links support the same QR code generation as redirect links. A QR code for a tree link encodes the tree’s own short URL (https://<domain>/<slug>), which always resolves to the hosted page. You can generate multiple QR codes per tree link, each with its own color scheme and dot/corner pattern.
Set a tree link as your domain’s fallback URL to turn every orphan visit on that domain into a curated landing experience. Any visitor who lands on an unknown slug, an archived link, or the bare root path will see your tree page instead of a 404.Example: set fallback_url on your domain to https://go.example.com/links, where links is the slug of your tree link.

​
OG Metadata and Social Sharing

When a link-preview crawler (Slack, iMessage, Twitter) hits the tree’s short URL, linq detects the crawler’s User-Agent and serves the same hosted HTML page — which already carries the correct Open Graph tags in its <head>. No separate OG-preview logic is needed; the tree page is the canonical response for all visitors, human and bot alike. Tree links follow the same active → archived → purged lifecycle as redirect links. Archiving a tree link stops the hosted page from being served. Purging destroys the link row, releases the slug, and destroys all associated visit records permanently. Archiving and purging require an admin-role API key.

Build docs developers (and LLMs) love

Get started for freeTalk to us