Google Promotes Google Chrome On Bing

By | March 28, 2012

Google Promotes Google Chrome On BingIt’s no secret that Google has been aggressively pushing its Google Chrome web browser across a variety of its services and partner’s web sites.

Now, Neowin reports that the search giant has decided to spice the things up and advertise on Microsoft’s search engine as well.

Once user types phrases to download different web browsers, such as, “get firefox”, the following ad will appear:

Google Promotes Google Chrome On Bing

While it’s nothing spectacular, once you combine all the advertising campaigns, one can only wonder how many millions of dollars Google is actually putting into the Google Chrome promotion, but hey, at least its working.

About (Author Profile)

Vygantas is a former web designer whose projects are used by companies such as AMD, NVIDIA and departed Westood Studios. Being passionate about software, Vygantas began his journalism career back in 2007 when he founded Having said that, he is also an adrenaline junkie who enjoys good books, fitness activities and Forex trading.

Comments (23)

Trackback URL | Comments RSS Feed

  1. Shane Bundy says:

    Who said it was working? For as long as it says “Google” on it then of course other people will download it.

    I’m not saying Chrome is bad as I use Chromium myself and it’s quite the pioneer of WebKit. Maxthon is still my default for those who are worried. :-)

  2. apád anyád says:

    No wonder chrome is so widespread, they actually shove it up to your a**. Two times, just to make it sure.

  3. Guest says:

    Fuck Chrome

  4. Gokle Krome says:

    Well, it’s (always!) nice to know where to get your… half baked browser :-)

  5. OccupyChrome says:

    This Chrome madness has to stop. People complained IE had too much market share and with that came the “best viewed in IE” BS. Soon you will be able to replace IE with Chrome in that line.

    On the mobile end, it’s even worse, WebKit dominates the market in such a way that one of the W3C guys called for it to stop; other browser vendors are gonna implement -webkit flags, which is so not good for the Web.

    Google says it supports openness and all, but that’s only if it fits into its schedule. Chrome will have 40% soon (I know StatCounter and other sources aren’t that reliable, but you get the point when looking at their charts). The higher its market share, the more broken the web will be. The only competitor that can rival it is Firefox, but it has to have a freaking process-per-tab model (which they’ve been attempting for over 3 years now), a better UI (which will come with “Australis” or w/e they’re calling it) and maybe some other stuff I forgot but definitely those 2, since those are the things fanboys shout when they move people to Chrome; however, the pace at which Mozilla is almost doing nothing could end up being too little, too late. They’re sitting on this huge pile of cash and are implementing very little things. MAKE IT HAPPEN, MOZILLA.

    Seriously people, you know this will heavily impact the way the Web will evolve (screw web apps, especially with more and more of them becoming Chrome-only) Get everyone to switch to Firefox or Opera or Safari, or even freaking IE (v9+ though). And don’t tell me to just have Chrome for “in case if” scenarios, 1 browser should suffice. Even with the cross-platform availability it has, I will not install it.

    It comes with Flash (which Google is bundling to keep it alive since they need ads in YouTube videos, which is only possible through h264), has no 64-bit builds, I could go on forever, but this post is getting quite long already.

    The whole argument of “it’s so much faster and more stable” is OUTDATED. Other browsers are as fast (0.1ms is NOT noticeable for the average user, and it’s mostly those people who are switching to it – for no reason!). And how many times does your browser really “crash”? (Doesn’t take away from the fact that Mozilla has to implement this though).

    I’mma end my rage post now,

    Happy browser switching! :)

    • Tiago Sá says:

       Well, if you use Firefox 18 hours a day, that’s…

      lemme do the math…

      once a month.

      • OccupyChrome says:

        WTF is that supposed to mean??

        • Rafael says:

          “OccupyChrome” hahahaha
          It’s supposed to mean that it cashes so much that he can’t stand it / don’t keep it open enough I guess.

          I like your post but it has a big fail: you tell us to use Safari which is also WebKit, you don’t consider Mozilla introduces the same problems with -gecko- and that it even is implementing SPDY.

          • OccupyChrome says:

            Ok lol, anyways;

            I don’t hate WebKit, I hate what Google’s doing with it (there are now more Google devs working on it than Apple devs fyi) and how they are aggressively pushing out these new de facto standards for modern Web technologies. Safari implements a lot of that, true, but Chrome’s WebKit is actually different from Safari’s, and what we’re seeing now is that some websites work in Chrome but not Safari – this will only get worse.

            It’s not bad if a browser vendor implements something from a competitor, it’s only bad when they are almost forced to do so, without any consent or discussion by W3C – check out that 1 blog post I mentioned btw. (it’s worse on the mobile end, but the desktop will follow with this Chromization)

            I don’t see why implementing SPDY is a bad thing, that’s just a separate project by Google (which they have submitted to the IETF). In the end, the new HTTP standard will include some SPDY stuff and probably also some of the stuff Microsoft recently announced.

            My biggest frustration is how Google at first released a seemingly amazing browser, and then tries to turn it into this ecosystem with ChromeOS – which BREAKS the Web!

          • Rafael says:

            Safari and  Mobile Safari are full of -webkit- too…

            I don’t get how you contradict yourself:
            Of course it’s bad if a browser vendor implements a Web technology from another! The technology wasn’t discussed and approved in W3C. They can’t implement it.
            If it’s implemented in Chrome and Firefox and they become the leading browsers, and then the Websites start to be only available for them, wouldn’t that force the others to implement too?
            This isn’t fair and it’s one of the reasons W3C and other organizations exist.

          • OccupyChrome says:

            I first clicked Like instead of Reply lol, I was like “why isn’t the reply thingie coming up?” :D

            Anyways.The mobile end is terrible yeah, the desktop not so much… yet! Atm, it’s WebKit dominating, but later on, it’ll be Chrome’s WebKit, or maybe I don’t get your first line :SThat’s what I said?! You just worded it differently, see: “It’s not bad if a browser vendor implements something from a competitor, it’s only bad when they are almost forced to do so, without any consent or discussion by W3C”Idk if your next paragraph is about SPDY or just continuing the previous one. Either way, like I said before, if one technology proves to be better than another, it’s time to adopt it – after it has gone through workgroups like W3C and IETF of course.

            The problem with WebKit atm is that it’s getting all this EXPERIMENTAL stuff that’s being aggressively pushed and therefore on its way to becoming the de facto standard.

          • Rafael says:

            You contradict yourself because Mozilla (Gecko) is also getting SPDY without any organization approval and yet you’d recommend Firefox.
            And you recommended switching to Safari when it also have vendor prefixes.

            I just commented to say that.

          • OccupyChrome says:

            It’s pretty obvious that SPDY will make it into the new standard, so what Mozilla’s doing right now (implementing SPDY support so that people can see how their website behaves in Firefox) isn’t a bad thing.

            Again, WebKit in Chrome will become more and more different from the one in Safari (which has the defaultish WebKit build)

          • Rafael says:

            Never mind, I don’t have time to keep repeating what I said (SPDY isn’t a standard, and if a standard is to be implemented it must be in an advanced stage on the spec, not before being submitted).
            You are simply being impartial against Google Chrome.

          • OccupyChrome says:

            Nvm yeah, we’re misunderstandingeach other

    • Chrome doesn't work says:

      Chrome crashes more for me than Internet Explorer, especially since Chrome is getting more bloated day by day and gives me constant BSOD

  6. apád anyád says:

    I just remembered an article, written 2-3 months ago. The one who wrote it, uses FF both on his computer at home and at his workplace. One day, he had to install chrome for some reason on his workplace PC. During installation, he let Chrome migrate passwords, bookmarks and other things from FF, thinking it will import the ones that were related to his job, making some things easier. Chrome migrated all the stuff from his PC at home. From the PC which was turned off, and of course, he never allowed Google to access or store his browser settings in any way.