Getting in Google's good graces

I use a number of techniques on my weblog, both in the code and how I create entries, that help Google get the most useful information out of my pages.

One of the constant topics that many webmasters and webloggers are concerned with these days is [Google][1], how to increase your site’s standing in Google’s eyes, and therefore drive more traffic to your site. I use a number of techniques on my weblog, both in the code and how I create entries, that help Google get the most useful information out of my pages.

[1]: “Google”

While I’ve [mentioned some in the past][2], the subject recently came up in [a thread on the TypePad User Group][3], and I shared some of my methods [in that thread][4]. At the request of both [Liza][5] and [Richard][6], who have also been posting about this topic, I’m re-posting my post (post-haste, though not post-mortem, and definitely not postpartum) here…

[2]: “Help search engines index your site”

[3]: “Increasing Blog/Site Traffic”

[4]: “A little bit of both, probably.”

[5]: “Getting Traffic to your site”

[6]: “Improve Your Blog’s Visibility on the Web”

> Still, I’m amazed to read that you had 1,000 per day BEFORE MS made you a web celeb (boo! to them). Do you think those hits came from your blogging subject or from special tactics you engaged in to increase your site traffic.

A little bit of both, probably.

First off, it’s not so much my subject, as my _lack_ of subject. ;) Because I’ve never really focused on any specific topic for my blog, and just randomly babble about whatever crosses my mind, that gives Google a _lot_ of potential keywords to pick up on.

Also, I’ve been at this for about three years now, so I’ve got a fairly large archive section, which also increases the probability of any given keyword turning up in a search.

As far as special tactics, there’s a few techniques I’ve picked up on over the years that seem to help (some of which you covered in your post).

1. **Descriptive headlines as a page title.** The title of a webpage scores very highly in Google’s ranking scheme, so I generally try to make sure that my post titles are descriptive of what I’m posting about (“Lord of the Rings Trailer” rather than “This is cool!”), and I make sure that the post title is included in the page title.

I believe that TypePad is set to include post titles in page titles for individual archives by default, but some weblog tools (including MovableType in its early stages, I believe, though I could be wrong) only include the site name for every page title, so instead of a site containing 1000+ differently named pages, you’d end up with a site containing 1000+ pages all named “My Weblog”, which doesn’t give Google nearly as much to work with.

2. **Setting a consistent structure for the code on each page.** As HTML was designed to emulate (though not visually replicate) the structure of a printed document, it includes various structural elements such as various levels of heading. As Google pays attention to these when it scans a document, it often helps to use them correctly.

In the past, rather than using the `

`, `

`, etc. elements for headlines, division markers, and so on, many sites would use `` tags to give their subdivision headings the look they wanted. Now that the `` tag has been deprecated and we can use CSS to style every element on a page the way we want, it’s good to return to using structurally correct markup. In addition to making a site much easier to code, it also assists Google in determining the structure, topic, and relevance of any given page.

For each individual archive page on my site, I’ve structured it as follows:

