- Joined
- Nov 18, 2014
- Messages
- 555
- Likes
- 345
- Degree
- 2
I've done a bit of research on this, and there seems to be a past consensus that Google probably devalues content that is hidden behind tabs or JavaScript/JQuery & CSS. Plenty of good reasons to collapse and expand certain details, and its often because they are non-essential.
But what about collapsing most of a page's essential information? Threads like this get me wondering. I have never in my entire life Google searched for something and wanted to read a 2,000 word article. Much less 5,000.
Table of contents at the top? Unless it starts floating in the sidebar, I'm going to scroll by, get several screens under, and then be annoyed that whatever long tail keyword brought me here is burred deep. Time is our commodity, and I don't see my generation getting any more patient when it comes to monstrosities of length.
For a broad skyscraper article or an article with extremely wide coverage, I would (personally) much rather see a short intro and then have most of the <h2>'s (or the <h3>'s under the <h2>'s) collapsed like this:
Or one of the "read more" fogs.
On the other hand, I definitely don't want to un-collapse everything inside a skyscraper article that I want to read most of... There are some I want to skim through, and the above would be annoying.
But, if I land on a massive informational page for tourism in the state of North Carolina, I'm almost never ever going to want to read more than 20% of it -- assuming it looked something like:
Intro: Why NC is awesome
- Top Attractions
-- Top Attractions for Couples
--- Top Attractions for Honeymooners
-- Top Attractions for Families
...
- Top Places to Visit
-- Top Tours
--...
---...
- Top Restaurants
...
- Top Hotels
- Famous local tattoo artists
...
- Statistics on the state
In terms of user experience, it seems to me that excessive use of collapsing could be very nice in some scenarios and err on obnoxious in others. And this seems like the type of distinction that would be very hard for an algorithm to judge. Besides bounce rates, maybe.
Is it worth collapsing large amounts of content that you can assume most people will only want one sub-heading of? Also, are there any "preferred ways" or "best practices" when it comes to collapsing content? I've just been using JQuery that changes display:none; and then animates.
But what about collapsing most of a page's essential information? Threads like this get me wondering. I have never in my entire life Google searched for something and wanted to read a 2,000 word article. Much less 5,000.
Table of contents at the top? Unless it starts floating in the sidebar, I'm going to scroll by, get several screens under, and then be annoyed that whatever long tail keyword brought me here is burred deep. Time is our commodity, and I don't see my generation getting any more patient when it comes to monstrosities of length.
For a broad skyscraper article or an article with extremely wide coverage, I would (personally) much rather see a short intro and then have most of the <h2>'s (or the <h3>'s under the <h2>'s) collapsed like this:
Or one of the "read more" fogs.
On the other hand, I definitely don't want to un-collapse everything inside a skyscraper article that I want to read most of... There are some I want to skim through, and the above would be annoying.
But, if I land on a massive informational page for tourism in the state of North Carolina, I'm almost never ever going to want to read more than 20% of it -- assuming it looked something like:
Intro: Why NC is awesome
- Top Attractions
-- Top Attractions for Couples
--- Top Attractions for Honeymooners
-- Top Attractions for Families
...
- Top Places to Visit
-- Top Tours
--...
---...
- Top Restaurants
...
- Top Hotels
- Famous local tattoo artists
...
- Statistics on the state
In terms of user experience, it seems to me that excessive use of collapsing could be very nice in some scenarios and err on obnoxious in others. And this seems like the type of distinction that would be very hard for an algorithm to judge. Besides bounce rates, maybe.
Is it worth collapsing large amounts of content that you can assume most people will only want one sub-heading of? Also, are there any "preferred ways" or "best practices" when it comes to collapsing content? I've just been using JQuery that changes display:none; and then animates.