View source for Help:CirrusSearch/hi

<languages />
{{PD Help Page}}
{{TOC right}}
विकिमीडिया परियोजनाओं पर जानकारी प्राप्त करने का सबसे त्वरित तरीका है उसे खोजना। 
हर पृष्ठ पर एक '''{{lcfirst:{{int|search}}}}''' वाला बॉक्स होता है।

'''CirrusSearch''' एक मीडियाविकि एक्सटेंशन है जो [[w:Elasticsearch|Elasticsearch]] की मदद से [[Special:MyLanguage/Help:Searching|डिफ़ॉल्ट मीडियाविकि खोज]] पर कुछ अतिरिक्त सुविधाएँ जोड़ता है।
विकिमीडिया संस्थान पर सभी [[m:Special:MyLanguage/Wikimedia_projects|विकिमीडिया परियोजनाओं]] पर CirrusSearch का इस्तेमाल किया जाता है।
यह पृष्ठ CirrusSearch की सुविधाओं को दर्शाता है।
अगर आपके सवाल का जवाब इस पृष्ठ पर नहीं मिलता है, [[Help talk:CirrusSearch|वार्ता पृष्ठ]] पर ज़रूर पूछें और कोई-न-कोई आपको जवाब दे देगा।

मीडियाविकि एक्सटेंशन पर अधिक जानकारी के लिए {{ll|Extension:CirrusSearch}} देखें।

विकिडेटा पर इसके प्रयोग के लिए {{ll|Help:Extension:WikibaseCirrusSearch}} देखें।

<span id="How_it_works"></span>
== यह कैसे काम करता है ==
कीवर्ड्स और वाक्यांश डालकर अपने कीबोर्ड पर 'Enter' या 'Return' दबाएँ या फिर आवर्धक ग्लास आईकॉन, "खोजें", या "जाएँ" बटन पर क्लिक करें।
{{void|1=या फिर आवर्धक काँच के आईकॉन, 'खोजें' या 'जाएँ' बटन पर क्लिक करें।}}
अगर किसी पृष्ठ के पास वह शीर्षक है जो आपने दर्ज किया, आपको उस पृष्ठ पर सीधे ले जाया जाएगा।
वरना यह विकि पर सभी पृष्ठों को ढूँढ़ता है, और उन लेखों की एक सूची प्रदान करता है जो आपके खोज शब्दों के साथ मेल खाते हों, या फिर आपको एक संदेश दिखाया जाएगा कि सभी कीवर्ड्स और वाक्यांश किसी भी पृष्ठ पर पाए नहीं जा सकते।

अगर आप कुछ भी खोजे बिना "{{int|searchbutton}}" बटन पर क्लिक करते हैं, आपको "Special:Search" पर ला जाया जाएगा जहाँ पर आपको खोजने के लिए अतिरिक्त विकल्प मिलेंगे (जो खोज परिणामों की सूची से भी उपलब्ध है)

शायद आप किसी विशिष्ट [[Special:MyLanguage/Help:Namespaces|नामस्थान]] के अंदर अपने खोज को सीमित करना चाहें, जैसे सिर्फ {{ns:2}} पृष्ठों के बीच खोजना।
इस खोज के लिए अपने मनचाहे नामस्थानों को चुन लें।

{{note|1=नीचे उल्लिखित सभी कीवर्ड केस-संवेदनशील हैं और छोटे अक्षरों में हैं।}}
<span id="What&#039;s_improved?"></span>
== क्या सुधार हुआ है? ==

CirrusSearch डिफ़ॉल्ट मीडियाविकि खोज पर तीन सुधार जोड़ता है, जो हैं:

* कई भाषाओं में खोज के लिए बेहतर समर्थन।
* खोज इनडेक्स पर अधिक संख्या में अपडेट, यानी लेखों पर बदलाव खोज परिणामों पर कुछ ही समय में प्रभाव डालने लगते हैं।
* विस्तृत साँचें, यानी कि साँचों के अंदर की सामग्री को भी खोज परिणामों में दाखिल किया जाता है।

<span id="How_frequently_is_the_search_index_updated?"></span>
== खोज इनडेक्स कितनी बार अपडेट किया जाता है? ==

दो प्राथमिक खोज इण्डेक्स हैं:

पहला है पूर्ण-टेक्स्ट खोज, Special:Search पर।
इस इण्डेक्स को करीब लाइव ही अपडेट किया जाता है।
खोज परिणामों पर पृष्ठ के बदलाव कुछ मिनट बाद नज़र आएँगे, मगर 30 मिनट को इसका साधारण समय माना गया है।
साँचों पर बदलाव करने पर साँचे का इस्तेमाल कर रहे लेखों पर कुछ ही मिनटों से कुछ घंटों में बदलाव दिखने लगेंगे, जो कि इस बात पर निर्भर है कि कितने पृष्ठ साँचे का इस्तेमाल कर रहे हैं।
लेख पर एक [[Special:MyLanguage/Manual:Purge|रिक्त सम्पादन]] करने पर बदलाव को ज़बरदस्ती आगे बढ़ा दिया जाएगा लेकिन अगर सब कुछ ठीक से काम कर रहा हो तो इसकी ज़रूरत नहीं।

दूसरा इण्डेक्स है फ़ज़ी स्वतः पूर्णकृत शीर्षक खोज।
यह इण्डेक्स दिन में एक बार अपडेट किया जाता है और इण्डेक्स के अपडेट किए जाने के दौरान पूर्ण-टेक्स्ट खोज इण्डेक्स में क्या मिला था, उसका एक दर्पण बना लेता है।
समय के आधार पर किसी नए पृष्ठ को फ़ज़ी शीर्षक स्वतः पूर्णकरण तक पहुँचने में दो दिन तक लग सकते हैं।
अगर यह किसी विशिष्ट कार्य के लिए अस्वीकार्य है, [[Special:Preferences#mw-prefsection-searchoptions|सदस्य खोज विकल्पों]] में शीर्षक स्वतः पूर्णकरण को क्लासिक उपसर्ग खोज में बदल दिया जा सकता है जो पूर्ण-टेक्स्ट खोज इण्डेक्स का इस्तेमाल करता है।

<span id="Search_suggestions"></span>
== खोज सुझाव ==
खोज बॉक्स में लिखने पर दिखने वाले खोज परिणामों को लेखों की गुणवत्ता के एक औसत नाप से छाँटा जाता है।
यह देखता है कि कितनी विकिकड़ियाँ उस पृष्ठ से जुड़ी हैं, उस पृष्ठ पर कितनी बाहरी कड़ियाँ हैं, कितने हैडिंग्स हैं, और कितने अनुप्रेषण हैं।

खोज सुझावों को नकारकर सीधे खोज परिणाम पृष्ठ पर जाना संभव है।
क्वेरी से पहले एक टिल्ड <code>~</code> जोड़ दें।
जैसे "~Frida Kahlo"।
खोज सुझाव फिर भी नज़र आएँगे, मगर Enter कुँजी दबाने पर आपको खोज परिणामों के पृष्ठ पर ले जाया जाएगा।

एक्सेंट/विशेषक कुछ भाषाओं के लिए सक्षम हैं; विस्तार भाषा पर निर्भर है।

The algorithm used to rank suggestions is described in more detail at [[Extension:CirrusSearch/CompletionSuggester#Ranking criteria]].

<span id="Full_text_search"></span>
== पूर्ण-टेक्स्ट खोज ==
एक "पूर्ण-टेक्स्ट खोज" एक "इण्डेक्स किया गया खोज" है।
सभी पृष्ठों को विकि डेटाबेस पर रखा जाता है, और गैर-अनुप्रेषण पृष्ठों पर सभी शब्द खोज डेटाबेस में रखे जाते हैं, जो कि विकि के पूरे टेक्स्ट का एक इण्डेक्स-सा है।
हर दृश्य शब्द को पृष्ठों को उस सूची में इण्डेक्स कर लिया जाता है जहाँ इसे पाया गया था, तो किसी शब्द के लिए खोजना उतना ही तेज़ है जितना किसी एक रिकॉर्ड को ढूँढ़ना।<ref>
ध्यान रखें कि [[Special:MyLanguage/Manual:Tagline (Site Subtitle)|टैगलाइन]] सामग्री का हिस्सा नहीं है।
किसी पृष्ठ पर खोजने योग्य सामग्री देखने के लिए URL पर <kbd>?action=cirrusdump</kbd> जोड़ दें।
</ref>
इसके अलावा, शब्दों में किसी बदलाव के मामले में खोज इण्डेक्स को कुछ ही सेकंड में अपडेट कर लिया जाता है।

विकि के "पूरे टेक्स्ट" के कई इण्डेक्स हैं जिनसे अलग-अलग प्रकार के खोज किए जा सकते हैं।
पूरे विकिटेक्स्ट को कई बार कई सारे विशेष-उद्देश्य इण्डेक्सों में इण्डेक्स किया जाता है, जिनमें से हर इण्डेक्स विकिटेक्स्ट को इस तरह से पार्स करता है कि उसके इस्तेमाल को ऑप्टिमाइज़ किया जा सके।
उदाहरण के कुछ इण्डेक्स हैं:

<div lang="en" dir="ltr" class="mw-content-ltr">
* "auxiliary" text, includes hatnotes, captions, ToC, and any wikitext classed by an HTML attribute <kbd>class=searchaux</kbd>.
* "Lead-in" text is the wikitext between the top of the page and the first heading.
* The "category" text indexes the listings at the bottom.
* Templates are indexed. If the transcluded words of a template change, then all the pages that transclude it are updated. (This can take a long time depending on a job queue.) If the subtemplates used by a template change, the index is updated.
* Document contents that are stored in the File/Media namespace are now indexed. Thousands of formats are recognized.
</div>

<span lang="en" dir="ltr" class="mw-content-ltr">There is support for dozens of languages, but all languages are wanted.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">There is a list of currently supported languages at [https://www.elastic.co/guide/en/elasticsearch/reference/current/analysis-lang-analyzer.html elasticsearch.org]; see their [https://www.elastic.co/elasticon/conf/2016/sf/contributing-to-elasticsearch-how-to-get-started documentation on contributing] to submit requests or patches.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Third-party open-source libraries are also used to support additional languages not covered by Elasticsearch.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
CirrusSearch will optimize your query, and run it. The resulting titles are weighted by relevance, and heavily post-processed, 20 at a time, for the search results page. For example snippets are garnered from the article, and search terms are highlighted in bold text.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Search results will often be accompanied by various preliminary reports. These include ''Did you mean'' (spelling correction), and, when no results would otherwise be found it will say ''Showing results for'' (query correction) and ''search instead for'' (your query).
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Search features also include:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* Sorting navigation suggestions by the number of incoming links.
* Starting with the tilde character <code>~</code> to disable navigation and suggestions in such a way that also preserves page ranking.
* Smart-matching characters by normalizing (or "folding") non-keyboard characters into keyboard characters.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Words and phrases that match are highlighted in bold on the search results page. The highlighter is a cosmetic analyzer, while the search-indexing analyzer actually finds the page, and these may not be 100% in sync, especially for regex. The highlighter can match more or less accurately than the indexer.
</div>

{{anchor|Words.2C_phrases.2C_and_modifiers}}
<span id="Words,_phrases,_and_modifiers"></span>
=== शब्द, वाक्यांश और संशोधक ===
खोज का एक बुनियादी शब्द है कोई साधारण शब्द या फिर "उद्धरणों चिह्नों में कोई वाक्यांश"।
विस्तार भाषा पर निर्भर है, खासकर कि बिना रिक्त स्थानों वाली भाषाओं में, जहाँ एक "शब्द" का मतलब होता है:

* अंकों का एक स्ट्रिंग
* अक्षरों का एक स्ट्रिंग
* अक्षर/अंक बदलावों के बीच उप-शब्द, जैसे <kbd>txt2regex</kbd> में
* एक compoundName के अंदर [[w:CamelCase|camelCase]] में उप-शब्द

एक "थाम शब्द" वह शब्द है जो अनदेखा कर दिया जाता है (क्योंकि शायद यह काफ़ी साधारण हो, या फिर दूसरे कारणों से)।
थाम शब्दों की सूची भाषा पर निर्भर है और सभी भाषाओं पर थाम शब्द समर्थित नहीं हैं।<ref>थाम शब्दों को CirrusSearch पर शायद ही कभी खोजा जाता है, अगर वे किसी वाक्यांश में न हों, जिसका उदाहरण नीचे दिया गया है।</ref> हर खोज शब्द का मिलान सामग्री के साथ किया जाता है (जो पृष्ठ पर रेंडर होता है)। विकिटेक्स्ट के साथ मिलान करने के लिए <kbd>insource</kbd> खोज पैरामीटर का इस्तेमाल करें (नीचे [[#Insource|अनुभाग]] देखें)। हर खोज पैरामीटर का अपना इनडेक्स है, और यह अपने दिए हुए शब्द अपने तरीके से विवेचन करता है।<ref>CirrusSearch के पैरामीटरों के पास इन खोज शब्दों को हैंडल करने का कोई संगत तरीका नहीं है।</ref> 

शब्दों, वाक्यांशों, पैरामीटरों, और पैरामीटरों के इनपुट के बीच वाइटस्पेस या ग्रेस्पेस अक्षर हो सकते हैं।
"ग्रेस्पेस अक्षर" गैर-अक्षरांकीय अक्षर <kbd>~!@#$%^&()_+-={}|[]\:";'<>?,./</kbd> हैं।
ग्रोस्पेस अक्षरों और वाइटस्पेस अक्षरों के मिश्रित स्ट्रिंग को "ग्रेस्पेस" कहा जाता है और इसे एक ही शब्द माना जाता है।
ग्रेस्पेस से इनडेक्स बनाए जाते हैं और क्वेरीज़ का विवेचन किया जाता है।<ref><span lang="en" dir="ltr" class="mw-content-ltr">[https://www.elastic.co/guide/en/elasticsearch/reference/current/analysis-analyzers.html The same analyzer] used to index the wikitext is also used to interpret the query.</span></ref>

<div lang="en" dir="ltr" class="mw-content-ltr">
Two exceptions are where 1) an <kbd>embedded:colon</kbd> is one word (it being treated as a letter), and 2) an embedded comma <kbd>,</kbd> such as in <kbd>1,2,3</kbd>, is treated as a number.
Greyspace characters are otherwise ignored unless, due to query syntax, they can be interpreted as modifier characters.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The modifiers are <kbd>~ * \? - " ! </kbd>. Depending on their placement in the syntax they can apply to a term, a parameter, or to an entire query. Word and phrase modifiers are the wildcard, proximity, and fuzzy searches. Each parameter can have their own modifiers, but in general:
</div>

* <span lang="en" dir="ltr" class="mw-content-ltr">A fuzzy-word or fuzzy-phrase search can suffix a tilde <code>~</code> character (and a number telling the degree).</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">A tilde <code>~</code> character prefixed to the first term of a query guarantees search results instead of any possible navigation.</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">A wildcard character inside a word can be an (escaped) question mark \? for one character or an asterisk <kbd>*</kbd> character for zero or more characters.</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">Truth-logic can interpret <kbd>AND</kbd> and <kbd>OR</kbd>, but parameters cannot. Note that the <kbd>AND</kbd> and <kbd>OR</kbd> operators currently '''do not function in the traditional truth-logic manner!''' For details see more on [[Special:MyLanguage/Help:CirrusSearch/Logical operators|logical operators]].</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">Truth-logic understands <kbd>-</kbd> or <kbd>!</kbd> prefixed to a term to invert the usual meaning of the term from "match" to "exclude".</span>
{{tip|1=<span lang="en" dir="ltr" class="mw-content-ltr">Words that begin with <kbd>-</kbd> or <kbd>!</kbd>, such as <kbd>-in-law</kbd> or <kbd>!Kung</kbd> can exactly match titles and redirects, but will also match every document that does ''not'' contain the negated word, which is usually almost all documents.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To search for such terms other than as exact matches for titles or redirects, use the <kbd>insource</kbd> search parameter (See [[#Insource|section]] below).</span>}}
* <span lang="en" dir="ltr" class="mw-content-ltr">Quotes around words mark an "exact phrase" search. For parameters they are also needed to delimit multi-word input.</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">Stemming is automatic but can be turned off using an "exact phrase".</span>

{{tip|1=<span lang="en" dir="ltr" class="mw-content-ltr">The two wildcard characters are the star and the (escaped) question mark, and both can come in the middle or end of a word.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The escaped question mark <kbd>\?</kbd> stands for one character and the star <kbd>*</kbd> stands for any number of characters.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Because many users, instead of writing a query, will ask a question, any question mark is ignored unless purposefully escaped <kbd>\?</kbd> into its wildcard meaning.</span>}}

<div lang="en" dir="ltr" class="mw-content-ltr">
A phrase search can be initiated by various hints to the search engine. Each method of hinting has a side-effect of how tolerant the matching of the word sequence will be. For ''greyspace'', ''camelCase'', or ''txt2number'' hints:
</div>

* <span lang="en" dir="ltr" class="mw-content-ltr">given <kbd>words-joined_by_greyspace(characters)</kbd> or <kbd>wordsJoinedByCamelCaseCharacters</kbd> it finds <kbd>words joined by</kbd> ... <kbd>characters</kbd>, in their bare forms or greyspace forms.</span>
* <span lang="en" dir="ltr" class="mw-content-ltr"><kbd>txt2number</kbd> will match <code>txt 2 number</code> or <code>txt-2.number</code>.</span> 
* <span lang="en" dir="ltr" class="mw-content-ltr">Stop words are enabled for the edge cases (in the periphery) of a grey_space or camelCase phrase.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An example using <kbd>the</kbd>, <kbd>of</kbd>, and <kbd>a</kbd> is that <kbd>the_invisible_hand_of_a</kbd> matches <code>invisible hand</code> within the text <code>meetings invisible hand shake</code>.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
A "search instead" report is triggered when a universally unknown word is ignored in a phrase.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Each one of the following types of phrase-matching contains and widens the match-tolerances of the previous one:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* An "exact phrase" "in quotes" will tolerate (match with) greyspace. Given <kbd>"exact_phrase"</kbd> or <kbd>"exact phrase"</kbd> it matches <code>"exact]phrase"</code>.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* A greyspace_phrase initiates stemming and ''stop word'' checks.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Given <kbd>CamelCase</kbd> it will ''additionally'' match <code>camelcase</code>, in all lowercase, because CirrusSearch is not case sensitive in matching.
</div> <span lang="en" dir="ltr" class="mw-content-ltr">Note that <kbd>CamelCase</kbd> matching is not enabled for all languages.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
Some parameters interpret greyspace phrases, but other parameters, like <code>insource</code> only interpret the usual "phrase in quotes".
</div>

{{tip|1=<span lang="en" dir="ltr" class="mw-content-ltr">In search terminology, support for "stemming" means that a search for "swim" will also include "swimming" and "swimmed", but may not include irregular forms like "swam".</span>}}

{| class=wikitable
! <span lang="en" dir="ltr" class="mw-content-ltr">Search phrase</span>
! parserfunction !! parserFunction !! parser function !! parser-function !! parser:function !! parSer:funcTion 
|-
| parserfunction || {{tick}} || {{tick}} || {{cross}} || {{cross}} || {{cross}} || {{cross}} 
|-
| "parser function" || {{cross}} || {{cross}} || {{tick}} || {{tick}} || {{cross}} || {{cross}} 
|-
| parser_function || {{cross}} || {{tick}} || {{tick}} || {{tick}} || {{cross}} || {{cross}} 
|-
| parserFunction || {{tick}} || {{tick}} || {{tick}} || {{tick}} || {{cross}} || {{cross}} 
|-
| "parser:function" || {{cross}} || {{cross}} || {{cross}} || {{cross}} || {{tick}} || {{tick}} 
|-
| "parser_function" || {{cross}} || {{cross}} || {{tick}} || {{tick}} || {{cross}} || {{cross}} 
|-
| "parSer_funcTion" || {{cross}} || {{cross}} || {{tick}} || {{tick}} || {{cross}} || {{cross}} 
|-
| parSer_FuncTion || {{cross}} || {{cross}} || {{tick}} || {{tick}} || {{tick}} || {{tick}} 
|}
<div lang="en" dir="ltr" class="mw-content-ltr">
Note that all stemming is case insensitive.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Note how the "exact phrase" search interpreted the <kbd>embedded:colon</kbd> character as a letter, but not the <kbd>embedded_underscore</kbd> character. A similar event occurs with the comma <kbd>,</kbd> character inside a number.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Given <code>in:this:word</code>, CirrusSearch, when in an "exact phrase" context, (which includes the ''insource'' parameter context), will not match <code>in</code>, <code>this</code>, or <code>word</code>, but will then only match <code>in:this:word</code>.
</div>

वरना, याद रखें कि CirrusSearch पर '''शब्दों का मतलब है अक्षर, अंक, या फिर दोनों का मिश्रण, और यह छोटे या बड़े अक्षरों में भेद नहीं करता'''। 

<div lang="en" dir="ltr" class="mw-content-ltr">
The common word search employs the space character and is aggressive with stemming, and when the same words are joined by greyspace characters or camelCase they are aggressive with phrases and subwords.
</div> 

<div lang="en" dir="ltr" class="mw-content-ltr">
When common words like "of" or "the" are included in a greyspace-phrase, they are ignored, so as to match more aggressively.
</div>

<span lang="en" dir="ltr" class="mw-content-ltr">A greyspace_phrase search term, or a camelCase, or a txt2number term, match the signified words interchangeably. You can use any of those three forms.</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">For example, common terms on this wiki, MediaWiki.org, are, redundantly, (searched):</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
* udp2log ''or'' udp2log2 (though the extra 2 will affect ranking)
* html2wt ''or'' wt2html
* log2ip ''or'' ip2log
There's test2wiki, wiki2xml, wiki2dict, apache2handler, apache2ctl, etc.
</div>
</ref>
<span lang="en" dir="ltr" class="mw-content-ltr">Now <kbd>camelcase</kbd> matches <kbd>camelCase</kbd> because Search is not case sensitive, but <kbd>camelCase</kbd> matches <kbd>camelcase</kbd> because camelCase is more aggressive.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Like the rest of Search, subword "words" are not case-sensitive. By comparison the "exact phrase" is greyspace oriented and ignores numeric or letter-case transitions, and stemming. "Quoted phrases" are not case sensitive.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
From the table we can surmise that the basic search <kbd>parser_function -"parser function"</kbd> is the sum of the basic searches <code>parserFunction</code> and <code>parser&lt;stems> function&lt;stems></code>.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Making inquiries with numbers, we would find that:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* <kbd>Plan9</kbd> or <kbd>Plan_9</kbd> matches any of: <code>plan9</code>, <code>plans 9</code>, <code>planned 9th</code>, <code>(planned) 9.2</code>, <code>"plans" (9:24)</code>
* <kbd>"plan9"</kbd> only matches <code>plan9</code> (case insensitive)
* <kbd>Plan*9</kbd> matches <code>plan9</code> or <code>planet4589</code>.
</div>

<span lang="en" dir="ltr" class="mw-content-ltr">The star <kbd>*</kbd> wildcard matches a string of letters and digits within a rendered word, ''but never the beginning character''.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">One or more characters must precede the <kbd>*</kbd> character.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
* When <kbd>*</kbd> matches numbers, a comma is considered part of one number, but the decimal point is considered a greyspace character, and will delimit two numbers.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Inside an "exact phrase" <kbd>*</kbd> is treated as a greyspace character and not a wild card character, so it delimits words.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The <kbd>\?</kbd> wildcard represents one letter or number; <kbd>*\?</kbd> is also accepted, but <kbd>\?*</kbd> is not recognized.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The wildcards are for basic word, phrase, and insource searches, and may also be an alternative to (some) advanced regex searches (covered later).
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Putting a tilde <kbd>~</kbd> character after a word or phrase activates a fuzzy search.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* For a phrase it is termed a ''proximity'' search, because ''proximal'' words are tolerated to an approximate rather than ''exact phrase''.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* For example, <kbd>"exact one two phrase"~2</kbd> matches <code>exact phrase</code>.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* For a word it means extra characters or ''changed'' characters.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* For a phrase a fuzzy search ''requires'' a whole number telling it how many extra words to fit in, but for a word a fuzzy search can have a decimal fraction, ''defaulting'' to <kbd>word~0.5</kbd> (<kbd>word~.5</kbd>), where at most two letters can be found swapped, changed, or added, but never the first two letters.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* For a proximity phrase, a large number can be used, but that is an "expensive" (slow) search.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* For a word <kbd>word~2</kbd> is most fuzzy with an edit distance of 2 (default), and <kbd>word~1</kbd> is least fuzzy, and <kbd>word~0</kbd> is not fuzzy at all.
</div>

{| style="text-align: center;" class="wikitable"
| ||flowers algernon||Flowers for Algernon||flowers are for Algernon||Flowers a1 2b 3c 4f 5j 6l 7j 8p q9 z10 for Algernon
|-
|"flowers algernon"||{{Tick}}||{{Cross}}||{{Cross}}||{{Cross}}
|-
|"flowers algernon"~0||{{Tick}}||{{Cross}}||{{Cross}}||{{Cross}}
|-
|"flowers algernon"~1||{{Tick}}||{{Tick}}||{{Cross}}||{{Cross}}
|-
|"flowers algernon"~2||{{Tick}}||{{Tick}}||{{Tick}}||{{Cross}}
|-
|"flowers algernon"~11||{{Tick}}||{{Tick}}||{{Tick}}||{{Tick}}
|-
|"algernon flowers"~1||{{Cross}}||{{Cross}}||{{Cross}}||{{Cross}}
|-
|"algernon flowers"~2||{{Tick}}||{{Cross}}||{{Cross}}||{{Cross}}
|-
|"algernon flowers"~3||{{Tick}}||{{Tick}}||{{Cross}}||{{Cross}}
|-
| "algernon flowers"~4||{{Tick}}||{{Tick}}||{{Tick}}||{{Cross}}
|-
|"algernon flowers"~13||{{Tick}}||{{Tick}}||{{Tick}}||{{Tick}}
|}

<span lang="en" dir="ltr" class="mw-content-ltr">For the closeness value necessary to match in reverse (right to left) order, count and discard all the extra words, then add twice the total count of remaining words minus one.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">(In other words, add twice the number of segments).</span>
<span lang="en" dir="ltr" class="mw-content-ltr">For the full proximity algorithm, see [https://www.elastic.co/guide/en/elasticsearch/guide/current/slop.html Elasticsearch slop].</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
Quotes turn off stemming, <kbd>"but appending"~</kbd> the tilde reactivates the stemming.
</div>

{| style="text-align: center;" class="wikitable" 
| ||flowers||flower||Flowers for Algernon||flower for Algernon 
|
|- 
|flowers ||{{Tick}}||{{Tick}}||{{Tick}}||{{Tick}} 
| <span lang="en" dir="ltr" class="mw-content-ltr">Stemming is in effect.</span>
|- 
|"flowers"||{{Tick}}||{{Cross}}||{{Tick}}||{{Cross}} 
| <span lang="en" dir="ltr" class="mw-content-ltr">Proximity search turns off stemming.</span> 
|- 
|"flowers"~||{{Tick}}||{{Tick}}||{{Tick}}||{{Tick}} 
| <span lang="en" dir="ltr" class="mw-content-ltr">Proximity plus stemming by suffixing a tilde.</span> 
|- 
|"flowers for algernon"||{{Cross}}||{{Cross}}||{{Tick}}||{{Cross}}
| <span lang="en" dir="ltr" class="mw-content-ltr">Proximity search turns off stemming.</span> 
|- 
|style=white-space:nowrap|"flowers for algernon"~||{{Cross}}||{{Cross}}||{{Tick}}||{{Tick}} 
| <span lang="en" dir="ltr" class="mw-content-ltr">Proximity plus stemming by suffixing a tilde.</span> 
|- 
|"flowers algernon"~1||{{Cross}}||{{Cross}}||{{Tick}}||{{Cross}} 
| <span lang="en" dir="ltr" class="mw-content-ltr">Proximity search turns off stemming.</span> 
|- 
|style=white-space:nowrap|"flowers algernon"~1~||{{Cross}}||{{Cross}}||{{Tick}}||{{Tick}} 
| <span lang="en" dir="ltr" class="mw-content-ltr">Proximity plus stemming by suffixing a tilde.</span> 
|}

<div lang="en" dir="ltr" class="mw-content-ltr">
==== Insource ====
</div>
{{MW version|version=1.24|compact=y|comment=and after|gerrit change=137733}}

<div lang="en" dir="ltr" class="mw-content-ltr">
Insource searches can be used to find any one ''word'' rendered on a page, but it's made for finding any phrase you might find - including [[Wikitext|MediaWiki markup]] (aka wikicode), on any page except redirects. This phrase completely ignores greyspace: <kbd>insource: "state state autocollapse"</kbd> matches <code>|state=<nowiki>{{{state|autocollapse}}}</nowiki></code>.
</div>

{| class="wikitable" style="background-color:white"
|<kbd>insource:&nbsp;word</kbd><br /><kbd>insource:&nbsp;"''word1''&nbsp;''word2''"</kbd>
| <span lang="en" dir="ltr" class="mw-content-ltr">Greyspace characters are ignored, just as they are with word searches and exact-phrase searches.</span>
|-
|<kbd>insource:/''regexp''/</kbd><br /><kbd>insource:/''regexp''/i</kbd>
| <span lang="en" dir="ltr" class="mw-content-ltr">These are [[w:regular expression|regular expressions]]. They aren't efficient, so only a few are allowed at a time on the search cluster, but they are very powerful. The regular expression matches case-sensitively by default; case-insensitivity can be opted in with the extra <code>i</code>, which is even less efficient.</span>
|}

<span lang="en" dir="ltr" class="mw-content-ltr">Insource complements itself. On the one hand it has full text search for any word in the wikitext, instantly. On the other hand it can process a regexp search for any string of characters.</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">CirrusSearch regex do not address the newline character directly, but a dot <kbd>.</kbd> will match a newline.</span></ref>
<span lang="en" dir="ltr" class="mw-content-ltr">Regexes scan all the textual characters in a given list of pages; they don't have a word index to speed things up, and the process is interrupted if it runs for more than twenty seconds.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Regexes run last in a query, so to limit needless character-level scanning, every regex query should include other search terms to limit the number of documents that need to be scanned.</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">A slow regex search cannot disable search, but can disable another's regex search, since there are only a limited number of regex searches allowed at a time.</span></ref>
<span lang="en" dir="ltr" class="mw-content-ltr">Often the best candidate to add to the regex query <kbd>insource:/''arg''/</kbd> is <kbd>insource:''arg''</kbd>, where ''arg'' is the same (and uses no wildcards).</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
The syntax for the regexp is <kbd>insource:</kbd> no space, and then <kbd>/''regexp''/</kbd>. (No other parameter disallows a space. All the parameters except <kbd>insource:/''regexp''/</kbd> accept space after their colon.)
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Insource indexed-search and regexp-search roles are similar in many respects:
</div> 

<div lang="en" dir="ltr" class="mw-content-ltr">
* Both search wikitext only. 
* Neither finds things "sourced" by a [[Special:MyLanguage/Help:Transclusion|transclusion]].
* Neither does stemmed, fuzzy, or proximity searches.
* Both want the fewest results, and both work faster when accompanied by another clause.
</div>

<span lang="en" dir="ltr" class="mw-content-ltr">But indexed searches all ignore greyspace; wildcards searches do not match greyspace, so regexes are the only way to find an exact string of ''any and all'' characters, for example a sequence of two spaces.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Regexes are an entirely different class of search tool that make matching a literal string easy (basic, beginner use), and make matching by metacharacter expressions possible (advanced use) on the wiki.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">See [[#Regular expression searches|#Regular expression searches]] below.</span>

{{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">The ''insource'' parameter treats words with embedded colons as one word. This affects search queries for templates, parser functions, URLs, wikilinks, HTML tags, and comments.</span>}}

{{tip|1=<span lang="en" dir="ltr" class="mw-content-ltr">When possible, please avoid running a bare regexp search. See how this is always possible at [[#Regular expression searches|#Regular expression searches]], below.</span>}}

{{tip|1=<span lang="en" dir="ltr" class="mw-content-ltr">To search for words that begin with <kbd>-</kbd> or <kbd>!</kbd>, such as <kbd>-in-law</kbd> or <kbd>!Kung</kbd>, use a case-insensitive <kbd>insource</kbd> query together with a simple search on the "plain" version of the term (to avoid a bare regexp search). For example, <code>"in-law" insource:/-in-law/i</code> or <code>"kung" insource:/!kung/i</code>.</span>}}

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Prefix and namespace ===
</div> 
<span lang="en" dir="ltr" class="mw-content-ltr">Prepending a namespace term like <code>file:</code> to a search query limits results to a specific {{ll|Manual:Namespace|namespace}}, instead of searching the entire wiki.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">The default namespace is "Main".</span>

<span lang="en" dir="ltr" class="mw-content-ltr">Only one namespace name can be set from the search box query.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">It must be the '''first''' term in the query, or, if used as part of a <code>[[#prefix:|prefix:]]</code> term, must appear as the '''last''' term in the query.</span>

<span lang="en" dir="ltr" class="mw-content-ltr">Two or more namespaces may be searched from the ''Advanced'' pane of the '''search bar''' found on the top of every search results page, [[Special:Search]].</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Your search domain, as a profile of namespaces, can be set here.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">The namespaces list will then present itself on the first page of future search results to indicate the search domain of the search results.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">To unset this, select the default namespace (shown in parentheses), select "Remember", and press Search.</span>

<span lang="en" dir="ltr" class="mw-content-ltr">The '''search bar''' graphically sets and indicates a search domain. "Content pages" (mainspace), "Multimedia" (File), "Everything" (''all'' plus File), "Translations", etc., are hyperlinks that can activate the query in that domain, and then indicate this by going inactive (dark). But the query will override the search bar.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">When a namespace or prefix is used in the query the search bar activations and indications may be misleading, so the search bar and the search box are mutually exclusive (not complementary) ways to set the search domain.</span>
<!-- I think I understand that the 'prefix:' and namespace terms make search box and other search controls not necessarily reflect the actual *parameters* applied, but this paragraph does not explain that in a comprehensible way. I'm not sure I understand what's trying to be conveyed here enough to fix it. -->

<div lang="en" dir="ltr" class="mw-content-ltr">
A namespace term overrides the search bar, and a <code>prefix:</code> term overrides a namespace.
</div>

<span lang="en" dir="ltr" class="mw-content-ltr">To specify a namespace name, prefix it with a colon, ''e.g.'', <code>talk:</code>.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Use <code>all:</code> to search across ''all'' namespaces, or '''<big><code>:</code></big>''' (a single colon) to search just the main article namespace.</span>

<span lang="en" dir="ltr" class="mw-content-ltr">The <code>all:</code> term does not include the File: namespace, which includes media content held at Commons such as PDF, which are all indexed and searchable.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">When File is involved, a namespace modifier <code>local:</code> has an effect, otherwise it is ignored.</span>
<!-- not even sure what this means; can it be re-worded? -->

<span lang="en" dir="ltr" class="mw-content-ltr">As with search parameters, <code>local:</code> and <code>all:</code> must be lowercase.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Namespaces names, though, are case insensitive.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{ll|Manual:$wgNamespaceAliases|Namespace aliases}} are accepted.
</div>

{|class=wikitable style=background-color:white
| <kbd>talk: "Wind clock"</kbd>
| <span lang="en" dir="ltr" class="mw-content-ltr">Find pages in the '''Talk''' namespace whose title or text contains the phrase "wind clock".</span>
|-
| <kbd>file: "Wind clock"</kbd>
| <span lang="en" dir="ltr" class="mw-content-ltr">Find pages in '''File''' namespace, whose title, text, or media content contains the phrase "wind clock".</span>
|-
| style="white-space:nowrap"| <kbd>file: local: "Wind clock"</kbd>
| <span lang="en" dir="ltr" class="mw-content-ltr">Filter out results from Commons wiki.</span>
|-
| <kbd>local: "Wind clock"</kbd>
| <span lang="en" dir="ltr" class="mw-content-ltr">Ignored.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Searches mainspace. Local is ignored unless File is involved.</span>
|}

==== <code>prefix:</code> ====

<span lang="en" dir="ltr" class="mw-content-ltr">The <code>prefix:</code> parameter matches any number of first-characters of all pagenames in one namespace.</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">Prefix does not match on first-characters of fullpagenames, so you cannot search two namespaces at once just because they start with the same letters, such as both ''namespace'' and ''namespace talk'' in one query.</span></ref>
<span lang="en" dir="ltr" class="mw-content-ltr">When the first letters match a namespace name and colon, the search domain changes.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
Given a namespace only, <code>prefix:</code> will match all its pagenames. Given one character only, it cannot be <code>-</code> (dash), <code>'</code> (quote), or <code>"</code> (double quote). The last character cannot be a colon.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
For pagenames that match, their subpage titles match by definition.
</div> 

<span lang="en" dir="ltr" class="mw-content-ltr">The <code>prefix:</code> parameter does not allow a space before a namespace, but allows whitespace before a pagename.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">This term '''always goes at the end''', so that pagename characters may contain quotation marks (<code>"</code>).</span>

{| class="wikitable" style=background-color:white
|-
| <kbd>prefix:</kbd><kbd>cow</kbd>
| <span lang="en" dir="ltr" class="mw-content-ltr">Find pages in mainspace whose title starts with the three letters <kbd>c o w</kbd>.</span>
|-
| <kbd>domestic</kbd>&nbsp;&nbsp;&nbsp;<kbd>prefix:</kbd><kbd>cow</kbd>
| <span lang="en" dir="ltr" class="mw-content-ltr">Find pages in mainspace whose title starts with the three letters <kbd>c o w</kbd>, and that contain the word "<kbd>domestic</kbd>".</span>
|-
| <kbd>domestic</kbd>&nbsp;&nbsp;&nbsp;<kbd>prefix:</kbd><kbd>cow/</kbd>
| <span lang="en" dir="ltr" class="mw-content-ltr">List any existing subpages of ''Cow'' but only if they contain the word "domestic".</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is a very common search and is frequently built using a special URL parameter called <kbd>prefix=</kbd>.</span>
|-
| style=" white-space:nowrap;"|<kbd>domestic</kbd>&nbsp;&nbsp;&nbsp;<kbd>prefix:</kbd><kbd>Talk:cow</kbd>/
| <span lang="en" dir="ltr" class="mw-content-ltr">List any subpages of ''Talk:cow'', but only if they contain the word "domestic".</span>
|-
| style=white-space:nowrap | <kbd>1967</kbd>&nbsp;&nbsp;&nbsp;<kbd>prefix:</kbd><kbd>Pink Floyd</kbd>/
| <span lang="en" dir="ltr" class="mw-content-ltr">List any subpages of ''Pink Floyd'', but only if it also contains the word "1967".</span>
|}

<span lang="en" dir="ltr" class="mw-content-ltr">The [[Special:MyLanguage/Extension:Translate|Translate extension]] creates a sort of "language namespace" of translated versions of a page.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">However, unlike namespace or prefix, which create the initial search domain, the <kbd>inlanguage</kbd> parameter is a ''filter'' of it. (See the next section.)</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Exclude content from the search index ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Content can be excluded from the search index by adding <code>class="navigation-not-searchable"</code>. This will instruct CirrusSearch to ignore this content from the search index (see {{phab|T162905}} for more context).
</div>

<span lang="en" dir="ltr" class="mw-content-ltr">Additionally content can be marked as auxiliary information by adding <code>class="searchaux"</code>.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">This will instruct CirrusSearch to move the content from the main text to an auxiliary field which has lower importance for search and snippet highlighting.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">This distinction is used for items such as image thumbnail descriptions, 'see also' sections, etc.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Filters ==
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">A filter will have multiple instances, or negated instances, or it can run as a standalone filtering a search domain.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">A query is formed as terms that filter a search domain.</span>

<span lang="en" dir="ltr" class="mw-content-ltr">Adding another word, phrase, or parameter filters more. A highly refined search result may have very many Y/N filters when every page in the results will be addressed. (In this case ranking is largely irrelevant.)</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Filtering applies critically to adding a regex term; you want as few pages as possible before adding a regex (because it can never have a prepared index for its search).</span>

<span lang="en" dir="ltr" class="mw-content-ltr">A namespace is a specified search domain but not a filter because a namespace will not run standalone.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">A ''prefix'' will negate so it is a filter.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">The search parameters below are filters for which there may be multiple instances.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
''Insource'' (covered above) is also a filter, but <kbd>insource:/''regexp''/</kbd> is not a filter. Filters and all other search parameters are lowercase. (Namespaces are an exception, being case insensitive.)
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Intitle and incategory ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Word and phrase searches match in a title and match in the category box on bottom of the page. But with these parameters you can select titles ''only'' or category ''only''.
</div>
* <kbd>cow*</kbd>
<div lang="en" dir="ltr" class="mw-content-ltr">
**Find articles whose title or text contains words that start with cow
</div>
* <kbd>intitle:foo</kbd>
<div lang="en" dir="ltr" class="mw-content-ltr">
**Find articles whose title contains foo. Stemming is enabled for foo.
</div>
* <kbd>intitle:"fine line"</kbd>
<div lang="en" dir="ltr" class="mw-content-ltr">
** Find articles whose title contains ''fine line''. Stemming is disabled.
</div>
* <kbd>intitle:foo bar</kbd>
<div lang="en" dir="ltr" class="mw-content-ltr">
** Find articles whose title contains foo and whose title or text contains bar.
</div>
* <kbd>-intitle:foo bar</kbd>
<div lang="en" dir="ltr" class="mw-content-ltr">
** Find articles whose title does not contain foo and whose title or text contains bar.
</div>
* <kbd>incategory:Music</kbd>
<div lang="en" dir="ltr" class="mw-content-ltr">
** Find articles that are in Category:Music
</div>
* <kbd>incategory:"music history"</kbd>
<div lang="en" dir="ltr" class="mw-content-ltr">
** Find articles that are in Category:Music_history
</div>
* <kbd>incategory:"musicals" incategory:"1920"</kbd>
<div lang="en" dir="ltr" class="mw-content-ltr">
** Find articles that are in both Category:Musicals and Category:1920
</div>
* <kbd>-incategory:"musicals" incategory:"1920"</kbd>
<div lang="en" dir="ltr" class="mw-content-ltr">
** Find articles that are not in Category:Musicals but are in Category:1920
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
''Intitle'' and ''incategory'' are old search parameters. Incategory no longer searches any subcategory automatically, but you can now add multiple category pagenames manually.
</div>

{{MW version|version=1.31|compact=y|comment=and after|gerrit change=413896}}
<div lang="en" dir="ltr" class="mw-content-ltr">
Since {{ll|MediaWiki 1.31/wmf.23|MediaWiki 1.31-wmf.23}} Regular expression searches are supported for intitle:
</div>
: <kbd>intitle:/regex/, intitle:/regex/i</kbd>

<div lang="en" dir="ltr" class="mw-content-ltr">
Everything written in the [[#Regular expression searches|#Regular expression searches]] is also valid for these searches, including warnings.
</div>

{{tip|1=<span lang="en" dir="ltr" class="mw-content-ltr">When possible, please avoid running a bare regexp search. See how this is always possible at [[#Regular expression searches|#Regular expression searches]], below.</span>}}

=== Deepcategory ===
<div lang="en" dir="ltr" class="mw-content-ltr">
Deep category search allows to search in category and all subcategories. The depth of the tree is limited by 5 levels currently (configurable) and the number of categories is limited by 256 (configurable). The deep search uses [[Special:MyLanguage/Wikidata Query Service/Categories|SPARQL Category service from WDQS]]. Keywords are ''deepcategory'' or ''deepcat''. Example:
</div>

* <kbd>deepcat:"musicals"</kbd>
<div lang="en" dir="ltr" class="mw-content-ltr">
** Find articles that are in Category:Musicals or any of the subcategories.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The DeepCat gadget that previously implemented the parameter was sunsetted in January 2020.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Linksto ===
</div> 

<div lang="en" dir="ltr" class="mw-content-ltr">
''Linksto'' finds wikilinks to a given ''name'', not links to ''content''. The input is the canonical, case sensitive, page ''name''.
It must match the title line of the content page, exactly, before any title modifications of the letter-case. (It must match its {<nowiki/>{FULLPAGENAME}}, e.g. {{FULLPAGENAME}}.)
</div>

<span lang="en" dir="ltr" class="mw-content-ltr">''Linksto'' does not find redirects. It only finds [<nowiki />[wikilinks]], even when they are made by a template.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">It does not find a link made by a URL, even if that URL is an internal wiki link.</span> 

<div lang="en" dir="ltr" class="mw-content-ltr">
To find all wikilinks to a "Help:Cirrus Search", if "Help:Searching" and "H:S" are redirects to it:
</div>
# linksto: "Help:Cirrus Search"
# linksto: Help:Searching
# linksto: H:S

<div lang="en" dir="ltr" class="mw-content-ltr">
<code>CirrusSearch -linksto: Help:CirrusSearch</code> finds articles that mention "CirrusSearch" but not in a wikilink.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Hastemplate ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
You can specify template usage with <code>hastemplate: ''template''</code>. Input the canonical pagename to find ''all usage'' of the template, but use any of its redirect pagenames finds ''just that naming''. Namespace aliases are accepted, capitalization is entirely ignored, and redirects are found, all in one name-search. (Compare ''boost-template'' no default namespace; ''linksto'' no namespace aliases, case-sensitive, no redirects; ''intitle'' no redirects.)
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
''Hastemplate'' finds secondary (or meta-template) usage on a page: it searches the post-expansion inclusion. This is the same philosophy as for ''words and phrases'' from a template, but here it's for ''templates'' from a template. The page will be listed as having that content even though that content is not seen in the wikitext.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* <kbd>hastemplate: "quality image"</kbd>, finds "Template:Quality image" usage in your default search domain (namespaces).
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* <kbd>hastemplate: portal:contents/tocnavbar</kbd>, finds mainspace usage of a "Contents/TOCnavbar" template in the Portal namespace.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
For installations with the Translate extension, ''hastemplate'' searches get interference wherever [[Template:Translatable template name]] wraps the template name of a translatable template. Use ''insource'' instead.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Inlanguage ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
For installations with the Translate extension, <kbd>inlanguage</kbd> is important for highly refined searches and page counts.
</div>

:<kbd>inlanguage: ''<span lang="en" dir="ltr" class="mw-content-ltr">[[w:List of ISO 639-2 codes|language code]]</span>''</kbd>
<div lang="en" dir="ltr" class="mw-content-ltr">
will produce search results in that language only.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
For example
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* to count all Japanese pages on the wiki
</div>
: <kbd>all: inlanguage: ja</kbd>
<div lang="en" dir="ltr" class="mw-content-ltr">
* to filter out German and Spanish pages in the Help namespace
</div>
: <kbd>help: -inlanguage: de -inlanguage: es</kbd>
<div lang="en" dir="ltr" class="mw-content-ltr">
* to ignore Translate, and where English is the base language, add
</div>
: <kbd>inlanguage:en</kbd>

=== Contentmodel ===
<div lang="en" dir="ltr" class="mw-content-ltr">
The <kbd>contentmodel:</kbd> keyword allows to limit the search to pages of a specific content model. For possible models cf. [[Special:MyLanguage/Content handlers|Content handlers]]. E.g.:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* To see only JSON pages:
</div>
: <code>contentmodel:json</code>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== subpageof ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
To find sub-pages.
</div>
:<kbd>subpageof: ''<span lang="en" dir="ltr" class="mw-content-ltr">ParentPage</span>''</kbd>

<div lang="en" dir="ltr" class="mw-content-ltr">
For example
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* To find all subpages of CirrusSearch.
</div>

: <kbd>subpageof:CirrusSearch</kbd>

<div lang="en" dir="ltr" class="mw-content-ltr">
* Use double quotes if the parent page contains spaces.
</div>

: <kbd>subpageof:"Requests for comment"</kbd>

{{note|1=<span lang="en" dir="ltr" class="mw-content-ltr">unlike ''prefix:'', do not include the page namespace in the keyword value. If you want to limit to sub-pages of a particular namespace use the namespace filter.</span>}}

=== Articletopic ===
<span lang="en" dir="ltr" class="mw-content-ltr">The <kbd>articletopic:</kbd> keyword allows filtering search results by topic. For possible topics see {{ll|Help:CirrusSearch/articletopic}}.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">E.g. <kbd>articletopic:books</kbd> will filter the search results to articles about books.</span>
<span lang="en" dir="ltr" class="mw-content-ltr"><kbd>articletopic:books|films</kbd> will filter to articles about books or films.</span>
<span lang="en" dir="ltr" class="mw-content-ltr"><kbd>articletopic:books articletopic:films</kbd> will filter to articles which are about both books and films.</span>

<span lang="en" dir="ltr" class="mw-content-ltr">Only mainspace articles belong into topics, and topics are only available on Wikipedias.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Unlike other filters, articletopic also does page weighting: articles which are a stronger match for a topic will be higher in the search results (while articles which aren't about that subject at all will be removed from the result set completely).</span>

<span lang="en" dir="ltr" class="mw-content-ltr">Topic models are derived via machine learning from [[ORES#Topic routing|ORES]].</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Any given article receives a score on dozens of different topics, and therefore may appear under different keywords.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">For instance, the article on Albert Einstein may appear as a "physics" article and a "biography" article.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">All Wikipedias have scores available -- some have local-language topic models that have coverage on all articles.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Other languages do not have local ORES models, and are using English-language scores assigned to articles in the local language that also exist in English Wikipedia.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">The languages with such "cross-wiki" scores do not have 100% coverage -- depending on the language, it may only be something like 60% of articles that have topics available.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
Topic-related search data is updated weekly, so recently created articles might not show up in topic-based search queries.
</div>

=== Pageid ===
<span lang="en" dir="ltr" class="mw-content-ltr">The <kbd>pageid:</kbd> keyword restricts search results to the given set of page IDs.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">This is not really useful for manual searching; it can be used by software tools for checking whether a set of pages match the given set of search conditions (e.g. for re-validating cached search results).</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Page weighting ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Weighting determines snippet, suggestions, and page relevance. The normal weight is one. Additional weighting is given through multipliers.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If the query is just words, pages that match them in order are given a boost. If you add any ''explicit'' phrases to your search, or for certain other additions, this "prefer phrase" feature is not applied.
</div> 

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Morelike ===
</div> 
* <kbd>morelike:''page name 1''|''page name 2''|...|''page name n''</kbd>
<div lang="en" dir="ltr" class="mw-content-ltr">
** Find articles whose text is most similar to the text of the given articles.
</div>
* <code>morelike:wasp|bee|ant</code>
** <span lang="en" dir="ltr" class="mw-content-ltr">Find articles about stinging insects.</span>
* <code>morelike:template:search|template:regex|template:usage</code>
** <span lang="en" dir="ltr" class="mw-content-ltr">Find templates about regex searching for template usage on the wiki.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
<code>morelike</code> is a "greedy" keyword, meaning that it cannot be combined with other search queries. If you want to use other search queries, use <kbd>morelikethis</kbd> in your search:
</div>

* <code>morelikethis:bee hastemplate:"featured article"</code>
** <span lang="en" dir="ltr" class="mw-content-ltr">Find articles about bees that also have the "featured article" template.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
The <kbd>morelike:</kbd> query works by choosing a set of words in the input articles and run a query with the chosen words. You can tune the way it works by adding the following parameters to the search results URL:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* <kbd>cirrusMltMinDocFreq</kbd>: Minimum number of documents (per shard) that need a term for it to be considered.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* <kbd>cirrusMltMaxDocFreq</kbd>: Maximum number of documents (per shard) that have a term for it to be considered.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* <kbd>cirrusMltMaxQueryTerms</kbd>: Maximum number of terms to be considered.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* <kbd>cirrusMltMinTermFreq</kbd>: Minimum number of times the term appears in the input to doc to be considered. For small fields (<kbd>title</kbd>) this value should be 1.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* <kbd>cirrusMltMinWordLength</kbd>: Minimal length of a term to be considered. Defaults to 0.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* <kbd>cirrusMltMaxWordLength</kbd>: The maximum word length above which words will be ignored. Defaults to unbounded (0).
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* <kbd>cirrusMltFields</kbd> (comma separated list of values): These are the fields to use. Allowed fields are <kbd>title</kbd>, <kbd>text</kbd>, <kbd>auxiliary_text</kbd>, <kbd>opening_text</kbd>, <kbd>headings</kbd> and <kbd>all</kbd>.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* <kbd>cirrusMltUseFields</kbd> (<code>true</code>|<code>false</code>): use only the field data. Defaults to <code>false</code>: the system will extract the content of the <code>text</code> field to build the query.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* <kbd>cirrusMltPercentTermsToMatch</kbd>: The percentage of terms to match on. Defaults to 0.3 (30 percent).
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Example: <syntaxhighlight lang="text">&cirrusMtlUseFields=yes&cirrusMltFields=title&cirrusMltMinTermFreq=1&cirrusMltMinDocFreq=1&cirrusMltMinWordLength=2</syntaxhighlight>
These settings can be made persistent by overriding <code>cirrussearch-morelikethis-settings</code> in [[Special:MyLanguage/Help:System message|System message]].
</div>

=== Prefer-recent ===
<span lang="en" dir="ltr" class="mw-content-ltr">Adding <kbd>prefer-recent:</kbd> anywhere in the query gives recently edited articles a slightly larger than normal boost in the page-ranking rules.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Prefer-recent is only applied when using the default <code>relevance</code> [[#Explicit sort orders|sort order]].</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
It defaults to boost only 60% of the score, in a large, 160-day window of time, which can be entered in the query as <kbd>prefer-recent:0.6,160</kbd>. This plays well with other page ranking rules, and is intended for most searches.
</div>

<span lang="en" dir="ltr" class="mw-content-ltr">You can manipulate the rules: <kbd>prefer-recent:''boost'',''recent''</kbd></span>
<span lang="en" dir="ltr" class="mw-content-ltr">Technically, "boost" is the proportion of score to scale, and "recent" is the half life in days.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">The boost is more than the usual ''multiplier'', it is an ''[[w:Exponential decay|exponential]]'' boost.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">The factor used in the exponent is the time since the last edit.</span> 

<div lang="en" dir="ltr" class="mw-content-ltr">
For example
</div>

:<kbd>prefer-recent:,7</kbd>

<span lang="en" dir="ltr" class="mw-content-ltr">Pages older than 7 days are boosted half as much, and pages older than 14 days are boosted half as much again, and so on.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">For a simple "sort by date" in highly refined search results, where page ranking and boosting are largely meaningless, just boost the entire score.</span>

* <kbd>prefer-recent:1,7</kbd> - <span lang="en" dir="ltr" class="mw-content-ltr">weeks</span>
* <kbd>prefer-recent:1,1</kbd> - <span lang="en" dir="ltr" class="mw-content-ltr">days</span>
* <kbd>prefer-recent:1,0.0007</kbd> - <span lang="en" dir="ltr" class="mw-content-ltr">minutes</span>
* <kbd>prefer-recent:1,0.0001</kbd> - <span lang="en" dir="ltr" class="mw-content-ltr">8.64 seconds</span>
* <kbd>prefer-recent:1,0.00001</kbd> - <span lang="en" dir="ltr" class="mw-content-ltr">seconds</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Boost-templates ===
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">You can boost pages' scores based on what templates they contain. This can be applied to all search queries by declaring boosts via [[MediaWiki:Cirrussearch-boost-templates]], or ad-hoc in individual queries via the <code>boost-templates:""</code> operator. If the <code>boost-templates</code> operator is set in a query, then the contents of <code>cirrussearch-boost-templates</code> are ignored.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Similar to the prefer-recent feature, boost-templates is applied as part of the default <code>relevance</code> [[#Explicit sort orders|sort order]]. It has no effect on other search orders.</span>

<span lang="en" dir="ltr" class="mw-content-ltr">The syntax of the message is as follows:</span>

* <span lang="en" dir="ltr" class="mw-content-ltr">Everything from a <code>#</code> character to the end of the line is considered a comment, and ignored.</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">Every non-blank line is interpreted as the exact name of a template that should receive boosting (including namespace prefix), followed by a pipe "|" character, followed by a number, followed by a "%" character.</span>

<span lang="en" dir="ltr" class="mw-content-ltr">Good examples:</span>

  Template:Important|150%
  Template:Very_Very_Important|300%
  Template:Less_important|50%

<span lang="en" dir="ltr" class="mw-content-ltr">Bad examples:</span>

  Template:Foo|150.234234% # <span lang="en" dir="ltr" class="mw-content-ltr">decimal points are not allowed.</span>
  Foo|150% # <span lang="en" dir="ltr" class="mw-content-ltr">technically valid, but acts on transclusions of Foo (main space article) instead of Template:Foo.</span>

<span lang="en" dir="ltr" class="mw-content-ltr">Some examples:</span>

;<kbd>boost-templates:"Template:Quality_Image|200%" incategory:china</kbd>

<div lang="en" dir="ltr" class="mw-content-ltr">
:Find files in the China category, sorting quality images first.
</div>
;<kbd>boost-templates:"Template:Quality_Image|200% Template:Low_Quality|50%" incategory:china</kbd>
<div lang="en" dir="ltr" class="mw-content-ltr">
:Find files in the China category, sorting quality images first and low-quality images last.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
;<kbd>boost-templates:"Template:Quality_Image|200% Template:Low_Quality|50%" popcorn</kbd>
:Find files about popcorn, sorting quality images first and low-quality images last. Remember that through the use of the <code>cirrussearch-boost-templates</code> message this can be reduced to just <code>popcorn</code>.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Decimal points are not permitted in percentage values. Search scoring is such that fractions of a percent are unlikely to make a difference.
</div>

<span lang="en" dir="ltr" class="mw-content-ltr">Beware that if you add very low or very high percentages via <kbd>cirrussearch-boost-templates</kbd>, they can poison the full-text scoring.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">For example, if Wikipedia were to boost the "Featured article" template by 1 million percent, then, searches for any term mentioned in featured articles, would rank the featured article above even the dedicated article about that term.</span>
{{void|1=<span lang="en" dir="ltr" class="mw-content-ltr">Then, searches for any term mentioned in featured articles, would rank the featured article above even the dedicated article about that term.</span>}}
<span lang="en" dir="ltr" class="mw-content-ltr">Phrase matching would be similarly blown away, so a search like <code>brave new world</code> would return a featured article as first result even if it merely has those three words mentioned throughout it, instead of the more relevant article about [[w:Brave New World|Brave New World]] itself.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Regular expression searches ==
</div>

{{warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not run a bare <kbd>insource:/''regexp''/</kbd> search. It will probably timeout after 20 seconds anyway, while blocking the queries of responsible users.</span>}}

<span lang="en" dir="ltr" class="mw-content-ltr">A basic indexed search finds ''words'' rendered visible on a page. Hyphenation and punctuation marks and bracketing, slash and other math and computing symbols, are merely boundaries for the ''words''. It is not possible to include them in an indexed search.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Mostly that search behavior is wanted by the user. However, sometimes one wants to have the ability for a more precise search.</span>

<span lang="en" dir="ltr" class="mw-content-ltr">To get around the syntactic deficiency of index-based searches regexp searches can be used.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">But as queries with only regexp expressions are very slow and resource consuming, they should always be combined with an index-based search, such that the regexp search-domain gets limited to the results of one or more index-based search.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
An "exact string" regexp search is a basic search; it will simply "quote" the entire regexp, or "backslash-escape" all non-alphanumeric characters in the string. All regexp searches also require that the user develops a simple filter to generate the search domain for the regex engine to search (index based search domain marked bold, regexp part marked in italics):
</div>

* <kbd>'''insource:"debian.reproducible.net"''' ''insource:/debian\.reproducible\.net/''</kbd>
* <kbd>'''insource:"c:\program files (x86)"''' ''insource:/C\:\\Program Files \(x86\)/i''</kbd>
* <kbd>'''insource:"&lt;tag>{<nowiki/>{template}}&lt;/tag>"''' ''insource:/"&lt;tag>{<nowiki/>{template}}&lt;"\/"tag>"/''</kbd>
* <kbd>'''insource:"[<nowiki/>[title|link label]]'s"''' ''insource:/"[<nowiki/>[title|link label]]'s"/''</kbd>
* <kbd>''insource:/regexp/'' '''prefix:{<nowiki/>{FULLPAGENAME}}'''</kbd>

<div lang="en" dir="ltr" class="mw-content-ltr">
The last example works from a link on a page, but {<nowiki/>{[[Special:MyLanguage/FULLPAGENAME|FULLPAGENAME]]}} doesn't function in the search box.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
For example: <kbd><nowiki>[[Special:Search/insource:/regex/&nbsp;prefix:{{FULLPAGENAME}}]]</nowiki></kbd> [[Special:Search/insource:/regex/ prefix:{{FULLPAGENAME}}| finds the term ''regex'' on this page]].
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
A query with no namespace specified and no prefix specified searches your default search domain, (settable on any search-results page, i.e. at ''[[Special:Search]]''). Some users keep their default search domain at "all namespaces", i.e. the entire wiki. On a large wiki if this user does a bare regexp search it will probably fail, incurring a timeout, before completing the search.
</div>

<span lang="en" dir="ltr" class="mw-content-ltr">A regex search actually scours each page in the search domain character-by character.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">By contrast, an indexed search actually queries a few records from a database separately maintained from the wiki database, and provides nearly instant results.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">So when using an ''insource://'' (a regexp of any kind), consider adding other search terms that will limit the regex search domain as much as possible.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">There are many search terms that use an index and so instantly provide a more refined search domain for the /regexp/. In order of general effectiveness:</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
* ''insource:""'' with quotation marks, duplicating the regexp except ''without the slashes'' or escape characters, is ideal.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* ''intitle'' (without regex search), ''incategory'', and ''linksto'' are excellent filters.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* ''hastemplate:'' is a very good filter.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* "''word1 word2 word3''", with or without the quotation marks, are good.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* ''namespace:'' is practically useless, but may enable a slow regexp search to complete.
</div>

<span lang="en" dir="ltr" class="mw-content-ltr">To test a bare regexp query you can create a page with test patterns, and then use the ''prefix'' parameter with that fullpagename.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">The match will be highlighted.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">It searches that page (in the database) and its subpages.</span> 

<div lang="en" dir="ltr" class="mw-content-ltr">
Search terms that do not increase the efficiency of a regexp search are the page-scoring operators: ''morelike'', ''boost-template'', and ''prefer-recent''.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
==== Metacharacters ====
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">This section covers how to escape metacharacters used in regexp searches.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">For the actual meaning of the metacharacters see the [https://www.elastic.co/guide/en/elasticsearch/reference/current/regexp-syntax.html explanation of the syntax].</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">For the formal definition see the [https://lucene.apache.org/core/7_3_0/core/org/apache/lucene/util/automaton/RegExp.html Lucene grammar for regular expressions].</span></ref>

{{tip|1=<span lang="en" dir="ltr" class="mw-content-ltr">The use of an exact string requires a regexp, but the regexp term obligates the search to limit itself. ''Add'' a regexp term, never search a bare regexp. ''Start'' by noting the number of pages in a previous search before committing an exact string search. Querying with an exact string requires a filtered search domain.</span>}}

<div lang="en" dir="ltr" class="mw-content-ltr">
For example:
</div> 

<div lang="en" dir="ltr" class="mw-content-ltr">
* to search a namespace, gauge the number of pages with a single term that is a namespace. This will list the number of pages in that namespace.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* starting out to find again what you may have seen, like "wiki-link" or "(trans[in]clusion)" start with namespace and insource filters.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
There are some notable differences from standard regex metacharacters:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* The <code>\n</code> or <code>\r\n</code> are not reserved for matching a newline.
</div> <span lang="en" dir="ltr" class="mw-content-ltr">To search for a string that contains a newline, you can do a search like <code><nowiki>insource:/[^\}]\}\}[^\} \|]{2}\<noinclude/i</nowiki></code> which means not a curly brace, then two curly braces, then any two characters except a curly brace, space, or pipe, then a {{tag|noinclude|open}} tag.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The "any character except" will include a newline in the search.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Note thas this search was designed only to match to the following string:</span>
:<syntaxhighlight lang="text">
}}

<noinclude>
</syntaxhighlight><!-- "syntaxhighlight" instead of "pre" to preserve indentation -->

<div lang="en" dir="ltr" class="mw-content-ltr">
* The dot <code>.</code> metacharacter stands for any character including a newline, so <code>.*</code> matches across lines.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* The number <code>#</code> sign means something, and must be escaped.
</div><ref><span lang="en" dir="ltr" class="mw-content-ltr">[https://lucene.apache.org/core/7_0_1/core/org/apache/lucene/util/automaton/RegExp.html Class RegExp], Lucene RegExp syntax</span></ref>
<div lang="en" dir="ltr" class="mw-content-ltr">
* The <code>^</code> and <code>$</code> are not implemented. Like "grep" (global per line, regular expression, print each line), each insource:// is a "global per document, regular expression, search-results-list each document" per document.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* <code>&lt;</code> and <code>&gt;</code> support a multi-digit numeric range like <code>[0-9]</code> does, but without regard to the number of character positions, or the range in each position, so <code>&lt;9-10></code> works, and even <code>&lt;1-111></code> works.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
====Substitutions for some metacharacters====
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
While character classes <code>\n</code>, <code>\s</code>, <code>\S</code> are not supported, in case of an acute need to use them in a regular expression, you may use these workarounds:
</div>

{|class="wikitable"
|+ 
!scope="col"| <span lang="en" dir="ltr" class="mw-content-ltr">[[w:PCRE|PCRE]]</span>
!scope="col"| <span lang="en" dir="ltr" class="mw-content-ltr">CirrusSearch</span>
!scope="col"| <span lang="en" dir="ltr" class="mw-content-ltr">Description</span>
|-
| <code>\n</code> || <code>[^ -􏿿]</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A newline (also can find a [[w:en:Tab key#Tab_characters|tabulation character]])</span>
|-
| <code>[^\n]</code> || <code>[ -􏿿]</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Any character except for a newline (and tabulation; you can add it to character set to include it as well)</span>
|-
| <code>\s</code> || <code>[^!-􏿿]</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A white space character: space, newline, or tabulation</span>
|-
| <code>\S</code> || <code>[!-􏿿]</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Any character except for white space characters (not a space, not a newline, and not a tabulation)</span>
|}

<span lang="en" dir="ltr" class="mw-content-ltr">In these ranges, " " (space) is used as the character immediately following [[w:Control character|control characters]], "!" – the character immediately following it, and "􏿿" as the U+10FFFF character, which is the last character in [[w:Unicode|Unicode]].</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Thus, the range from " " to "􏿿" includes all characters except for control ones, of which articles may contain newlines and tabs, while the range from "!" to "􏿿" includes all characters except for control ones and the space.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
==== Refining with an exact string ====
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* refining an ongoing search process with what you want to see, like "2 + 2 = 4", or "''site''.org" This is ideally the best use of regex, because it adds it as a single regexp term while refining a search, the limited number of pages the regexp must crawl is can be seen.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
You can start out intending an exact string search, but keep in mind:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* regex only search the wikitext not the rendered text, so there are some differences around the markup, and even the number of space characters must match precisely.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* You are obligated to supply an accompanying filter.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* You must learn how to escape regex metacharacters.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
There are two ways to escape metacharacters. They are both useful at times, and sometimes concatenated side-by-side in the escaping of a string.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* Backslash-escape one of them \''char''. The insource:/''regexp''/ uses slashes to delimit the regexp. Giving /reg/exp/ is ambiguous, so you must write /reg\/exp/.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Put a string of them in double quotes "''string''". Because ''escaping a character can't hurt'', you can escape any character along with any possible metacharacters in there. Escaping with quotes is cleaner.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* You can't mix methods, but you can concatenate them.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''Double-quotes escaping''' using insource:/"''regexp''"/ is an easy way to search for many kinds of strings, but you can't backslash-escape anything inside a double-quoted escape.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* <code>/"[<nowiki/>[page/name|{<nowiki/>{temp-late"/</code> instead of <code>/\[\[page\/name\|\{\{temp\-late/</code>
* <code>/"literal back\slash"/</code> is as good as <code>/literal back\\slash/</code>
* But <code>/"This \" fails"/</code> always.
* And <code>/"This \/ depends"/</code>. It finds the <code>\/</code> literally, which is not the <code>/</code> you probably wanted.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''Backslash-escape''' using insource:/''regexp''/ allows escaping the " and / delimiters, but requires taking into account metacharacters, and escaping any:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* To match a <code>/</code> delimiter character use <code>\/</code>.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* To match a <code>"</code> delimiter character use <code>\"</code>.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* The escaped metacharacters would be <code>\~\@\#\&\*\(\)\-\+\{\}\[\]\|\<\>\?\.\\</code>.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* The equivalent expression escaped with double-quotes is <code>"~@#&*()-+{}[]|\<>?.\"</code>.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The simplest algorithm to create the basic string-finding expression using insource:/"''regexp''"/, need not take metacharacters into account except for the " and / characters:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
# Write <code>the/str"ing</code> out. (The /" delimiters "/ are not shown.)
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# Replace <code>"</code> with <code>"\""</code> (previous double-quote: stop, concatenate, quote restart).
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# Replace <code>/</code> with <code>"\/"</code> (stop, concatenate, start).
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# You get <code>insource:/"the"\/"str"\""ing"/</code>, showing concatenation of the two methods.
</div>

{{tip|1=<span lang="en" dir="ltr" class="mw-content-ltr">While refining a regexp on a search results page, keep in mind that the snippet "wikitext" has modified spacing. Regex are sensitive to space characters, so copying from snippets is dangerous.</span>}}

<span lang="en" dir="ltr" class="mw-content-ltr">The square-bracket notation for creating your own character-class ''also'' escapes ''its'' metacharacters. To target a literal right square bracket in your character-class pattern, it must be backslash escaped, otherwise it can be interpreted as the closing delimiter of the character-class pattern definition.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">The first position of a character class will also escape the right square bracket. Inside the delimiting square brackets of a character ''class'', the dash character also has special meaning (range) but it too can be included literally in the class the same way as the right square bracket can.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">For example both of these patterns target a character that is either a dash or a right square bracket or a dot: <code>[-.\]]</code> or <code>[].\-]</code>.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
For general examples using metacharacters:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
*<kbd>insource:"2+2=4" insource:/"2+2=4"/</kbd> matches "2 + 2 = 4", with zero spaces between the characters.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
*<kbd>insource:"2 + 2 = 4" insource:/2 ?\+ ?2 ?= ?4\./</kbd> match with zero or one space in between. The equals = sign is not a metacharacter, but the plus + sign is.
</div>
*<kbd>insource:"<''tag''>[<nowiki/>[link|2\3?]]\</''tag''>" insource:/"<''tag''>[<nowiki/>[link|2\3?]]<'''<big>"\/"</big>'''''tag''>"/</kbd>

<div lang="en" dir="ltr" class="mw-content-ltr">
====Regex on titles====
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">The <kbd>insource</kbd> keyword does only search the page source content.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">To run regex searches on the title strings <kbd>intitle:/regex/</kbd> can be used.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
====Advanced example====
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
For example, using metacharacters to find the usage of a template called ''Val'' having, inside the template call, an unnamed parameter containing a possibly signed, three to four digit number, possibly surrounded by space characters, ''and'' on the same page, inside a template Val call, a named argument <code>fmt=commas</code> having any allowable spaces around it, (it could be the same template call, or a separate one):
</div>

:<small><code>hastemplate:val insource:"fmt commas" insource:<big>'''/'''</big>\{\{ *[Vv]al *\|[^}]*fmt *= *commas/ insource:/\{\{ *[Vv]al *\|[^}]*[-+]?[0-9]{3,4} *[|}]<big>'''/'''</big></code></small>

<span lang="en" dir="ltr" class="mw-content-ltr">Note that the = sign in "fmt commas" is not needed but that adding it would not change the search results.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">It is fast because it uses two filters so that every page the regexp crawls has the highest possible potential.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Geo Search ==
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">Searching based on the (primary) coordinates associated with pages.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Depends on {{ll|Extension:GeoData}} and <code><nowiki>{{#coordinates:}}</nowiki></code></span>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== bounded ===
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">You can limit search to pages identified as being near some specified geographic coordinates.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">The coordinates can either be specified as a &lt;lat>,&lt;lon> pair, or by providing a page title from which to source the coordinates.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">A distance to limit the search to can be prepended if desired.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Examples:</span>

* <kbd>neartitle:"San Francisco"</kbd>
* <kbd>neartitle:"100km,San Francisco"</kbd>
* <kbd>nearcoord:37.77666667,-122.39</kbd>
* <kbd>nearcoord:42km,37.77666667,-122.39</kbd>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== boosted ===
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">You can alternatively increase the score of pages within a specified geographic area.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">The syntax is the same as bounded search, but with boost- prepended to the keyword.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">This effectively doubles the score for pages within the search range, giving a better chance for nearby search results to be near the top.</span>

* <kbd>boost-neartitle:"San Francisco"</kbd>
* <kbd>boost-neartitle:"100km,San Francisco"</kbd>
* <kbd>boost-nearcoord:37.77666667,-122.39</kbd>
* <kbd>boost-nearcoord:42km,37.77666667,-122.39</kbd>

<div lang="en" dir="ltr" class="mw-content-ltr">
== File properties search ==
</div>
{{MW version|version=1.28|compact=y|comment=and after|gerrit change=311061}}

<div lang="en" dir="ltr" class="mw-content-ltr">
Since MediaWiki 1.28, CirrusSearch supports indexing and searching of properties of files in the <code>File:</code> namespace. This includes:
* file media type
* MIME type
* size
* width & height
* resolution
* bit depth for files that support these
</div>

{{tip|1=<span lang="en" dir="ltr" class="mw-content-ltr">While these predicates are useful only for files, they by themselves do not limit search to the <code>File:</code> namespace. It is recommended to include this namespace in a search or restrict the search to only this namespace when using these conditionals.</span>}}

<div lang="en" dir="ltr" class="mw-content-ltr">
=== filetype ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Searching for file type allows to retrieve files according to their classification, such as office documents, videos, raster images, vector images, etc. The following types currently exist:
</div> 

* <code>UNKNOWN</code>
* <code>BITMAP</code>
* <code>DRAWING</code>
* <code>AUDIO</code>
* <code>VIDEO</code>
* <code>MULTIMEDIA</code>
* <code>OFFICE</code>
* <code>TEXT</code>
* <code>EXECUTABLE</code>
* <code>ARCHIVE</code>

<div lang="en" dir="ltr" class="mw-content-ltr">
This list may be extended in the future. See also <code>MEDIATYPE_*</code> constants in <code>Defines.php</code>.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The syntax of the search is: <kbd>filetype:{type}</kbd>. Example:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
<kbd>filetype:video</kbd> - looks for all videos
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The filetype search is not case-sensitive.
</div> 

<div lang="en" dir="ltr" class="mw-content-ltr">
=== filemime ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Matches file MIME type. The syntax is:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
<kbd>filemime:{MIMEtype}</kbd> - look for files of this MIME type
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The argument can be quoted to specify exact match. Without quotes, partial matches to components of MIME type will be accepted too.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Examples:
</div>

* <kbd>filemime:"image/png"</kbd> - <span lang="en" dir="ltr" class="mw-content-ltr">look for files with MIME type exactly <code>image/png</code></span>
* <kbd>filemime:pdf</kbd> - <span lang="en" dir="ltr" class="mw-content-ltr">look for all PDF documents</span>
* <kbd>-filemime:pdf</kbd> - <span lang="en" dir="ltr" class="mw-content-ltr">skip all PDF documents (notably on Commons)</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
The MIME type search is not case-sensitive.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== filesize ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Search for file of given size, in kilobytes (kilobyte means 1024 bytes). The syntax is:
</div>

* <kbd>filesize:{number}</kbd> या <kbd>filesize:>{number}</kbd> - <span lang="en" dir="ltr" class="mw-content-ltr">file with size at least given number</span>
* <kbd>filesize:<{number}</kbd> - <span lang="en" dir="ltr" class="mw-content-ltr">file with size no more than given number</span>
* <kbd>filesize:{number},{number}</kbd> - <span lang="en" dir="ltr" class="mw-content-ltr">file with size between given numbers</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
Examples:
</div>

* <span lang="en" dir="ltr" class="mw-content-ltr"><kbd>filesize:>20</kbd> or <kbd>filesize:20</kbd></span> - <span lang="en" dir="ltr" class="mw-content-ltr">files 20KB and bigger</span>
* <kbd>filesize:<1024</kbd> - <span lang="en" dir="ltr" class="mw-content-ltr">files smaller than 1MB</span>
* <kbd>filesize:100,500</kbd> - <span lang="en" dir="ltr" class="mw-content-ltr">files with sizes between 100KB and 500KB</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== File measures ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
It is possible to search for specific file measures: width, height, resolution (which is defined as square root of height × width), and bit depth. Not all files may have these properties. The syntax is:
</div>

* <kbd>{measure}:{number}</kbd> - <span lang="en" dir="ltr" class="mw-content-ltr">file with measure that equals to given number</span>
* <kbd>{measure}:>{number}</kbd> - <span lang="en" dir="ltr" class="mw-content-ltr">file with measure that is at least given number</span>
* <kbd>{measure}:<{number}</kbd> - <span lang="en" dir="ltr" class="mw-content-ltr">file with measure that is no more than given number</span>
* <kbd>{measure}:{number},{number}</kbd> - <span lang="en" dir="ltr" class="mw-content-ltr">file with measure that is between given numbers</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
Where <code>measure</code> can be:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
<kbd>filew</kbd> or <kbd>filewidth</kbd> - file width
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
<kbd>fileh</kbd> or <kbd>fileheight</kbd> - file height
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
<kbd>fileres</kbd> - file resolution (see above)
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
<kbd>filebits</kbd> - file bit depth
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Examples:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
<kbd>filew:>800 fileh:>600</kbd> - files that are at least 800×600 pixels in size
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
<kbd>filebits:16</kbd> - files with 16-bit color depth
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
<kbd>fileheight:100,500</kbd> - file between 100 and 500 pixels high
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Wikibase search ==
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">The {{ll|Wikibase}} extension defines some search keywords in order to make it easier to search for certain Wikibase items. This is useful on {{ll|Wikidata}} and other Wikibase sites, including to search for images with [[commons:Special:MyLanguage/Structured data|Structured data]] on {{ll|Wikimedia Commons}}.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">See {{ll|Help:WikibaseCirrusSearch}} for details.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Cross-wiki search results ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
There are two kinds of cross-wiki results that may be shown when searching on Wikipedia.
</div>

<span lang="en" dir="ltr" class="mw-content-ltr">Cross-project search (also known as interwiki search, sister search, or sister projects search) shows additional results from other projects (Wiktionary, Wikisource, Wikiquote, etc.) shown to the side on the Wikipedia results page.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Cross-project search is available on most Wikipedias with sister projects.</span>

<span lang="en" dir="ltr" class="mw-content-ltr">Cross-language search (see [[wmfblog:2016/07/27/wikipedia-language-search/|blog post]]) refers to additional results shown below the main results that are from a Wikipedia in a different language.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Cross-language search uses a heavily modified and optimized version of a light-weight language detector called {{ll|TextCat}}.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Cross-language search is currently only available on a few Wikipedias (see TextCat link for details).</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Explicit sort orders ==
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">In addition to the default relevance based sort, CirrusSearch can provide results using a few other explicit sort orders.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Specifying a sorting order other than <code>relevance</code> will disable all search keywords that affect scoring, such as <code>prefer-recent</code> or <code>boost-templates</code>.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">The keywords will still be parsed, but they will have no effect.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
Sorting options are currently available from the MediaWiki API by providing the <code>srsort</code> parameter.
</div>

'''<span lang="en" dir="ltr" class="mw-content-ltr">Guidance:</span>'''

<div lang="en" dir="ltr" class="mw-content-ltr">
Sorting options can be manually added to a search URL by adding <code>'''&sort=''order'''''</code>, for example:
</div>

* <code>[https://www.mediawiki.org/w/index.php?search=foo&sort=last_edit_desc https://www.mediawiki.org/w/index.php?search=foo'''&sort=''last_edit_desc''''']</code>

'''<span lang="en" dir="ltr" class="mw-content-ltr">Valid sort orders include:</span>'''

{| class="wikitable sortable"
! <span lang="en" dir="ltr" class="mw-content-ltr">URL supplement</span>
! <span lang="en" dir="ltr" class="mw-content-ltr">Description</span>
|-
|<code>'''&sort=''incoming_links_asc'''''</code>
| <span lang="en" dir="ltr" class="mw-content-ltr">Lowest to highest number of incoming links.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is approximately from least to most popular.</span>
|-
|<code>'''&sort=''incoming_links_desc'''''</code>
| <span lang="en" dir="ltr" class="mw-content-ltr">Highest to lowest number of incoming links.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is approximately from most to least popular.</span>
|-
|<code>'''&sort=''last_edit_asc'''''</code>
| <span lang="en" dir="ltr" class="mw-content-ltr">From least recently to most recently edited</span>
|-
|<code>'''&sort=''last_edit_desc'''''</code>
| <span lang="en" dir="ltr" class="mw-content-ltr">From most to least recently edited</span>
|-
|<code>'''&sort=''create_timestamp_asc'''''</code>
| <span lang="en" dir="ltr" class="mw-content-ltr">From least to most recently created</span>
|-
|<code>'''&sort=''create_timestamp_desc'''''</code>
| <span lang="en" dir="ltr" class="mw-content-ltr">From most to least recently created</span>
|-
|<code>'''&sort=''just_match'''''</code>
| <span lang="en" dir="ltr" class="mw-content-ltr">A simple relevance sort based only on text matching</span>
|-
|<code>'''&sort=''relevance'''''</code>
| <span lang="en" dir="ltr" class="mw-content-ltr">A relevance sort taking into account many features of the document</span>
|-
|<code>'''&sort=''random'''''</code>
| <span lang="en" dir="ltr" class="mw-content-ltr">Randomized</span>
|-
|<code>'''&sort=''none'''''</code>
| <span lang="en" dir="ltr" class="mw-content-ltr">Unsorted, arbitrarily ordered lists.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Preferred for large result sets.</span>
|}

<div lang="en" dir="ltr" class="mw-content-ltr">
== Interface for advanced options ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
[[File:AdvSearch Screen 20170620.png|thumb|Advanced Search Interface]]
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The [[Special:MyLanguage/Extension:AdvancedSearch|AdvancedSearch]] extension adds an improved interface to the search page allowing the use of several options described above in a user-friendly manner. See [[Special:MyLanguage/Help:AdvancedSearch|here for the user manual]].
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== See also ==
</div>
* {{ll|Extension:CirrusSearch}}
<div lang="en" dir="ltr" class="mw-content-ltr">
* [[Extension:CirrusSearch/CompletionSuggester|Completion Suggester]] - the incremental search feature of CirrusSearch
</div>
* {{ll|Wikimedia Search Platform/Search/Glossary}} — <span lang="en" dir="ltr" class="mw-content-ltr">definitions, context, and links for terms related to search.</span>
<div lang="en" dir="ltr" class="mw-content-ltr">
* See {{ll|Help:Searching}} for MWSearch, used by the many wikis that don't have a search extension.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== External links ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* [http://lucene.apache.org/core/3_5_0/queryparsersyntax.html From Lucene], highly relevant documentation.
</div>
* {{git file |file=tests/browser/features |sha=31869139d0bdac6674817b104772ae28efef45c3<!--Last version to contain this now-deleted file--> |project=mediawiki/extensions/CirrusSearch |text=<span lang="en" dir="ltr" class="mw-content-ltr">Full specifications in the extension's browser tests</span>}} {{as of|2017-12-06}}
* [[Extension:CirrusSearch/Profiles]]&nbsp;– <span lang="en" dir="ltr" class="mw-content-ltr">sets of tunable parameters that influence various aspect of the indexing</span>
* [https://blog.wikimedia.org/c/technology/search/ Wikimedia blog articles related to search]
* [https://global-search.toolforge.org/ WMF Global Search]

<span id="Notes_and_references"></span>
== टिप्पणियाँ और सन्दर्भ ==
<references />

[[Category:Search{{#translation:}}]]
[[Category:Help{{#translation:}}]]