Wikipedia:Merging
![]() | This is aninformation page. It is not one ofWikipedia's policies or guidelines;rather, its purpose is to explain certain aspects of Wikipedia's norms, customs, technicalities, or practices. It may reflect differing levels ofconsensusandvetting. |
Amerge,ormerger,is the process of uniting two or more pages into a single page. It is done by copying some or all content from the source page(s) into the destination page and then replacing the source page with aredirectto the destination page.
Any editor can perform a merge. No permission or discussion is needed if you think the merge is uncontroversial;just do it(but it might get reverted). Otherwise, the merge should be first proposed and discussed, as detailed below.
When performing a merge, one should remember to reconcile talk pages, and to attribute copied content, asrequired by Wikipedia's license.At minimum, this means adding words "Merged content to/from [[page]]"toedit summaries. SeeHow to mergebelow for details.
Reasons for merging
There are several good reasons to merge pages:
- Duplicate:There are two or more pages on exactly the same subject, with the same scope. If a duplicate article was recently created, it may also be a candidate for speedy deletion underCSD A10 criteria.
- Overlap:There are two or more pages on related subjects that have a large overlap and might beWP:REDUNDANT.Remember, thatWikipedia is not a dictionary;there does not need to be a separate entry for every concept. For example, "flammable" and "non-flammable" can both be explained in an article onflammability.Topics with the same name that are normally covered in a single article for exampleGreenlanddeals with both the country and island (which have similar boundaries) thus aGreenland (island)article can be merged with the "Greenland" country article, seeWikipedia:Semi-duplicate.
- Short text:If a page is very short (consisting of perhaps only one or two sentences) and is, in your opinion as editor, unlikely to be expanded within a "reasonable" (unspecified) amount of time, it often makes sense to merge it into a page on a broader topic.
- Insufficient notability:Some topics may not reach thegeneral notability guidelines,or more specific criteria, so merging is analternative to deletion.While this can also be implemented through thearticles for deletionprocess, merging directly may be more efficient. For example, parents or children of a celebritywho themselves are otherwise unremarkableare generally covered in a section of the article on the celebrity.
- Context:If a short article requires the background material or context from a broader article in order for readers to understand it. For example, minor characters from works of fiction are generally covered in a "List of characters in <work>" article (and can be merged there); see alsoWikipedia:Notability (fiction).
Merging should be avoided if:
- The resulting article would betoo long or "clunky",
- The separate topics could be expanded into longer standalone (but cross-linked) articles, or
- The topics are discrete subjects warranting their own articles, with each meeting theGeneral Notability Guidelines,even if short.
Proposing a merge
![]() | Need help? List your articles at the bottom ofWikipedia:Proposed mergers,and someone will list the suggested merge for you. |
If the need for a merge is obvious, editors canbe boldand simply do it.Seehow to mergebelow. Bold merges may be reverted, even though they are labor-intensive to complete, but this edit process andcivil discussionproduces better articles. Articles that are young or short, such asstubsdiffering only in title and wording, should be merged immediately. Articles that have been separate for a long time should usually be discussed first, especially those on controversial topics.
To start a discussion, perform the following steps. If the merge is difficult to perform or seems potentially controversial, you should request assistance and feedback atWikipedia:Proposed mergers.
Do notuse the discussion procedure described here to propose:
- Category merges:Category merges should be requested atWikipedia:Categories for discussion,which uses the separate{{cfm}}template.
- Template merges:Template merges should be requested atWikipedia:Templates for discussion,which uses the separate{{tfm}}template.
Step 1: Create a discussion
This is usually done on the proposed destination page's talk page. Exceptions:
- If the destination does not exist, do not create its talk page (it could get speedily deleted).
- If a discussion exists already, do not move it (for example, having a discussion on the source page is acceptable).
For example, if suggesting thatFoobe merged intoBar,create a proposal in a new section atTalk:Bar. Start a new section at thebottomof that talk page and includethe proposal itself, the list of the affected pages, and a merge rationale. A good example is the following section:
== Merge proposal ==
I propose merging[[Foo]]into[[Bar]].I think the content in Foo can easily be explained in the context of Bar, and a merge would not cause any article-size or[[WP:UNDUE|weighting]]problems in Bar.~~~~
Notify involved users (optional)
You may optionally notify involved users (e.g. contributors to the source and destination pages), who might not bewatchlistingthem. One way is to simplynotify themdirectly from the merge discussion page:
{{ping|User1|User2|User3|...}}
Message text. ~~~~
Alternatively, go to those users' talk pages and start a new section. Make sure to provide a link to the merge discussion. You may use the following standard templates to leave a standard message:
{{subst:Mergenote|Foo|Talk:Bar#Merge proposal}}
Please respectneutralitywhen making invitations to participate in the merge discussion.Votestacking,that is, canvassing support by selectively notifying editors who have a predetermined point of view or opinion, is inappropriate.
Step 2: Tag the relevant pages
These templates shouldnotbesubstituted.
To propose a merge of two pages, place the following template at the top of each page or section:
{{merge|OTHERPAGE|discuss=Talk:DESTINATIONPAGE#Merge proposal|date=August 2024}}
If you know which page should be removed, use
{{merge to|DESTINATIONPAGE|discuss=Talk:DESTINATIONPAGE#Merge proposal|date=August 2024}}
on the source page, and
{{merge from|SOURCEPAGE|discuss=Talk:DESTINATIONPAGE#Merge proposal|date=August 2024}}
on the destination page.
If two pages are proposed to be merged into a third destination page that already exists, use
{{merge|OTHERSOURCEPAGE|target=DESTINATIONPAGE|discuss=Talk:DESTINATIONPAGE#Merge proposal|date=August 2024}}
on the source pages, and
{{merge from|SOURCEPAGE1|SOURCEPAGE2|discuss=Talk:DESTINATIONPAGE#Merge proposal|date=August 2024}}
on the destination page.
If two pages are proposed to be merged at a destination page that does not yet exist (destination does not have a talk page), use
{{merge|OTHERSOURCEPAGE|target=DESTINATIONPAGE|discuss=Talk:SOURCEPAGE#Merge proposal|date=August 2024}}
on each source page, choosing one of the source talk pages as the discussion location and ensuring thediscuss
parameter directs to this talk page on both source pages.
Please use thediscuss
parameter to directto the same talk page.Otherwise, two separate discussions could take place.
If thediscuss
parameter is not specified, the "Discuss" links lead to the top of each article's Talk page.
In{{merge to}},{{merge from}}), it always leads to the destination talk page, but it is still preferable to link to a specific section of the talk page.
In other namespaces
- Do not use the above templates to propose acategorymerge. This should be requested atWP:Categories for discussion,which uses a separate{{cfm}}template.
- For a merge of pages within "Wikipedia" namespace (titles with the "Wikipedia:" or "WP:" prefix), do not include this prefix in the parameter.
- When proposing a merge between two different namespaces, these templates won't work because of technical limitations.
Step 3: Discuss the merge
Make sure to followstandard talk page guidelines,which includescivilityandstaying focused on the content, not on the involved editors,usingthreaded discussion formatting,not biting newcomers,and being clear and concise.
In many cases, a hybrid discussion/straw poll is used, but remember thatpollingis not a substitute fordiscussion.Example formatting:
*'''Merge'''– <insert reason for supporting merge here>~~~~
*'''Don't merge'''– <insert reason for opposing merge here>~~~~
Step 4: Close the merge discussion and determine consensus
During discussion, arough consensusmay emerge to proceed with the merge.Any user, including the user who first proposed the merge,may close the discussion and move forward with the merge if enough time (normally one week or more) has elapsed and therehas been no discussionor if there is unanimous consent to merge. Closing of merge discussions differs fromclosing of requested move discussionsin that closings of uncontroversial merge discussions byinvolved usersare allowed. Admin tools are not needed unless page protection prohibits editing.
In more unclear, controversial cases, the determination that a consensus to merge has or has not been achieved should be made by an editor who is neutral and not directly involved in the merge proposal or the discussion. The discussion can be posted atWP:Proposed mergersto get some help. If necessary, a request that an administrator, who is notinvolved,close the discussion can be made at theRequests for Closurenoticeboard.
To close a merge proposal discussion, the{{Discussion top}}and{{Discussion bottom}}templates are used in the following manner:
== Merge proposal ==
{{Discussion top|result=The result of this discussion was....~~~~}}
The merge proposal...
*and discussion...
*...
{{Discussion bottom}}
After closing the merge proposal discussion, remove the{{Merge to}}template from the source page and place the{{Old merge}}template on the corresponding talk page in the following manner:
{{Old merge
|otherpage=<destination page, entered as "Page name" (without brackets)>
|date=<date merge was proposed, entered as "a date string" (according to preference)>
|result=<result of discussion, entered as "'''No consensus'''"(with boldface markup)>
|talk=<merge discussion, entered as "Talk:Page name#Section name" (without brackets)>
|URL=<permanent link, entered as "U_R_L" (with underscored spaces and without brackets)>}}
Remove the{{Merge from}}template from the target page if the consensus is "do not merge" or "no consensus".
Merges can be easily reversed if a consensus is formed against it shortly after it was performed. If there is a consensus against the merge, or if there is no consensus or no discussionandyou don't believe that it is appropriate to merge the pages, then please remove the merge proposal tags and, if necessary, close any discussion.
Step 5: Perform the merge
See§ How to mergebelow. The main reason that the merge backlog includes thousands of articles is because the people who support the merge neglect to undertake this final step.Any editor, including the editor who originally proposed the merge,is permitted to perform a merge in accordance with consensus. Merging pages doesnotrequire intervention from an administrator.
Merge as a result of a deletion discussion
InArticles for Deletion (AfD) discussions,editors may suggest that thearticle(s) nominated for deletion bemergedto an appropriate article. If there is a rough consensus for a merge at the end of a deletion discussion, the following template is placed at the top of the nominated article:
{{Afd-merge to|destination article|debate name|debate closure date}}
Similarly, the following template is placed on the destination article's talk page:
{{Afd-merge from|nominated article|debate name|debate closure date}}
This informs users involved in those pages that content is to be merged as a result of a deletion discussion. It is theinvolved editors' job,not theclosing administrators' job,to perform the merge. Proceed in the manner described above. See alsoWikipedia:Merge what?for an essay encouraging not to just votemergeinAfDdiscussions.
How to merge
- Copyall or some of the content from the source page(s) andpastethe content in an appropriate location at the destination page.Don'tjust redirect the source page without copying any content if any good content from the source page exists. Publish the edit, leaving the following edit summary (a link to the source article isrequired by copyright):
Merged content from [[source page]] to here. See [[Talk:merge discussion section]].
- Ideally, do any necessary copyediting and rearranging in a separate, second edit rather than when you first paste the moved text (to simplify attribution). In practice, this means: Copy and paste all the content you want to transfer; publish the page with the required edit summary (even if it duplicates parts or looks a bit messy at this stage; you can use{{In use}}if you want to let others know you'll be fi xing it right away); then edit the page a second time to clean it up.
- Redirectthe source page whose content was just merged by replacingeverythingwith the following:
#REDIRECT [[destination page]]{{R from merge}}
- Or if the content was merged to a single section, the following:
#REDIRECT [[destination page#section]]{{R from merge}}{{R to section}}
- Publish the page, leaving the following edit summary:
Merged content to [[destination page#section]]. See [[Talk:merge discussion section]].
- Reconciletalk page tags. If the source page has a talk page:
- Move any{{merged-from}}and{{copied}}templates to the destination page's talk page.
- Reconcile{{WikiProject....}}templates: copy them from the source page to the destination and remove duplicates (look out for alternative templates; e.g.{{WikiProject Software|Computing=yes}}is the same as{{WikiProject Computing|Software=yes}}). Once copied, change the source article WikiProject templates so that they contain
|class=redirect
(even for WikiProjects that do not yet support a redirect class); this does not have to be done if{{WikiProject banner shell}}is being used, since that template will automatically choose the class.
- Optionally:Tagthe destination page's talk page with
{{merged-from|source page name|date}}
,and the source page's talk page with{{merged-to|destination page name|date}}
.Place these tags at the top of the talk pages.- As an alternative, experienced users can add
{{copied|from=|from_oldid=|to=|to_oldid=|to_diff=|date=}}
to the top of both talk pages.
- As an alternative, experienced users can add
- Optionally:Fixanydouble redirectsfound atSpecial:WhatLinksHere.A bot automatically fixes this problem but it may take a day or two.
- Checkfornon-freeimages (or other files). Examples:a book cover,a poster,a logo,etc. The description page of such an image will have a red copyright icon and anon-free use rationale(a summary box withNon-free use rationalein the title, or aFair usesection) – the article title mentioned in such a rationale should be updated. This is required under thenon-free content criteria.
- Removethe relevant
{{Merge from}}
template from the destination article, if it still exists.
Note:Most merged articles are not good candidates for merging of page histories because they have been edited in parallel and the collation of their edit states would create unhelpful and/or misleading diffs. In most cases, no request for a history-merge should be submitted. (A more detailed explanation is availablehere.)
See also
Pages to merge
October 2023 | 2 |
November 2023 | 54 |
December 2023 | 92 |
January 2024 | 50 |
February 2024 | 93 |
March 2024 | 253 |
April 2024 | 217 |
May 2024 | 270 |
June 2024 | 219 |
July 2024 | 318 |
August 2024 | 372 |
Undated articles | 0 |
Wikipedia:WikiProject Mergewas initiated to clear merge backlog. Current pages tagged for merging can be found atCategory:Articles to be merged,which lists pages that have been tagged for merging on a particular month (tagging began in September 2006).
List of merge templates
Seeherefor a table with examples.
Other guides
- Wikipedia:Moving a page
- Wikipedia:Splitting
- Wikipedia:Section move
- Wikipedia:Content forks,on duplicated content in acceptable and unacceptable cases
- Wikipedia:Copying within Wikipedia,more details on copyright issues
- Wikipedia:Merge and delete,on deleting the source page instead of redirecting (to be avoided)
- Wikipedia:Administrators' guide/Fi xing cut-and-paste movesandWikipedia:Requests for history merge,in cases when changing page history is needed
- Wikipedia:Articles for merging,a failed proposal for a different discussion process