| 4:37 pm on Sep 13, 2006 (gmt 0)|
Certainly, as long as the divs and their content are written directly into the html mark-up, the entire page is indexable. I use this approach on one site and I know it works -- but I don't use it for full articles, just for small bits of extra information.
By putting everything on one page, you seriously limit the ability of Google (or any search engine) to focus on the "fine details" of the various articles. Also, you need to think through what will happen to a visitor who comes from a search and their search phrase is hidden by the default state of the page. And finally, beware of the total page size.
| 6:16 pm on Sep 13, 2006 (gmt 0)|
Thanks for the advice. Will go the static route instead, it's what I was going to do in the first place just wanted to make sure my concerns were valid.
| 8:29 pm on Sep 13, 2006 (gmt 0)|
That sounds like a great idea for the FAQ page instead of jumping up and down.
| 10:50 pm on Sep 13, 2006 (gmt 0)|
There's loads of free scripts available -- usually called something like "show hide div" or perhaps "show hide layers". A little searching will turn up many examples you can choose from. But it's not the purpose of the Google forum to teach DHTML, sorry.
| 10:46 am on Sep 17, 2006 (gmt 0)|
| 3:22 pm on Sep 17, 2006 (gmt 0)|
we use this technique extensively to display tabs that reveal specified content on large pages - saves scrolling, looks more profesh. no problem with getting spidered, indexed, or ranked.
I think the code we use is called tabpane: <url removed>
<See Forum Charter [webmasterworld.com]>
[edited by: tedster at 6:26 pm (utc) on Sep. 17, 2006]
| 7:02 pm on Sep 17, 2006 (gmt 0)|
1. The user must keep the mouse hovering over the selected link. That is, there is no way with CSS alone to keep the change in display stable so the window can be scrolled.
2. IE6 does not support child selectors.
In terms of accessibility, according to my current understanding, a screen reader will still read the contents of div with a display:none CSS rule