Search Engine Optimization is not one of my favorite subjects to talk about. But I think this article is worth the time. It explains some of the challenges with voice search in very simple terms, and shows how voice search is growing and affecting the web.
Voice search is the fastest growing type of search, according to the keynote speech given by Behshad Behzadi at SMX West in March, Principal Engineer at Google Zurich. Already, 55% of teens and 41% of adults use voice search on a daily basis, and that number is only growing. The allure of voice chat is undeniable—it’s faster, it’s hands-free, it lets you multi-task, and (especially among millennials) it’s considered cool.
Voice chat is also becoming increasingly reliable as technology improves. In fact, two years ago word error rate was over 20%, but currentspeech recognition word error rate is as low as 8%—a huge leap in a short amount of time.
Last year we heard informal statements from several Google employees that mobile search queries would probably overtake desktop queries some time this year. Google just confirmed this has now happened.
The company says that “more Google searches take place on mobile devices than on computers in 10 countries including the US and Japan.” The company declined to elaborate further on what the other countries were, how recently this change happened or what the relative volumes of PC and mobile search queries are now.
Google groups tablets with desktops. So this is just smartphones and does not include tablets.
There’s also an interesting misalignment of this report with some Comscore reports.
CakePHP framework comes with the default PagesController which is an awesome out of the box way to build a website of mostly static pages. There is one rather annoying limitation though – no search option. If you need a website of mostly static pages with search functionality, you are out of luck. I spent a good chunk of time Googling (searching, eh?) for a solution and even talking to people in #cakephp IRC channel. The best alternatives, it turned out are listed in this StackOverflow answer:
There is no built in way to search static pages as they are just files on disk.
You have three options
Build a model to hold the data somewhat like a CMS so you can use mysql search.
google search for sites
the more hacky approach of reading the contents of all the pages and using preg_match() or similar on the contents to find matches.
The first option is probably the best depending on your use case. The second option is the easiest if its public facing content. The third option is a horrible idea
logstash is a tool for managing events and logs. You can use it to collect logs, parse them, and store them for later use (like, for searching). Speaking of searching, logstash comes with a web interface for searching and drilling into all of your logs.
It is fully free and fully open source. The license is Apache 2.0, meaning you are pretty much free to use it however you want in whatever way.
Read-later apps let you separate reading from finding, since they ideally happen with different mindsets and environments. This is necessary not because browsing aggregators, timelines, and feed readers is given too little time — people happily devote hours to it — but because the goal is to “get through” them and keep checking for new items, keeping readers in a skimming, active, dismissive mindset that’s hostile to attentive reading.
Instapaper’s usage data backed this up: there was almost no correlation between article length and number of saves on Instapaper. People routinely saved everything from three-paragraph Lifehacker posts to 10,000-word feature articles. The most-saved sites were usually just the most popular sites read by the kind of people who knew about Instapaper, not just the longest articles they found.
Nobody was saving Lifehacker posts because they couldn’t read three paragraphs right then: they saved them because they wanted to attentively read them, which wasn’t going to happen in their current context.