Plugin info

Total downloads: 2,225
Active installs: 30
Total reviews: 0
Average rating: 0
Support threads opened: 0
Support threads resolved: 0 (0%)
Available in: 1 language(s)
Contributors: 5
Last updated: 11/24/2025 (37 days ago)
Added to WordPress: 8/29/2019 (6 years old)
Minimum WordPress version: 5.0
Tested up to WordPress version: 6.8.3
Minimum PHP version: f

Maintenance & Compatibility

Maintenance score

Actively maintained • Last updated 37 days ago

59/100

Is Permalink History abandoned?

Likely maintained (last update 37 days ago).

Compatibility

Requires WordPress: 5.0
Tested up to: 6.8.3
Requires PHP: f

Similar & Alternatives

Explore plugins with similar tags, and compare key metrics like downloads, ratings, updates, support, and WP/PHP compatibility.

"SEO-HEADERS-Easy" Protocol HTTP 1.1
Rating 4.7/5 (3 reviews)Active installs 100
TDMRep: TDM Reservation Protocol
Rating 0.0/5 (0 reviews)Active installs 50
Protocol Relative Theme Assets
Rating 4.0/5 (2 reviews)Active installs 30
Allow Skype Protocol
Rating 0.0/5 (0 reviews)Active installs 30
HTTP URLs
Rating 0.0/5 (0 reviews)Active installs 10
protocols.io Publications Widget
Rating 0.0/5 (0 reviews)Active installs 0

Description

Saves the history of your WordPress site and provides automatic redirects.

Installation

  1. Upload permalink-history.zip to the /wp-content/plugins/ directory
  2. Extract the Plugin to a permalink-history Folder
  3. Activate the plugin through the ‘Plugins’ menu in WordPress

Frequently Asked Questions

How does it work?

This plugin tries to save all changes of permalinks in your system. When someone uses an old permalink that is in the history database it will not show 404 page but instead redirect to the new location.

Does this work with changes made before plugin installation?

Nobe! You need to first install this plugin to start saving the history.

Does this effect my site performance?

For small sites (less than 30.000 posts) there should be no performance issue. We use a custom table with good indexation to provide quick search access for historical permalinks.

But to be honest. Perhaps it could get an issue, yes. Therefore you export a redirect map on the permalinks settings page and make early redirects before php starts working.

Review feed

No reviews available

Screenshots

No screenshots available

Changelog

2.0.2

  • Fix: no css error fix

2.0.1

  • Fix: Gutenberg panel produce js error in non-public post types

2.0.0

  • Breaking: Dropped support for meta box (classic editor)
  • Feature: Gutenberg document settings panel for permalink history
  • Feature: full permalink history endpoint
  • Fix: only save permalinks of publish posts

1.4.0

  • Feature: get history by content id ajax endpoint
  • Fix: database getById sql

1.3.2

  • Fix: meta box for all other post types than post itself

1.3.1

  • Php 8.2 compatibility warning fix

1.3.0

  • Added filters for find redirect use case extensions

1.2.0

  • Added admin ajax endpoint for permalink history mapping

1.1.0

  • Optimization: multisite compatibility

1.0.5

  • Optimization: Performance optimization by reducing redundant function calls
  • Bugfix: Migrate field handler did not clean up old permalinks on update migration. It does now

1.0.4

  • Feature: WP Cli extension

1.0.3

  • Optimization: on check for redirect in frontend (!is_admin())
  • Bugfix: only redirect posts with status publish

1.0.2

  • Bugfix: Was redirecting too early. Works now with amp plugin.

1.0.1

  • Feature: Action “permalink_history_redirect_404” if permalinks could not help you can try it yourself

1.0.0

  • First release