Wikipedia:Requested moves/Closing instructions

The following are guidelines for closing Wikipedia:Requested moves discussions. Please only apply these after the normal seven day listing period has elapsed. These guidelines are addressed to formal move requests that occur on talk pages, i.e. controversial move requests, but are instructive as to the necessary page history investigation and preservation and cleanup procedures advisable upon any move. Requests listed in the technical requests section can be simply removed after they have been processed. Where technical moves are contested, move the listing to the contested technical requests section.

Failure of an RM Closer to follow the spirit and intent of these instructions, especially about properly weighing consensus with applicable policies and guidelines, may result in the initiation of a Move Review.

Who can close requested moves

Conflicts of interest

In closing a discussion, it is important to avoid conflicts of interest, because such circumstances cast doubt on the fairness of the closure, and often make the closure unstable. Even the appearance of conflict of interest is worth avoiding, for the same reason. Remember that there is no harm in erring on the side of caution.

Apparent conflicts of interest can arise in different ways:

• Any editor who has participated in a move discussion, either in support of the move or in opposition to it, will very likely be seen as a biased judge of that discussion.
• An editor who has previously closed a move request relating to the same article may not be seen as unbiased, especially if the previous request they closed is similar to the new request.
• Conflicts of interest may arise, or appear to arise, in many ways, and it is good to be alert to these possible circumstances.

No user, whether an administrator or otherwise, should ever close an unwithdrawn requested move discussion in which they supported or opposed, and in which the result of discussion is not a unanimous result. However, it is fine for a discussion participant to close a requested move in the following circumstances:

• If the discussion reaches a unanimous result after a full listing period (seven days).
• If the nominator wishes to withdraw a proposal about which no one has yet commented, or which is unanimously opposed. In this case, the nominator may close the discussion as "withdrawn".
• If the closer's participation in the discussion has been limited to clarifying questions, or is otherwise neutral with respect to the proposed move.

If any question of conflict of interest does arise, the best solution is for the potentially conflicted editor to recuse him or herself from closing the discussion, and leave it to someone who is more clearly neutral.

Non-admin closure

Experienced editors in good standing are allowed to close some requested move surveys. It is recommended that any non-admin closure be explicitly declared with template {{RMnac}} after the closer's signature.

Non-admin closes normally require:

• The consensus or lack of consensus is clear after a full listing period (seven days).
• No history merge or history swap is necessary.
• There are no more than a few associated subpages that need to be moved along with the move of the page under discussion, such as voluminous talk page archives. (Administrators have the ability to move up to 100 pages in a single click.)

Non-administrators are reminded that closing a discussion calls for an impartial assessment of consensus or lack of consensus, through arguments supported by directly relevant policy and guidelines (while keeping broader Wikipedia policy, guidelines, and consensus in mind). Any editor wishing to express an opinion on the requested move should join the discussion, not close it.

Many editors do not approve of non-admins closing contentious debates. Non-admins should be cautious when closing discussions where significant contentious debate among participants is unresolved. All non-admin closures are subject to review by an admin; but if the conditions listed above are met, the mere fact that the closer was not an admin is not sufficient reason to reverse a closure.

Where a move is not technically possible without administrative intervention, non-admins closing a discussion and then tagging the redirect with {{db-move|1=PAGE TO BE MOVED HERE|2=REASON FOR MOVE}} should actively monitor that speedy deletion request, and be ready and willing to perform all tidying after the move (as instructed below), such as fixing all double redirects created and fixing fair use rationales of images included on the page.

Determining consensus

Consensus is determined not just by considering the preferences of the participants in a given discussion, but also by evaluating their arguments, assigning due weight accordingly, and giving due consideration to the relevant consensus of the Wikipedia community in general as reflected in applicable policy, guidelines and naming conventions.

