Twenty Fourteen: Fixing some SEO issues (H1 & Rich Snippets)

[Vyndariel]

Fixed H1 mess-up
Added 'updated' to entry-date variable for rich snippet support

[Vyndariel]

svn patch for ticket

[markoheijnen]

Can you please add a patch from the root instead of inside a theme. Also from here you need to guess the theme but I guess it's twentyfourteen.

For only titles I would say invalid since as far as I know h1 inside an article is totally fine. No clue about adding the class 'updated' in inc/template-tags.php but that seems invalid too. Since it doesn't have to be the updated time.

[Vyndariel]

Patch from root

[Vyndariel]

Added patch-file from root

h1 on single pages is fine, but currently you have all titles as h1 elements, no matter if they're in category, tags, frontpage.

from seo point of view there should be only 1 h1-element per page, which is fine for the title on single.php, but front-page has the website-name as h1-element + all titles from all posts. So I changed all, except from single to h2.

for the updated-tag: as you can see here ​http://bit.ly/1cNMCDG currently the updated variable is missing to work smoothly with google structured data and by the suggested changes it'll work.

[markoheijnen]

Are you sure from a HTML5 perspective? I thought it was fine to have a h1 for every article

[Vyndariel]

Replying to markoheijnen:

Are you sure from a HTML5 perspective? I thought it was fine to have a h1 for every article

Well, I don't know from HTML5 perspective, but I'm definitely from SEO / Google perspective.

H1 describes the most important information on your page, with a drilldown on H2 and even Google and Matt Cutts tell you that there should be only 1 H1 element

[sabreuse]

You're incorrect on that point -- Cutts has been saying since at least 2009 that multiple H1s are fine when they make semantic sense, such as for distinct articles or sections on a page (ref: ​http://www.youtube.com/watch?v=GIn5qJKU8VM). What you shouldn't do (and we don't) is use them all over the place just for visual impact or with the intention of making article content look more "important". This is an old SEO myth that refuses to die, and we shouldn't be building WordPress to appease a myth.

As for validity, it's perfectly valid HTML5.