PageRenameAuto-Update can fix page links and transclusions on other pages when not leaving a redirect. This script adds a button in the dropdown on any page (called "Rename & update"), which will redirect to the page renaming form. It is strongly recommended to have a bot flag applied to your user account while using this script, as it has the potential to severely clutter the recent changes list. This script works best when used as a Gadget, but can still be used in personal or wiki-wide Wikia.js regardless.

Note that this script does not rename sub-pages (yet); they will have to be renamed individually.


This is a maintenance script that involves renaming pages. This script is considered semi-automated editing. Do not use this script without first reviewing your wiki's policies regarding automated editing and obtaining necessary approvals and/or user rights. You must have Administrator or Content moderator rights on the wiki you wish to use this on.


Add this JavaScript on your wiki:

Global Personal Site-wide
w:Special:Mypage/global.js Special:Mypage/common.js MediaWiki:Common.js
importScriptPage("PageRenameAuto-update/code.js", "dev");
importArticles — Best Practices for installing JavaScript on FANDOM
The importArticles statement is designed to combine multiple HTTP requests into a single data transfer, allowing multiple scripts to load and execute faster. If you've been installing several different scripts, your JavaScript file has probably accumulated unnecessary import statements. Click "Expand" to learn how to efficiently batch import scripts to speed up performance and make your code look cleaner. One other approach is by using the MediaWiki:ImportJS.
If your JavaScript file has several lines of code that say importScript, importScriptPage, or importArticles, you may be able to combine them! By batch importing a collection of scripts with a single import, your JavaScript code will load faster and look cleaner. Consider the example below. On the left is an example of what your JavaScript file might currently look like. On the right is how you could improve that code.
Multiple imports — messy and slow One import — clean and efficient
  type: 'script',
  article: 'u:dev:FloatingToc/code.js'
importScriptPage('page1.js', 'wikiname');
importScriptPage('page2.js', 'wikiname');
    type: 'script',
    articles: [
Note: In this example, pay close attention to the placement of commas and other punctuation. For people who aren't familiar with programming (and even those who are!), a common mistake when writing code is to accidentally delete, forget, or misplace critical symbols like commas or quotation marks. This can cause a syntax error that breaks the code. Carefully follow the convention shown here when using importArticles.
But there's much more to importArticles than just this! For more examples and advanced usage, see the help page at Help:Including additional JavaScript and CSS.


Currently, you can change the edit summary that will be displayed in the history when updating links on pages. This option, if specified, must come before your importArticles/importScriptPage function. Note that all values specified must be enclosed inside of the quotation marks.

PRAoptions = {
    editSummary: 'Updating page links (automatic)'