Google listens… if you shout loudly enough

Yesterday evening I wrote about the bizarre disappearance from Google News of my news site, Berkeleyside. What happens next is either an illustration of the power of digital democracy or an example of the value of friends with fantastic megaphones.

Shortly after my post went up, a number of friends tweeted about it. Dave Winer and Felix Salmon were first off the mark. Felix’s rare use of an exclamation mark (“Berkeleyside axed from Google News!”) seems to have provoked some of his regular followers to retweet, including The New York Times’ David Carr, with over 300,000 followers.  My co-founders on Berkeleyside were doing their own tweeting and that reached plenty of others, from Exceptional Women in Publishing to the Knight Digital Media Center’s hyperlocal maven Michele Mclellan. Online media beacon Dan Gillmor added his voice and this morning local media/tech writer extraordinaire Scott Rosenberg piled on with a direct plea: “If you’re a Googler reading this, pls help!” (I’ve never liked exclamation marks as much as in the last 24 hours.)

I was doing more behind the scenes as well. After I wrote my post last night I emailed Josh Benton, who edits the wonderful Nieman Journalism Lab site at Harvard. Benton had published an earlier item I wrote reflecting on AOL/Patch and local sites. He assigned someone to look into it with Google.

Early this morning I had an email from an engineer on the Google News team. He said he was also a Berkeleyside reader and that, off the record, I should know that the problem was a bug and the Google News team was working to resolve it. No ETA for a solution, but he was happy to help me with a Google News backchannel. I’d earlier posted on a Google support forum thread that I reckoned the problem was a screw-up, not a conspiracy. I’m glad I was right.

At about 3pm Pacific time today we started reappearing in the Google News index. Megan Garber wrote an article on Nieman Lab explaining the kerfuffle. (I wish I’d thought of the headline: “Bug, not snub!” Again with the exclamation mark.) Google’s Jeannie Hornung told Garber, “Google News experienced technical difficulties that may have prevented the indexing of recent articles from some news sources. We believe all issues have been resolved. We apologize to our users and the sites affected.”

Phew.

What lessons can anyone draw from this? First, for all the ascendance of Twitter I’m convinced that my fuller, more reasoned explanation of what happened here on Davos Newbies was crucial. If I had 300,000 followers on Twitter perhaps 140 characters would have provoked someone to action. With less Twitter clout I think the fact that I actually marshaled my arguments in a more discursive form was crucial.

Second, it sure is great to have friends who have bigger megaphones, particularly in the media and tech worlds. The Google support forums where I was posting yesterday were filled with howls from media site owners who had been delisted. No one from Google was replying, so a lot of the forum posts were either grand conspiracy theorists or despairing writers wondering what was going on. From my back channel I’m sure that the Google News team was aware of the bug and was working away. But the cascade of protests on our behalf and the swift resolution today strikes me as more than a coincidence.

Third, it sure is helpful to be producing a vital news source in the Bay Area, where we’re almost bound to have readers who work at Google (and just about any other tech giant you can think of). If we were somewhere else in the world, perhaps we could have gathered the same forces in support, but I think the direct connection to at least one Googler who looks to us for news helped.

One thought on “Google listens… if you shout loudly enough

  1. Scott Rosenberg

    Glad to hear it!

    Another lesson here, one that I was taught over and over during my Salon years is: Any time you have to wonder whether a problem is the result of somebody’s bad behavior or a software bug, assume it’s the software until proven otherwise.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *