H1 being your main, or overall topic (hence the title) H2 being a main topic within the main topic (hence the blog post title) H3 being a topic under the secondary topic (hence, used within the blog posts)
Personally, I've found that semantically constructed blogs do better in the search engines than those who use multiple H2 tags solely for SEO purposes.
Headings should be used to build a structure. Of course, this is still open to debate (and it has been debated a lot).
My personal rule of thumb is to look at the individual blog entry and develop a basic table of contents for it. That table of contents then becomes my heading structure for it.
~ Teli
Teli Adlam
· 3 years ago
It may not be logical for SEO purposes, but it is logical for semantic purposes. Heading tags should be looked at as a type of table of contents.
H1 being your main, or overall topic (hence the title) H2 being a main topic within the main topic (hence the blog post title) H3 being a topic under the secondary topic (hence, used within the blog posts)
Personally, I've found that semantically constructed blogs do better in the search engines than those who use multiple H2 tags solely for SEO purposes.
Headings should be used to build a structure. Of course, this is still open to debate (and it has been debated a lot).
My personal rule of thumb is to look at the individual blog entry and develop a basic table of contents for it. That table of contents then becomes my heading structure for it.
~ Teli
AndyBeard
· 3 years ago
A lot of theme designs are semantically well constructed.
Among those are your Optiniche themes which I use frequently, and this one I am using on this blog.
It is semantically correct to have post titles H1, and subheadings H2, if you use a graphics header.
For some niche sites I have modified the markup for SEO experimentation, for others I haven't.
I don't need H1 for my blog title here. It doesn't contain any keyword I have difficulty in gaining top rankings for ;) In fact it is not even the full keyword currently "ndy Beard"
But the whole context of this post is I wasn't thinking about how content was appearing in RSS readers.
There are lots of bloggers or template designers who do very weird and illogical things with markup.
I can't for any logical reason work out why the theme designer used H1 in that way.
The temptation is to use markup in a way that the existing CSS makes what you create look good on your site, without thinking about how it looks in RSS. Sometimes the better option is to change the CSS rather than the markup, but that is not a WYSIWYG option.
AndyBeard
· 3 years ago
A lot of theme designs are semantically well constructed.
Among those are your Optiniche themes which I use frequently, and this one I am using on this blog.
It is semantically correct to have post titles H1, and subheadings H2, if you use a graphics header.
For some niche sites I have modified the markup for SEO experimentation, for others I haven't.
I don't need H1 for my blog title here. It doesn't contain any keyword I have difficulty in gaining top rankings for ;) In fact it is not even the full keyword currently "ndy Beard"
But the whole context of this post is I wasn't thinking about how content was appearing in RSS readers.
There are lots of bloggers or template designers who do very weird and illogical things with markup.
I can't for any logical reason work out why the theme designer used H1 in that way.
The temptation is to use markup in a way that the existing CSS makes what you create look good on your site, without thinking about how it looks in RSS. Sometimes the better option is to change the CSS rather than the markup, but that is not a WYSIWYG option.
sportcrazy
· 3 years ago
I'm with the H1 blogname, H2 post title, H3 subtitle crowd.
You're right, graphic blogname, H1 post title, H2 subtitle could also be considered semantic HTML.
A heading element briefly describes the topic of the section it introduces. Heading information may be used by user agents, for example, to construct a table of contents for a document automatically.
There are six levels of headings in HTML with H1 as the most important and H6 as the least. Visual browsers usually render more important headings in larger fonts than less important ones.
<h1> is the HTML element for the first-level heading of a document:
* If the document is basically stand-alone, for example Things to See and Do in Geneva, the top-level heading is probably the same as the title. * If it is part of a collection, for example a section on Dogs in a collection of pages about pets, then the top level heading should assume a certain amount of context; just write <h1>Dogs</h1> while the title should work in any context: Dogs - Your Guide to Pets.
Unlike the title, this element can include links, emphasis and other HTML phrase elements.
The default font size for <h1> in some browsers have, unfortunately, motivated many writers and tools to use an <h2> element in stead. This is misleading to tools that take advantage of heading structure of pages, such as Amaya's table of contents view. Consider using Cascading Style Sheets, which are designed to express the author's preferred font sizes corresponding to elements such as <h1> and <h2>
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
After reading that I'm still not sure :)
Cheers, Al.
sportcrazy
· 3 years ago
I'm with the H1 blogname, H2 post title, H3 subtitle crowd.
You're right, graphic blogname, H1 post title, H2 subtitle could also be considered semantic HTML.
A heading element briefly describes the topic of the section it introduces. Heading information may be used by user agents, for example, to construct a table of contents for a document automatically.
There are six levels of headings in HTML with H1 as the most important and H6 as the least. Visual browsers usually render more important headings in larger fonts than less important ones.
<h1> is the HTML element for the first-level heading of a document:
* If the document is basically stand-alone, for example Things to See and Do in Geneva, the top-level heading is probably the same as the title. * If it is part of a collection, for example a section on Dogs in a collection of pages about pets, then the top level heading should assume a certain amount of context; just write <h1>Dogs</h1> while the title should work in any context: Dogs - Your Guide to Pets.
Unlike the title, this element can include links, emphasis and other HTML phrase elements.
The default font size for <h1> in some browsers have, unfortunately, motivated many writers and tools to use an <h2> element in stead. This is misleading to tools that take advantage of heading structure of pages, such as Amaya's table of contents view. Consider using Cascading Style Sheets, which are designed to express the author's preferred font sizes corresponding to elements such as <h1> and <h2>
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
After reading that I'm still not sure :)
Cheers, Al.
Teli Adlam
· 3 years ago
It is semantically correct to have post titles H1, and subheadings H2, if you use a graphics header.
Depends on how you use the graphic, but yes, it is still semantically correct. It's important that you provide adequate alt text and an even better solution would be using some sort of image replacement.
I see your point where it concerns blogs that don't have keywords in the title, however, that doesn't absolve the blog from using a heading structure on the site.
What I'm trying to get at is there should only be one H1 heading on any page. It's the most important heading and the one that encompasses all others. Deciding to use an H1 tag for post titles simply because the title of the blog doesn't contain keywords won't cut it.
Of course, this is my personal view and there's no definitive documentation. But, it appears to be the accepted norm, especially for accessibility.
~ Teli
P.S. Thanks for the compliments on the templates. :)
Teli Adlam
· 3 years ago
It is semantically correct to have post titles H1, and subheadings H2, if you use a graphics header.
Depends on how you use the graphic, but yes, it is still semantically correct. It's important that you provide adequate alt text and an even better solution would be using some sort of image replacement.
I see your point where it concerns blogs that don't have keywords in the title, however, that doesn't absolve the blog from using a heading structure on the site.
What I'm trying to get at is there should only be one H1 heading on any page. It's the most important heading and the one that encompasses all others. Deciding to use an H1 tag for post titles simply because the title of the blog doesn't contain keywords won't cut it.
Of course, this is my personal view and there's no definitive documentation. But, it appears to be the accepted norm, especially for accessibility.
~ Teli
P.S. Thanks for the compliments on the templates. :)
Teli Adlam
· 3 years ago
And another note, I completely agree about the ProBlogger set up. That coding - especially the use of the H1 tag - is brutal. It serves no purpose, not even SEO, and it was even styled with the CSS which indicates that it wasn't an accident or a momentary lapse in judgment...
Frankly, the date should have been wrapped in a paragraph tag, the blog's title should be in a heading level one and each of Darren's post titles should be in heading level 2. Again, just my opinion. ;)
~ Teli
Teli Adlam
· 3 years ago
And another note, I completely agree about the ProBlogger set up. That coding - especially the use of the H1 tag - is brutal. It serves no purpose, not even SEO, and it was even styled with the CSS which indicates that it wasn't an accident or a momentary lapse in judgment...
Frankly, the date should have been wrapped in a paragraph tag, the blog's title should be in a heading level one and each of Darren's post titles should be in heading level 2. Again, just my opinion. ;)
~ Teli
Web Desgn Book
· 2 years ago
That's an interesting article and worth knowing.
However, I don't think you should use heading tags incorrectly just to accommodate weaknesses in current RSS feeders.
Also, I don't think on a pragmatic basis that RSS readers are enough of an issue to ditch the correct sue of headings. The benefits for SEO and accessibility of using semantic HTML (as as semantic as you can manage) far outweigh this downside.
Web Desgn Book
· 2 years ago
That's an interesting article and worth knowing.
However, I don't think you should use heading tags incorrectly just to accommodate weaknesses in current RSS feeders.
Also, I don't think on a pragmatic basis that RSS readers are enough of an issue to ditch the correct sue of headings. The benefits for SEO and accessibility of using semantic HTML (as as semantic as you can manage) far outweigh this downside.
merlia
· 2 years ago
Of course H3 looks better than H2 tags, its visible or more clear than H2 tags, anyway its a good conversation between H2 and H3 tags...Thanks for this blog got a clear idea about the difference in heading tags...
merlia
· 2 years ago
Of course H3 looks better than H2 tags, its visible or more clear than H2 tags, anyway its a good conversation between H2 and H3 tags...Thanks for this blog got a clear idea about the difference in heading tags...
All Comments
a typical blog layout will have:
- H1 for the Blog title
- H2 for the post titles
- (and thus) H3 for headings within blog posts
a typical blog layout will have:
- H1 for the Blog title
- H2 for the post titles
- (and thus) H3 for headings within blog posts
Many SEOs would argue that you should have post titles as H1 as the blog title might not be relevant for SEO purposes.
Or in your header you might use H1 then H2
And then in the post H1 H2, or H2 H3
On your blog you can control the look separately for each section of the page.
Unfortunately that is a lot harder to do in your RSS feed.
Many SEOs would argue that you should have post titles as H1 as the blog title might not be relevant for SEO purposes.
Or in your header you might use H1 then H2
And then in the post H1 H2, or H2 H3
On your blog you can control the look separately for each section of the page.
Unfortunately that is a lot harder to do in your RSS feed.
See HTML 4.0.1 Headings and Heading Elements.
H1 being your main, or overall topic (hence the title)
H2 being a main topic within the main topic (hence the blog post title)
H3 being a topic under the secondary topic (hence, used within the blog posts)
Personally, I've found that semantically constructed blogs do better in the search engines than those who use multiple H2 tags solely for SEO purposes.
Headings should be used to build a structure. Of course, this is still open to debate (and it has been debated a lot).
My personal rule of thumb is to look at the individual blog entry and develop a basic table of contents for it. That table of contents then becomes my heading structure for it.
~ Teli
See HTML 4.0.1 Headings and Heading Elements.
H1 being your main, or overall topic (hence the title)
H2 being a main topic within the main topic (hence the blog post title)
H3 being a topic under the secondary topic (hence, used within the blog posts)
Personally, I've found that semantically constructed blogs do better in the search engines than those who use multiple H2 tags solely for SEO purposes.
Headings should be used to build a structure. Of course, this is still open to debate (and it has been debated a lot).
My personal rule of thumb is to look at the individual blog entry and develop a basic table of contents for it. That table of contents then becomes my heading structure for it.
~ Teli
Among those are your Optiniche themes which I use frequently, and this one I am using on this blog.
It is semantically correct to have post titles H1, and subheadings H2, if you use a graphics header.
For some niche sites I have modified the markup for SEO experimentation, for others I haven't.
I don't need H1 for my blog title here. It doesn't contain any keyword I have difficulty in gaining top rankings for ;)
In fact it is not even the full keyword currently "ndy Beard"
But the whole context of this post is I wasn't thinking about how content was appearing in RSS readers.
There are lots of bloggers or template designers who do very weird and illogical things with markup.
Take for example Darren Rouse's Problogger.net
I can't for any logical reason work out why the theme designer used H1 in that way.
The temptation is to use markup in a way that the existing CSS makes what you create look good on your site, without thinking about how it looks in RSS.
Sometimes the better option is to change the CSS rather than the markup, but that is not a WYSIWYG option.
Among those are your Optiniche themes which I use frequently, and this one I am using on this blog.
It is semantically correct to have post titles H1, and subheadings H2, if you use a graphics header.
For some niche sites I have modified the markup for SEO experimentation, for others I haven't.
I don't need H1 for my blog title here. It doesn't contain any keyword I have difficulty in gaining top rankings for ;)
In fact it is not even the full keyword currently "ndy Beard"
But the whole context of this post is I wasn't thinking about how content was appearing in RSS readers.
There are lots of bloggers or template designers who do very weird and illogical things with markup.
Take for example Darren Rouse's Problogger.net
I can't for any logical reason work out why the theme designer used H1 in that way.
The temptation is to use markup in a way that the existing CSS makes what you create look good on your site, without thinking about how it looks in RSS.
Sometimes the better option is to change the CSS rather than the markup, but that is not a WYSIWYG option.
You're right, graphic blogname, H1 post title, H2 subtitle could also be considered semantic HTML.
Let's check with W3C..
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://www.w3.org/TR/html401/struct/global.html... :
A heading element briefly describes the topic of the section it introduces. Heading information may be used by user agents, for example, to construct a table of contents for a document automatically.
There are six levels of headings in HTML with H1 as the most important and H6 as the least. Visual browsers usually render more important headings in larger fonts than less important ones.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://www.w3.org/QA/Tips/Use_h1_for_Title :
<h1> is the HTML element for the first-level heading of a document:
* If the document is basically stand-alone, for example Things to See and Do in Geneva, the top-level heading is probably the same as the title.
* If it is part of a collection, for example a section on Dogs in a collection of pages about pets, then the top level heading should assume a certain amount of context; just write <h1>Dogs</h1> while the title should work in any context: Dogs - Your Guide to Pets.
Unlike the title, this element can include links, emphasis and other HTML phrase elements.
The default font size for <h1> in some browsers have, unfortunately, motivated many writers and tools to use an <h2> element in stead. This is misleading to tools that take advantage of heading structure of pages, such as Amaya's table of contents view. Consider using Cascading Style Sheets, which are designed to express the author's preferred font sizes corresponding to elements such as <h1> and <h2>
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
After reading that I'm still not sure :)
Cheers,
Al.
You're right, graphic blogname, H1 post title, H2 subtitle could also be considered semantic HTML.
Let's check with W3C..
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://www.w3.org/TR/html401/struct/global.html... :
A heading element briefly describes the topic of the section it introduces. Heading information may be used by user agents, for example, to construct a table of contents for a document automatically.
There are six levels of headings in HTML with H1 as the most important and H6 as the least. Visual browsers usually render more important headings in larger fonts than less important ones.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://www.w3.org/QA/Tips/Use_h1_for_Title :
<h1> is the HTML element for the first-level heading of a document:
* If the document is basically stand-alone, for example Things to See and Do in Geneva, the top-level heading is probably the same as the title.
* If it is part of a collection, for example a section on Dogs in a collection of pages about pets, then the top level heading should assume a certain amount of context; just write <h1>Dogs</h1> while the title should work in any context: Dogs - Your Guide to Pets.
Unlike the title, this element can include links, emphasis and other HTML phrase elements.
The default font size for <h1> in some browsers have, unfortunately, motivated many writers and tools to use an <h2> element in stead. This is misleading to tools that take advantage of heading structure of pages, such as Amaya's table of contents view. Consider using Cascading Style Sheets, which are designed to express the author's preferred font sizes corresponding to elements such as <h1> and <h2>
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
After reading that I'm still not sure :)
Cheers,
Al.
Depends on how you use the graphic, but yes, it is still semantically correct. It's important that you provide adequate alt text and an even better solution would be using some sort of image replacement.
I see your point where it concerns blogs that don't have keywords in the title, however, that doesn't absolve the blog from using a heading structure on the site.
What I'm trying to get at is there should only be one H1 heading on any page. It's the most important heading and the one that encompasses all others. Deciding to use an H1 tag for post titles simply because the title of the blog doesn't contain keywords won't cut it.
Of course, this is my personal view and there's no definitive documentation. But, it appears to be the accepted norm, especially for accessibility.
~ Teli
P.S. Thanks for the compliments on the templates. :)
Depends on how you use the graphic, but yes, it is still semantically correct. It's important that you provide adequate alt text and an even better solution would be using some sort of image replacement.
I see your point where it concerns blogs that don't have keywords in the title, however, that doesn't absolve the blog from using a heading structure on the site.
What I'm trying to get at is there should only be one H1 heading on any page. It's the most important heading and the one that encompasses all others. Deciding to use an H1 tag for post titles simply because the title of the blog doesn't contain keywords won't cut it.
Of course, this is my personal view and there's no definitive documentation. But, it appears to be the accepted norm, especially for accessibility.
~ Teli
P.S. Thanks for the compliments on the templates. :)
Frankly, the date should have been wrapped in a paragraph tag, the blog's title should be in a heading level one and each of Darren's post titles should be in heading level 2. Again, just my opinion. ;)
~ Teli
Frankly, the date should have been wrapped in a paragraph tag, the blog's title should be in a heading level one and each of Darren's post titles should be in heading level 2. Again, just my opinion. ;)
~ Teli
However, I don't think you should use heading tags incorrectly just to accommodate weaknesses in current RSS feeders.
Also, I don't think on a pragmatic basis that RSS readers are enough of an issue to ditch the correct sue of headings. The benefits for SEO and accessibility of using semantic HTML (as as semantic as you can manage) far outweigh this downside.
However, I don't think you should use heading tags incorrectly just to accommodate weaknesses in current RSS feeders.
Also, I don't think on a pragmatic basis that RSS readers are enough of an issue to ditch the correct sue of headings. The benefits for SEO and accessibility of using semantic HTML (as as semantic as you can manage) far outweigh this downside.