<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
	
	>
<channel>
	<title>
	Comments on: CMS Requirements for SEO	</title>
	<atom:link href="https://www.searchenginepeople.com/blog/seo-cms-requirements.html/feed" rel="self" type="application/rss+xml" />
	<link>https://www.searchenginepeople.com/blog/seo-cms-requirements.html?utm_source=feed&#038;utm_medium=feed&#038;utm_campaign=feed</link>
	<description>Canada&#039;s Search and Social Media Authority</description>
	<lastBuildDate>Tue, 22 Apr 2014 16:06:05 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Dave Sottimano		</title>
		<link>https://www.searchenginepeople.com/blog/seo-cms-requirements.html/comment-page-1#comment-139852</link>

		<dc:creator><![CDATA[Dave Sottimano]]></dc:creator>
		<pubDate>Thu, 15 Dec 2011 11:41:31 +0000</pubDate>
		<guid isPermaLink="false">https://www.searchenginepeople.com/?p=22703#comment-139852</guid>

					<description><![CDATA[@Robert - 99.9% of us know what he&#039;s referring to. You have a valid point, but probably not the best place to inform the masses.

@Joydeep - Nice job! Good to have an SEO / CMS universal recommendations resource I can send aspiring custom CMS devs.]]></description>
			<content:encoded><![CDATA[<p>@Robert &#8211; 99.9% of us know what he&#8217;s referring to. You have a valid point, but probably not the best place to inform the masses.</p>
<p>@Joydeep &#8211; Nice job! Good to have an SEO / CMS universal recommendations resource I can send aspiring custom CMS devs.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Ravi		</title>
		<link>https://www.searchenginepeople.com/blog/seo-cms-requirements.html/comment-page-1#comment-139769</link>

		<dc:creator><![CDATA[Ravi]]></dc:creator>
		<pubDate>Thu, 15 Dec 2011 05:03:42 +0000</pubDate>
		<guid isPermaLink="false">https://www.searchenginepeople.com/?p=22703#comment-139769</guid>

					<description><![CDATA[Nice post Joydeep. A good reference to cross check what the CMS one uses is and is not offering. One more point is if a URL name is changed, then a 301 from the old to the new by default or options like &#039;redirect type&#039; and &#039;to URL&#039; as a dropdown selection. This would be another option to reduce duplicates (since canonical tag is still more of a guideline, while redirects are more specific)]]></description>
			<content:encoded><![CDATA[<p>Nice post Joydeep. A good reference to cross check what the CMS one uses is and is not offering. One more point is if a URL name is changed, then a 301 from the old to the new by default or options like &#8216;redirect type&#8217; and &#8216;to URL&#8217; as a dropdown selection. This would be another option to reduce duplicates (since canonical tag is still more of a guideline, while redirects are more specific)</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Robert Visser		</title>
		<link>https://www.searchenginepeople.com/blog/seo-cms-requirements.html/comment-page-1#comment-139429</link>

		<dc:creator><![CDATA[Robert Visser]]></dc:creator>
		<pubDate>Wed, 14 Dec 2011 04:33:56 +0000</pubDate>
		<guid isPermaLink="false">https://www.searchenginepeople.com/?p=22703#comment-139429</guid>

					<description><![CDATA[Just a point of clarification on web standards, the discussion is on a Title element; “title tag” is a colloquialism. Using the the term “tag”  when referencing a Title element is ambiguous and open to confusion with a title attribute. Please see the World Wide Web Consortium (W3C) documents below.

HTML 4.01 Specification
W3C Recommendation 24 December 1999
The global structure of an HTML document
7.4.2 The TITLE element
http://goo.gl/o2htI

and

7.4.3 The TITLE attribute
http://goo.gl/xJnN0

or if you’d prefer:

HTML5
A vocabulary and associated APIs for HTML and XHTML
Editor’s Draft 30 September 2011
4.2.2 The title element
http://goo.gl/L3gLQ

For a Title element there is a difference between what Google displays on a search engine results page and what may actually be indexed. Beginning in late May 2010 we began seeing discussions on the forums that Google had increased the number of displayed characters on their SERPs to 70. And while there, of course, is no means to limit the number of characters one can place in this field, there are some additional places we can look for guidance.

The input filed for a Business Title on the form to create (or edit) a Google Places business listing has a limit of 80 characters.

On Aug. 17th, 2011 Matt Cutts stated in a Webmaster Central Help video, “What role does being in DMOZ play in rankings?” http://goo.gl/xPzQZ , that Google does still relies on DMOZ listings for a few asian countries (the implication being non-roman alphabets) as well as for some snippets. The input field for a title element in a DMOZ listing is limited to 100 characters.

Again, neither the character counts of 80 nor 100 specifically indicate Google has any limit on the number of characters which might be indexed for the Title element.

As far as authority given to the keywords placed in a Title element, long tail keyword phrases at the beginning of the field (to the left on a roman keyboard) receive a higher value.]]></description>
			<content:encoded><![CDATA[<p>Just a point of clarification on web standards, the discussion is on a Title element; “title tag” is a colloquialism. Using the the term “tag”  when referencing a Title element is ambiguous and open to confusion with a title attribute. Please see the World Wide Web Consortium (W3C) documents below.</p>
<p>HTML 4.01 Specification<br />
W3C Recommendation 24 December 1999<br />
The global structure of an HTML document<br />
7.4.2 The TITLE element<br />
<a href="http://goo.gl/o2htI" rel="ugc nofollow external noopener noreferrer" data-wpel-link="external" target="_blank" class="ext-link">http://goo.gl/o2htI</a></p>
<p>and</p>
<p>7.4.3 The TITLE attribute<br />
<a href="http://goo.gl/xJnN0" rel="ugc nofollow external noopener noreferrer" data-wpel-link="external" target="_blank" class="ext-link">http://goo.gl/xJnN0</a></p>
<p>or if you’d prefer:</p>
<p>HTML5<br />
A vocabulary and associated APIs for HTML and XHTML<br />
Editor’s Draft 30 September 2011<br />
4.2.2 The title element<br />
<a href="http://goo.gl/L3gLQ" rel="ugc nofollow external noopener noreferrer" data-wpel-link="external" target="_blank" class="ext-link">http://goo.gl/L3gLQ</a></p>
<p>For a Title element there is a difference between what Google displays on a search engine results page and what may actually be indexed. Beginning in late May 2010 we began seeing discussions on the forums that Google had increased the number of displayed characters on their SERPs to 70. And while there, of course, is no means to limit the number of characters one can place in this field, there are some additional places we can look for guidance.</p>
<p>The input filed for a Business Title on the form to create (or edit) a Google Places business listing has a limit of 80 characters.</p>
<p>On Aug. 17th, 2011 Matt Cutts stated in a Webmaster Central Help video, “What role does being in DMOZ play in rankings?” <a href="http://goo.gl/xPzQZ" rel="ugc nofollow external noopener noreferrer" data-wpel-link="external" target="_blank" class="ext-link">http://goo.gl/xPzQZ</a> , that Google does still relies on DMOZ listings for a few asian countries (the implication being non-roman alphabets) as well as for some snippets. The input field for a title element in a DMOZ listing is limited to 100 characters.</p>
<p>Again, neither the character counts of 80 nor 100 specifically indicate Google has any limit on the number of characters which might be indexed for the Title element.</p>
<p>As far as authority given to the keywords placed in a Title element, long tail keyword phrases at the beginning of the field (to the left on a roman keyboard) receive a higher value.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
