External Permalinks

Enable pages, posts and/or custom post types to have permalinks that point to external URLs. The rel="noopener noreferrer nofollow" attribute will also be added for enhanced security and SEO benefits. Compatible with links added using Page Links To.

Overview

External Permalinks stores an outbound URL on a WordPress content object while keeping it in your admin lists, menus, and editorial workflows. Visitors who open the item’s native permalink are forwarded—commonly with a 301 Moved Permanently—to the external destination, signaling search engines that equity should consolidate on the target (when that is editorially correct). Teams use
this for “resource hub” posts that always live on a partner domain, sponsor stories, or temporary bridges during acquisition rebrands.

Meta boxes or sidebar controls (per implementation) capture the URL; Advanced Settings may gate post types, validate schemes, or adjust redirect codes—confirm UI labels for your release.

Who is this for?

Affiliate and partnership desks surface curated listings in WordPress but send clicks to retailers’ canonical PDPs. Corporate comms teams publish placeholder posts that redirect to intranet PDFs on day one and external microsites later. Developers migrating subdomain blogs can keep old permalinks active while Google updates to the final host. Always pair with analytics events if you need redirect telemetry beyond server logs.

Features

Per-Item Destination

Each post maps to its own external target string stored in post meta.

Single-View Redirect

Visiting /resources/example/ triggers HTTP redirect to configured URL.

SEO-Oriented Status

Defaults toward permanent redirects when appropriate—verify code policy with SEO leads.

Scope Controls

Advanced Settings limit which CPTs may redirect to reduce misuse.

Validation

May block obviously unsafe schemes or local loops depending on filters used.

How It Works

Enable the Module

Enable "External Permalinks" in WP PowerSuite.

Edit Content

Open an allowed item and paste HTTPS URL (or allowed scheme) into module field; save.

Test Incognito

Hit the WordPress permalink; confirm redirect chain length, status code, and final landing page.

Submit to Search Console

When replacing internal pages with outbound-only pointers, monitor coverage and backlinks.

Document Governance

Who may create redirects? How often are targets audited for 404s?

Performance Note

Single extra hop per qualifying request—negligible latency if destination is fast. Archive templates that surface meta per row should avoid N+1 external URL fetches; rely on cached object meta.

Installation & Activation

Install WP PowerSuite

Activate plugin.

Enable External Permalinks

Toggle on.

Configure Post Types

Restrict to types that should ever leave the domain from an editorial item.

Coordinate with Redirect Plugins

Avoid stacking rules that fight this module’s canonical WordPress route.

Requirements

PHP 8.1 or higher WordPress 6.0 or higher Permission to edit scoped post types

Use Cases

ExternalRedirects
“Further reading” landing posts that always click through to Medium or Substack originals until a full migration completes.

GrantListings
Government sites listing grant opportunities hosted on federal domains.

TicketLinks
Event microsites linking ticketing platforms without orphaning navigation.

Frequently Asked Questions

What about feeds and REST?
Syndicated consumers may still see the WordPress URL in GUID fields—test newsletter tools and mobile apps.
Can I use relative paths?
Destinations should be absolute URLs with valid schemes; relative targets risk ambiguous behavior.
Temporary vs permanent?
Use 302/307 only when editorially temporary—confirm Advanced Settings or filters allow status tuning.
Multilingual sites?
Each translation post may store different outbound URLs—maintain per-locale QA spreadsheets.
Security scanners flag open redirects?
Ensure module validates against allowlists or internal policies; never echo raw untrusted query parameters into Location headers.

Troubleshooting

Redirect loop or blank target
Verify destination does not point back to same path, check http↔https mix, and purge stale cache at edge.

302 when expecting 301
Adjust module/SEO plugin settings; conflicting plugins may override status.

Menu item vs single URL mismatch
Menus may link differently than single template—standardize via menu editor.

Destination 404s silently
Schedule quarterly link audits; broken external targets hurt trust and SEO.

On This Page