| Tutorial | Discussion | New page feed | Reviewers | Curation tool Suggestions | Coordination |
 | This page is a reference and tutorial for reviewing new articles. It is essential reading for users interested in joining theNew Page Reviewer group. |
Reading time: approx. 34 minutes
New pages patrol (NPP) is agroup of Wikipedians that check whether new articles, redirects and other pages conform to Wikipedia'score content policies. The purpose of new pages patrol is equally to identify pages which cannot meet this standard, and so should bedeleted, and tosupport the improvement of those that can. Pages that pass new pages patrol don't have to be perfect, just not entirely unsuitable for inclusion.
All new articles and redirects are patrolled, unless the user that created them had theautopatrolled permission. NPP's first priority is to identify pages with serious content problems—includingattack pages,copyright violations, andvandalism—and mark them forspeedy deletion. Beyond that, patrollers consider whether articles are suitable for inclusion in their current state according to the relevant policies and guidelines. Articles considered unsuitable are nominated for deletion or,in certain circumstances, moved to thedraft namespace for improvement. Articles considered suitable for inclusion are marked as 'reviewed', with anotification sent to the user that created it. Reviewers may also flag issues with reviewed pages withmaintenance tags, perform basic copyediting, and/or sort the article into relevant categories and WikiProjects. New pages are notindexed by external search engines until they are patrolled.
New page patrol is carried out by users with thenew page reviewer permission and byadministrators. New page reviewers are expected to have a good knowledge of Wikipedia'scontent policies and prior experience with itsprocesses for handling articles. They primarily use thenew pages feed andpage curation tool for patrolling.
There are currently842 users with the new page reviewer permission and a total of 1,683 new page patrollers (including administrators). Aside from the technical ability to mark pages as reviewed, new page patrollers do not have any special decision-making powers over new articles. They are expected to work carefully andassume good faith, paying particular attention totreating newcomers with kindness and patience. Disputes over new page patrolling should be resolved using theusual processes.
This page consists of the guidelines and resources for using the reviewing system; discussions related to new page patrolling and further help take place primarily at thetalk page for reviewers .
The most important tool is thepage curation toolbar, which appears on all pages in the new pages feed. It contains the actual button to mark a page as reviewed. It also contains an information summary about the page and its creator, tools for tagging articles with maintenance tags, and a tool to send barnstars and other nice things to editors that have worked on the article. A copyright violation detector can be added to the toolbar withthis user script. There are many other useful tools available to make doing NPP easier. You can find many of them on theresources page or linked throughout this page.
Special:NewPagesFeed is the central motor for reviewing new pages and drafts. It logs new pages immediately after the first version is saved. While it is a good idea to reduce the backlog of unreviewed pages by working from the back of the list, it is nevertheless important that serious breaches of policy such as spam and attack pages be deleted very quickly. A comprehensive preferences panel lets you select what kind of new pages you want to review. The system remembers your preferences each time you open the feed. A list daily created by a bot atsorted list classifies all unreviewed articles by topic, along with a short excerpt of the article. Use this list if you prefer to work on articles in your own sphere of knowledge. A system calledORES inserts alerts of possible problems with the article. Other information will easily help you identify if the article creator is a beginner.
This useful script conveniently adds a "Page Curation" link to your top toolbar that loads theNewPagesFeed.
It is often helpful to review the oldest pages in the NPP queue, rather than the newest, as these may have even been indexed by search engines. When reviewing from the back of the queue, you may come across pages that were created long ago but that recently were changed from being a redirect to an article (or vice versa). These articles pose a distinct challenge, as they are often the result ofedit wars, other forms of tendentious editing, or paid editing and spam. You can find a guide to additional concerns and suggestions related to these types of pageshere.
Reviewing articles is the primary purpose of new pages patrol and should be prioritized over other namespaces. Although new articles appear in the new pages feed immediately, take care not to alienate article creators (especially new editors) by patrolling them while they are still in progress. Unless there areserious content problems,wait at least an hour before nominating an article for deletion,blank-and-redirecting it, or moving it to draftspace.
If the page is not a candidate for a deletion process, but has other issues, there is rarely any need to rush. Inform the creator of any problems using maintenance tags, the article talk page, or the message feature of the curation tool and give them time to address them (perhaps several days) before taking further action. If improvements are not forthcoming, itmay be appropriate to move the article to draftspace, to give the creator more space to work on it. However, it is important to remember that 'draftifying' is not a substitute to the deletion process, nor a catch-all solution for articles you don't know what to do with.
Briefly, to review an article:
The rest of this section summarises the range of issues that you might encounter in reviewing an article, in rough order of priority, and how to respond to them. Step 5 is optional – if you don't know what you do with an article, you can always leave it to another reviewer.
There are three types of serious content problems that new page reviewers should immediately respond to: attack pages, copyright violations, and vandalism. You do not have to wait the usual hour before acting to remove these kind of problems. When you tag something for speedy deletion, do not mark it as reviewed.
Thecriteria for speedy deletion (CSD) specify when an article can be immediately deleted without discussion. It is intended to reduce the time spent on deletion discussions for pages or media withno practical chance of surviving one. New page reviewers should be familiar with all the speedy deletion criteria, but the most commonly encountered are:
sufficiently identical copies; this is hard to assess without access to the former page, but if in doubt nominate and the patrolling admin will compare the current version to the deleted history.
You can nominate an article for speedy deletion with the{{db}} series of templates; there is a specific tag for each criterion.A patrolling administrator will then either delete the page ordecline the nomination by removing the tag.Any editor other than the creator of the article may also remove the tag, which should be taken as a sign that the deletion is controversial and thatanother deletion process should be used.If the article creator removes the tag, you can restore it and use {{subst:uw-speedy1}} to warn them on their talk page.Do not mark pages as reviewed after you tag them for speedy deletion. If the nomination is declined, or the creator removes the tag, it will need to be reviewed again.
Always consideralternatives to deletion before nominating an article for speedy deletion. Check the history for a better version; a page is eligible for speedy deletion only if all of its history is also eligible. Consider whether it could bestubbed, merged, orredirected instead. Speedy deletion must be completelyuncontroversial and used in only the most obvious cases. If a page has survived a deletion discussion in the past, it usually cannot be speedily deleted.
| Notability |
|---|
| General notability guideline |
| Subject-specific guidelines |
| See also |
Unless an article falls underwhat Wikipedia is not or the speedy deletion criteria, notability is the main test for determining whether or not it can exist.Wikipedia's notability guidelines are complex, frequently subjective, and change often. New page patrollers should be familiar with the corenotability guideline (especially thegeneral notability guideline, GNGs) and at least some of the more importantsubject-specific notability guidelines (SNGs). However, few if any editors can claim to have a comprehensive knowledge of every notability guideline, so it is important to tread carefully and be aware of what you don't know.
Opinions are divided on how important it is to consider notability during new page patrol.[1] On the one hand, NPP's core purpose is to screen articles that are not suitable for inclusion, and notability is the key test of this in all but the most clear-cut examples of unwanted content. Many patrollers consider notability their "bread and butter" on this basis. On the other hand, assessing notability can be very time-consuming, requiring aproactive search for and evaluation of sourcing, subject-specific knowledge, and ultimately is only decided one way or another via a consensus at AfD. Some have therefore argued that focusing too much on notability causes significant backlogs and that patrollers' time would be better spent on more readily apparent types of unsuitable content.[2]
At a minimum, as a new page patroller, you should be able to identify topics that patently lack notability and nominate them for deletion. You may also opt to investigate the notability of topics in more depth, but bear in mind that a fullWP:BEFORE-style search is only really necessary for AfD nominations. Assessment of articles in topic areas with highly detailed SNGs is best left to reviewers familiar with those areas and guidelines. The{{notability}} maintenance tag (and its more specialised subtemplates) can be used to mark articles on topics of uncertain notability for further review in the future.
You must considerthe alternatives before nominating any article for deletion. First and foremost, if you canfix the issues yourself, do so, or use maintenance tags to bring the article to attention of someone who can. Otherwise, there are alternatives to wholesale deletion that retain some or all of the article's content:
All of these actions may be carried outboldly, unless you think it will be controversial or if it is challenged by another editor. In that case, it should be proposed and discussed at AfD.
If an article is not suitable for inclusion, does not meet any of the speedy deletion criteria, and you have rejected alternative to deletion, it should be nominated for deletion. Most commonly, this is because the topic[4] of the article is notnotable, or violatesWP:NOT. The options are:
In each case, it is important to follow the "before" steps of each of this processes, to ensure the article is actually eligible:
If the article is a cut-and-paste of (all or part of) an article in another language's Wikipedia, which is often the case, it should be tagged with{{db-foreign}} (CSD A2). Do not tag articles written in another language withG1 patent nonsense. If an article is acopyright violation, it may be nominated forG12.
For other non-English articles, follow the instructions atPages needing translation into English/Procedures. Essentially, this consists of reading a machine translation the article (seecomparison of machine translation applications). If the translated content of the article does not violate a CSD and is likely to be notable, you can place the{{notenglish}} template, e.g., {{notenglish|Spanish}}, to flag it for translation. If the content of the article is not worth keeping due to CSD or notability, you should use the appropriate deletion process.
Check that the page title is appropriate and, if not,move it to corrected title. Be aware that there are general naming conventions (such as using sentence case for non-proper nouns, or not adding disambiguation terms in parentheses if they are not needed), and also topic-specificnaming conventions.
If you move an article and the former name is an implausible redirect (and you can'tsuppress the creation of a redirect following the move), you will need to request its deletion using{{Db-r3}}. If you cannot perform the move for technical reasons, ask for help atWP:RM#TR. If the move is potentially controversial, follow the instructions atWikipedia:Requested moves.
Wikipedia's licensing allows editors tocopy material from one article to another and totranslate material from our sister projects in other language, providing that the original authors of the material are attributed. Copied material is therefore generally not a problem for NPPunless an entire article has been copied to a new title (a 'cut-and-paste move'), the copying has created acontent fork, or theproper attribution is not been maintained.
The attribution requirement is usually fulfilled by a statement in theedit summary that links to the original page (e.g.copied content frompage name; see that page's history for attribution). If you find an article that contains copied or translated material without attribution, you can add one in adummy edit. For further information, seeWikipedia:Copying within Wikipedia#Repairing insufficient attribution.
To aid reader navigation and make efficient use of editor resources, Wikipedia prohibits having multiple articles on the same or an extremely similar topic, which is known ascontent forking.
If you encounter a broad or popular topic that you are surprised didn't already have a page, there is a high chance that it has been forked. Authors sometimes also link to pages they have forked from the "see also" section.
When you encounter a fork, you have two options. If the new page has content the existing page does not, nominate the pages formerging; otherwise, just convert the new page into aredirect.
Finding they cannot change a typo in the title, or being unaware of redirects and wanting a topic found at another title, new users sometimes create new pages with the content of existing articles – 'cut-and-paste moves'. Doing so severs the edit history, required under copyright. In such situations, request deletion using{{Db-a10|article=Existing article title}} / {{Db-same|article=Existing article title}}. Though these templates have their own warnings, separately warn the user using{{subst:Uw-c&pmove}}. In the rare situation that the user has added significant content to the copy they posted that isworth merging, list the page for a history merge (note: not the same as a merge) atWP:SPLICE.
Where an existing page or redirect has been used as the target of a cut-and-paste move the edit should be reversed, restoring the original page content.
If you come upon an article on a duplicate topic but that has aseparate origin (not copied from the existing article, addressed above), this also can be asked to be deleted under CSD A10. However, here, if the article has content that warrants merging, perform amerge (do not ask for a history merge) and redirect to the existing article. Be sure to provide mandatory copyright attribution when you do so. SeeWP:MERGETEXT.
The following steps are often useful for improving new articles or bringing them to the attention of others who will. However, do not feel obligated to perform them.Wikipedia is a work in progress and your main responsibility as a new page patroller is to identify articles that definitely should not be included, not bring them up to a given standard.
If you find an unpatrolled redirect that is at RFD, or you send a redirect to RFD, mark it as reviewed.
Is somebody creating a lot of redirects, and you are finding zero problems with them? Consider posting an application for them at theredirect autopatrol list. They need around 100 redirects to qualify. Usextools (and select "only include redirects") to check number of redirects created.
If a redirect or blanked page is converted to an article, it will be marked as unreviewed and placed in the new pages feed. This is to avoid people hijacking reviewed redirects to create unreviewed articles.
I'd say that on a typical day of patrolling the back end of the queue, I'll go through 150-300 [redirects], send 5-10 to RfD, tag around 5 with G5 or R3, and either retarget or convert-to-dab 5 more. Attack redirects are less frequent, I'll come across a handful of attack redirects per week. --Rosguill
Redirects from titles in languages other than English are allowed if there is a significant connection between the language in question and the target subject. Examples include non-English titles for creative works originally written in those languages such asCien años de soledad, or regional names for foods such askebapcinja. These are allowed even in alphabets other than Latin, such asМосква or日本. However, names for common objects that have no particular association with any culture despite global use (e.g.Bahnwagen, German forRailroad car) or even use with a sufficiently broad subset of countries (e.g.Bidé, Italian for bidet), are discouraged and generally deleted atRfD.
New page patrollers should focus their patrolling on mainspace articles and mainspace redirects. Patrolling other namespaces is discouraged due to the importance of patrolling mainspace (search engine indexing implications, most likely to contain BLP or copyright violations, etc.) and also the large backlog. Below are some checklists for patrolling other namespaces, kept for historical reasons:
Disambiguation pages are located in mainspace so will appear inSpecial:NewPagesFeed like a regular article. They are usually easier to review than a normal article. Here are some tips specific to disambiguation pages.
The draft namespace is managed by theArticles for Creation project. New drafts are not reviewed by NPP. However, unless the user that moves them isautopatrolled, drafts moved to the article namespace enter the new pages feed and should be reviewed as normal. New page patrollers are automatically placed on the allow list for theArticles for Creation Helper Script gadget, in case they are ever interested in helping out at AFC. The AFC reviewing skillset is very similar to new page patrolling, but be sure to read AFC's tutorials to familiarize yourself with the differences.
The purpose of new pages patrol is to review thecontent of new pages, not theconduct of the editors who created them. Nevertheless, new page patrollers are well-placed to identify conduct issues such assockpuppetry,promotion,serial copyright violations,undisclosed paid editing and other conflicts of interest, andchild protection issues. It is always worth checking the history of pages for evidence of these issues.
New page patrollers are in a good position to spotconflict of interest (COI) editing, which includes people writing about themselves, their family, friends, clients, employers, or anything else they have a financial and or other close relationship with. Conflict of interest editing is strongly discouraged, but permitted within certain conditions, namely that a) the COI is disclosed and b) that editors with a COI avoid directly editing the article in question. For new articles, the latter requirement means that they should be created via theArticles for Creation process and accepted by a reviewer there. Editing with afinancial conflict of interest ('paid editing') is even more tightly regulated, with disclosuremandated by the Wikimedia Terms of Use and AfC mandated by local policy.
Some indicators of COI editing include:
If you suspect conflict of interest editing in a new article, the first thing to do is to check whether the creator hasproperly disclosed a COI (check both their user page, the article history, and the article talk page) and whether the article was accepted by an AfC reviewer. Then:
paid-en-wp@wikimedia.org, where afunctionary will review it and take appropriate further actionWhen reviewing any article where you suspect a conflict of interest, be especially on the lookout foradvertising masquerading as articles,promotional content,notability of commercial entities, overuse ofprimary orunreliable sources, and related problems. If you are not sure if there is a conflict of interest, or need help investigating one, ask at theCOI Noticeboard. At all times, remember toassume good faith and avoidcasting aspersions: an editor with an undisclosed conflict of interest may simply not be aware of our requirements.
In serious cases, the creator of a new page may need to be blocked to prevent further disruption or damage to Wikipedia's reputation. Familiarise yourself with theWP:UAA andWP:AIV systems and their policies and report such cases as necessary.
Other editors, particularly those who are interested in fighting vandalism, also regularly check newly created articles to tag them for maintenance or deletion. Although they don't have access to the features of the Page Curation Toolbar, all editors, even IP users, can tag pages. Tagged pages remain listed in the feed until patrolled by a reviewer, enabling New Page Reviewers to identify and isolate poor patrolling. Use the 'Unreview' feature for good faith errors and see the templates that can be used to encourage users to do less demanding maintenance tasks until they have more experience. If you find inappropriate new page patrolling, you can use the template{{Stop NPP}} as a supportive ask. In persistent cases however, it will be necessary to escalate through the warning levels and might need administrator attention at a place likeANI or by getting help on theNPP discussion page.
Throughout the entire process of new pages patrol, it is important to remembernot to bite the newbies. Far from being a monolithic horde of vandals,trolls, and spammers, the available evidence seems to indicatethat newcomers write most of Wikipedia's content. If you see a new user or IP address contributingsignificantly, post awelcome template to their talk page, such as {{subst:welcome}} or {{subst:welcomeg}} or, for IPs specifically, {{subst:welcome-anon}} or {{subst:Anonwelcomeg}}, and include a pointer or two of feedback about how they can make their contributions even better. Most will gladly welcome the support.
It is also important toassume good faith as much as possible, or, minimally, toassume incompetence instead of malice. For example, remember not everyone is as computer-literate as you; some people will accidentally blank or damage pages when attempting to cut and paste material from Wikipedia. Others may not understand that, yes, their changes really are visible to the entire world immediately; consider using {{subst:uw-draftfirst}} to suggest that new users work on their article as a userspace draft.
Please do not be too hasty with speedy deletions for "non-egregious" (other than attack pages, copyvios, vandalism, or complete nonsense), especially those lackingcontext (CSD A1) orcontent (CSD A3). Writers unfamiliar with Wikipedia guidelines should be accorded at least an hour to fix the article before it is nominated for speedy deletion. If you see a page that has been tagged too hastily, please notify the tagger about their hasty deletion with {{subst:uw-hasty}}. The template{{hasty|placed above existing speedy tag to inform admins to of hasty tagging and to wait}} can also be added to the tagged article to flag that it was hastily tagged.
If you tag an article written by a newcomer, consider leaving a friendly note on their talk page, pointing them toHelp:Maintenance template removal (WP:MTR), which is dedicated to explaining the process of addressing and removing maintenance tags and including that anyone can remove them (except for AFD and CSD tags) after the problems have been addressed (or if they were truly added in error). Most new editors don't know that they are permitted to do this.
Excellent communication is an important part of the new page patrol process. Reviewers should make use of Page Curation to post short messages to the creator, provide informative edit summaries, and otherwise appropriately engage with other editors. Reviewers are encouraged to makefrequent use of the existingmessage to creator tool. It is essential that good faith new creators be encouraged to continue creating articles and editing Wikipedia.
Reviewers are not obligated to mentor new users or complete their articles, but may wish to direct new users to theTeahouse question forum,help desk andArticles for Creation for assistance.Wikipedia:Your first article,Wikipedia:Contributing to Wikipedia, theWikipedia:Tutorial,The Wikipedia Adventure, and other help pages are also available. When drafts are approved at AfC and moved to the mainspace they will be checked again by new page patrollers in many instances.
As a new page patroller, any action you take other than marking an article as reviewed is not likely to be welcomed by the page creator. In the best case scenario, they will simply listen to your feedback and address the issue promptly. However, disputes are common. Whether it is about a cleanup tag, a deletion nomination, a move to draft, or something else, try to approach these disputes with humility and empathy. Avoid the temptation to 'pull rank' over a user who probablyknows a lot less about our processes than you do. Even if you are completely correct in your judgement of an article, it is not surprising that the creator could react badly if you tell them that there is something wrong with their contribution, or threaten to remove it. New editors might be unfamiliar with our practice ofnot asking permission to fix problems – and its obverse, not being offended when someone points out a problem with your work. Experienced editors might be reluctant to acknowledge that they aren't immune to making mistakes. All reviewing disputes are more likely to be resolved amicably if you try to understand the other party's point of view before putting forth your own.
It is especially important to remember that thenew page reviewer right gives you thetechnical ability to mark pages "reviewed"; it does not give you any special decision-making powers over new articles. Like all advanced rights holders, from page movers to bureaucrats, the way you use your tools is subject to theconsensus of other editors. For example, if you move a page to draftspace and the creator of the article objects to this, there isno consensus on where the page should be. Therecommended course of action here is to return the page to the state it was in before the dispute began (i.e., in mainspace), and then attempt to solve it through discussion, for example, by opening anAfD.[5] You should not simply insist that the page remains in your preferred namespace because you are a new page patroller and the other editor is not.
Page Curation also includes a feature to 'unreview' a new article. Nobody is absolutely perfect and errors can happen. If you come across an article that appears to have been wrongly or inappropriately tagged, consider clicking the checkmark icon in the Page Curation toolbar ("Mark this page as unreviewed") and leave a friendly note for the patroller.
If you notice a patroller making frequent errors, tagging too quickly, or tag-bombing, offer friendly support or direct them to a specific section of this or another help page. In extreme cases you may need to inform an administrator, an NPP coordinator, or post atWP:ANI, butalways try to help your colleague first.
If a redirect or blanked page is converted to an article, it will be marked as unreviewed and placed in the new pages feed. This is to avoid people creating redirects for inappropriate pages and later converting them into articles to avoid review. If you see an old page (such as one from 2005 or 2016), it is likely that it was recently converted from a redirect. In these cases, you should check the page history, and if the page is not appropriate as an article, restore the redirect and notify the person who created the article. If you are reverted and you still believe the article is inappropriate, you should list it atArticles for Deletion. Redirects that are currently listed atRedirects for Discussion should simply be marked as reviewed.
[Mark this page as patrolled], which appears in the bottom right corner of some pages, makes an entry in the patrol log only. Clicking the green check mark in your toolbar always creates an entry in the page curation log, and often creates an entry in the patrol log, but not always due tosome bugs. Most people use the "mark as reviewed" button, so most people should be checking the page curation log exclusively. You canapply the "Reviewing" log filter if needed, which will filter out non-reviewing from the page curation log. The patrol log should usually be ignored.[Mark this page as patrolled] appears when the Page Curation toolbar is closed (see next bullet), and in namespaces where PageTriage doesn't operate (for example, draftspace, template space, and talk pages). We do not need to patrol non-mainspace pages methodically and should focus on mainspace.Editors with theadministrator user right can review new articles without any additional permissions. There are also a number of support tasks where admin assistance is especially needed:
Variousproject coordination tasks also benefit from the input of experienced editors.
Editors regularly monitoredSpecial:NewPages from the earliest days of the project, before there was an organised new pages patrol.Uncle G's guide to article triage illustrates the workflow used for thesead hoc patrols. Two major constraints in these early days were that new pages only remained in the log for thirty days[11] and that there was no function to mark a page as reviewed. It was thus difficult for people looking at the log to know if a page had already been patrolled by someone else. Thefirst attempt to organise a new pages patrol (2004) tried to address this by working in shifts, so that someone would always be checking new pages as they were created, but it didn't work. New pages patrol was subsequently folded intorecent changes patrol for the next couple of years.
The new pages patrol project as we know it wassplit off from recent changes patrol in December 2006. The ability to mark new pages as reviewed wasadded to MediaWiki in November 2007. Originally restricted to admins, it was made available to all autoconfirmed users shortly thereafter.[12][13] This brought with it a problem that has remained present ever since: the backlog. The thirty-day limit on pages appearing in theSpecial:NewPages remained, and articles would regularly move off it without being marked as reviewed.[14] By 2010–2011, there was a sense that new page patrollers could not cope with the workload, even though the actual number of pages needing to be manually patrolled had been decreasing steadily since 2007.[15] A bot was created totag these articles as "unpatrolled",[16] but a more permanent solution was needed.
Motivated in large part by the pressure on new pages patrol,a major RfC in 2011 proposed that page creation should be restricted toautoconfirmed users.[17] It had previously been restricted to registered users in 2005, in an "experiment" initiated by Jimmy Wales following theSeigenthaler incident.[18] The RfC found a strong consensus for extending this requirement to autoconfirmed, but as a concession to those who were worried that this was too big of a compromise of the principle that anyone can edit, it was agreed it would first be put in place for a six-month trial (WP:ACTRIAL). However, controversially, MediaWiki developers refused to implement the change because it would "significantly and negatively impact the Foundation's goals of editor engagement",[19] leaving ACTRIAL in limbo for thenext six years.
In the aftermath of the ACTRIAL controversy, the WMF initiated a project to improve the workflow of new page patrollers. A survey of patrollers was conducted, which amongst other things indicated a desire for better tools for navigating and patrolling new articles.[20][21] The result of this project was a new Mediawiki extension,PageTriage (originally called 'Zoom'), which was enabled on the English Wikipedia in 2012. It addedSpecial:NewPagesFeed (intended to replaceSpecial:NewPages) and thePage Curation tools.[22] Further work in 2018 addedAfC drafts,ORES predictions and automated copyright violation checking to the feed.[23] The new tools introduced in 2012 brought with them a small but consequential change: they removed the thirty-day limit on pages appearing in the new pages feed.[24] From this point on, all articles had to be explicitly reviewed.
The user right, New Page Reviewer, was introduced in 2016 to ensure quality of reviewing. The system is the front line of interaction between new authors and the community's volunteers who maintain the quality of Wikipedia's articles.[25]