Redirect Management Guide
Form-driven 301/302 rules across every Cloudflare zone you own — versioned locally, applied in batch, no per-zone clicking.
Templates That Cover Most Cases
- Redirect work happens from one operational surface instead of scattered provider dashboards.
- The workflow sits on top of trusted integrations, synced domains, and optional account structure.
- Teams can treat redirects as a real day-to-day operating layer, not just a loose collection of one-off edits.
How to Create a Redirect
- Open Redirects. Filter by project or site if your account has multiple — keeps the dropdowns short.
- Use projects and sites where they improve clarity, especially in larger setups.
- Create redirect rules from a model your team can still review later without guesswork.
- Use the platform as the central place to review, update, and sync redirect logic.
Why Sync Is a Separate Step
- Edits stay local until you sync. You see a diff against what Cloudflare currently has, so nothing reaches production by accident.
- Better visibility when multiple domains or destinations are involved.
- "Sync all" batches every pending change in one operation. For agencies migrating 50+ rules at once, that is the difference between a 5-minute task and a 30-minute one.
How Redirects Connect to the Stack
- Integrations establish access to the infrastructure you already own.
- Domains provide the working inventory for routing decisions.
- Projects and sites keep the account readable where structure matters.
- Redirects turn that foundation into a stable traffic workflow.
Table Features
The redirect table shows source domain, target URL, status, sync state, and an enabled toggle per row. Inline edits open the drawer with the rule pre-loaded — no full-page navigation.
Bulk operations work on row selection: bulk enable/disable for instant traffic gating, bulk delete for cleanup, bulk sync for shipping batches of pending changes. T7 maintenance mode is the recommended way to gate traffic during deploys — toggle on, sync, deploy, toggle off, sync.
FAQ
Should I use Redirects or TDS?
Redirects for unconditional URL → URL moves (domain parking, path moves, maintenance). TDS when the rule depends on the request itself — geo, device, bot status, UTM parameters, or A/B testing weight. Start with Redirects; layer TDS in when a use case actually needs the condition.
Do redirects require projects and sites?
You need at least one site with an acceptor domain (the target). A project is optional but recommended past a handful of redirects — without it, filtering and bulk-scoping get awkward.
What happens if Cloudflare sync fails?
Yes. Redirect management is one of the most mature operational areas in the current product.