<?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>Search Engine Journal &#187; HTML</title>
	<atom:link href="http://searchenginejournal.org/tag/html/feed" rel="self" type="application/rss+xml" />
	<link>http://searchenginejournal.org</link>
	<description></description>
	<lastBuildDate>Sat, 05 Sep 2009 21:48:07 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Platforms, Coding, Site Building</title>
		<link>http://searchenginejournal.org/platforms-coding-site-building.html</link>
		<comments>http://searchenginejournal.org/platforms-coding-site-building.html#comments</comments>
		<pubDate>Sat, 20 Jun 2009 12:40:43 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[HTML and Page Coding]]></category>
		<category><![CDATA[HTML]]></category>
		<category><![CDATA[SEO]]></category>

		<guid isPermaLink="false">http://searchenginejournal.org/?p=175</guid>
		<description><![CDATA[What editors have you used when just started making first sites? Personally I have started with Macromedia Dreamweaver, but very soon I made sure that it ads a lot of bugs in HTML and started learning the language itslef. Since then I’m using Allaire Homesite and PsPad editors (Now there is Home Site 5 released [...]]]></description>
			<content:encoded><![CDATA[<p>What editors have you used when just started making first sites? Personally I have started with Macromedia Dreamweaver, but very soon I made sure that it ads a lot of bugs in HTML and started learning <span id="more-175"></span>the language itslef. Since then I’m using Allaire Homesite and PsPad editors (Now there is Home Site 5 released by Macromedia after they’ve bought Allaire, but I don’t like it too). I”m telling this not just to discuss editors we use, but to stress your attention on importance of clean HTML. because the more bugs you make in code, the more corrupted it appears in serps and title “$#ajgd^&amp;87″ or url “..php?gophp127jags7a…” don’t looks attractive, huh? However, after several years of practice, those webmasters, who work with lots of content and have less time to edit HTML are moving to various content management systems. So do I.</p>
<p>I have tried a lot of them. One I was using up to last year is PhpNuke available at http://searchenginejournal.org. It is convenient, includes a lot of useful tools for site management. However, it contains a couple of bugs that are unwanted for SEO. For instance it always builds ugly-looking urls and has problems with putting correct titles. When I have worked on PhpNuke I spent a lot of time by tuning and adjusting it to fit my needs. I found plugins that replace page title with title of first article on this page, modules that made permanent urls and so on, but it took a lot of time to make it rolling for each new site I’ve made and I started looking for something more easy and covenient. That is how blogs became platforms for the majority of my sites.</p>
<p>After trying several blog scripts I have finally chosen two of them, which, I think are useful for building good sites. The first one I have tried is MT, which is available fromhttp://searchenginejournal.org. Powerfull platform for creating site. Rather easy installation and management. Good layout. Try it yourself to have your own opinion of convenience.</p>
<p>My second choice, which I consider to be the best choice for today is WordPress. Uptimebot is currently working on this platform and I am completely satisfied with it’s functional abilities. Of course it has lesser functions that MT and much less functions than PhpNuke, but ease of five minutes installation, attractive layout and amazingly clean code make WordPress to be the best script for building text sites, which I’d recommend for everybody, moreover that google loves blogs and this additionaly attracts me. Besides, there is a WordPress plugin that allows visitors to see when GoogleBot came for the last time &#8211; you can see it in footer of our page.</p>
<p>The only thing I’d like to be developed by WordPress is multi-site WordPress that would allow to build several blogs using one cpy of script (as it is possible with MT). They currently have only beta of multi-site script, but it is yet half-done and I wouldn’t recommend to use it.</p>
<p>Wordpress is available for download from http://searchenginejournal.org.  Enjoy it!</p>
]]></content:encoded>
			<wfw:commentRss>http://searchenginejournal.org/platforms-coding-site-building.html/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Moving from HTML to PHP</title>
		<link>http://searchenginejournal.org/moving-from-html-to-php.html</link>
		<comments>http://searchenginejournal.org/moving-from-html-to-php.html#comments</comments>
		<pubDate>Sat, 20 Jun 2009 12:21:06 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[HTML and Page Coding]]></category>
		<category><![CDATA[HTML]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[SEO]]></category>

		<guid isPermaLink="false">http://searchenginejournal.org/?p=173</guid>
		<description><![CDATA[This is a problem that many webmasters are ought to deal with sooner or later. Especially those, who have old sites, which were all based on .html files. Of course one can just change all .html extensions to .php and replace the same characters in pages’ code. However, if you deal with SEO and your [...]]]></description>
			<content:encoded><![CDATA[<p>This is a problem that many webmasters are ought to deal with sooner or later. Especially those, who have old sites, which were all based on .html files. Of course one can just change all .html extensions <span id="more-173"></span>to .php and replace the same characters in pages’ code. However, if you deal with SEO and your old good site occupies good position in SERPs, such changes can be fatal for your project for the following reasons:</p>
<p>1. All indexed .html files must be indexed again with .php extensions.<br />
2. All links pointing particular page will be lost, unless you report all of your link partners and site owners, who link to you (re-indexing of new links will take some time too).<br />
3. You will lose a lot of traffic from search engines during re-indexing of the whole site will occur, even if you put an error page that will redirect surfers somewhere to your .php pages.<br />
4. Nobody knows whether your site will return back to good positions in SERPs after it will drop out.</p>
<p>So, what to do if you don’t want to change file extensions for the purpose of SEO, but need to include some php code in your pages anyway? There are several methods.</p>
<p>The first, and the most obvious is to use mod_rewrite (in case if your server supports mod_rewrite and you have permissions to modify .htaccess file). If yes &#8211; put the following strings in your .htaccess file:</p>
<p>RewriteEngine on<br />
RewriteRule ^(.*)\.html $1\.php</p>
<p>Now all requested .html pages will be automatically substituted with .php pages.</p>
<p>Another method works with .htaccess again. Add the following string to .htaccess file:</p>
<p>AddHandler application/x-httpd-php .php .html .htm</p>
<p>I think that this method is the most convenient one, because it simply allows executing PHP scripts to run in .html files. If you have no access to your .htaccess file, contact your hoster and request to make appropriate modification of httpd.conf for your site.</p>
<p>If you were using SSI on your site, for instance like this:</p>
<p>Than you can replace it with the following string in your .php files:</p>
<p>&lt; ? include(&#8217;file.txt&#8217;); ?&gt;</p>
]]></content:encoded>
			<wfw:commentRss>http://searchenginejournal.org/moving-from-html-to-php.html/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
