the new way of searching in magento 2
TRANSCRIPT
The new way of searching in Magento 2
E-commerce Search
Why on-site Search matters
Why on-site Search matters
• Searching has become the predominant method for users to find products on websites.
• The Search feature on website is immensely important as those searching have a better idea of what they want, compared to those who are browsing using the site links and navigation.
Searchers are almost twice as likely to convert than non-searchers in a given visit.
200+ M1 Search extensions on Magento Connect
M1 Search problems
Like, Full Text, Combined -
confusing for merchants.
Limited ability for extension
and customization
High degrees of code coupling
Weighting attributes only available in EE
Like, Combined are SLOW
Low Search Accuracy
M1 Search problems
FullText Search doesn’t support partial phrase
matching
MyISAM FullText by default ignores
words under 4 characters
There is no SOLR 4.*
support for EE version
MyISAM FullText has a list of ignored
words
Others
Community Feedback
https://github.com/magento/magento2/issues/622
Community Feedback
https://github.com/magento/magento2/issues/622
E-commerce Search
Deep Dive
The 12 Query Types
Identified during large-scale usability study of e-commerce search made by Baymard Institute
5 essential query types
1. Exact2. Product Type3. Feature4. Thematic5. Relational Searches.
Users can get by with basic e-commerce search when these 5 query types are supported. Conversely, failing to support any of these core query types will result in a defective search experience.
New way of Searching
Declarative Search
Declarative search. Request parts
1Filters
2Queries
3Aggregation
1. Exact matching2. Binary yes/no searches
1. Full text searches2. Relevance sorting
1. Faceted Search
Declarative Search. Queries
app\code\Magento\CatalogSearch\etc\search_request.xml
Declarative Search. Filters
app\code\Magento\CatalogSearch\etc\search_request.xml
Declarative Search. Aggregations
app\code\Magento\CatalogSearch\etc\search_request.xml
Search Service Contract
Basic workflow
Simple Example
1. User inputs search request into the quick search form. For example: “gold iPhone“
2. Search request comes to back-end and Magento fulfill \Magento\Search\Api\SearchInterfaces::search(SearchCriteriaInterface $searchCriteria)
3. Implementation reads declaration for current search request (Quick Search) .
4. Add Searchable attributes including custom attributes.Add Filter queries for visibility, price, category, colorAggregations for: price, color, category
Simple Example
5. Bind user's data:“gold iPhone" ->
<query xsi:type="matchQuery" value="$search_term$" name="search"> "visibility" -> Search (2) and Category and Search (4)
6. Clean unused queries and filters:price, category, color (filter)
7. Build final request
8. Search engine handles request and gets results
Simple Example. Result
Library vs Adapter
Adapters are supposed to be a set of factories which build generic search entities handled in client’s code
The right way to write own Search Extensions
SmartSearch - https://github.com/Sebwite/Magento2-SmartSearch
SmartSearch API usage
Performance
* Don’t consider values. Important just a trend
Magento meets Elasticsearch
1.7.* and 2.* versions supported
