Here are a few things to keep in mind after a relaunch:

[hoxesi8100@]

Screencap of HubSpot’s Content Hub.

Image Source

9. Migrate your content.
If you’re working with a technical partner, ask them early in the process how they typically handle content migration. This can be a huge — and hugely expensive — job, and it’s not always included in the redesign quote.

If you have a small amount of content, or are building a site for the first time, this may be something you can handle on your own. But if you have even a moderate amount of content, trying to do a manual migration is a daunting, time-consuming task.

10. Make a post-launch checklist.
The period immediately after a website relaunch is a critical time: You’ll find bugs or other glitches, a stakeholder will ask why a logo is purple when they thought it would be green, or links will be broken.

Don’t panic! Even the best-laid plans always have a hiccup or two. I like to allow an extra two weeks after a relaunch to find all the bugs. (Then I take a long vacation; web relaunches are a lot of work.)


Implement a bug-reporting system. Stakeholders should know czech republic whatsapp number database how to report any bugs they find, whether that’s using an automated system or simply Slacking a single person who can track everything.
Spot-check your new site for broken links and images. Look at some of your highest-performing pages. Are there any glaring errors, like broken links, broken images, or formatting issues?
Check for 404 errors. After leading a web relaunch that involved significant changes to URL structure, I found that a number of pages were still returning 404 errors. Solutions to 404 errors can get somewhat technical, so consult with your tech or product team before setting up redirect links yourself.
Have a plan for your old website. If you’ve built a brand new website and migrated your old content, you may effectively have a duplicate of your entire website. In most cases, this won’t turn into a problem — your tech or product team will follow best practices to make sure the transition is seamless.
But in one redesign I worked on, this became an issue because we migrated the content in stages — meaning that we needed two active websites for a period of time.