Closed Bug 663925 Opened 9 years ago Closed 9 years ago

[SEO] Update H1, H2, H3 in copy on specified pages

Categories

(www.mozilla.org :: General, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: christine.brodigan, Assigned: sgarrity)

Details

Attachments

(1 file)

As we round out our SEO efforts, we'd like to see changes made to H1, H2, H3 text on the user-facing page designs.

Pages for this update are identified in column "M" here: http://bit.ly/ieMuHL

Thank you! Please ping CB with questions.
Assignee: nobody → steven
Bumping to 2.10 as 2.9 is full of Fx5 critical stuff.
OS: Mac OS X → All
Hardware: x86 → All
Target Milestone: 2.9 → 2.10
Priority: -- → P1
As mentioned in Bug 657387, <h1> tag is used on all mozilla.com pages to wrap the "Mozilla Firefox" title/image in the top left of the template.

The page-specific heading is then the <h2> tag.

Is this bug proposing to change that, or should I interpret the changes in the spreadsheet as H1->H2, H2->H3, etc?

Also, the /firefox/fx/ page has been re-worked and no longer contains the Panda/wheel image/text.
Much of the test in the spreadsheet for this bug seems to already match the copy on the pages. Chrissie, can you clarify?
(In reply to comment #3)
> Much of the test in the spreadsheet for this bug seems to already match the
> copy on the pages. Chrissie, can you clarify?

As soon as I'm at my desk I will review. Super surprised about the panda page change. Could you tell me where that bug is?
(In reply to comment #4)
> As soon as I'm at my desk I will review. Super surprised about the panda
> page change. Could you tell me where that bug is?

Bug 659514.
(In reply to comment #2)
> As mentioned in Bug 657387, <h1> tag is used on all mozilla.com pages to
> wrap the "Mozilla Firefox" title/image in the top left of the template.
> 
> The page-specific heading is then the <h2> tag.
> 
> Is this bug proposing to change that, or should I interpret the changes in
> the spreadsheet as H1->H2, H2->H3, etc?
> 
> Also, the /firefox/fx/ page has been re-worked and no longer contains the
> Panda/wheel image/text.

Steven,

I just updated the spreadsheet, so you'll notice there will be multiple H2s per page, which is OK. Later this week on the Thursday call it woud be great to just get a better understanding of how we might switch out H1 if it's not helping with SEO to an H4 and then we can better utilize H1 in other areas of the pages.

Forget the Panda/Sync page for this bug, we'll work on that in Q3.

And, yes, a lot of these copy-wise should be pretty similar to what's there now, it's more about updating the markup to reflect H2, etc. 

LMK if there are other outstanding questions.

:)CB
Target Milestone: 2.10 → 3.0
Some comments and issues I ran into while trying to implement this:


> http://www.mozilla.com/en-US/firefox/new
> H2: Download Mozilla Firefox Web browser for free
> H2: Get Firefox on your phone
> H3: Tour Mozilla Firefox

Is "Download Mozilla Firefox Web browser for free" intended to replace the "Made to make the Web a better place." heading that's there now? It's a bit awkward to fit in that space. I'll attach a screenshot of the best fit I was able to work out.


> http://www.mozilla.com/en-US/firefox/fx
This page has been redesigned.

> http://www.mozilla.com/en-US/firefox/features/
> H2: Learn about Firefox Web browser features
> H2: Top Firefox features
> H3: Browsing made easy

For the first H2 tag ("Learn about Firefox Web browser features"), should this replace the "Firefox FEATURES" heading? this proposed headline doesn't break up easily into two lines (one italic, one bold/caps).

For the "Top Features" tag - it's current an H3 - which I think makes sense as a side-bar.


> http://www.mozilla.com/en-US/firefox/security/
> H2: Firefox helps you stay safe
> H2: Protect your privacy
> H3: Browse with security

The "Protect your privacy" and "Browse with security" headings are peers in the document - why do we want one as an H2 tag?


> http://www.mozilla.com/en-US/firefox/performance/
> H2: Blazing performance
> H2: Making the Web faster
> H3: Web application speed

Same issue as the Security page - the second two headings are peers - why should one be an H2 tag?


> http://www.mozilla.com/en-US/firefox/customize/
> H2: Easy ways to personalize
> H2: Go mobile
> H3: Add style: Personas

Like "Top Features" on the Features page, "Go mobile" is current an H3 - which I think makes sense as a side-bar.


> http://www.mozilla.com/en-US/firefox/technology/
> H2: Built on open technology
> H2: Innovating with HTML5
> H3: Beautifying with CSS

Same issue as the Security page - the second two headings are peers - why should one be an H2 tag?


> http://www.mozilla.com/en-US/firefox/video/
> H2: Our videos
> H3: The rest of the video titles

This is already setup this way.
(In reply to comment #7)
> Created attachment 543792 [details]
> Screenshot of updated headline on /firefox/new/ page
> 
> Some comments and issues I ran into while trying to implement this:
> 
> 
> > http://www.mozilla.com/en-US/firefox/new
> > H2: Download Mozilla Firefox Web browser for free
> > H2: Get Firefox on your phone
> > H3: Tour Mozilla Firefox
> 
> Is "Download Mozilla Firefox Web browser for free" intended to replace the
> "Made to make the Web a better place." heading that's there now? It's a bit
> awkward to fit in that space. I'll attach a screenshot of the best fit I was
> able to work out.


Argh. Great catch. Please do not replace the H2, which should read, "Made to make the web a better place."


> 
> > http://www.mozilla.com/en-US/firefox/fx
> This page has been redesigned.
> 
> > http://www.mozilla.com/en-US/firefox/features/
> > H2: Learn about Firefox Web browser features
> > H2: Top Firefox features
> > H3: Browsing made easy

Yes, thanks Steven, we were behind on this, so don't worry about it.

> For the first H2 tag ("Learn about Firefox Web browser features"), should
> this replace the "Firefox FEATURES" heading? this proposed headline doesn't
> break up easily into two lines (one italic, one bold/caps).
> 
> For the "Top Features" tag - it's current an H3 - which I think makes sense
> as a side-bar.
> 
> 
> > http://www.mozilla.com/en-US/firefox/security/
> > H2: Firefox helps you stay safe
> > H2: Protect your privacy
> > H3: Browse with security
> 
> The "Protect your privacy" and "Browse with security" headings are peers in
> the document - why do we want one as an H2 tag?

They should both be H2s.
 

> > http://www.mozilla.com/en-US/firefox/performance/
> > H2: Blazing performance
> > H2: Making the Web faster
> > H3: Web application speed
> 
> Same issue as the Security page - the second two headings are peers - why
> should one be an H2 tag?

They should both be H2s.

> > http://www.mozilla.com/en-US/firefox/customize/
> > H2: Easy ways to personalize
> > H2: Go mobile
> > H3: Add style: Personas
> 
> Like "Top Features" on the Features page, "Go mobile" is current an H3 -
> which I think makes sense as a side-bar.

H2 is more valuable, and unfortunately "Easy ways to personalize" has no search-friendly juice. If it needs to be an H3 that's OK, it's just the only truly helpful word on the page.

> 
> > http://www.mozilla.com/en-US/firefox/technology/
> > H2: Built on open technology
> > H2: Innovating with HTML5
> > H3: Beautifying with CSS
> 
> Same issue as the Security page - the second two headings are peers - why
> should one be an H2 tag?

Both should be peers.

> 
> > http://www.mozilla.com/en-US/firefox/video/
> > H2: Our videos
> > H3: The rest of the video titles
> 
> This is already setup this way.

Cool.
Target Milestone: 3.0 → 3.1
Target Milestone: 3.1 → 3.2
Implemented in trunk in r92643. Merged to stage in r92646.

Left the side-bar headings as is for now.
Status: NEW → RESOLVED
Closed: 9 years ago
Keywords: qawanted
Resolution: --- → FIXED
Tested on stage,leaving this for Chrissy to confirm
Keywords: qawanted
pushed to production r92712
Component: www.mozilla.org/firefox → www.mozilla.org
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in before you can comment on or make changes to this bug.