<?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>Ohio Web Design - OmniSpear Inc. &#187; seo tips</title>
	<atom:link href="http://ohio-web-design.com/tag/seo-tips/feed/" rel="self" type="application/rss+xml" />
	<link>http://ohio-web-design.com</link>
	<description>Web Design tips and tricks for developers located in Dayton, Ohio and other areas</description>
	<lastBuildDate>Tue, 24 Jan 2012 22:52:40 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Top SEO Tips</title>
		<link>http://ohio-web-design.com/2009/07/10/top-seotips/</link>
		<comments>http://ohio-web-design.com/2009/07/10/top-seotips/#comments</comments>
		<pubDate>Fri, 10 Jul 2009 17:34:13 +0000</pubDate>
		<dc:creator>OmniSpear</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[dayton web design]]></category>
		<category><![CDATA[seo]]></category>
		<category><![CDATA[seo tips]]></category>

		<guid isPermaLink="false">http://blog.omnispear.com/?p=329</guid>
		<description><![CDATA[Different META tags per page META tags, keywords, description, and most specifically title &#8211; must be unique on each page and describe the content on the page. Canonical URLs Use a consistent URL scheme across the site &#8211; don’t mix &#8230; <a href="http://ohio-web-design.com/2009/07/10/top-seotips/">Continue reading <span class="meta-nav">&#8594;</span></a><div class="addthis_toolbox addthis_default_style " addthis:url='http://ohio-web-design.com/2009/07/10/top-seotips/' addthis:title='Top SEO Tips '  ><a class="addthis_button_facebook_like" fb:like:layout="button_count"></a><a class="addthis_button_tweet"></a><a class="addthis_button_google_plusone" g:plusone:size="medium"></a><a class="addthis_counter addthis_pill_style"></a></div>]]></description>
			<content:encoded><![CDATA[<p><BR><BR><br />
<strong>Different META tags per page</strong><br />
META tags, keywords, description, and most specifically title &#8211; must be unique on each page and describe the content on the page. </p>
<p><strong>Canonical URLs</strong><br />
Use a consistent URL scheme across the site &#8211; don’t mix http://domain.com with http://www.domain.com/ and never use a link to index.php or index.php?page=home. In the latter three cases, a link back to the web root is preferential eg. http://www.domain.com. </p>
<p><strong>Search friendly URLs and absolute URLs</strong><br />
Using URL rewriting, create URLs that make sense to the human eye, eg. http://www.domain.com/products/sofas/big-brown-sofa.html. NOTE: NEVER use underscores in URLs or for file naming, always use hyphens. Use absolute links throughout the site eg. include the http://www.domain.com in every A HREF. When linking to a page, as opposed to an index, always suffix “.html” onto the URL. All URLs should end with “/” or “.html”.</p>
<p><strong>Proper use of H1 tags</strong><br />
The H1 should be the main heading of the page, semantically proceeded by H2, H3 etc. Do not use H1 for the logo, use an alternative tag. Your H1 should also be reflected in the META Title of the page.</p>
<p><strong>Logo naming</strong><br />
Don’t name your logo image Logo.jpg. Instead name it something relevant to the site &#8211; for example for a jewelry site, name it jewellery.jpg</p>
<p><strong>NoFollow links</strong><br />
The rel=”nofollow” attribute prevents search engines from leaking page rank to useless pages, for example, for terms and conditions, privacy policy and in most cases contact pages (unless they include a physical address for example).</p>
<p><strong>XML Sitemap</strong><br />
There is a Google sitemap generator available that will create an XML sitemap and update it on the fly, informing Google of any new pages. All sites should contain an XML sitemap as well as a XHTML one. Show both sitemaps in the footer like this:</p>
<p>Contact | Privacy | Terms | Sitemap (XML Version)</p>
<p><strong>Images with ALT attributes</strong><br />
All images should have ALT attributes, primarily to describe the image for screenreaders, but they can have an SEO benefit by including site keywords.</p>
<p><strong>301 redirects</strong><br />
Especially important when redeveloping an old site &#8211; ensure old URLs are 301 back to the homepage. A 301 redirect tells search engines “This content has moved permanently”.</p>
<p><strong>Don’t use frame</strong>s<br />
We’re sure you don’t use them.. do you? Well don’t because amongst other things the content within a frame isn’t accessible to search engines. Same applies to iframes.</p>
<p><strong>Check for W3C compliance</strong><br />
This is part of best practice and has a positive benefit for SEO.<br />
Don’t call links page “links”<br />
This has negative connotations to link farms, reciprocal linking etc. Instead, use a term like “Resources”, “Related Sites” etc. You should preferably come up with a term which is unique to the site, whilst still describing the page accurately.</p>
<p><strong>Keep CSS and JS external</strong><br />
The less clutter there is in the page, the less markup search engines have to sift through. Also, avoid inline styles and inline javascript for the same reason.</p>
<div class="addthis_toolbox addthis_default_style " addthis:url='http://ohio-web-design.com/2009/07/10/top-seotips/' addthis:title='Top SEO Tips '  ><a class="addthis_button_facebook_like" fb:like:layout="button_count"></a><a class="addthis_button_tweet"></a><a class="addthis_button_google_plusone" g:plusone:size="medium"></a><a class="addthis_counter addthis_pill_style"></a></div>]]></content:encoded>
			<wfw:commentRss>http://ohio-web-design.com/2009/07/10/top-seotips/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

