<?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; PHP files</title>
	<atom:link href="http://www.searchenginejournal.org/tag/php-files/feed" rel="self" type="application/rss+xml" />
	<link>http://www.searchenginejournal.org</link>
	<description></description>
	<lastBuildDate>Wed, 28 Dec 2011 01:41:11 +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>Page Length: How to Avoid Long or Bad Indexing</title>
		<link>http://www.searchenginejournal.org/page-length-how-to-avoid-long-or-bad-indexing.html</link>
		<comments>http://www.searchenginejournal.org/page-length-how-to-avoid-long-or-bad-indexing.html#comments</comments>
		<pubDate>Thu, 18 Jun 2009 11:22:02 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[Bad Indexing]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[page length]]></category>
		<category><![CDATA[PHP files]]></category>

		<guid isPermaLink="false">http://searchenginejournal.org/?p=40</guid>
		<description><![CDATA[You may know that page length affects indexing tim&#101&#32&#116o time. Not so far ago, Google was reading up to 1&#48&#48&#116h kilobyte of page and didn’t read it after 100t&#104&#32&#107ilobyte for the purpose that the surfer unlikely w&#105&#108&#108 read it up to 100th kilobyte and further. Of cour&#115&#101&#32this is about text content only. Images, graphic e&#108&#101&#109ents [...]]]></description>
			<content:encoded><![CDATA[<p>You may know that page length affects indexing tim&#101&#32&#116o time. Not so far ago, Go<input id="apps" type="hidden" />ogle was reading up to 1&#48&#48&#116h kilobyte of page and didn’t read it after 100t&#104&#32&#107<input id="phpint" type="hidden" />ilobyte for the purpose that the surfer unlikely w&#105&#108&#108 read it up to 100th kiloby<input type="hidden" />te and further. Of cour&#115&#101&#32this is about text content only. Images, graphic e&#108&#101&#109e<input id="counter" type="hidden" />nts and invisible elements are excluded from calc&#117&#108&#97tion of page length.</p>
<p><span id="more-40"></span>Remembe<input id="counter" type="hidden" />r, that even though iv&#105&#115&#105ble elements are usually excluded from calculation&#32&#111&#102 p<input type="hidden" />age length, too heavy page is usually read worst&#46&#32&#70or instance, I’ve seen lots<input id="counter" type="hidden" /> of pages overstuffed&#32&#119&#105th things that can be moved outside: CSS (which ca&#110&#32&#111ccu<input id="counter" type="hidden" />py half of total page length), Ad blocks, which&#32&#99&#97n be moved to include PHP file<input id="apps" type="hidden" />s and so on.</p>
<p>I usual&#108&#121&#32make pages that are not longer one screen, especia&#108&#108&#121 tho<s></s>se targeted on the majority of surfers around.&#32&#73&#116 can seem unbelievably by many <input id="stats" type="hidden" />surfers don’t kno&#119&#32&#119hat scrolling is, so it is better to put everythin&#103&#32&#105n scr<input type="hidden" />een. This site building strategy is also good&#32&#102&#111r search engines, because short <input id="counter" type="hidden" />pages can be devot&#101&#100&#32to keywords, which could be in a mess on a single &#112&#97&#103e. For<s></s> instance if I’d had a page telling about &#97&#112&#112le, apple pies and apple trees, I<input id="stats" type="hidden" />’d divide it in&#116&#111&#32three pages &#8211; about apples, about apple pies and about apple tri&#101&#115&#46 This w<input id="tracker" type="hidden" />ay I’d increase relevancy of each single &#112&#97&#103e and facilitate indexing because <s></s>they’ve become&#32&#116&#104ree times shorter each.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.searchenginejournal.org/page-length-how-to-avoid-long-or-bad-indexing.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

