Hello everyone, There are many cases that you should repeat h1 or others headers.
I do many homepages or homepages of areas, and i don't know were i should or not use the h1. I don't use in page title because is not relevant. The correct use should be on the titles of modules that i use, such as "last news" or "last updates" or any title of some list of items. And they have the some importance. This problem will be solved, I hope, with the use of <section> and <header> in HTML5. Gaspar On 16/10/2009, Darren Lovelock <i...@munkyonline.co.uk> wrote: > > > > > To have the logo as a H1 on every page will most likely trigger spam filters > in the search engines as you are duplicating the heading throughout the > website, they should always be unique. Anyone advising to do this to boost > your page's keyword relevancy simply doesn't know what they are talking > about. > > I cant think of a single reason why you would wrap a H1 around a logo as > there is no advantage to you, search engines or your visitors. Maybe if you > had a business directory where each listing had its own logo and alt text of > the company name then it could work there but not if there was already an H1 > on the page. > > The only case that you could possibly use two H1s on a page is if you had a > page containing two entirely different topics. But then again wouldn't you > just put this content on two separate pages? If your sites theme is to write > about lots of different content e.g. a general blog, then it should have a > main H1 and each topic be summarised using H2's and then include a link to > their own individual pages. > > Why is the topic starter looking for reasons for why they shouldn't do it, > when they should be asking themselves what is their reason for using the H1 > this way in the first place? > > Did they see it on some 'SEO's website and think 'they must know what they > are doing so I'll copy them'? LOL > > Maybe they should listen to the SEO expert they've already spoken to... > > I would have thought it's pretty obvious that you shouldn't do it ;) > > > Darren Lovelock > Munky Online Web Design > http://www.munkyonline.co.uk > T: +44 (0)20-8816-8893 > > ________________________________ > From: li...@webstandardsgroup.org > [mailto:li...@webstandardsgroup.org] On Behalf Of EBS Admin > Sent: 16 October 2009 15:52 > > To: wsg@webstandardsgroup.org > Subject: RE: [WSG] RE: More than one H1? > > > > The way to wrap the H1 for the logo is not to wrap it around an image, the > fist H1 should be text with keywords for the page that is being represented > in a grammatical format, with clever use of CSS these can be styled up to > look like graphic logos but degrade for accessibility and provide a tool to > get the H1 as the first element in a page whilst complementing the > semantics, accessibility and seo requirements. > > ________________________________ > From: li...@webstandardsgroup.org > [mailto:li...@webstandardsgroup.org] On Behalf Of > ja...@flexewebs.com > Sent: 16 October 2009 15:45 > To: wsg@webstandardsgroup.org > Subject: Re: [WSG] RE: More than one H1? > > > Yes but my argument against putting the H1 around the logo is that the logo > is present on all pages and typically each site will be optimised for it's > brand name (e.g. Flexewebs) so no value in highlighting that. > > I would potentially agree with you if you were arguing for putting H1 around > other content within the page, but certainly not the logo. > > Sent from my BlackBerry® wireless device ________________________________ > > From: "EBS Admin" <ad...@essentialebizsolutions.net> > Date: Fri, 16 Oct 2009 15:36:00 +0100 > To: <wsg@webstandardsgroup.org> > Subject: RE: [WSG] RE: More than one H1? > > > Okay so the justify, the first H1 is the title of a page which is to be > shown at the top of a page commonly used as the logo. The next h1 will be > the subject title i.e. Welcome to... so semantically this would require more > the 1 H1. > > For accessibility which styles switched off it clearly breaks up the pages, > and has a similar effect for screen readers. > > Hope this makes it a little clearer. > > ________________________________ > From: li...@webstandardsgroup.org > [mailto:li...@webstandardsgroup.org] On Behalf Of Jason > Grant > Sent: 16 October 2009 15:25 > To: wsg@webstandardsgroup.org > Subject: Re: [WSG] RE: More than one H1? > > > EBS Admin - Matt doesn't say to use multiple H1s on the page, but says that > you will not get penalised for using them (within reason) on a given page. > Every site I ever worked on I had used only one H1 on and it still enjoys > being on first page of Google. > My formula, hence, does not only say Google or only Accessibility, but all > of the points I mentioned. > You say it is semantic to use more than one H1, but don't actually justify > your reasoning behind it. > > > On Fri, Oct 16, 2009 at 3:02 PM, EBS Admin > <ad...@essentialebizsolutions.net> wrote: > > > > > > > Jason, > > Thats clearly not the case, if you read the WIA guidlines then is > advocates the use of multiple H1's, from an semantic point of view they make > sense and in terms of SEO the make sense because every site we've built uses > mutiple H1's and they enjoy page 1 results on Google. > > > > The video that Tim has just sent in is by Google and they say to use > multiple H1's! > > > > ________________________________ > From: li...@webstandardsgroup.org > [mailto:li...@webstandardsgroup.org] On Behalf Of Jason > Grant > > Sent: 16 October 2009 14:48 > > To: wsg@webstandardsgroup.org > > > > Subject: Re: More than one H1? (was [WSG] Out of Office AutoReply: WSG > Digest) > > > > > > Tim > > > > > > To keep it really simple: > > > > > > Spec + SEO + Good IA + Semantics + Accessibility + Common sense == One H1 > per page > > > > > > Hope this makes sense? > > > > > > Thanks, > > > > Jason > > > > > > On Fri, Oct 16, 2009 at 2:39 PM, Tim White <tjameswh...@gmail.com> wrote: > > > > > OK, straight from Google Webmaster Central: > > > > http://www.youtube.com/watch?v=GIn5qJKU8VM&feature=channel > > > (video from March 2009) > > > > > > > > > Tim > > > > > > > > > > > > > > > On Fri, Oct 16, 2009 at 7:55 AM, Jason Grant <ja...@flexewebs.com> > wrote: > > > > > > > > > > > > > > > Tim, > > > > > > > > Well done for reading the spec - it's always a must. > > > > > > > > > > > > However, Google came after the HTML4.01 spec and what Google wants we > give it - so the 'only one H1 per page' guideline comes from SEO best > practices as well as general semantics and IA best practices. > > > > > > > > > > > > So the spec does not tell you to use one H1 per page, but the spec is > not the be all and end all of guidelines. > > > > > > > > > > > > > > > > Thanks, > > > > > > > > Jason > > > > > > > > > > > > > > > > > > > > On Fri, Oct 16, 2009 at 12:32 PM, Tim White <tjameswh...@gmail.com> > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Oct 16, 2009 at 4:23 AM, Marilyn Langfeld > <m...@langfeldesigns.com> wrote: > > > > > > > > > > > > > > > > > > > > > > > ... > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > H1 is reserved for the title of the page. In a document, at least, > there's only one title, while there may be many first level headings. > > > > > > ... > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > So H1 is, IMHO, not the first level header, but the T1, or main > title of the page. A logo is never, IMHO again, the title of the page. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Let's look at what the specification says; > > > > > > > > > > > > > > > "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/TR/html401/struct/global.html#h-7.5.5 > > > > > > > > > > Nowhere does it say that H1s are for page titles or that there can > be only 1 per page. In fact, the example shows two being used. > > > > > > > > > > ~ Tim > > > > > > > > > > > > > > > > > > > > > ******************************************************************* > > > > > > > > > > List Guidelines: > http://webstandardsgroup.org/mail/guidelines.cfm > > > > > Unsubscribe: > http://webstandardsgroup.org/join/unsubscribe.cfm > > > > > Help: memberh...@webstandardsgroup.org > > > > > > ******************************************************************* > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > Jason Grant BSc, MSc > > > > CEO, Flexewebs Ltd. > > > > www.flexewebs.com > > > > ja...@flexewebs.com > > > > +44 (0)7748 591 770 > > > > Company no.: 5587469 > > > > > > > > www.flexewebs.com/semantix > > > > www.twitter.com/flexewebs > > > > www.linkedin.com/in/flexewebs > > > > > > > > > > > > > ******************************************************************* > > > > > > > > > > > > > > > > > > > > List Guidelines: > http://webstandardsgroup.org/mail/guidelines.cfm > > > > Unsubscribe: > http://webstandardsgroup.org/join/unsubscribe.cfm > > > > Help: memberh...@webstandardsgroup.org > > > > > ******************************************************************* > > > > > > > > > > > > > > > > > > > > > > ******************************************************************* > > > List Guidelines: > http://webstandardsgroup.org/mail/guidelines.cfm > > > Unsubscribe: > http://webstandardsgroup.org/join/unsubscribe.cfm > > > Help: memberh...@webstandardsgroup.org > > > > ******************************************************************* > > > > > > > > -- > > Jason Grant BSc, MSc > > CEO, Flexewebs Ltd. > > www.flexewebs.com > > ja...@flexewebs.com > > +44 (0)7748 591 770 > > Company no.: 5587469 > > > > www.flexewebs.com/semantix > > www.twitter.com/flexewebs > > www.linkedin.com/in/flexewebs > > > > > > > ******************************************************************* > > List Guidelines: > http://webstandardsgroup.org/mail/guidelines.cfm > > Unsubscribe: > http://webstandardsgroup.org/join/unsubscribe.cfm > > Help: memberh...@webstandardsgroup.org > > > ******************************************************************* > > > > No virus found in this incoming message. > > Checked by AVG - www.avg.com > > Version: 8.5.421 / Virus Database: 270.14.20/2439 - Release Date: 10/15/09 > 20:39:00 > > > > > > > > > > > ******************************************************************* > > List Guidelines: > http://webstandardsgroup.org/mail/guidelines.cfm > > Unsubscribe: > http://webstandardsgroup.org/join/unsubscribe.cfm > > Help: memberh...@webstandardsgroup.org > > > ******************************************************************* > > > > -- > Jason Grant BSc, MSc > CEO, Flexewebs Ltd. > www.flexewebs.com > ja...@flexewebs.com > +44 (0)7748 591 770 > Company no.: 5587469 > > www.flexewebs.com/semantix > www.twitter.com/flexewebs > www.linkedin.com/in/flexewebs > > ******************************************************************* > List Guidelines: > http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: > http://webstandardsgroup.org/join/unsubscribe.cfm > Help: memberh...@webstandardsgroup.org > ******************************************************************* > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 8.5.421 / Virus Database: 270.14.20/2439 - Release Date: 10/15/09 > 20:39:00 > > ******************************************************************* > List Guidelines: > http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: > http://webstandardsgroup.org/join/unsubscribe.cfm > Help: memberh...@webstandardsgroup.org > ******************************************************************* > ******************************************************************* > List Guidelines: > http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: > http://webstandardsgroup.org/join/unsubscribe.cfm > Help: memberh...@webstandardsgroup.org > ******************************************************************* > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 8.5.421 / Virus Database: 270.14.20/2439 - Release Date: 10/15/09 > 20:39:00 > > ******************************************************************* > List Guidelines: > http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: > http://webstandardsgroup.org/join/unsubscribe.cfm > Help: memberh...@webstandardsgroup.org > ******************************************************************* > > ******************************************************************* > List Guidelines: > http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: > http://webstandardsgroup.org/join/unsubscribe.cfm > Help: memberh...@webstandardsgroup.org > ******************************************************************* ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *******************************************************************
