There was a time when speaking commands or questions to a machine and receiving an answer was something out of a science-fiction future. Well, for more than 110 million people in the US alone, that\u2019s their everyday present. According to Gartner, 30% of searches will be conducted via voice in 2020.\r\n\r\nVoice is the default interface for the more than 200 million smart speakers that Canalys predicts will exist by the end of 2019. But most smartphones today have installed some sort of digital assistant as well that allows for a voice interface. Research company Juniper Research estimates that by 2023 there will be 8 billion digital voice assistants in use. Most of them will be on smartphones, but smart TVs, wearables, smart speakers and other IoT devices will also experience significant growth in their usage through voice commands.\r\n\r\n\r\n\r\nThe digital voice assistant market is dominated by four big players:\r\n\r\n \tGoogle Assistant. This digital assistant comes installed with all Android phones as part of the Google app. Of course, it uses Google search to answer your queries. Other Google properties, like YouTube or Google Maps, are also closely tied to the assistant. Companies can expand on the Assistant\u2019s capabilities by developing Actions. These Actions can be used to interact with hardware (\u201cHey Google, turn off the lights in the living room\u201d) or with any other online service (\u201cHey Google, give me today\u2019s headlines for my favourite website\u201d).\r\n \tAmazon Alexa. Amazon\u2019s digital assistant is available most famously on Amazon\u2019s line of smart speakers, Echo. But in fact, it\u2019s available on over 20.000 devices, including not just smart speakers or wearables, but also TVs and even cars. Alexa also allows the creation of voice apps through Alexa Skills. Amazon even allows the possibility of premium subscriptions for Skills, so publishers can monetize their efforts by offering more personalization options or more detailed coverage. Alexa uses Bing as a search engine.\r\n \tApple Siri. What started in 2011 as an iOS app for the iPhone is now a full-fledged digital voice assistant embedded in all Apple products, including their line of smart TVs, speakers and wearables. Apple offers SiriKit to allow companies to extend their apps and allow voice interaction through Siri. The default search engine Siri uses is Google, although it can be configured to use a different search engine, like Duck Duck Go or Bing.\r\n \tMicrosoft Cortana. Microsoft\u2019s digital assistant is available in Windows natively, and in Android and iOS devices as a stand-alone app. Cortana seems to have been lagging in adoption against other digital assistants, and Microsoft\u2019s strategy seems to be to integrate Cortana with other digital assistants, rather than competing with them. Microsoft also allows the development of third-party Skills for Cortana, but only for the US market for now. Given their strategy shift, it\u2019s unclear whether Cortana Skills would become more widely available. Cortana uses Bing as a search engine. \u00a0\r\n\r\nVoice search is not just for mobile, it\u2019s for our everyday life\r\nThe early stages of voice search were triggered by the ever-expanding adoption of mobile phones. Google Now, the Assistants previous incarnation, was launched in 2012 and Siri launched even before, in 2011. This changed with the introduction of Alexa in 2014. The digital assistant was now living in a piece of hardware designed to never leave your home.\r\n\r\nThe digital assistants now are embedded in a wide range of devices, from phones to watches to TVs to cars. People can now interact with them in a wider range of situations. But the way we interact with the assistant is of course radically different from the usual text interface of search engines.\r\nHow voice search is different from text-based search\r\n\r\n \tMore complex and longer queries. Speech recognition has evolved a lot over the past few years, and it now allows for more complex queries than just a few years ago. This drives the user to employ a more natural language for their queries and commands.\r\n\r\n \r\n\r\n \tMore questions. According to research from seoClarity, more than 15% of voice searches start with how, what, where, when, why and who. This is due to the different interface compared to a text-based search engine.\r\n\r\n \r\n\r\n \tShort and concise answers. Even though the user may use longer queries to express what they want the assistant to do or look up, people expect short and clear responses.\r\n\r\n\r\n \tNo visual information hierarchy. We are used to employing and detecting visual cues to organize content and highlight the most important aspects of what we want to convey to the user. The content on a landing page should be re-thought for voice-only interfaces to identify what to highlight and how to do it without the visual cues a browser allows.\r\n\r\n\r\n \tWinner takes all. When using a search engine you can skim through the search results, and even though you would rarely reach the second page of the SERP, you may well click on a link below the first three top results. In a voice interface, people don\u2019t get a results page from where they can choose where to go. The digital assistant will return just one result.\r\n\r\n\r\n \tLocal search. Considering that between 30 and 40% of mobile searches are local queries, we can also expect a high percentage of queries in voice search to ask for local results.\r\n\r\n \r\n\r\n \r\nKeyword research for voice search\r\nThe main difference in doing keyword research for voice instead of text is that you will use much more natural language keywords. The way we speak is completely different than the way we type. We use natural phrases instead of a short string of keywords.\r\n\r\nTo discover which keywords to target, we need to use a semantic keyword research tool. Answer the public is the most commonly used tool in these cases. Insert your seed keyword and you will get a list of questions with that keyword. The data is presented first in a graph, which is pretty, but not very useful. Fortunately, you can download the data in a handy CSV.\u00a0\r\n\r\nTwinword\u2019s keyword research tool also has some useful filters to mine keyword ideas. You can filter the results by search intent and by keyword patterns, which would allow you to see only questions including your seed keyword.\r\n\r\nYou can also take note of the \u201cPeople also ask\u201d snippet in Google Search to uncover more keyword opportunities.\r\n\r\nIf you have a call center or a live chat or chatbot feature, mine the data from those conversations to find the most commonly asked questions.\r\n\u2018Near me\u2019 queries\r\nAs local queries make a big share of voice search, you can expect a lot of queries ending with the phrase \u201cnear me\u201d. As in: \u201cwhat\u2019s the best sushi near me\u201d, or \u201cwhat\u2019s the best gym near me\u201d. How to optimize for that? Local businesses should have their data updated in directories like Yelp, review sites like Tripadvisor and services like Kayak. For publishers, structured data is the answer.\r\nHow to optimize your content for voice search\r\nOptimize your site for mobile\r\nMost of the optimizations you should make to your site to ensure it performs well in mobile search will be beneficial for your voice search rankings as well. One of the most important factors is site speed. Whether the interface is voice or a mobile device, people expect fast results.\r\nUse AMP and structured data\r\nStructured data is key to help Google better understand and analyze your content so that it can better provide your audience with the answers they are looking for. You can help Google identify people, organizations, events, recipes, products, places.\u00a0\r\n\r\nAMP stands for Accelerated Mobile Pages. It\u2019s an open-source project launched by Google that restricts the functionality of web pages to increase their speed dramatically. AMP is often used with structured data, as that\u2019s what allows AMP pages to be featured in rich results on the search results page.\r\n\r\nAdditionally for publishers, displaying your content through the AMP format with structured data is one of the requirements to build an Action for Google Assistant.\r\n\r\nThere is a structured data schema called \u201cspeakable\u201d, currently in beta, that identifies sections on an article that are suited for text-to-voice playback. Content tagged with this schema will be identified by the Google Assistant as content that can be read through a Google Assistant-enabled device. The content is attributed to the source and the URL is sent to the mobile device of the user.\r\n\r\nThis structured data schema is only available for English-speaking users in the US, through publishers which are in Google News.\r\nAnswer user questions concisely\r\nAccording to research from Backlinko, the typical voice search result is just 29 words long, but the word count of a voice search results page is 2,312 words. This is not contradictory. In the first case, we\u2019re talking about the digital assistant answering a specific question or query. In the second case, the word count refers to the source of the answer. It\u2019s unclear whether Google favours long-form content as a mark of quality or if it\u2019s just that more content means there are more chances that a page is used as an answer to a query.\u00a0\r\n\r\nEither way, what these two stats combined tell us is that we need to think about the structure of our content so that we address the main ideas and key takeaways in short paragraphs that can be picked up by a voice assistant.\r\nWrite content that is easy to read and understand\r\nIf you want your content to be used in voice interaction it needs to be easy to read, and most of all, easy to understand to your readers. Remember that users won\u2019t be able to use visual cues or elements to better understand your content, like headlines or graphs.\r\n\r\nRemember that most queries will be done using natural speech-language as if they were having a conversation. Keep that in mind when developing your content and write conversationally when answering specific questions.\r\nAim for a high rank and featured snippets\r\nThis is a case of correlation and not causation. But there\u2019s evidence, as analyzed by Backlinko in their voice results research in Google Assistant, that more than 75% of voice search results come from the top three positions in the SERP, and that 40% came from a featured snippet.\r\n\r\nThis is just more proof that Google Assistant and other digital voice assistants will favor highly authoritative results to ensure they satisfy the user query on their first answer.\r\n\r\nAs featured snippets are already short answers to specific questions, it makes sense for the Assistant to use those.\r\n\r\nThis means that your optimization efforts for Google search will also have a measurable impact on how your content is used by a digital voice assistant.\r\nAnalyze and answer the user intent\r\nIdentify what\u2019s the user intent you are providing content for. Three main user intents can be answered through voice search. First is getting information: what is this? how do I do this?. The second is navigating: where is this?. And the third and final intent is acting: booking a table at a restaurant, buying a pair of shoes, get a list of all the music concerts taking place this weekend.\r\n\r\nL\u2019Oreal has been implementing a content strategy based on answering \u201cHow to\u201d questions. Their research shows that\u2019s what their users are looking for using voice search queries.\r\nBuild your trust and authority\r\nAs we saw, voice search is a winner-takes-all game. A digital voice assistant won\u2019t display a list of results but instead will provide directly an answer from those search results. As they can only provide one result, it makes sense that they tend to favor results from domains with high authority, even though they may not be the top result for that query.\u00a0\r\nLocal SEO is key for voice search\r\nA high volume of voice search queries is for local results. Optimizing for local SEO queries is not much a matter of churning out content with local keywords as maintaining a healthy and updated presence on certain services and directories. For example, local businesses should claim their listing on Google My Business, Bing Places for Business and Apple Maps Connect. You would then be able to have a greater degree of control of the information pulled by Google Assistant, Alexa, Cortana and Siri, which also uses data and reviews from Yelp.\r\n\r\nPublishers (and local business too) can implement structured data to highlight local elements in their content, the way Yelp and Ticketmaster do for their reviews and events. Create Google Actions or Alexa Skills to allow users to interact with your content\r\n\r\nAll the main digital voice assistants allow for the creation of voice apps to allow users to interact with your content through the assistants.\r\n\r\nGoogle takes it a bit further and automatically creates Actions for your content based on the structured data from your website. When that happens, your site owner, as specified in the Google Search Console data, would receive an email. Then you can claim your Action or disable it.\r\n\r\nFor example, Google will create an Action for podcasts based on their RSS feed that will allow users to find and play episodes on their devices through the Assistant. How-to guides, FAQs and recipes also use structured data markup to auto-generate Actions.\r\n\r\nFor news publishers, you have to already be included in Google News and use AMP and structured data in your articles to be eligible to auto-generate an Action.\r\n\r\nPublishers have already started to develop partnerships with Google to develop specialized Actions. Vogue launched a feature in 2017 where users could interact with the publication in Google Home to get more information about certain stories, told by the writers themselves.\r\n\r\nOther publishers, like Bloomberg or The Washington Post, have developed Alexa Skills that allow users to listen to daily briefs of the most important news of the day.\r\n\r\nThe Daily Mail went one step beyond, as they put their entire daily edition on Alexa. While other publishers record the audio themselves, in this case, the Daily Mail uses Alexa\u2019s automated text-to-speech capabilities. Another difference is that in this case, the Daily Mail makes this feature available only to their current subscribers.\r\nCan you analyze the impact of voice search?\r\nThe short answer is no. Not yet, at least. Even though Google has been saying since at least 2016 that they want to include voice search analytics to Google Search Console, the fact is that, as of today, there\u2019s no way to analyze voice search queries and results.\r\n\r\nThere are a few challenges that prevent Google and other analytics providers to deliver this feature:\r\n\r\n \tThe first is that natural language queries tend to be longer than keyword-based queries. And people will formulate what is essentially the same query using different words or sentence constructions. This means that the same query will have lots of low-volume variations, which makes it difficult to analyze and extract meaningful insights.\r\n \tThe second challenge is that voice search queries are often chained together, as if in a conversation. For example, you can ask a digital voice assistant: \u201cWho is Stephen Curry?\u201d. The assistant will return a summary of the NBA-star achievements. You can ask them \u201cHow tall is he?\u201d, and the assistant will know that you\u2019re referring to Stephen Curry. The problem gets more complicated when you realize that both queries could be answered by the assistant using two different content sources.\r\n\r\nAny voice search analytics functionality needs to take into account both challenges and:\u00a0\r\n\r\n \tProvide a way to cluster together similar queries, while at the same time giving analysts the freedom to explore what are those variations, to better understand the user\u2019s language.\r\n \tShow conversational trees to understand how users navigate the information and which queries keep them in our content and which ones result in the query being answered with content from other sites.\r\n\r\nPublishers that want to understand how voice search is impacting their online presence could start by analyzing the queries that get people on your site and look for longer, more conversational queries, as well as queries that are formulated as a question.\r\n\r\nYou could also conduct tests with different digital voice assistants to check what sources they use for their answers (voice assistants start their answers with \u201caccording to\u2026\u201d), and how that correlates with SERPs on Google search.\u00a0\r\nVoice search is already our present\r\nThe shift in consumer habits and the increasing role smart devices and digital assistants are playing in our everyday lives mean that voice search is not a thing of the future. Is already a present we need to deal with.\r\n\r\nPublishers need to take into account the interface change from text and visual references to just voice. It\u2019s a shift that changes the way people access and consume our content. The lack of reliable analytics to understand voice search performance makes this objective difficult to achieve. But, as with any other facet of search, it all comes down to developing trust with your audience through authoritative, high-quality content.