Technical writers not posting their online help systems to a server that can be accessed and indexed by Google take the risk that their content becomes overshadowed by a third-party authority such as a support forum, said Joe Welinske, president of WritersUA.
In the same way that marketers have employed Search Engine Optimization (SEO) to improve the visibility of corporate web sites, online help that can be indexed by the search engines can provide faster answers to your customers and potential customers who are using Google, Yahoo, and Bing.
Here are my thoughts on the advantages of adding online help to a public location:
* Your content is given a much wider audience. Instead of limiting your readers to the people who have bought your product, your online help can be made available to anyone on the Internet. If a customer is struggling with a feature of your product, he or she could find the answer using Google’s search.
* The rules of support have changed. People expect quick and relevant answers with the widespread use of Google. Even with the possibility of social media sites superseding search engines, 92 percent of us still use search engines regularly. For example, when I have a problem with something I own, such as a DVD player, I might look up the problem in the printed user guide (if I still have it!), go to the manufacturer’s web site, or just type the name and model of the DVD player in Google. From my experience, Google often provides results that are as useful as the manufacturer’s support web site.
* Adding online help to a public server may benefit the company’s brand. For example, technical writer Sarah Maddox of Atlassian said that the company’s documentation web site attracts more traffic than the company’s corporate web site.
Why are writers not adding content to a public server? A few reasons:
* We are strapped for time. We don’t have the time to move our content to a server that can be accessed by Google’s webcrawlers that troll and index millions of web pages.
* Companies are reluctant to post detailed information to a public server. Conceivably, competitors could read the details of a feature in your online help and emulate it. Other companies may be worried of security breaches. But, in many cases, an external source may already be writing about a company’s product or service, said Welinske, who presented at the Jan. 17th meeting of the STC West Coast chapter.
* We lack the interest or knowledge. We may lack the interest or the know-how to port the content to a public-facing server. You need to consider the type of help you’re generating, the HTML tags that are embedded in each web page, and the formatting of your help.
Here are some best practices:
* Types of help. If you’re planning to post your help, certain file formats work well, such as web pages, WebHelp, and PDFs. Older file formats such as Microsoft Help (i.e. CHM files) or Flash are not the best choices.
* Optimizing meta-tags. To help webcrawlers index the content in your help, spend some time adding HTML tags to each topic. You need to double-check the title tags, review your keywords, and add relevant hyperlinks to your help. See my earlier blog post Making Online Help SEO Friendly.
* Social media. Incorporating social media in your online help is a way to foster an online community of users. See my earlier article on Marrying Twitter with User Documentation.
* Formatting and presentation. In his presentation, Welinske suggested you need to add navigation elements and company branding on all pages so that users know that the content is the company’s material. When you search for content using a search engine, it strips out the table of contents and index so that each page should identify that the content is the company’s documentation. In addition, include the last date that the content was updated and which version the documentation addresses.
* Register your online help with the search engines. It’s worthwhile registering your online help with Google, Bing, and Yahoo. You can register Google using Google Webmaster Tools. It’s also valuable to submit a XML sitemap of your online help to search engines. Sitemaps are a way to tell search engines about all of the pages in your online help.
WritersUA provides training to technical writers and hosts an annual conference.
Good presentation!
Cud says
I think you only face a risk of overshadowing it the VALUE your docs provide can be overshadowed by the VALUE of the crowd. There are some products for which I only go to the web for information — especially a HAT product I will not name right now. Crowd sourcing for those docs amounts to a band-aid pasted over a mortal wound. Of course the crowd overshadows bad documentation.
For some products the docs are so good (or the product so specialized) that I never look outside for help or information. No risk whatsoever for those products.
Then there are the hybrid cases… Information domains that get value from both specialized content and the crowd. Programming languages, and open source products usually fall into that category. The not-to-be-named HAT tries this approach as well. But again, if the docs are bad, this is just a band-aid… In this concrete case it really doesn’t solve anything. But for PHP (for example) it’s a real benefit. Yes, these hybrids are on the Web, and they should be. But not all content is general enough to achieve the critical mass that makes this a viable option.
Cud says
Yes, I agree. I’m not suggesting that all online help should be placed on public servers to be indexed. For some products, it would benefit customers, potential customers, and the company. In other cases, there may be few advantages. As always, the key is understanding your users.
mattrsullivan says
Chris is right, of course!
If your documentation is bad enough to reflect poorly on your product, then it ought not be put out for all to see. But then the issue of putting it online isn’t really the problem, eh?
Jonathan Wexler says
I think for the profession as a whole, making our content public, hooking it up to social media, even allowing collaboration Wiki-style, can help to give technical writers more recognition which they deserve. Moreover, I think this will lead to better products and an overall healthier software ecosystem as integration can move to the forefront and unnecessary complexity reduced. Companies must be more open, Apple notwithstanding, so it makes business sense. I imagine a grand pedia of documentation but I have drunk the coolaid.
RDesprez says
Hi Matt,
I agree! If your online help is poorly written and designed, it doesn’t really benefit anyone to post it to Google for indexing.