<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>From Accessibility to Zope &#187; Search Engines</title>
	<atom:link href="http://blog.mauveweb.co.uk/category/search-engines/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mauveweb.co.uk</link>
	<description>experiments in contemporary web development</description>
	<lastBuildDate>Thu, 18 Aug 2011 23:26:00 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Debunking SEO</title>
		<link>http://blog.mauveweb.co.uk/2008/11/17/debunking-seo/</link>
		<comments>http://blog.mauveweb.co.uk/2008/11/17/debunking-seo/#comments</comments>
		<pubDate>Mon, 17 Nov 2008 14:30:32 +0000</pubDate>
		<dc:creator>mauve</dc:creator>
				<category><![CDATA[Search Engines]]></category>

		<guid isPermaLink="false">http://blog.mauveweb.co.uk/?p=156</guid>
		<description><![CDATA[I've discussed previously how the SEO industry constructs its advice. But I now want to take them to task on actual advice I've received from SEO companies. SEO companies make claims that are poorly scientifically verifiable, because it's very difficult to distinguish causal factors in changes in search result positions.
To validate these claims we could [...]]]></description>
			<content:encoded><![CDATA[<p>I've <a href="http://blog.mauveweb.co.uk/2007/09/28/the-church-of-the-search-engines/">discussed previously</a> how the <acronym title="Search Engine Optimisation">SEO</acronym> industry constructs its advice. But I now want to take them to task on actual advice I've received from <acronym title="Search Engine Optimisation">SEO</acronym> companies. <acronym title="Search Engine Optimisation">SEO</acronym> companies make claims that are poorly scientifically verifiable, because it's very difficult to distinguish causal factors in changes in search result positions.</p>
<p>To validate these claims we could imagine a study where we compare the rankings of two groups of websites, distinguished only by whether they implement a given <acronym title="Search Engine Optimisation">SEO</acronym> suggestion. If the hypothesised recommendation does affect ranking we would expect to see a statistically significant amelioration of search engine ranking.</p>
<p>I don't believe this is possible. For one thing, there are too many factors, given the complexity of the web, to be able to extract a clear picture, so any results would be unlikely to be "statistically significant". This means any effect noted would not be as great as the margins of error of the experiment. The results would be too muddied by independent and much more important considerations like inbound links and accessibility. Also you can't get a very good appreciation of how much a rank is affected: you only see the order of results, not how much better one result is considered than the next. Statistically that should widen the margins of error.</p>
<p>I am skeptical about a lot of these things. I don't think I can disprove them given the doubts I've expressed above, but I do contest them. I believe they are unlikely and I believe <acronym title="Search Engine Optimisation">SEO</acronym> people believe them for invalid reasons.</p>
<p><span id="more-156"></span></p>
<p><em>Using meta keywords tags increases ranking for those keywords.<br />
</em></p>
<p>No major search engine uses meta keywords. It's far too easy to manipulate and does not reflect the actual page content.<strong></strong></p>
<p><em>Using meta keywords tags increases search engine traffic if the keywords also appear in the page content.</em></p>
<p>I doubt this would predict relevance well enough to be useful. For example, anyone could mirror the content in the page into the meta keywords, and the page would rank higher. Meanwhile sites that omit keywords would be penalised.</p>
<p><em>Using meta description tags increases search engine traffic.<br />
</em></p>
<p>The meta description tag appears in place of an excerpt from the content in several major search engines. This undoubtedly increases the apparent quality and apparent relevance of a site in a search engine's result pages, and that could persuade more people to click on a link.</p>
<p><em>Using keywords in &lt;title&gt; increases search engine ranking.</em></p>
<p>Unfortunately, I think this is very plausible. However, I frequently see page titles ransacked by keyword stuffing. There's a trade-off here between providing something that reflects the content of your site and making your site untidy and the search result listing unclear. For example, I would prefer to see</p>
<p>&lt;title&gt;Fireplaces &#8211; Mobstone Marble&lt;/title&gt;</p>
<p>in search results to</p>
<p>&lt;title&gt;Mobstone Marble for cheap fireplaces, fireguards, hearths, gravestones and more &#8211; Call 01234 567890&lt;/title&gt;</p>
<p>which is the sort of thing I've seen recommended by some <acronym title="Search Engine Optimisation">SEO</acronym> companies. I think there's an argument that as long as you're putting the terms "Fireplaces" and "Mobstone Marble" into the title, you've covered the relevant keywords for that page, plus the page is described clearly and unambiguously in search results.</p>
<p><em>Keywords in &lt;h1&gt; tags are more heavily weighted for relevance than keywords in &lt;h2&gt; tags and so on down to &lt;h6&gt; and any other tag.<br />
</em></p>
<p>This is definitely a good predictor of relevance, but it should be remembered that it can be generalised to all tags, not just &lt;h1-6&gt; tags. You could deduce a weighting scheme like this through statistical analysis of a corpus of <acronym title="HyperText Markup Language">HTML</acronym>. In particular, you might find that &lt;th&gt; or &lt;dt&gt; or maybe even just nested &lt;b&gt;&lt;i&gt; trumps &lt;h6&gt;.</p>
<p><em>Putting keywords into bigger &lt;h1-6&gt; tags increases ranking for those terms.<br />
</em></p>
<p>This is the kind of thing that non-programmers/non-statisticians would assume is implied by the previous fact, but is not. Tag weights definitely guide how a search engine apportions weight but it would be fairly naïve if it just counted as simple boost in the rankings. Search engines strive to assess relevance from page content in the way humans do, and bigger titles don't imply more relevance to humans. They catch your<em> attention</em> more, but you assess their <em>relevance</em> in a more holistic fashion<strong>. </strong></p>
<p><em>Putting keywords into URLs makes a page appear more relevant for those keywords.<br />
</em></p>
<p>It's a fact that URLs are intended to be opaque: there's no reason to believe http://work-safe-images.org/racoon.png is not a <acronym title="Joint Photographics Experts Group"><acronym title="Joint Photographic Experts Group Image">JPEG</acronym></acronym> image of a vagina. Humans don't treat them this way of course. Filenames would be useless if they didn't help us to identify the content of a file. However, one problem with using something defined as not being relevant as relevant is that you would get a significant rate of misprediction. If you take a <acronym title="Uniform Resource Locator">URL</acronym> of /animals/racoon.html as lending credence to an assessment that it's a page about racoons, what happens when you discover it's not a page about racoons at all? In short, a search engine must assess relevance of a page based on the page itself. Since it has to do that, does it really get more information from the <acronym title="Uniform Resource Locator">URL</acronym>? Let's say URLs are relevant 70% of the time. Something that is wrong 30% of the time and otherwise merely confirms what you already know is pretty worthless. I think friendly URLs are good from a usability perspective, and they confer a certain element of quality as far as I'm concerned, but I don't think it's very plausible that they affect rankings.</p>
<p><em>Putting keywords in image URLs </em><em>makes it appear more relevant for those keywords.</em><em><br />
</em></p>
<p>This is possibly a lot more plausible than with <acronym title="HyperText Markup Language">HTML</acronym>. When spidering images you will really struggle to find enough information. Since we can't assess relevance directly with images, the example above changes. URLs may be wrong 30% of the time, but 70% of the time there is information you could not otherwise find. Still, one way around this, if I was writing a search engine, would be simply not to index images where I cannot gather enough information to assess relevance.</p>
<p><em>Putting keywords in URLs and alt tags will get images to appear combined searches and thereby boost conversions.</em></p>
<p>Images that are likely to produce conversions don't appear in combined search results. Have a look on Google now, if you want, and convince yourself of that. I suspect you would not be able to find any image that promotes one specific vendor. There must be some heuristic which ensures that images in combined search results are vendor-neutral encyclopaedia-type images. Googling "Britney Spears" gets you pictures of Britney Spears. Googling "Asus eee 700&#8243; doesn't get you pictures. I suspect there's a reason for that.</p>
<p><em>Providing buttons to "Bookmark this page" boosts conversions.<br />
</em></p>
<p>It obvious that users who bookmark pages come back more than those who don't, but I doubt a great many people use these, unless they are frequent enough users to know where the "bookmark this page" button is better than they know where the star is on their web browser. That kind of user doesn't need the encouragement to come back.<strong> </strong></p>
<p><em>Opening external sites in new windows encourages people to return when they have finished reading an external page.</em></p>
<p>There's no doubt that if you can keep your site in a background window, it can allow visitors to pick up where they left off when they close the foreground window. However, the most heavily used navigational tool is the back button, not desktop windows, and opening a new window disables the ability to use the back button to return. Instead of closing windows to return to what they were doing, users fall into a pattern of piling up windows and then use "Close Group" from the Windows taskbar, or some just closing a batch of windows at once. Which approach is best can be established by usability research, and on this issue usability analyst Jakob Nielsen is unambigous: <a href="http://www.useit.com/alertbox/990530.html">don't break the back button! Don't open new windows!</a></p>
<p><em>Absolute URLs are better than relative URLs.</em></p>
<p>Software can convert between relative and absolute URLs as necessary. This only affects broken software that needs to and doesn't. There is a lot of broken software in the world but any software that's been tested against the wild wild web shouldn't fall into this trap. The amount of software that's broken in this way is negligible in comparison to the amount broken for hundreds of other reasons that you also need not support.</p>]]></content:encoded>
			<wfw:commentRss>http://blog.mauveweb.co.uk/2008/11/17/debunking-seo/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>The Church of the Search Engines</title>
		<link>http://blog.mauveweb.co.uk/2007/09/28/the-church-of-the-search-engines/</link>
		<comments>http://blog.mauveweb.co.uk/2007/09/28/the-church-of-the-search-engines/#comments</comments>
		<pubDate>Fri, 28 Sep 2007 21:22:39 +0000</pubDate>
		<dc:creator>mauve</dc:creator>
				<category><![CDATA[Search Engines]]></category>

		<guid isPermaLink="false">http://blog.mauveweb.co.uk/2007/09/28/the-church-of-the-search-engines/</guid>
		<description><![CDATA[Do you expect web developers to hold qualifications in computer science? By the same account, you should expect search engine optimisation (SEO) specialists to hold a degree in statistics or game theory. Or computer science, in fact.
Ever since I set up Mauve Internet, it has been asserted on the website that SEO is a myth. [...]]]></description>
			<content:encoded><![CDATA[<p>Do you expect web developers to hold qualifications in computer science? By the same account, you should expect search engine optimisation (<acronym title="Search Engine Optimisation">SEO</acronym>) specialists to hold a degree in statistics or game theory. Or computer science, in fact.</p>
<p>Ever since I set up Mauve Internet, it has been asserted on the website that <a href="http://www.mauveinternet.co.uk/cons_services"><acronym title="Search Engine Optimisation">SEO</acronym> is a myth</a>. In recent weeks I have brushed up on my understanding of the realm of <acronym title="Search Engine Optimisation">SEO</acronym> so as to defend Mauve Internet's practices. What I have encountered could reasonably be described a religion. Scant evidence is mused over, formulated into doctrine, and memorized by rote. The priests of <acronym title="Search Engine Optimisation">SEO</acronym> wield power in the eyes of the faithful, they preach their beliefs to others and they have heated religious debates about which beliefs are important.</p>
<p>Building a site which is genuinely more popular than the competition is the crux of search engine ranks and the responsibility for that lies entirely with the site owner. There are also a wealth of accessibility techniques for removing barriers to spidering, and there are some common sense techniques, like canonicalising URLs so as not to divide the weight of the page. But these are within the remit of the developer, who, if they are any good, will have done them as standard. More importantly, these are done once and for all. These do not yield incremental improvements and they do not need to be continually revised.</p>
<p>I don't believe <acronym title="Search Engine Optimisation">SEO</acronym> specialists stick to this territory, although hopefully many now pay attention to it. <acronym title="Search Engine Optimisation">SEO</acronym> specialists I have corresponded with carve out a niche where they can remain unchallenged, a territory of keyword density, meta tags, link depth, link penalties and link juice shaping, the application of ill-defined theories which are unproven (in some cases, disproven) and which they can continue to charge for as they tweak in response to the latest webstats.</p>
<p>The assertion that <acronym title="Search Engine Optimisation">SEO</acronym> is a racket can be easily substantiated. If website owners could, by invoking <acronym title="Search Engine Optimisation">SEO</acronym> voodoo, position themselves arbitrarily highly in the natural listings of search engines, then the search results would be determined by website owners as a function of time and money. The usefulness of the search would quickly degenerate and users would migrate to other search engines who provide better quality results. Therefore, search engines would not make as much money from sponsored links. Search engines like making money from sponsored links, so they won't allow this to happen.</p>
<p>This isn't some abstract scenario I've imagined. It actually happened in the late 1990's to the search engine Altavista. Altavista's search results had become a free-for-all and it haemorraged users, primarily to Google, whose search results were vastly superior and clean of link farms. I watched it happen; in fact I was one of Altavista's users who switched to Google.</p>
<p>The one thing we know for certain about the ranking systems of search engines is that they are extremely complex and closely guarded secrets. They don't have to be scrutable or even produce optimal results: they merely need to produce good results &#8211; which implies being hardened against exploitation.</p>]]></content:encoded>
			<wfw:commentRss>http://blog.mauveweb.co.uk/2007/09/28/the-church-of-the-search-engines/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

