# Single Redirects

Single Redirects are the current product for URL forwarding, replacing Page Rule forwards. They support static and dynamic redirects with configurable status codes.

## The constraints that shape design

- **Quotas**: 10 rules on Free, 25 on Pro, 50 on Business, 300 on Enterprise. On lower plans, consolidate: one dynamic redirect with captures beats five static ones.
- **Regex**: only available on Business and Enterprise. On Free/Pro, use wildcard and exact-match patterns; rewrite redirect needs accordingly.
- **First match wins**: the first rule matching a request executes and evaluation stops. Order specific redirects before catch-alls.

## The failure modes

- **Redirect chains**: A -> B -> C. Each hop costs a round trip and leaks SEO value. Audit chains with `curl -L` and collapse them to A -> C.
- **Redirect loops**: A -> B -> A, often between a redirect rule and origin behavior (the Flexible SSL trap is the classic). `curl` without `-L` shows the loop in one or two requests.
- **Catch-all swallowing new routes**: a `/*` redirect added for a migration sits above a newer specific redirect added later; the new one never fires because the catch-all matched first. Specific first, general last.

## Checklist

- Prefer 301 for permanent, 302/307 for temporary; 308 if the method must be preserved permanently.
- After any redirect change, `curl -sI` the old URLs and confirm single-hop destinations.
- Bulk Redirects exist for large static lists; do not burn Single Redirect quotas on hundreds of static mappings.