A website relaunch is a launch: run it like one

Most website redesigns are run as projects with a finish line: the agency hands over, somebody presses the button, and the team moves on. A relaunch is better run as a launch, with an owner, a date, a set of readiness checks and a plan for reading the results. The difference matters most for an industrial company, whose old site, however dated it looks, is often the source of a steady trickle of enquiries from buyers who searched for a specific product, grade or capability.

The new site starts life with that trickle at risk. URLs change, pages are merged or dropped, the staging setup leaks into production, and a form that worked for eight years now sends enquiries to a mailbox nobody reads. A design review catches none of these, so they usually come to light only when enquiries fall in the weeks after the switch.

What does launch discipline mean for a website?

Launch discipline means four things exist before the switchover: one owner, one date, a readiness check and a measurement plan. Each one closes a gap that redesign projects leave open by default.

• An owner on the business side. The developer owns the build. Somebody inside the company has to own the decision to go live, the content sign-off and the review a month later. In a manufacturing company this is usually the marketing head or a director, and it should be written down with a name.
• A fixed switchover date. A date chosen in advance lets everything else be scheduled backwards from it: the redirect map, the staging checks, the content freeze. Google's site move guidance suggests moving during a period of lower traffic, so avoid the week before a trade fair or any month in which your enquiries usually peak.
• A readiness check. A list of conditions the new site must meet before it replaces the old one, each with a pass or fail. The eight dimensions below give that list a structure.
• A measurement plan. A baseline taken from the old site before the switch, and a fixed reading of the new one over thirty days.

The eight readiness dimensions, mapped to a relaunch

The launch readiness framework scores a launch across eight dimensions. Each one applies to a website relaunch with a slightly different meaning, and translating them gives a manufacturer a checklist that covers more than the technical move.

Two of these translate less obviously. Demand evidence, for a product launch, means proof that people want the thing. For a relaunch it means knowing what the old site already does well. If a page about a particular flange standard or a stainless steel grade brings in three enquiries a month, that page is evidence of demand, and the redesign has to keep it, redirect it properly, or improve it. Product and activation, for a product, means a new user reaching value. For a manufacturer's website the equivalent moment is a buyer getting a useful reply to an enquiry, which depends on the inbox, the routing and the person behind it as much as on the site.

Which checks matter most on switchover day?

On the day itself, search foundations, the conversion path and measurement matter most, in that order. The other dimensions should have been settled weeks earlier, and switchover day is too late to rewrite positioning.

Search foundations: can search engines still reach and read the site?

The commonest relaunch failure is a staging setting that reaches production. Google's site move documentation lists leftover noindex rules and robots.txt blocks among the common mistakes, and recommends preparing in advance the list of URLs from which noindex will be removed. On the day, check that the live site returns no noindex in the page or in the HTTP header (Google's noindex documentation covers both forms), that robots.txt blocks only what you intend, and that each important old URL sends a single permanent redirect to its matching new page. Google recommends server-side permanent redirects such as 301 or 308, advises against sending many old URLs to an unrelated page such as the new homepage, and says to keep redirects for at least a year.

Conversion path: do enquiries still arrive?

A redesigned form often posts to a new script, uses a new mail sender, or sits behind a new spam filter. Submit a real enquiry from every form on the live site, from a phone and from a desktop, and confirm each one lands in the inbox that sales watches. Check the WhatsApp and phone links too. A form that fails without showing an error is especially costly, because nothing alerts anyone until sales notices that enquiries have stopped.

Measurement: is anything being recorded?

Confirm analytics fires on the new templates, that enquiry submissions are recorded as conversions, and that Search Console is verified for the live site. A relaunch measured from day three loses the first two days of comparison, and those are the days most likely to show a fault.

What should the measurement plan contain?

The measurement plan should contain a baseline from the old site and a fixed set of readings over thirty days after the switch. Write it before switchover, so the numbers cannot be chosen afterwards to suit the result.

The baseline needs four numbers taken across the same period last year and the last ninety days: organic visits to the site, enquiries received through the site, the top fifty landing pages by organic visits, and the number of pages Google reports as indexed. Add one reading that is easy to forget: ask three AI assistants the questions a buyer would ask about your product category and note whether the company is named and described correctly. That gives the relaunch an AI visibility baseline, which cannot be reconstructed once the old site is gone.

After the switch, read the same numbers weekly. Google says rankings can fluctuate temporarily during a move and that small and medium sites can take a few weeks for most pages to move, so a dip in week one is normal and a dip still deepening in week four is not. The post-launch 30 day measurement plan covers how to read a month of data without reacting to noise. For a relaunch, the one number to watch most closely is enquiries from organic search, because it combines the search, conversion and activation dimensions into one figure the owner cares about.

Where relaunches usually go wrong

Relaunches tend to go wrong in the gap between the design project and the switchover, where nobody is clearly responsible. The design is signed off, the build is approved, and the move itself is treated as a technical step on a Friday evening.

The pattern repeats in a few forms. Content is rewritten during the redesign and the specification tables that buyers searched for are shortened or moved into a PDF. The URL structure changes for neatness and nobody builds the redirect map until the week of launch. The old hosting account is closed before Google has finished crawling the redirects. The new site is approved on a large monitor and nobody walks the enquiry path on a phone. Each of these belongs in the readiness list as a check with a named owner.

If you are still deciding whether the site needs a full rebuild or a set of repairs, SEOtop10's guide on whether to rebuild or repair a website covers that decision. For the scope and stages of a manufacturer's website transformation from planning to switchover, see EbizIndia's guide to website transformation for manufacturers.

How to start

Start by naming the owner and fixing the date, then run the launch readiness check against the new site on staging, answering each question for the relaunch rather than for a product. Any dimension that scores below half is where the next two weeks should go. Record the baseline the same week, before anyone touches the live site, and put the thirty day review in the calendar with the people who will have to act on what it finds.