1. ``: website name > post title</p> <p> 2. `</p> <h1>`: website name</p> <p> 3. `</p> <h2>`: website ‘tagline’</p> <p> 4. `</p> <h3>`: post title</p> <p> 5. `</p> <p>`: post body</p> <p> 6. `</p> <h3>`: trackback</p> <p> 7. `</p> <h4>`: trackback source</p> <p> 8. `</p> <p>`: trackback body</p> <p> 9. `</p> <h3>`: comments</p> <p> 10. `</p> <h4>`: comment author</p> <p> 11. `<p&>`: comment body</p> <p> 12. `</p> <h3>`: comment posting form</p> <p> This gives each page a clearly delineated, easy to read structure that tells both the reader and Google which parts of the page are the most important and the most relevant to the topic of the page.</p> <p>3. **Link descriptively.** Simply, this involves using natural language for your links so that the link is descriptive to what it points to. For instance, saying “The new [Lord of the Rings trailer][7] is out!” instead of “You’ve gotta see [this][7]!” gives Google more information about what you’re linking to.</p> <p> This carries a double benefit, in that not only does it give Google better information about what you’re referencing, it also lets Google know more about what you’re linking to, which helps out whoever is on the target end of your link.</p> <p>4. **Alt text on all images.** This is important for a few reasons. First off, it lets Google know what each image is so that Google can include it more reliably in their image search feature. Secondly, though, and more importantly, it greatly improves the readability of your site for people with disabilities using specialized browsers to read the web.</p> <p> Blind users can use a “screen reader” to read websites — this is a specialized browser which translates the text to audio, and reads the page to them. Without alt text, all that screen reader can do is give them the name of the graphic, and might end up telling them something like “Image named funnypicture.jpg”. With alt text, they’ll instead hear something like “Image named Gimli falls off his horse”.</p> <p>5. **Use the excerpt field to create useable descriptions.** While keywords are no longer recognized by Google, another `<meta>` tag in the `<head>` section of your document still is (I think), which helps Google determine the topic of the page, and that’s the ‘description’ tag. What I’ve done is put this code into the `<head>` of each individual archive:</p> <p> `<meta title="description" content="<$MTEntryExcerpt>” />`</p> <p> I then make sure to take a moment to create an excerpt for each entry as I’m making it that relates to the topic of the post, rather than just relying on TypePad’s auto-generated excerpt (which generally just grabs the first _n_ words of each post).</p> <p>[7]: “The Return of the King trailer”</p> <p>Anyway, there’s a few of the things I do which seem to help my site visibility. Mostly, though, I think a lot of it just boils down to the fact that after three years of babbling, I give Google a lot to work with. ;)</p> </div><!-- .entry-content --> <footer class="entry-footer"> <span class="byline"><span class="author vcard"><img alt='' src='' srcset=' 2x' class='avatar avatar-49 photo' height='49' width='49' /><span class="screen-reader-text">Author </span> <a class="url fn n" href="">djwudi</a></span></span><span class="posted-on"><span class="screen-reader-text">Posted on </span><a href="" rel="bookmark"><time class="entry-date published" datetime="2003-12-02T00:12:12+00:00">December 2, 2003</time><time class="updated" datetime="2016-11-25T14:55:46+00:00">November 25, 2016</time></a></span><span class="tags-links"><span class="screen-reader-text">Tags </span><a href="" rel="tag">google</a>, <a href="" rel="tag">html</a>, <a href="" rel="tag">movable type</a>, <a href="" rel="tag">MovableType</a>, <a href="" rel="tag">search engine optimization</a>, <a href="" rel="tag">seo</a>, <a href="" rel="tag">Technology</a>, <a href="" rel="tag">traffic</a>, <a href="" rel="tag">typepad</a>, <a href="" rel="tag">weblogs</a></span><span class="comments-link"><a href="">2 Comments<span class="screen-reader-text"> on Getting in Google's good graces</span></a></span> </footer><!-- .entry-footer --> </article><!-- #post-## --> <article id="post-1538" class="post-1538 post type-post status-publish format-standard hentry category-uncategorized tag-google tag-movable-type tag-search-engine-optimization tag-seo tag-technology tag-tutorial tag-typepad tag-weblogs"> <header class="entry-header"> <h2 class="entry-title"><a href="" rel="bookmark">Help search engines index your site</a></h2> </header><!-- .entry-header --> <div class="entry-summary"> <p>Tips and tricks to help search engines index your site more intelligently. Written for, but not specific to, TypePad Advanced accounts.</p> </div><!-- .entry-summary --> <div class="entry-content"> <p>We all know that [Google][1] is god. Chances are you’ve used Google when doing a search on the ‘net at least once, if not daily, or many times a day. If not, then I’ve heard rumors that there are other search engines out there — though I haven’t used any in so long, I can’t really vouch for the veracity of that rumor. ;)</p> <p>[1]: “Google”</p> <p>I wanted to share a few tricks I use here to help Google (and other search engines) index my site, and to try to ensure that searches that hit my site get the most useful results.</p> <p>All of the following tips and tricks do require access to your source HTML templates (in TypePad, you’ll need to be using an Advanced Template Set). While I’m writing this for an Advanced TypePad installation, the tips will work just as well in any other website or weblog application where you have access to the HTML code.</p> <p>####Specify which pages get indexed, and which don’t####</p> <p>**What?** One of the most important pages on a weblog from a user’s point of view is the main page. It has all your latest posts, all the links to your archives, your bio, other sites you enjoy reading, webrings, and who all knows what else. However, from the perspective of a search engine, the main page of a weblog is most likely the single _least_ important page of the entire site!</p> <p>This is simply because the main page of a weblog is _always changing_, but search engines can only give good results when the information that they index is still there the next time around. I’ve run into quite a few situations where I’ve done a search for one term or another, and one of the search results leads to someone’s weblog. Unfortunately, when I go to their page, the entry that Google read and indexed is no longer on the main page. At that point, I _could_ start digging through their archives and trying to track down what I’m looking for — but I’m far more likely to just bounce back to Google and try another page.</p> <p>Thankfully enough, though, there’s an extremely easy fix for this that keeps everyone happy.</p> <p>**How?** One short line of code at the top of some of your templates is all it takes to solve the problem. We’re going to be using the [robots meta tag][1] in the head of the HTML document. The tag was designed specifically to give robots (or spiders, or crawlers — the automated programs that search engines use to read websites) instructions on what pages should or shouldn’t be indexed.</p> <p>[1]: “HTML Author’s guide to the Robots META tag”</p> <p>For the purposes of a weblog, with one constantly changing index page and many static archive pages, the best possible situation would be to tell the search engine to read and follow all the links on an index page (so that it finds all the other pages of a site), but not to index that page. The rest of the site, it will be free to read and index normally.</p> <p>That’s very easy to set up, as it turns out. The robots meta tag allows four possible arguments:</p> <dl> <dt>INDEX</dt> <dd>Read and index a page normally</dd> <dt>NOINDEX</dt> <dd>Do not index any of the text of the page</dd> <dt>FOLLOW</dt> <dd>Follow all the links on a page to read linked pages</dd> <dt>NOFOLLOW</dt> <dd>Ignore all links on a page</dd> </dl> <p>So, in order to do what we want, we add the following meta tag to our document, in the head section, right next to the meta tags that are already there:</p> <p> <meta name="robots" content="noindex,follow" /></p> <p>Now, when a search engine robot visits the index page of the site, it knows that it should _not_ index the page and add it to its database, however, it _should_ follow any links on that page to find other pages within the site. This way, searches that return hits for the site will be sure to find your archive pages for the information that is requested, rather than your front page, which may not have the information anymore.</p> <p><ins>Update:</ins> It turns out that this technique may have some side effects that I hadn’t considered, and might possibly not work at all. For more details, please scroll down to Anode’s comment and my reply in the comment thread for this post. Hopefully I’ll be able to dig up more information on this soon.</p> <p>####Fine tune what sections of a page get indexed####</p> <p>**What?** There is a proposed extension to the robots meta tag that allows you to not just designate which pages of a site get indexed, but also which sections of a page get indexed. I discovered this when I was setting up a shareware search engine for my old website, and have since gotten in the habit of using it. Now, this is not a formal standard, and I don’t know for sure which search engines support it and which don’t — the creator of this technique has [suggested it to the major search sites][2], but it is not known what the final result was.</p> <p>[2]: “How to prevent sections of your page from being indexed”</p> <p>Now, why would you want to do this? Simply this: on many weblogs, including TypePad sites, the sidebar information is repeated on every page of the site. There is also certain informational text repeated on every page (for instance, the TrackBack data, the comments form, and so on). This creates a lot of extraneous, mostly useless data — doubly so when that information changes regularly.</p> <p>By using these proposed tags, any search engine that supports them will only index the sections of a page that we want indexed, and will disregard the rest of the page.</p> <p>**How?** Because this is based on the robots meta tag discussed above, it uses the same four arguments (INDEX, NOINDEX, FOLLOW, and NOFOLLOW). Instead of using a meta tag, though, we use HTML comment syntax to designate the different sections of our document.</p> <p>For instance, every individual archive page on a TypePad weblog that has TrackBack enabled will have the following text (or something very similar):</p> <p>> **Trackback**</p> <p>> TrackBack URL for this entry:</p> <p>></p> <p>></p> <p>> Listed below are links to weblogs that reference (the name of the post)</p> <p>In order to mark this out as a section that we wanted the search engine not to index and not to follow (as the only link is to the page that the link is on), we would surround it with the following specialized tags:</p> <p> <!-- robots content="noindex,nofollow" --></p> <p> <!-- /robots --></p> <p>For example, I would change the code in the TypePad Individual Entry template to look like this:</p> <p> <mtentryIfAllowPings></p> <p> <!-- robots content="noindex,nofollow" --></p> <h2><a id="trackback"></a>TrackBack</h2> <p>TrackBack URL for this entry:<br /><$MTEntryTrackbackLink$></p> <p>Listed below are links to weblogs that reference <a href="<$MTEntryPermalink$>“><$MTEntryTitle$></a>:</p> <p> <!-- /robots --></p> <p> <mtpings></p> <p>The same technique can be used wherever you have areas in your site with content that doesn’t really need to be indexed.</p> <p>Now, as I stated above, this is only a proposed specification, and it is not known which (if any) search engines support it. It also requires a healthy chunk of mucking around with your template code. Because of these two factors, it may not be an approach that you want to take, instead simply using the “sledgehammer” approach of the page-level robots meta tag discussed above.</p> <p>However, I do think that the possible benefits of this being used more widely would be worth the extra time and trouble (at least, for those of us obsessive about our code), and I’d also suggest that should TypePad gain a search functionality, that these codes be recognized and followed by the (purely theoretical, at this point) TypePad search engine.</p> <p>####Put the entry excerpt to use####</p> <p>**What?** The entry excerpt is another very handy field to use in fine tuning your site. I believe that the field is turned off on the post editing screen by default, but it can be enabled by clicking on the ‘Customize the display of this page’ link at the bottom of the post editing screen.</p> <p>By default, the entry excerpt is used for two things in TypePad: when you send a TrackBack ping to another weblog, the excerpt is sent along with the ping as a short summary of your post; and it is used as the post summary in your RSS feed if you have selected the ‘excerpts only’ version of the feed in your weblog configuration. However, it can come in handy in a few other instances too. One that I’ve discussed previously is [in your archive pages][3]. However, the excerpt can also be used to help out search engines.</p> <p>[3]: “Tweaking TypePad templates”</p> <p>You may have noticed that when you do a search on Google, rather than simply returning the link and page title, Google also returns a short snippet of each page that the search finds. Normally, this text snippet is just a bit of text from the page being referenced, intended to give some amount of context to give you a better idea of how successful your search was. There is a meta tag that lets us determine exactly what text is displayed by Google for the summary, though — which is where the extended entry field comes in.</p> <p>**How?** We’re adding another meta tag here, so this will go up in the head section of your Individual Archives template. Next to any other meta tags you have, add the following line:</p> <p> <meta name="description" content="<$MTEntryExcerpt>” /></p> <p>Then save, and republish your Individual Archives, and you’re done. Now, the next time that Google indexes your site, the excerpt will be saved as the summary for that page, and will display beneath the link when one of your pages comes up in a Google search.</p> <p>So what happens if you don’t use the entry excerpt field? Well, TypePad is smart enough to do its best to cover for this — if you use the `<$MTEntryExcerpt$>` tag in a template, and no excerpt has been added to the post, TypePad automatically pulls the first 20 words of your post to be the excerpt. While this works to a certain extent, it doesn’t create a very _useful_ excerpt (unless you’re in the habit of writing extremely short posts). It’s far better to take a moment to create an excerpt by hand, whether it’s a quick cut and paste of relevant text in the post, or whether it’s more detailed (“In which we find out that…yadda yadda yadda.”). In the end, of course, it’s your call!</p> <p>####Use the Keywords####</p> <p>**What?** Keywords are short, simple terms that are either used in a page, or relate to the page. The original intent was to place a line in the head of an HTML page that listed keywords for that page, which search engines could read in addition to the page content to help in indexing.</p> <p>Unfortunately, keywords have been heavily abused over the years. ‘Search Engine Optimizers’ started putting everything including the kitchen sink into their HTML pages for keywords in an effort to drive their pages rankings higher in the search engines. Because of this, some of the major search engines (Google included) now disregard the ‘keywords’ meta tag — however, not all of them do, and used correctly, they can be a helpful additional resource for categorizing and indexing pages.</p> <p>**How?** One of the various fields you can use for data in each TypePad post is the ‘Keywords’ field. I believe that it is turned off by default, however you can enable it by clicking on the ‘Customize the display of this page’ link at the bottom of your TypePad ‘Post an Entry’ screen.</p> <p>Once you have the ‘Keywords’ field available, you can add specific keywords for each post. You can either use words that actually appear in the post, or words that relate closely to it — for instance, I’ve had posts where I’ve used the acronym WMD in the body of the post, then added the three keywords ‘weapons mass destruction’ to the keywords field. You never know exactly what terms someone will use in their search, might as well give them the best shot at success, right?</p> <p>Okay, so now you have keywords in your posts. What now? By default, TypePad’s templates don’t actually use the data in the Keywords field at all. This is fairly easy to fix, however.</p> <p>In your Individual Archives template, add the following line of code just after the meta tags that are already there:</p> <p> <meta name="keywords" content="<$MTEntryKeywords$>” /></p> <p>Then save your template, republish your site (you can republish everything, but doing just the Individual Archives is fine, too, as that’s all that changed), and you’re done! Now, the next time that a search engine that reads the keywords meta tag reads your site, you’ve got that much more information on every individual post to help index your site correctly.</p> <p>####Conclusion####</p> <p>So there we have it. One _extremely_ long post from me, with four hopefully handy tips for you on how you can help Google, and the rest of the search engines out there, index your site more intelligently. If you find this information of use, wonderful! If not…well, I hope you didn’t waste too much of your day reading it. ;)</p> <p>Feel free to leave any questions, comments, or words of wisdom in the comments below!</p> </div><!-- .entry-content --> <footer class="entry-footer"> <span class="byline"><span class="author vcard"><img alt='' src='' srcset=' 2x' class='avatar avatar-49 photo' height='49' width='49' /><span class="screen-reader-text">Author </span> <a class="url fn n" href="">djwudi</a></span></span><span class="posted-on"><span class="screen-reader-text">Posted on </span><a href="" rel="bookmark"><time class="entry-date published" datetime="2003-07-30T23:59:00+00:00">July 30, 2003</time><time class="updated" datetime="2016-11-25T14:29:02+00:00">November 25, 2016</time></a></span><span class="tags-links"><span class="screen-reader-text">Tags </span><a href="" rel="tag">google</a>, <a href="" rel="tag">movable type</a>, <a href="" rel="tag">search engine optimization</a>, <a href="" rel="tag">seo</a>, <a href="" rel="tag">Technology</a>, <a href="" rel="tag">tutorial</a>, <a href="" rel="tag">typepad</a>, <a href="" rel="tag">weblogs</a></span><span class="comments-link"><a href="">10 Comments<span class="screen-reader-text"> on Help search engines index your site</span></a></span> </footer><!-- .entry-footer --> </article><!-- #post-## --> </main><!-- .site-main --> </div><!-- .content-area --> <aside id="secondary" class="sidebar widget-area" role="complementary"> <section id="search-3" class="widget widget_search"> <form role="search" method="get" class="search-form" action=""> <label> <span class="screen-reader-text">Search for:</span> <input type="search" class="search-field" placeholder="Search …" value="" name="s" /> </label> <button type="submit" class="search-submit"><span class="screen-reader-text">Search</span></button> </form> </section><section id="archives-4" class="widget widget_archive"><h2 class="widget-title">Archives</h2> <label class="screen-reader-text" for="archives-dropdown-4">Archives</label> <select id="archives-dropdown-4" name="archive-dropdown" onchange='document.location.href=this.options[this.selectedIndex].value;'> <option value="">Select Month</option> <option value=''> January 2018 </option> <option value=''> December 2017 </option> <option value=''> November 2017 </option> <option value=''> September 2017 </option> <option value=''> July 2017 </option> <option value=''> June 2017 </option> <option value=''> May 2017 </option> <option value=''> April 2017 </option> <option value=''> March 2017 </option> <option value=''> February 2017 </option> <option value=''> January 2017 </option> <option value=''> December 2016 </option> <option value=''> November 2016 </option> <option value=''> March 2016 </option> <option value=''> December 2015 </option> <option value=''> November 2015 </option> <option value=''> July 2015 </option> <option value=''> June 2015 </option> <option value=''> April 2015 </option> <option value=''> March 2015 </option> <option value=''> February 2015 </option> <option value=''> January 2015 </option> <option value=''> December 2014 </option> <option value=''> November 2014 </option> <option value=''> October 2013 </option> <option value=''> September 2013 </option> <option value=''> July 2013 </option> <option value=''> June 2013 </option> <option value=''> February 2013 </option> <option value=''> January 2013 </option> <option value=''> December 2012 </option> <option value=''> September 2012 </option> <option value=''> July 2012 </option> <option value=''> June 2012 </option> <option value=''> December 2011 </option> <option value=''> November 2011 </option> <option value=''> October 2011 </option> <option value=''> September 2011 </option> <option value=''> July 2011 </option> <option value=''> June 2011 </option> <option value=''> May 2011 </option> <option value=''> April 2011 </option> <option value=''> March 2011 </option> <option value=''> February 2011 </option> <option value=''> January 2011 </option> <option value=''> December 2010 </option> <option value=''> November 2010 </option> <option value=''> October 2010 </option> <option value=''> September 2010 </option> <option value=''> August 2010 </option> <option value=''> July 2010 </option> <option value=''> June 2010 </option> <option value=''> May 2010 </option> <option value=''> April 2010 </option> <option value=''> March 2010 </option> <option value=''> February 2010 </option> <option value=''> January 2010 </option> <option value=''> December 2009 </option> <option value=''> November 2009 </option> <option value=''> October 2009 </option> <option value=''> September 2009 </option> <option value=''> August 2009 </option> <option value=''> July 2009 </option> <option value=''> June 2009 </option> <option value=''> May 2009 </option> <option value=''> April 2009 </option> <option value=''> March 2009 </option> <option value=''> February 2009 </option> <option value=''> January 2009 </option> <option value=''> December 2008 </option> <option value=''> November 2008 </option> <option value=''> October 2008 </option> <option value=''> September 2008 </option> <option value=''> August 2008 </option> <option value=''> July 2008 </option> <option value=''> June 2008 </option> <option value=''> May 2008 </option> <option value=''> April 2008 </option> <option value=''> March 2008 </option> <option value=''> February 2008 </option> <option value=''> January 2008 </option> <option value=''> December 2007 </option> <option value=''> November 2007 </option> <option value=''> October 2007 </option> <option value=''> September 2007 </option> <option value=''> August 2007 </option> <option value=''> July 2007 </option> <option value=''> June 2007 </option> <option value=''> May 2007 </option> <option value=''> April 2007 </option> <option value=''> March 2007 </option> <option value=''> February 2007 </option> <option value=''> January 2007 </option> <option value=''> December 2006 </option> <option value=''> November 2006 </option> <option value=''> October 2006 </option> <option value=''> September 2006 </option> <option value=''> August 2006 </option> <option value=''> July 2006 </option> <option value=''> June 2006 </option> <option value=''> May 2006 </option> <option value=''> April 2006 </option> <option value=''> March 2006 </option> <option value=''> February 2006 </option> <option value=''> January 2006 </option> <option value=''> December 2005 </option> <option value=''> November 2005 </option> <option value=''> October 2005 </option> <option value=''> September 2005 </option> <option value=''> August 2005 </option> <option value=''> July 2005 </option> <option value=''> June 2005 </option> <option value=''> May 2005 </option> <option value=''> April 2005 </option> <option value=''> March 2005 </option> <option value=''> February 2005 </option> <option value=''> January 2005 </option> <option value=''> December 2004 </option> <option value=''> November 2004 </option> <option value=''> October 2004 </option> <option value=''> September 2004 </option> <option value=''> August 2004 </option> <option value=''> July 2004 </option> <option value=''> June 2004 </option> <option value=''> May 2004 </option> <option value=''> April 2004 </option> <option value=''> March 2004 </option> <option value=''> February 2004 </option> <option value=''> January 2004 </option> <option value=''> December 2003 </option> <option value=''> November 2003 </option> <option value=''> October 2003 </option> <option value=''> September 2003 </option> <option value=''> August 2003 </option> <option value=''> July 2003 </option> <option value=''> June 2003 </option> <option value=''> May 2003 </option> <option value=''> April 2003 </option> <option value=''> March 2003 </option> <option value=''> February 2003 </option> <option value=''> January 2003 </option> <option value=''> December 2002 </option> <option value=''> November 2002 </option> <option value=''> October 2002 </option> <option value=''> September 2002 </option> <option value=''> August 2002 </option> <option value=''> July 2002 </option> <option value=''> June 2002 </option> <option value=''> May 2002 </option> <option value=''> April 2002 </option> <option value=''> March 2002 </option> <option value=''> February 2002 </option> <option value=''> January 2002 </option> <option value=''> December 2001 </option> <option value=''> November 2001 </option> <option value=''> October 2001 </option> <option value=''> September 2001 </option> <option value=''> August 2001 </option> <option value=''> July 2001 </option> <option value=''> June 2001 </option> <option value=''> May 2001 </option> <option value=''> April 2001 </option> <option value=''> March 2001 </option> <option value=''> February 2001 </option> <option value=''> January 2001 </option> <option value=''> December 2000 </option> <option value=''> November 2000 </option> <option value=''> February 1999 </option> <option value=''> January 1999 </option> <option value=''> December 1998 </option> <option value=''> August 1998 </option> <option value=''> July 1998 </option> <option value=''> June 1998 </option> <option value=''> February 1997 </option> <option value=''> January 1997 </option> <option value=''> May 1996 </option> <option value=''> April 1996 </option> <option value=''> January 1996 </option> <option value=''> December 1995 </option> <option value=''> August 1995 </option> <option value=''> April 1995 </option> <option value=''> March 1995 </option> <option value=''> February 1995 </option> <option value=''> January 1995 </option> <option value=''> December 1994 </option> <option value=''> February 1994 </option> <option value=''> January 1994 </option> <option value=''> December 1993 </option> <option value=''> November 1991 </option> <option value=''> October 1991 </option> <option value=''> January 1990 </option> </select> </section><section id="twitter_timeline-4" class="widget widget_twitter_timeline"><h2 class="widget-title">On Twitter…</h2><a class="twitter-timeline" data-height="1000" data-theme="light" data-link-color="#f96e5b" data-border-color="#e8e8e8" data-lang="EN" data-partner="jetpack" data-chrome="noheader nofooter" href="">My Tweets</a></section><section id="wpcom_social_media_icons_widget-3" class="widget widget_wpcom_social_media_icons_widget"><h2 class="widget-title">Elsewhere</h2><ul><li><a href="" class="genericon genericon-facebook" target="_blank"><span class="screen-reader-text">View michael.hanscom’s profile on Facebook</span></a></li><li><a href="" class="genericon genericon-twitter" target="_blank"><span class="screen-reader-text">View djwudi’s profile on Twitter</span></a></li><li><a href="" class="genericon genericon-instagram" target="_blank"><span class="screen-reader-text">View djwudi’s profile on Instagram</span></a></li><li><a href="" class="genericon genericon-linkedin" target="_blank"><span class="screen-reader-text">View michaelhanscom’s profile on LinkedIn</span></a></li><li><a href="" class="genericon genericon-youtube" target="_blank"><span class="screen-reader-text">View djwudi’s profile on YouTube</span></a></li><li><a href="" class="genericon genericon-vimeo" target="_blank"><span class="screen-reader-text">View djwudi’s profile on Vimeo</span></a></li><li><a href="" class="genericon genericon-googleplus" target="_blank"><span class="screen-reader-text">View michael.hanscom’s profile on Google+</span></a></li></ul></section> </aside><!-- .sidebar .widget-area --> </div><!-- .site-content --> <footer id="colophon" class="site-footer" role="contentinfo"> <nav class="main-navigation" role="navigation" aria-label="Footer Primary Menu"> <div class="menu-main-menu-container"><ul id="menu-main-menu-1" class="primary-menu"><li class="menu-item menu-item-type-post_type menu-item-object-page menu-item-9883"><a href="">About the Author</a></li> <li class="menu-item menu-item-type-post_type menu-item-object-page menu-item-11650"><a href="">Worth Reading</a></li> </ul></div> </nav><!-- .main-navigation --> <div class="site-info"> <span class="site-title"><a href="" rel="home">Eclecticism</a></span> <a href="">Proudly powered by WordPress</a> </div><!-- .site-info --> </footer><!-- .site-footer --> </div><!-- .site-inner --> </div><!-- .site --> <div style="display:none"> <div class="grofile-hash-map-9a076924469560ca18a153003fc750ea"> </div> </div> <script type='text/javascript' src=''></script> <script type='text/javascript' src=''></script> <script type='text/javascript' src=''></script> <script type='text/javascript'> /* <![CDATA[ */ var WPGroHo = {"my_hash":""}; /* ]]> */ </script> <script type='text/javascript' src=''></script> <script type='text/javascript' src=''></script> <script type='text/javascript'> /* <![CDATA[ */ var screenReaderText = {"expand":"expand child menu","collapse":"collapse child menu"}; /* ]]> */ </script> <script type='text/javascript' src=''></script> <script type='text/javascript' src=''></script> <script type='text/javascript' src=''></script> <script type='text/javascript' src='' async defer></script> <script type='text/javascript'> _stq = window._stq || []; _stq.push([ 'view', {v:'ext',j:'1:5.7',blog:'20976999',post:'0',tz:'-8',srv:''} ]); _stq.push([ 'clickTrackerInit', '20976999', '0' ]); </script> </body> </html>