Edge Redirector
Edge Redirector lets Akamai issue redirects at the edge, based on match rules — URL path, query string, cookie, header, geography or device type — before the request ever reaches the origin. No origin code change, no origin load, and the rule can be turned on or off instantly from Property Manager.
Scenario 1 — Legacy URL migration
A classic case: a customer relaunches a promo page under a new URL, but old links, bookmarks and search results still point at the old path. Instead of patching the origin, a single Edge Redirector rule fixes it for every visitor, instantly.
🕹️ Before — old URL
This is the legacy page. Once the rule is active, hitting this URL should 301 to the new one below.
/demos/edge-redirector/legacy-promo.html Open old URL →✅ After — new URL
This is where visitors should land. It's the actual page the origin serves going forward.
/demos/edge-redirector/new-promo.html Open new URL →/demos/edge-redirector/legacy-promo.html and
redirect (301, preserve query string) to
/demos/edge-redirector/new-promo.html. Until that rule is deployed,
both URLs will simply load their own page — which is exactly the "before" state
to show a customer.
Ideas for more scenarios on this page
Once the first rule is live, this section is a good place to layer in more Edge Redirector match conditions using the same two pages, or new ones:
- Device-based: redirect mobile user agents from a desktop path to a mobile-optimized one.
- Geo-based: redirect visitors from a given country to a localized landing page.
- Query-string based: route
?campaign=oldtraffic to an updated campaign page while leaving everything else untouched. - Maintenance mode: temporarily redirect an entire path to a "we'll be right back" page with one toggle.