Overview
Create memorable local paths for web, email or telephone destinations without changing existing pages or posts.
This guide explains how to install WPSDDC Redirect Gateway, set up its options and use it in your everyday WordPress workflow.
Requirements and Compatibility
- WordPress 6.0 or later.
- PHP 8.1 or later.
- An account with permission to install and activate plugins. Site settings require administrator permissions.
It works independently: WP StudioDDC HQ and other collection plugins are not required to register its administration screen.
Installation
- Obtain the installable WPSDDC Redirect Gateway ZIP package and keep a current site backup before installation.
- In the dashboard, open Plugins → Add New Plugin → Upload Plugin.
- Select the ZIP file, choose Install Now and then Activate Plugin.
- Open WPSDDC → Redirect Gateway to access its controls and usage information.
For manual installation, copy the wpsddc-redirect-gateway folder into wp-content/plugins/ and activate the plugin from Plugins. The package entry file is wpsddc-redirect-gateway.php.
Configuration and Options
Rules use one source path and destination per line, separated by a vertical bar. Save at most 50 exact rules. Start with a temporary 302 redirect while checking destinations; choose 301 when a permanent destination is final.
| Setting | Initial Value | Options |
|---|---|---|
| Enable Redirects | Disabled | Enable or disable |
| Redirect Status | 301 | 301 — Permanent / 302 — Temporary |
| Accept a Leading Language Code | Disabled | Enable or disable |
How to Use the Plugin
- Open WPSDDC → Redirect Gateway and enter a rule such as profile | https://example.org/profile in the rules field.
- Choose 302 while configuring the destination, enable redirects and save the settings.
- Visit the local source path in a new browser tab. Use a path that does not already belong to a published page, post or another public route.
- If your site needs the same rule after a language prefix, explicitly enable that option. An exact stored language-specific rule takes priority.
- Once the destination is final, select 301 if the move is permanent. Remove or edit a rule from the same settings screen when its destination changes.
Practical Example
Use contact | mailto:[email protected] for an email shortcut, or call | tel:+34910000000 for a telephone shortcut. Replace these sample destinations with your own public contact details.
profile | https://example.org/profile
contact | mailto:[email protected]
Data and Operating Limits
Up to 50 local rules are supported. Matching navigation receives an HTTP redirect; the server does not fetch the destination. Optional language prefixes depend on your configuration.
Frequently Asked Questions
Does the plugin record clicks or fetch the destination?
No. It sends the configured HTTP redirect. It does not fetch remote content, log clicks or use request query parameters to choose a destination.
Where can I find the included help?
Open WPSDDC → Redirect Gateway and expand the native Help tab at the top of the screen. Its sections explain getting started, data and limits, and version details and support links.
Troubleshooting
Existing public routes keep their normal behavior, and redirects apply only to GET and HEAD requests. Check for a path conflict, invalid destination, reserved path or redirect loop. A browser may retain a previous 301; retest in a fresh session after correcting the rule.
Updates and Deactivation
- Back up the database and files before updating.
- When WordPress offers an update in Plugins, use its native update action. To update by ZIP, upload the new package and choose to replace the installed version when WordPress prompts you.
- Review the changes included with the package, keep the settings you need and check a typical workflow after updating.
To stop the feature, deactivate the plugin from Plugins. Deactivation does not delete WordPress content and does not replace a backup.
Support and Related Links
For support, include the WordPress, PHP and plugin versions, the relevant setting and the steps needed to reproduce the issue. Share only the information needed to describe it.


