Closed Bug 920212 Opened 11 years ago Closed 11 years ago

Redirect /firefox/fx/ to /firefox/new/

Categories

(www.mozilla.org :: Bedrock, defect)

Product:
www.mozilla.org
Component:
Bedrock
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: cmore, Assigned: retornam)

References

(Blocks 1 open bug)

Details

(Whiteboard: [kb=1135301] )

The next step in the unified download project is to redirect /firefox/fx/ to /firefox/new/. The /firefox/new/ page can handle both desktop and mobile with conditional content and correct buttons. Traffic to /firefox/fx/ is about 6% of the traffic compared to /firefox/new/ and it is 91% desktop visitors. Since /firefox/fx/ is promoting Android and 91% of the visitors are desktop, and to view desktop you have to click another tab, only 8% of those visitors download Firefox for desktop -- we can surely do better on the /firefox/new/ page. If we can convert the 6% of additional traffic originally from /firefox/fx/ at the conversion rate on /firefox/new/, this redirect will be a high impact change. The /firefox/new/ has good conversion rates and can handle desktop and mobile without having to add an extra step of clicking a desktop or mobile tab as on the /firfox/fx/. We also promote mobile on the /firefox/new/ page for users running the latest version of Firefox. When we redirect /firefox/fx/ to /firefox/new/ we should make sure we pass along all query parameters to /firefox/new/ for campaign tracking. Also, we should adjust the main /firefox/ redirect to point people directly to /firefox/new/ to eliminate an additional redirect.
Blocks: 868199
Users primarily currently get to /firefox/fx/ from organic search and from the main www.mozilla.org/firefox/ redirect and there is a long-tail of referral traffic.
One complexity about this change is that the Firefox nav header points to /firefox/fx/ for mobile. Until we have the Firefox family website complete, changing the "Mobile" header link to point to /mobile/ and "Desktop" to /firefox/new/ is probably the best solution.
+1 from an l10n perspective, that will make our life much easier to have this big php page on python for locales.
Also, another reason to redirect /firefox/fx/ to /firefox/new/ is that /firefox/fx/ in bedrock is en-US only and all other locales have the old pinstripe php legacy design.
+1 for getting rid of legacy pages!
Live date for /firefox/family is Nov 20. Let's do it then.
(In reply to Jennifer Bertsch [:jbertsch] from comment #6) > Live date for /firefox/family is Nov 20. Let's do it then. This is a small change and will more likely affect ADIs given the low conversion rate on /firefox/fx/, the amount of possible downloads between now and Nov. 20th is fairly high. The sooner we can get this change done, the sooner we could recover some of the ADI decline in Firefox desktop.
Ok, we have a plan of attack here: For now, let's make this change: 1) change the /firefox/ redirect to *only* point to /firefox/new/. Once the Firefox family website is live at the end of November 2013: 1) Remove /firefox redirect as it will be the home for firefox. 2) Remove references to /firefox/fx/ in mozilla.org and point them to firefox family URLs. 3) Redirect /firefox/fx/ legacy URL to /firefox/new/ This helps gets traffic from the main /firefox redirect and firefox.com to the best download page we have and that is at /firefox/new/. It also doesn't make the site any worse by taking /firefox/fx/ out of the mix given that it unfortunately turned into the mobile product page, which was never the original intention. Yes, a bit of a mess, but it is what we have for now. How does this sound?
Chris - Sounds like a great plan. I approve. Thanks.
Here is an Etherpad of the firefox.fx and firefox/fx references in bedrock that will need to be updated after the Firefox family website is live: https://etherpad.mozilla.org/firefox-fx-bedrock-references
Depends on: 920268
Blocks: 855132
(In reply to Jennifer Bertsch [:jbertsch] from comment #6) > Live date for /firefox/family is Nov 20. Let's do it then. err, what is firefox/family? l10n needed I suppose?
(In reply to Pascal Chevrel:pascalc from comment #11) > (In reply to Jennifer Bertsch [:jbertsch] from comment #6) > > Live date for /firefox/family is Nov 20. Let's do it then. > > err, what is firefox/family? l10n needed I suppose? The Firefox family website will eventually be located at www.mozilla.org/firefox. It will be the new home for all-things Firefox since the legacy architecture of mozilla.org is very desktop-centric. It will be the hub to go to to learn about desktop, mobile, os, and marketplace. There will be sub-sections for each product that will replace some of the existing firefox desktop product content and complimenting what we already created for Firefox OS. The URLs will probably be something like /firefox/, /firefox/desktop/, /firefox/mobile/, /firefox/os/, /firefox/marketplace/, etc. This project has been discussed for about 6 months now in the WebProd check-in meeting and the mozilla.org meeting. It was put on hold the past 5 months due to Firefox OS priorities, but it is back alive and we are aiming for 2013-11-20 launch date and it will be localized. jbertch and malexis can provide some additional details. The tracking bug is bug 855132 and we will be soon adding more info to it.
(In reply to Chris More [:cmore] from comment #12) > The tracking bug is bug 855132 and we will be soon adding more info to it. Thanks, the sooner we get the templates done the better, I heard we have a lot of FirefoxOS stuff to translate next quarter too :)
(In reply to Pascal Chevrel:pascalc from comment #13) > (In reply to Chris More [:cmore] from comment #12) > > The tracking bug is bug 855132 and we will be soon adding more info to it. > > Thanks, the sooner we get the templates done the better, I heard we have a > lot of FirefoxOS stuff to translate next quarter too :) It is still in design/prototype phase now. We make sure l10n has a early heads up.
Whiteboard: [kb=1135301]
We will put this redirect in place after bug 855132 (family page) is resolved.
Blocks: 764129
Blocks: mozorg-redirects
jbertsch/habber/cmore made the decision today to redirect /firefox/fx/ (all locales) to /firefox/new/ for the Australis launch.
Summary: Redirect /firefox/fx/ to /firefox/new/ for the Unified Firefox Download project → Redirect /firefox/fx/ to /firefox/new/
Blocks: 939305
Flags: needinfo?(chrismore.bugzilla)
Yes please Raymond, let's redirect /firefox/mobile to /firefox/partners for now. Do you want me to file a separate bug?
Flags: needinfo?(chrismore.bugzilla)
(In reply to Jennifer Bertsch [:jbertsch] from comment #18) > Yes please Raymond, let's redirect /firefox/mobile to /firefox/partners for > now. Do you want me to file a separate bug? Thanks Jen. Please don't file a new bug. We can work off this bug. Thanks.
Assignee: nobody → mozbugs.retornam
Raymond: any movement on comment 18?
Flags: needinfo?(mozbugs.retornam)
submitted https://github.com/mozilla/bedrock/pull/1866
Flags: needinfo?(mozbugs.retornam)
(In reply to raymond [:retornam] (needinfo? me) from comment #21) > submitted https://github.com/mozilla/bedrock/pull/1866 That's changing the links and needs to happen. We will still need another PR to redirect /firefox/fx/ and /firefox/new/.
(In reply to Chris More [:cmore] from comment #22) > (In reply to raymond [:retornam] (needinfo? me) from comment #21) > > submitted https://github.com/mozilla/bedrock/pull/1866 > > That's changing the links and needs to happen. We will still need another PR > to redirect /firefox/fx/ and /firefox/new/. The first pull request has been merged. I'll follow up with removing /firefox/fx and redirect it to /firefox/new/
Could we simply use the /firefox/ URL for the landing page, instead of /firefox/new/ ?
Hi Kohei- I'll let Cmore provide a final answer, but the longer term plan (July?) for the /firefox/ url is to have a page that talks about all Firefox products (Fx OS, desktop, Android, Marketplace, etc) live there. So I would stick with redirecting /firefox/fx to /firefox/new Thx, Jen
Flags: needinfo?(chrismore.bugzilla)
Understood, thanks!
Submitted https://github.com/mozilla/bedrock/pull/1915 which redirects firefox/fx desktop instances to firefox/new
Status: NEW → ASSIGNED
OS: Mac OS X → All
Hardware: x86 → All
(In reply to raymond [:retornam] (needinfo? me) from comment #27) > Submitted https://github.com/mozilla/bedrock/pull/1915 which redirects > firefox/fx desktop instances to firefox/new let's just do /firefox/fx/ to /firefox/new/ since /firefox/ will soon be the desktop family website even though /firefox/ redirects to /firefox/new/ for now.
Flags: needinfo?(chrismore.bugzilla)
Commits pushed to master at https://github.com/mozilla/bedrock https://github.com/mozilla/bedrock/commit/9edbbc678b5e349b5a8f95cab6858a3848d9bca4 Bug 920212 - Redirect /firefox/fx/ to /firefox/new/ https://github.com/mozilla/bedrock/commit/3019601a288458b3628a9aa2064196640af74679 Merge pull request #1915 from retornam/bug-920212 Bug 920212 - Redirect /firefox/fx/ to /firefox/new/
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Commits pushed to master at https://github.com/mozilla/bedrock https://github.com/mozilla/bedrock/commit/b1fadc0eca7958c23fe51a16090094aee2989871 Fix Bug 920212 - Redirect /firefox/fx/ to /firefox/new/ https://github.com/mozilla/bedrock/commit/fb845fc7cdf32080f8267d95d2146541abcd0453 Merge pull request #1940 from kyoshino/bug-920212-firefox-fx-redirect Fix Bug 920212 - Redirect /firefox/fx/ to /firefox/new/
fixed on stage https://www.allizom.org/en-US/firefox/new/ curl -IL http://www.allizom.org/firefox/fx HTTP/1.1 301 Moved Permanently Content-Type: text/html Date: Tue, 29 Apr 2014 13:23:30 GMT Location: https://www.allizom.org/firefox/fx Connection: Keep-Alive Content-Length: 0 HTTP/1.1 301 Moved Permanently Server: Apache X-Backend-Server: bedrock1.stage.webapp.phx1.mozilla.com Vary: Accept-Encoding Content-Type: text/html; charset=iso-8859-1 Date: Tue, 29 Apr 2014 13:23:30 GMT Location: https://www.allizom.org/firefox/new/ Transfer-Encoding: chunked Connection: Keep-Alive X-Cache-Info: caching HTTP/1.1 301 Moved Permanently Server: Apache X-Backend-Server: bedrock1.stage.webapp.phx1.mozilla.com Vary: User-Agent,Accept-Language, Accept-Encoding Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0, private Content-Type: text/html; charset=UTF-8 Date: Tue, 29 Apr 2014 13:23:30 GMT Location: https://www.allizom.org/en-US/firefox/new/ Pragma: no-cache Transfer-Encoding: chunked Connection: Keep-Alive X-Robots-Tag: noodp X-Cache-Info: not cacheable; response specified "Cache-Control: no-store" HTTP/1.1 200 OK Server: Apache X-Backend-Server: bedrock1.stage.webapp.phx1.mozilla.com Vary: Accept-Encoding Cache-Control: max-age=600 Content-Type: text/html; charset=utf-8 Date: Tue, 29 Apr 2014 13:23:30 GMT Expires: Tue, 29 Apr 2014 13:33:30 GMT Transfer-Encoding: chunked X-Robots-Tag: noodp Connection: Keep-Alive X-Frame-Options: DENY X-Cache-Info: caching
You need to log in before you can comment on or make changes to this bug.