FAMEPedia:Moving a page

On Wikipedia, a page can usually be renamed if the already existing title is incorrect or needs to be changed; this is called moving a page. A page may also be moved to another namespace without changing the base title—for example, a userspace draft may be moved to article space. Autoconfirmed rights are required for page moving, but you may request a page move at Requested moves if you are not yet autoconfirmed, if there is a technical barrier to the move, or if the retitling is expected to be controversial and you need to seek consensus for the name change.

Files (images and media) can be moved only by Wikipedia administrators and file movers, but moves can be requested.

Category moves should be investigated and planned before they are initiated. Please post requests for category moves at Categories for discussion if you are, or expect to be, unable to complete the process.

Do not move or rename a page by cutting and pasting its content, because doing so fragments the edit history. Instead, please follow the instructions given below.

Reasons for moving a page
There are many reasons why you might wish to move a page:
 * The title does not follow Wikipedia's naming conventions, such as that it is not the common name of the subject or it is overprecise.
 * The subject of the article has changed its name and the new name has come into majority use.
 * The title has been misspelled, does not contain standard capitalization or punctuation, or is misleading or inaccurate.
 * It needs to be disambiguated in some way to avoid confusion with an existing, similarly named topic, or it exists at a disambiguated name but should not because it is the primary topic.
 * It is an article at a descriptive name and the scope of the article has been reduced, extended or otherwise changed.
 * It is an article that has been created as a subpage of a Wikipedian's user or user talk space for development purposes and it is ready to be posted to the mainspace or to draft space.
 * It is a draft article that has been created or edited in draft space for development purposes and it is ready to be posted to the mainspace.

Technical restrictions
Technical restrictions prevent the storage of titles beginning with a lowercase letter, containing certain characters, and using formatting such as italics. Templates which may be used as workarounds include:

Before moving a page
Consider listing pages that you want to have renamed/moved at Requested moves. List them at Requested moves/Technical requests if it appears unlikely that anyone would reasonably disagree with the move, and:
 * You are unable to move the page because your account is too new (the account must be autoconfirmed)
 * You are unable to move the page because the target page exists
 * The page is protected from moves
 * The target page is protected from creation

For other cases, follow the instructions for controversial and potentially controversial moves:
 * If you believe the move might be controversial
 * If you are unsure about the best page name, despite reading Wikipedia:Article naming guidelines
 * If you believe your proposed move would benefit from wider community input

Do not move or rename a page by copying/pasting its content, because doing so fragments the edit history. (Wikipedia's copyright license requires acknowledgement of all contributors, and editors continue to hold copyright on their contributions unless they specifically give up this right. Hence, it is required that edit histories be preserved for all major contributions until the normal copyright expires. See also Copying within Wikipedia.)

If you find a cut-and-paste move that needs to be fixed, please follow the instructions at Requests for history merge to have an administrator take care of the problem.

If you need technical help in a simple page move situation which is blocked by history at the target of the move, list the page at Requested moves/Technical requests following the listing procedure outlined there.

How to move a page
To be able to move pages yourself, you must be logged in and you must have an autoconfirmed account (i.e., generally you must have had the account for four days and made at least ten article edits with it). Moreover, the move will fail if a page already exists at the target name, unless it is simply a redirect to the present name that has never been modified, in which case you can move over the redirect (check the edit history). If you cannot move a page yourself because of a technical restriction, and you expect the move to be uncontroversial, you can list it at the technical section of requested moves. Otherwise, you can make your request at its section for controversial and potentially controversial moves.

To move a page:
 * 1) Go to the page that you want to move. There is no need to click "Edit".
 * 2) Locate the "Move" option at the top of the page.
 * 3) *Most users will find the "Move" option in a drop-down menu at the top right of the screen, labelled "More", after "History" and the "Watchlist" star (see picture). It may be under a menu labelled "Page" if you have enabled "MoreMenu" at Special:Preferences.
 * 4) *The layout of the screen will be different if you have selected a "skin" other than the default Vector in your preferences. In the Monobook skin, it is a tab at the top.
 * 5) *If there is no "move" link at the top of the page at all, the page is most likely protected from moving. Ask for the page to be moved at the technical move request page.
 * 6) Click the "Move" option, and fill in the details of your move.
 * 7) *If the page is for the main encyclopedia, choose "(Article)" from the drop-down box. Otherwise choose the appropriate namespace prefix.
 * 8) *To the right of the text box, enter the new name of the page as the "New title".
 * 9) *Give a reason for the move (which is like an edit summary). Although filling out the "Reason" field isn't required, you should state a reason for the page move.
 * 10) *Choose whether to also move the page's talk page (this box should usually be left checked). This box is not present if the page has no talk page.
 * 11) When ready, click the Move page button and, if successful, the page will be renamed to the new title. The old title will become a redirect page, so any links to the old title will still go to the new page. However, note that double redirects (pages that redirect to the original page), will not automatically follow to the new page, so you will have to refer them manually (as explained at How to fix a double redirect and Checking for double redirects).
 * 12) A successful page move will be recorded in the Move Log (against the old page name) and a "move has succeeded" message will be displayed, on a page looking like this: MediaWiki:Movepage-moved.
 * 13) *If the old page was protected, its protection settings will be generally automatically copied to the new page, and thus be recorded in the Protection Log (against the new page name). If Pending changes was enabled, the settings will be moved but they will not be logged against the new page title.

