Closed Bug 1140186 Opened 9 years ago Closed 9 years ago

Update meta tags on Firefox pages

Categories

(www.mozilla.org :: Pages & Content, enhancement)

Production
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: kohei, Assigned: kohei)

References

Details

(Whiteboard: [kb=1682738] [social])

Attachments

(1 file)

44 bytes, text/x-github-pull-request
Details | Review
+++ This bug was initially created as a clone of Bug #1133145 +++

https://www.mozilla.org/firefox/new/
https://www.mozilla.org/firefox/33.1/whatsnew/?oldversion=33.0.3
https://www.mozilla.org/firefox/all/
https://www.mozilla.org/firefox/developer/

The copy and images are in Bug 1131216.

William, do you want to use the Choose Independent graphic (attachment 8572004 [details]) as the *default* sharing image for pages under /firefox/ except /firefox/os/? The current default image is a small, simple Firefox logo, as specified by: 

<meta property="og:image" content="https://mozorg.cdn.mozilla.net/media/img/firefox/firefox-256.e2c1fc556816.jpg">

Also, the Developer Edition graphic (attachment 8572006 [details]) could be used for the download and firstrun pages:

https://www.mozilla.org/en-US/firefox/developer/all/
https://www.mozilla.org/en-US/firefox/38.0a2/firstrun/
Flags: needinfo?(williamr)
Blocks: 1131354, 1133049
(In reply to Kohei Yoshino [:kohei] from comment #0)
> William, do you want to use the Choose Independent graphic (attachment
> 8572004 [details]) as the *default* sharing image for pages under /firefox/
> except /firefox/os/? 

Yes, please use the Choose Independent graphic as the default sharing image for pages under /firefox/ except /firefox/os/ and the 3 Developer edition (/firefox/developer and the 2 pages below).

> Also, the Developer Edition graphic (attachment 8572006 [details]) could be
> used for the download and firstrun pages:
> 
> https://www.mozilla.org/en-US/firefox/developer/all/
> https://www.mozilla.org/en-US/firefox/38.0a2/firstrun/

Yes, please use the Developer Edition graphic for these pages as well. Thanks!
Flags: needinfo?(williamr)
Got it. I have a couple of questions on the copy:
https://docs.google.com/document/d/1co1xOwbok2rQg99SX0ySEsbm_3BtFWgJYvw3sJLgyJA

> https://www.mozilla.org/en-US/firefox/new/
> Headline: Choose the independent browser

In this case "Firefox" won't be included in the page title. Is this okay?

> https://www.mozilla.org/en-US/firefox/all/
> Headline: Download Firefox in [locale language name (ex Spanish)]

This page has been localized only in Japanese, so it's almost in English. "Download Firefox in English" might probably be confusing, at least for now, as this page has all language downloads as you see. The current title "Download Firefox in your language" might be better here?
Flags: needinfo?(williamr)
(In reply to Kohei Yoshino [:kohei] from comment #2)
> Got it. I have a couple of questions on the copy:
> https://docs.google.com/document/d/
> 1co1xOwbok2rQg99SX0ySEsbm_3BtFWgJYvw3sJLgyJA
> 
> > https://www.mozilla.org/en-US/firefox/new/
> > Headline: Choose the independent browser
> 
> In this case "Firefox" won't be included in the page title. Is this okay?
> 

Thanks for checking on these, Kohei.  I'm thinking we need to not change the /new title as right now it is optimized for SEO (vs optimized for sharing).  +Cmore to confirm
Flags: needinfo?(chrismore.bugzilla)
(In reply to Jennifer Bertsch [:jbertsch] from comment #3)
> (In reply to Kohei Yoshino [:kohei] from comment #2)
> > Got it. I have a couple of questions on the copy:
> > https://docs.google.com/document/d/
> > 1co1xOwbok2rQg99SX0ySEsbm_3BtFWgJYvw3sJLgyJA
> > 
> > > https://www.mozilla.org/en-US/firefox/new/
> > > Headline: Choose the independent browser
> > 
> > In this case "Firefox" won't be included in the page title. Is this okay?
> > 
> 
> Thanks for checking on these, Kohei.  I'm thinking we need to not change the
> /new title as right now it is optimized for SEO (vs optimized for sharing). 
> +Cmore to confirm

This bug is only about changing the og:title tag (which we have called headline in this bug). We are not proposing to change any text that appears on the page itself (which is already optimized for SEO), we only want to change the og: tags, which do not impact SEO.

(In reply to Kohei Yoshino [:kohei] from comment #2)
> Got it. I have a couple of questions on the copy:
> https://docs.google.com/document/d/
> 1co1xOwbok2rQg99SX0ySEsbm_3BtFWgJYvw3sJLgyJA
> 
> > https://www.mozilla.org/en-US/firefox/new/
> > Headline: Choose the independent browser
> 
> In this case "Firefox" won't be included in the page title. Is this okay?

Yes, this is okay for the og:title tag. The word "Firefox" appears in the og:description and the logo appears in the image.

> > https://www.mozilla.org/en-US/firefox/all/
> > Headline: Download Firefox in [locale language name (ex Spanish)]
> 
> This page has been localized only in Japanese, so it's almost in English.
> "Download Firefox in English" might probably be confusing, at least for now,
> as this page has all language downloads as you see. The current title
> "Download Firefox in your language" might be better here?

I agree. "Download Firefox in your language" is better than "Download Firefox in English".
Flags: needinfo?(williamr)
(In reply to William Reynolds [:williamr] from comment #4)
> Yes, this is okay for the og:title tag. The word "Firefox" appears in the
> og:description and the logo appears in the image.

Okay, the current templates use the same title for <title> and <meta property="og:title">, so I'll figure out how to differentiate those.
Attached file pull request
(In reply to Kohei Yoshino [:kohei] from comment #0)
> https://www.mozilla.org/firefox/33.1/whatsnew/?oldversion=33.0.3

Who is going to see this page? Does it make sense to update it? I would think nobody should see this page at this point
Please don't update the title on /firefox/new/ as that one has already been optimizations for SEO. All other pages, I am fine with. /firefox/new/ is critical to optimize to seo and not brand terms.
Flags: needinfo?(chrismore.bugzilla)
(In reply to Francesco Lodolo [:flod] from comment #7)
> (In reply to Kohei Yoshino [:kohei] from comment #0)
> > https://www.mozilla.org/firefox/33.1/whatsnew/?oldversion=33.0.3
> 
> Who is going to see this page? Does it make sense to update it? I would
> think nobody should see this page at this point

Good point, :flod. Nobody should see that page at this point. Instead, I suggest we update the meta tags on the /whatsnew pages starting with Firefox 36 (the current version). It appears these are the two current pages that we can update the meta tags on:

www.mozilla.org/firefox/36.0/whatsnew/?oldversion=35.0.1
www.mozilla.org/firefox/36.0.1/whatsnew/?oldversion=35.0.1

As Chris said in comment 8, let's be careful to not update the <title> tag. We do want to update the og:title tag with the copy from comment 0 where possible.
The whatsnew/firstrun pages don't have the Share button and are not essentially intended to be shared, I guess. Do we still need a description for those pages?

I'll keep the page title and description on /firefox/new/ and change only the og:title and og:description.
(In reply to Kohei Yoshino [:kohei] from comment #10)
> The whatsnew/firstrun pages don't have the Share button and are not
> essentially intended to be shared, I guess. Do we still need a description
> for those pages?

Yes. Even though there are no sharing buttons on those pages, there are thousands of people sharing the pages on their own. We want to update the og: tags for these pages so they will show relevant content on social networks.

> I'll keep the page title and description on /firefox/new/ and change only
> the og:title and og:description.

Great - thank you!
(In reply to William Reynolds [:williamr] from comment #11)
> (In reply to Kohei Yoshino [:kohei] from comment #10)
> > The whatsnew/firstrun pages don't have the Share button and are not
> > essentially intended to be shared, I guess. Do we still need a description
> > for those pages?
> 
> Yes. Even though there are no sharing buttons on those pages, there are
> thousands of people sharing the pages on their own. We want to update the
> og: tags for these pages so they will show relevant content on social
> networks.

Well, in that case, we might want to change the og:url too:

> <meta property="og:url" content="https://www.mozilla.org/en-US/firefox/36.0/whatsnew/">

Here, people share the dead-end page URL and it doesn't make sense. We could override the URL like this:

> <meta property="og:url" content="https://www.mozilla.org/en-US/firefox/new/">

Similarly, on the Developer Edition firstrun page:

> <meta property="og:url" content="https://www.mozilla.org/en-US/firefox/38.0a2/firstrun/">

could be 

> <meta property="og:url" content="https://www.mozilla.org/en-US/firefox/developer/">

Thoughts?

https://developers.facebook.com/docs/sharing/best-practices#tags
(In reply to Kohei Yoshino [:kohei] from comment #12)
> Well, in that case, we might want to change the og:url too:
> 
> > <meta property="og:url" content="https://www.mozilla.org/en-US/firefox/36.0/whatsnew/">
> 
> Here, people share the dead-end page URL and it doesn't make sense. We could
> override the URL like this:
> 
> > <meta property="og:url" content="https://www.mozilla.org/en-US/firefox/new/">
> 
> Similarly, on the Developer Edition firstrun page:
> 
> > <meta property="og:url" content="https://www.mozilla.org/en-US/firefox/38.0a2/firstrun/">
> 
> could be 
> 
> > <meta property="og:url" content="https://www.mozilla.org/en-US/firefox/developer/">

I think that is a great idea for both pages you suggested. It is a much better user experience to send people to /firefox/new and /firefox/developer instead of the whatsnew/firstrun pages. Those pages have better content for learning about the products too. Thanks for the suggestion!
Okay, I'll implement that :)
(In reply to William Reynolds [:williamr] from comment #11)
> Yes. Even though there are no sharing buttons on those pages, there are
> thousands of people sharing the pages on their own. 

Can you share some numbers? It seems an edge case, and creates quite the confusion (i.e. strings in shared base templates)
I'd like to question why we are adding sharing meta data to the /firstrun and /whatsnew pages. While it may be possible for someone to share a link, these URL's should be treated as in-product, as much of the code is written specifically for individual versions of Firefox. I don't think we should be encouraging sharing these URL's that may lead to giving people broken experiences.
Ah, I see Kohei has changed the sharing URL for the /firstrun and /whatsnew pages. This makes me less worried :) Still good to know if this is enough of an edge case to warrant doing or not.
Yes, but now I think that those Open Graph tags are not necessary on firstrun/whatsnew pages anyway. How about adding a Share button instead with an arbitrary URL and tweet like "Hey I just installed Firefox!" or "Whoa, this is the latest version of Firefox!" That may probably uplift referrals more and better.
(In reply to Kohei Yoshino [:kohei] from comment #18)
> Yes, but now I think that those Open Graph tags are not necessary on
> firstrun/whatsnew pages anyway. How about adding a Share button instead with
> an arbitrary URL and tweet like "Hey I just installed Firefox!" or "Whoa,
> this is the latest version of Firefox!" That may probably uplift referrals
> more and better.

If we add a share button to those pages, please just do it for the most recent /firstrun and /whatsnew. it would be superfluous to do it for every such page in bedrock.
Great discussion and question here - my answers are inline.

(In reply to Francesco Lodolo [:flod] from comment #15)
> (In reply to William Reynolds [:williamr] from comment #11)
> > Yes. Even though there are no sharing buttons on those pages, there are
> > thousands of people sharing the pages on their own. 
> 
> Can you share some numbers? It seems an edge case, and creates quite the
> confusion (i.e. strings in shared base templates)

Last year 748,241 users came to the /whatsnew page from a social network site. That makes /firefox/whatsnew the #3 landing page on mozilla.org from Social websites (/firefox/new is #1 and /plugincheck is #2). While we don't know how many people shared the page, we know that it is being shared by thousands of people.

We have a Q1 goal to amplify our marketing efforts by giving Firefox advocates ways to share and ultimately increase Firefox downloads. More information about Word of Mouth referrals is in this slide deck (page data is on slide 6):
https://docs.google.com/presentation/d/1HQG4lGTurNVgYxvTzf914T1PITNWrZaCDOJ-znUBgkM/edit?usp=sharing


(In reply to Alex Gibson [:agibson] from comment #16)
> I'd like to question why we are adding sharing meta data to the /firstrun
> and /whatsnew pages. While it may be possible for someone to share a link,
> these URL's should be treated as in-product, as much of the code is written
> specifically for individual versions of Firefox. I don't think we should be
> encouraging sharing these URL's that may lead to giving people broken
> experiences.

Our social media team very much wants better sharing meta data on top Mozilla pages in order to provide relevant content. Since our fans are already sharing these pages, we want to make sure the page previews shown on social sites look good, both visually  and with the right copy. Currently the default meta tag data does not create a good experience for users seeing it on social networks and we're losing an opportunity to talk with non-Firefox users who could become Firefox users.


(In reply to Alex Gibson [:agibson] from comment #17)
> Ah, I see Kohei has changed the sharing URL for the /firstrun and /whatsnew
> pages. This makes me less worried :) Still good to know if this is enough of
> an edge case to warrant doing or not.

Yes, changing the sharing URL is even better so that we can send people to the product download pages.


(In reply to Kohei Yoshino [:kohei] from comment #18)
> Yes, but now I think that those Open Graph tags are not necessary on
> firstrun/whatsnew pages anyway. How about adding a Share button instead with
> an arbitrary URL and tweet like "Hey I just installed Firefox!" or "Whoa,
> this is the latest version of Firefox!" That may probably uplift referrals
> more and better.

I think the Open Graph tags are still necessary, since hundreds of thousands of people will continue to see the page previews on Facebook and Twitter, and the Open Graph tags that generate those previews should be updated with the better content we have created.

I think adding a Share button on these pages would be good to try as an experiment. Since the /whatsnew page usually has one primary action (use Firefox Hello, watch this video, etc), we want to be careful to not take people away from that primary action. I suggest we consider adding a Share button in a separate bug.


(In reply to Alex Gibson [:agibson] from comment #19)
> If we add a share button to those pages, please just do it for the most
> recent /firstrun and /whatsnew. it would be superfluous to do it for every
> such page in bedrock.

100% agree.
I plan to push out all pending strings today, so it would be really helpful to figure out the strings eventually needed for tour pages.

Is it safe to assume the only one needed would be the following string, used as og:description?

> Firefox is non-profit, non-corporate, non-compromised. 
> Choosing Firefox isn’t just choosing a browser. 
> It’s a vote for personal freedom."
(In reply to William Reynolds [:williamr] from comment #20)
> (In reply to Alex Gibson [:agibson] from comment #19)
> > If we add a share button to those pages, please just do it for the most
> > recent /firstrun and /whatsnew. it would be superfluous to do it for every
> > such page in bedrock.
> 
> 100% agree.

There's going to be a whatsnew page for Fx37 (limited set of locales), and definitely one for Fx38. Maybe it makes sense to target the latter.

Can you confirm if the strings currently in the bug are all we need for now?
Flags: needinfo?(williamr)
Got information on IRC with the strings planned for whatsnew pages.
Flags: needinfo?(williamr)
Commits pushed to master at https://github.com/mozilla/bedrock

https://github.com/mozilla/bedrock/commit/275c287876ed043be299f3126d1b0eb559a41953
Fix Bug 1140186 - Update meta tags on Firefox pages

https://github.com/mozilla/bedrock/commit/e2a7657738ef9f0e702148251488423826822ec1
Merge pull request #2823 from kyoshino/bug-1140186-firefox-meta

Fix Bug 1140186 - Update meta tags on Firefox pages
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: