For general info and coordination guidelines for all Wikimedia projects, on creating redirects see Help:Redirect.

跳轉係一版,本身無內容,但係會彈去另一篇文度,或者文中一段,或者另一版。可以睇成文嘅另一標題。好似打UK,或者撳UK,就會跳去英國,上面會話,由UK跳轉過來。識得咁彈,皆因UK之中,內含#REDIRECT [[United Kingdom]]。呢句就就由明由邊度彈去邊度。要彈去版中一,可以咁寫#REDIRECT [[版名#節題]]

呢一版有跳轉指南,介紹維基百科裏,點用跳轉先至啱。至於,技術上嘅嘢,可以睇Help:Redirect。其他相關有Wikipedia:Double redirects, Wikipedia:Hatnote#Redirect and WikiProject Redirect



  • 別名。
  • 單數、眾數。
  • 意思相關嘅字。
  • 名詞嘅形容方式。
  • 無咁專嘅名,跳去專啲嘅名。
  • 專啲嘅名,跳去無咁專嘅名。
  • 減筆。
  • 另一種寫法。
  • 標點問題。題中嘅標點有唔同寫法。好似減號同破折號。
  • 寫成純拉丁母,因爲標音唔易打。
  • 好可能寫錯嘅字。
  • 拉丁字母大細楷。唔關搵嘢事,不過方便出其他文同出面網站引用維基百科。
  • 大題目中嘅細題相。通常會係某文一節。
  • 有啲搞清楚版,無搞清楚喺題上面。
  • 維基副文嘅減筆。

點樣整跳轉 (redirect跳轉指令)[編輯]


#REDIRECT [[乙版個名]]


#REDIRECT [[香港中文大學]]

你亦都可彈去一篇文某一(section)。睇Meta:Help:Redirect#A redirect to an anchor:

#REDIRECT [[香港中文大學#史]]










要個寫埋理由可以響#REDIRECT [[邊度都好]]後面隔個空格加。例如,整中文大學

#REDIRECT [[香港]] {{彈自縮寫}} 







理由 用法,有乜出 標籤 /
簡寫 Template:彈自簡寫 {{彈自簡寫}}





錯字 Template:彈自錯字 {{彈自錯字}}


遞二尐寫法,或者加標點 Template:彈自遞二尐寫法 {{遞二尐寫法}}


Other capitalisations, to ensure that "Go" to a mixed-capitalisation article title is case-insensitive
  • 以其它大寫形式:呢個係個由一個標題用另外一個方式去大寫嘅。佢係,指向為咗符合維基百科大寫命名約定,或者佢係要指去以另外方式大寫嘅標題。呢個可能幫助寫、搵同埋國際語言嘅問題嘅跳轉。
    • 如果呢個跳轉係唔正確嘅大寫,噉{{R from miscapitalisation}}就應該要用,同埋嗰啲版用呢拎嗰陣應該要更新將個拎直接連去目標版度。唔正確嘅大寫係可以加註喺任何空間名度。
    • 用呢個 rcat 只係加註喺主空間嘅跳轉度;當用喺其它空間名度,噉就要改用{{R from modification}}。

Adding a redirect for mixed-capitalisation article titles (e.g., Isle of Wight) allows going to these articles to be case-insensitive. For example, without the redirect Isle of wight going to "Isle Of wight" or any capitalisation other than exactly 'Isle of Wight' would not find the article Isle of Wight.

Why: Articles whose titles contain mixed-capitalisation words (not all initial caps, or not all lower case except the first word) are found only via an exact case match. (Articles, including redirects, whose titles are either all initial caps or only first word capitalised are found via "Go" using a case-insensitive match.)

Note: Related redirects are needed only if the article title has two or more words and words following the first have different capitalisations. They are not needed, for example, for proper names which are all initial caps.


  • Natural Selection redirects to Natural selection
  • Redirect Vice chancellor of austria to Vice Chancellor of Austria is needed because the Go search is case-sensitive for mixed-caps titles. Adding this redirect allows the article to be found when a user enters "vice chancellor of austria" or "vice chancellor of Austria" as a Go search.
  • No redirect to Francis Ford Coppola is needed because the "Go" command is case-insensitive for an article whose title is all initial caps. Any capitalisation (e.g. "francis fOrD CoPPola") entered as a "Go" will find the article.
{{R from other capitalisation}}

Category:Redirects from other capitalisations

遞二尐名,假名,花名,同義辭 Template:彈自遞二尐名 {{彈自遞二尐名}}


學名 Template:彈自學名 {{彈自學名}}


遞二尐文 Template:彈自遞二尐文 {{彈自遞二尐文}}


Accents Template:R from ASCII {{R from ASCII}}

Category:Redirects from titles with ASCII

Plurals Template:R from plural

Note that [[greenhouse gas]]es shows up as greenhouse gases, so it is not usually necessary to redirect plurals. However third-party websites started adding automatic links to Wikipedia from their topics (see, e.g., [1]). Many of them follow the opposite naming convention, i.e., topics are named in plural, and the link to Wikipedia may land into an empty page, if there is no redirect.

{{R from plural}}

Category:Redirects from plurals

相關字 Template:彈自相關字 {{彈自相關字}}


