Docs → CORA Custom Redirects
Core Features
CORA Custom Redirects
Manage URL redirects in WordPress and push them to Cloudflare Workers KV — so redirects resolve at the CDN edge before requests ever reach your server.
On this page
How it works
Traditional redirect plugins process redirects on the server — the request hits WordPress, PHP evaluates it, then the visitor is redirected. On busy sites this adds load.
CORA Custom Redirects manages redirects in the WordPress admin for convenience, then pushes them to Cloudflare Workers KV — a globally distributed key-value store. A Worker intercepts incoming requests, checks KV for a match, and sends the visitor to the new URL before WordPress is ever involved. The result: near-instant redirects with zero server load.
Adding redirects
- Go to CORA → Redirects
- Click Add Redirect
- Enter the source path (e.g.
/old-page/) - Enter the destination URL
- Select a status code (301, 302, etc.)
- Save
⚠️ New redirects are not live until you sync to Cloudflare.
Syncing to Cloudflare
After adding or editing redirects, click Sync to Cloudflare. This pushes all active redirects to Cloudflare Workers KV.
- Only active redirects are pushed
- Deleted redirects are soft-deleted and removed from KV on the next sync
- Sync is a manual step — there is no auto-sync on save
- Last sync time is shown at the top of the Redirects admin page
Regex & advanced matching
Regex patterns are supported for flexible source matching — useful for redirecting entire directory paths, handling trailing slash variations, or matching URL parameters.
Regex redirects are evaluated in order. List more specific patterns before broader ones.
Bulk import
To import redirects in bulk:
- Prepare a CSV with columns:
source,destination,status_code - Go to CORA → Redirects → Import
- Upload your CSV
- Confirm the import preview
- Sync to Cloudflare to push live
Requirements
- Cloudflare account with Workers and KV enabled
- Cloudflare API token with Workers:Edit and KV:Edit permissions
- WordPress 6.0+
