If you have ever worked on a WordPress site with a large number of Posts and pages, you may have noticed WordPress search. Not working properly. This article describes why the default word press search cannot be extended and how to improve it. WordPress search methodby default, the default WordPress search performs the following queries in the database: Let me break down this query. First, use sql\calc\u found\u rows in the wp\u Posts table. That is, if there is no limit (to be provided later), how many results will be displayed in the next query? Then search the post\u title, post\u extract, and post\u content columns of the search term (in this case, \
On websites with many posts, the query took more than 20 seconds! This is not a scalable search option for high traffic sites. If you know your current understanding of the default search behavior for problem identification, it is important to explain why it is not suitable for some websites. WordPress searches only the \
A search tool for searching all content or custom content sets, not limited to the default defined post type or post field. Search tools provided with big data sets. When the traffic is large, the search tool will not cause server performance degradation. Next, we will learn about several solutions such as enterprise level external services and WordPress plug-ins. Algorithmic search algolia is an enterprise level search solution. It indexes posts and content in different places and returns the results to users. The feature set includes hash search, geographic location search, multilingual support, and synonym search. The
Algolia has several obvious advantages in comparing the search performance of sites with thousands of posts. The performance of the default word press search is as follows: Use the default WordPress search, and the search time is 7.43 seconds. But after algolia search, the result is almost
