The page mover user right ('extendedmover' user group) allows users to move pages without leaving behind a redirect and to quickly move subpages when moving parent pages.

At their discretion, any administrator can grant this right to experienced and trusted users who regularly move pages and demonstrate familiarity with Wikipedia's policies and guidelines regarding page moving and naming. Users are expected to have at least 6 months of editing history and at least 3,000 edits. Users should also have experience with the requested moves venue and know how page moving works.

If you wish to request page mover rights for yourself or another user, please see Wikipedia:Requests for permissions/Page mover. Administrators do not need to request or add this user right for themselves or other administrators, as it is automatically granted to administrators.

There are currently 400 users with page mover, which makes the total number of users with this permission 1,264 (the rest are administrators).

Flags granted

The page mover group includes the following user rights:

  1. suppressredirect (move a page without creating a redirect)
  2. move-subpages (move a page and all its subpages in a single action)

Suppressredirect

By default, a redirect is created with each page move. This is undesirable in some cases, such as when reverting pagemove vandalism, or when the page name needs to be made available for a different page. With the suppressredirect right, page movers can move pages without leaving a redirect.

Page moves that do not leave a redirect will still be logged, but with a note ("without leaving a redirect"). These moves are not recorded in the deletion log. However, if the source page remains without content, it will be displayed like any other deleted page: logged-in users will still see the "A page with this title has previously been deleted" message, listing the deletion and move logs for that page; and anonymous IPs will still see the "Wikipedia does not have a page with this exact name" error message.

Move-subpages

With move-subpages, a page mover can move a page and all of its subpages in a single action. For example, a user could rename Talk:Foo to Talk:Bar, and also move Talk:Foo/Archive 1 to Talk:Bar/Archive 1 in a single action. This becomes useful when moving a page with a lot of archives.

Suppress redirect criteria

Shortcuts

Page movers can suppress a redirect during a page move if the redirect would be eligible for one of the criteria for speedy deletion. G3, G6, R2, and U1 and are the most commonly applicable criteria of the lot for redirects that would result from a page move. The five widely undisputed uses for suppressredirect are codified here:

No. Criteria Shortcut
1 Reverting page move vandalism (WP:CSD#G3) WP:PM/C#1
2 Moving pages within a requester's own userspace to another location (WP:CSD#U1) WP:PM/C#2
3 Moving pages from a title unambiguously created in error or in the incorrect namespace (WP:CSD#G6) WP:PM/C#3
4 "Round-robin" page moves when blocked by a redirect with non-trivial page history – see below (WP:CSD#G6) WP:PM/C#4
5 For non-admin page movers with the file mover user right only: Moving files per WP:FNC#9 (WP:CSD#G6)
Note: Currently, such moves can be undone only by administrators.		 WP:PM/C#5
6 Moving a page from the mainspace to another namespace when appropriate (WP:CSD#R2) WP:PM/C#6

Two procedures for "round-robin" page moves
  1. The correctly-named redirect page B is moved to a new page C without leaving a redirect behind. This is followed by the incorrectly-named page A being moved to where B was without leaving a redirect behind. Then C is moved where A was without leaving a redirect behind. Note: Redirects are suppressed during all three moves in the round-robin page move process.
  2. Another way to do a round-robin is to move the incorrectly-named page A to a new page C without leaving a redirect behind. Follow that by moving the correctly-named page B to where A was without leaving a redirect behind. Then C is moved where B was without leaving a redirect behind. Note: Redirects are suppressed during all three moves in the round-robin page move process.
  • Both of the above procedures work equally well and will give the same end result.
  • There is a redirect to this page, Draft:Move, that can be used as a holding pen for a subpage used as C above. For example, the correctly-named redirect B in the first procedure above can be moved to C = Draft:Move/temp page. The subpage name that appears after the slash (/) can be any name chosen by the page mover as long as it is a red-linked, non-existing page when the round-robin procedure begins. When the round robin is finished, then the C page will once again be a red link.
  • See also the examples below.

Round-robin page moves

Swapping two page titles example

You may want to move The Adventures of Gromit the Hobbit to Gromit the Hobbit, but the latter title already exists as a redirect, and has edits which prevent a one-step move-over-redirect. Here instructions to do so using the tools provided by this right:

(edit summaries suggestion: linking WP:PM/C#4 within the move summaries is a good practice)

Conduct expectations

Page move disputes

This right should never be used to gain an upper hand in page move disputes. You have a privilege that most editors do not have. Editors without the right are sometimes unable to revert your moves (e.g. "round-robin" moves). Therefore, avoid making unilateral decisions, and revert upon request if a page move of yours proves to be reasonably controversial. Lastly, never wheel war with admins or other page movers.

Have a strong password

See also: Wikipedia:User account security

Page movers must have a strong password and follow appropriate personal security practices. Because a page-move vandal with these rights would be able to quickly move many subpages, a compromised account will be blocked and its privileges will be removed for site security. In the unlikely event that your account is compromised, notify an administrator immediately so they can block your account and remove any sensitive privileges to prevent damage.

Guidelines for granting

1. The editor should be a registered Wikipedia user for at least 6 months.
2. The editor should have made at least 3,000 edits.
3. The editor should have experience with moving pages in accordance with guidelines. Participation in and closing requested moves and move reviews is a good way to gauge this, but not required.
4. The editor should have no behavioral blocks or 3RR violations for a span of 6 months prior to applying.

The above items are merely guidelines. An administrator may grant page mover rights to users they otherwise deem competent.

Criteria for revocation

The user right can be revoked for violating any of the above conduct standards and for other misconduct. Additionally, it can be revoked at any time by an administrator without any process or prior notice in any of the following circumstances:

  1. The editor demonstrated a pattern of performing obviously controversial moves without first determining consensus.
  2. The editor demonstrated a pattern of failing to exercise sufficient care when moving pages, resulting in serious errors appearing on pages, or when using suppress redirect.
  3. The editor used the permission to gain the upper hand in disputes.
  4. The editor performed any blatant vandalism (not limited to page move vandalism).
  5. The editor failed to report to an administrator after noticing unauthorized use of their account or otherwise neglected account security practices.
  6. The editor has been inactive for 12 months.

Additionally, the right may be removed immediately at the request of the editor.

If your page mover right was revoked and you would like to appeal the decision, first discuss with the revoking administrator. If after such an exchange you still feel the matter is unresolved and requires outside input, you may post at WP:AN to appeal the decision. Request for the right after a revocation for inactivity or self-requested removal must be made at WP:PERM.

See also

Categories