Match not found

What happens when a redirect comes in, but a redirect cannot be found?

Path not found

Let's say we have the following redirects set-up:

https://example.com/ -> https://new-domain.com
https://example.com/contact -> https://new-domain.com/contact-us

Example 1: The user lands on the source ("https://example.com/contact"). The user can be correctly redirected to the destination!

Example 2: Let's say the user lands on "https://example.com/old-contact-page". In this case, we don't have an exact path match. redirect.pizza moves to 1 lower condition, and is looking to see if there is a redirect set-up for "https://example.com/". We then redirect the user to "https://new-domain.com". Due to this behavior, we always recommend setting up a "root path redirect" when using paths in your redirect. This is recommended in the interface automatically:

Recommend root path

Because we always fall back on the root path (if this is defined), your visitors will not be presented with a 404 page.

Due to this, we don't see the value of adding a "custom 404 page". Let us know if you have a use-case for this, we would always be happy to reconsider our train of thought.

Read more about our Matching behavior here.

Hostname not found

When the hostname is not found, i.e. not set-up in redirect.pizza, we do not know where to redirect the request to. In this case, we're forced to serve a "404 not found". 

Want to customize the branding on this error? A Dedicated IP would be required. See our Dedicated IP article for more info.

More articles

Can’t find the answer you’re looking for?

E-mail us
support@redirect.pizza
Start a chat
Online 9:00 - 21:00 CEST
Phone
Available with Enterprise