Search Tips: What makes a Scopus search complex?
Last updated on October 20, 2025
Boolean-type search is a powerful and precise tool that allows you to tailor your search criteria to obtain specific results. You can use Boolean search through both Basic Document Search and Advanced Search.
Previously, the legacy Scopus query interpreter was more lenient with complex string combinations, deeply nested proximity operators, extensive use of filters, incorrect usage of special characters and search fields, and intricate Boolean logic. With the recent system optimizations (Summer 2025) for more robust and efficient parsing, these complex query structures may on occasion be identified as syntactically incorrect or too ambiguous for effective processing if they trigger alerts that might harm our system, meaning we cannot guarantee they will run reliably on Scopus.
Please Note: Scopus has NO EXPLICIT limit on the length of queries or the number of Boolean operators. However, when using the Exclude or Limit to function (please use them responsibly)
To ensure your queries function correctly and efficiently, you may encounter some that must now be restructured and optimised to align with these enhanced parsing capabilities. Our team is available to assist you in optimizing your queries to meet current system requirements.
Contact Usopens in new tab/window: Reason: Using the Product. Subject: Optimize My Query
Below are a few tips to help you get started:
When you search in Scopus, it's important to understand how different types of documents are indexed and searched. This can explain why your search results might vary depending on the fields you use.
Core Documents: Documents fully indexed in Scopus. Scopus has complete information (titles, abstracts, authors, keywords, full reference lists, etc.), and all of it is searchable across various fields.
Secondary Documents (references to non-indexed items): Documents cited in a Core Document that are not fully indexed themselves. Scopus only knows about them because they were referenced, so think of them as citations to external works rather than fully cataloged items.
Why search results can differ depending on the field used:
- Incomplete data for Secondary Documents: Scopus may have only partial or inconsistent information about them (e.g., missing abstracts, keywords, or slight variations in titles).
Impact: If a term should be in a Secondary Document's abstract but Scopus doesn't have that abstract, the document won't appear in your results. The title you see for a reference may not be what Scopus searches in its index. - "REF" field (searching references): The REF field searches the cited references of a Core Document. It is "scoped": all your search terms must be found together within the same individual reference. It will not match terms spread across different references of the same document.
Example: REF ( "term A" AND "term B" ) only returns documents where both terms are in a single citation. If "term A" is in citation #1 and "term B" is in citation #2, the document is not a result. - "ALL" field vs. specific fields: The ALL field searches a very broad range of fields (e.g., Abstract, Title, Keywords, Authors, References). Searching specific fields individually (ABS, TITLE, REF) narrows the scope.
Impact: An ALL search often yields more results than individual field searches, because it covers a wider array of indexed content, including the primary content of Core Documents, which is more comprehensively indexed.
Key Takeaway: When searching, especially with the REF field, be aware that the information displayed for a reference might not be fully indexed or might be indexed differently. For comprehensive searches, using the ALL field is generally recommended, or carefully structure your REF searches to account for their scoped nature.
PUBYEAR: Searches using the PUBYEAR field typically yield more results because this field includes all "in-press" articles slated for a specific publication year (e.g., 2024) but lacking a finalized publication date.
PUBDATETXT: A free-text field containing the publication date exactly as supplied by the publisher. It is not standardized, so it only finds articles where the publisher's date string exactly matches one of your search terms (e.g., "january 2024", "february 2024").
Example A: Whole-year search
AF-ID ( 60000000 ) AND PUBYEAR
2,619 documents found
Example B: Whole-year search combining PUBYEAR and PUBDATETXT
( AF-ID ( 60000000 ) AND PUBYEAR = 2024 OR ( PUBDATETXT ( October AND 2024 ) OR PUBDATETXT ( November AND 2024 ) OR PUBDATETXT ( December AND 2024 ) ) ) OR ( AF-ID ( 60000000 ) AND PUBYEAR = 2024 AND ( PUBDATETXT ( July AND 2024 ) OR PUBDATETXT ( August AND 2024 ) OR PUBDATETXT ( September AND 2024 ) ) ) OR ( AF-ID ( 60000000 ) AND PUBYEAR = 2024 AND ( PUBDATETXT ( April AND 2024 ) OR PUBDATETXT ( May AND 2024 ) OR PUBDATETXT ( June AND 2024 ) ) ) OR ( AF-ID ( 60000000 ) AND PUBYEAR = 2024 AND ( PUBDATETXT ( january AND 2024 ) OR PUBDATETXT ( february AND 2024 ) OR PUBDATETXT ( march AND 2024 ) ) )
2,619 documents found (same as Example A)
Example C: Restricting results to a single quarter
AF-ID ( 60000000 ) AND PUBYEAR = 2024 AND ( PUBDATETXT ( january AND 2024 ) OR PUBDATETXT ( february AND 2024 ) OR PUBDATETXT ( march AND 2024 ) )
541 documents found
Some searches can take longer than usual and use a lot of processing time and capacity. A search with common terms, many OR groups, and many wildcards and proximity operators is complex and can require a lot of processing. Scopus searches may even time out, especially if the server is very busy.
Searches like this can also slow down simpler queries, so Scopus now tries to identify them in advance and processes them in an area that interferes less with other searches.
Please consider the following common Don'ts when constructing your queries:
Don'ts | Examples |
|---|---|
Don't run dot/slash/hyphen queries with wildcards. The dot/slash/hyphen will be stripped, and the query will fail. | TITLE-ABS-KEY (5.0*) is translated into (5 0*), and 0* is not allowed (it's a single-character wildcard). FUND-ALL (izp-2021/1*) is translated into (izp-2021 1*), and 1* is not allowed (it's a single-character wildcard). TITLE-ABS-KEY (fire-*) is translated into (fire *), and a standalone * wildcard is not allowed. |
Don't use a minus in front of a term, as (-) is a reserved character. A hyphen between terms is OK. | TITLE (-french) The query will fail or return no results. |
Don't use a proximity operator (W/n, PRE/n) with exact-match terms in curly braces { } on either side of the operator. This applies to a single word, a phrase, or a group of exact terms joined by OR. Use keywords or a loose phrase (straight double quotes) instead. Terms inside a proximity operator are matched loosely, including plurals and spelling variants. | (x) TITLE-ABS-KEY ( {nitrous oxide} W/2 emission* ) Not supported. No results, and no error is shown. (x) TITLE-ABS-KEY ( {Peak} W/1 {Concentration} ) Not supported. No results. (x) TITLE-ABS-KEY ( ( {Maximum} OR {Peak} ) W/1 ( {Concentration} ) ) Not supported. No results, or only some of the matching results. (/) TITLE-ABS-KEY ( "nitrous oxide" W/2 emission* ) Supported. (/) TITLE-ABS-KEY ( ( "Metabolite" OR "Plasma" OR "Serum" ) W/1 ( "Level" OR "Levels" OR "Concentration" ) ) Supported. |
Don't use wildcards with exact search unless you want to search for the exact character. | TITLE-ABS-KEY ({nitrous oxi*} will find ONLY nitrous oxi* |
Don't use double truncation, as it's not allowed. | TITLE-ABS-KEY (*daylight*) The query will fail or return no results. |
Don't use quotes around single terms, especially not if you're also using a wildcard. P.S. # is not a wildcard. | TITLE ("mou*") Don't use it! TITLE ("mou#") The query will fail or return no results. |
Don't use single quotes, as they don't do anything. For a phrase search, use double quotes. | TITLE-ABS-KEY ('daylight saving') Doesn't do anything. Use a loose phrase search instead: TITLE-ABS-KEY ("daylight saving") |
Don't use two single quotes to make a double quote, or faux quotes. Those are different characters. | TITLE-ABS-KEY (' 'daylight saving'') Doesn't do anything and will give unexpected results. |
The following factors require the search engine to do extra processing. Reducing them in a query may speed things up.
- Broad searches - If a search contains only many terms joined with OR, the engine must find all documents containing ANY of them. Unless limited by AND or other definitions (like a date range), the number of documents to consider becomes very large.
- Common terms - Terms that occur in very many documents also make searches very broad.
- Wildcards - Wildcards, especially the multi-character *, mean the engine must match every word that fits the pattern. This is less of a problem at the end of a word, but it still requires calculating all possibilities. Wildcards at the start of a word increase the possibilities exponentially (see examples below).
Examples
- contrast finds contrast, contrasts, and vice versa (about 69,000 results in article titles).
- contrast* finds both of these, plus (about 84,000 results in article titles) contrasting, contrasted, contrastain, contrastive, contrasteric, Contrastivism, contraste, ContrastRank, contrastivity, contrastable, contrastivist, contrastion, and various non-English terms.
- con* finds about 43,000,000 results.
Note: A hyphen is treated as punctuation and ignored unless it is in an exact phrase. Wildcards must be used with words because they cannot be standalone. When a hyphen is placed between a wildcard and a word, the wildcard is dropped.
- title-abs-key (*-art) is searched as title-abs-key (art)
- abs (iwv-*) is searched as abs (iwv)
- Proximity operators - "Within" and "preceding" (W/n, PRE/n) mean "AND, but within the specified distance." The engine must calculate the distance between the terms in every document containing them, and the longer the distance, the larger the calculation.
- Singular/plural forms - You do not need a wildcard for these. Scopus uses lemmatization (unless you use an exact phrase) for English words and most scientific terms.
For more guidelines, see How Best to Use Advanced Search.
Did we answer your question?
Related answers
Recently viewed answers
Functionality disabled due to your cookie preferences