urllo supports redirect and link management for domains and websites. Depending on your use case, redirects can be implemented using either a DNS-based (hosted) setup or an edge-based (headless) setup.
In a DNS-based setup, redirects are managed through your DNS provider (for example, GoDaddy, Namecheap, or Google Domains), while edge-based redirects and links run through a CDN or edge platform (for example, Cloudflare, AWS CloudFront, or Fastly).
Before you get started
To use urllo, you’ll need one of the following:
The ability to update DNS settings for your hostname(s), or
Have cloud engineering resources available to implement urllo at the edge for your hostname(s) or website(s).
You can choose different implementation methods for different hostnames or websites, depending on your setup and needs, which we will highlight below.
If you’d like help determining which implementation is best for your use case, contact us and one of our experts would be happy to help.
Redirect and link setup options
Hosted implementation (DNS-based)
This setup can be used when the hostname is dedicated to redirects, branded links or QR codes. Because this setup relies on DNS, it cannot be used for redirects within the same hostname or on hostnames that are actively serving website content.
Hosted capabilities:
Paths from one hostname to another, for example:
parkeddomain.com → newdomain.com
acquiredcompany.com/about-us → primarywebsite.com/about-us
vanitydomain.com -> primarywebsite.com/marketing-campaign-page
brandname.ca -> brandname.com/ca
Hosted requirements:
You control DNS for the domain.
The domain is not serving website content.
Redirects point to a different fully qualified domain (for example, oldsite.com → newsite.com).
In this model, DNS for the hostname is pointed to urllo, and all forwarding logic is handled by our platform.
What's Next?
After setting up your redirect you'll need to configure the DNS record for the domain you want to redirect.
Headless implementation (edge-based)
Headless (edge-based) setups can be used for any hostname or website, and are required when the hostname is actively serving content. Redirect logic runs at your edge or CDN and supports both same-domain and cross-domain redirects and links.
Headless capabilities:
Paths within a website, for example:
example.com/page-2025 → example.com/page-2026
website.com/removed-page → website.com/equivalent-content
Paths from a website to another hostname, for example:
website.com/help → help.website.com
primarybrand.com/product-a → product-a-website.com
Paths from one hostname to another, for example:
parkeddomain.com → newdomain.com
acquireddomain.com/about-us → primarywebsite.com/about-us
vanitydomain.com -> primarywebsite.com/marketing-campaign-page
brandname.ca -> brandname.com/ca
Requirements:
You, or someone on your team, must have the cloud engineering resources to:
Implement integration code.
Connect urllo to your environment.
Configure the required settings within your edge or CDN provider.
With a headless setup, urllo manages redirect and link logic, which is executed at your edge or CDN so redirects can run without interfering with live website content.
What's Next?
If you would like to move forward with a headless setup we would be happy to help you out. Please contact us, we’ll review your setup and help you get started with your implementation.