anadnet

Current Version 5.2.4
This plugin has two redirect functionalities – “Quick Redirects” and “Individual Redirects”:
<h4>QUICK REDIRECTS (301 Redirects)</h4>
Quick Redirects are designed to be quick and simple to add. You do not need to have an existing page or post set up to add one. You just put the Request URL and the Destination URL and the plugin will redirect it. This type of redirect is great for fixing typos when a page was created, redirecting old URLs to a new URL so there is no 404, and to redirect links from an old site that has been converted to WordPress.
<h4>INDIVIDUAL REDIRECTS (for existing pages/posts)</h4>
For pages/posts that already exist, the plugin adds an option meta box to the edit screen where you can specify the redirect location and type (301, 302 or meta). This type of redirect is useful for many things, including menu items, duplicate posts, or just redirecting a page to a different URL or location on your existing site.
For best results use some form of WordPress Permalink structure. If you have other Redirect plugins installed, it is recommended that you use only one redirect plugin or they may conflict with each other or one may take over before the other can do its job.
<h4>What You CAN Do (aka, Features):</h4>
<ul>
<li>Works with WordPress Nav Menus</li>
<li>Works with WordPress Custom Post Types (select setting on options page)</li>
<li>You can set a redirected page or menu item to open in a new window (Quick Redirects require Use jQuery? option to be set)</li>
<li>You can add a rel=”nofollow” attribute to the page or menu item link for the redirect (Quick Redirects require Use jQuery? option to be set)</li>
<li>You can completely re-write the URL for the redirect so it takes the place of the original URL (rewrite the href link)</li>
<li>You can redirect without needing to create a Page or Post using Quick Redirects. This is useful for sites that were converted to WordPress and have old links that create 404 errors (see FAQs for more information).</li>
<li>Destination URL can be to another WordPress page/post or any other website with an external URL.</li>
<li>Request URL can be a full URL path, the post or page ID, permalink or page slug.</li>
<li>Option Screen to set global overrides like turning off all redirects at once, setting a global destination link, make all redirects open in a new window, etc.</li>
<li>View a summary of all redirected pages/posts, custom post types and Quick Redirects that are currently set up.</li>
<li>Plugin Clean up functions for those who decide they may want to remove all plugin data on uninstall.</li>
<li>Import/Export of redirects for backup, or to add bulk Quick Redirects.</li>
<li>Built-in FAQs/Help feed that can be updated daily with relevant questions.</li>
<li>Optional column for list pages to easily show if a page/post has a redirect set up and where it will redirect to.</li>
<li>Helper functions for adding or deleting redirects programmatically (see ‘filters-hooks-helper_functions.txt’ file in plugin folder for help and usage).</li>
</ul>
<h4>What You CANNOT Do:</h4>
<ul>
<li>This plugin does not have wild-card redirect features.</li>
<li>This plugin DOES NOT modify the .htaccess file. It works using the WordPress function wp_redirect(), which is a form of PHP header location redirect.</li>
<li>You cannot redirect the Home (Posts) page – unless you set a page as the home page and redirect that.</li>
<li>If your theme uses some form of custom layout or functionality, some features may not work like open on a new window or no follow functionality UNLESS you have the Use jQuery? option to set.</li>
</ul>
This plugin is not compatible with WordPress versions less than 4.0. Requires PHP 5.2+.
PLEASE NOTE: A new page or post needs to be Published in order for Page/Post redirect to happen for Individual Redirects (existing page is not necessary for Quick Redirects). It WILL work on a DRAFT Status Post/Page ONLY, and I mean ONLY, if the Post/Page has FIRST been Published and the re-saved as a Draft. This does not apply to Quick Redirects.
<h4>TROUBLESHOOTING:</h4>
<ul>
<li>To include custom post types, check the setting on the plugin option page – and you also can hide it from post types you don’t want it on.</li>
<li>If you experience jQuery conflicts with the plugin, try turning off the Use jQuery? setting in the options page. BUT, please note that if this option if off, the new window and no follow functionality may be inconsistent (this mainly depends on how your theme is set up)</li>
<li>If you check the box for “Show Redirect URL below” on the edit page, please note that you MUST use the full URL in the Redirect URL box. If you do not, you may experience some odd links and 404 pages, as this option changes the link for the page/post to the EXACT URL you enter in that field. (i.e., if you enter ‘2’ in the field, it will redirect to ‘http://2’ which is not the same as ‘http://yoursite.com/?p=2’).</li>
<li>If your browser tells you that your are in an infinite loop, check to make sure you do not have pages redirecting to another page that redirects back to the initial page. That WILL cause an infinite loop.</li>
<li>If you are using the Quick Redirects method to do your redirects, try to use Request URLs that start with a ‘/’ and are relative to the root (i.e., ‘http://mysite.com/test/’ should be set to ‘/test/’ for the request field).</li>
<li>If your site uses mixes SSL, use relative links whenever possible (i.e., ‘/my-page/’). The plugin is designed to detect the incoming protocol and try to apply the appropriate protocol to the destination URL.</li>
<li>Links in page/post content and links that are created using get_permalink() or the_permalink() will not open in a new window or add the rel=nofollow UNLESS you have the Use jQuery? option set.</li>
<li>If your page or post is not redirecting, this is most likely because something else like the theme functions file or another plugin is outputting the header BEFORE the plugin can perform the redirect. This can be tested by turning off all plugins except the Quick Page/Post Redirect Plugin and testing if the redirect works. Many times a plugin or bad code is the culprit.</li>
<li>We try to test the plugin in many popular themes and alongside popular plugins. In our experience, (with exception to a few bugs from time to time) many times another plugin is the cause of the issues – or a customized theme. If you do notice a problem, please let us know at info@anadnet.com – along with the WP version, theme you are using and plugins you have installed – and we will try to troubleshoot the problem.</li>
<li>Check the FAQs/Help located in the Plugin menu for more up to date issues and fixes.</li>
</ul>

Quick Page/Post Redirect Plugin

We've stopped using this because it has apparently been taken over by people who exploit it to add advertising to the sites that use it. Please remove from this catalog.

Adware/malware added recently.

Easily redirect pages/posts or custom post types to another page/post or external URL by specifying the redirect URL and type (301, 302, 307, meta).

Sylwester Ulatowski

Post Forwarder lets you syndicate content from one WordPress site to any combination of destinations with a single click at publish time — or schedule it ahead with the built-in calendar. Configure as many portals as you need and choose per-post which ones receive each article.
Supported Destinations
<ul>
<li>WordPress sites — forwards via the REST API with taxonomy mapping, featured image upload, ACF field support, and duplicate prevention. One-click authorization using WordPress Application Passwords, or enter credentials manually.</li>
<li>LinkedIn — posts as a link-share article card with your excerpt, featured image thumbnail, and hashtags auto-generated from your WordPress post tags. Supports personal profiles and organisation pages. One-click connect — no configuration required.</li>
<li>X (Twitter) — posts the title and post URL as a tweet; the featured image attaches directly on paid API tiers or appears as a link preview card. Connect with your own free X developer app.</li>
</ul>
Plan ahead with the content calendar
Post Forwarder includes a built-in weekly calendar so you can do more than fire-and-forget on publish. Schedule posts to go out to your connected channels at the time that suits you, see everything that’s queued at a glance, and manage upcoming posts across all your WordPress sites, LinkedIn, and X from one screen. Great for keeping a steady publishing rhythm without babysitting the clock.
WordPress forwarding highlights
<ul>
<li>One-click “Save & Connect with WordPress” using the built-in Application Password flow.</li>
<li>Taxonomy mapping with automatic fallback to tags.</li>
<li>Featured image, ACF fields, and custom post types are carried across.</li>
<li>Duplicate prevention so the same post is never forwarded twice.</li>
</ul>
LinkedIn highlights
<ul>
<li>Zero-configuration connect — click “Connect with LinkedIn” and authorize in one step.</li>
<li>Featured image is uploaded directly to LinkedIn and shown as the article thumbnail.</li>
<li>WordPress post tags become LinkedIn hashtags automatically (the tag “my topic” becomes #MyTopic).</li>
<li>Supports personal profiles and organisation pages.</li>
<li>Token expiry is shown in settings, with a reconnect prompt before it lapses.</li>
</ul>
Compatibility
Tested with WordPress 7.0 and PHP 8.3.
<h3>Platform Requirements & Limitations</h3>
<h4>WordPress</h4>
<ul>
<li>The destination site must run WordPress 5.6+ with the REST API enabled (default).</li>
<li>The connecting user must have at least the Editor role on the destination site.</li>
<li>Use “Save & Connect with WordPress” for one-click Application Password authorization, or enter a username and Application Password manually.</li>
</ul>
<h4>LinkedIn</h4>
<ul>
<li>No extra configuration required — one-click connect handles sign-in.</li>
<li>LinkedIn access tokens expire after 60 days. The plugin shows the expiry date and prompts you to reconnect.</li>
<li>For organisation page posts set the Author URN to <code>urn:li:organization:YOUR_ORG_ID</code>. You’ll also need the Community Management API product approved on the LinkedIn app (not needed for personal profile posts).</li>
<li>LinkedIn needs the post URL to be publicly reachable to show an article card. Posts from localhost or <code>.local</code>/<code>.test</code> domains fall back to image-only or text+URL mode.</li>
</ul>
<h4>X (Twitter)</h4>
You need a free X developer account to post tweets. X limits write access per developer app, so each plugin user connects their own app.
Step 1 — Create an X developer account (one-time)
<ol>
<li>Go to <a href="https://developer.x.com" rel="nofollow ugc">developer.x.com</a> and sign in with your X account.</li>
<li>Click Sign up and agree to the terms — your developer account is created instantly.</li>
</ol>
Step 2 — Create an app and get credentials
<ol>
<li>In the <a href="https://console.x.com" rel="nofollow ugc">Developer Portal</a> go to Apps and click Create App.</li>
<li>Give it any name (e.g. “My Post Forwarder”).</li>
<li>Open the app, click Keys & Tokens then User authentication settings then Set up.</li>
<li>Set:
<ul>
<li>App permissions: Read and write</li>
<li>Type of App: Web App, Automated App or Bot</li>
<li>Callback URI: the callback URL shown in the plugin’s X portal settings</li>
<li>Website URL: your site URL</li>
</ul>
</li>
<li>Click Save and copy the Client ID and Client Secret (the secret is shown only once).</li>
</ol>
Step 3 — Connect in the plugin
<ol>
<li>In Post Forwarder -> Settings -> Connection Configuration, add an X portal.</li>
<li>Enter the Client ID and Client Secret you copied.</li>
<li>Click Save Portals, then click Save & Connect with X.</li>
<li>Authorize the app on X and you are redirected back with a “Connected” badge.</li>
</ol>
Notes: 
* The free tier allows 1,500 tweet writes per month. Each user’s app has its own separate quota. 
* X access tokens are long-lived and refreshed automatically before expiry. 
* Featured images on the free tier appear as link preview cards (public sites only), not as direct attachments. The X Basic plan enables direct image upload.
<h3>External Services</h3>
Post Forwarder only sends data when you choose to connect an account or forward a post — nothing is sent in the background.
To publish to LinkedIn or X (Twitter), the plugin uses a small open-source connection helper to handle the secure sign-in step, then sends the post you’re forwarding (such as its title, link, and image) to the network you connected. WordPress-to-WordPress forwarding talks only to the site you set up.
You stay in control: connect or disconnect any destination at any time, and advanced users can self-host the connection helper. Each network’s handling of the content you send is governed by its own terms:
<ul>
<li>LinkedIn — <a href="https://www.linkedin.com/legal/user-agreement" rel="nofollow ugc">Terms</a> · <a href="https://www.linkedin.com/legal/privacy-policy" rel="nofollow ugc">Privacy</a></li>
<li>X (Twitter) — <a href="https://twitter.com/en/tos" rel="nofollow ugc">Terms</a> · <a href="https://twitter.com/en/privacy" rel="nofollow ugc">Privacy</a></li>
</ul>
<h3>Technical Notes</h3>
Security: 
* OAuth tokens are stored in the WordPress database. Enable at-rest encryption on your host for best protection. 
* Sensitive fields (access tokens, client secrets, passwords) are never echoed back to the browser — submitting a blank field preserves the saved value. 
* All form inputs are sanitized and validated; WordPress nonces protect all forms and OAuth callbacks.
Tested with: 
* WordPress 7.0 
* PHP 8.3
Minimum Requirements: 
* WordPress 5.6+ 
* PHP 7.4+

Post Forwarder

Forward WordPress posts to other WordPress sites, LinkedIn, and X — automatically on publish or scheduled from a built-in content calendar.

Quick Page/Post Redirect Plugin vs Post Forwarder