How to move a category
Most users lack permission to move pages in the category namespace. ("Only administrators, page movers, and bots can move Category pages.") (Conveniently, the Move button is not displayed.)

To request the move, follow the procedure at.

For those permitted to move categories
It is recommended to follow the procedure at, and let a bot handle it, especially for complex cases.

Moving a category manually is possible, but it requires significant post-move cleanup, and can be time-consuming. A category move is not complete until the old category contains only the soft redirect and no pages.

To move a category manually:
 * 1) Move the category page (description wiki markup).
 * 2) Change all of its subcategories. (Change the category of each subcategory to the new category.)
 * 3) Change every page that is listed in the old category to the new category:
 * 4) *Change the category on every page where it is explicitly specified. (This could be hundreds or thousands of pages.)
 * 5) *Change the template code for every template that assigns pages to the old category.
 * 6) **It may be necessary to purge (or perform a null edit on) every page that uses the template(s).

When pages are listed in a category that is not shown in the wiki-markup, this most likely means that a template placed on those pages is adding the category. When the category is moved, the template must also be changed. After the template is updated with the new category, the pages with the template are automatically placed into the job queue and will eventually be updated with the new category. If there are a very large number of pages transcluding the template(s), the process of updating all pages through the job queue may take days, weeks, or even months to complete. Protected pages or templates may require elevated privileges to accomplish the change. In such cases, the normal protected edit request process should be followed. Depending on the number of templates and articles that require elevated privileges to edit them, it may be more appropriate to involve an administrator from the beginning of the process (see Categories for discussion).

Post-move cleanup
Please perform appropriate post-move cleanup after a successful move, as needed.

Change the boldfaced title in the article lead
Since the article name is reflected in the lead section, that section may need to be updated to be consistent with the new name. Along with generic lead corrections, add appropriate hatnotes where appropriate to affected pages.

Address any technical restrictions
If the article meets the criteria for italic titles given in the Article titles policy, place italic title at the top of the article. Some infobox templates, e.g. Infobox album and Infobox book, automatically italicize titles. If only part of the title should be italicized after the move, use DISPLAYTITLE instead.

The moved page may have an existing DISPLAYTITLE that will become invalid after the move and will produce red warnings. It is highly recommended to update these values appropriately to reflect the new title. If its corresponding talk page has a DISPLAYTITLE, it would need to be updated as well.

Fix double redirects
Generally, don't. "Double redirects are easily and automatically fixed by bots, and most are fixed within a few minutes of creation. Because of this, human editors are better off putting their time on other tasks that can't be automated."

