Below is a list of basic checks that new page patrollers should perform on each page patrol involving redirects.
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 the redirect autopatrol list. They need around 100 redirects to qualify. Use xtools (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
Below is a list of basic checks that new page patrollers should perform on each page patrol involving redirects.
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 the redirect autopatrol list. They need around 100 redirects to qualify. Use xtools (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