Every use case starts the same way: point the domain at redirect.pizza. What happens next depends on why you're redirecting it.
Every use case starts the same way: point the domain at redirect.pizza. What happens next depends on why you're redirecting it.
Merge websites
After a merger or acquisition, one site stays and the other domains send their visitors there. Map the URLs, apply the DNS changes in bulk and keep their email working.
Learn moreKeep SEO intact
When URLs change, a redirect map decides where visitors and crawlers end up. Send each old URL to its closest match, import the map as a CSV and check it after launch.
Learn morePark unused domains
Typo domains, old brands and names for later still get visitors. Send them to your main site over HTTPS, and guard their email with SPF and DMARC.
Learn moreChange your domain name
A new domain name changes every URL, while links and search results still point at the old domain. Redirect it with 301s, and keep HTTPS and email working on it.
Learn moreRelieve your IT team
Campaign domains, retired product names and typo domains all land on the IT team's desk. Give marketing its own logins, while IT keeps the roles, the DNS and the API tokens.
Learn moreRedirect apex to www
People type your domain with and without www. Pick one address and redirect the other to it with a 301, over HTTP and HTTPS.
Learn moreRedirect over HTTPS
Without a valid certificate, an old domain stops visitors at a browser warning. Point it at redirect.pizza, and every hostname gets a certificate, renewed automatically.
Learn more