I am one of those historians who believes that history can (and should) be written for broader audiences than university professors and specialized scholars. And, I’m sure a similar opinion informs many decisions to publish scholarship on the web. But, just because something exists on the web doesn’t mean people will read it, and in a space of infinite pages, they may never even find it. I appreciated then the readings this week; they highlighted a certain deliberateness- a certain order- about the web that is not often apparent to the user. For example, the semantic markup of a page may not make any visual difference and may seem irrelevant to the viewer who lands on that page, but, as James Williamson points out, “browsers, accessibility devices, and other user agents will notice the difference.” How we tag our pages matters, especially to search engines that are charged with sorting endless amounts of data; knowing how to identify and define page content can help us direct traffic to our sites.
Good coding might help users to land on our sites, but then what? What do users do once landed? Do they even stay? Duckett cites Google Analytics as a great tool for learning more about those who visit our sites and how our sites are used. Analytics can help us understand how users are finding our sites, but perhaps more interestingly, Analytics can tell us what users are looking at once they are there (or not looking at.) Granted there are many factors that might encourage a viewer to stay or leave a site- it may not have the information that they were looking for or maybe the background color is the wrong shade of blue for some- but we can likely draw some conclusions from Analytics trends. Data can show which pages users are visiting most frequently and what pages they are spending the most time on; this can help us determine what users of our site are interested in and influence how we author our sites moving forward. By the same note, “Exit Pages” data can help us determine which pages are discouraging viewers and ultimately leading them to other sources. As a historian who believes that history can be written to appeal to broader audiences, I think that tools such as Analytics might help to achieve such an end. And wouldn’t it be great, as a historian, to write something that people actually read? To build something that people actually used?
Comment on Sara’s post.
I agree – the readings got me thinking about what happens after we get our pages up – the work doesn’t end there. Running something like Google Analytics will help us to improve our pages. It is much more complicated to create an effective webpage than I may have thought!
I think your point about the importance of analytics is a great one. Having proper meta data is so important and can also highlight the goals and intended audience of a website. From that standpoint, metadata is important not only for those finding your site but for the credibility and evaluation of any site.
The other useful thing that analytics does is it will show you what words people used in search engines to find you. Its hard to evaluate any of this before you actually have a website and it highlights the ongoing nature of doing scholarship on the web. It constantly has to be revised, updated, and adjusted.
Bravo for focusing on the analytics portion this week! I admit that I found it mildly intriguing, as I watched the video, and that it would be great to be able to add that to consideration as I build my website. However, I thought it was smarter for me to focus on code and design first. The analytics seemed to be a higher order function that could come later.
I completely agree with your thoughts on drawing people in, though. We must be thinking of this as we design our websites. What message are we trying to convey? What would we want people to walk away with? And most of all, how do we draw in an audience? We are talking about identify and identifying with history in another class of mine. Perhaps there is a way we can make audiences identify with the content on our sites? Would really like to talk with you more in person, and hope to see you at the help session tomorrow!
I think those are great questions to consider as we move forward…and the actual application and usage of analytics will come later- you know, once we actually have legitimate sites to analyze. I, like you, think that I just need to stick to the code and design for now.