Thursday 21 February 2008

Clarifications on local - for news readers and publishers



Two weeks ago we launched a new feature that lets you create local sections on your personalized Google News page. After some feedback we've been getting, we wanted to clarify a couple of issues. We want to make sure that it's easy for you to use this feature, but we also want to ensure that publishers know how to best update the information about their sites.

First, I'll address the specific steps that you should take to use the local feature. In both our feedback and some of the press coverage on this feature, there was some confusion about how to actually create a local section. Specifically, a number of people tried to enter a zip code or a city/state combination in our main search bar and did not get the results they wanted. Currently, you must create a local section to get local results. We're working to make this more clear on the site and improve the functionality. In the meantime, here's the step-by-step process to create your own local section.

First, look for the local section on your front page and the local search bar, as you see here:




All you have to do is enter the information in this section and PRESTO! You've got yourself a local section. If you don't see this promotion, you can set up a local section via your personalized page settings. Just access this option using "Personalize this page" or "Edit this personalized page" (if you've already personalized). Once you've clicked on this you'll see a menu similar to this image (US edition only). Click on "Add a local section."



Once you've clicked on this local section link, you'll see a place to enter a zip code or city/state combination. Use the drop-down menu to choose the number of stories you'd like to see. Once you click "Add Section" you'll see this section on your personalized Google News page.



And that's it -- you should be up and running with local news from wherever you want it. We're still working to improve this new feature both with our results and the features on our site, so keep the feedback coming!

The other feedback we got came from a number of publishers asking us how they could make sure we get all the great local news they're producing and ensure they shown up in results for their readers. As we explained, most of the work takes place on our side as we read every article to understand what location the story is about. However, we also look to check that against the location of the publisher. If you're a publisher and want to make sure we have all the latest information about your site, please contact our support team. If you notice that we are not including all of your articles, please send us a list of your news sections. If you notice that we don't include location information for your source, let us know what your accurate location is. Finally, if you're not included in News at all, let us know and we'll review your site for inclusion.

We hope the local feature is a interesting and useful feature for you to get information about cities near you or of interest to you. We're always working to improve our product, and appreciate your feedback.

Friday 15 February 2008

DITL Volume 1: News' First Engineer



As one of the first engineers assigned to Google News, I'm excited to kick off the inaugural Day in the Life ("DITL") post. Over the next few months, we hope to bring you a unique window into the world of Google News by publishing more DITL posts from other people who work on News. Our team is diverse and passionate, and we hope that we can show that to you in this series of posts. I've worked on Google News for over three years, and have seen a lot of amazing innovations. So enjoy my description of a typical day here for me at Google....

9:30am: Get into work and check my email. At Google we have engineers from all over the world, so I often receive code reviews and/or questions from those working in India or China. I starred them in my email inbox so I'm reminded to get back to them later in the day.

10:00 - 11:00 am: Attend the News team weekly meeting. Our team's product manager sets a unique agenda every week. We normally use this meeting to do project presentations so the team can learn what each engineer is working on. Sometimes we review recently launched features and forecast upcoming launches. This is also where we sync up with our international offices.

11:30am: The Google News Frontend team meets so each team member can provide a status update on their project tasks and reveal any dependencies that might be holding up their progress.

12:00pm: Usually my office-mates Dan and Chris start to initiate lunch. They like to browse the menus of different cafes on campus and usually pick the one with the best dessert. Once a location is decided, we gather the rest of the team to join us.

12:10pm: We've arrived at Off the Grid cafe. After getting our food, we sit, eat, and chat about the future of online journalism and how we can make Google News better.

1:00pm: After lunch, I like to block off an hour to do code reviews. A code review is when someone else other than the author examines the code for correctness and readability. News has many remote engineers so many code reviews come from India or China. I try to complete these by the end of the day, so they do not have to wait another 24 hours to hear a response.

2:00: Attend a meeting with UX (User Experience) designers, our product manager, and other engineers to discuss design specifications for a new feature. We come up with use cases and list out pros and cons of various solutions. In the end, our goal is to build a feature that is useful.

3:13pm: I'm pager-holder for the week and the pager goes off. The pager goes off when something requires immediate attention since News is 24/7 and every minute counts. The team has built numerous useful monitoring tools and status pages which I use to debug the issue.

4:04pm: Our product manager comes into our office to check on the status of a feature release planned for this week. I inform him that all the pre-launch procedures are being followed and we should be on schedule for launch. He leaves with a big smile.

4:30pm: I get some coding time and work on the implementation for the feature launches I'm responsible for.

6:33pm: An engineer from other project drops by my office to ask questions about how to integrate their product into Google News. I share my experience with him from when we did similar integrations with Google Finance and Archive News Search.

7:00pm: I go grab dinner from No Name cafe and eat at my desk.

8:20pm: I finish replying to some emails before getting on the Google shuttle and head home.

9:30pm - 12am: I normally stay online during this time since this is when some international engineers are getting into work. I try to be available to answer questions using gChat. It is also a good time to get some work done before the new day starts.

Wednesday 6 February 2008

All News is Local



Something you already know about Google News is that we crawl thousands of sources from around the world. This means you get as many different perspectives on a story from many perspectives. A while back, we started thinking about how to bring this same diversity of sources to local news, so that "local" doesn't necessarily mean "limited".

Today we're releasing a new feature to find your local news by simply typing in a city name or zip code. While we’re not the first news site to aggregate local news, we’re doing it a bit differently -- we're able to create a local section for any city, state or country in the world and include thousands of sources. We’re not simply looking at the byline or the source, but instead we analyze every word in every story to understand what location the news is about and where the source is located.

You can see an example with the latest news from Duluth, Minnesota:




As always, results will be clustered with multiple sources on a story. The top stories for a given area will be at the top of your results. Our article rankings will also take into account a publication's location so we can promote all the local sources for each story.

This feature is still a bit of an experiment for us, which is why today it’s only available in English. But we hope to launch this in other languages and editions soon. Please let us know what you think!

Tuesday 5 February 2008

Following the polls on Super Tuesday



If you somehow escaped US electioneering up to this point, you probably won't today, Super Tuesday, when 24 states choose their candidates for the fall election. This will be the largest number of primaries going on at one time in the history of the U.S. electoral system.

Over the last few weeks and months, there has been a massive volume of news coverage, statistics and polls -- and there will be even more today. Our mission is to help organize all of it for you, so you can find what you're looking for. There are a number of ways Google can help you keep track of all the candidates and issues -- from Maps with the latest results, to YouTube videos from voters across the country. You can read all about these initiatives on the Google Blog.

Of course, we want to do our part as well. In addition to all the latest stories from thousands of sources in our new Elections section, we've also put together a gadget that tracks the progress of the candidates in each of the 24 states. Here's an example of how it might look; please note these are not actual results!


In addition to providing up to date information about the results on all the candidates as the polls close, you'll also be able to view this information on Google Maps. You can see the results across the United States, within a particular region, and even as specific as a particular county.

So check it out and let us know what you think.