![]() | This page documents an English Wikipediadeletion guideline. Editors should generally follow it, thoughexceptions may apply.Substantive edits to this page should reflectconsensus. When in doubt, discuss first onthis guideline's talk page. |
![]() | Are you new here? If so,welcome! There is a simplified version of this page atWikipedia:Introduction to deletion process. |
Thedeletion process encompasses theprocesses involved in implementing and recording the community's decisions todelete or keeparticles,media, and other pages.
Normally, adeletion discussion must be held to form aconsensus to delete a page. In general, administrators are responsible for closing these discussions, though non-administrators in good standingmayclose them under specific conditions. However, editors maypropose the deletion of a page if they believe that it would be an uncontroversial candidate for deletion. In some circumstances, a page may bespeedily deleted if it meetsstrict criteria set by consensus.
Note:Office actions and declarations from theWikimedia Foundation Board or thesystem administrators, particularly concerning copyright, legal issues, or server load, take priority over community consensus.
Deletion discussions |
---|
Articles |
Templates and modules |
Files |
Categories |
Redirects |
Miscellany |
Speedy deletion |
Proposed deletion |
Thespeedy deletion process applies to pages which meet at least one of thecriteria for speedy deletion (CSD), which specify the only cases in which administrators have broad consensus support to, at their discretion, bypass deletion discussion and immediately delete Wikipedia pages or media.
Before deleting a page through the speedy deletion process, please verify that it meets at least one of the criteria for speedy deletion, check thepage history to assess whether it would instead be possible torevert and salvage a previous version and to determine whether there was acut-and-paste move involved, and search for other information which may impact the need or reason for deletion:
If speedy deletion is inappropriate for a page:
When deleting a page through the speedy deletion process, please specify the reason for deletion in the deletion summary, so that it will be recorded into thedeletion log. Quoting page content in the deletion summary may be helpful, butmust not be done forattack content orcopyrighted text. In some cases, it would be appropriate to notify the page's creator of the deletion.
If they wish, administrators are free to use theCSD Helperuser script to help them process editors' CSD nominations. It makes the process smoother and quicker.
Theproposed deletion (PROD) process applies to articles and files that do not meet the stringent criteria for speedy deletion, but for which it is believed that deletion would be uncontroversial. In this process, an editor places a tag on the article or the file, and any editor can remove the tag to save the page. If the tag remains after seven days, the page can be deleted. For instructions on handling articles and files that have been proposed for deletion, seeWikipedia:Proposed deletion#Deletion.
Astronger version of the proposed deletion criteria (BLPPROD) applies to articles about biographies of living people with no sources. Their deletion can only be contested by adding a source.
Pages may be speedily deleted in the case of unambiguous copyright infringement (seeWikipedia:Criteria for speedy deletion#G12. Unambiguous copyright infringement for details). Pages written extensively by contributors with a history of copyright violation may also be deleted if they qualify forpresumptive deletion and have been listed atWikipedia:Copyright problems for at least 7 days.
If you delete a file due to copyright or non-free use issues that will not apply after some future date (for example, once the file enters thepublic domain in the United States) and that future date is known, please list the file atCategory:Future copyright expiration.
Deletion discussion venues (ordeletion forums) are the six places to formally nominate for a discussion, a page not eligible forspeedy deletion.
Discussion type | Scope | Closing instructions |
---|---|---|
Deletion review (DRV) | For appealing the deletion of a page or outcome of a deletion discussion that appears to be against community consensus, if the request is outside of the scope ofrequests for undeletion, and after discussing with the deleting administrator or closer respectively. | Purpose Starting a discussion Closing instructions |
Move review (MR) | For appealing the closure of a requested move, including one that resulted in a deletion or merger, if it appears to be against consensus or proper closing procedure, and after discussing with the closer. | Purpose Starting a discussion Closing instructions |
Discussions are usually closed after seven days (168 hours). Although thesteps or process for closing deletion discussions vary between the#Deletion discussion venues, a few general principles apply for all deletion discussions.
Usually, closing a discussion is anadministrator action, but experienced users in good standing may close (or relist), perthe guidelines below.
When closing a discussion, make certain that all pages under discussion have anXfD notification template placed upon the page (also known as "tagging" the page under discussion), in order to notify others about the discussion. And pay close attention to this for group nominations, as it is not uncommon for only one of the pages in question to have been tagged. In general, if this happens, all the pages under discussion should be tagged, and once that is done,#RELIST the discussion. If circumstances indicate that relisting may be inappropriate, then instead just close (depending on tagging) part or all of the discussion as "no action", due to the lack of tagged notification.
Consensus is formed through the careful consideration, dissection and eventual synthesis of different perspectives presented during the discussion, andis not calculated solely by number of votes.
Outcomes should reflect therough consensus reached in the deletion discussion andcommunity consensus on a wider scale. (Whileconsensus can change, consensus among a limited group of editors, at one place and time, cannot override community consensus on a wider scale.)
Other possible (non-standard) decision results, and/or "combinations" may sometimes be appropriate at the closer's discretion. For example, "Merge and delete", "Rename and merge", or "Transwiki". The closer should aim in any case, to decide based upon consensus, policy, and community norms.
In addition, it can sometimes be useful to provide a brief explanatory note, to make the rationale for the decision clear. This is especially true in heated and high public profile discussions, or where many views will be given little weight (or a few views given substantial weight), or where you think the basis of the close may be misunderstood or potentiallyreviewed by others.
Also remember thatnobody is obligated to close a discussion, nor is it crucial that a discussion be closed immediately once its week-long run has ended. If you feel that there is a conflict between the views expressed, andWikipedia's policies and guidelines (e.g., an inappropriate super-majority viewwithout an appropriate basis), it may be preferable to instead comment yourself, rather than closing, even if the "due date" for closing has been reached, and leave the close to another editor.
Deletion discussions concerning biographies of living persons who are relatively unknown, non-public figures, where the subject has requested deletionand there is no rough consensus to keep,may be closed as 'delete' per thedeletion policy andBLP policy (request for deletion). Closers should review these policies to confirm the criteria are met, and then use their discretion.
If a nomination has received few or no comments from any editor, and no one has opposed deletion, and the article hasn't been declined for proposed deletion in the past,the closing administrator should treat the XfD nomination as an expired PROD and follow the instructions listed atWikipedia:Proposed deletion#Procedure for administrators. Generally, this will result in soft deletion (see below), but administrators should evaluate the nominating statement as they would a PROD rationale. Closing an unopposed XfD nomination under this procedure does not require the discussion to have been relisted any particular number of times.
If the nomination has received very few or no comments but appears controversial to the closing administrator, or has been declined for proposed deletion in the past, the discussion may be closed at the closer's discretion and best judgement. Common options include, but are not limited to:
Soft deletion is a special kind of deletion which may be used after an article's deletion discussion. If a deletion discussion receives minimal participation, the article may be deleted. However, in this case, the article can be restored for any reason on request. If your article was soft-deleted, you can request it be restored atRequests for undeletion. The closer should make it clear the deletion is a soft delete as part of the close, ideally with a link to this guideline.
There is consensus among the community that problematic or likely problematic articles[2] with an appropriate redirection target may beblanked and redirected by any editor if there are no objections. This similarly applies to deletion nominations as well; if no editor suggests that the corresponding article should be kept, then redirection is an option.
If, at the end of the initial seven-day period:
it may be appropriate torelist the discussion instead of closing, in order to allow for the possibility that further discussion might lead to a discernible consensus. However, relisting should not be a substitute for ano consensus closure. If the closer feels there has been substantive discussion, and disparate opinions supported by policy have been expressed, but consensus has not been achieved, a no-consensus close may be preferable. A relisted discussion may be closed once consensus is determined, without necessarily waiting for another seven days.
Editor qualifications torelist a discussion are the same as required toclose a discussion - see#NAC, for further information.
While having adeletion notice on a page is not harmful, its presence over several weeks can become disheartening for potential editors. Therefore, repeatedly relisting discussions merely in the hope of getting sufficient participation isnot recommended. In general,a discussion should not be relisted more than twice. When relisting for a third (or further) time, or when relisting a discussion with a substantial number of commenters, the relisting editor should write a short explanation either within the{{relist}} template, or in addition to it, on why they did not consider the current state of the discussion sufficient to determine a closure result.[4]
When relisting a discussion, it should beremoved from the log for its original date (or in some venues replaced with a pointer to the current date) and moved to the current date's log where the discussion will continue. Scripts and gadgets such asXFDcloser automate the process.
In general,administrators (admins) are responsible for closing deletion discussions, but non-administrators who areregistered (i.e. notIP users) may close (or relist) these discussions, with the following provisions:
{{nacd}}
("non-admin closure") template in the comment for the closure.Do not close a discussion if:
However, you may close your own#Withdrawn nomination as aspeedy keep, when all other viewpoints were for keep as well.
If an administrator has deleted a page (including by speedy deletion) but neglected to close the discussion, anyone with a registered account may close the discussion provided that the administrator's name and deletion summary are included in the closing rationale.
Closed discussions generally should not be re-opened. A non-admin should not re-open a discussion unless they were the closer. Anuninvolved administrator, acting in their individual capacity, and giving their reasoning, may re-open a discussion closed by a non-admin. The administrator should notify the original closer of the re-opening. Discussions may also be re-opened as a result of a closure review discussion, such as at theAdministrators' noticeboard, or at theDeletion review orMove review processes. If a discussion is re-opened, take it only as a sign that the decision may not have been as obvious as you thought.
When closing an AfD, do the following:
{{subst:Afd top|'''result'''}}. ~~~~ | ← Addthis line at thevery top of the page, with the appropriate result in '''bold'''. |
===[[Header]]=== | ← Leave this line, the article page title, alone. |
← Remove the line containing{{REMOVE THIS TEMPLATE WHEN CLOSING THIS AfD}}. | |
DISCUSSION | ← Body of the discussion stays unchanged |
{{subst:Afd bottom}} | ← Add bottom template |
Discussion type | Information page | Instructions for closing |
---|---|---|
Articles for deletion (AfD) | Wikipedia:Articles for deletion | |
Categories for discussion (CfD) | Wikipedia:Categories for discussion | Wikipedia:Categories for discussion/Administrator instructions |
Files for discussion (FfD) | Wikipedia:Files for discussion | |
Miscellany for deletion (MfD) | Wikipedia:Miscellany for deletion | Wikipedia:Miscellany for deletion/Administrator instructions |
Redirects for discussion (RfD) | Wikipedia:Redirects for discussion | Wikipedia:Redirects for discussion/Administrator instructions |
Templates for discussion (TfD) | Wikipedia:Templates for discussion | |
Deletion review (DRV) | Wikipedia:Deletion review |
As a result of a closer#Determining consensus, a deletion discussion may result in one of a number of distinct outcomes, with certain outcomes being more common at certain deletion discussion venues.
Outcome | Commonly used for | Details |
---|---|---|
Keep | All | Arough consensus to retain (i.e. not delete) a page, though not necessarily in its current form. To implement a 'keep' outcome: close the deletion discussion as 'keep'; edit the page to remove the deletion notice; and record the outcome on the page'stalk page using one of several venue-specific templates (see#Closing instructions per venue for details). |
Delete | All | A rough consensus to remove (i.e. not retain) a page, including its entire revision history. To implement a 'delete' outcome: close the deletion discussion as 'delete'; delete the page, and link to the deletion discussion in the deletion summary; and, if the page should not be recreated, remove incoming links in other pages (except in discussions, archives and tracking pages). |
No consensus | All | A lack of a rough consensus for any one particular action. To implement ano consensus outcome: close the deletion discussion as 'no consensus'; edit the page to remove the deletion notice; and record the outcome on the page's talk page using one of several venue-specific templates (see#Closing instructions per venue for details). |
Move (non-category pages), or Rename (categories) | All | Issues to be addressed by changing the page title (and perhaps then expanding or improving its content). This can happen at AFD especially, if the article could be suitable for Wikipedia, but is created under an inappropriate title, and was nominated for deletion, but consensus agrees it isfixable if the title is changed. Categories require a different method than other pages. |
Merge | Articles, categories, templates | This combines two separate pages into a single page. Merge votes should bespecific and clear. If you wish to merge templates or categories, use the deletion discussions. If you wish to merge articles, do not use a deletion discussion, but instead discuss it on the talk page. |
Disambiguate (or "Dabify") | Articles, redirects | If the discussion concludes that the title can refer to many topics, it can be changed to a disambiguation page to list all of them. |
Redirect | Articles, templates, miscellaneous pages | This would be used if the page has no unique and usable content, but information about the topic is found in another article. |
Userfy | Articles, templates, miscellaneous pages | This would move the page into the creator's userspace so that they may make improvements. IfWikipedia essays are nominated, they will sometimes be moved to userspace if they are found to violate policies or guidelines. |
Incubate (or "Draftify") | Articles | This changes the article into a draft to be improved so that it meets inclusion requirements. |
Delete but allow undeleting withan appropriate licence | Files | If a file is only deleted due to copyright issues, it could be re-uploaded if these issues are resolved |
Listify | Categories | This means to delete the category and create a list article instead. |
Retarget | Redirects | This means that the redirect should lead to a different page. |
Refine (or "Keep and refine") | Redirects | The redirect should lead to a specific section of the page it currently targets (e.g.Africa →Africa#History) |
In certain situations, a deletion discussionmay require correcting, moving elsewhere, or a null outcome ("procedural close"), due to issues with the deletion nomination rather than the merits of the page itself.
A deletion discussion that is poorly formatted should not be closed for this reason alone, in order to avoidbiting new users. Instead,fix it.
Error | Correction |
---|---|
No deletion notice on nominated page | The best course of action is to add the tag and note that you've done so. The time of tagging would then be treated as the nomination time. |
Currently linked fromMain Page | If the nominated page is currently linked from the Main Page, remove any tag from the page itself. Then, if there are legitimate concerns, please useWikipedia:Main Page/Errors to have the link removed before nominating the article. If there are clearly none, or the nomination is disruptive, the nomination page should be closed early (see 'speedy close'). |
Nomination is an immediate objection to a prior deletion outcome, more appropriate fordeletion review | List it at deletion review on the nominator's behalf, and link it appropriately (including linking it from the closed discussion), notify the nominator, and close the deletion discussion. |
Venue inappropriate (e.g., a file hosted onCommons, category or redirect at AFD, or discussions that the chosen venue is unable to address) | List the topic at the correct venue, notify the nominator, and close the discussion providing a link to the new discussion. Never close a discussion as a wrong venue without opening a discussion at an appropriate one. |
Page does not exist or has already been deleted prior to the nomination | Close the discussion, and place a notice on the nominator's talk page. It is entirely possible that they may have mistyped the page name, or that the page was already deleted before they could start the deletion discussion. If the former was the case, politely tell the nominator to properly start a new discussion with the correct title, and the time they start the new discussion will be treated as the nomination time. |
In general, deletion discussions should remain open for at least seven days (168 hours) to allow interested editors adequate time to participate. However, under certain circumstances, discussions may be closed prior to the seven-day timeframe.
Closers should apply good judgment before speedily closing a discussion, since often it is best to allow the discussion to continue for the entirety of the seven-day period.
Reason | Explanation |
---|---|
Withdrawn | While the nominator may withdraw their nomination at any time, if subsequent editors have suggested an outcome besides keep or added substantive comments unrelated to deletion, the discussionshould not be closed simply because the nominator wishes to withdraw it.
|
Speedy keep | A "speedy keep" close is warranted when the nominator withdraws the nomination or fails to advance an argument for deletion or redirection—perhaps only proposing an alternative action such as moving or merging—and no one other than the nominator recommends that the page be deleted or redirected. A "speedy keep" outcome is also appropriate when the nomination unquestionably is an attempt to vandalize or to otherwise create disruption. For example:
|
Speedy delete (see also§ Speedy deletion) | When the nominated page unambiguously falls within any criteria for speedy deletion, particularlycriterion G10 (attack page) orcriterion G12 (copyright violation), it is not necessary to wait until the end of the discussion period. |
Snowball clause | The "snowball clause" exists to avoidprocess for the sake of process, or when the outcome of the deletion discussion is, or has become,almost certain, such that there is not a "snowball's chance in hell" that the outcome will be anything other than what is expected, and there is clearly no need at all to prolong discussion further. This clauseshould not be used to close a discussion when a particular outcome is merely "likely" or "highly likely", and there is a genuine and reasoned basis for disagreement. This is because deletion discussions arenot a vote; it is important to be reasonably sure that there is little or no chance of accidentally excluding significant input or perspectives, or changing the weight of different views, if closed early. Especially, closers should beware of interpreting "early pile on" as necessarily showing how a discussion will end up. This can sometimes happen when a topic attracts high levels of attention from those engaged (or having a specific view) but slower attention from other less involved editors, perhaps with other points of view. It can sometimes be better to allow a few extra days even if current discussion seems very clearly to hold one opinion, to be sure that it really will be a snowball and as a courtesy to be sure that no significant input will be excluded if closed very soon. |
To search for any mention of an existingfullpagename of interest in "all discussion types" listed above, go to the page of interest, andpreview this line in any of its wikitext:{{#lst: WP: Deletion process | search links }}
These threesearch links will then appear in this box (but in warning coloration):
From that preview, activate a search. From search results, modify the query, return to the preview, or not. Preview is safe. Return and search all three.
The deletion of pages with long histories may impact server performance. As a precaution, therefore, deletions of pages with more than5,000 revisions require the special "bigdelete" user right, which administrators do not have. Such deletions can be requested of stewards atmeta:Steward requests/Miscellaneous.