Unlike articles for deletion, where lack of participation requires relisting, no minimum participation is required for requested moves because for most moves there is no need to make a request at all; the need arises only because of a technical limitation resulting from the target article name existing as a redirect with more than one edit. Thus, if no one has objected, go ahead and perform the move as requested unless it is out of keeping with naming conventions or is otherwise in conflict with applicable guidelines or policy. Further, any move request that is out of keeping with naming conventions or is otherwise in conflict with applicable guideline and policy, unless there is a very good reason to ignore rules, should be closed without moving regardless of how many of the participants support it. Remember, the participants in any given discussion represent only a tiny fraction of the Wikipedia community whose consensus is reflected in the policy, guidelines and conventions to which all titles are to adhere. Thus, closers are expected to be familiar with such matters, so that they have the ability to make these assessments.

If objections have been raised, then the discussion should be evaluated just like any other discussion on Wikipedia: lack of consensus among participants along with no clear indication from policy and conventions normally means that no change happens (though like AfD, this is not a vote and the quality of an argument is more important than whether it comes from a minority or a majority). However, sometimes a requested move is filed in response to a recent move from a long existing name that cannot be undone without administrative help. Therefore, if the closer feels that no consensus has been reached, they may move the article back to the most recent stable name. If the most recent stable name is itself a matter of dispute, closers are expected to use their own judgment in determining the proper destination.

Relisting

If a discussion is ongoing or has not reached a reasonable conclusion, you may elect to re-list the discussion, though it is entirely optional and up to the closer. Relisting simply consists of stating Relisted. ~~~~ before the initial requester's first timestamp (see this diff for an example), or the previous relisting comment. This gives the request a new timestamp which RMCD bot will use as the date to relist the entry on the requested moves project page. This can be done using {{subst:relisting}}, which also signs it automatically.

If the discussion has become stale, or seems that it would benefit from the input of more editors, some editors will notify at least one relevant WikiProject of the discussion, in addition to (or instead of) relisting it. The template {{RM notification}} could be useful for this. These WikiProjects can often be found by means of the banners placed at the top of many articles' talk pages.

Moving procedures

Edit history of destination page

The majority of target names for move requests already exist as redirects to the present names. Whether a redirect or otherwise, that existing target title should be investigated to see whether it has a minor or major page history. If it has a minor page history, generally meaning it only existed as a redirect, and was never a duplicate article, never had content that was cut and pasted to the present title, nor merged there, it may simply be deleted. However, if the target page title has a major history it should never be simply deleted, as we need to retain such page histories for proper copyright attribution. There are three ways to deal with target pages with major histories, dependent on circumstances. In the event this situation presents itself on a move, click "show" below for instructions.

Procedure for redirects with major histories

1. For page histories resulting from cut and paste moves, the correct way to fix this is to merge the page history of the present article and the redirect, using the procedure outlined at Wikipedia:How to fix cut and paste moves. On rare occasions, this procedure will not work correctly. Once a history merge is done, it cannot easily be undone, so don't pick this option unless it is definitely the right one. You can request history merges at Wikipedia:Cut and paste move repair holding pen.
2. For duplicate articles and merged content, or alternatively for cut and paste moves, the page histories of the article and the redirect can be swapped. For cut and paste moves this leaves a bifurcated history, but has less chance of causing problems. Simply move one of the pair to a temporary name (NAME/temp is suggested), suppressing the creation of a redirect (in the event you forget to suppress the redirect, delete the same); next, move the other page of the pair across to the first one's old location, again suppressing the redirect and deleting the same if you forget; next, move the first page from its temporary location to its new name. Finally, fix the old redirect to point at the article again (at this point, it will be pointing to itself). See also WP:SWAP.
3. Another option is for redirect pages with major histories to be archived into a talk namespace, and a link then placed on the article's talk page. (An example of such a page is at Talk:Network SouthEast, which was originally created as a duplicate article at Network SouthEast and later archived, when the original article was moved from Network South East).

Cleaning up after the move

It is important that you clean up after any move you perform. Accordingly, you should not close any move if you are unwilling to do the necessary clean up tasks listed below.

Fixing double redirects

