From the category archives:

Google/SEO

[Just as a reminder: everything below is my personal opinion. I haven't sent it to anyone else at Google for a review, etc.]

Valleywag used a recent podcast I did as material for two points in Six Delusions of Google’s Arrogant Leaders. The two assertions that used my comments as material were “Google’s wealth means Google ‘gets it’” and “Google must sacrifice user privacy to grow.”

Valleywag has either misinterpreted what I said, or I didn’t express myself clearly, because I don’t believe either of those claims. I’ll try to explain the intent of what I said, in case I wasn’t clear during the podcast. I’ll address the latter claim first (“Google must sacrifice user privacy to grow”), because I certainly don’t believe that “Google must sacrifice user privacy to grow.” I think Google benefits the most when users understand what Google is doing and why; I also think that user trust in Google (and by extension our privacy policies) is paramount to our success.

A good example is our Google Ad Preferences page. As one blog concluded a couple days ago: “Google’s Ad Preference Manager, with its persistent opt-out plug-in, offers precisely the kind of robust opt-out that privacy advocates have always demanded.” And it’s not that we’re shy about talking about privacy; Googlers Alma Whitten and Nicole Wong recently talked privacy for an Ars Technica article that came out earlier this week. It’s a long article, but an example useful fact is that if X is the number of people who visit the Ad Preferences page and opt out, 10X people don’t opt out and 4X people actually edit their categories to improve the targeting relevance of the ads they see. Let me say that again: four times as many people change their settings to make their ads *more* relevant than opt out of interest-based targeting. I think the Ad Preferences page is a good example where users get more transparency and control regarding their privacy.

Another example where Google helps your privacy (rather than sacrificing it) is the Google Dashboard. This is a single site that gives you an overview of what information Google has from various services, and allows you to edit and to manage settings. This is another example where Google is trying to give more information to users, not less. I could point out lots of examples where we try to debunk privacy misconceptions. Where we actively fight for our users’ privacy. Or where we talk about privacy and engage in debates about user privacy. And of course there’s Google’s full privacy center (with videos!) at http://www.google.com/privacy.html . Suffice it to say, I don’t believe that Google “must sacrifice user privacy to grow.”

Okay, what about the other claim that Valleywag used me for: “Google’s wealth means Google ‘gets it’”? Ryan Tate wrote “It’s a truly bizarre moment, in which Cutts defends some horrendous management decisions based on Wall Street trades.” I don’t agree with that either, so let me try to clarify. Eric Schmidt joined the company in 2001. The first time I got to meet Eric was at the weekly TGIF meeting where he was introduced to the wider company. He answered questions for an hour, and I thought his answers were spot on. He was one of the original authors of lex, a well-known Unix utility that I had used in the past, so I knew that he was also a solid engineer and technologist. Schmidt also had experience at large companies (Sun and Novell).

All in all, I was very happy and impressed that Eric was joining Google. When I went home that day, my wife asked what had happened at work. And I replied with something like “I think the value of our stock options just went up a lot.” What I meant by that was that I thought Google had recruited the perfect person to lead the company from start-up to the next level. I still believe that. Eric has been a truly great CEO–and I’m not just saying that because for the last several years he has worked for $1 a year. :) Maybe I didn’t tell the anecdote well or clearly, but my intent was to explain that I think Eric Schmidt has been a great CEO right from the beginning of this decade, not to defend any decisions “based on Wall Street trades.”

If you want to listen to the full podcast, it’s available, but I hope this post helps to clarify.

{ 66 comments }

In a previous post I covered how to link to a specific timestamp in a YouTube video. The short version looks like this:

http://www.youtube.com/watch?v=PjDw3azfZWI#t=31m08s

The “#t=31m08s” takes you to 31 minutes and 8 seconds in a video. I just found out that you can also start embedded videos at a certain timestamp.

To do it on an embedded video, use the “start” parameter. Note that start takes seconds as a parameter, not minutes and seconds. For example, to start an embedded video 31 minutes and 8 seconds into a video, 31*60+8 = 1868 seconds, so you would use this code:

<object width="640" height="385"><param name="movie" value="http://www.youtube.com/v/PjDw3azfZWI&hl=en_US&start=1868"></param><param name="allowscriptaccess" value="always"></param><embed src="http://www.youtube.com/v/PjDw3azfZWI&hl=en_US&start=1868" type="application/x-shockwave-flash" allowscriptaccess="always" width="640" height="385"></embed></object>

and it would look like this:

That’s all there is to it. :)

{ 42 comments }

Google has been working on some new algorithms and tools to tackle linkspam and we’d like to ask for linkspam reports from you. If you’d like to tell us about web sites that appear to be using spammy links (e.g. paid links that pass PageRank, blog spammers, guestbook spammers, etc.), here’s how to send us more info. Go to

https://www.google.com/webmasters/tools/spamreport

and tell us about the site that appears to be employing link spam. Be sure to include the word “linkspam” (all one word, all lower-case) in the textarea (the last field in the form).

If that’s too hard to remember, you can also use the shortcut

http://goo.gl/linkspam

which will pre-populate the text area field to say “linkspam” in it. Note: to use these forms, you must sign in with a Google account. We’re moving away from using the anonymous spam report form.

Thanks in advance for any data you’d like to send our way!

{ 171 comments }

My speaking plans for 2010

February 17, 2010

in Google/SEO

Last year I tried to limit my travel but still ended up making about ten (!) trips in 2009. This year I’ve resolved to travel less for work. Right now, here’s my current speaking/travel plans for 2010:

March 2-4, 2010: SMX West, Santa Clara, CA. I’m doing a “Ask the Search Engines” panel.

May 19-20, 2010: Google I/O conference in San Francisco. I’m doing a site review session.

May 21-30, 2010: I’ll be doing a trip to Europe. Right now I don’t have any SEO-related events planned though.

June 8-9, 2010: SMX Advanced in Seattle

June 25-27, 2010: I’ll be at Foo Camp.

August, 2010: Sometime in August I’m going to try to climb Mt. Kilimanjaro.

November 8-11, 2010: PubCon in Vegas

I was gone last week (February 9-13) for the TED conference, but that was attending, not speaking.

{ 64 comments }

Back in December, I happened to click on a Greasemonkey script in Chrome and was shocked that it just worked. At the time, I wrote a note within Google that said

Whoa. I just clicked on a Greasemonkey script in the latest dev version of Chrome (4.0.266.0 on Linux). Chrome offered to install the GM script, so I said okay. The script ran perfectly in Chrome with no changes at all! I don’t know how many Greasemonkey scripts will run in Chrome unchanged, but at least some will.

Last week brought that news as an official announcement. My guess is that scripts that don’t use specific Greasemonkey APIs should be fine.

(Side-note: I found a good post from November that claims that ~60% of Greasemonkey scripts don’t use any sort of special API calls at all. The top API calls appear to be GM_getValue and GM_setValue (16.5% of Greasemonkey scripts), plus GM_xmlhttpRequest (15.5% of Greasemonkey scripts). It’s unclear which of these functions might be worth supporting. Some could have security implications (GM_xmlhttpRequest). Others like the get/setValue functions could be done by using other ways to store data.)

So this is cool. There’s a good chance that your favorite Greasemonkey script might just work in Chrome. Personally, I recommend the dev channel version of Chrome. It gets all the cool features early, and it’s been very stable/fast for me.

{ 35 comments }