Redirects to redirects, a.k.a. double redirects, aren't automatically followed (this prevents infinite loops and spaghetti linking). Don't fix double redirects if you think your move might be controversial and be reverted.
 * 1) Open Special:WhatLinksHere for that page (there may be a shortcut link on the page-moved summary screen to this directly).
 * 2) In the section of that page marked filters, click on the button labeled "Hide links" to filter to redirects to the prior name. For each redirect, change its target to the new page title.
 * 3) If there are more than 50 redirects listed, don't forget to navigate to all parts of the list using the "next 50" or other links available.

Unless subsequently usurped, a page move will result in a redirect page at the old title that sends the reader to the new one. Generally, there is no problem with this – for example, one should not change inbound links in articles to bypass the redirect.

Editing of this redirect itself is usually not helpful, but if such a need exists, then a special care should be taken about inbound "double" redirects. If the page was moved because of a misnomer (i.e. its content has a sense, but does not match the title), then its old title should be replaced or deleted. It should be done quickly, otherwise bots will start to alter redirects bound to the old title, pointing them to the new title, which is obviously not a correct solution in the case of a misnomer.

Contrarily, if the page had a lot of legitimate inbound links, but has to move because of a title usurpation, then inbound redirects should be promptly examined. If most redirects rightfully belong to the page just moved, then the old→new redirect should not be replaced until bots fixed those double redirects. Early replacing the old→new redirect with old→something_else can be especially disruptive, since bots start to "fix" redirects to "something_else" target – see [ example] after usurpation of the title Viper.

Categorizing redirects
Redirects should be categorized per the WikiProject Redirect style guide.

Interlanguage links
Check to see if there are any interlanguage links. Usually, with a page move, the Wikidata for the associated item is automatically updated. If necessary, update it using the "Edit links" link at the bottom of the list of links.

Sort key
If the page has a sort key, change how this article is to be sorted, if appropriate.

Sidebars and navbars
Pages that have a sidebar- or navbar-template will need their page title in the template edited from the old name to the new name. Until this is altered, the old page title, which usually becomes a redirect to the new title, will appear as a blue wikilink instead of as the unlinked page name in boldface type.

Update talk page notifications
Usually, the move discussion has a tag. Follow the instructions given in the tag to inform that the discussion is closed.

Update talk page parameters (including archiving bot settings)
If the talk page is automatically archived, it will have archiving bot settings (such as with or  ) which have hardcoded page names. After closing the move and moving the talk page and its archived subpages, the bot settings needs to be updated or the archiving bot will stop archiving the moved talk page. In some circumstances, this will involve updating (moving) a hard-coded bot subpage.

Editnotices
Occasionally, a page has an accompanying editnotice in the template namespace. For example, the editnotice for 0.999... is Template:Editnotices/Page/0.999.... Sometimes, a page may be accompanied by a group editnotice (like this one), or more rarely, a protection editnotice (like this one). If a page with an editnotice is moved, the editnotices should move with them. Currently, this requires the technical assistance of an administrator or template editor. If the move was done by a non-page-mover a redirect may be left over. This should typically be deleted as G6, unless the editnotice also applies to the redirect itself.

Files: containing non-free content
If you moved an article which contains any non-free content (such as images or sound clips), you will need to edit the files' own Wikipedia page, changing the non-free use rationale to refer to the new article title. This is to ensure continued compliance with the non-free content criteria (part 10c), which if not followed, may result in the file's speedy deletion.

Categories and subcategories
Ensure there are no pages in categories that will no longer be used because of moves. Subcategories from wiki markup and templates should be updated with the new category.

If the title of the article coincides with the name of a category, consider requesting that the category name be changed accordingly. This should be done at Categories for discussion/Speedy specifying criterion C2D.

Page histories
The "move page" function keeps the entire edit history of the page before and after the move in one place, as if the page had always been named that way.

The move itself is recorded in the edit histories of both pages. This feature was introduced in MediaWiki 1.5 and does not work retroactively: older moves are only recorded indirectly, in the page history of the old page name.