好密切嘅主題,可以同一篇講 Template:R with possibilities {{R with possibilities}}

Category:Redirects with possibilities

用來搞清楚 Template:彈去搞清楚 {{彈去搞清楚}}


方便搵日子 Template:彈來搵日子 {{彈來搵日子}}


彈去年代 Template:彈去年代 {{彈去年代}}




{{R from shortcut}}

Category:Redirects from shortcut

Oldstyle CamelCase links Template:R from CamelCase {{R from CamelCase}}

Category:Redirects with old history

links autogenerated from EXIF information Template:R from EXIF {{R from EXIF}}

Category:Redirects from EXIF information

From school microstub to merge location Template:R from school {{R from school}}

Category: Redirects from school articles

  • Avoiding broken links (see below)
  • Minor but notable topics

Sub-topic or supra-topic redirects (redirect with possibilities) are often temporary, eventually being replaced by fully fledged articles on the sub-topic in question. Be conservative when creating sub-topic redirects — they can sometimes be counter-productive, because they disguise the absence of a proper article from editors. Sub-topic redirects should only be used where the main article has a section or item on the sub-topic. For example, denial of service has a section on distributed denial of service. Sub-topics should be boldfaced on their first appearance in the section, to indicate that they are in fact alternate titles or sub-titles.

In accordance with wikipedia:naming conventions (precision) it's best to have an article at a well-defined, unambiguous term, with redirects from looser colloquial terms, rather than vice versa.

Some editors prefer to avoid redirects and link directly to the target article, as it is reported[未記出處或冇根據] that redirects lower search engine rankings.

See also: Wikipedia:Template messages/Redirect pages which contains a somewhat longer list of available redirect templates

Renamings and merges[編輯]

We try to avoid broken links because they annoy visitors. Therefore, if we change the layout of some section of Wikipedia, or we merge two duplicate articles, we always leave redirects in the old location to point to the new location. Search engines and visitors will probably have linked to that page at that url. If the page is deleted, potential new visitors from search engines will be greeted with an edit window. The same is true for anyone who previously bookmarked that page, and so on.

On a small scale, this applies to cases where we had duplicate articles on some subject, or lots of twisty little stubs on different aspects of the same overall subject. On a larger scale, we've had a few fairly major reorganisations:

When should we delete a redirect?[編輯]

To delete a redirect without replacing it with a new article, list it on redirects for discussion. See deletion policy for details on how to nominate pages for deletion.

Listing isn't necessary if you just want to replace a redirect with an article, or change where it points: see How do I change a redirect? for instructions on how to do this. If you want to swap a redirect and an article, but are not able to move the article to the location of the redirect please use Wikipedia:Requested moves to request help from an admin in doing that.


What needs to be done on pages that are targets of redirects?[編輯]

We follow the "principle of least astonishment" — after following a redirect, the reader's first question is likely to be: "hang on ... I wanted to read about this. Why has the link taken me to that?". Make it clear to the reader that they have arrived in the right place.

Normally, we try to make sure that all "inbound redirects" are mentioned in the first couple of paragraphs of the article. For example:

  • James Tiptree, Jr. (August 24, 1915 – May 19, 1987) was the pen name of American science fiction author Alice Bradley Sheldon ...
  • Water (H2O, HOH) is the most abundant molecule ...

If there is an ambiguity associated with a redirect, one of the redirect disambiguation templates may be useful.

Don't cause a secondary redirect. They don't work like a primary redirect; same with tertiary redirects.

Self-links, duplicate links[編輯]

Avoid self-links, including self-links through redirects ("loop links"). Also, avoid having two links that go to the same place. These can confuse readers, and cause them to unnecessarily load the same page twice.

Don't fix links to redirects that aren't broken[編輯]

Some editors are tempted, upon finding links using a legitimate redirect target, to edit the page to "fix" the link so that it points "straight" at the "correct" page. Unless the link displays incorrectly — for instance, if the link is to a misspelling, or other unprintworthy redirects, or if the hint that appears when you hover over the link is misleading — there is no need to edit the link. The link may be deliberate, may consolidate related information in one place, or may indicate possible future articles.

In particular, there should never be a need to replace [[redirect]] with [[target|redirect]]. That is, there should be no need to replace a redirect with a piped link to the target if the description is exactly the same as the redirect title.

Some editors have the mistaken impression that fixing redirected links improves the capacity of the Wikipedia servers. Because editing a page uses much more resources than following a redirect, the opposite is true. It is inadvisable to worry about performance anyway.

One exception where it is preferable to fix redirected links is in series templates, such as those found at the bottom of many articles (e.g. {{USPresidents}} on George W. Bush). In this case, when the template is placed on an article, and contains a direct link to that article (not a redirect), the direct link will display in bold (and not as a link), making it easier to navigate through a series of articles using the template.

Template redirects[編輯]

A template T2 can be redirected to another template T1. This creates an alias (T2 is an alias for T1). The alias name T2 can be used instead of the "real" template T1.

Aliases for templates can cause confusion and make migrations of template calls more complicated. For example, assume calls to T1 are to be changed ("migrated") to some new template TN1. To catch all calls, articles must be searched for {{T1}} and all aliases of T1 (T2 in this case).

See also[編輯]