Redirect old and broken website URLs from one place

A website redirector manages redirects for the pages on a website that hosts content. It sends visitors from an old URL to its new destination when a page is renamed, moved or replaced.

For example:

example.com/old-page → example.com/new-page

Instead of letting visitors hit a broken page, a website redirector routes them to the most relevant destination.

The real difference is whether the domain is hosting content.

A website redirector is for websites that host content. Your site keeps serving pages as normal, and you redirect specific URLs to another page on your site or to a different site:

example.com/old-blog-post → example.com/new-blog-post

Domain forwarding is for domains that don't host content. The domain's DNS points to urllo, and urllo sends all of its traffic somewhere else:

oldbrand.com → newbrand.com

Yes. With the right setup, you can redirect one specific page while the rest of your website continues to load normally.

For example:

example.com/old-page → example.com/new-page

While:

example.com/pricing

example.com/contact

example.com/blog

Continue loading as usual.

This is where cdn-level redirecting is useful, because it can apply redirect logic to specific URLs without taking over the whole domain.

Yes. urllo supports same-domain redirects, which means you can redirect one URL path to another URL path on the same website.

For example:

example.com/services-old → example.com/services

This is useful for page updates, deleted pages, blog restructures, campaign cleanup, content consolidation and SEO maintenance.

It depends on the redirect setup.

For domain forwarding, DNS changes are usually required because the whole domain needs to point to the redirect provider.

For same-domain or edge-level website redirects, the setup may involve connecting urllo through your edge provider, CDN or infrastructure rather than fully moving your DNS. This allows redirects to be handled before requests reach your origin while keeping the rest of your site live.

Yes. urllo can work with cdn-level setups such as Cloudflare, Fastly or AWS CloudFront. urllo runs as a small function inside your CDN, which means redirect logic runs before requests reach your server. You control exactly which paths it applies to, without forwarding the entire domain.

If the origin returns a 200 OK status code, the visitor continues to the original page as normal. If the page is available and loads successfully, your CDN serves the page as usual. urllo never touches the request.

In case of a 404, one of two things can happen:

If you've set up a redirect in urllo for that URL, the visitor is sent to the new destination. For example, if an old page returns a 404, urllo can route visitors to the most relevant replacement page instead of leaving them on a broken URL.

If there's no matching redirect in urllo, your regular 404 page shows as usual.