Page length – do you make each page long – or go wide with more pages…?
Size matters – that’s what everyone says anyway.
Reading on a computer screen can be tiresome for some people and other people like to read from printed pages from a web site rather than directly from the screen.
So if you have lots to say how do you best represent that on “bottomless” web pages…?
I’m in two minds about this – on the one hand is the concept of “information chunking” where you keep like information together but separate from other information with nice and clear “drill-down” navigation structures to allow web visitors to get to the information that they want – on the other hand is the need to have significant “weight” to a page so that search engines can be persuaded to visit the site and rank it highly for the key words within the page.
In most cases it’s a call depending on the type of information represented – as an example - if the information is the end point of a web visitors search (such as a product detail page) then the longer is probably the better but if it’s a transition or gateway page (such as a menu of resources available) it makes more sense that a long list of resources - even if they were sorted or categorised - would not be a good idea.
So in the two examples above – the Product details would be long – while the List of Resources would best be represented by several pages each with it’s own category of resources.
In both instances it is important to write good content for search engine bait – which I’ll cover in another post.
Discuss this Article:
| Ask a New Question |
|To view or respond to a question, please select the appropriate link.|
This forum is moderated posts may take up to 48 hours to appear