<?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: H1 or H2? How to Handle Headers?</title>
	<atom:link href="https://www.webmaster-source.com/2008/10/29/h1-or-h2-how-to-handle-headers/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.webmaster-source.com/2008/10/29/h1-or-h2-how-to-handle-headers/</link>
	<description>Useful Resources For Webmasters</description>
	<lastBuildDate>Wed, 29 Apr 2026 13:07:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.1.42</generator>
	<item>
		<title>By: Haruyoshi</title>
		<link>https://www.webmaster-source.com/2008/10/29/h1-or-h2-how-to-handle-headers/#comment-3657</link>
		<dc:creator><![CDATA[Haruyoshi]]></dc:creator>
		<pubDate>Mon, 03 Nov 2008 15:23:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.webmaster-source.com/?p=965#comment-3657</guid>
		<description><![CDATA[In my opinion, never mind h1 or h2, each once is enough.]]></description>
		<content:encoded><![CDATA[<p>In my opinion, never mind h1 or h2, each once is enough.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>https://www.webmaster-source.com/2008/10/29/h1-or-h2-how-to-handle-headers/#comment-3617</link>
		<dc:creator><![CDATA[Matt]]></dc:creator>
		<pubDate>Thu, 30 Oct 2008 17:27:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.webmaster-source.com/?p=965#comment-3617</guid>
		<description><![CDATA[@Mike, There is a brief note about search engine penalties for multiple h1s in the article, though perhaps a little too brief. In retrospect I wonder if I should have put a little more emphasis on that statement. It&#039;s something that people need to be aware of.&lt;br /&gt;&lt;br /&gt;I wrote this post partly because I&#039;m needing to optimize my current heading structure, it&#039;s a little flawed. Currently I don&#039;t have any h1s at all, and post titles are all h2s on every page. It will be a pain to update posts when I make the change...&lt;br /&gt;]]></description>
		<content:encoded><![CDATA[<p>@Mike, There is a brief note about search engine penalties for multiple h1s in the article, though perhaps a little too brief. In retrospect I wonder if I should have put a little more emphasis on that statement. It&#8217;s something that people need to be aware of.</p>
<p>I wrote this post partly because I&#8217;m needing to optimize my current heading structure, it&#8217;s a little flawed. Currently I don&#8217;t have any h1s at all, and post titles are all h2s on every page. It will be a pain to update posts when I make the change&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Robinson</title>
		<link>https://www.webmaster-source.com/2008/10/29/h1-or-h2-how-to-handle-headers/#comment-3616</link>
		<dc:creator><![CDATA[Mike Robinson]]></dc:creator>
		<pubDate>Thu, 30 Oct 2008 16:47:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.webmaster-source.com/?p=965#comment-3616</guid>
		<description><![CDATA[From what I understand, SE&#039;s will actually penalise you for using multiple H1&#039;s (whether maliciously or not). This caused many SEO people to place everything in H2&#039;s, which didn&#039;t seem to have the negative effect. But, of course, this skipped the h1 and invalidated things.I didn&#039;t read your post first time round when checking out the Devlounge one, but now I did I am glad to see I am not the only one who ponders what to do with supplementary (sidebar) content. Suffice to say, headings are greatly flawed... :(]]></description>
		<content:encoded><![CDATA[<p>From what I understand, SE&#8217;s will actually penalise you for using multiple H1&#8217;s (whether maliciously or not). This caused many SEO people to place everything in H2&#8217;s, which didn&#8217;t seem to have the negative effect. But, of course, this skipped the h1 and invalidated things.I didn&#8217;t read your post first time round when checking out the Devlounge one, but now I did I am glad to see I am not the only one who ponders what to do with supplementary (sidebar) content. Suffice to say, headings are greatly flawed&#8230; <img src="https://www.webmaster-source.com/wp-includes/images/smilies/icon_sad.gif" alt=":(" class="wp-smiley" /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Handling Headers: Where to Use h1 and h2 &#124; Devlounge</title>
		<link>https://www.webmaster-source.com/2008/10/29/h1-or-h2-how-to-handle-headers/#comment-3612</link>
		<dc:creator><![CDATA[Handling Headers: Where to Use h1 and h2 &#124; Devlounge]]></dc:creator>
		<pubDate>Thu, 30 Oct 2008 11:01:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.webmaster-source.com/?p=965#comment-3612</guid>
		<description><![CDATA[[...] reason I&#8217;m bringing it up now is this post on the topic, over at Webmaster-Source. I&#8217;ve gotten several emails asking if Matt&#8217;s conclusion is the right one. Basically, [...]]]></description>
		<content:encoded><![CDATA[<p>[&#8230;] reason I&#8217;m bringing it up now is this post on the topic, over at Webmaster-Source. I&#8217;ve gotten several emails asking if Matt&#8217;s conclusion is the right one. Basically, [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>https://www.webmaster-source.com/2008/10/29/h1-or-h2-how-to-handle-headers/#comment-3597</link>
		<dc:creator><![CDATA[Matt]]></dc:creator>
		<pubDate>Wed, 29 Oct 2008 21:46:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.webmaster-source.com/?p=965#comment-3597</guid>
		<description><![CDATA[I think it is mainly up to personal preference, so long as you do it consistently, and don&#039;t try to spam search engines by making as many things as possible h1s.&lt;br /&gt;]]></description>
		<content:encoded><![CDATA[<p>I think it is mainly up to personal preference, so long as you do it consistently, and don&#8217;t try to spam search engines by making as many things as possible h1s.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Clark</title>
		<link>https://www.webmaster-source.com/2008/10/29/h1-or-h2-how-to-handle-headers/#comment-3596</link>
		<dc:creator><![CDATA[Steven Clark]]></dc:creator>
		<pubDate>Wed, 29 Oct 2008 20:10:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.webmaster-source.com/?p=965#comment-3596</guid>
		<description><![CDATA[I&#039;m actually very similar to Richard. First, regardless that by the spec you can use more than 1 h1 element it strikes me (as a computer guy) as a strange information hierarchy to have 2 top level headings. That implies two pages. So I&#039;m definately a single h1 guy. I would say that site name versus page name in h1 is probably a personal choice thing - my blog is using site name at present but the next design iteration may not. Both arguments have pros and cons on that one - and I think Google can get the information as long as you have good content and meaningful headers / structure so it&#039;s probably not as important what level heading as much as it is important to have meaningful heading structure / hierarchy and supporting content. The tags themselves just explain hierarchy and what follows them. I tend to use h2 level headings in the sidebar or when I write content for new logical div sections of the page... if that makes sense. Just my 2 cents.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;m actually very similar to Richard. First, regardless that by the spec you can use more than 1 h1 element it strikes me (as a computer guy) as a strange information hierarchy to have 2 top level headings. That implies two pages. So I&#8217;m definately a single h1 guy. I would say that site name versus page name in h1 is probably a personal choice thing &#8211; my blog is using site name at present but the next design iteration may not. Both arguments have pros and cons on that one &#8211; and I think Google can get the information as long as you have good content and meaningful headers / structure so it&#8217;s probably not as important what level heading as much as it is important to have meaningful heading structure / hierarchy and supporting content. The tags themselves just explain hierarchy and what follows them. I tend to use h2 level headings in the sidebar or when I write content for new logical div sections of the page&#8230; if that makes sense. Just my 2 cents.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard</title>
		<link>https://www.webmaster-source.com/2008/10/29/h1-or-h2-how-to-handle-headers/#comment-3594</link>
		<dc:creator><![CDATA[Richard]]></dc:creator>
		<pubDate>Wed, 29 Oct 2008 10:39:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.webmaster-source.com/?p=965#comment-3594</guid>
		<description><![CDATA[I&#039;ve always put the site name in a h1, the page title h2, and then article sections in h3. Even when using a logo and not a site name I use the h1 and display: none. Not sure if its right, but it makes sense to me when I turn CSS off.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;ve always put the site name in a h1, the page title h2, and then article sections in h3. Even when using a logo and not a site name I use the h1 and display: none. Not sure if its right, but it makes sense to me when I turn CSS off.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!--
Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/


Served from: www.webmaster-source.com @ 2026-04-29 18:20:03 by W3 Total Cache
-->