Skip to main content
Domain settings control what visitors see when they open the hostname without a valid Biqli alias. Configure the root landing redirect, expired-link destination, and not-found destination with valid public URLs. You can also add a favicon for branded browser tabs where the option is available. These settings apply at the domain level, so review their effect before changing a domain used by several resources. Domain redirects do not replace the destination configured on a valid short link.

​
Root landing behavior

The root redirect controls a visit to the hostname without a valid alias, such as https://go.example.com/. Send it to a trusted brand homepage or campaign hub so visitors do not meet an empty domain.

​
Error destinations

The expired URL is used for the supported expired-link experience. The not-found URL handles aliases that do not resolve on the domain. Use public HTTPS destinations that explain what the visitor should do next. Avoid redirecting them back to the same missing or expired Biqli path.

​
Favicon

Add the favicon through the supported domain setting and test it in a fresh browser session. Browsers cache favicons aggressively, so an older icon can remain visible after an update. Review domain-level changes with every team using the hostname because they can affect many links at once.

​
Frequently asked questions

​
Does the root redirect affect valid aliases?

No. A valid short-link path uses its own destination.

​
Can the not-found URL point back to the same hostname?

Avoid a destination that creates a loop through the same missing path. Use a known valid external or brand page.

​
Why is the old favicon visible?

Browser and crawler caches can keep it. Confirm the saved setting and test in a fresh session before replacing it again.