No XSLT in customizing the display of search results in 2013
The method of customizing the display of the search results in SharePoint 2013 search has improved drastically from SharePoint 2010. You will no longer have to go through the painful experience of modifying the thousand lines long XSL configuration setting in the tiny text editor on the core search results Web Part.
In SharePoint 2013 Search, the format and presentation of search results can be controlled by using display templates, which are just HTML templates with placeholders for the actual fields from the search results.
Clumsy Search Scope Rules Replaced by Query Transform/KQL
Search scopes and the clumsy rules to define them are gone in SharePoint Search 2013.
Instead of Search Scopes, SharePoint 2013 Search uses Results Sources to define a subset of searchable content. Result Sources use a query transform property to define the items that are included in the result source. You have the option to manually type in the query transform property, which is based on the Keyword Query Language (KQL) with some special syntax for placeholders and other operations or you can use the Query Builder user interface to define your query transform.
Improved Keyword Query Language
SQL Syntax support has been removed in SharePoint 2013 so Keyword Query Language (KQL) is now the preferred query language for search in SharePoint. The NEAR operator has been improved and the ONEAR and XRANK operators have been added to KQL.
New Search REST API
The SharePoint Search Query web service (http://server/site/_vti_bin/search.asmx) has been deprecated in SharePoint 2013, but a brand new Search REST API (http://server/_api/search/) has been added. The new REST service has many features and is very easy to use. As an example, to search for apples, the URL to execute the query would be as simple as: http://server/site/_api/search/query?querytext=’apples’