ER

Platform Engineering

Edge Redirect Manager

Migration-safe routing, campaign continuity, and URL equity protection at the edge.

Redirect Lane

Route intent should be legible before the edge starts rewriting traffic.

This lane shows which URLs are being permanently moved, temporarily diverted, or transparently rewritten so teams can protect campaigns and migrations without guessing what the edge is doing.

Redirect Rules

Rule posture by path, cache behavior, and risk.

Source Target Type Cache Risk Intent
/platform/old-security-overview /platform/security/control-plane 301 edge ttl 24h healthy Preserve historical search equity during product taxonomy cleanup.
/lp/q3-demand-sprint /campaigns/q3-demand-sprint rewrite bypass for UTM variants watch Keep campaign vanity URLs stable while marketing swaps landing internals.
/pricing-enterprise /pricing?plan=enterprise 302 edge ttl 5m watch Temporary plan-test split while offer architecture is still moving.
/blog/identity-maturity-framework /insights/identity/maturity-framework 301 edge ttl 7d healthy Move a high-performing post into the new insight taxonomy without losing inbound authority.
/trial /get-started/demo rewrite no-store on auth state critical Unify high-intent traffic under one conversion surface while preserving old entry paths.

Operating workflow

The page explains who should act, what breaks, and how the redirect map proves the fix.

A useful redirect system has to speak to SEO, RevOps, platform engineering, and executives at once. This section makes the handoff explicit so reviewers can understand the product without reading the source code first.

Before launch

Map every route to intent and owner.

Classify the path as SEO continuity, campaign continuity, migration cleanup, or application routing. Each rule needs a clear owner and a reason it exists.

During release

Watch breakage where business value is highest.

Prioritize pricing, demo, trial, docs, partner, and high-authority pages so paid and organic traffic do not disappear into stale URLs.

After release

Turn routing outcomes into evidence.

Use the JSON outputs, static proof pages, and screenshots to show which risks were contained and which routes still need cleanup before the next launch.