Edge Link Router
| 开发者 | 301st |
|---|---|
| 更新时间 | 2026年3月3日 21:11 |
| 捐献地址: | 去捐款 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 6.9 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
Simple redirect management that works immediately. Create
/go/your-slug redirects in WordPress admin — no configuration required. Optionally accelerate with Cloudflare Workers.
Built by 301.st — your redirect management experts.
What It Does
- Instant redirects — Works right after activation. No setup, no external services needed.
- Full control — 301/302/307/308 codes, UTM auto-append, query passthrough.
- 404 catch-all — Redirect all 404 pages to your homepage or any URL (WP-only).
- CSV import/export — Migrate affiliate links between sites in seconds.
- WordPress handles everything by default — Redirects work via WP rewrite rules
- Enable edge mode (optional) — Connect Cloudflare for sub-millisecond redirects
- Fail-open design — If edge fails, WordPress takes over. Redirects never break.
- Aggregated click stats only (daily totals)
- No IP addresses, no cookies, no User-Agent
- GDPR compliant — no consent required
- Project Home
- GitHub
- Redirect Inspector — free Chrome extension
安装:
- Upload the plugin files to
/wp-content/plugins/edge-link-router/ - Activate the plugin through the 'Plugins' screen in WordPress
- Go to Link Router > Links to create your first redirect
屏幕截图:
常见问题:
Do I need Cloudflare to use this plugin?
No. The plugin works perfectly with just WordPress. Cloudflare integration is optional for users who want edge acceleration.
What redirect types are supported?
The plugin supports 301 (permanent), 302 (temporary), 307 (temporary, preserve method), and 308 (permanent, preserve method) redirects.
Can I add UTM parameters automatically?
Yes! Each redirect can have its own UTM parameters (source, medium, campaign) that are automatically appended to the target URL.
What happens if Cloudflare edge fails?
The plugin is designed with a "fail-open" approach. If edge has any issues, requests automatically fall back to WordPress handling. Your redirects keep working.
Does this plugin collect user data?
No personal data is collected. Statistics are aggregated (total clicks per day) with no IP addresses, user agents, or cookies stored.
How can I verify my redirects work correctly?
Use our free Redirect Inspector Chrome extension to see the full redirect chain and HTTP status codes.
更新日志:
1.0.23
- New: URL Normalization — 301-redirect uppercase paths, duplicate slashes, and trailing slash mismatches to canonical form
- Bump stable tag to 1.0.23
- New: Strip Tracking Parameters — remove ad-platform click IDs (fbclid, gclid, etc.) from URLs
- Internal cleanup and version bump
- New: 404 Catch-All Redirect — automatically redirect all 404 pages to a specified URL
- New: Settings link on the Plugins page
- CI: Plugin Check added as pre-release gate
- Add External services section to readme (WP.org review)
- Fix: Sanitize and validate CSV file upload before import
- Fix: Remove wp_json_encode flags per review feedback
- Fix: ZIP filename now matches WP.org expectation (no version suffix)
- Change sample link from 301.st to wordpress.org
- Fix: Clean up cfelr_plugin_version option on uninstall
- Fix: Edge mode detection after plugin update (no longer shows "WP Only" when edge is active)
- Add worker deployment and route existence checks to diagnostics
- Smart health cache: schedule immediate re-check on update instead of clearing cache
- Move inline styles to enqueued admin.css (review compliance)
- Migrate SQL queries to %i identifier placeholder (WP 6.2+)
- Plugin Check: zero errors, zero warnings
- Fix clicks column alignment
- Updated banner assets
- Fix: Clear health status cache on plugin update to prevent stale "Edge Degraded" status
- Fix: Edge health check now correctly detects worker (use /settings API endpoint)
- UI: hide Target URL column on narrow screens (< 1200px)
- UI: move action buttons to toolbar row with search
- UI: align inline form inputs with buttons
- Fix: CI build ZIP structure for WordPress installer
- Updated "Tested up to" to WordPress 6.9
- Fixed Plugin Check errors (fopen/fclose, variable prefixes)
- Improved readme for WordPress.org submission
- Unified admin badge styles
- Added plugin assets (banners, icons)
- Worker: add snapshot version headers for debugging (X-CFELR-Snapshot-Version, X-CFELR-Snapshot-Updated)
- Worker: remove all trailing slashes, trim target URL
- Worker: dynamic prefix from SNAPSHOT (not hardcoded in regex)
- Worker: pre-decode length check to prevent DoS
- Worker: UTM key charset validation (alphanumeric + underscore)
- Worker: try-catch around new URL() for malformed targets
- Complete edge hardening: slug length limit, UTM validation, synced status codes with WP
- Worker hardening: protocol validation, options normalization, status code whitelist
- Better error handling for malformed URL slugs
- Fixed fail-open mode API parameter (request_limit_fail_open)
- Fixed constant redefinition warning during updates
- Route pattern mismatch detection and warning
- "Fix Route Now" button to repair mismatched routes
- Auto-update CF route when prefix changes
- Routes now use fail_open mode (true fail-open design)
- Simplified Cloudflare API token setup (Custom Token with 4 permissions)
- Added edge mode notice on Stats page with link to Cloudflare metrics
- Fixed Cloudflare Worker upload multipart format
- Added Git Updater support
- Initial release
- WP-only redirect handling
- Links CRUD management
- CSV import/export
- UTM parameter support
- Aggregated click statistics
- Dashboard widget
- Cloudflare edge integration
- Diagnostic tools
- REST API