recommended reading

Agencies should look at cost and usability before cutting websites, CIO says

Government officials charged with rationalizing their agencies' Web presence should consider potential cost savings from cutting or consolidating seldom visited websites and aim for a sleeker online footprint that better serves the public, according to guidance released Tuesday.

Federal agencies have historically set a low bar for what warrants a new website, leading the government's online universe to balloon to nearly 2,000 domains and more than 20,000 individual sites.

A Web domain is essentially a packet of individual sites with similar names and architecture. The Internet is currently broken up into a handful of top-level domains, including dot-com, dot-gov and dot-edu. The State Department's main website,, for example, would be considered a second-level domain and the agency's various divisions would be lower level domains, each housing numerous websites. The distinction between a website and a lower-level domain gets murky after the first few levels.

An inventory of all government websites broken out by agency was due out this week on the government's internal MAX message board. A General Services Administration spokesman was unable to confirm whether the list had been posted by 4 p.m. Tuesday.

The government's website cutting initiative aims to shutter some rarely visited legacy sites, such as, and to fold other sites into larger Web domains, where they'll share a common architecture, content management systems and security features.

The initiative is part of two broader White House campaigns, one aimed at cutting waste throughout government and the other attempting to improve its online customer service.

Limiting agencies to one or a few major Web domains will cut down on upkeep and security costs, according to Tuesday's guidance from federal Chief Information Officer Steven VanRoekel's office. The Energy Department, for instance, estimates it will save about $150,000 for each potential new site that it builds within its main site.

The consolidation also will improve customer service, the CIO's office said, by putting more vital information where citizens will look for it first and by raising that information's ranking in search results.

"Setting up a new domain may actually hinder the 'findability' of separate content because it can take weeks or months to build up status on search engines," the guidance noted.

As agencies debate which sites to cut and which to consolidate, update or leave alone, the guidance recommends looking at Web metrics to determine how many visitors a site is getting, whether those visitors are finding what they're looking for -- gauged by how long they remain on the site -- and whether they're successfully completing tasks the site includes, such as registering to receive more information or filling out a survey.

Tuesday's guidance also directs agencies to review the number of redirects they log -- Web addresses that don't match an existing website but automatically send a user to a site that does exist. Redirects are typically old names for a new site, common misspellings of a site, or common variations on what a Web surfer might guess an agency's website is named.

GSA recently deleted redirects that refer fewer than 300 users to actual government Web domains annually, the guidance said.

In general, agencies should retain redirects that send a significant number of people to a particular site, such as, a legacy name for that sends "thousands of users annually" to its successor, the guidance said.

In some cases, though, "multiple redirect domains may dilute the primary brand you're trying to promote and marketing multiple domains can sometimes confuse your message," the guidance said.

A federal dot-gov task force is developing guidance for how interagency projects should be dealt with online.

"In most cases, a primary agency should be designated to host interagency content . . . and should use clear language on the site to indicate that it is a partnership among multiple agencies," the guidance said.

Agencies that manage an interagency domain name should be "the definitive, authoritative source for that topic across government," the guidance said, and "must have the capacity to broadly cover that entire topic."

Tuesday's guidance also directs agencies to ensure they archive Web content before deleting it to comply with rules for executive branch material established by the National Archives.

Threatwatch Alert

Thousands of cyber attacks occur each day

See the latest threats


Close [ x ] More from Nextgov

Thank you for subscribing to newsletters from
We think these reports might interest you:

  • It’s Time for the Federal Government to Embrace Wireless and Mobility

    The United States has turned a corner on the adoption of mobile phones, tablets and other smart devices, outpacing traditional desktop and laptop sales by a wide margin. This issue brief discusses the state of wireless and mobility in federal government and outlines why now is the time to embrace these technologies in government.

  • Featured Content from RSA Conference: Dissed by NIST

    Learn more about the latest draft of the U.S. National Institute of Standards and Technology guidance document on authentication and lifecycle management.

  • A New Security Architecture for Federal Networks

    Federal government networks are under constant attack, and the number of those attacks is increasing. This issue brief discusses today's threats and a new model for the future.

  • Going Agile:Revolutionizing Federal Digital Services Delivery

    Here’s one indication that times have changed: Harriet Tubman is going to be the next face of the twenty dollar bill. Another sign of change? The way in which the federal government arrived at that decision.

  • Software-Defined Networking

    So many demands are being placed on federal information technology networks, which must handle vast amounts of data, accommodate voice and video, and cope with a multitude of highly connected devices while keeping government information secure from cyber threats. This issue brief discusses the state of SDN in the federal government and the path forward.

  • The New IP: Moving Government Agencies Toward the Network of The Future

    Federal IT managers are looking to modernize legacy network infrastructures that are taxed by growing demands from mobile devices, video, vast amounts of data, and more. This issue brief discusses the federal government network landscape, as well as market, financial force drivers for network modernization.


When you download a report, your information may be shared with the underwriters of that document.