Showing posts with label search engine. Show all posts
Showing posts with label search engine. Show all posts

Why Every Site Needs a Search Engine

This article gives you two ways you can implement site-specific searches on your web page. Think of it as like having your own site-wide search engine. The question is: why should you do it?

It's simple, really: keywords used by your target market are part of your marketing resources. They help in market research, market development, and outreach marketing.

Search terms used by your visitors tell you what they want to see on your site. They also tell you how you should be marketing your site, what content you you should be producing, and how items should be listed for sale.

However, it can be tricky to make the most of this valuable information, and capturing it through various plug-ins is not always straightforward, or cheap.

Both these techniques are highly transparent, and free to use; my advice is to start using on-site search to monitor your existing market and build out your strategic keyword management process using the data that you gather as a result.

The Simple Search Solution

Use Google site search.

The background to this approach is represented by the following Google query:

  • site:searchengineland.com keyword research

This simple instruction tells Google to only return results for the site mentioned. This is convenient for site owners who want to check their coverage of keyword terms, but also very convenient if you want to provide a site specific search function.

The only caveat is that the pages must be indexed by Google.

Drop-In Javascript

There are two parts to the solution:

  • The HTML for the search form;
  • The Javascript to open the search.

Refinements on the following drop-in HTML and Javascript are many and various:

  • open the search in a new window;
  • open the search in an inline frame;
  • use various search modifiers to steer the result;
  • etc.
The one major advantage is that you'll see, in your web traffic statistics, the search terms being used to query Google. This means that you can check that people are coming to your site for the right reasons, and, crucially, check that you're still serving them to the best of your ability.

Here's the basic HTML:

<input id="search query" type="text" />
<button 
onClick="window.location.href=submitSearch(document.getElementById('search_query').value);">
Search</button>

All that this does is call the Javascript function submitSearch (defined below) with the contents of the text input (that's what all that getElementById code does), and then set the URL of the current page to the result of the submitSearch function.

Here's the Javascript (stick it at the top of the page, in the head section):

<script type="text/javascript">
function submitSearch(search_query) {
  search_domain = encodeURIComponent('site:your-domain.com');
  search_text = '+"' + search_query.replace(" ", "+") + '"';
  return search_domain + search_text;
}
</script>

This snippet forms the query out of the site and the query text, making sure that it is safe for use in a URL. Important: you should replace your-domain.com with your own domain.

The result is a Google search page, containing results for the keywords typed in by the visitor, restricted to pages from your site. In your logging, you will then see an Exit with the URL, inclduign the keywords.

Note that this doesn't work for sub-domains terribly well; so, for it to work, you will need to buy your own domain name, even if you only use it to point to Blogger!

More Advanced Options

Create a Google Custom Search engine, and add it to your site.

There are a few pre-requisites:

  • Your site is registered in Search Console;
  • You have Google Analytics set up.

The process is relatively painless, if a little technical. However, as always, the Google help on the topic is pretty good, and as long as you can edit your web site HTML, it should be fairly straightforward.

A big plus for bloggers, especially, is that it can be monetised via AdSense, too.

Tip: You get a bit more power, and advanced analytics (thanks to integration with Google Analytics and Search Console) including the ability to use sub-domains.

So, What Now?

The worst thing you can do is nothing.

At a minimum you need to give your site users a decent way to search your content for something that is meaningful to them. The next worst thing would be not to track the things they look for.

Google has tried to make this a bit more opaque, in the name of privacy. They hide the content of query strings made by users who are logged into their Google account, for example. However, you should attempt to get as much search data from your own site as possible.

Why?

The reasoning is simple: if a visitor comes to your site, looking for something specific and can't find it, it's your responsibility to make sure that you supply it.

This is how market research operates. Strategic keyword management - treating your pool of available SEO friendly keyword phrases as a valuable business resource - relies on market research.

Without it, you're just throwing spaghetti at the wall, hoping that some of it sticks.

Friday, 20 January 2017

Why Search Engine Privacy is bad for Search Context

Mention search, and a discussion of privacy usually isn't far behind.

Whether it's Google's (in my opinion unnecessary) masking of search queries for logged-in users, or concerns about using your browsing history to suggest products or even web sites you should visit, it seems everyone has an opinion.

Now search engines are starting to use enhanced privacy in their market differentiation.

Here's how Search Engine Journal's Matt Southern ("Qwant, a French Search Engine, thinks it can take on Google.") puts it:
Like search engine DuckDuckGo, Qwant’s competitive advantage is privacy. It protects users’ privacy by not tracking what they’re doing or searching for online. Qwant doesn’t use cookies, collect browsing data, or do any kind of data profiling.
Sounds great. My privacy is protected.

But that also means that the search engine doesn't know anything about me.

It doesn't know where I am located. Nor does it know the kinds of sites and search results that I've visited in the past.

In fact, all that the search engine has to go on is the page I visited last (the HTTP Referrer) and the query I've just entered.

Search Engine Context, Choice & Privacy


The job of a search engine is to act as a librarian/gatekeeper for all the content in its index.

Whether the engine is responsible for finding a product (i.e. Amazon, eBay, etc.), a person (i.e. LinkedIn, Fiverr, Facebook, etc.) or a resource (Google, Yahoo, Bing, Qwant, DuckDuckGo, et al), the users -- you and me -- expect a result list that contains the most relevant, highest quality, useful and valuable items that they know about.

But what's useful and valuable to me, might not be useful and valuable to you for the same search query.

It's to be hoped that a real world librarian, when asked for a "romance" book, isn't going to give the same recommendations to a teenage girl as they do a middle-aged housewife.

By the same token, knowing the search context is vital to a search engine's success. Building a competitive advantage out of treating all queries (with the same keyword phrase) as identical, to my mind at least, misses the point.

Enhanced privacy has the power to remove context, and thereby render results less relevant to the end user, leading to lower quality results.

It won't just hit organic search, either. It's across the board -- taking paid inclusion and sponsored entries as well as the various AdSense / AdWords style PPC services into account, too.

Squaring the circle requires giving end users the chance to activate more private -- i.e. context-restricted -- browser sessions. It's one area where I agree with Alphabet: making users login to get the most out of a search engine like Google is a good thing.

At the same time, giving users the option to start a private browsing session also solves a lot of the issues that Qwant and DuckDuckGo appear to be building their entire competitive advantage upon.

However, users need to both be educated, and use the private browsing features, as well as encouraged to view access to things like location, language, browsing data and subsequent data profiling as a way to help the search engine better serve their needs.

A Simple Example of Search Context


One example is the "near me" query. As in: "bank near me".


  • My usual logged-in Google session gives me a list of banks that I am a customer at, near my location.



  • Qwant gives me a list of reasonably random US based sites that include the term "bank near me" in their web page. None of them are "near me".



  • A private browsing session with Chrome, using Google, gives me a slightly different list of banks near me -- probably because it doesn't have access to my browsing or search history, so doesn't know which one I favour.


That's the effect of removing context.

As mobile search becomes ever-more popular, the chances of using, say a search engine like Qwant, and getting a reasonable local search result seem, if not remote, then at least less likely.

It's not a reason to drop privacy concerns completely, but it is an argument for education and choice over blanket removal of all search context; something that Qwant ought to take into account if it wants to challenge the established players going forward.