WordPress.org

Make WordPress Core

Opened 4 years ago

Closed 4 years ago

#26279 closed enhancement (invalid)

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

Reported by: Vyndariel Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.8
Component: Bundled Theme Keywords: has-patch
Focuses: Cc:

Description

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

Attachments (2)

.patch (4.6 KB) - added by Vyndariel 4 years ago.
svn patch for ticket
new.patch (5.4 KB) - added by Vyndariel 4 years ago.
Patch from root

Download all attachments as: .zip

Change History (10)

@Vyndariel
4 years ago

svn patch for ticket

#1 @markoheijnen
4 years ago

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.

Last edited 4 years ago by markoheijnen (previous) (diff)

#2 @SergeyBiryukov
4 years ago

  • Component changed from Themes to Bundled Theme
  • Summary changed from FIxing some SEO issues (H1 & Rich Snippets) to Twenty Fourteen: FIxing some SEO issues (H1 & Rich Snippets)

@Vyndariel
4 years ago

Patch from root

#3 @Vyndariel
4 years ago

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.

Last edited 4 years ago by Vyndariel (previous) (diff)

#4 follow-up: @markoheijnen
4 years ago

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

#5 @SergeyBiryukov
4 years ago

  • Summary changed from Twenty Fourteen: FIxing some SEO issues (H1 & Rich Snippets) to Twenty Fourteen: Fixing some SEO issues (H1 & Rich Snippets)

#6 in reply to: ↑ 4 @Vyndariel
4 years ago

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

#7 @sabreuse
4 years ago

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.

#8 @helen
4 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.