Checklist for a Successful Website Redesign
We often receive questions when an agency conducts a major website upgrade, changes content management systems, or both. We created this checklist to help ensure your redesign is successful. The stages are:
Ready…
1. Let the Search.gov team know you are launching a new site
Set…
3. Prepare xml sitemaps and SEO elements
5. Prepare color scheme updates and new logo to add to Admin Center
6. Prepare updates to your other search features
Go!
7. Flip the new website live, let us know
8. Implement the changes to the search site
Victory lap
10. Alert Google and Bing that your website has been refreshed
Website relaunch flow chart detailed description
Ready…
1. Let the Search.gov team know you are launching a new site
Who: You, the agency web team
What: Send us an email, give us a call, either way, please let us know that you’re working on a redesign of your website. If we know ahead of time, we can help you get your new search experience prepped and in good shape on the day of the relaunch. When you reach out to us, include the planned launch date.
It’s important to plan ahead, because if there are any changes to your site structure, your search results will break, which will lead to frustration for the public as they try to use your new site. This is true for our service, and out on Google and Bing. To avoid an avalanche of 404 not found
errors from your search results, wherever possible, use 301 redirects to send visitors from the old pages to the appropriate new pages. For more on 301 redirects, read tips from Bing and Google. Notify other websites that link to you of the changes.
2. Develop a reindexing plan
Who: Search.gov team, in consultation with you, the agency web team
What: We will ask you about your search needs for the new site, including what domains you need to include, how you can generate an xml sitemap, and what SEO supports you’re putting in place in your new templates, like metadata and other structured elements. Read more about our indexing process here.
As part of this discussion, we’ll make some recommendations and likely agree on some action items for your team to consider implementing prior to your launch. If there are any major SEO warning signs in your setup, we’ll let you know.
We’ll also ask you about the timeline for launch, so that we can reserve a time to coordinate Step 8 with you.
Set…
3. Prepare xml sitemaps and SEO elements
Who: You, the agency web team
What: Action items that usually come out of the planning discussions include
- Ensure that each domain and subdomain you want to be searchable launches with an xml sitemap.
- Add metadata blocks to the
<head>
of your page templates, and Semantic Markup to the<body>
.- Sometimes these pieces are in place, but need to be modified or moved.
- Talk with other web teams to ask them to do the above items on their sites, so you can leverage them when your site searches their site’s content.
4. Add a Search Page Alert in the Admin Center
Who: You, the agency web team
What: Use our Search Page Alert feature to display a “pardon our dust” type message on your results page. For example:
We are launching a new example.gov. If your search does not return the content you expected, please check back soon for updated results.
- Set the status of the alert to
Inactive
and wait for the relaunch.
5. Prepare color scheme updates and new logo to add to Admin Center
Who: You, the agency web team
What: Gather your new logo and color palette, if needed. Many sites find it helpful to mock up their redesigned results page in a non-production search site — you can either clone your existing site or just use the Add Site button to create a totally new one.
Don’t implement these changes on your production site ahead of the actual relaunch (that comes in Step 8, below).
6. Prepare updates to your other search features
Who: You, the agency web team
What: When your URL structure changes, this will affect several of our search features. You’ll want to get your updates ready to go, but don’t implement them ahead of the relaunch, or people will end up in the wrong places:
- Domains: make sure your Domains list includes the domains and subdomains that you want included as the default content to search.
- Collections: make sure your Collections are searching for the right content in the new location.
- Best Bets: make sure your Best Bet URLs are correct for the content’s new location.
- Routed Queries: update the target of your Routed Queries, so searchers will end up on the correct page.
- RSS feeds should be removed, and re-added from their new locations.
Go!
7. Flip the new website live, and let us know
Who: You, the agency web team
What: When your new website is publicly available, reach out to us by email or phone. This will be our signal to begin our part of Step 8.
8. Implement the changes to the search site
At this point, the work splits into two parallel tracks, with your team and ours working on related items at the same time.
Who: You, the agency web team
What: Add the updates you prepared in Steps 4, 5, and 6 to the Admin Center for your production search site:
- Set your Search Page Alert to
Active
. - Update your colors and logo.
- Update your Domains, Collections, Best Bets, Routed Queries, and RSS Feeds as necessary.
Who: The Search.gov team
What: We complete several backend tasks
- Switch your production search site to use the new index, which will begin empty for your domain(s).
- Tell our indexer to begin working on your domain(s).
- The time it takes to get your content indexed depends on the number of items you have, and whether you have a crawl delay declared in your
/robots.txt
file. Generally speaking, a few hundred items should be done in an hour or two, a few thousand items should be done in several hours, etc.
- The time it takes to get your content indexed depends on the number of items you have, and whether you have a crawl delay declared in your
9. Results begin to show
What: Our indexer will first read your sitemap, collect the urls, and then work through them in the order they were collected. We will work at the crawl delay set in your /robots.txt
file, or 1 request per second, whichever is slower. This delay is the time after we’ve rendered a page, before requesting the next page to render.
Victory lap
10. Alert Google and Bing that your website has been refreshed.
Who: You, the agency web team
What: Register for the commercial search engines’ webmaster tools, if you haven’t already done so.
- Bing Webmaster Tools
- Google Search Console.
- Resources:
How to move your content to a new location, Google Webmaster Central Blog.
- In Bing, submit your new Sitemaps together with the Content Removal tool.
If you’ve undergone a redesign, followed these steps, and your site search results are not what you’d expect, send us an email.