{"id":46,"date":"2006-09-27T02:42:52","date_gmt":"2006-09-27T08:42:52","guid":{"rendered":"https:\/\/www.visualfuture.com\/davetech\/2006\/09\/27\/more-on-yahoo-store-404-error-pages-and-google-analytics-this-time\/"},"modified":"2006-09-27T02:42:52","modified_gmt":"2006-09-27T08:42:52","slug":"more-on-yahoo-store-404-error-pages-and-google-analytics-this-time","status":"publish","type":"post","link":"https:\/\/www.visualfuture.com\/davetech\/2006\/09\/27\/more-on-yahoo-store-404-error-pages-and-google-analytics-this-time\/","title":{"rendered":"More on Yahoo store &#8220;404 error&#8221; pages and Google. (Analytics this time&#8230;)"},"content":{"rendered":"<p>Ok, now that everyone has had a chance to develop a &#8220;content rich&#8221; super-converting 404-error page, it&#8217;s time to put it to good use.<\/p>\n<p>And what better use for an error page, than to have it give us some indication of what link may have *caused* the error to occur in the first place. Thankfully, Alix Obitz posted <a title=\"Tip: Tracking 404 Pages\" target=\"_blank\" href=\"http:\/\/analytics.blogspot.com\/2006\/09\/tip-tracking-404-pages.html\">just how to do that<\/a> on the Google Analytics blog the other day. So now we can:<\/p>\n<ol>\n<li>Serve up a custom, &#8220;content rich&#8221; 404-error page in our Yahoo! store.<\/li>\n<li>Track which links are causing the error page to show up.<\/li>\n<li>Surely, you didn&#8217;t think we were done yet, did you?<\/li>\n<\/ol>\n<p>Once you have the new code in place, you&#8217;ll have access to the URLs the visitor was originally looking for. Depending on what the URLs look like, you may be able to determine the visitor&#8217;s original intent. A page URL of &#8220;http:\/\/mystore.com\/gensym23.html&#8221; is not going to reveal much about what type of content was at that URL previously. A URL of &#8220;http:\/\/mystore.com\/soft-blue-widgets.html&#8221; is much more helpful. (I know <a href=\"http:\/\/robsnell.com\/\">Rob Snell<\/a> has a page on &#8220;Why You Should Always Create New Pages from the &#8216;Contents&#8217; page&#8221; but I can&#8217;t find it right now&#8230; The tip is also on pg. 179 of his book, <a title=\"Starting a Yahoo! Business for Dummies\" href=\"http:\/\/www.amazon.com\/gp\/product\/0764588737\/sr=1-1\/qid=1139356210\/ref=pd_bbs_1\/103-9316914-0179869?%5Fencoding=UTF8\">Starting a Yahoo! Business for Dummies<\/a>)<\/p>\n<p>Anyway, when you *do* come across information laden broken links like the &#8220;soft-blue-widgets&#8221; example, one possibility is to go create a new page at that location that will redirect the visitor to an existing relevant page. This can be valuable for 2 reasons:<\/p>\n<ul>\n<li>Your visitor will now end up on a page even more relevant than your &#8220;content rich&#8221; 404-error page.<\/li>\n<li>You now have another *working* link to your site. (Your PageRank should skyrocket any minute now&#8230;)<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Ok, now that everyone has had a chance to develop a &#8220;content rich&#8221; super-converting 404-error page, it&#8217;s time to put it to good use. And what better use for an error page, than to have it give us some indication of what link may have *caused* the error to occur in the first place. Thankfully, &hellip; <a href=\"https:\/\/www.visualfuture.com\/davetech\/2006\/09\/27\/more-on-yahoo-store-404-error-pages-and-google-analytics-this-time\/\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">More on Yahoo store &#8220;404 error&#8221; pages and Google. (Analytics this time&#8230;)<\/span><\/a><\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0},"categories":[13,3,7],"tags":[],"_links":{"self":[{"href":"https:\/\/www.visualfuture.com\/davetech\/wp-json\/wp\/v2\/posts\/46"}],"collection":[{"href":"https:\/\/www.visualfuture.com\/davetech\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.visualfuture.com\/davetech\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.visualfuture.com\/davetech\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.visualfuture.com\/davetech\/wp-json\/wp\/v2\/comments?post=46"}],"version-history":[{"count":0,"href":"https:\/\/www.visualfuture.com\/davetech\/wp-json\/wp\/v2\/posts\/46\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.visualfuture.com\/davetech\/wp-json\/wp\/v2\/media?parent=46"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.visualfuture.com\/davetech\/wp-json\/wp\/v2\/categories?post=46"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.visualfuture.com\/davetech\/wp-json\/wp\/v2\/tags?post=46"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}