You should never just move a page by cutting all the text out of one page, and pasting it into a new one; old revisions, notes, and attributions are much harder to keep track of if you do that. (But you may have to if, for instance, you're splitting a page into multiple topics. If you do, please include a note in the new page's edit summary and talk page stating where you took the text from.) Also see below.

Moving redirect pages
A page that is a redirect can be moved like any other page, although it is rarely useful because it has the same detrimental effect on page history as copy-pasting content to a new page, and making the old page a redirect: when moving a redirect page to a new page name, the redirect on the old page (now directing to the new redirect page) will have to be altered in order to avoid double redirects. So the content of the old page will no longer redirect to the page containing the history of that old page. The effect is that the whereabouts of the page history of the old page (now seemingly a "recently created page") are a bit trickier to find, while on the other hand the new page has a history attached to it not clarifying why it would need to be a redirect page. However, if a redirect page has to be evacuated (for example, to reuse its title), but contains a valuable edit history, then it should be moved (unless merging of history is suitable).

If a redirect page does not redirect to the page it would need to be redirecting to, then the only viable strategy that respects page histories is to adapt the redirect on that page, without moving the page.

Moves where the target name has an existing page
Non-administrators cannot complete a move where the target page exists (except sometimes over a redirect). If the user is not a page mover, moving the existing page out of the way will not help, as it leaves behind a redirect which cannot be overwritten either. Administrators can delete a page and move another page to the deleted name, in one step. Page movers can move the target page to a new location without leaving a redirect, move the intended page to the target page, and optionally request deletion of the moved page.

If the new title already exists and isn't just a redirect to the old title, with no history, and you are not an administrator, the wiki will tell you that you can't rename the page. If this happens, list the move at Requested moves, or (if the replacement of the existing page merits further discussion) nominate the existing page for deletion (typically via Articles for deletion).

Moving over a redirect
If the new title exists but is a redirect to the old title with a single line in the page history, then you can rename the page using the regular procedure. The most common case in which this applies is that of re-renaming a page back to its original name.

Before to the release of MediaWiki 1.28/wmf.16 in August 2016, information about a redirect overwritten by a moved page was lost. Starting with that version, deletion of the redirect has been added to the deletion log; this is the only way that non-administrators can get entries in the deletion log. If the deletion was the result of an earlier move of the page that is now moved back, that information is still available in the history of that page.

More moves back and forth are possible, and the page history of the current title always shows all moves, and that of the other title only contains the edit line of the latest move. Pages moved before MediaWiki 1.5 do not have an entry in the page move log, so only the latest page move prior to MediaWiki 1.5 is recorded. The oldest moves recorded in the move log date to June 28, 2005.