Moving a page changes any redirects that pointed to the original page location, into double redirects. These make for an unpleasant experiences for the reader, waste server resources, and make the navigational structure of the site confusing. It is the responsibility of the closer to fix these. Periodically a bot will attempt to fix any double redirects missed but that does not relieve the closer of the responsibility which should be handled soon after the move.

The "move succeeded" summary page that you are taken to directly upon a move provides a link entitled "Check what links here" specifically geared to listing offending double redirects created by a move. Fix any double redirects shown on the resulting page.

Some talk pages, archive pages and subpages that you may also have moved, may also have had redirects that have become double redirects. These associated moved pages are listed at the bottom of the move succeeded page. Open up the prior page names (which should now be themselves all at redirects) and click on "What links here" in the toolbox on the left hand side of the page, then click on "Hide transclusions" and "Hide links". This is the manual procedure to perform the same search the move succeeded page provides with the "Check what links here" link noted above.

Fixing fair use rationales

Please check whether there are any images on the moved page with fair use rationales (any Commons images can be immediately excluded, easily recognizable by the logo on the image page: ). If you find such fair use images present, change all mentions of the prior article name, to the retitled name, so that the image is not marked for deletion as orphaned.

Fixing category sort keys

Many pages have a template above the page categories in the form {{DEFAULTSORT:Name}} Where the name field provided in the template is the old title of the page (pages are sometimes categorized in other ways), change it to the new title. Alternatively, in some pages categories are piped in the category links themselves, e.g., [[Category:Monty Python films|Name of Film]]. In the example you would fix the name of the film.

Fixing hatnotes, DAB pages and first sentences in leads

Though not as common as the above, a move may occasionally render a hatnote obsolete. The documentation page at {{Hatnote templates documentation}} may be instructive in finding a suitable replacement, if one is needed (sometimes simple removal may be appropriate). Often the reason for the hatnote is because there is either a disambiguation page related to the topic, or another topic pointing to yours and vice-versa per WP:TWODABS. In such cases you should visit either the DAB page or the other article with the hatnote, and replace the old name of the article you have just moved, with its new name. The first sentence of the article's lead section may, following the move, need tweaking to conform the language to the changed title.

Fixing talk page archiving

Some archiving bots, such as MiszaBot, have hardcoded page names in their archiving settings. After closing the move and moving the talk page archiving, the bot settings should be updated on the talk page to the new name of the talk page.

Moves of disambiguation pages to primary topic titles

Unlike most moves where the pages that link to the moved title will still point to it after the move because of redirects, when a disambiguation page is moved to a primary title, this severs the connection between pages which linked to the primary title. For example, if Foo is moved to a parenthetically disambiguated name, and Foo (disambiguation) is then moved to Foo, everything that linked to Foo, now leads to the primary disambiguation page. In such instances, significant cleanup involving hand dabbing of the pages that formerly linked to the title may be needed. At the very least, following such a move, list it at Wikipedia:Disambiguation pages with links#To do.

Closing the requested move

When you complete an entry on the project (whether the move was accepted or rejected), remove the {{requested move/dated}} tag from the talk page, or change {{requested move/dated}} to {{requested move/old}}. You should also add and sign a comment to indicate whether the move was accepted or rejected in the discussion area for the requested move. This can take the form of an informal note or a more formal close (see below).

There are a few options for formally closing the move request survey on the affected article's talk page. One is to use the templates {{subst:RM top|result of the discussion.}} and {{subst:RM bottom}}. The other is just to leave a statement like "This article has been renamed per the above move request". For requests that for some reason did not apply, you can use {{subst:notmovedmalformed}} or a similar statement based on the circumstances.

Step-by-step formal closing procedure

After clicking the [edit] tab next to the move discussion, you may follow these step-by-step instructions for closing an RM discussion:

Before closing	After closing	Description
==Requested move==	==Requested move==	Leave the header alone; the close starts below it.
{{Requested move/dated|Foo}}	{{subst:RM top|'''RESULT.'''}}	Replace text on left with text on right. Add {{RMnac}} within the template if necessary.
DISCUSSION	DISCUSSION	Body of the discussion stays unchanged.
	{{subst:RM bottom}}	Add the bottom template.

