My last few blog posts have been dedicated to the importance of visual and functional tests for on-site search. Before we wrap up the series, let’s review a few more ideas related to the back-end areas of your site not noticeable to the visitor:
- Algorithm: Test the underlying algorithm that powers your search. The algorithm determines what the search returns. Testing a new or updated algorithm highlights opportunities to improve. You can test sending users to different versions of a search algorithm, your own vs. one provided by a vendor.
- Vendor: Compare two different vendors in head-to-head competition. Take the guesswork out of which vendor tool works best for your site. You can use SiteSpect to compare searches provided by two different vendors.
Bringing It All Together
Now that you have the list of suggested tests, how do you move forward? As a first step, identify all the stakeholders on your optimization team. Then bring in other teams: cross-team collaboration is a critical element of prioritizing your roadmap and determining how to begin. Note the areas of search that are affected by each test so they don’t collide. For example, you don’t want to test relevancy when another part of the organization is testing the algorithm. The two are so closely related that changes to one may affect the results for the other.
We started the series with a refresher about the importance of testing on-site search. Then we provided some specific examples on what to test. Hopefully this has sparked a few ideas that you can put to work in your own organization. For your reference, here is the list of test ideas:
- Calls to Action
- Default Sort Order
- Customer Ratings
- Error Handling
- Vendor Testing
Are there any other topics you want to learn more about? If so, let us know on Twitter.