494:) and misspellings that are simply typos. It is important to have redirects from the first category (provided that the misspelling is reasonable), because someone may plausibly try to search for the target using that incorrect spelling. The second category is much less useful, as someone who has made a typo should be able to recognize their mistake when taken to the page for internal search results. However, due to the amount of overhead associated with opening an RfD discussion, it is often acceptable to approve redirects from typos, even if they provide little utility to Knowledge. It is important, however, to delete redirects from typos that could plausibly refer to more than one target article (e.g.
180:
overall utility of the redirect to readers of
Knowledge. As many redirects are simply pointing from an alternative spelling or phrasing of the target article's title, it's actually possible to review many redirects without even clicking through to the target page. Some bots have been deployed to automatically patrol the most predictable and uncontroversial kinds of redirects, such as redirects whose only differences are interchangeable characters such as hyphens ("-"), em-dashes ("โ"), and spaces (" "). Additionally, a large proportion of the overall volume of redirects are created by a small group of editors diligently linking together certain patterns of redirects and articles. While
291:, non-notable songs should be redirected to the albums they appear on, and non-notable albums should be redirected to their recording artists. If a song was not released on an album, or if its corresponding album is not notable, then it should also be redirected to the recording artist. These redirects are almost always approvable, and the risk of vandalism associated with them is low. Note, however, that if an artist has a discography page, it may be more appropriate to redirect songs/albums to there, instead of the artist page. Particularly prolific artists may not mention every single or EP that they've ever released on their main page. You may want to tag the redirects using
160:
inappropriate nonetheless and should be taken to RfD. Cross namespace redirects to these spaces should serve a clear and obvious purpose to justify the possibility of surprising an editor by whisking them away from an actual
Knowledge article. By contrast, redirects from main to Category space are often directly helpful to encyclopedia readers and do not need to be treated so stringently.
34:
171:
approved out of the new pages queue even if they provide little benefit to the encyclopedia. Examples of this class of redirect include redirects from unlikely alternate capitalizations for unique titles, redirects from unnecessary or unlikely disambiguators, and redirects from quotes or minutiae in a fictional setting that are not discussed at length at the target article.
212:; RfD discussions for outcomes other than deletion should only be raised if multiple different related redirects are being discussed at once, to settle disputes in progress, to suggest disambiguation when you feel that you have insufficient knowledge to put together an effective disambiguation page, or for complicated cases where multiple outcomes seem reasonable.
594:
section-targeting redirects should be double-checked to confirm that this is an actual section title that belongs at the target article (redirects may be targeted to sections that do not exist or that have since been removed, in which case the redirect will dump readers at the top of the article as if no extension was provided).
474:), but extra care should be taken to make sure that they are appropriate for such redirects. Additionally, nicknames that are particularly associated with a particular context may have better targets than the literal referent of the nickname (for example, for nicknames coined and primarily used by Donald Trump,
419:
Redirects from alternative names of a subject are acceptable provided that the alternative name is not more likely to refer to something else. Relevance can often be quickly confirmed by looking at bold terms in the target lead or conducting a ctrl-F search. Potential alternative targets can be found
389:
Redirects from unnecessary disambiguations are generally acceptable, providing that the disambiguation is somehow accurate. If the disambiguation is inaccurate or indecipherable, nominating for deletion at RfD may be appropriate. If the disambiguation contains an obvious typographical error (such as
165:
Because redirects are cheap to create and don't have any content, and because redirect deletion discussions at RfD take up a non-trivial amount of editors' time and energy to participate in, it is less important that a redirect be actively useful, and more important that the redirect simply does not
89:
on
Knowledge is significantly different from patrolling articles. While article reviews focus on establishing the subject's notability and removing any unacceptable content, redirects do not have notability, and do not have any content beyond the redirect itself. Thus, when evaluating redirects, you
138:
If this criterion is not obviously satisfied from reading the target article's text, a reviewer should conduct an internet and Google
Scholar search, as well as looking through articles on other language Knowledge projects that are linked to the target. If no evidence can be found that the redirect
440:
Redirects from longer titles are almost always appropriate, provided that the longer title is accurate, since generally a longer title reduces ambiguity, rather than increasing it. Redirects from longer titles that obviously follow from the target's title do not require checking the target article
319:
Redirects from acronyms and initialisms are appropriate if there is no other subject on
Knowledge that the redirect could refer to. However, if the abbreviation is not widely used (as evidenced by an internet search), it may still be appropriate to nominate the redirect for deletion, especially if
593:
If a redirect has the same title as a section that it is targeted to, and this title is non-generic and unlikely to appear in other articles, it is permissible to approve the redirect without even clicking through to the target article. However, particularly unconventional or otherwise suspicious
420:
by using
Knowledge's internal search function. However, it is not strictly necessary for the alternative name to be directly attested in the target: if the redirect title is a name that could be plausibly used by an English speaker to refer to the target, then it is acceptable as a redirect (e.g.
208:. Unlike in AfD discussions, deletion is not implied in an RfD nomination, and editors nominating a redirect for RfD should explicitly say what their intended outcome for the redirect is. That having been said, retargeting a redirect or converting it to a disambiguation page can generally be done
179:
While article reviews focus on establishing the subject's notability and removing any unacceptable content, redirects are not subject to notability guidelines, and do not have any content beyond the redirect itself. Thus, when evaluating redirects, a new pages patroller is primarily assessing the
258:
These categories are only intended to contain redirects, and are helpful in keeping track of redirects and further subcategorizing them as needed. They include both redirects within main namespace and in other namespaces. They are often applied using templates, though such categories can also be
380:
Note that many non-Latin alphabets can have letters that map onto Latin letters in ways that may be confusing for
English speakers without proficiency in the relevant language. For example, the Cyrillic character "ะต", depending on context, can be transliterated as "e", "ye", or "yo" for English
376:
If the language of a redirect has any special significance or association with the target, then the redirect is acceptable, otherwise the redirect should be nominated for deletion at RfD. This applies to redirects that are either fully in another language or that are transliterated or otherwise
170:
has a good list of criteria for why to create a redirect and why to delete one, a fair amount of redirects live in a gray area between these categories. We should not encourage editors to create such redirects, but it is also not worth the effort to actually delete them, and they can be safely
255:(rcats), then these should be used. For clarity, all category links should be added at the end of the page on their own lines, after the redirect target link and rcat(s). Use of a blank line between the redirect target link and all rcats and category links promotes readability of the code.
159:
By far the most common R2-qualifying redirects are redirects pointing to Draft space, usually as the result of a move. Note, however, that while redirects pointing from mainspace to
Template, Knowledge, Help and Portal spaces are not immediately eligible for speedy deletion, they are often
457:
Nicknames can be valid redirects to a target. However, when evaluating nickname redirects, take care to make sure that the redirect is actually in wide use and that it unambiguously refers to the target. Pejorative nicknames are permissible as long as they meet the prior criteria (e.g.
361:
These are acceptable, provided that there are no other subjects by that name on
Knowledge. It is generally the case that if there is a fictional character with the same name as a notable real person, the real person is going to be the primary topic, but this is not a hard and fast rule.
320:
the abbreviation could also refer to a subject which is likely notable despite not having an article on
Knowledge at the moment. Redirects from abbreviations in languages other than English are subject to the same conditions as all other redirects from languages other than English.
567:
Redirects that begin with determiners (such as "the", "a", etc.) that point to the same title without determiners are generally acceptable (although in cases where particular subject is known as the canonical example of its type, targeting to another article is acceptable such as
97:
to readers, and the redirect is not clearly in violation of Knowledge's policies against promotional or attack content, then a redirect should be approved out of the page queue. Otherwise, a redirect can be pointed to a new target, nominated for speedy deletion, nominated for an
381:
pronunciation. Prolific redirect patrollers should seriously consider studying foreign alphabets to a level of basic proficiency to aid in their work (particularly the Cyrillic alphabet, which as of this writing is one of the most common non-Latin scripts for redirect titles).
127:
Redirects that do not meet this criterion should either be retargeted to a more appropriate target, converted to a disambiguation, or nominated for a deletion discussion at RfD. In some cases, it may be appropriate to leave the redirect as is, but add a
584:
pointing to the same title without a determiner, take care to make sure that the same title without a determiner is not a redirect pointing to a different subject. Whenever possible, redirects with equivalent titles should point to the same target.
184:
permissions include redirects, many of these editors would not necessarily qualify for autopatrol, as they may not have the necessary history of article creation to justify the permission. As such, we have created an
314:
149:(Note, however, that non-neutral redirects are allowed provided that the non-neutral search term is plausible). Redirects failing this criterion should be nominated for speedy deletion.
226:
There are a series of categories that are used only for redirects. Redirects are placed in categories by templates. These categories explain why the redirect exists, for example
486:
Redirects from misspellings come in two categories: misspellings that occur due to a reader's genuine misunderstanding of the spelling of the target article's name (e.g.
365:
467:
384:
186:
522:
530:
391:
603:
356:
139:
is pertinent, it should be nominated for an RfD discussion (or in the cases of gibberish or implausible misspellings, nominated for speedy deletion).
526:
414:
174:
270:
user script adds a check button interface for adding redirect categories to redirect pages and an input field to change the redirect target.
215:
536:
541:
It is generally permissible to approve redirects without checking the target if the redirect is an obvious subtopic of the target, e.g.
405:
251:
562:
49:
It contains the advice or opinions of one or more Knowledge contributors. This page is not an encyclopedia article, nor is it one of
435:
495:
481:
475:
588:
452:
93:
If a redirect is pointing to a relevant target, and there are no other possible targets for the redirect that could cause
273:
421:
390:
a missing parenthesis or an unconventional use of punctuation) or is totally inconceivable as a search term (such as
50:
240:
221:
192:
429:
278:
54:
529:), or almost any misspelling that includes multiple incorrect characters without phonetic similarity (e.g.
347:
573:
249:
A redirect may be categorized in the same way as for any other page; however, when it is possible to use
337:
17:
125:
There is no article that contains more information about the redirect's title than the current target.
619:
259:
created and populated directly. This categorization is intended for Knowledge editors, not readers.
553:
542:
327:
459:
442:
136:
The redirect title is a plausible search term for the target, or for a subtopic of the target.
323:
Titles where the initials form a pronounceable word (for example NATO) should be tagged with
305:
230:
606:, a pseudo-user group for editors who create lots of uncontroversially approvable redirects
343:. If the title is an abbreviation, but not an acronym or initialism, tag the redirect with
295:
181:
72:
8:
267:
546:
262:
Automated tools are available to make redirect categorization easier while patrolling.
94:
64:
517:
Particularly unlikely misspellings can be deleted using the speedy deletion criterion
263:
120:
A redirect can be approved without further action if the following criteria are met:
333:. If the initials are not a word (for example NFL) the redirect should be tagged as
57:. Some essays represent widespread norms; others only represent minority viewpoints.
425:
288:
144:
115:
42:
132:
to the target informing readers about other articles that they may be looking for.
569:
471:
371:
284:
111:
487:
209:
189:, which allows a bot to automatically approve all of their redirect creations.
613:
446:
129:
99:
266:'s tag module will show redirect templates when viewing redirect pages. The
105:
90:
should assess the overall utility of the redirect to readers of Knowledge.
518:
511:
395:
154:
577:
167:
86:
580:). When coming across a redirect that begins with a determiner that is
491:
521:. Examples of such misspellings include extraneous punctuation (e.g.
246:
means that the redirect is an alternative name for the main title.
102:
discussion, or converted to a disambiguation page as appropriate.
463:
507:
499:
187:
autopatrol list for prolific and productive redirect creators
153:
The article is not a cross-space redirect that qualifies for
525:), a cross-keyboard typo with no phonetic explanation (e.g.
514:) or that could otherwise lead to confusing search results.
315:
Redirects from acronyms, initialisms and other abbreviations
503:
597:
604:
Knowledge:New pages patrol/Redirect autopatrol list
175:
Differences between the redirect and article queues
432:may be an appropriate tag to add to the redirect.
377:approximated into Latin letters used in English.
611:
283:Per the subject-specific notability guidelines
411:may be useful for categorizing the redirect.
143:The redirect is not blatantly promotional or
478:is likely to be a more appropriate target).
366:Redirects from languages other than English
385:Redirects from unnecessary disambiguations
166:impede or confuse readers. Thus, while
14:
612:
476:List of nicknames used by Donald Trump
274:Common types of redirects and outcomes
398:speedy deletion may be appropriate.
28:
357:Redirects from fictional characters
236:means it was created by a merge or
23:
498:, which could be a misspelling of
55:thoroughly vetted by the community
51:Knowledge's policies or guidelines
24:
631:
422:French and Low Countries campaign
406:R from unnecessary disambiguation
537:Redirects from obvious subtopics
415:Redirects from alternative names
222:Knowledge:Categorizing redirects
32:
430:Template:R from incorrect title
197:Note that while AfD stands for
13:
1:
510:...; these are instances of
436:Redirects from longer titles
7:
574:Crucifixion of Jesus Christ
482:Redirects from misspellings
252:redirect category templates
10:
636:
563:Redirects with determiners
369:
219:
109:
62:
26:Essay on editing Knowledge
18:Knowledge:New pages patrol
543:2011 Challenge Cup Final
453:Redirects from nicknames
468:Benefactor of Dictators
241:R from alternative name
216:Redirect categorization
460:The Butcher of Beijing
443:United States Route 66
589:Redirects to sections
220:Further information:
199:articles for deletion
95:surprise or confusion
53:, as it has not been
523:Mission:: Impossible
531:Worldd Trsde Center
348:R from abbreviation
547:2011 Challenge Cup
401:Templates such as
394:), nominating for
392:Foo (second draft)
155:R2 speedy deletion
428:). In some cases
338:R from initialism
201:, RfD stands for
106:Redirect criteria
83:
82:
627:
620:Knowledge essays
558:
552:
426:Battle of France
410:
404:
352:
346:
342:
336:
332:
326:
311:as appropriate.
310:
304:
300:
294:
245:
239:
235:
229:
75:
36:
35:
29:
635:
634:
630:
629:
628:
626:
625:
624:
610:
609:
600:
591:
570:The Crucifixion
565:
556:
554:R from subtopic
550:
539:
484:
472:Henry Kissinger
470:redirecting to
462:redirecting to
455:
438:
417:
408:
402:
387:
374:
368:
359:
350:
344:
340:
334:
330:
324:
317:
308:
302:
298:
292:
281:
279:Music redirects
276:
243:
237:
233:
227:
224:
218:
195:
177:
118:
108:
85:Patrolling new
79:
78:
71:
67:
59:
58:
33:
27:
22:
21:
20:
12:
11:
5:
633:
623:
622:
608:
607:
599:
596:
590:
587:
564:
561:
538:
535:
488:Abraham Lincon
483:
480:
454:
451:
437:
434:
416:
413:
386:
383:
367:
364:
358:
355:
328:R from acronym
316:
313:
280:
277:
275:
272:
217:
214:
203:redirects for
194:
191:
176:
173:
164:
162:
161:
150:
140:
133:
107:
104:
81:
80:
77:
76:
68:
63:
60:
48:
47:
39:
37:
25:
15:
9:
6:
4:
3:
2:
632:
621:
618:
617:
615:
605:
602:
601:
595:
586:
583:
579:
575:
571:
560:
555:
548:
544:
534:
532:
528:
527:United Statzs
524:
520:
515:
513:
509:
505:
501:
497:
493:
489:
479:
477:
473:
469:
465:
461:
450:
448:
447:U.S. Route 66
444:
433:
431:
427:
423:
412:
407:
399:
397:
393:
382:
378:
373:
363:
354:
349:
339:
329:
321:
312:
307:
297:
290:
286:
271:
269:
265:
260:
256:
254:
253:
247:
242:
232:
223:
213:
211:
207:
206:
200:
190:
188:
183:
172:
169:
158:
156:
151:
148:
146:
141:
137:
134:
131:
126:
123:
122:
121:
117:
113:
103:
101:
96:
91:
88:
74:
70:
69:
66:
61:
56:
52:
46:
44:
38:
31:
30:
19:
592:
581:
572:pointing to
566:
540:
516:
485:
456:
439:
418:
400:
388:
379:
375:
360:
322:
318:
306:R from album
282:
261:
257:
250:
248:
231:R from merge
225:
204:
202:
198:
196:
178:
163:
152:
142:
135:
124:
119:
92:
84:
40:
578:Crucifixion
576:instead of
370:Main page:
296:R from song
41:This is an
492:Bourgoisie
466:, but not
205:discussion
193:RfD vs AfD
182:autopatrol
147:in nature.
110:See also:
73:WP:RPATROL
289:WP:NALBUM
268:Capricorn
145:WP:ATTACK
116:WP:COSTLY
87:redirects
614:Category
598:See also
372:WP:RLOTE
285:WP:NSONG
112:WP:CHEAP
65:Shortcut
464:Li Peng
264:Twinkle
130:hatnote
549:. Use
441:(e.g.
210:boldly
512:WP:XY
508:Spoon
500:Spain
496:Spoin
396:WP:R3
43:essay
16:<
504:Spin
287:and
168:WP:R
114:and
582:not
533:).
490:or
449:).
445:to
424:to
301:or
100:RfD
616::
559:.
557:}}
551:{{
519:R3
506:,
502:,
409:}}
403:{{
353:.
351:}}
345:{{
341:}}
335:{{
331:}}
325:{{
309:}}
303:{{
299:}}
293:{{
244:}}
238:{{
234:}}
228:{{
545:โ
157:.
45:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.