<?xml version="1.0"?>
<?xml-stylesheet href="/transform" type="text/xsl"?>
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" xmlns:bibo="http://purl.org/ontology/bibo/" xmlns:bs="http://purl.org/ontology/bibo/status/" xmlns:ci="https://vocab.methodandstructure.com/content-inventory#" xmlns:dct="http://purl.org/dc/terms/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:xhv="http://www.w3.org/1999/xhtml/vocab#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#" lang="en" prefix="bibo: http://purl.org/ontology/bibo/ bs: http://purl.org/ontology/bibo/status/ ci: https://vocab.methodandstructure.com/content-inventory# dct: http://purl.org/dc/terms/ foaf: http://xmlns.com/foaf/0.1/ rdf: http://www.w3.org/1999/02/22-rdf-syntax-ns# xhv: http://www.w3.org/1999/xhtml/vocab# xsd: http://www.w3.org/2001/XMLSchema#" vocab="http://www.w3.org/1999/xhtml/vocab#" xml:lang="en">
  <head>
    <title property="dct:title">Idiot SEO Savant</title>
    <base href="https://doriantaylor.com/idiot-seo-savant"/>
    <link href="document-stats#E5PxqvyTw6WrLqrUo0RdOJ" rev="ci:document"/>
    <link href="elsewhere" rel="alternate bookmark" title="Elsewhere"/>
    <link href="this-site" rel="alternate index" title="This Site"/>
    <link href="http://purl.org/ontology/bibo/status/published" rel="bibo:status"/>
    <link href="" rel="ci:canonical" title="Idiot SEO Savant"/>
    <link href="lexicon/#EqIUfKvI93wG3TQRQDwoVJ" rel="dct:audience" title="Information Architect"/>
    <link href="person/dorian-taylor#me" rel="dct:creator" title="Dorian Taylor"/>
    <link href="person/dorian-taylor" rel="meta" title="Who I Am"/>
    <link about="./" href="3f36c30c-6096-454a-8a22-c062100ae41f" rel="alternate" type="application/atom+xml"/>
    <link about="./" href="f07f5044-01bc-472d-9079-9b07771b731c" rel="alternate" type="application/atom+xml"/>
    <link about="./" href="this-site" rel="alternate"/>
    <link about="./" href="elsewhere" rel="alternate"/>
    <link about="./" href="e341ca62-0387-4cea-b69a-cdabc7656871" rel="alternate" type="application/atom+xml"/>
    <link about="verso/" href="3f36c30c-6096-454a-8a22-c062100ae41f" rel="alternate" type="application/atom+xml"/>
    <link about="verso/" href="this-site" rel="alternate"/>
    <link about="verso/" href="elsewhere" rel="alternate"/>
    <meta content="idiot-seo-savant" datatype="xsd:token" property="ci:canonical-slug"/>
    <meta content="I have a low tolerance for snake oil, and search engine optimization is near the top of my list." name="description" property="dct:abstract"/>
    <meta content="2010-05-27T09:04:04+00:00" datatype="xsd:dateTime" property="dct:created"/>
    <meta content="idiot-seo-savant" property="dct:identifier"/>
    <meta content="2010-05-27T09:04:54+00:00" datatype="xsd:dateTime" property="dct:issued"/>
    <meta content="2010-05-27T09:05:43+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2010-05-27T09:25:55+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2010-05-27T15:34:10+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2010-05-27T15:36:15+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2010-05-27T16:02:17+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2010-05-27T16:51:13+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2010-05-28T20:41:48+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2010-05-28T20:46:42+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2010-05-28T20:47:05+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2013-03-03T18:16:49+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2022-05-31T04:18:52+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2022-05-31T15:10:50+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta about="person/dorian-taylor#me" content="Dorian Taylor" name="author" property="foaf:name"/>
    <meta content="summary" name="twitter:card"/>
    <meta content="@doriantaylor" name="twitter:site"/>
    <meta content="Idiot SEO Savant" name="twitter:title"/>
    <meta content="I have a low tolerance for snake oil, and search engine optimization is near the top of my list." name="twitter:description"/>
    <object>
      <nav>
        <ul>
          <li>
            <a href="document-stats#E5PxqvyTw6WrLqrUo0RdOJ" rev="ci:document" typeof="qb:Observation">
              <span>urn:uuid:e4fc6abf-24f0-4e96-9acb-aab528d1174e</span>
            </a>
          </li>
        </ul>
      </nav>
    </object>
  </head>
  <body about="" id="EvVz2aUdYNe94vigCkrMSK" typeof="bibo:Article">
    <aside role="note" id="EH5y-eqa7al_x8gfGu1NBL">
      <p>TL;DR <ins datetime="2013-02-19">February 19, 2013</ins>: This is way out of date, insofar as $GOOG has changed its secret sauce a number of times since I wrote it. The point was to say that you can do pretty decent <acronym title="Search engine optimization">SEO</acronym> just by creating decent content&#x2014;no need to partake in any hucksterism. As far as I can tell, this is still true.</p>
    </aside>
    <p>For as long as I can account, one of the biggest sources of traffic to my intentionally un-promoted site is some <a href="policy/http-url-path-parameter-syntax" title="HTTP URL Path Parameter Syntax" rel="dct:references">embarrassingly unfinished work I did</a> trying to suggest a uniform syntax for <a href="http://tools.ietf.org/html/rfc3986#section-3.3" title="RFC 3986 - Uniform Resource Identifier (URI): Generic Syntax" rel="dct:references"><acronym title="Uniform Resource Identifier">URI</acronym> path parameters</a>. This was something I knocked out as a precursor to some considerably more important work I was doing around a <a href="http://en.wikipedia.org/wiki/Functional_programming" title="Functional programming &#x2014; Wikipedia" rel="dct:references">functional</a> <a href="http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm" title="Fielding Dissertation: CHAPTER 5: Representational State Transfer (REST)" rel="dct:references"><acronym title="Representational State Transfer">REST</acronym> interface</a>. The funny thing is, it's <ins datetime="2010-05-27">currently</ins> #1 on the <a href="http://www.google.com/finance?q=goog" title="Google Inc.: NASDAQ:GOOG quotes &amp; news - Google Finance" rel="dct:references">GOOG</a> for various and surprisingly distant permutations of its subject matter. It has been for some time, and it's not the only one of mine like it.</p>
    <p>I should note that I think <a href="http://en.wikipedia.org/wiki/Search_engine_optimization" title="Search engine optimization &#x2014; Wikipedia" rel="dct:references">search engine optimization</a>, otherwise known as <acronym title="Search Engine Optimization">SEO</acronym>, is largely a fraud. More specifically, I have reason to believe that nobody has any idea about what cocktail of behaviour will consistently yield even close to the highest-ranking search result. I posit this holds even for the employees of the respective companies who work directly on the stuff. What makes it a fraud is when somebody claims otherwise.</p>
    <aside role="note" id="EIkilEInL56dluw6Z_6euI">
      <p>To illustrate this assertion, let's say I'm a carny that goes by the name Knuckles McGoog, and I have a <a href="http://en.wikipedia.org/wiki/Shell_game" title="Shell game &#x2014; Wikipedia" rel="dct:references">shell game</a>. The deal is you put down one dollar and if you pick the shell with the marble under it, you get back two. There's a <a href="http://en.wikipedia.org/wiki/Shill" title="Shill &#x2014; Wikipedia" rel="dct:references">guy standing next to you</a> who seems to be having an easy time of it. You play a few rounds. Sometimes you win, most of the time you lose. Why? Because you'll never win unless I let you. A cheater you say? Hey buddy, it's my game, you don't have to play it if you don't want to. Take note as well that if you do, it will always cost you more to figure out the rules of the game than for me to change them.</p>
    </aside>
    <p>From my perspective, <acronym title="Search Engine Optimization">SEO</acronym> breaks down into two categories: <em>active</em> and <em>passive</em>. Active entails hiring an army of people, or more smarmily, robots, to plug links into various places around the <abbr title="World-Wide Web">Web</abbr>. Passive is about setting up the <em>content</em> &#x2014; or ultimately the <em>data</em> &#x2014; of a given site to lend itself to easy, or more specifically, <em>inexpensive</em> consumption by search crawlers.</p>
    <p>To me, active <acronym title="Search Engine Optimization">SEO</acronym> is always at best tantamount to <a href="http://en.wikipedia.org/wiki/Spam_%28electronic%29" title="Spam (electronic) &#x2014; Wikipedia" rel="dct:references">spam</a>. Passive can go two routes. It can either attempt to subvert the search engines' algorithms, or it can simply present itself in a manner that is conducive to their consumption, and <a href="http://en.wikipedia.org/wiki/Computational_complexity_theory" title="Computational complexity theory &#x2014; Wikipedia" rel="dct:references">computationally cheap</a> to process. After all, <a href="advice-from-an-old-statesman" title="Advice from an Old Statesman" rel="dct:references"><acronym title="Central Processing Unit">CPU</acronym> time is money</a>.</p>
    <p>In my experience, successful passive <acronym title="Search Engine Optimization">SEO</acronym> is not something you can tack onto a <abbr title="World-Wide Web">Web</abbr> property after it's done, but rather <em>weave</em> it in as a part of the development process of the site. I believe this because my decade in software and the <abbr title="World-Wide Web">Web</abbr> has taught me that the most innocuous or trivial cut corner, early enough on, can irrevocably hobble an expected outcome. Likewise, it can cripple a genuine attempt to present, as I mentioned, a cohesive picture of what the <em>content</em> is about in a way that is cheaply accessible to dumb machines that really don't have a lot of spare time.</p>
    <p>It occurs to me then that much of an <acronym title="Search Engine Optimization">SEO</acronym> consultant's job can be replaced by software, and the remainder can be supplied by <a href="http://en.wikipedia.org/wiki/Information_architecture" title="Information architecture &#x2014; Wikipedia" rel="dct:references">information architects</a> and <a href="http://en.wikipedia.org/wiki/Content_strategy" title="Content strategy &#x2014; Wikipedia" rel="dct:references">content strategists</a>, whose principal objective is to <em>organize knowledge and communicate with people</em>, rather than game the <a href="http://en.wikipedia.org/wiki/Search_engine_results_page" title="Search engine results page &#x2014; Wikipedia" rel="dct:references"><acronym title="Search Engine Results Page">SERP</acronym></a>.</p>
    <p>This all said, there may still be some value in active <acronym title="Search Engine Optimization">SEO</acronym>, which ideally demands human attention.  The question here is <em>how much</em> attention, and from whom. I once visited a company who boasted that they had an entire floor in their building, in the order of about 30,000 square feet, dedicated to search marketing. I couldn't help but wonder at the time how wise an expenditure that was. Whether the money is spent in Bucharest, Bangalore or Los Angeles, you can still spot a dodge a mile away, and therefore eventually so will the crawlers. Likewise I wonder if the people involved couldn't have been doing something more rewarding, or at least more <em>effective</em>, with their time.</p>
    <p>I can't help but imagine that a site with useful content that is clear of clutter and conducive to linking by regular people will have the bulk of its active <acronym title="Search Engine Optimization">SEO</acronym> done in kind for the value it provides. The passive stuff, if you can successfully command the representation of the data from the <acronym title="Uniform Resource Identifier">URI</acronym>s, <acronym title="Hypertext Transfer Protocol">HTTP</acronym> headers and <acronym title="Hypertext Markup Language">HTML</acronym> markup on upward, should likewise take care of itself.</p>
    <p>As for myself, I really wasn't trying. Go figure.</p>
  </body>
</html>
