Post by account_disabled on Feb 27, 2024 10:12:42 GMT
The dropped to just under half and table snippets only generated voice answers onethird of the time. This makes sense long lists and most tables are simply harder to translate into voice. In the case of tables some of these results were from different sites or in a different format. In other words the search generated a Featured Snippet and a voice answer but the voice answer was of a different type text for example and attributed to a different source.
Only of Featured Snippets in table format generated Kazakhstan Phone Number voice answers that came from the same source. From a search marketing standpoint text snippets are going to generate a voice answer almost out of times. Optimizing for textparagraph snippets is a good starting point for ranking on voice search and should generally be a winwin across devices. Special Knowledge Graph What about the Featured Snippets that didnt generate voice answers It turns out there was quite a variety of exceptions in play. One exception was answers that came directly from the Knowledge.
Graph on Google Home without any attribution. For example the question What is the nuclear option produces this Featured Snippet for me at least on desktop On Google Home though I get an unattributed answer that seems to come from the Knowledge Graph Its unclear why Google has chosen one over the other for voice in this particular case. Across the keyword set there were about keywords where something similar happened. Special to translate some searches as devicespecific help. For example How to change your name returns desktop results about legally changing your name as an individual. On Google Home I get the following Other searches from our list that triggered device help include How to contact Google How to send a fax online What are you up to Special Easter eggs Google Home has some Easter eggs that seem unique to voice search. One of my personal favorites the question.
Only of Featured Snippets in table format generated Kazakhstan Phone Number voice answers that came from the same source. From a search marketing standpoint text snippets are going to generate a voice answer almost out of times. Optimizing for textparagraph snippets is a good starting point for ranking on voice search and should generally be a winwin across devices. Special Knowledge Graph What about the Featured Snippets that didnt generate voice answers It turns out there was quite a variety of exceptions in play. One exception was answers that came directly from the Knowledge.
Graph on Google Home without any attribution. For example the question What is the nuclear option produces this Featured Snippet for me at least on desktop On Google Home though I get an unattributed answer that seems to come from the Knowledge Graph Its unclear why Google has chosen one over the other for voice in this particular case. Across the keyword set there were about keywords where something similar happened. Special to translate some searches as devicespecific help. For example How to change your name returns desktop results about legally changing your name as an individual. On Google Home I get the following Other searches from our list that triggered device help include How to contact Google How to send a fax online What are you up to Special Easter eggs Google Home has some Easter eggs that seem unique to voice search. One of my personal favorites the question.