This is an archive of past discussions on Wikipedia:Hatnote. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.
Searching for an italicized title. Normal text in results list, italics in the "containing" search.
The issue of italicized italics in hatnotes which are already in italics was discussed in 2017 and again in 2019. I've just found those discussions now, as I don't watch discussions on this page. The 2019 discussion led to the introduction of the Wikipedia:Hatnote § Hatnotes with italics in the links section by SchreiberBike on 28 August 2019 (diff).
A couple of reasonable objections to this convention were raised:
The point of the italics in the hatnote is to show that it is not part of the actual article, so any other formatting is confusing. Siuenti (씨유엔티) 23:56, 10 April 2017 (UTC)
In my IRL work I used to take the un-italicize route, but at some point I decided to looks weird, and I began to underline, like this:
"Spotted angle" redirects here. For the other butterfly with this common name, see Caprona alida.
I'm not going so far as to recommend that for use here, but just thought I'd throw it out. EEng 11:04, 9 August 2019 (UTC)
I agree with both of those points – it's debatable whether the "non-italic" formatting is confusing or helpful, and it looks weird. In addition to those issues, I'll add my own.
The purpose of hatnotes is navigation. They are a part of the tools readers use to find articles. The main tool they have is the search box. Observe the example search I uploaded. A reader searching for the Abaratha alida article just types "Abaratha alida" into the search box. They are not required to type the name in italics. Indeed, if they try to italicize the title in the search box, they run into trouble:
The page "''Abaratha alida''" does not exist. You can create a draft and submit it for review, or you may create the page "Abaratha alida" directly, but consider checking the search results below to see whether the topic is already covered.
The list of search results shows all results in normal text. It does not distinguish titles which are italicized from those which are not. Then the "Search for pages containing" link always italicizes the title which to search for in pages. It doesn't "non-italic" the title to search for pages containing the italicized title. In short, the convention for use of italics in search is different from the convention used in the bodies of articles.
Italics in hatnotes can cause false-positive population of Category:Missing redirects, a category I patrol. This is why I've started this discussion today. The hatnote on Nocturnes (Debussy) is populating this category, because of the use of "non-italic" in the hatnote:
"Trois Nocturnes" redirects here. For other uses, see Three Nocturnes.
The problem is that no, ''Trois Nocturnes'' does not redirect to there. Trois Nocturnes, in plain text, is what actually redirects there. Italics do not work inside Wikilinks. They must be placed outside the Wikilink to work properly.
This problem also came up recently at Interdiction of MV Matthew, where, after conflicting with Tamzin, I resorted to creating a custom {{hatnote}}, to avoid the issue. This compromise means that the page has been removed from the hatnote patrol, making it more vulnerable to potential future vandalism or other issues that the hatnote might have detected.
Issue goes back to my August 2015 RfA, where there was concern about I redirect I created in order to accommodate a Chinese character in a hatnote:
Thanks, Redrose. I created ''唐山'' because an editor was quite persistent in insisting that Chinese characters should not be italicized in hatnotes. I would have been happy to have simply removed that foreign-language "redirects here" hatnote, but they insisted on keeping it. So, my compromise kludge was to create that redirect to keep the page out of the "flagged for maintenance" category. I was quite happy to see the redirect finally come off that page, which in turn made my work-around unnecessary. Wbm1058 (talk) 12:16, 24 August 2015 (UTC)
I'm not understanding what the problem is? Italics work fine in hatnotes, using '' outside links or making use of the {{!}} template when piping is needed (e.g. when only part of the title needs to be italicised. For occasions when it's the "redirects here" that needs partially italicising then just use a custom hatnote template (or someone more skilled than me can create a new standard one). When items that would normally be italicised occur in otherwise italicised text the standard is to deitalicise it, and other than your personal dislike of that I'm not seeing any reason to deviate from that standard? Thryduulf (talk) 18:53, 4 November 2023 (UTC)
While, as one of the people writing code for hatnotes, italicization is annoying, I think I generally lean towards including it, and largely agree with Thryduulf.
Where I diverge from Thryduulf is that I'd prefer to not either use custom hatnotes or change the behaviour of {{redirect}} and similar: when we display the redirected title, we are mentioning title text (a string that is recognized by MediaWiki), and not an actual title (a name for a specific subject), therefore we should not (de)italicize in those cases—a razor-sharp semantic distinction, to be sure, but it seems reasonable to me. I can probably add an option so that you can do something like {{redirect|Foo|redirectmask1=Bar}} to specify italicization, but since I disagree with the semantics, I don't want to write it unless we get a consensus that it's preferred.
Longer-term, I wish we'd get a way to pull the title content of {{DISPLAYTITLE:title}} via something in the mw.title Scribunto library (without, you know, transcluding and pattern-matching the whole page for the DISPLAYTITLE declaration) so that I could automate away having to manually specify italics most of the time, but that's a whole other suggestion. {{Nihiltres |talk |edits}}23:38, 10 November 2023 (UTC)
Can you center a hatnote, rather than it just be indented?
Sometimes it looks as though it doesn't stand out enough, like it's engulfed by the section header and the text of that section. Just wondering how I offset that. Thanks. --Cinemaniac86TalkStalk17:21, 12 November 2023 (UTC)
You could try adding a few colons before the template, although it's likely someone will eventually delete them as non-standard. Station1 (talk) 17:40, 12 November 2023 (UTC)
Indeed they would, also per MOS:INDENT, since it would be an abuse of list markup for visual indentation which is an accessibility problem (despite the fact that we permit it on talk pages; that should have been fixed a long time ago by a parser change to handle line-initial colons differently on talk pages). If you insist on indenting something in an article for visual effect, use {{block indent}}, {{indent}} or {{in5}}, which ever works better for the use case in question (or {{blockquote}}, but only if it is actual block quotation). Back to hatnotes: The desire expressed here seems to be based on something like mobile device viewports, and does not take account of the fact that on a wide monitor, centring the hatnote would have the opposite of the desired effect, and move it so far inward in the wide viewport that it would be less likely to be noticed. There is no consensus to change the layout of hatnote placement, and unlikely there would ever be one, so going around massively indenting or centring them is apt to be seen as unconstructive WP:MEATBOT behavior and reverted. PS: It's also important to remember that our hatnotes are just cross-references and are not part of the article content, but a form of permissible Wikipedia self-reference that we tolerate as something that can be useful for readers, for specific purposes and when it is not done in excess. Using visual trickery to make them much more promiment [for a particular class of users] than the real content is against their purpose and design. So don't go around making them boldface or orange or all-caps, either. — SMcCandlish☏¢ 😼 20:09, 12 November 2023 (UTC)
Thank you for that adorable advice. No, no rainbows or crazy-Karen-capslock-hatnote shouting, like my mom on Facebook. This was just a hypothetical inquiry. I tested out the asterisk, pound, and colon indents, and they just looked ugly and disjointed. And a "br" in between left too large a gap.
Actually, I'm on a laptop, not a mobile. The situation in question is on an actress's article page, Bette Davis#Selected filmography. Initially, with the two columns, it only said "main article: Bette Davis filmography". But altering it to this more descriptive hatnote emphasizes the page better; and it isn't so short, where it looks as if it's the first item on the list at first glance. That's what I was bothered about at first.
In any event though, thank you both @Station1 & @SMcCandlish for your input! Much appreciated. Idk if you think there was a better solution, but I'll opt to try different hatnotes first that fit the situation and keep in mind that advice you mentioned above. --Cinemaniac86TalkStalk20:49, 12 November 2023 (UTC)
@Cinemaniac86: It looks okay to me, in that it's how hatnotes always appear in front of lists, but I think what you're concerned about is that a hatnote is usually indented a little from the content that follows it, and here it is not (in effect) because they are all list items that are also indented the same amount. Because the original intent of the hatnote template is to be slightly indented from main text (not centred!), an argument could thus be made to indent it more, by the same amount, in this kind of case. I happen to randomly know (from various template work) that the indentation amount is 1.6em, so the intended effect here could be done with:
{{block indent|{{Main list|Bette Davis filmography}}|left=1.6|reason=Hatnotes are supposed to indent a bit from the content after them, so this will do that when the content is itself an indented list.}}
Actually, the same effect could be done by just doubling the "hatnoteness":
{{hatnote|{{Main list|Bette Davis filmography}}|reason=Hatnotes are supposed to indent a bit from the content after them, so this will do that when the content is itself an indented list.}}
Both code approaches have an identical visual output for the reader. But Station1 is probably correct that someone is apt to remove it later as unnecessary/nonstandard. An explanatory |reason= might forestall such reversion. — SMcCandlish☏¢ 😼 21:14, 12 November 2023 (UTC)
Would a redirect from the term, here "Gyroid", be compliant with WP:Redirect and particularly WP:R#KEEP? If so, then if the term has other uses, a hatnote or dab page should be provided. PamD06:23, 7 December 2023 (UTC)
Yeah, I'm pretty sure it's another thing left to consensus at a particular article's talk page. We have a whole lot of those, and they are often lead to butt-pain disputes, but are a necessary cost of WP:CREEP being a concern that most of the community have. That is, if we tried to nail down everything we can think of in explicit rules, it would take all year just to read our rules and no one would be able to remember more than a fraction of them. — SMcCandlish☏¢ 😼 21:22, 7 December 2023 (UTC)
PS: Looked at the articles, and am inclined to keep the hatnote. If it were an occurrence of a gyroid or a pentagonal icositetrahedron (also called a gyroid) in the game, then it would not be a necessary hatnote, but it's a video game character which is a different sort of thing, and the game is popular, so various readers would be looking for it and the two non-game articles have nothing to do with it. It's just a fact of the times that video-game schtuff is "important" to various readers. — SMcCandlish☏¢ 😼 21:26, 7 December 2023 (UTC)
There should be at least a full sentence about the hat's topic in the target article. Not everything mentioned in another article is worth a dab hat. fgnievinski (talk) 00:55, 8 December 2023 (UTC)
Meh. By that reasoning, we would have an entire "WP:HFD", "WP:Hatnotes for deletion" process that examined hatnote link targets (the content of which can change at any time). The whole paragraph or even section that is in a page this minute might turn into just a sentence in the next minute, or vice versa. The coverage being in the article at all should be sufficient (as long as it's actually a distinct topic that happens to share the same name as other topic(s) and needs disambiguation). Maybe this makes me a "hatnote inclusionist", but our goal with hanotes should be getting readers to what they are looking for, whether we think they should be looking for it or not and whether we think they'll find much there (as long as they'll find something there). — SMcCandlish☏¢ 😼 01:23, 8 December 2023 (UTC)
There are two basic questions, will someone searching for a different topic plausibly end up at this article? Will someone searching for a different topic find useful information about that topic at (or via a dab/sia at) the other page? If the answer to both questions is yes then there should be a hatnote. Thryduulf (talk) 03:08, 8 December 2023 (UTC)
Right, but then what do we do if you come across a "hatnote deletionist" (like me)? I propose consensus can be found in WP:R#CRD: if the hatnote doesn't justify the creation of a redirect, then the hatnote shouldn't be posted on another article's lead. In the present case, Gyroid (character) is a reasonable redirect, so you win. fgnievinski (talk) 03:09, 8 December 2023 (UTC)
Despite being here since the Neolithic, I hadn't remembered that CRD thing. Seems like a good thumb-rule to remember; thanks for that. It's more concrete than the "seems reasonable to me" sense I've been using (though I guess what constitutes a sensible redirect is also open to a certain level of debate). Thryduulf's double-razor is pretty useful, too. — SMcCandlish☏¢ 😼 07:25, 8 December 2023 (UTC)
There can be exceptions: Linking to redirects is typically not preferred, although of course exceptions can occur. It's a matter or consensus if a given situation warrants an exception. This is basically WP:IAR codified for a specific case.—Bagumba (talk) 09:20, 7 December 2023 (UTC)
More aptly, I would say it's a reminder of WP:P&G: "Guidelines are sets of best practices supported by consensus. Editors should attempt to follow guidelines, though they are best treated with common sense, and occasional exceptions may apply." It's not IAR if a rule isn't being ignored. :-) — SMcCandlish☏¢ 😼 21:17, 7 December 2023 (UTC)
@Bagumba I think pointing from one guideline to the other makes more sense than to try to short-circuit to the other guideline's manual of style. We generally want whoever is following these instructions to be aware of the entire context. --Joy (talk) 11:02, 2 January 2024 (UTC)
There really isn't much relevant at Wikipedia:Disambiguation w.r.t. redirects and hatnotes. TLDR is the danger. The risk is readers not having the wherewithal to find their way over to the relevant MOS subsection. —Bagumba (talk) 11:14, 2 January 2024 (UTC)
I suppose that could be a risk, but there's a whole section named "Hatnotes", which explains the listed " (disambiguation)" topic and a lot of other stuff. Maybe the real question is why do we split this information in two separate guidelines and a section of the manual of style in the first place :) --Joy (talk) 16:00, 2 January 2024 (UTC)
I see this over and over again: hatnotes added to sections for no good reason IMO. I just got reverted for removing the hatnote in Thor: Love and Thunder#Documentary special. What possible purpose is served here? The link is in the first sentence of a two-sentence section. It's not particularly hard to find. Clarityfiend (talk) 03:13, 1 April 2024 (UTC)
In this particular case the {{main}} hatnote is not appropriate - not because of the small size of the section, but because the section is not a summary of the hatnote target. Per {{Main}} documentation, replacing the example article and section with this specific case: "For example, in Thor: Love and Thunder, the template under the "Documentary special" section should not be {{Main|Marvel Studios: Assembled}}, because the section specifically deals with The Making of Thor: Love and Thunder as one example of a documentary and not Marvel Studios: Assembled documentaries in general."
"because Marvel Studios: Assembled does not have a section for Thor: Love and Thunder." It may not have a section, although it does have an episode description w/ cast and crew details for it in the episode table. Per WP:BRD, I have restored the WP:STATUSQUO to let the natural discussion process run its course. I have also notified other members of the MCU taskforce at WT:MCU regarding this to gauge the perspectives of other contributors across these articles in question, as we strive to keep them consistent. I honestly did not think this one revert would cause a little stir and warrant such discussion, though I'll WP:AGF (even though sometimes we all need to keep a level head, take no for an answer, and work with each other).
There is no ill-intent with using the hatnote and it is being used to better serve our readers in navigating them to the main article on these documentary specials. If it would better service concerns to title the section header "Marvel Studios: Assembled documentary special", then that could be a form of a compromise, though removing it outright is not the intended goal here. {{See also}} could be a workable replacement, though this seems to be just another case of words being used to convey different meanings when they share the same result of how to better direct and guide our readers across this encyclopedia. Not every reader is expected to read every sentence and some just want to look for the other articles themselves for the details there. Trailblazer101 (talk) 04:02, 1 April 2024 (UTC)
I also want to question where does it specify that hatnotes ought to point to dedicated sections only? {{Main}} states "When a Wikipedia article is large, it is often written in summary style. This template is used after the heading of the summary, to link to the subtopic article that has been summarized. The Assembled article's contents of this film's special are being summarized in the section at the film article and is explained further at the Assembled article in the body and the episode table where the exact special in question is mentioned in detail. {{Further}} supports this usage: "It is typically used at the top of a section, when the topic of that section is covered in more detail by another page." Not all readers are expected to know what Assembled is, hence the brief summar in the section, though the bulk contents of the said special is covered at the Assembled article.
I will note there is also {{Broader}}, which exists (per its documentation): "It is used in sections for which there is also a separate article on the subject. It should be used when there should be a link to another article that discusses a subject more broadly, but is not a main article (which should use {{Main}}), a narrower topic (which should probably use {{Further}}), or at the same level of focus (which should probably use {{See also}})." I believe using Broader in these instances is a workable compromise that best addresses the concerns raised while also maintaining the goals of the taskforce in adequate, proper, and easy navigation for our readers. Trailblazer101 (talk) 04:08, 1 April 2024 (UTC)
It [Marvel Studios: Assembled] may not have a section [for Thor: Love and Thunder], although it does have an episode description w/ cast and crew details for it in the episode table. — in which case the appropriate hatnote would be {{further|Marvel Studios: Assembled#ep12}}. However (similar to Clarityfiend}'s original point) there is already a wiki-link (via redirect The Making of Thor: Love and Thunder) to that target in the text of Thor: Love and Thunder#Documentary special, so the hatnote is someone superfluous in such a small section. Mitch Ames (talk) 06:05, 1 April 2024 (UTC)
Sounds to me like we just need to clean-up the links for the section: replace the current hatnote with {{further|The Making of Thor: Love and Thunder}} and remove the unnecessary links from the prose considering it is such a small section. - adamstom97 (talk) 06:57, 1 April 2024 (UTC)
replace the current hatnote with {{further|The Making of Thor: Love and Thunder}} and remove the unnecessary links from the prose — What's wrong with "leave the existing wikilink in the prose and remove the unnecessary hatnote" (considering it is such a small section, containing the words "The Making of Thor: Love and Thunder")?
Better still, remove the existing first sentence "In February 2021, the documentary series Marvel Studios: Assembled was announced" because it's irrelevant in this context. Instead reword the section as:
It is expected for short summary sections about a different project that the section starts with a hatnote, I don't see why we should treat this one differently. - adamstom97 (talk) 08:47, 1 April 2024 (UTC)
It is expected for short summary sections about a different project that the section starts with a hatnote — Which policy or guideline says that? Mitch Ames (talk) 10:20, 1 April 2024 (UTC)
It appears that the style of hatnotes has changed. I've looked at various templates but I haven't managed to find where this change was actually made. Was there a discussion before the change was made? Un assiolo (talk) 19:35, 13 June 2024 (UTC)
Do we have an "About-Distinguish-For" hatnote? If not, I think we should.
"About-Distinguish-For" would be a very useful template. Several articles I recall would benefit from hatnotes of that particular nature. Here's one example:
There might be better examples, but in this instance:
ABOUT: Identifies which one this is, obviously.
DISTINGUISH: Specifically singling out the most significant (Oscar winner), and most likely to be incorrectly Wikilinked.
FOR: Then the disambiguation page w/ multiple other Departure-named flicks; directly to section.
While it could be done all freeform with one of those custom text ones, I was kind of surprised not to see one of these amongst the lists of potential hatnote options, considering all of the other combinations.
And I found this in the archive, which looked suitable, but unfortunately it doesn't exist:
Testing //composed hatnote|about|SUBJECT|distinguish|SIMILARCONCEPT|for|USE|PAGE|text|TEXT\\.
But that would be the ideal About-Distinguish-For.
I dunno if there's one that I'm overlooking somewhere OR some way to squeeze a "For-custom-text" hatnote template WITHIN an About-Distinguish one, by any chance…? Dubious. --Cinemaniac86TalkStalk15:56, 17 June 2024 (UTC)
I don't see why the 2008 and 2015 films need some special distinction separate from the other films. I think {{For|other films with the same title|Departure (disambiguation)#Films}} producing:
would be sufficient. If there is actually some good need to distinguish two out of the set for some reason, this can be done with {{About|the 2015 English-French film|the 2008 Japanese film|Departures (2008 film)|other films with the same title|Departure (disambiguation)#Films}} producing:
Yeah, I appreciate that option and your POV, thank you. But it doesn't phrase it as "Not to be confused with", in the middle. Like I stated, I feel like that is one missing combo, and there are so many similar combos.
For example, there is REDIRECT-Distinguish-For. So why can't there be About-Distinguish-For?
Like I said, this may not be the quintessential example to work with, but it's AN example. Think outside the box. Is there some way to manipulate the templates to create This page is about XXXX. Not to be confused with Xx Xx. For other/similar ____, see XXXX (disambiguation)? --Cinemaniac86TalkStalk00:38, 18 June 2024 (UTC)
The multiplicity of hatnote templates with differing parameters is already very confusing. I can't see adding yet another to the mix, especially when the use case need isn't very clear. Why make more work when there is no need? older ≠ wiser01:19, 18 June 2024 (UTC)
Is there a way to combine multiple hatnotes?
Specifically for this article. I find hatnotes on multiple lines looks trashy and like we don't know what we're doing, I think both hatnotes in this scenario assume the audience is stupid but it's got consensus so I just want to tidy it up if possible. Darkwarriorblake (talk) 20:48, 1 July 2024 (UTC)
Ah, that ought to be utilizing the Redirect-Distinguish-For hatnote template. I just replaced it, so it's now combined all on one line. It follows example #4, where the "redirect" input is also the same as the "disambiguation" input, with the "not to be confused…" in the middle. Hopefully that doesn't create some kerfuffle! --Cinemaniac86TalkStalk23:15, 1 July 2024 (UTC)
No, I don't think it's helpful: we're talking about two different kinds of navigation, and the combined hatnote is confusing. I#ve reverted to the two separate hatnotes which, I think, are clear and not "trashy". PamD08:06, 2 July 2024 (UTC)
No, it looks trashy and puts a longer barrier between the reader and the important text. I've found hatnote group which does what I want per step 5 "Ideally, limit hatnotes to just one at the top of the page or section. Multiple hatnotes may be appropriate when they serve different purposes, such as disambiguating topics with similar names and explaining redirects. (In such cases, consider using hatnote group.)" Darkwarriorblake (talk) 08:21, 2 July 2024 (UTC)
Yes, that looks good. There's always something new to learn about editing Wikipedia, and {{hatnote group}} is today's new thing for me. PamD08:24, 2 July 2024 (UTC)
Ahh, good, everyone's happy! Yes, I was worried there would be an issue with the fact that the "redirect" and "disambiguation" was interrupted by the "distinguish". This solution seems most ideal, so that it doesn't look discombobulated. --Cinemaniac86TalkStalk15:15, 2 July 2024 (UTC)
With reference to this previous discussion (which I cannot find in the archives), the resulting change has created an issue where the first item at WP:HATNOTERULES: "Link directly to other articles" seems to discourage the use of redirects in hatnotes. However, following that, we are sent to WP:Disambiguation to follow the rules for linking to redirects, but there are no specific rules for hatnotes in that guideline. Specifically this has caused an issue in this discussion. I think we need more clarity on what was intended. Personally, I don't think we should be linking to redirects as they can cause WP:EGG issues in certain cases. --woodensuperman10:37, 5 August 2024 (UTC)
We should always do what is best for readers in any given case. Usually this will mean linking to redirects with possibilities (so that when content is written at the redirect title readers are taken directly there), and to redirects that are more concise than section titles without being a SURPRISE. Constructions like "Redirect" → "Article title#Redirect" and similar (i.e. where the subject implied by the title of the redirect matches the subject implied by the title of the section) are not normally going to be surprising and will very rarely present WP:EGG issues. I agree the current guidance could be clearer on this topic, but it does make it clear that linking to WP:INTDABLINK redirects is the correct thing to do so claiming it "discourages the use of redirects in hatnotes" is nonsense. Thryduulf (talk) 15:11, 5 August 2024 (UTC)
Don't twist my words. It makes a specific exception for this one case, I maintain that we should still be using direct links in most other cases so that readers end up where they expect. The change in January seems poorly thought out and has just muddied the guideline. --woodensuperman15:40, 5 August 2024 (UTC)
Of course we should be linking the redirect. A valid redirect is also not an WP:EGG link so I'm not sure how that is relevant. In the example you gave, an episode redirect is a valid link as if and when it becomes an article, the link is already there. It's also makes changing the target a simple one page edit, instead of having to edit every link to the target. That is exactly what a redirect is and that is covered by the various MoS pages on the topic. Gonnym (talk) 16:48, 5 August 2024 (UTC)
The point is that you need to know every article that needs editing, and then edit every one of those articles (could be one could be a hundred). Thryduulf (talk) 08:49, 6 August 2024 (UTC)
If that contravenes the guideline then the guideline is wrong and needs changing, but per Bagumba's quote it is actually compatible: The Magic Johnson article contains "Earvin "Magic" Johnson" in the lead (and thus contains the term "Earvin Johnson" and the redirect could absolutely served as an alternative title for the article. Thryduulf (talk) 09:24, 6 August 2024 (UTC)
Okay, I think I've worked out what's wrong with the guideline. I think it makes it clearer, and I now believe this is what is intended by the current wording, if we changed it to something along the lines of:
I would have expected that there'd be a rule or description at this page which instructs editors not to use hatnotes to link articles which have no mention of the title. For example, at Major Payne, there's a hatnote that says {{for|the webcomic character named Major Payne|VG Cats}}. However, there's no content at VG Cats about such a topic. I was inclined to remove the hatnote, and was going to explanatorily link to the section of this guideline that prohibits hatnote links that don't have related content, but I didn't find such a prohibition. Am I missing it? Am I misunderstanding the purpose of a hatnote in this instance? — Fourthords | =Λ= |02:03, 18 March 2025 (UTC)
I considered that, but that page specifically says,
Note that these style guidelines do not apply to article pages containing such sentence- or paragraph-level disambiguation techniques as having a hatnote at the top of an article pointing to a related subject. These guidelines only apply to pages correctly tagged with a disambiguation template.
It should be clear to someone following the link why they have been taken to the destination article. That doesn't necessarily mean the term always has to be mentioned, but the combination of link text and destination article shouldn't leave anyone, surprised, puzzled or frustrated. In most cases this means the topic needs to be included on the destination page but there could be exceptions.
If you come across something where you aren't able to find relevant content, check whether it has been moved elsewhere (e.g. the article has been split or moved) and updating the hatnote before just deleting it. Thryduulf (talk) 12:57, 18 March 2025 (UTC)
File metadata link hatnote?
If a file metadata link goes to an unrelated article, should that article have a hatnote linking to the correct page? For example, File:"Beware Ducks Crossing" sign 2025-05-08.jpg's camera model is listed as "A001" (the internal model name for the CMF Phone 2 Pro), which redirects to A-001 (an Apollo abort test). I imagine not, since it's not the most likely way to get to an article, but I'm not sure. Suntooooth, it/he (talk/contribs) 21:12, 8 May 2025 (UTC)
I'd say that there should be a hatnote for the exact reason we have redirects from file metadata titles in the first place - to enable people to find out information about the make/model of the equipment used. It's not the most likely way to get to an article, but that just means it's unlikely to be the primary topic in the event of a clash, not that nobody uses it. Thryduulf (talk) 22:12, 8 May 2025 (UTC)
