dannysullivan

Joined 18 years ago

Karma
577
Submissions
189
Member since
Jun 7
Google's public liaison of Search, helping people better understand search & Google better hear public feedback: https://twitter.com/searchliaison
View on Hacker News

Recent submissions

Comment · 2 years ago
Comment · 3 years ago
I absolutely don't think it's a laughing matter. I made a joke in the interview with the reporter as a kind of icebreaker (which clearly didn't seem to go well).

But as I also explained after doing that, "I’m pretty sure, went into what I thought was a more serious and thoughtful discussion, at least from my perspective."

I don't think making a joke about something is the same as someone then thinking an entire matter isn't serious. But I can appreciate you disagree.

Comment · 3 years ago
It's because when I was interviewed, what I said was all speaking officially for Google. You can attribute anything there to the company directly.

My blog post -- I wrote that on my own. No one from the Google communications team reviewed it, approved it, vetted it and so on. That's what I was trying to explain.

That doesn't mean, of course, people won't think it somehow reflects on Google or what I do there. It no doubt will. But that's not quite the same thing as something being an official company statement.

Comment · 3 years ago
I know it was a long post I made. But yes, I (and we) recognize people want the results better. I covered this at the end (along with some other parts):

"That said, there’s room to improve. There always is. Search and content can move through cycles. You can have a rise in unhelpful content, and search systems evolve to deal with it. We’re in one of those cycles. I fully recognize people would like to see better search results on Google. I know how hard people within Google Search are working to do this. I’m fortunate to be a part of that. To the degree I can help — which includes better communicating, ensuring that I reflect the humbleness that we — and I feel — I’ll keep improving on myself."

Comment · 3 years ago
Comment · 3 years ago
I was on vacation when this came up, so playing some catch up. I work for Google Search. I've been very involved with the concerns raised about quoted searches last year, especially because they never stopped working. They do work.

We did make an update last year to better reflect where quoted content appears on a page in the snippets we show. We did this because sometimes it's hard to find the quoted material on the page itself, leading to the "quotes don't work" issues.

This post explains more about this: https://blog.google/products/search/how-were-improving-searc...

The post also explains things like how with punctuation, we'll ignore that -- which leads to the "example.com" type of issue you might be having. If you're quoting a domain name, we're likely seeing that as "name com" rather than a request to just search within the domain. If you want to just search within the domain, that's what site: is for such as [site:example.com whatever you want to search for]

Comment · 3 years ago
"They say that old content does actually affect a site in terms of it’s average ranking" -- We didn't say this. We said the exact opposite.
Comment · 3 years ago
Comment · 3 years ago
No. I don't code. I'm not an engineer. That doesn't mean I can't communicate how Google Search works. And our systems do not calculate how much "old" content is on a site to determine if it is "fresh" enough to rank better. The engineers I work with reading about all this today find it strange anyone thinks this.
Comment · 3 years ago
There is. Which is why I specifically talked only about writing for algorithmic systems. Machine learning systems are different, and not everyone fully understands how they work, only that they do and can be influenced.
Comment · 3 years ago
I actually work for our search quality team, and my job is to foster two-way communication between the search quality team and those outside Google. When issues come up outside Google, I try to explain what's happened to the best I can. I bring feedback into the search quality team and Google Search generally to help foster potential improvements we can make.
Comment · 3 years ago
No. But it's also complicated, as Matt did thinks beyond web spam. Matt worked within the search quality team, and he communicated a lot from search quality to the outside world about how Search works. After Matt left, someone else took over web spam. Meanwhile, I'd retired from journalism writing about search. Google approached me about starting what became a new role of "public liaison of search," which I've done for about six years now. I work within the search quality team, just as Matt did, and that type of two-way communication role he had, I do. In addition, we have an amazing Search Relations team that also works within search quality, and they focus specifically on providing guidance to site owners and creators (my remit is a bit broader than that, so I deal with more than just creator issues).
Comment · 3 years ago
thanks, Ernie!
Comment · 3 years ago
I'm the source. I officially work for Google. The account is verified by X. It's followed by the official Google account. It links to my personal account; my personal account links back to it. I'm quoted in the Gizmodo story that links to the tweet. I'm real! Though now perhaps I doubt my own existence....
Comment · 3 years ago
That Googler here. I do use Google! And yeah, I get sometimes people want older content and we show fresher content. We have systems designed to show fresher content when it seems warranted. You can imagine a lot of people searching about Maui today (sadly) aren't wanting old pages but fresh content about the destruction there.

Our ranking system with freshness is explained more here: https://developers.google.com/search/docs/appearance/ranking...

But we do show older content, as well. I find often when people are frustrated they get newer content, it's because of that crossover where there's something fresh happening related to the query.

If you haven't tried, consider our before: and after: commands. I hope we'll finally get these out of beta status soon, but they work now. You can do something like before:2023 and we wouldn't show pages from before 2023 (to the best we can determine dates). They're explained more here: https://twitter.com/searchliaison/status/1115706765088182272

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton