Help:CirrusSearch

The quickest way to find information in Wikimedia projects is to look it up directly. On every page there is a  box.

CirrusSearch is a MediaWiki extension that uses Elasticsearch to provide enhanced search features over the helps>Special:MyLanguage/Help:Searching|default MediaWiki search. The Wikimedia Foundation uses CirrusSearch for all wmproj>m:Special:MyLanguage/Wikimedia_projects|Wikimedia projects.

This page describes the features of CirrusSearch. If your question is not answered here, feel free to ask on the talk>Help talk:CirrusSearch|talk page and someone will answer it for you.

For information on the MediaWiki extension see extcc>Special:MyLanguage/Extension:CirrusSearch|Extension:CirrusSearch.

How it works
Enter key words and phrases and press Enter or Return on your keyboard. Or click the magnifying glass icon, Search, or Go button.

If a page has the same title as what you entered you will be directed to that page.

Otherwise, it searches all pages on the wiki, and presents a list of articles that matched your search terms, or a message informing you that no page has all the key words and phrases.

If you click the "" button without filling in anything, you will be taken to "Special:Search" which gives you extra searching options (also available from any search results list)

You may find it useful to restrict a search to pages within a particular help>Special:MyLanguage/Help:Namespaces|namespace e.g., only search within the     pages.

Check the namespaces you require for this search.

What's improved?
CirrusSearch features three main improvements over the default MediaWiki search, namely:


 * Better support for searching in different languages.


 * Faster updates to the search index, meaning changes to articles are reflected in search results much faster.


 * Expanding templates, meaning that all content from a template is now reflected in search results.

How frequently is the search index updated?
Updates to the search index are done in near real time.

Changes to pages should appear immediately in the search results.

Changes to templates should take effect in articles that include the template in a few minutes.

The templates changes use the job queue, so performance may vary.

A purge>Special:MyLanguage/Manual:Purge|null edit to the article will force the change through, but that shouldn't be required if everything is going well.

Search suggestions
The search suggestions you get when you type into the search box that drops down candidate pages is sorted by a rough measure of article quality.

This takes into account the number of incoming wikilinks, the size of the page, the number of external links, the number of headings, and the number of redirects.

Search suggestions can be skipped and queries will go directly to the search results page. Add a tilde   before the query. Example "~Frida Kahlo". The search suggestions will still appear, but hitting the Enter key at any time will take you to the search results page.

ASCII/accents/diacritics folding is turned on for English text, but there are some formatting problems with the result. See.

Full text search
A "full text search" is an "indexed search". All pages are stored in the wiki database, and all the words in the non-redirect pages are stored in the search database, which is an index to practically the full text of the wiki. Each visible word is indexed to the list of pages where it is found, so a search for a word is as fast as looking up a single-record. Furthermore, for any changes in wording, the search index is updated within seconds.

There are many indexes of the "full text" of the wiki to facilitate the many types of searches needed. The full wikitext is indexed many times into many special-purpose indexes, each parsing the wikitext in whatever way optimizes their use. Example indexes include:


 * "auxiliary" text, includes hatnotes, captions, ToC, and any wikitext classed by an HTML attribute  class=searchaux .
 * "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.

There is support for dozens of languages, but all languages are wanted.

There is a list of currently supported languages at [<tvar|url>http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/analysis-lang-analyzer.html</> elasticsearch.org]; see their [<tvar|doc>http://www.elasticsearch.org/contributing-to-elasticsearch/</> documentation on contributing] to submit requests or patches.

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.

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).

Search features also include:


 * Sorting navigation suggestions by the number of incoming links.
 * Starting with the tilde character <tvar|tilde> </> 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.


 * 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.

Words, phrases, and modifiers
The basic search term is a word or a "phrase in quotes". Search recognizes a "word" to be:


 * a string of digits
 * a string of letters
 * subwords between letters/digit transitions, such as in <tvar|txt2r> txt2regex </>
 * subwords inside a compoundName using camelCase

A "stop word" is a word that is ignored (because it is common, or for other reasons).

A given search term matches against content (rendered on the page). To match against wikitext instead, use the <tvar|insource> insource </> search parameter (See section below). Each search parameter has its own index, and interpret its given term in its own way.

Spacing between words, phrases, parameters, and input to parameters, can include generous instances of whitespace and greyspace characters. "Greyspace characters" are all the non-alphanumeric characters <tvar|characters> ~!@#$%^&_+-={}|[]\:";'<>?,./ </>. A mixed string of greyspace characters and whitespace characters, is "greyspace", and is treated as one big word boundary.  Greyspace is how indexes are made and queries are interpreted.

Two exceptions are where 1) an embedded:colon is one word (it being treated as a letter), and 2) an embedded comma, such as in <tvar|123> 1,2,3 </>, is treated as a number. Greyspace characters are otherwise ignored unless, due to query syntax, they can be interpreted as modifier characters.

The modifiers are <tvar|mod> ~ * \? - " ! </>. 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:


 * A fuzzy-word or fuzzy-phrase search can suffix a tilde <tvar|tilde> </> character (and a number telling the degree).
 * A tilde <tvar|tilde> </> character prefixed to the first term of a query guarantees search results instead of any possible navigation.
 * A wildcard character inside a word can be a (escaped) question mark \? for one character or an asterisk <tvar|asterisk> * </> character for more.
 * Truth-logic can interpret <tvar|and> AND </> and <tvar|or> OR </>, but parameters cannot. Note that the <tvar|and> AND </> and <tvar|or> OR </> operators currently do not function in the traditional truth-logic manner! For details see more on logical operators.
 * Truth-logic understands <tvar|dash> - </> or <tvar|exclaim> ! </> prefixed to a term to invert the usual meaning of the term from "match" to "exclude".


 * Quotes around words mark an "exact phrase" search. For parameters they are also needed to delimit multi-word input.
 * Stemming is automatic but can be turned off using an "exact phrase".

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:


 * given <tvar|wjgrey> words-joined_by_greyspace(characters) </> or <tvar|wjcamel> wordsJoinedByCamelCaseCharacters </> it finds <tvar|wjb> words joined by </> ... <tvar|char> characters </>, in their bare forms or greyspace forms.
 * <tvar|txt2n> txt2number </> will match <tvar|t2n> </> or <tvar|t2np> </>.
 * Stop words are enabled for the edge cases (in the periphery) of a grey_space or camelCase phrase. An example using <tvar|the> the </>, <tvar|of> of </>, and <tvar|a> a </> is that <tvar|ihoa> the_invisible_hand_of_a </> matches <tvar|mihs> </>.

A "search instead" report is triggered when a universally unknown word is ignored in a phrase.

Each one of the following types of phrase-matching contains and widens the match-tolerances of the previous one:


 * An "exact phrase" "in quotes" will tolerate (match with) greyspace. Given <tvar|exact_phrase> "exact_phrase" </> or <tvar|exactphrase> "exact phrase" </> it matches <tvar|exactbracket> </>.


 * A greyspace_phrase initiates stemming and stop word checks.


 * Given <tvar|camel> CamelCase </> it will additionally match <tvar|camelcase> </>, in all lowercase, because CirrusSearch is not case sensitive in matching.

Page ranking saves you from typing quotes for a two-word search. With no quotes a word-pair index is used in page-ranking, plus it finds the two words anywhere on the page.

Some parameters interpret greyspace phrases, but other parameters, like <tvar|insource> </> only interpret the usual "phrase in quotes".

Note that all stemming is case insensitive.

Note how the "exact phrase" search interpreted the embedded:colon character as a letter, but not the embedded_underscore character. A similar event occurs with the comma <tvar|comma>, </> character inside a number.

Given <tvar|inthisword> </>, CirrusSearch, when in an "exact phrase" context, (which includes the insource parameter context), will not match <tvar|in> </>, <tvar|this> </>, or <tvar|word> </>, but will then only match <tvar|inthiswordcolon> </>.

Otherwise, remember that for CirrusSearch words are letters, numbers, or a combination of the two, and case does not matter.

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.

When common words like "of" or "the" are included in a greyspace-phrase, they are ignored, so as to match more aggressively.

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.

Now <tvar|camelcase> camelcase </> matches <tvar|camelCase> camelCase </> because Search is not case sensitive, but <tvar|camelCase2> camelCase </> matches <tvar|camelcase2> camelcase </> because camelCase is more aggressive. 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.

From the table we can surmise that the basic search <tvar|1> parser_function -"parser function" </> is the sum of the basic searches <tvar|2> </> and <tvar|3> </>.

Making inquiries with numbers, we would find that:


 * <tvar|Plan9> Plan9 </> or <tvar|Plan_9> Plan_9 </> matches any of: <tvar|plan9> </>, <tvar|plans9> </>, <tvar|planned9th> </>, <tvar|planned92> </>, <tvar|plans> </>
 * <tvar|plan92> "plan9" </> only matches <tvar|plan93> </> (case insensitive)
 * <tvar|planast> Plan*9 </> matches <tvar|plan94> </> or <tvar|planet> </>.

The star <tvar|asterisk> * </> wildcard matches a string of letters and digits within a rendered word, but never the beginning character. One or more characters, a percentage of the word, must precede the <tvar|asterisk1> * </> character.


 * If the leading part is only letters then it will limit a match to a string of (zero of more) letters.
 * If only numbers, then it will limit a match to a sequence of (zero or more) numbers, including also ordinal letters (st, nd, rd), capital letters, or time abbreviations (am or pm); and it will match the entirety of (both sides of) a decimal numbers.
 * Otherwise the comma is considered part of one number, but the decimal point is considered a greyspace character, and will delimit two numbers.
 * Inside an "exact phrase" it matches stemming plus compounding.

The <tvar|quest> \? </> wildcard represents one letter or number; The <tvar|bsq> *\? </> is also accepted, but <tvar|bsqast> \?* </> is not recognized.

The wildcards are for basic word, phrase, and insource searches, and may also be an alternative to (some) advanced regex searches (covered later).

Putting a tilde <tvar|tilde> ~ </> character after a word or phrase activates a fuzzy search.


 * For a phrase it is termed a proximity search, because proximal words are tolerated to an approximate rather than exact phrase.
 * For example, <tvar|exact12p> "exact one two phrase"~2 </> matches <tvar|exact> </>.
 * For a word it means extra characters or changed characters.
 * 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 <tvar|word05> word~0.5 </> (<tvar|wordtilde> word~.5 </>), where at most two letters can be found swapped, changed, or added, but never the first two letters.
 * For a proximity phrase, a large number can be used, but that is an "expensive" (slow) search.
 * For a word <tvar|wordtilde1> word~2 </> is most fuzzy with an edit distance of 2 (default), and <tvar|wordtilde9> word~1 </> is least fuzzy, and <tvar|wordtilde12> word~0 </> is not fuzzy at all.

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. (In other words, add twice the number of segments). For the full proximity algorithm, see [<tvar|esslop>https://www.elastic.co/guide/en/elasticsearch/guide/current/slop.html</> Elasticsearch slop].

Quotes turn off stemming, <tvar|appendtilde> "but appending"~ </> the tilde reactivates the stemming.

Insource
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 MediaWiki markup, on any page except redirects. This phrase completely ignores greyspace: <tvar|issa> insource: "state state autocollapse" </> matches <tvar|state> </>.

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. Regex 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 must run more than twenty seconds. Regex run last, so to limit needless character-level scanning, you advance it a list of pages (a search domain) selected by an indexed search added to the query as a "clause", and you do this to every single regex query. Insource can play both roles, and the best candidate for <tvar|insourcearg> insource:/arg/ </> is often <tvar|insourcearg2> insource: arg </>, where arg is the same.

The syntax for the regexp is <tvar|insource> insource: </> no space, and then <tvar|regexp> /regexp/ </>. (No other parameter disallows a space. All the parameters except <tvar|regex> insource:/regexp/ </> generously accept space after their colon.)

Insource indexed-search and regexp-search roles are similar in many respects:


 * Both search wikitext only.
 * Neither finds things "sourced" by a transclusion>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.

But indexed searches all ignore greyspace; wildcards searches do not match greyspace, so regex are the only way to find an exact string of any and all characters, for example a sequence of two spaces. Regex 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. See regexanchor>#Regular expression searches</> below.

Prefix and namespace
For Search, a namespace term functions to specify the initial search domain. Instead of searching the entire wiki, the default is the main namespace (mainspace).

Only one namespace name can be set from the search box query. It is either the first term or in the last term, in a prefix parameter.

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. Your search domain, as a profile of namespaces, can be set here. The namespaces list will then present itself on the first page of future search results to indicate the search domain of the search results. To unset this, select the default namespace (shown in parentheses), select "Remember", and press Search.

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. 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.

A namespace term overrides the search bar, and a prefix term overrides a namespace.

Enter a namespace name, or enter <tvar|all> </>, or enter a <tvar|colon>  </> colon for mainspace.

All does not include the File namespace. File includes media content held at Commons such as PDF, which are all indexed and searchable.

When File is involved, a namespace modifier <tvar|local> </> has an effect, otherwise it is ignored.

Namespace aliases are accepted.

As with search parameters, local and all must be lowercase. Namespaces names are case insensitive.

The <tvar|prefixcolon> prefix: </> parameter matches any number of first-characters of all pagenames in one namespace. When the first letters match a namespace name and colon, the search domain changes.

Given a namespace only, prefix will match all its pagenames. Given one character only, it cannot be - dash or ' quote or " double quote. The last character cannot be a colon.

For pagenames that match, their subpage titles match by definition.

The prefix parameter does not allow a space before a namespace, but allows whitespace before a pagename.

The prefix parameter goes at the end so that pagename characters may contain " quotation marks.

The extrans>Special:MyLanguage/Extension:Translate</>|Translate extension creates a sort of "language namespace", of translated versions of a page. But unlike namespace or prefix, which create the initial search domain, the <tvar|inlang> inlanguage </> parameter is a filter of it. (See the next section.)

Exclude content from the search index
Content can be excluded from the search index by adding <tvar|css-class> </>. This will instruct CirrusSearch to ignore this content from the search index (see <tvar|phab></> for more context).

Additionally content can be marked as auxiliary information by adding <tvar|css-class> </>. 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. This distinction is used for items such as image thumbnail descriptions, 'see also' sections, etc.

Filters
A filter will have multiple instances, or negated instances, or it can run as a standalone filtering a search domain.

A query is formed as terms that filter a search domain.

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.) 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).

A namespace is a specified search domain but not a filter because a namespace will not run standalone.

A prefix will negate so it is a filter.

The search parameters below are filters for which there may be multiple instances.

Insource (covered above) is also a filter, but <tvar|regexp> insource:/regexp/ </> is not a filter. Filters and all other search parameters are lowercase. (Namespaces are an exception, being case insensitive.)

Intitle and incategory
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.
 * cow*


 * Find articles whose title or text contains words that start with cow
 * intitle:foo


 * Find articles whose title contains foo. Stemming is enabled for foo.
 * intitle:"fine line"


 * Find articles whose title contains fine line. Stemming is disabled.
 * intitle:foo bar


 * Find articles whose title contains foo and whose title or text contains bar.
 * -intitle:foo bar


 * Find articles whose title does not contain foo and whose title or text contains bar.
 * incategory:Music


 * Find articles that are in Category:Music
 * incategory:"music history"


 * Find articles that are in Category:Music_history
 * incategory:"musicals" incategory:"1920"


 * Find articles that are in both Category:Musicals and Category:1920
 * -incategory:"musicals" incategory:"1920"


 * Find articles that are not in Category:Musicals but are in Category:1920

Intitle and incategory are old search parameters. Incategory no longer searches any subcategory automatically, but you can now add multiple category pagenames manually.

Since <tvar|ver></> Regular expression searches are supported for intitle:
 * intitle:/regex/, intitle:/regex/i

Everything written in the 1>#Regular expression searches</>|#Regular expression searches is also valid for these searches, including warnings.

Deepcategory
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 1>Special:MyLanguage/Wikidata Query Service/Categories</>|SPARQL Category service from WDQS. Keywords are deepcategory or deepcat. Example:


 * deepcat:"musicals"


 * Find articles that are in Category:Musicals or any of the subcategories.

The DeepCat gadget that previously implemented the parameter was sunsetted in January 2020.

Note that some deepcat searches return incomplete results.

See bug <tvar|1></> for more details.

Linksto
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 { {FULLPAGENAME}}, e.g. .)

Linksto does not find redirects. It only finds [ [wikilinks]], even when they are made by a template.

It does not find a link made by a URL, even if that URL is an internal wiki link.

To find all wikilinks to a "<tvar|hcs>Help:Cirrus Search</>", if "<tvar|helpSearching>Help:Searching</>" and "<tvar|HS>H:S</>" are redirects to it:
 * 1) linksto: "Help:Cirrus Search"
 * 2) linksto: Help:Searching
 * 3) linksto: H:S

<tvar|linksto> </> finds articles that mention "<tvar|CirrusSearch>CirrusSearch</>" but not in a wikilink.

Hastemplate
You can specify template usage with <tvar|hastemplate> </>. 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.)

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.


 * <tvar|hastempquality> hastemplate: "quality image" </>, finds "<tvar|tempquality>Template:Quality image</>" usage in your default search domain (namespaces).


 * <tvar|hastportal> hastemplate: portal:contents/tocnavbar </>, finds mainspace usage of a "<tvar|tocnavbar>Contents/TOCnavbar</>" template in the Portal namespace.

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.

Inlanguage
For installations with the Translate extension, <tvar|inlang> inlanguage </> is important for highly refined searches and page counts.


 * inlanguage:  language code 

will produce search results in that language only.

For example


 * to count all Japanese pages on the wiki
 * all: inlanguage: ja


 * to filter out German and Spanish pages in the Help namespace
 * help: -inlanguage: de -inlanguage: es


 * to ignore Translate, and where English is the base language, add
 * inlanguage:en

Contentmodel
The <tvar|contentmodel> contentmodel: </> keyword allows to limit the search to pages of a specific content model. For possible models cf. cthandle>Special:MyLanguage/Content handlers</>|Content handlers. E.g.:


 * To see only JSON pages:
 * contentmodel:json

subpageof
To find sub-pages.
 * subpageof:  ParentPage 

For example


 * To find all subpages of CirrusSearch.
 * subpageof:CirrusSearch


 * Use double quotes if the parent page contains spaces.


 * subpageof:"Requests for comment"

Articletopic
The <tvar|1> articletopic: </> keyword allows filtering search results by topic. For possible topics see <tvar|2></>.

E.g. <tvar|1> articletopic:books </> will filter the search results to articles about books.

<tvar|1> articletopic:books|films </> will filter to articles about books or films.

<tvar|1> articletopic:books articletopic:films </> will filter to articles which are about both books and films.

Only mainspace articles belong into topics, and topics are only available on Wikipedias. 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).

Topic models are derived via machine learning from <tvar|1>ORES</>. Any given article receives a score on dozens of different topics, and therefore may appear under different keywords. For instance, the article on Albert Einstein may appear as a "physics" article and a "biography" article. All Wikipedias have scores available -- some have local-language topic models that have coverage on all articles. 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. 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.

Topic-related search data is updated weekly, so recently created articles might not show up in topic-based search queries.

Page weighting
Weighting determines snippet, suggestions, and page relevance. The normal weight is one. Additional weighting is given through multipliers.

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.

Morelike

 * morelike:page name 1|page name 2|...|page name n


 * Find articles whose text is most similar to the text of the given articles.
 * morelike:wasp|bee|ant
 * Find articles about stinging insects.
 * morelike:template:search|template:regex|template:usage
 * Find templates about regex searching for template usage on the wiki.

<tvar|more> morelike </> is a "greedy" keyword, meaning that it cannot be combined with other search queries. If you want to use other search queries, use <tvar|morethis> morelikethis </> in your search:
 * morelikethis:bee hastemplate:"featured article"
 * Find articles about <tvar|biz>bees</> that also have the "<tvar|tmpl>featured article</>" template.

The <tvar|morelike> morelike: </> 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:


 * <tvar|1> cirrusMltMinDocFreq </>: Minimum number of documents (per shard) that need a term for it to be considered.


 * <tvar|1> cirrusMltMaxDocFreq </>: Maximum number of documents (per shard) that have a term for it to be considered.


 * <tvar|1> cirrusMltMaxQueryTerms </>: Maximum number of terms to be considered.


 * <tvar|1> cirrusMltMinTermFreq </>: Minimum number of times the term appears in the input to doc to be considered. For small fields (<tvar|title> title </>) this value should be 1.


 * <tvar|1> cirrusMltMinWordLength </>: Minimal length of a term to be considered. Defaults to 0.


 * <tvar|1> cirrusMltMaxWordLength </>: The maximum word length above which words will be ignored. Defaults to unbounded (0).


 * <tvar|1> cirrusMltFields </> (comma separated list of values): These are the fields to use. Allowed fields are <tvar|title> title </>, <tvar|text> text </>, <tvar|auxtext> auxiliary_text </>, <tvar|opening> opening_text </>, <tvar|headings> headings </> and <tvar|all> all </>.


 * <tvar|1> cirrusMltUseFields </> (<tvar|true> </>|<tvar|false> </>): use only the field data. Defaults to <tvar|false2> </>: the system will extract the content of the <tvar|text2> </> field to build the query.


 * <tvar|1> cirrusMltPercentTermsToMatch </>: The percentage of terms to match on. Defaults to 0.3 (30 percent).

These settings can be made persistent by overriding <tvar|cirrusmlt> </> in hlpsysmsg>Special:MyLanguage/Help:System message</>|System message.
 * Example: <tvar|1> </>

Prefer-recent
Adding <tvar|pr> prefer-recent: </> anywhere in the query gives recently edited articles a slightly larger than normal boost in the page-ranking rules.

Prefer-recent is only applied when using the default <tvar|1> </> 2>#Explicit sort orders</>|sort order.

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 <tvar|pr2> prefer-recent:0.6,160 .</> This plays well with other page ranking rules, and is intended for most searches.

You can manipulate the rules: <tvar|pr-boost> prefer-recent:boost,recent </>

Technically "boost" is the proportion of score to scale, and "recent" is the half life in days.

The boost is more than the usual multiplier, it is an exd>w:Exponential_decay</>|exponential boost.

The factor used in the exponent is the time since the last edit.

For example
 * prefer-recent:,7

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.

For a simple "sort by date" in highly refined search results, where page ranking and boosting are largely meaningless, just boost the entire score.
 * prefer-recent:1,7 (weeks)
 * prefer-recent:1,1 (days)
 * prefer-recent:1,0.0007 (minutes)
 * prefer-recent:1,0.0001 (8.64 seconds)
 * prefer-recent:1,0.00001 (seconds)

Boost-templates
You can boost pages' scores based on what templates they contain. This can be done directly in the search via <tvar|bt> </> or you can set the default for all searches via the <tvar|cbt> </> message. <tvar|btempty> </> replaces the contents of <tvar|cbtempty> </> if the former is specified. The syntax is a bit funky but was chosen for simplicity.

Like prefer-recent, boost-templates is only applied when using the default <tvar|1> </> 2>#Explicit sort orders</>|sort order.

Some examples:


 * File:boost-templates:"Template:Quality Image|200%" incategory:china


 * Find files in the China category sorting quality images first.


 * File:boost-templates:"Template:Quality Image|200% Template:Low Quality|50%" incategory:china


 * Find files in the China category sorting quality images first and low quality images last.


 * <tvar|tqpop> File:boost-templates:"Template:Quality Image|200% Template:Low Quality|50%" popcorn </>
 * Find files about popcorn sorting quality images first and low quality images last. Remember that through the use of the <tvar|sbt1> </> message this can be reduced to just <tvar|popcorn> </>.

Don't try to add decimal points to the percentages. They don't work and search scoring is such that they are unlikely to matter much.

A word of warning about <tvar|csbt> </>: if you add really really big or small percentages they can poison the full text scoring. Think, for example, if enwiki boosted featured articles by a million percent. Then searches for terms mentioned in featured articles would find the featured articles before exact title matches of the terms. Phrase matching would be similarly blown away so a search like <tvar|bnws> </> would find a featured article with those words scattered throughout it instead of the article for Brave New World.

Regular expression searches
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.

These return much much faster when you limit the regexp search-domain to the results of one or more index-based searches.

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 develop a simple filter to generate the search domain for the regex engine to search:


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

The last example works from a link on a page, but <tvar|fullpagename>{ {FULLPAGENAME}}</> doesn't function in the search box.

For example: <tvar|exampleofsearch> Special:Search/insource:/regex/ prefix: </> exampleofsearch2>Special:Search/insource:/regex/ prefix:</>| finds the term regex on this page.

A query with no namespace specified and no prefix specified searches your default search domain, (settable on any search-results page, i.e. at ss>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 an HTML timeout, before completing the search.

A regex search actually scours each page in the search domain character-by character. By contrast, an indexed search actually queries a few records from a database separately maintained from the wiki database, and provides nearly instant results. So when using an <tvar|insource>insource://</> (a regexp of any kind), consider creating one the other search terms that will limit the regex search domain as much as possible. 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:


 * insource:"" with quotation marks, duplicating the regexp except without the slashes or escape characters, is ideal.


 * intitle (without regex search), incategory, and linksto are excellent filters.


 * hastemplate: is a very good filter.


 * "word1 word2 word3", with or without the quotation marks, are good.


 * namespace: is practically useless, but may enable a slow regexp search to complete.

To test a bare regexp query you can create a page with test patterns, and then use the prefix parameter with that fullpagename.

The match will be highlighted.

It searches that page (in the database) and its subpages.

Search terms that do not increase the efficiency of a regexp search are the page-scoring operators: morelike, boost-template, and prefer-recent.

Metacharacters
This section covers how to escape metacharacters used in regexp searches

For the actual meaning of the metacharacters see the [<tvar|link1>https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-regexp-query.html#regexp-syntax</> explanation of the syntax].

For example:


 * 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.


 * starting out to find again what you may have seen, like "wiki-link" or "(trans[in]clusion)" start with namespace and insource filters.

Refining with an exact string

 * refinining 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.

You can start out intending an exact string search, but keep in mind:


 * 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.


 * You are obligated to supply an accompanying filter.


 * You must learn how to escape regex metacharacters.

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.


 * 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/.


 * 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.


 * You can't mix methods, but you can concatenate them.

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.


 * <tvar|pntemp> </> instead of <tvar|pntemp-late> </>
 * <tvar|literal> </> is as good as <tvar|literal2> </>
 * But <tvar|thisfails> </> always.
 * And <tvar|thisdepends> </>. It finds the <tvar|vvv> </> literally, which is not the <tvar|slash> </> you probably wanted.

Backslash-escape using insource:/regexp/ allows escaping the " and / delimiters, but requires taking into account metacharacters, and escaping any:


 * To match a <tvar|slash2> </> delimiter character use <tvar|vvv2> </>.


 * To match a <tvar|quote> </> delimiter character use <tvar|slashquote> </>.


 * The escaped metacharacters would be <tvar|grawlix2> </>.


 * The equivalent expression escaped with double-quotes is <tvar|grawlix3> </>.

The simplest algorithm to create the basic string-finding expression using insource:/"regexp"/, need not take metacharacters into account except for the " and / characters:


 * 1) Write <tvar|str_ing> </> out. (The /" delimiters "/ are not shown.)


 * 1) Replace <tvar|doublequote> </> with <tvar|slashdoublequote> </> (previous double-quote: stop, concatenate, quote restart).


 * 1) Replace <tvar|slash4> </> with <tvar|vvv3> </> (stop, concatenate, start).


 * 1) You get <tvar|insource> </>, showing concatenation of the two methods.

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. 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. For example both of these patterns target a character that is either a dash or a right square bracket or a dot: <tvar|code1> </> or <tvar|code2> </>.

For general examples using metacharacters:


 * <tvar|insource0> insource:"2+2=4" insource:/"2+2=4"/ </> matches "2 + 2 = 4", with zero spaces between the characters.


 * <tvar|insource01> insource:"2 + 2 = 4" insource:/2 ?\+ ?2 ?= ?4\./ </> match with zero or one space in between. The equals = sign is not a metacharacter, but the plus + sign is.
 * insource:"<tag>[ [link|2\3?]]\</tag>" insource:/"<tag>[ [link|2\3?]]< "\/" tag>"/

There are some notable differences from standard regex metacharacters:


 * The <tvar|code1> </> or <tvar|code2> </> are not reserved for matching a newline. To search for a string that contains a newline, you can do a search like <tvar|1> </> which means not a curly brace, then two curly braces, then any two characters except a curly brace, space, or pipe, then a <tvar|2></> tag.  The "any character except" will include a newline in the search.  Note thas this search was designed only to match to the following string:


 * The dot . metacharacter stands for any character including a newline, so .* matches across lines.


 * The number # sign means something, and must be escaped.


 * The ^ and $ are not needed. 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.


 * support a multi-digit numeric range like [0-9] does, but without regard to the number of character positions, or the range in each position, so <9-10> works, and even <1-111> works.

Regex on titles
The <tvar|1> insource </> keyword does only search the page source content.

To run regex searches on the title strings <tvar|1> intitle:/regex/ </> can be used.

Advanced example
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 <tvar|fmtcomma> </> having any allowable spaces around it, (it could be the same template call, or a separate one):



Note that the = sign in "fmt commas" is not needed but that adding it would not change the search results.

It is fast because it uses two filters so that every page the regexp crawls has the highest possible potential.

bounded
You can limit search to pages identified as being near some specified geographic coordinates.

The coordinates can either be specified as a, pair, or by providing a page title from which to source the coordinates.

A distance to limit the search to can be prepended if desired.

Examples:


 * neartitle:"San Francisco"
 * neartitle:"100km,San Francisco"
 * nearcoord:37.77666667,-122.39
 * nearcoord:42km,37.77666667,-122.39

