Making Site Architecture Search-Friendly: Lessons From whitehouse.gov

by Vanessa Fox | comments: 11

Guest blogger Vanessa Fox is co-chair of the new O'Reilly conference Found: Search Acquisition and Architecture. Find more from Vanessa at ninebyblue.com and janeandrobot.com. Vanessa is also entrepreneur in residence at Ignition Partners, and Features Editor at Search Engine Land.

Yesterday, as President-elect Obama became president Obama, we geeky types filled the web with chatter about change. That change of change.gov becoming whitehouse.gov, that is. The new whitehouse.gov robots.txt file opens everything up to search engines while the previous one had 2400 lines! The site has a blog! The fonts are Mac-friendly! That Obama administration sure is online savvy.

Or is it?

An amazing amount of customer acquisition can come from search (a 2007 Jupiter research study found that 92% of online Americans search monthly and over half search daily). Whitehouse.gov likely doesn't need the kind of visibility that most sites need in search, but when people search for information about today's issues, such as the economy, the Obama administration surely wants the whitehouse.gov pages that explain their position to show up.

The site has a blog, which is awesome, but the title tag, the most important tag on the page, has only the text "blog". Nothing else. Which might help the page rank well for people doing a search for blog, but that's probably not what they're going for. This doesn't just hurt them in search of course. It's also what shows up in the browser tab and bookmarks.

The site runs on IIS 6.0. Does the site developer know about tricky configuration that makes the redirects search engine-friendly?

Search engines are text-based, so they can't read text hidden in images. Some whitehouse.gov pages get around this issue well, by making the text look image-like, but leaving it as text, such as below.

However, other pages have text in images and don't use ALT text to describe them. (This, of course, is an accessibility issue as well, as it keeps screen readers from being able to access the text in the images.) An example of this is the home page, which may be part of why whitehouse.gov doesn't show up on the first page in a search for President Obama.

There are all kinds of technical issues, big and small, that impact whether your site can be found in search results for what you want to be found for. (whitehouse.gov using underscores rather than dashes in URLs, the meta descriptions are the same on every page...) Probably the biggest issue in this case is the lack of 301 redirects between the old site and the new site. When you change domains and move content to the new domain, you don't want to have to rebuild the audience and links all over again. (Not that Obama or whitehouse.gov will have a problem with attracting and audience, but we all can't be president!) When you use a 301 redirect, both visitors and search engines know to replace the old page with the new one.

In the case of change.gov, it's unclear if they intend to maintain the old site. The home page asks people to join them at whitehouse.gov, but all the old pages still exist (even the old home page at http://change.gov/content/home).

And in many cases, the same content exists at both change.gov and whitehouse.org (see, for instance, http://change.gov/agenda/iraq_agenda/ and http://www.whitehouse.gov/agenda/iraq/).

As Matt Cutts, Googler extraordinaire pointed out, give them a few days to relax before worrying so much about SEO. And I certainly think the site is an excellent step towards better communication between the president and the American people. But not everyone has the luxury of having one of the most well-known names and sites in the world, so the technical details are more important for the rest of us.

If you want to know more about technical issues that can keep your site from being found in search and tips for making sure that you don't lose visibility in a site move, join us for the O'Reilly Found conference June 9-11 in Burlingame. And if you're in Mountain View tomorrow night (Thursday, January 22nd), stop by Ooyala from 6pm to 9pm for our webdev/seo meetup, and get all your search questions answered. Hope to see you there! (Macon Phillips and the whitehouse.gov webmasters are welcome, but my guess is that they're a little busy.)

change.gov Becomes whitehouse.gov

by Tim O'Reilly | @timoreilly | comments: 31

In all the excitement of the inauguration today, I wanted to call out one amazing success story. Today, change.gov became WhiteHouse.gov. For those of us in tech, this is an amazing affirmation. Not only did the Web 2.0 principles of user-engagement, viral outreach, rapid development, and real-time intelligence help Obama to win the presidency, he's bringing the same principles and the same team to manage his outreach during his time in office.

This is an amazing moment for anyone involved with Web 2.0. There's a long road ahead, but it's clear that many of the lessons that were learned first on the consumer internet are now being applied to much harder, more serious problems.

Congratulations also to the team at Blue State Digital, who built both sites (along, no doubt, with many people on the transition team.) (BTW, for more information, see the Radar interview with Blue State co-founder and CTO Jascha Franklin-Hodge.) Big Oops. Don't know why I said this, as Jascha explicitly told me last month that they hadn't worked on the site. He confirmed this just now in email, saying " We've long said that our focus as a business is not going to be government work, but we expect the incoming White House New Media team to continue the tradition of innovation that marked the campaign and the transition." Brain fart. Thanks to commenter Arnie, who reminded me of this fact.

One of the things that excites me the most is the way that the new administration is reaching out to small companies rather than to the normal behemoths who bid on government contracts. Among other things, in an environment where we all need to do more with less, it's fabulous to see how the latest web technology can be deployed by small teams. I think that there will be many opportunities in the coming year for technologists to make a difference in helping our new administration achieve its ambitious goals.

My favorite bit from today's announcement on WhiteHouse.gov:

President Obama started his career as a community organizer on the South Side of Chicago, where he saw firsthand what people can do when they come together for a common cause. Citizen participation will be a priority for the Administration, and the internet will play an important role in that. One significant addition to WhiteHouse.gov reflects a campaign promise from the President: we will publish all non-emergency legislation to the website for five days, and allow the public to review and comment before the President signs it.

There are going to be some real challenges for the administration in digesting and responding to those comments. But what a change!