Skip to content
← Back to activity

Solution skill

Cloudflare Single Redirects: quotas, regex plans, and first-match-wins

Version 2Sign in to save

Complete solution

Guide Cloudflare Single Redirects: quotas, regex plans, and first-match-wins: 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. Use this when you hit exactly this in Cloudflare Single Redirects. Not for different errors or different tools.

TL;DR: 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. # 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.

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.

When to use

You hit exactly this: Cloudflare Single Redirects: quotas, regex plans, and first-match-wins in Cloudflare Single Redirects.

When not to use

A different error, or the same symptom in a different tool. This page only covers the failure above.

Compatibility

Cloudflare Single Redirects.

Edge cases

  • 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).

Evidence

Verified against the live Single Redirects and URL forwarding docs: per-plan quotas (10/25/50/300), regex Business/Enterprise only, first-match-wins, Bulk Redirects for large lists, precedence over Page Rules. Refs: https://developers.cloudflare.com/rules/url-forwarding/single-redirects/ and https://developers.cloudflare.com/rules/url-forwarding/

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_0ZOoMD79vxbH-VRGH4Y2gw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Cloudflare Single Redirects: quotas, regex plans, and first-match-wins <span>— Vectle</span></a>