boosted
You can alternatively increase the score of pages within a specified geographic area.

The syntax is the same as bounded search, but with boost- prepended to the keyword.

This effectively doubles the score for pages within the search range, giving a better chance for nearby search results to be near the top.


 * boost-neartitle:"San Francisco"
 * boost-neartitle:"100km,San Francisco"
 * boost-nearcoord:37.77666667,-122.39
 * boost-nearcoord:42km,37.77666667,-122.39

File properties search
Since MediaWiki 1.28, CirrusSearch supports indexing and searching of properties of files in the <tvar|file> </> namespace. This includes:
 * file media type
 * MIME type
 * size
 * width & height
 * resolution
 * bit depth for files that support these

filetype
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:



This list may be extended in the future. See also <tvar|mediatype> </> constants in <tvar|defines> </>.

The syntax of the search is: <tvar|filetype> filetype:{type} </>. Example:

<tvar|ftvideo> filetype:video </> - looks for all videos

The filetype search is not case-sensitive.

filemime
Matches file MIME type. The syntax is:

<tvar|filemime> filemime:{MIMEtype} </> - look for files of this MIME type

The argument can be quoted to specify exact match. Without quotes, partial matches to components of MIME type will be accepted too.

Examples:

<tvar|fmimg> filemime:"image/png" </> - look for files with MIME type exactly <tvar|imgpng> </>

<tvar|fnpdf> filemime:pdf </> - look for all PDF documents

The MIME type search is not case sensitive.

filesize
Search for file of given size, in kilobytes (kilobyte means 1024 bytes). The syntax is:

<tvar|fsnum> filesize:{number} </> or <tvar|fsgreater> filesize:>{number} </> - file with size at least given number

<tvar|fsless> filesize:<{number} </> - file with size no more than given number

<tvar|fsbetween> filesize:{number},{number} </> - file with size between given numbers

Examples:

<tvar|fs20> filesize:>20 </> or <tvar|fseq20> filesize:20 </> - files 20KB and bigger

<tvar|fsless1024> filesize:<1024 </> - files smaller than 1MB

<tvar|fs100k> filesize:100,500 </> - files with sizes between 100KB and 500KB

File measures
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:

<tvar|mn> {measure}:{number} </> - file with measure that equals to given number

<tvar|mng> {measure}:>{number} </> - file with measure that is at least given number

<tvar|mnl> {measure}:<{number} </> - file with measure that is no more than given number

<tvar|mnn> {measure}:{number},{number} </> - file with measure that is between given numbers

Where <tvar|measure> </> can be:

<tvar|filew1> filew </> or <tvar|filew2> filewidth </> - file width

<tvar|fileh1> fileh </> or <tvar|fileh2> fileheight </> - file height

<tvar|fres> fileres </> - file resolution (see above)

<tvar|fbd> filebits </> - file bit depth

Examples:

<tvar|fw800> filew:>800 fileh:>600 </> - files that are at least 800x600 pixels in size

<tvar|fb16> filebits:16 </> - files with 16-bit color depth

<tvar|fh100k> fileheight:100,500 </> - file between 100 and 500 pixels high

Wikibase search
The <tvar|1></> extension defines some search keywords in order to make it easier to search for certain Wikibase items. This is useful on <tvar|2></> and other Wikibase sites, including to search for images with Structured data on Wikimedia Commons.

See <tvar|1></> for details.

Cross-wiki search results
The search on Wikimedia projects includes iwsearch>Special:MyLanguage/Cross-wiki Search Result Improvements</>|improved cross-wiki search results (also known as interwiki search results, sister projects search results).

Explicit sort orders
In addition to the default relevance based sort CirrusSearch can provide results a few other explicit sort orders.

Specifying a sorting order other than <tvar|1> </> will disable all search keywords that affect scoring, such as <tvar|2> </> or <tvar|3> </>.

The keywords will still be parsed, but they will have no effect.

Sorting options are currently available from the MediaWiki API by providing the <tvar|1> </> parameter.

Sorting options can be manually added to a search URL by adding <tvar|1> </>, for example <tvar|2>https://www.mediawiki.org/w/index.php?search=foo&sort=last_edit_desc</>.

Valid sort orders include:

Interface for advanced options


The url>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 hlpadvsearch>Special:MyLanguage/Help:AdvancedSearch</>|here for the user manual.