Description
DevLemon Redirect Manager lets you manage URL redirects directly from the WordPress admin — no server file editing required.
Who needs this?
- Your page slugs changed after a redesign.
- You migrated from another platform and old URLs are still getting traffic.
- A post was permanently removed and you want to return a proper 410 Gone response.
- You have campaigns whose URLs changed and you need to preserve external links.
Supported redirect types
- 301 — Moved Permanently (most common; tells search engines to transfer link equity)
- 302 — Found / Temporary Redirect
- 307 — Temporary Redirect (method-preserving)
- 410 — Gone (tells search engines the content is permanently removed)
What you can do
- Create, edit, enable, disable, and delete redirects.
- Import redirects in bulk via CSV.
- Export your current redirects to CSV.
- Search by source or target, and filter by redirect type or active status.
- See how many times each redirect has been triggered (hit counter).
- Loop detection prevents you from creating circular redirects.
Design philosophy
- One function, done well. No SEO suites, analytics, or marketing tools bundled in.
- Zero front-end overhead — no CSS, JavaScript, or external requests added to your site.
- Privacy-first: no visitor IPs, user agents, or personal data stored anywhere.
- Redirects are processed via WordPress APIs — no
.htaccessmodifications. - Fully uninstallable: removing the plugin cleans up all its database tables and options.
Screenshots
Installation
- Upload the
devlemon-redirect-managerfolder to/wp-content/plugins/, or install it via the WordPress plugin screen. - Activate the plugin.
- Go to Tools DevLemon Redirect Manager to start adding redirects.
FAQ
-
Does it support external redirects?
-
Yes. You can redirect to any valid
http://orhttps://URL. Dangerous URL schemes such asjavascript:,data:, andfile:are always rejected. -
Does it collect visitor data?
-
No. The only data stored is an aggregate hit counter per redirect rule. No IP addresses, user agents, cookies, or personal information are ever recorded.
-
What happens when I deactivate the plugin?
-
Your redirect rules are preserved in the database. Redirects will simply stop working while the plugin is deactivated.
-
What happens when I delete the plugin?
-
All redirect rules and plugin options are permanently removed from the database.
-
What is the difference between 301, 302, 307, and 410?
-
301 is a permanent redirect — search engines will update their index and transfer authority to the new URL. 302 and 307 are temporary redirects that preserve the original URL in search engine indexes. 410 tells search engines and browsers that the content is permanently gone and should be removed from indexes; no destination URL is needed.
-
Does it modify .htaccess or any server configuration files?
-
No. DevLemon Redirect Manager processes redirects entirely through WordPress PHP execution. Server configuration files are never touched.
-
Does it support wildcards or regular expressions?
-
Not in this version. Matching is exact and based on the URL path. This keeps behaviour predictable and easy to audit.
-
What does “query strings are ignored during matching” mean?
-
A redirect rule for
/page/will also match/page/?utm_source=newsletter. The query string is not part of the match criteria. -
How does loop detection work?
-
The plugin checks for direct loops (A A) and one-hop indirect loops (A B where B A already exists) at the time you save a redirect.
-
Can I import existing redirects?
-
Yes. Go to the Import page and upload a CSV file with the format:
source,target,status_code. See the import page for a full example.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“DevLemon Redirect Manager” is open source software. The following people have contributed to this plugin.
Contributors
Translate “DevLemon Redirect Manager” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.0.5
- Fixed: Prevents the admin interface and action hooks from being registered twice if duplicate plugin copies are loaded in WordPress.
- Improved: Added a defensive one-time initialization guard for the admin controller.
1.0.4
- WordPress.org review: Changed the public plugin name to DevLemon Redirect Manager and aligned the slug/text domain with devlemon-redirect-manager for a more distinctive identity.
1.0.3
- Code quality: Removed the development-only legacy database migration that triggered Plugin Check database warnings.
- WordPress.org readiness: Keeps the unique devlrdm_ / DEVLRDM_ prefix without legacy SQL compatibility code.
1.0.2
- Compatibility: Updated Tested up to to WordPress 7.1.
- WordPress.org: Removed manual translation loading and bundled translation files. WordPress.org loads translations automatically.
- Code quality: Replaced the previous short internal prefix with the unique DevLemon prefix devlrdm_ / DEVLRDM_ across global identifiers.
- Upgrade safety: Added a one-time migration for redirect rules created with development builds that used the previous storage prefix.
1.0.1
- Fixed: Plugin URI now points to the plugin-specific page.
- Improved: Translation strings are compatible with translate.wordpress.org.
- Fixed: Escaping applied to all dynamic output in the admin list view.
- Code: Removed unused variable from list view.
1.0.0
- Initial release.