Hyperflow Site Redirector

Used to redirect a custom map of URLs

Use Cases

  • You've rebuilt and rebranded your site on an entirely new platform. Both the URLs and domain name have changed.

  • You've split part of your site out into a new site, and you need clean redirection for all of those pages

  • You want to keep your SEO and backlinks, so redirecting individual pages map-style is valuable

Technical Notes

  • Redirects are all 301 redirects

  • Implemented as a worker

  • Typical worker route is e.g. *mysite.com/* to map everything, but this is not mandatory

  • Map is stored as a JSON object in the worker's KV store

  • Has a fallback for unmatched items

Configuration Notes

Configuration is stored in the KV store, under a site identifier key, which is the naked domain, e.g. mysite.com.

Value includes a fallback URL for anything unknown, and a list of redirects.

"fallback": "https://www.mysite.com/", 
"redirects": {
    "/": "https://www.mysite.com/",
    "/privacy": "https://www.mysite.com/privacy-policy/",
    "/team/mike": "https://www.mysite.com/mike/",

Within the redirects;

  • Key must be unique, and is path-only.

  • Value must be a full URL to redirect to;

    • You can use the same destination multiple times

    • You can redirect to any URL, thus splitting a site among multiple destinations


  • Tracking stats?

  • Google analytics trigger?

  • Special path handling e.g. /robots.txt and /sitemap.xml

Last updated