There was a bug in earlier versions of MediaWiki that caused inaccurate dates in edit histories. In these versions of the software, if a page was moved over a redirect, the edit history of the newly created redirect would show the latest move with the correct user name, but with the date and time when the overwritten redirect was created. The date and time of the actual page move was therefore lost (though it appeared in the recent changes list). See [//en.wikipedia.org/w/index.php?title=Talk:PETA&diff=16054409&oldid=1512139 this comment at Talk:PETA] for a demonstration of this bug.

If a redirect has more than just one line in the page history but still a minor edit history, file a technical move request at Requested moves/Technical requests.

Usurping a page title
Usurping a page title is the process of moving an existing page to a new title followed by creating a new page (such as a new article or a disambiguation page) on the old title, or redirecting the old title to a different destination.

Once the move of the original page is completed, the old title instantly becomes a redirect, and the redirect can then be edited to become a separate, possibly unrelated article, disambiguation page, or some other type of page.

It is permitted to usurp a page title for a new article, and it generally does not require administrative assistance, though good judgment should be used in determining if these are best positions for both the old and the new page.

If in doubt, holding a discussion before such a move following the instructions on the requested moves page is recommended. If you wish to create the new page initially before a decision is made from a discussion, you can create it using a different, unused title for the new page you wish to create, and then usurp the title once this is agreed.

If you do decide to boldly usurp a title, it is strongly recommended that you check all incoming links and fix them as necessary. To do this, while on the new page bearing the old title, click on "What links here" below "Tools" in the menu on the left. This will list all the pages linking to the old title. Once you reach this list, check the incoming links on each of these pages and if necessary, modify them to point to the new title of the old page. For more information, see Help:What links here and Disambiguation pages with links.

If there are so many pages linking to the old title, that you feel you cannot make all the changes yourself, or for any other reason, you feel you cannot change them all yourself, place the template converted at the top of the new page you created on the old title. This will let others know that this move was recently made, and that all these changes are necessary.

Move restrictions
Unregistered users and new users who are not yet autoconfirmed cannot move any pages. With a few exceptions, autoconfirmed users have the technical ability to move any page.

Move-protected pages
Administrators can protect pages from moves, so that only administrators can move them. If a page is protected from moves only, the "Move this page" link will not be available. In this case, you can ask that an administrator move it for you, but you should not manually move the page by copying the contents to the new page and redirecting the old page to the new page, as this destroys the page history.

Pages that are protected from editing are implicitly protected from moves.

Moving a file page
Administrators or file movers can move pages in the file namespace. When such a page is moved the associated file is moved as well. The move leaves a redirect that functions like the file itself. For instance, the image can be displayed by linking to a redirect to it. In non-controversial cases you can request a file to be moved by adding the template rename media to the description page of the file. Files should generally only be moved for one of nine reasons.

Files uploaded to Wikimedia Commons cannot be renamed by Wikipedia administrators or filemovers. c:Commons:File naming describes how Commons files should be named. In general, Commons aims to provide stable file names as there might be external file clients and file moving involves significant human and computing resources. Thus renaming should be used with caution. To request the rename of a file at Commons, follow the instructions at Commons:File renaming.

To rename a file:
 * 1) Ensure the file meets one of the nine reasons
 * 2) Place  on the page of the file and a file mover or administrator will move the file if it conforms to the guidelines.

You can also use a script to add the rename request. Twinkle (a Swiss Army knife of maintenance tagging) or LuckyRename (specialized for this job) can do this. For more information about appropriate names for pages in the file namespace, see File names.

Other notes
Avoid moving a page while the edit box of the corresponding Talk page is open: when you hit "Publish changes" you overwrite the redirect to the new talk page (you do not get the usual warning that the page has been edited while your edit box was open) and get a duplication of the contents of the talk page, with your latest addition added to the old instead of the new one.

It is useful to copy the text "moved page ... to ..." (part of the automatic move summary) to the new talk page, especially if there has been discussion about the name of the page.

Moving a page shows up in Recent Changes under "Move log", which links to a log of all moves. It also shows up on the watchlist if the page is watched; after the move both the old and the new name are watched.

Talk subpages
When moving a page, the talk page is automatically moved as well. A talk page may include subpages, such as archives, to-do pages, good article nominations, and the like. To ensure that these subpages are moved, check "Move all subpages, if applicable" during the move process. This ability is granted to administrators and page movers. A list of talk page subpages is visible in the "Special:MovePage" form.

If subpages were not moved, they will show as redlinks on the new talk page. To locate lost subpages, use Special:Prefixindex; enter the name of the old article page followed by a "/" and set the namespace to Talk. Move individual subpages as needed.

On some occasions, one might inadvertently move a talk page incorrectly assumed by the MediaWiki software to be a talk subpage of a different article. For example, Talk:A/B testing is the talk page for A/B testing, but not technically a subpage for Talk:A. If a mover uses move-subpages on Talk:A, the move operation would incorrectly move Talk:A/B testing. (This is not an issue for the article mainspace, as it does not have subpages enabled.)

Moving a portal
A portal consists of a main portal page plus tens, sometimes hundreds, of interconnected subpages. To rename a portal efficiently, post at Requested moves/Technical requests to ask for an administrator to move the page and its subpages, and once that is done, post at AutoWikiBrowser/Tasks to ask for an AWB user to scan all the portal pages to fix the outdated links. You may also need to visit Categories for Discussion to have a category renamed, if the portal's pages have been placed in a category; and Template talk:Portal, if the Portal template does not recognise the new name.

Undoing a move
To undo a move from page A to page B, simply move page B back to page A. But if someone intervened to the A → B redirect, then the move cannot be fixed without special privileges, in which case the guidance about undiscussed moves at the "requested moves" page may be helpful.

Note that the usual "undo" link on history or diff pages does not work on moves. An easy way to rename the page back is clicking "" from the history page, typing in the previous page name that you want to revert to and then "" link from the corresponding record in Special:Log.

The software requires that the redirect be pointing to the page you're moving it from. Therefore, if a user moved page A to page B and then to page C, you cannot simply move C to A. If a bot has not "fixed" the double A → B redirect yet (see above), then you have to:
 * 1) Move page C to page B
 * 2) Move page B to page A

If page A has subsequently been edited, or the move software is behaving weirdly, only an admin can sort things out:
 * 1) Delete page A (make sure it has no useful history – you may wish to add an explicit author credit on a talk page to compensate)
 * 2) Move page B to page A
 * 3) Delete page B (should be a history-free redirect to page A )

"Move wars" are highly unproductive, and leave vast numbers of pointless redirects littering the place, which some poor soul will have to fix.

After undoing a move, if you do not need B as a redirect, tag it for deletion (using the appropriate process on the wiki you're using, for instance 'speedy deletion' or list it at 'redirects for discussion'), or (administrators only) just delete it.

Swapping two pages
There are two methods to swap pages A and B, preserving history. Classic sequence
 * 1) Move page A to the title C (previously non-existing, and preferably to a name useful for redirecting)
 * 2) Tag page A for deletion (the method of doing this depends on the wiki), or (administrators only) just delete it.
 * 3) Move page B to the title A (allowed because A is deleted)
 * 4) Tag/Delete page B as above
 * 5) Move page C to the title B (allowed because B is deleted)
 * 6) Tag/Delete page C as above, unless it is useful as a redirect to B

Improved sequence This improved sequence, sometimes called a "round-robin move", does not require deletions, but rather it relies on the redirect-suppressing (red move) feature, which is available to administrators and page movers. You can think about it as compressing two operations (moving and deleting the resulting redirect) to one. The classical sequence has an advantage that it relies only on conventional operations such as WP:G6. Help with this task can be found at.
 * 1) Move page A to the title C (previously non-existing) without creating a redirect
 * 2) Move page B to the title A (allowed because A is evacuated) without creating a redirect
 * 3) Move page C to the title B (allowed because B is evacuated) without creating a redirect unless it is useful as a redirect to B

The same sequences, but with only two moves, can be used for half-swapping (chain shifting) two pages (such that A would become C and B would become A ).

Fixing cut-and-paste moves
Many past renamings took place before the move page function was created by our hard-working developers, and others are done by people not aware of this function. Such manual moves were done using cut and paste. As a result, the page history of an article or talk page can be split among two or more pages. In some circumstances, administrators can fix this by merging page histories. If you find a cut-and-paste move that needs to be fixed, please follow the instructions at Requests for history merge to have an administrator take care of the problem.

Move vs rename
The terms "rename" and "move" mean the same in this context. They just refer to different models for picturing the operation:


 * rename: keep the page but give it another name; the page history is now attached to the new name; a new page with the old name is created which redirects to the new name and whose page history records the renaming.
 * move: move the contents and the page history to a new page; change the old page into a redirect; change the page history into one that only records the move.

Since the system marks the page with the old name as a new page, it applies the first of the two models. (The entry in the page table connects a new page name to the page ID. The revision table just gets entries about the move, nothing else, because the relation between page ID and revision IDs remains the same.) This model avoids "changing the history", a kind of "historical revisionism".

"Rename" may have other meanings on Wikipedia. See Help:Rename.

Automating multiple subpage moves
Administrators and other users with the "move-subpages" right (such as page movers) are also given an option to move up to 100 subpages. Talk subpages can be moved along with the move target.

Administrators and page movers can also use the Mass move tool by adding the following lines to their common.js page, which will add a "Mass move" link to their tools menu on the left of the page: