SearchEkko is like a “related posts” widget for your blog, but it’s only visible to readers who arrive from a search engine. It uses each visitor’s search query to find the best-matching pages on your site.
For example, imagine that a user searches “new cars” at Google, and one of your posts shows up as a top hit. They then click the link and arrive at your site. The SearchEkko widget notices that the visitor arrived from a search engine, and that their query was “new cars”. It then finds all the best pages on your site for that query, and presents them to the user.
SearchEkko helps minimize your bounce rate by presenting visitors with your best, most relevant content, helping to ensure that they’ll find what they’re looking for. It also helps drive page views by finding related posts using each visitor’s real-time intent.
Try it out today! 🙂
- Activate the plugin through the ‘Plugins’ menu in the WordPress Admin section of your site.
How does SearchEkko work?
SearchEkko looks at each visitor’s HTTP referer header and identifies visitors coming from Google, Yahoo, or Bing. It then parses the referer for the search query. Finally, it uses the Yahoo BOSS index of your site to find other matching pages.
What happens if there aren’t any other matching pages for a search query?
The SearchEkko widget only displays if there are other top-ranking pages on your site for the query. It will display up to four other matching results.
How can I change how the SearchEkko widget looks?
You can modify the CSS of the widget as described here. This is the first release of the widget, but other options will be added soon. Stay tuned!
Why doesn’t the widget display on my site?
Firstly, remember that the widget only displays if you arrive at the site from a search engine and there are in-site results for your search query (in addition to the page you arrived at). Secondly, the widget requires a space at least 480px wide in order to display — this rules out most sidebars. (The reason for the width requirement is that it’s hard to display the matching results with anything narrower.) Otherwise, it looks like you’ve found a bug :). Please email me about it at noah at anoaharc.com!