Help:Interwiki linking

By adding a prefix to another project, internal link style ("prefixed internal link style") can be used to link to a page of another project. For example,  links to the InterWiki article on the English Wikipedia. This is called interwiki. For each project, an interwiki map (a list of target projects with their prefixes) is specified (example). These target projects need not use MediaWiki and need not even be a wiki.

New PP: check Special:ParserDiffTest/Help:Interwiki linking.

Interwiki linking from and within Wikimedia
Within Wikimedia, for the purpose of (see below) the project families are Wikipedia, Wiktionary, Wikiquote, Wikibooks and Wikisource. Thus this applies for a link like en:, de:, etc., from a Wikipedia to another one, from a Wiktionary to another one, from a Wikiquote to another one, from a Wikibooks to another one or from a Wikisource to another one.

The interlanguage link feature works on Commons, and produces links to the Wikipedias. This is not reciprocal: a link from a Wikipedia to Commons is an in-page link.

Project titles and shortcuts
{| class="wikitable sortable" ! Project !! Long form !! Shortcut Some prefixes work only with a page, e.g. (fails) vs. Interwikimedia link (works). These prefixes are case insensitive.
 * Wikipedia
 * Wiktionary
 * Wikinews
 * Wikibooks
 * Wikiquote
 * Wikisource
 * Wikispecies
 * Wikiversity
 * Wikimedia Foundation
 * Wikimedia Incubator
 * MediaZilla
 * for the English Wikipedia working from any Wiki supporting the Meta Interwiki map, not only from MediaWiki Wikis.
 * Wikibooks
 * Wikiquote
 * Wikisource
 * Wikispecies
 * Wikiversity
 * Wikimedia Foundation
 * Wikimedia Incubator
 * MediaZilla
 * for the English Wikipedia working from any Wiki supporting the Meta Interwiki map, not only from MediaWiki Wikis.
 * Wikisource
 * Wikispecies
 * Wikiversity
 * Wikimedia Foundation
 * Wikimedia Incubator
 * MediaZilla
 * for the English Wikipedia working from any Wiki supporting the Meta Interwiki map, not only from MediaWiki Wikis.
 * Wikiversity
 * Wikimedia Foundation
 * Wikimedia Incubator
 * MediaZilla
 * for the English Wikipedia working from any Wiki supporting the Meta Interwiki map, not only from MediaWiki Wikis.
 * Wikimedia Incubator
 * MediaZilla
 * for the English Wikipedia working from any Wiki supporting the Meta Interwiki map, not only from MediaWiki Wikis.
 * Wikimedia Incubator
 * MediaZilla
 * for the English Wikipedia working from any Wiki supporting the Meta Interwiki map, not only from MediaWiki Wikis.
 * MediaZilla
 * for the English Wikipedia working from any Wiki supporting the Meta Interwiki map, not only from MediaWiki Wikis.
 * MediaZilla
 * for the English Wikipedia working from any Wiki supporting the Meta Interwiki map, not only from MediaWiki Wikis.
 * MediaZilla
 * for the English Wikipedia working from any Wiki supporting the Meta Interwiki map, not only from MediaWiki Wikis.
 * for the English Wikipedia working from any Wiki supporting the Meta Interwiki map, not only from MediaWiki Wikis.

One-letter prefixes (as a live check on the table):

Non-Wikimedia interwiki codes have a limitation. They can only be used through a link. For example, the entry for "John" on Wiktionary, a Wikimedia project, can be accessed by  John  or http://meta.wikimedia.org/wiki/wikt:John. However, the latter method does not work for non-Wikimedia wikis. For example, the main page on the Mozilla Wiki can be accessed via  Main Page , but http://meta.wikimedia.org/wiki/MozillaWiki:Main_Page results in an error.

Technical
A project's own namespace prefix cannot be reused as code for an external project. However, the prefix used for a target project may coincide with the prefix for a project namespace within that project. As a result, to link to a page in that namespace, use the same prefix twice, e.g. en:Wikisource:Wikisource:Scriptorium.

For portability across projects, one may want to select a link code that leads to the same target from all projects, e.g. MetaWikipedia:wikibooks:Main Page. The "superfluous" "MetaWikipedia:" prevents "wikibooks:" being interpreted as namespace prefix when the code is used at wikibooks itself, while at Meta the "MetaWikipedia:" is ignored (it is not a namespace prefix, and even at Meta itself it is recognized as code for Meta). The codes above work from all projects. However, the existence detection and the self-link feature do not work on interwiki links.

Prefixes
Interwiki links can use prefixes for the project and/or for the language. Without prefix links are local, for pages in the same project and the same language. If only a language is given they go to a page in the same (or similar) project for the specified language:

fr: fr: os: os:

If only the project is specified they typically go to the language of the source, see above. At most two prefixes are needed for pages in any existing project and any supported language:

Hauptseite Hauptseite Main page &#160; Main page

In the case of more than one prefix a page name has to be specified. For example, while and en: from Meta lead to the English Wikipedia's main page, a bare   does not work:. If the language is different specifying it before the project can also work:

de:q:Hauptseite de:q:Hauptseite en:n:Main page &#160; en:n:Main page Main page &#160; Main page

The second example doesn't work from English Wikipedia  pages, a project prefix before the language is better. More than two prefixes are generally unnecessary. The following examples should work everywhere:

m:Help:Help m:Help:Help Interwiki Interwiki

Two prefixes can have unexpected effects, e.g. from Meta the following links end up on different pages:

About &#160; About en:m:About en:m:About About &#160; &#160; About

In the first case Meta ignores the, because it's local, and then interprets as  prefix for the English Wikipedia. In the second case the leading  goes to the English Wikipedia, where the following   goes straight back to Meta. The second example doesn't work at all from English Wikipedia  pages, only the third example works everywhere.

In other words multiple prefixes are evaluated left to right by the relevant Wikimedia servers (project and language). For projects without different languages like Meta (because Meta is multilingual by itself) language prefixes can be handled as shorthands for  plus the specified language:

pl:2006 &#160; pl:2006 2006 &#160; 2006 pl:w:2006 pl:w:2006

From Meta the first two links both arrive at the Polish 2006 page. The third arrives at the English Wikipedia, because that's how the server selected by  interprets the second prefix .

For a portable link on that server it would be a bad idea to use , but  does the trick. To test that effect from Meta the following links should go to the same page:

ja:2006 &#160;&#160; ja:2006 2006 2006

A universal interwiki link, that is, one that works no matter from which Wikimedia wiki, can be written m: project:language:page name (e.g. m:b:nl:Wiskunde); this routes the parsing of the links via Meta (bug 4285).

Wikia
In Wikia, the prefix is the internal project name for some older wikis. For others, "Wikia:c:" is added in front (e.g. [&#91;Wikia:c:psychology&#93;] or shorter [&#91;w:c:trains:locomotive&#93;]). (The "c" is for "city", a legacy of Wikia's original name Wikicities.)

From Wikimedia projects use [&#91;wikiasite:psychology&#93;] giving psychology, [&#91;wikia:trains:locomotive&#93;] giving wikia:trains:locomotive, or, for the central Wikia, About Wikia.

Interlanguage link
For a multilingual family of similar projects, with one project per language, a system for interlanguage linking can be set up, setting $wgInterwikiMagic to true, and $wgHideInterlanguageLinks to false. If this project is in a family for which this applies, Help:Interlanguage link demo may demonstrate what is explained below (this depends on whether the same language codes are used).

An interwiki link within the family is treated differently (unless it is on a talk page of any namespace): it appears at one or two edges of the webpage (left in Monobook, and top and bottom in Classic). The link label depends only on the sister project that is linked to, not on the linked page. The label is set in the configuration of the project. Typically, it is the name of the language written in that language. The target is only shown in the status bar, depending on the browser (oddly, there is not even a hover box).

Thus, interlanguage link is mainly suitable for linking to the corresponding page in another language. It is not suitable for multiple links of the same other language. See Interlanguage use case for a discussion of common troubles with this system and other possible implementations.

The feature can also be used on an image description page to link to the same or a similar image in a sister project. Other interwiki links to images require the prefixed colon.

Note that, if a page may be used as a template (even if it is not in the template namespace), it should note its interlanguage links between &lt;noinclude&gt; and &lt;/noinclude&gt;. This is the same idea as for categories. Comparison: [&#91;en:link&#93;]</tt> without leading colon adds an interlanguage link to the page. &lt;noinclude&gt;[&#91;en:link&#93;]&lt;/noinclude&gt;</tt> ditto limited to actual page.
 * 1) [&#91;:en:link&#93;]</tt> or [&#91;:category:name&#93;]</tt> are ordinary links.
 * 2) [&#91;m:en:link&#93;]</tt> or [&#91;m:category:name&#93;]</tt> are Interwiki links, see above.
 * 3) [&#91;category:name&#93;]</tt> without leading colon adds a category to the page.
 * 1) &lt;noinclude&gt;[&#91;category:name&#93;]&lt;/noinclude&gt;</tt> limited to actual page.

For projects like Meta a missing leading colon has no effect, Meta doesn't support Interlanguage links. For Wikipedia and similar projects it's a major difference.

The mutual order of interlanguage links is preserved, but otherwise the positions within the wikitext are immaterial, again the same rule as for categories. Usually they are put at the end. With section editing they appear in the preview if they are in the section being edited.

A link to the project itself (hence also a link to the page itself), even if referred to with the project prefix, appears in-page.

Suppose that we have pages de:Zug, en:Train, fr:Train then we need:
 * on de: en:Train, fr:Train
 * on en: de:Zug, fr:Train
 * on fr: de:Zug, en:Train

Thus there is no possibility of simply copying each list, let alone of using a template, as can be done if different languages share one project, with or without separate namespaces, see e.g.:
 * Template:H-langs:Interwiki linking used at the bottom of this page on Meta
 * wikisource:Template:InterLingvLigoj
 * Template:About.

In-page interlanguage links
To make an interlanguage link in-page, prefix a colon (e.g. wiki ). This can e.g. be useful to link to a page in another language if no local version is available. See also some example templates for conveniently making such links:


 * - nl: (in Dutch)
 * - (nl)
 * -  (nl)
 * - (nl)
 * - (nl)

Interlanguage link in the wider sense
An interlanguage link in the wider sense includes a link to a corresponding page in another language which, for the software, is a regular link, as opposed to one employing the special interlanguage link feature as described above. This can also be an internal link on a multilingual project, e.g. on Meta:


 * Interlanguage links

Possible reasons for using an "interlanguage link" in the page body include:
 * control over position
 * control over label
 * the target contains an anchor

Interwiki links versus external links
Disadvantages of interwiki links:
 * the wikitext is less portable across wikis, because wikis do not always have an interwiki prefix for the same sites, and even if they do, the prefixes may differ
 * there is no feature to find interwiki links, while searching for an external link can be done with Special:Linksearch (if installed). This is due to the fact that, while there is an externallinks table, there is no such thing for interwiki links (the interwiki table only stores the interwiki prefixes with their targets as function of the parameter, not the instances of the links). Using the general text search to search for interwiki links is more work for the server, and therefore it may be slow, or not up-to-date, or in busy hours disabled. See also Finding external links to a page.

Using templates like, the advantages of interwiki links and external links are combined. When a page using this template, which is in this case used for links to the English Wikipedia, is copied to that site, a template with the same name is needed there too. Due to that template,, which redirects to , the interwiki links are automatically converted to internal links. Hence they provide existence detection, and allow use of "What links here" as well as Linksearch.

Comparison: Linksearch works for the latter only.
 * Bee Movie gives Bee Movie
 * Bee Movie gives Bee Movie

The applicable CSS classes are "extiw" and "external text". The choice may be governed by this, either way, for uniformity or distinction. An interwiki link is easier to type by itself, but if one goes to the webpage anyway before putting the link, copying the URL is very convenient. When a template is created, e.g. imdb title, the template can be made such that it uses an interwiki link, and a parameter like "tt0389790" or "0389790", or that it uses an external link, and a parameter like one of those or the full url if that if more convenient.

Interwiki links to the same wiki versus internal links
Disadvantages of interwiki links to the same wiki, compared to internal links: Advantages of interwiki links to the same wiki, compared to internal links:
 * no existence detection
 * "What links here" works for internal links only
 * better portability across wikis, provided that the same prefix applies, and is not equal to a namespace name

Using templates like, the advantages of internal links, interwiki links and external links are combined (with respect to portability: provided that a template with the same name and adapted content is present on the other site).