A B2B website redesign checklist
Yes or no checks for a B2B website redesign, from the brief to the weeks after launch, with what a no usually means and what to fix first.
This checklist is for a team redesigning a B2B website, with the current site and the new one open beside it. Each line is a statement you can check and mark yes or no. The groups run in the order the work does: the brief, the inventory of the old site, the content, the address changes, testing, and launch.
Give every line an owner and a link to the evidence before you mark it yes. A preview link, a successful deployment and a working site on your own domain are three separate things, and the checks treat them separately. How to structure the pages themselves is covered in our guides to structuring a technical website and to landing pages.
1. Agree what the redesign must improve
A no here usually means the redesign has no test it can fail, so it will be judged on taste. Save the baseline first. It is the one item that cannot be done later, because a baseline taken after launch measures the new site.
2. Inventory the existing site
A no here usually means some old addresses will break at launch without anyone noticing. Start with the Search Console and analytics exports, which show the pages that get visits and links. Keep the inventory short enough to maintain: current URL, new URL, content status, owner and decision.
3. Write content buyers can evaluate
A no here usually means the pages were designed before the words existed. Put the real copy for one product page into the layout first, with its longest product name and its comparison table. A layout that works with placeholder text often fails on the first real case study.
4. Prepare the address changes
A no here usually means an old link will land on an error or an unrelated page. Test the map first by requesting each old URL on staging and reading the status and the page it lands on. Google’s guidance on site moves covers each of these steps, and its page on redirects explains why a permanent redirect tells Google the new address should replace the old one in results.
5. What we saw on our own site
When we rebuilt our own site, Search Console was still reporting old addresses as not found. We checked each against the live site and kept a written map of what each now does.
| Old address | Now | Why |
|---|---|---|
| /portfolio | A 301 to /work | The work index does the same job |
| /manifesto | A 301 to /about | The about page holds the same principles |
| Eight old project pages | A 301 each to the case study that replaced it | Each case study carries that work |
| Retired projects | Still a 404 | No current page has the same content |
Each redirect is listed one by one, with no catch-all rule, and keeps its query string. We tested 100 variants of the old addresses on the production server and kept them out of the sitemap. The same review found service pages that were live and linked but still marked noindex. After the release went live we checked every URL in the sitemap on the live site. That shows the site behaves as intended. It says nothing yet about search traffic, which needs a longer period of data.
6. Test the buying journey
A no on the enquiry checks comes before everything else, because a form that fails quietly loses the buyers the redesign was for. The access checks are preliminary; W3C’s Easy Checks describe the same first review and its limits. A no on the editing check means every correction after launch will need a developer, which is a running cost to raise now.
7. Release, verify and watch
A no here usually means nobody owns the launch, so name that person first. A working preview does not prove the domain points to that version, which is why the checks repeat on the live site. Search Console’s URL Inspection tool shows whether a page is indexed and which canonical Google chose. Google says rankings can move while a site settles, and nobody can promise that every one holds. Account for seasonality, campaigns and tracking changes before crediting or blaming the redesign.
Websites with us start from $15,000, and most of our builds, redesigns among them, take four to eight weeks. Approvals and the amount of content to carry over are what usually stretch one.
8. Questions
A B2B website redesign checklist should cover six stages: agreeing what the redesign must improve and saving a baseline, an inventory of every current URL, content buyers can evaluate, the redirect map, testing the enquiry journey, and the checks after launch. Each line should be something a named person can mark yes or no, with a link to the evidence.
List every URL that brings in visitors, from the sitemap, analytics, Search Console and server logs. Redirect each changed one permanently to its closest replacement, update internal links and canonicals, and submit the new sitemap. Google says rankings can fluctuate during a move and to keep redirects for at least a year. Nobody can promise every position holds.
Most of the websites we build take four to eight weeks, and a redesign usually sits in that range. What stretches a redesign is the content: how many pages are rewritten, how quickly they are approved and how much is carried over from the old site. The timeline is set before the project starts.
Our websites start from $15,000. That is our own published price. A redesign moves up from there with the number of page types, how much copy is written and how much content is carried over. Scope and price are agreed before work begins. Our B2B website cost guide covers what moves the price and how to compare quotes.
When the site is not the problem. If the pages explain the company well and too few people reach them, the work is search and content. If one page or one form is failing and you know which, fix that page. If the offer still changes from month to month, wait until it settles, or the new pages will be out of date at launch.
Written on by