MarketingConference CoverageA 12-Point Checklist for Your Next Website Redesign and Migration

A 12-Point Checklist for Your Next Website Redesign and Migration

Get it right, before the launch.

Redesigns are challenging, especially for an SEO team at a company that has not yet done a website migration with SEO properly integrated into every facet of the project. Doing it right is worth the investment and will reap massive rewards. To help guide you through the landmines, I offer a few tips based on the misses I’ve seen when auditing SEO programs and working on redesign projects. Redesigns are not easy; the level of effort for the SEO team is underestimated by both managers and the SEO team because they do not realize how ingrained in the process SEO needs to be.

Train the Project Team

Bringing in a firm to do SEO training before a redesign project is valuable because it brings SEO concepts to the forefront, and a good trainer knows how to get the team thinking about both SEO concepts and different approaches in the upcoming redesign project. Training doesn’t have to be a full day; adjust the scope to the size of the knowledge gaps.

Questions to ask yourself:

  • Does the team know everything they need to know for a successful launch in terms of SEO?
  • What does the team need to learn, and can in-house staff teach it or do you need to hire someone?

Redefine the Keyword Strategy

Overhaul (or create) your targeted keyword list before the redesign and site migration, so that the keyword strategies are consistent with the goals of the new site, and the new site has what is needed to rank high for primary keywords.


  • Will the types of audience change?
  • Will content change?
  • Will new content need to be added?
  • Will the information architecture change?

Contribute to the Wireframes

Invest the time with designers at the beginning of the design phase to ensure that pages are designed with SEO best practices in mind. Make sure that the designs presented to the project team are SEO approved so that no one gets married to a design that isn’t search engine-friendly.


  • Do the designs have functionality that generates special SEO requirements?
  • Is there any functionality at risk of not being seen by search engines?
  • Is there anything that SEO needs added to the design to make it optimal for SEO?
  • Is there enough body copy?
  • What notations or direction for developers should be added to the wireframes?

Make the New Information Architecture Keyword Driven (at Least a Little):

Work with the person or team defining the information architecture and taxonomy. Ensure that the content is semantically defined and aligned.


  • Can the information architecture and taxonomy be improved in a way that gives better keyword alignment?
  • Has internal linking changed? Is SEO “link juice” most strategically passed?

Write the SEO Requirements

Here’s one of the biggest mistakes I’ve seen when auditing in-house SEO: the SEO gives a few SEO requirements verbally in a meeting, then says “make it search engine-friendly.” The problem is that most people do not know what “search engine-friendly” means. To put it into perspective, the baseline SEO requirements that we send to project teams contain over 160 items.


  • Are you writing your own SEO requirements?
  • How thorough are they?
  • Are they working, or do you continue to have challenges on every project?

Ensure That the CMS Will Be Search Engine Friendly

Vet the platform and integration vendor thoroughly. Make sure that you understand all of the functionality and inherent SEO risks. Define specific SEO requirements for the CMS and talk with the vendor about them before you sign (many CMS systems are not search engine-friendly out of the box). In particular, ask about customizing and pattern-defining title tags, meta descriptions, and URLs.


  • What needs to happen in the CMS?
  • Which SEO requirements are addressed in the quote price versus what will be a custom build?
  • Which SEO requirements are not feasible with this platform?

Define Search Engine-Friendly URLs

Work with development to understand system URL needs, then suggest a proposed SEO-friendly version of the URL. Watch for parameters, tracking codes, and other common URL challenges.


  • What technical elements need to be in the URL?
  • Will tracking codes ever be in the URL (even with cookies turned off)?
  • What is the worst-case-scenario URL (the longest and most complex)?

Define a URL Migration Plan

Define the current information architecture and map against the redesigned site. Focus on strategically passing all page values throughout the new website, with emphasis on semantic alignments.


  • What are the URLs currently on the site and where would their value be best placed on the new site?

Conduct SEO Code Checks

Few SEOs are technical enough to conduct proper SEO code checks; as a result, they rarely think of checks, let alone execute them. You can fix many issues during the development phase if you add code checks to the project plan. If you do not have the skills to do this in house, it’s worth outsourcing (at the very least for the most important templates on the site).


  • Do we have the technical skills to do an SEO code check?
  • Have SEO code checks been added to the project plan?

Improve the 404 Page

There is a good chance that people will hit the 404 page from a search engine after a redesign, so make sure that it drives people into the site rather than to the back button. Some ideas are to link to main sections of the website; customize the content based on content contained in the original URL; and design the page in a way to gracefully display promotions such as free shipping that would encourage the user to take the extra time to find the right page.


  • What could go on our 404 page that would cause the user to continue looking on our site?
  • What are other sites doing that we can learn from (both positive and negative examples)?

QA Test the Site Before Launch, Thoroughly

Too many SEOs either do not QA test a website, or do a spot-check rather than a proper and systematic check. If a site takes months to code, a proper QA test will take several hours and maybe a couple of days. It’s worth investing the time to find and fix issues before the launch.


  • Are we doing QA testing systematically?
  • What needs to go into the QA testing checklist?
  • How can SEO get more than a few days before launch to test, so there is time to make technical changes?

Set up a Monitoring Plan

Before launch, put everything in place to monitor the migration’s progress from an SEO standpoint, looking for any signals that indicate an SEO problem to fix.


  • What needs to be set up before launch?
  • Who will monitor it?
  • Do they know what to look for, how to spot red flags in the data, and what actions to take?

Jessica Bowman will be giving a presentation, “SEO and Website Migrations: How to Have a Smooth Transition,” on Wednesday, March 21, at SES New York.

Related Articles

Vodafone's top three tips to improve your mobile marketing

Conference Coverage Vodafone's top three tips to improve your mobile marketing

2y Mike O'Brien
Comedy Central CMO: shareable or die

Conference Coverage Comedy Central CMO: shareable or die

2y Yuyu Chen
8 Good Reasons to Join Us at ClickZ Live San Francisco #CZLSF

Conference Coverage 8 Good Reasons to Join Us at ClickZ Live San Francisco #CZLSF

3y Tetyana Miroshnichenko
Flexibility Is Key for SEOs [#CZLNY]

Conference Coverage Flexibility Is Key for SEOs [#CZLNY]

3y Mike O'Brien
Top 7 Reasons You Need, Nay, You Must Be at ClickZ Live New York

Conference Coverage Top 7 Reasons You Need, Nay, You Must Be at ClickZ Live New York

3y Shivali Bhammer
Q&A: Tribune Publishing's Carolyn Shelby

Conference Coverage Q&A: Tribune Publishing's Carolyn Shelby

4y Mel Carson
Insights, Tricks, Mistakes, and Future Trends Digital Marketers Should Know [Video]

Conference Coverage Insights, Tricks, Mistakes, and Future Trends Digital Marketers Should Know [Video]

4y Yuyu Chen
#CLZNY: B2B Case Study on Tensions and Reality of E-Business Integration

Conference Coverage #CLZNY: B2B Case Study on Tensions and Reality of E-Business Integration

4y Greg Jarboe