1. When adding a friendly URL, we meant to make it “friendly" and “easy" for the user to read and remember, so avoid using specific characters and try to make it short.
2. Some characters are unsafe characters, they will be encoded, which end up making the URL really messy and ugly, e.g double quote (“) will be encoded to %22.

Some characters are reserved characters, which may not be supported by some features, based on our experience, “+" is not supported in “canonical" to redirect from http to https.​​

In the above source code, the URL http://rules.ssw.com.au:80/do-you-know-when-to-use-+1 [note: don't include as a hyperlink as it's a broken URL] will throw a 404 error rather than redirecting to https://rules.ssw.com.au:80/do-you-know-when-to-use-+1,but it works fine if the URL doesn't include “+", e.g. https://rules.ssw.com.au/do-you-know-when-to-use-plus-one.

A file name without spaces means that the search engine doesn't know where one word ends and the other one begins. This means that searching for 'monthly' or 'report' might not find this document.

MonthlyReport.docx

Bad Example: File name doesn't contain any separators between words

As far as search goes, using spaces is actually a usable option. What makes spaces less-preferable is the fact that the URL to this document will have those spaces escaped with the sequence %20. E.g. https://sharepoint/site/library/Monthly%20​Report.docx. URLs with escaped spaces are longer and less human-readable.

Monthly Report.docx 

Bad Example: File name uses a space to separate words

Underscores are not valid word separators for search in SharePoint, and not recommended by others. Also, sometimes underscores are less visible to users, for example, when a hyperlink is underlined. When reading a hyperlink that is underlined, it is oft​en possible for the user to be mistaken by thinking that the URL contains spaces instead of underscores. For these reasons it is best to avoid their use in file names and titles.

Monthly_Report.docx 

Bad Example: File name uses an underscore (snake_case) to separate words

A hyphen is the best choice, because it is understood both by humans and all versions of SharePoint search.

Monthly-Report.docx 

Good Example: File name uses a kebab-case​ to separate words

Add relevant metadata where possible

If a document library is configured with metadata fields, add as much relevant information as you can. Metadata is more highly regarded by search than the contents within documents, so by adding relevant terms to a documents metadata, you will almost certainly have a positive effect on the relevance of search results.​

Use descriptive file names and titles

The file name and title is regarded more highly by search than the content within documents. Also, the title or file name is what is displayed in the search results, so by making it descriptive, you are making it easier for people who perform searches to identify the purpose of your document.​

Related Rule

• Do you know how to use SharePoint search?
  
• Do you use dashes in your URLs?
  

• Use the categories (top)
• Use the filters (right navigation / faceted search)
• Use the scope to go wider
• Use the specific properties (see below)
• People - Use Delve indexed properties (i.e. Skills)
  

2. Search a specific property 

if you are familiar with the structure of the metadata in the content you're searching, y​ou​ can restrict your searches to a property with the syntax <property>:<search term>. E.g. to search the filename field for the term "report", you would use "filename:report".

Example of properties you can use (common ones);

• Filetype:
• CreatedBy:
• ModifiedBy:
  
• Title:
  

More: https://docs.microsoft.com/en-us/office365/securitycompliance/keyword-queries-and-search-conditions

Figure: Example of using Filetype: filter

3. Use Boolean OR and AND operators

Similar to Google and Bing, you can use OR and AND Boolean operators. E.g. "sharepoint AND search".

Note: OR and AND must be capitalized, however case is irrelevant for actual search terms.

4. Use an asterisk (*) wildcard for partial matches

This can be useful if you know that certain words are used together, e.g. Fire* will return results for FireBootCamp.

Note: Because of word stemming which is enabled by default in ​SharePoint 2019, 2016 and 2013, you do not need to use wildcards to find variations on words. For example, searching for "computer" will return results that contain "computers", so you do not need to search for "computer*". 

5. Use double quotes to find specific phrases

E.g. search for "social media" to make sure you get results for social media, as opposed to results that simply contain the words "social" and "media" in the same document.

Watch the video which explains how to view the version history for a page in SharePoint 2013 (Same as in SharePoint 2016). This allows you to see changes that were made to the page, as long as versioning is enabled in advance.

​​

Related rules

If you want to see how this is done in TFS, read Do you know the benefits of using source control?​

• Alt + N - New
• Alt + E - Edit
• Alt + U - Upload​
• Alt + M - Manage​
  
• Alt + S - Share
• Alt + Y - Synchronization​​
  

Read more at https://support.office.com/en-us/article/Keyboard-shortcuts-for-SharePoint-7dec847a-4f2a-47f6-9964-0ea1fba45160

​