Forum Moderators: phranque
I know this is webmaster 101 stuff ... but there you go. That's where I am at!
Also you mentioned that nesting font tags withign the <H> tags will read as font. How do you suggest getting around the appearence of the large text if nesting is a no-no?
Even if the SE spiders start taking external CSS files, changing the size of an H tag shouldn't be a problem -- H tags are really about logical structure, and not visual rendering. That's why netcommr's input about not placing them out of order is important.
However, this is the first I've heard anyone recommend not repeating the same H tag number on a given page. I don't quite get why that's a problem. Documents of all kinds have more than one same-level heading. Using two similar H tags would still create a valid information structure, wouldn't it?
Take this [w3.org] page for example,
The headline of the page is the H1 tag, it is the main topic for the page, this page should only have 1 headline. I does mave multiple sections of the page, therefore multiple H2's, and under each H2 you can hace multiple H3's. This is also why you don't want to skip from an H1 to a H3, it would not be logically structure.
How I stated it above was wrong, I should have said you should usually never use an H1 more than once.
... I tend to think of the H1 tag as
the 'displayed' <title> of the document, in many instances
try this on your next test page
<h1>copy of title tag</h1>
copy of description
<h2>focused statement</h2>
<p>body text...
So to wrap it all together, H tags are about the information structure, not the visual rendering. This is an inheritance from SGML, which is HTML's parent language.
Browsers originally had a specific way of rendering H tags visually. With the advent of CSS we can play with that, but the informational hierarchy is what it always was, and highly important for a well formed page that makes an algorithm smile.