![\"about\"](\"http:\/\/garysieling.com\/blog\/wp-content\/uploads\/2013\/07\/about-578x525.png\")
<\/p>\nNormally I don’t like to write about “blogging,” but since website traffic generates some interesting data, it’s worth looking at it from a computer science perspective, to see the issues involved.<\/p>\n
By default, WordPress has two multi-valued fields associated with an article, “Categories” and “Tags.” Categories are treated as a closed, hierarchical set, and tags are an open, flat set. The software uses these and other attributes to generate lots of pages of dubious value (date-based archives, for instance). Coming up with the “right” tags is a bit of a puzzle, and I find my needs changing with time. For instance one might use this to tag posts with phrases not in the post that have some SEO value, or one might use it to generate a table of contents style index. Consider for instance the “Antiques” page on About.com:<\/p>\n
<\/p>\n
By default the \/tag\/[tag name] pages in WordPress are lists of posts, which is a poor choice, considering the amount of scrolling involved. Recently I made a few changes, modifying the URL from “\/tag\/[item]” to “\/examples\/[item],” which made it easy to separate the data:<\/p>\n
Before:
\n![\"tag-tag\"](\"http:\/\/garysieling.com\/blog\/wp-content\/uploads\/2013\/07\/tag-tag-578x63.png\")
\nAfter:
\n![\"examples-tag\"](\"http:\/\/garysieling.com\/blog\/wp-content\/uploads\/2013\/07\/examples-tag-578x74.png\")
<\/p>\n
I made simple modifications to the title boxes on the page:<\/p>\n
function get_custom_title($value) {\n $result = '';\n $value = trim(strtolower($value));\n if ($value == 'extjs examples' or\n $value == 'extjs 4 examples'\n ) {\n $result = ucwords($value);\n } else {\n $result = \"Gary's Guide To \" . $result = ucwords($value);\n }\n\n $result = str_replace(\"Extjs\", \"Ext JS\", $result);\n $result = str_replace(\"Ext Js\", \"Ext JS\", $result);\n $result = str_replace(\"Nlp\", \"Natural Language Processing\", $result);\n\n return $result;\n}<\/pre>\nSimilarly, I also added an introductory paragraph to each page (a generated sentence by default, or a paragraph for pages I care about). Each page now has a table of contents at the top, followed by post summaries, which you can see on the page about scraping<\/a>:<\/p>\n![\"scraping\"](\"http:\/\/garysieling.com\/blog\/wp-content\/uploads\/2013\/07\/scraping-578x486.png\")
<\/p>\n
Even though this still looks awful, you can see a noticeable boost in the metrics:
\n![\"metrics-before\"](\"http:\/\/garysieling.com\/blog\/wp-content\/uploads\/2013\/07\/metrics-before1-578x56.png\")
<\/p>\n
After:
\n![\"metrics-after\"](\"http:\/\/garysieling.com\/blog\/wp-content\/uploads\/2013\/07\/metrics-after-578x34.png\")
<\/p>\n
It looks like people are finding something useful and clicking away to it much quicker, since time on page and bounce rate are a lot lower (% exit is determined by how many visitors leave from this page vs the rest of the site – this is likely more dependent where people are landing when they start on my site). At this point there isn’t enough data to say much about per page numbers (considering that visits drop off exponentially, only the top two or three are meaningful). The best way to improve these pages now is likely to improve the selection of content, followed by better introductory text and article summaries, as well as fixing rendering issues.<\/p>\n","protected":false},"excerpt":{"rendered":"
Normally I don’t like to write about “blogging,” but since website traffic generates some interesting data, it’s worth looking at it from a computer science perspective, to see the issues involved. By default, WordPress has two multi-valued fields associated with an article, “Categories” and “Tags.” Categories are treated as a closed, hierarchical set, and tags … <\/p>\n