Forum Moderators: open
I'm not 100% about these reports, having not formally tested the idea. So I pass it on for your consideration.
I can see how exact wording might set off a filter that looks for potentially machine generated pages. And in practice, I don't always find that my Title content works well for humans when exactly duplicated as a page heading.
Since I know that the Google staff loves "natural" pages and hates having their algo manipulated, I've decided to keep a bit of variation between the two when it feels natural for the human user.
Further, I leave it large and bold. I feel that it lets the user know, loud and clear, what the focus of this page is. I have never done any tests with H1, but feel is strongly falls into the usability arena.
Seems to me H tags are no big deal.
Not a big deal by themselves. But, when you combine them with other elements on the page, they begin to work as part of the team. It's a team effort! ;)
And please remember, this is all about document structure, not whether or not an <h1> is going to help with rankings. By itself, it may not have much effect. Combined with other elements and it could be the one element that helps users to find your site more easily.
[edited by: pageoneresults at 11:11 pm (utc) on June 19, 2003]
I know you said you were not 100% but I don't think google would filter this if WC3 recommends.
WC3 says the following:
"The title is generally duplicated in an <h1> element towards the top of the page. Unlike the title, this element can include links, emphasis and other HTML phrase elements."
Point taken. I just got into the habit of throwing up quick pages with frontpage and didn't bother to use their H tag feature. Large and bold text seems to accomplish the same thing. I'll try it on some lagging sites and see what happens.
Document structure did u mean all the elements or factors like bold, link text,keyword location etc.
Could you eloborate on these?And please indicate specific team members...:)
I am personally of the opinion that till now I have implemented most of the on page optimization techiniques I learned here, but couldn't implement <H1>.Due to css style sheet, which I am learning now.
This week will try out that and get back to our team of seo's here
:) and I hope to get into top 10 from top 20.
Aravind
Do any of you have an idea whether there is much difference between h1, h2 and h3 tags.
I think there is a difference between <h1> and other <hx> tags.
I know I could make my pages look better by using css but it seems a little risky to me.
I think using CSS is not a Problem. Maybe Nick or some other HTML forum specialist will clear it out.
...don't think google would filter this if WC3 recommends
I agree - I only reported what I did because I heard it from two sources, and one of them has been extremely reputable over many years.
However, I validated some pages at the W3C right after I made that post. And my Tip Of The Day on their validation page was -- you guessed it -- "duplicate your page title in an <h1> element."
I agree - probably not a problem at all.
difference between h1, h2 and h3
You can't legitimately use <H2> or <H3> unless the previous, lower-numbered tag has already appeared in the document. It's about headings and sub-headings, the logical structure of the document.
Because many of us learned "street HTML" -- you know, just make it look the way you want no matter what code it takes -- we got the idea that HTML markup was about rendering. And especially with HTML 3.2, the W3C started to go in that direction. But they've rapidly backed off that approach.
The use of an <Hn> element has nothing to do with how a browser renders the tag's appearance.
In fact, the W3C has been working on an accessibility "validator" and one of the errors it will report is whether the <Hn> elements are properly formed. That is:
1. No <Hn> element can be used unless there was a preceeding <Hn-1> element
2. No jumps from <Hn> to <Hn+2> or further.
3. Only one <H1> element per document.
HTML is about the structure of the document's content. CSS is about instructions for how various user agents should render that content. The entire direction and development of HTML/CSS is the separation of content and appearance.
Search engines are looking for content, not appearance or rendering. There is one, but only one, exception here -- search engines don't like your content to be rendered as invisible ;) But styling any element to be aesthetically pleasing is what CSS is all about and there is absolutely no problem with it at all.
At any rate, using <hn> tags to clarify the structure and logic of your document is what makes sense. So of course, keywords will naturally appear in them. I mean, wouldn't a sub-heading naturally set apart one of the major subjects of a document? And wouldn't the page's heading itself say something key about entire page's topic?
I'd say it's really a simple thing. It's all about making your page's content totally obvious to a relatively stupid machine intelligence.