• If additional explanation is provided as to why you have closed the move discussion as a certain result, add additional comments immediately after '''RESULT'''..
• Save the page with an edit summary such as "Closing requested move survey; page moved/not moved".

After closing, the page should look similar to this:

Requested move

---

The following discussion is an archived discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review. No further edits should be made to this section.

The result of the move request was: RESULT. [Additional comments]. Example (talk) 12:09, 10 July 2024 (UTC)

---

Foo → Foobar – rationale of nominator. Example (talk) 12:09, 10 July 2024 (UTC)

• Supports/Opposes with discussion

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Add {{Oldmoves}} or {{Old move}} to the talk page

After the move is complete, the {{Oldmoves}} or {{Old move}} templates can be added to the top of the talk page (or updated if already present), allowing editors to see previous move discussions that might otherwise be archived. In the case of pages with multiple move discussions, these templates should always be added/updated after the closure of an RM.

Automatic removal of request from Requested moves page

Once the article's talk page has been updated, there's no need to return to the Wikipedia:Requested moves page and delete the article's entry there; this will be performed automatically by a bot.

Using move protection during RMs and immediately after RM closes

See also: WP:MOVP

Some RM discussions are contentious; un-discussed, unilateral page moves during a discussion or page moves made immediately after and contrary to an RM close decision are disruptive and hurt the integrity of the RM process. Admins monitoring RM discussions should use their discretion to move protect articles during contentious RM discussions when they believe a premature, un-discussed unilateral move would be disruptive to the discussion. The same discretion should be used to start or continue move protection immediately after the RM close. Generally, such move protection should be limited to no more than 30 days under normal circumstances. The RM closing comment should reference the move protection.

Bot considerations

"Time could not be ascertained"

A request will be listed in a special section titled "Time could not be ascertained" on Wikipedia:Requested moves if the listing bot cannot ascertain the date on which the request was made. This may be because:

• The move request was closed while a bot update was in progress. This should resolve itself with the next bot update.
• (Malformed requests) The move request is not signed. Sign the move request, and the problem is solved. If you are signing for someone else and you use {{Unsigned}}, you must place today's time/date stamp for this to remedy the problem, so you can use the form {{subst:unsigned|Foo|~~~~~}}, and note this uses five tildes to place the time stamp, or the actual timestamp can be copied from history - but adding (UTC) is required, and the hidden left-to-right mark at the end of the date must be deleted.
• A missing – between the proposed move and the proposal description will prevent the description from appearing. This can be fixed by simply adding the missing –.
• Unusually formatted signatures will prevent recognizing the end of the proposal description, for example, if the date is formatted Month Day, Year instead of Day Month Year. This can be fixed by editing the timestamp or adding a formatted time stamp.[1] In the first case, December 20, 2012 was changed to 20 December 2012, in the second case, a second time stamp was added.

Header confusion

Because the instructions state that the talk page section containing the move request should be called "Requested move", occasionally two sections with the same name will appear on a talk page. When this happens, the bot will link to the first one, even if the current move request is the second one. This can be remedied by giving the section containing the current move request a different name, such as "Requested move 2", or by giving the older section a different name, like "Requested move (month year)". A duplicate header for the same discussion can be deleted.

If the talk page section heading is not picked up, look for a blank space after the section header == equal signs, including on the line following the heading, and remove any.

Ampersands

The bot is unable to correctly parse ampersands, as they are the first character of an escape sequence. They need to be escaped as & within the template after the request move template is subst'd. In a multimove from a page containing an &, the current1= parameter needs to be left blank to allow subst'ing the template. After which the page name needs to be added, with the & escaped using & so that the proposed move will be displayed correctly. The same technique can be used if the error appears that the current page is not the current page, leaving the current1= parameter blank until after the move template has been subst'd.